Yesterday

• 46 hours ago

  issue 19 (Compilation Error) commented on by andrew.lyon   -   please post your .config

  please post your .config

Last 7 days

• Dec 17, 2009

  issue 19 (Compilation Error) reported by edufrazao   -   What steps will reproduce the problem? 1. Configuring and Compiling Kernel Error message: CC drivers/xen/balloon/balloon.o CC drivers/xen/balloon/sysfs.o LD drivers/xen/balloon/built-in.o CC drivers/xen/blkback/blkback.o CC drivers/xen/blkback/xenbus.o CC drivers/xen/blkback/interface.o CC drivers/xen/blkback/vbd.o CC drivers/xen/blkback/cdrom.o LD drivers/xen/blkback/blkbk.o LD drivers/xen/blkback/built-in.o CC drivers/xen/char/mem.o LD drivers/xen/char/built-in.o CC drivers/xen/console/console.o CC drivers/xen/console/xencons_ring.o LD drivers/xen/console/built-in.o CC drivers/xen/core/evtchn.o /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c: In function 'arch_init_chip_data': /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1640: error: 'struct irq_desc' has no member named 'affinity' /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c: In function 'arch_probe_nr_irqs': /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1666: error: 'nr_ioapics' undeclared (first use in this function) /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1666: error: (Each undeclared identifier is reported only once /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1666: error: for each function it appears in.) /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1667: error: implicit declaration of function 'io_apic_get_redir_entries' make[4]: *** [drivers/xen/core/evtchn.o] Error 1 make[3]: *** [drivers/xen/core] Error 2 make[2]: *** [drivers/xen] Error 2 make[1]: *** [drivers] Error 2 make: *** [sub-make] Error 2 Hardware: XEON 5504 // 4GB RAM GCC: gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) Many thanks!

  What steps will reproduce the problem? 1. Configuring and Compiling Kernel Error message: CC drivers/xen/balloon/balloon.o CC drivers/xen/balloon/sysfs.o LD drivers/xen/balloon/built-in.o CC drivers/xen/blkback/blkback.o CC drivers/xen/blkback/xenbus.o CC drivers/xen/blkback/interface.o CC drivers/xen/blkback/vbd.o CC drivers/xen/blkback/cdrom.o LD drivers/xen/blkback/blkbk.o LD drivers/xen/blkback/built-in.o CC drivers/xen/char/mem.o LD drivers/xen/char/built-in.o CC drivers/xen/console/console.o CC drivers/xen/console/xencons_ring.o LD drivers/xen/console/built-in.o CC drivers/xen/core/evtchn.o /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c: In function 'arch_init_chip_data': /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1640: error: 'struct irq_desc' has no member named 'affinity' /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c: In function 'arch_probe_nr_irqs': /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1666: error: 'nr_ioapics' undeclared (first use in this function) /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1666: error: (Each undeclared identifier is reported only once /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1666: error: for each function it appears in.) /usr/src/linux-2.6.31-xen-r9/drivers/xen/core/evtchn.c:1667: error: implicit declaration of function 'io_apic_get_redir_entries' make[4]: *** [drivers/xen/core/evtchn.o] Error 1 make[3]: *** [drivers/xen/core] Error 2 make[2]: *** [drivers/xen] Error 2 make[1]: *** [drivers] Error 2 make: *** [sub-make] Error 2 Hardware: XEON 5504 // 4GB RAM GCC: gcc version 4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) Many thanks!
• Dec 17, 2009

  issue 18 (2.6.31-r7 compiles okay but system is instable) commented on by sven.sch...@gmail.com   -   Done that already and it's running stable (but under little load) for 20hrs now. Thanks for the patching!!

  Done that already and it's running stable (but under little load) for 20hrs now. Thanks for the patching!!
• Dec 17, 2009

  issue 18 (2.6.31-r7 compiles okay but system is instable) commented on by andrew.lyon   -   Please try -r9 ebuild. andy

  Please try -r9 ebuild. andy
• Dec 16, 2009

  xen-sources-2.6.31-r9.ebuild (2.6.31-r9 ebuild ) file uploaded by andrew.lyon
• Dec 16, 2009

  xen-patches-2.6.31-9.tar.bz2 (2.6.31 xen patches v9 (rebased minimal openSUSE-11.2 patches...) file uploaded by andrew.lyon
• Dec 14, 2009

  issue 18 (2.6.31-r7 compiles okay but system is instable) reported by sven.sch...@gmail.com   -   I'm running a i7-920 with 8G RAM and two SATA HDs in a softraid. Dom0 (this kernel) is pinned to 1 CPU and only one DomU (Gentoo 2.6.31) is active. DomU's root partition is a 180GB ext4 file, furthermore it has it's own physical 50GB partition for the swapfile, logs, database etc. Xen is at 3.4.2 with routed networking. Both Dom0 and DomU boot just fine, but after some hours without much load, the machine becomes unresponsive and has to be resetted. (With unresponsive I mean that you can't connect via SSH neither Dom0 nor DomU. I don't have physical access to the hardware.) The logs however don't show anything odd at all. There seems to be an issue in the most recent Suse patches which causes this behavior for machines using physical partitions for root - which is not the case here.

  I'm running a i7-920 with 8G RAM and two SATA HDs in a softraid. Dom0 (this kernel) is pinned to 1 CPU and only one DomU (Gentoo 2.6.31) is active. DomU's root partition is a 180GB ext4 file, furthermore it has it's own physical 50GB partition for the swapfile, logs, database etc. Xen is at 3.4.2 with routed networking. Both Dom0 and DomU boot just fine, but after some hours without much load, the machine becomes unresponsive and has to be resetted. (With unresponsive I mean that you can't connect via SSH neither Dom0 nor DomU. I don't have physical access to the hardware.) The logs however don't show anything odd at all. There seems to be an issue in the most recent Suse patches which causes this behavior for machines using physical partitions for root - which is not the case here.

Earlier this year

• Oct 28, 2009

  issue 16 (xen-sources-2.6.31-r4: Compilation fails) commented on by andrew.lyon   -   fixed in r7.

  fixed in r7.
• Oct 28, 2009

  issue 17 (xen-sources-2.6.31-r4: Kernel Compile Error) commented on by andrew.lyon   -   I think openSUSE only support Xen 3.0.4 or later, if you set "Xen version compatibility" to 3.0.4 or greater I think you will find the compile is successful. Andy

  I think openSUSE only support Xen 3.0.4 or later, if you set "Xen version compatibility" to 3.0.4 or greater I think you will find the compile is successful. Andy
• Oct 28, 2009

  xen-sources-2.6.31-r7.ebuild (2.6.31-r7 ebuild ) file uploaded by andrew.lyon
• Oct 28, 2009

  xen-patches-2.6.31-7.tar.bz2 (2.6.31 xen patches v7 (rebased patches.xen from opensuse kot...) file uploaded by andrew.lyon
• Oct 28, 2009

  xen-patches-2.6.31-6.tar.bz2 (2.6.31 xen patches v6 (rebased patches.xen from opensuse kot...) file uploaded by andrew.lyon
• Oct 28, 2009

  xen-sources-2.6.31-r6.ebuild (2.6.31-r6 ebuild) file uploaded by andrew.lyon
• Oct 22, 2009

  xen-sources-2.6.31-r5.ebuild (2.6.31-r5 ebuild) file uploaded by andrew.lyon
• Oct 22, 2009

  xen-patches-2.6.31-5.tar.bz2 (2.6.31 xen patches v5 (rebased patches.xen from opensuse ker...) file uploaded by andrew.lyon
• Oct 16, 2009

  issue 17 (xen-sources-2.6.31-r4: Kernel Compile Error) reported by h.meissner   -   32bit Kernel With XEN disabled, kernel make runs fine. With XEN enabled this error occurs: AR arch/x86/lib/lib.a LD vmlinux.o MODPOST vmlinux.o WARNING: vmlinux.o (__xen_guest): unexpected non-allocatable section. Did you forget to use "ax"/"aw" in a .S file? Note that for example <linux/init.h> contains section definitions for use in .S files. WARNING: modpost: Found 1 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 ld: kernel image bigger than KERNEL_IMAGE_SIZE ld: kernel image bigger than KERNEL_IMAGE_SIZE drivers/built-in.o: In function `ioat_dca_get_tag': ioat_dca.c:(.text+0xa09dc): undefined reference to `per_cpu__x86_cpu_to_apicid' drivers/built-in.o: In function `ioat2_dca_get_tag': ioat_dca.c:(.text+0xa0b22): undefined reference to `per_cpu__x86_cpu_to_apicid' drivers/built-in.o: In function `ioat3_dca_get_tag': ioat_dca.c:(.text+0xa0c4b): undefined reference to `per_cpu__x86_cpu_to_apicid' make: *** [.tmp_vmlinux1] Error 1 Any idea?

  32bit Kernel With XEN disabled, kernel make runs fine. With XEN enabled this error occurs: AR arch/x86/lib/lib.a LD vmlinux.o MODPOST vmlinux.o WARNING: vmlinux.o (__xen_guest): unexpected non-allocatable section. Did you forget to use "ax"/"aw" in a .S file? Note that for example <linux/init.h> contains section definitions for use in .S files. WARNING: modpost: Found 1 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 ld: kernel image bigger than KERNEL_IMAGE_SIZE ld: kernel image bigger than KERNEL_IMAGE_SIZE drivers/built-in.o: In function `ioat_dca_get_tag': ioat_dca.c:(.text+0xa09dc): undefined reference to `per_cpu__x86_cpu_to_apicid' drivers/built-in.o: In function `ioat2_dca_get_tag': ioat_dca.c:(.text+0xa0b22): undefined reference to `per_cpu__x86_cpu_to_apicid' drivers/built-in.o: In function `ioat3_dca_get_tag': ioat_dca.c:(.text+0xa0c4b): undefined reference to `per_cpu__x86_cpu_to_apicid' make: *** [.tmp_vmlinux1] Error 1 Any idea?
• Oct 15, 2009

  issue 16 (xen-sources-2.6.31-r4: Compilation fails) reported by blshadow   -   What steps will reproduce the problem? 1. Enable CONFIG_MICROCODE option 2. Try to build kernel Error message: arch/x86/kernel/microcode_core-xen.c: In function 'microcode_write': arch/x86/kernel/microcode_core-xen.c:100: error: 'totalram_pages' undeclared (first use in this function) arch/x86/kernel/microcode_core-xen.c:100: error: (Each undeclared identifier is reported only once arch/x86/kernel/microcode_core-xen.c:100: error: for each function it appears in.) make[2]: *** [arch/x86/kernel/microcode_core.o] Error 1 Patch to fix this error: --- linux-2.6.31-xen-r4/arch/x86/kernel/microcode_core-xen.c.orig 2009-10-15 20:22:24.000000000 +0400 +++ linux-2.6.31-xen-r4/arch/x86/kernel/microcode_core-xen.c 2009-10-15 20:24:04.000000000 +0400 @@ -34,6 +34,7 @@ #include <linux/firmware.h> #include <linux/uaccess.h> #include <linux/vmalloc.h> +#include <linux/swap.h> #include <asm/microcode.h> #include <asm/processor.h>

  What steps will reproduce the problem? 1. Enable CONFIG_MICROCODE option 2. Try to build kernel Error message: arch/x86/kernel/microcode_core-xen.c: In function 'microcode_write': arch/x86/kernel/microcode_core-xen.c:100: error: 'totalram_pages' undeclared (first use in this function) arch/x86/kernel/microcode_core-xen.c:100: error: (Each undeclared identifier is reported only once arch/x86/kernel/microcode_core-xen.c:100: error: for each function it appears in.) make[2]: *** [arch/x86/kernel/microcode_core.o] Error 1 Patch to fix this error: --- linux-2.6.31-xen-r4/arch/x86/kernel/microcode_core-xen.c.orig 2009-10-15 20:22:24.000000000 +0400 +++ linux-2.6.31-xen-r4/arch/x86/kernel/microcode_core-xen.c 2009-10-15 20:24:04.000000000 +0400 @@ -34,6 +34,7 @@ #include <linux/firmware.h> #include <linux/uaccess.h> #include <linux/vmalloc.h> +#include <linux/swap.h> #include <asm/microcode.h> #include <asm/processor.h>
• Oct 15, 2009

  issue 13 (Build error) commented on by gu...@anka.net.pl   -   It works (now 2.6.31-xen-r4)

  It works (now 2.6.31-xen-r4)
• Oct 14, 2009

  xen-sources-2.6.31-r4.ebuild (2.6.31-r4 ebuild) file uploaded by andrew.lyon
• Oct 14, 2009

  xen-patches-2.6.31-4.tar.bz2 (2.6.31 xen patches v4 (rebased patches.xen from opensuse ker...) file uploaded by andrew.lyon
• Oct 05, 2009

  issue 13 (Build error) commented on by kornelijus   -   try with CONFIG_ACPI_PROCESSOR=y

  try with CONFIG_ACPI_PROCESSOR=y
• Aug 16, 2009

  issue 15 (Suspend (xm save) not working) reported by valtt...@kiviniemi.net   -   Hi, When I try to run "xm save" the domU will shutdown and in xend.log I can see following: 2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:110) [xc_save]: /usr/lib64/xen/bin/xc_save 57 6 0 0 0 [2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417) ERROR Internal error: Can't create lock file for suspend event channel [2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417) [2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417) xc_save: suspend event channel initialization failedusing slow path [2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:388) suspend [2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:113) In saveInputHandler suspend [2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:115) Suspending 6 ... [2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:511) XendDomainInfo.shutdown(suspend) [2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:1709) XendDomainInfo.handleShutdownWatch [2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:1709) XendDomainInfo.handleShutdownWatch Same problem with 2.6.29 and 2.6.30. Xen version is 3.4.1.

  Hi, When I try to run "xm save" the domU will shutdown and in xend.log I can see following: 2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:110) [xc_save]: /usr/lib64/xen/bin/xc_save 57 6 0 0 0 [2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417) ERROR Internal error: Can't create lock file for suspend event channel [2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417) [2009-07-16 18:09:34 2559] INFO (XendCheckpoint:417) xc_save: suspend event channel initialization failedusing slow path [2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:388) suspend [2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:113) In saveInputHandler suspend [2009-07-16 18:09:34 2559] DEBUG (XendCheckpoint:115) Suspending 6 ... [2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:511) XendDomainInfo.shutdown(suspend) [2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:1709) XendDomainInfo.handleShutdownWatch [2009-07-16 18:09:34 2559] DEBUG (XendDomainInfo:1709) XendDomainInfo.handleShutdownWatch Same problem with 2.6.29 and 2.6.30. Xen version is 3.4.1.
• Aug 13, 2009

  issue 7 (bad register name `%bpl') commented on by ben.langenberg   -   same for me openSuse 11.1 on Intel Xeon: scripts/kconfig/conf -s arch/x86/Kconfig CHK include/linux/version.h CHK include/linux/utsrelease.h CALL scripts/checksyscalls.sh CHK include/linux/compile.h CC arch/x86/mm/fault.o arch/x86/mm/fault-xen.c: Assembler messages: arch/x86/mm/fault-xen.c:303: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:315: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:303: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:315: Error: bad register name `%bpl' make[1]: *** [arch/x86/mm/fault.o] Error 1 make: *** [arch/x86/mm] Error 2

  same for me openSuse 11.1 on Intel Xeon: scripts/kconfig/conf -s arch/x86/Kconfig CHK include/linux/version.h CHK include/linux/utsrelease.h CALL scripts/checksyscalls.sh CHK include/linux/compile.h CC arch/x86/mm/fault.o arch/x86/mm/fault-xen.c: Assembler messages: arch/x86/mm/fault-xen.c:303: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:315: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:303: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:315: Error: bad register name `%bpl' make[1]: *** [arch/x86/mm/fault.o] Error 1 make: *** [arch/x86/mm] Error 2
• Aug 12, 2009

  issue 7 (bad register name `%bpl') commented on by hel...@quasar-net.de   -   same here. but it is a 32bit problem, i think.

  same here. but it is a 32bit problem, i think.
• Aug 11, 2009

  issue 7 (bad register name `%bpl') commented on by giorgenes   -   same for me: arch/x86/mm/fault-xen.c: Assembler messages: arch/x86/mm/fault-xen.c:304: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:316: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:304: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:316: Error: bad register name `%bpl'

  same for me: arch/x86/mm/fault-xen.c: Assembler messages: arch/x86/mm/fault-xen.c:304: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:316: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:304: Error: bad register name `%bpl' arch/x86/mm/fault-xen.c:316: Error: bad register name `%bpl'
• Aug 10, 2009

  issue 14 (Build failure: xen/core/firmware.c: implicit declaration of ...) reported by reto.gantenbein   -   Architecture: i686 Xen Configuration: domU only/Xen-3.1.0 compatibility (for CentOS dom0) What steps will reproduce the problem? 1. install xen-sources-2.6.29-r4 2. build kernel with config-2.6.29-domU What is the expected output? What do you see instead? bzImage of kernel is expected, but I see a build error: [...] CC drivers/xen/console/xencons_ring.o LD drivers/xen/console/built-in.o CC drivers/xen/core/evtchn.o drivers/xen/core/evtchn.c: In function 'evtchn_from_per_cpu_irq': drivers/xen/core/evtchn.c:182: warning: no return statement in function returning non-void CC drivers/xen/core/gnttab.o CC drivers/xen/core/features.o CC drivers/xen/core/reboot.o CC drivers/xen/core/machine_reboot.o CC drivers/xen/core/firmware.o drivers/xen/core/firmware.c: In function 'copy_edid': drivers/xen/core/firmware.c:72: error: implicit declaration of function 'memset' make[3]: *** [drivers/xen/core/firmware.o] Error 1 make[2]: *** [drivers/xen/core] Error 2 make[1]: *** [drivers/xen] Error 2 make: *** [drivers] Error 2 What version of the product are you using? On what operating system? xen-sources-2.6.29-r4, Funtoo (2008.0), gcc (Gentoo 4.3.3-r2 p1.1, pie-10.1.5) 4.3.3 See config-2.6.29-domU

  Architecture: i686 Xen Configuration: domU only/Xen-3.1.0 compatibility (for CentOS dom0) What steps will reproduce the problem? 1. install xen-sources-2.6.29-r4 2. build kernel with config-2.6.29-domU What is the expected output? What do you see instead? bzImage of kernel is expected, but I see a build error: [...] CC drivers/xen/console/xencons_ring.o LD drivers/xen/console/built-in.o CC drivers/xen/core/evtchn.o drivers/xen/core/evtchn.c: In function 'evtchn_from_per_cpu_irq': drivers/xen/core/evtchn.c:182: warning: no return statement in function returning non-void CC drivers/xen/core/gnttab.o CC drivers/xen/core/features.o CC drivers/xen/core/reboot.o CC drivers/xen/core/machine_reboot.o CC drivers/xen/core/firmware.o drivers/xen/core/firmware.c: In function 'copy_edid': drivers/xen/core/firmware.c:72: error: implicit declaration of function 'memset' make[3]: *** [drivers/xen/core/firmware.o] Error 1 make[2]: *** [drivers/xen/core] Error 2 make[1]: *** [drivers/xen] Error 2 make: *** [drivers] Error 2 What version of the product are you using? On what operating system? xen-sources-2.6.29-r4, Funtoo (2008.0), gcc (Gentoo 4.3.3-r2 p1.1, pie-10.1.5) 4.3.3 See config-2.6.29-domU
• Aug 04, 2009

  issue 13 (Build error) commented on by gu...@anka.net.pl   -   I found this http://d.hatena.ne.jp/int128/20081218/1229612504 It's work

  I found this http://d.hatena.ne.jp/int128/20081218/1229612504 It's work
• Aug 04, 2009

  issue 13 (Build error) commented on by gu...@anka.net.pl   -   Same error on x86_64 (-march=nocona) with gcc 4.1.2

  Same error on x86_64 (-march=nocona) with gcc 4.1.2
• Aug 03, 2009

  issue 13 (Build error) reported by gu...@anka.net.pl   -   When I try to compile sources I've got: --- [...] CC arch/x86/lib/scrub.o CC arch/x86/lib/string_32.o CC arch/x86/lib/strstr_32.o CC arch/x86/lib/usercopy_32.o AR arch/x86/lib/lib.a LD vmlinux.o MODPOST vmlinux.o WARNING: vmlinux.o(.exit.text+0x35c): Section mismatch in reference from the function evtchn_cleanup() to the variable .cpuinit.data:evtchn_cpu_nfb The function __exit evtchn_cleanup() references a variable __cpuinitdata evtchn_cpu_nfb. This is often seen when error handling in the exit function uses functionality in the init path. The fix is often to remove the __cpuinitdata annotation of evtchn_cpu_nfb so it may be used outside an init section. GEN .version CHK include/linux/compile.h dnsdomainname: Unknown host UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 arch/x86/kernel/built-in.o: In function `show_cpuinfo': proc.c:(.text+0x8e14): undefined reference to `cpufreq_quick_get' make[1]: *** [.tmp_vmlinux1] Error 1 make: *** [sub-make] Error 2 --- xen-sources-2.6.30-r2 x86 (Pentium4) -- guzik

  When I try to compile sources I've got: --- [...] CC arch/x86/lib/scrub.o CC arch/x86/lib/string_32.o CC arch/x86/lib/strstr_32.o CC arch/x86/lib/usercopy_32.o AR arch/x86/lib/lib.a LD vmlinux.o MODPOST vmlinux.o WARNING: vmlinux.o(.exit.text+0x35c): Section mismatch in reference from the function evtchn_cleanup() to the variable .cpuinit.data:evtchn_cpu_nfb The function __exit evtchn_cleanup() references a variable __cpuinitdata evtchn_cpu_nfb. This is often seen when error handling in the exit function uses functionality in the init path. The fix is often to remove the __cpuinitdata annotation of evtchn_cpu_nfb so it may be used outside an init section. GEN .version CHK include/linux/compile.h dnsdomainname: Unknown host UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 arch/x86/kernel/built-in.o: In function `show_cpuinfo': proc.c:(.text+0x8e14): undefined reference to `cpufreq_quick_get' make[1]: *** [.tmp_vmlinux1] Error 1 make: *** [sub-make] Error 2 --- xen-sources-2.6.30-r2 x86 (Pentium4) -- guzik
• Aug 01, 2009

  issue 4 (making the kernel fail with r4/r5) commented on by xdeller   -   I`ve get same error with gcc-3.4.6(hardened profile) but with 4.3.2 all seems okay. Unfortunately hardened USE flags available only for 4.3.3+ but this version of gcc does not make sufficiently stable binaries even for desktop right now(this is my experience).

  I`ve get same error with gcc-3.4.6(hardened profile) but with 4.3.2 all seems okay. Unfortunately hardened USE flags available only for 4.3.3+ but this version of gcc does not make sufficiently stable binaries even for desktop right now(this is my experience).
• Jul 20, 2009

  issue 12 (Wrong image format) commented on by wsong.cn   -   My bad. It's due to a stupid copy&paste error. I copied the grub entry and didn't change 'kernel' to 'module'.

  My bad. It's due to a stupid copy&paste error. I copied the grub entry and didn't change 'kernel' to 'module'.
• Jul 19, 2009

  issue 12 (Wrong image format) commented on by wsong.cn   -   The error message is "Invalid or unsupported executable format"

  The error message is "Invalid or unsupported executable format"
• Jul 19, 2009

  issue 12 (Wrong image format) reported by wsong.cn   -   I applied v3 patch set to vanilla 2.6.30.1 kernel. If disable XEN the image boots. If I enable XEN, it always reports recognized format and refuse to boot. File command yields different outputs on xen enabled/disabled kernel image. Please advise. file /boot/vmlinuz-2.6.30.1-xen /boot/vmlinuz-2.6.30.1-xen: gzip compressed data, from Unix, last modified: Sun Jul 19 20:17:42 2009, max compression file /boot/bzImage-noxen /boot/vmlinuz-2.6.30.1-noxen: Linux kernel x86 boot executable RO-rootFS, root_dev 0x805, swap_dev 0x3, Normal VGA

  I applied v3 patch set to vanilla 2.6.30.1 kernel. If disable XEN the image boots. If I enable XEN, it always reports recognized format and refuse to boot. File command yields different outputs on xen enabled/disabled kernel image. Please advise. file /boot/vmlinuz-2.6.30.1-xen /boot/vmlinuz-2.6.30.1-xen: gzip compressed data, from Unix, last modified: Sun Jul 19 20:17:42 2009, max compression file /boot/bzImage-noxen /boot/vmlinuz-2.6.30.1-noxen: Linux kernel x86 boot executable RO-rootFS, root_dev 0x805, swap_dev 0x3, Normal VGA
• Jul 19, 2009

  issue 11 (kernel build fails) commented on by wsong.cn   -   Enable older network device API compatibility, first option in Network driver section

  Enable older network device API compatibility, first option in Network driver section
• Jul 17, 2009

  issue 11 (kernel build fails) reported by sstahl   -   When I try to make the kernel I get the following error: /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c: In function 'netif_alloc': /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:212: error: 'struct net_device' has no member named 'hard_start_xmit' /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:213: error: 'struct net_device' has no member named 'get_stats' /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:214: error: 'struct net_device' has no member named 'open' /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:215: error: 'struct net_device' has no member named 'stop' /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:216: error: 'struct net_device' has no member named 'change_mtu' make[4]: *** [drivers/xen/netback/interface.o] Error 1 make[3]: *** [drivers/xen/netback] Error 2 make[2]: *** [drivers/xen] Error 2 make[1]: *** [drivers] Error 2 make: *** [sub-make] Error 2 I assume this is part of the XEN networking backend?

  When I try to make the kernel I get the following error: /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c: In function 'netif_alloc': /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:212: error: 'struct net_device' has no member named 'hard_start_xmit' /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:213: error: 'struct net_device' has no member named 'get_stats' /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:214: error: 'struct net_device' has no member named 'open' /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:215: error: 'struct net_device' has no member named 'stop' /usr/src/linux-2.6.30-xen-r2/drivers/xen/netback/interface.c:216: error: 'struct net_device' has no member named 'change_mtu' make[4]: *** [drivers/xen/netback/interface.o] Error 1 make[3]: *** [drivers/xen/netback] Error 2 make[2]: *** [drivers/xen] Error 2 make[1]: *** [drivers] Error 2 make: *** [sub-make] Error 2 I assume this is part of the XEN networking backend?
• Jul 15, 2009

  issue 10 (Compile error with CONFIG_SPARSE_IRQ turned off) commented on by Suertreus   -   Patch to drivers/xen/core/evtchn.c attached.

  Patch to drivers/xen/core/evtchn.c attached.
• Jul 14, 2009

  issue 1 (Can you post where you got the patches from opensuses from?) commented on by elcorreodeale   -   http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/src/ http://download.opensuse.org/factory/repo/src-oss/suse/src/ http://download.opensuse.org/repositories/Base:/Kernel/standard/src/ ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/ read more at gentoo forums. if you want to. http://forums.gentoo.org/viewtopic-t-709908-postdays-0-postorder-asc-start-125.html

  http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/src/ http://download.opensuse.org/factory/repo/src-oss/suse/src/ http://download.opensuse.org/repositories/Base:/Kernel/standard/src/ ftp://ftp.suse.com/pub/projects/kernel/kotd/HEAD/x86_64/ read more at gentoo forums. if you want to. http://forums.gentoo.org/viewtopic-t-709908-postdays-0-postorder-asc-start-125.html
• Jul 10, 2009

  issue 10 (Compile error with CONFIG_SPARSE_IRQ turned off) commented on by blshadow   -   Same here

  Same here
• Jul 09, 2009

  issue 10 (Compile error with CONFIG_SPARSE_IRQ turned off) reported by Lutz.Heermann   -   I tried to compile xen-sources-2.6.30-r1 on an amd64 machine. With CONFIG_SPARSE_IRQ deactivated, I get the following comile error: drivers/xen/core/evtchn.c: In function 'unbind_from_irq': drivers/xen/core/evtchn.c:641: error: 'struct kernel_stat' has no member named 'irqs' After activating CONFIG_SPARSE_IRQ it compiles fine. Unfortunatly I could not test the kernel yet.

  I tried to compile xen-sources-2.6.30-r1 on an amd64 machine. With CONFIG_SPARSE_IRQ deactivated, I get the following comile error: drivers/xen/core/evtchn.c: In function 'unbind_from_irq': drivers/xen/core/evtchn.c:641: error: 'struct kernel_stat' has no member named 'irqs' After activating CONFIG_SPARSE_IRQ it compiles fine. Unfortunatly I could not test the kernel yet.
• Jul 08, 2009

  issue 9 (arch/x86/kernel/cpu/common-xen.c:1067: error: 'KERN_WARN' un...) reported by tzvala   -   I get this error when compiling with attached .config. Patching the file to use KERN_WARNING instead fixes the error, but i'm quite not sure, if it's not breaking anything else ...

  I get this error when compiling with attached .config. Patching the file to use KERN_WARNING instead fixes the error, but i'm quite not sure, if it's not breaking anything else ...
• Jul 01, 2009

  xen-patches-2.6.30-2.tar.bz2 (2.6.30 xen patches v2 (rebased patches.xen from opensuse ker...) file uploaded by andrew.lyon
• Jul 01, 2009

  xen-sources-2.6.30-r1.ebuild (2.6.30-r1 ebuild) file uploaded by andrew.lyon
• May 20, 2009

  xen-patches-2.6.29-6.tar.bz2 (2.6.29 xen patches v5 (rebased patches.xen from opensuse ker...) file uploaded by andrew.lyon
• May 20, 2009

  xen-sources-2.6.29-r4.ebuild (2.6.29-r4 ebuild ) file uploaded by andrew.lyon
• May 17, 2009

  issue 4 (making the kernel fail with r4/r5) commented on by adwo...@ayuda.com.au   -   Same problem exists with 2.6.29-r3

  Same problem exists with 2.6.29-r3
• May 17, 2009

  xen-patches-2.6.29-5.tar.bz2 (2.6.29 xen patches v5 (rebased patches.xen from opensuse ker...) file uploaded by andrew.lyon
• May 17, 2009

  xen-sources-2.6.29-r3.ebuild (2.6.29-r3 ebuild ) file uploaded by andrew.lyon
• May 12, 2009

  issue 8 (tap:aio/tap:sync causes disk subsystem freeze) commented on by ybdaba   -   Got same serious problem, when using guest at lvm http://pastebin.com/m3c0a061d dmesg

  Got same serious problem, when using guest at lvm http://pastebin.com/m3c0a061d dmesg
• Apr 17, 2009

  issue 8 (tap:aio/tap:sync causes disk subsystem freeze) reported by tzvala   -   What steps will reproduce the problem? 1. Use 2.6.29-r1 ebuild found here 2. Create temporary empty file using dd 3. Start PV Guest with tap:aio or tap:sync block device backend What is the expected output? What do you see instead? I guess it should work like a charm, but i get this instead: [ 159.568089] ------------[ cut here ]------------ [ 159.568952] kernel BUG at /usr/src/linux-2.6.29-xen-r1/arch/x86/include/mach-xen/asm/hypervisor.h:200! [ 159.568952] invalid opcode: 0000 [#1] SMP [ 159.568952] last sysfs file: /sys/class/misc/evtchn/dev [ 159.568952] CPU 0 [ 159.568952] Modules linked in: fuse [ 159.568952] Pid: 5613, comm: blktap.1.sda Not tainted 2.6.29-xen-r1blade #6 B7DW3 [ 159.568952] RIP: e030:[<ffffffff805d6bbd>] [<ffffffff805d6bbd>] dispatch_rw_block_io+0x4cd/0xbb0 [ 159.568952] RSP: e02b:ffff88003844fa70 EFLAGS: 00010202 [ 159.568952] RAX: 0000000000000000 RBX: ffff88003844fe80 RCX: 0000000000000001 [ 159.568952] RDX: 0000000000000002 RSI: ffff88003844fb50 RDI: 0000000000000000 [ 159.568952] RBP: ffff88003844fe50 R08: 0000000000223db1 R09: 0000000000000000 [ 159.568952] R10: 0000000000000000 R11: ffff880001008200 R12: 0000000000000002 [ 159.568952] R13: 0000000000000002 R14: ffff880039382480 R15: 0000000000000000 [ 159.568952] FS: 00007fb6f21b06f0(0000) GS:ffffffff80af2040(0000) knlGS:0000000000000000 [ 159.568952] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [ 159.568952] CR2: 00007f2fdb5a1000 CR3: 0000000039096000 CR4: 0000000000002620 [ 159.568952] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 159.568952] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 159.568952] Process blktap.1.sda (pid: 5613, threadinfo ffff88003844e000, task ffff88003680a610) [ 159.568952] Stack: [ 159.568952] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 159.568952] 0000000000000000 0000000000000000 0000000000000000 ffff88003e8da000 [ 159.568952] ffff88003844fe80 ffff8800390a9780 00007f40f77dc000 0000000000000000 [ 159.568952] Call Trace: [ 159.568952] [<ffffffff80209adc>] ? __switch_to+0x16c/0x740 [ 159.568952] [<ffffffff80230fe0>] ? update_curr+0xe0/0x130 [ 159.568952] [<ffffffff8023147d>] ? dequeue_task_fair+0x4d/0x190 [ 159.568952] [<ffffffff805d7320>] ? tap_blkif_schedule+0x0/0x770 [ 159.568952] [<ffffffff80825031>] ? thread_return+0x40/0x7ef [ 159.568952] [<ffffffff8022e77a>] ? __wake_up_common+0x5a/0x90 [ 159.568952] [<ffffffff805d7931>] tap_blkif_schedule+0x611/0x770 [ 159.568952] [<ffffffff805d7320>] ? tap_blkif_schedule+0x0/0x770 [ 159.568952] [<ffffffff80251859>] kthread+0x49/0x90 [ 159.568952] [<ffffffff8020c56a>] child_rip+0xa/0x20 [ 159.568952] [<ffffffff80251810>] ? kthread+0x0/0x90 [ 159.568952] [<ffffffff8020c560>] ? child_rip+0x0/0x20 [ 159.568952] Code: ff ff 31 ff e8 85 fe fe ff 31 ff 89 c1 48 8d b5 00 fd ff ff 44 89 ea e8 d2 06 c3 ff 41 89 c7 85 c0 0f 85 03 04 00 00 84 c9 74 0b <0f> 0b eb fe 0f 1f 80 00 00 00 00 80 3d d3 54 4a 00 00 0f 84 8b [ 159.568952] RIP [<ffffffff805d6bbd>] dispatch_rw_block_io+0x4cd/0xbb0 [ 159.568952] RSP <ffff88003844fa70> [ 159.582917] ---[ end trace 5421270289e5ca89 ]--- What version of the product are you using? On what operating system? xen-sources-2.6.29-r1 found here xen-3.3.0 from gentoo portage

  What steps will reproduce the problem? 1. Use 2.6.29-r1 ebuild found here 2. Create temporary empty file using dd 3. Start PV Guest with tap:aio or tap:sync block device backend What is the expected output? What do you see instead? I guess it should work like a charm, but i get this instead: [ 159.568089] ------------[ cut here ]------------ [ 159.568952] kernel BUG at /usr/src/linux-2.6.29-xen-r1/arch/x86/include/mach-xen/asm/hypervisor.h:200! [ 159.568952] invalid opcode: 0000 [#1] SMP [ 159.568952] last sysfs file: /sys/class/misc/evtchn/dev [ 159.568952] CPU 0 [ 159.568952] Modules linked in: fuse [ 159.568952] Pid: 5613, comm: blktap.1.sda Not tainted 2.6.29-xen-r1blade #6 B7DW3 [ 159.568952] RIP: e030:[<ffffffff805d6bbd>] [<ffffffff805d6bbd>] dispatch_rw_block_io+0x4cd/0xbb0 [ 159.568952] RSP: e02b:ffff88003844fa70 EFLAGS: 00010202 [ 159.568952] RAX: 0000000000000000 RBX: ffff88003844fe80 RCX: 0000000000000001 [ 159.568952] RDX: 0000000000000002 RSI: ffff88003844fb50 RDI: 0000000000000000 [ 159.568952] RBP: ffff88003844fe50 R08: 0000000000223db1 R09: 0000000000000000 [ 159.568952] R10: 0000000000000000 R11: ffff880001008200 R12: 0000000000000002 [ 159.568952] R13: 0000000000000002 R14: ffff880039382480 R15: 0000000000000000 [ 159.568952] FS: 00007fb6f21b06f0(0000) GS:ffffffff80af2040(0000) knlGS:0000000000000000 [ 159.568952] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b [ 159.568952] CR2: 00007f2fdb5a1000 CR3: 0000000039096000 CR4: 0000000000002620 [ 159.568952] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 159.568952] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [ 159.568952] Process blktap.1.sda (pid: 5613, threadinfo ffff88003844e000, task ffff88003680a610) [ 159.568952] Stack: [ 159.568952] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 159.568952] 0000000000000000 0000000000000000 0000000000000000 ffff88003e8da000 [ 159.568952] ffff88003844fe80 ffff8800390a9780 00007f40f77dc000 0000000000000000 [ 159.568952] Call Trace: [ 159.568952] [<ffffffff80209adc>] ? __switch_to+0x16c/0x740 [ 159.568952] [<ffffffff80230fe0>] ? update_curr+0xe0/0x130 [ 159.568952] [<ffffffff8023147d>] ? dequeue_task_fair+0x4d/0x190 [ 159.568952] [<ffffffff805d7320>] ? tap_blkif_schedule+0x0/0x770 [ 159.568952] [<ffffffff80825031>] ? thread_return+0x40/0x7ef [ 159.568952] [<ffffffff8022e77a>] ? __wake_up_common+0x5a/0x90 [ 159.568952] [<ffffffff805d7931>] tap_blkif_schedule+0x611/0x770 [ 159.568952] [<ffffffff805d7320>] ? tap_blkif_schedule+0x0/0x770 [ 159.568952] [<ffffffff80251859>] kthread+0x49/0x90 [ 159.568952] [<ffffffff8020c56a>] child_rip+0xa/0x20 [ 159.568952] [<ffffffff80251810>] ? kthread+0x0/0x90 [ 159.568952] [<ffffffff8020c560>] ? child_rip+0x0/0x20 [ 159.568952] Code: ff ff 31 ff e8 85 fe fe ff 31 ff 89 c1 48 8d b5 00 fd ff ff 44 89 ea e8 d2 06 c3 ff 41 89 c7 85 c0 0f 85 03 04 00 00 84 c9 74 0b <0f> 0b eb fe 0f 1f 80 00 00 00 00 80 3d d3 54 4a 00 00 0f 84 8b [ 159.568952] RIP [<ffffffff805d6bbd>] dispatch_rw_block_io+0x4cd/0xbb0 [ 159.568952] RSP <ffff88003844fa70> [ 159.582917] ---[ end trace 5421270289e5ca89 ]--- What version of the product are you using? On what operating system? xen-sources-2.6.29-r1 found here xen-3.3.0 from gentoo portage
• Apr 06, 2009

  xen-sources-2.6.29-r1.ebuild (2.6.29-r1 ebuild) file uploaded by andrew.lyon