WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Xen boot errors

Hi there,

I was trying to use the kernel patches at:

http://code.google.com/p/gentoo-xen-kernel/downloads/list?can=1&q=&colspec=Filename+Summary+Uploaded+Size+DownloadCount

with the linux-image-2.6.31.10 source snapshop (from 2.6.31.y tree) at:

http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.31.y.git;a=commit;h=fe21db377c34c1a24a6069713bcf87d44bb89a18

to Xenify the 2.6.31.10 kernel source code. I believe I have successfully patched the source code by running "patch -p1 -s -i *.patch1" for all 75 patches.

60000_add-console-use-vt.patch1
60001_linux-2.6.19-rc1-kexec-move_segment_code-i386.patch1
60002_linux-2.6.19-rc1-kexec-move_segment_code-x86_64.patch1
60003_ipv6-no-autoconf.patch1
60004_pci-guestdev.patch1
60005_pci-reserve.patch1
60006_sfc-driverlink.patch1
60007_sfc-resource-driver.patch1
60008_sfc-driverlink-conditional.patch1
60009_sfc-external-sram.patch1
60010_xen3-auto-xen-arch.patch1
60011_xen3-auto-xen-drivers.patch1
60012_xen3-auto-include-xen-interface.patch1
60013_xen3-auto-xen-kconfig.patch1
60014_xen3-auto-common.patch1
60015_xen3-auto-arch-x86.patch1
60016_xen3-auto-arch-i386.patch1
60017_xen3-auto-arch-x86_64.patch1
60018_xen3-fixup-xen.patch1
60019_sfc-sync-headers.patch1
60020_sfc-endianness.patch1
60021_941-xenbus-transaction-mutex.patch1
60022_945-MSI-disable-check.patch1
60023_958-fbfront-resume.patch1
60024_959-netback-delayed-copy-cleanup.patch1
60025_xen3-fixup-kconfig.patch1
60026_xen3-fixup-common.patch1
60027_xen3-fixup-arch-x86.patch1
60028_xen3-patch-2.6.18.patch1
60029_xen3-patch-2.6.19.patch1
60030_xen3-patch-2.6.20.patch1
60031_xen3-patch-2.6.21.patch1
60032_xen3-patch-2.6.22.patch1
60033_xen3-patch-2.6.23.patch1
60034_xen3-patch-2.6.24.patch1
60035_xen3-patch-2.6.25.patch1
60036_xen3-patch-2.6.26.patch1
60037_xen3-patch-2.6.27.patch1
60038_xen3-patch-2.6.28.patch1
60039_xen3-patch-2.6.29.patch1
60040_xen3-patch-2.6.30.patch1
60041_xen3-patch-2.6.31.patch1
60042_xen3-patch-2.6.31.1.patch1
60043_xen3-patch-2.6.31.1-2.patch1
60044_xen3-patch-2.6.31.3-4.patch1
60045_xen3-patch-2.6.31.5-6.patch1
60046_xen-balloon-max-target.patch1
60047_xen-blkback-cdrom.patch1
60048_xen-blktap-write-barriers.patch1
60049_xen-scsifront-block-timeout-update.patch1
60050_xen-op-packet.patch1
60051_xen-blkfront-cdrom.patch1
60052_xen-sections.patch1
60053_xen-kconfig-compat.patch1
60054_xen-cpufreq-report.patch1
60055_xen-staging-build.patch1
60056_xen-sysdev-suspend.patch1
60057_xen-ipi-per-cpu-irq.patch1
60058_xen-virq-per-cpu-irq.patch1
60059_xen-configurable-guest-devices.patch1
60060_xen-netback-nr-irqs.patch1
60061_xen-netback-notify-multi.patch1
60062_xen-vmalloc_32.patch1
60063_xen-x86-panic-no-reboot.patch1
60064_xen-x86-dcr-fallback.patch1
60065_xen-x86-consistent-nmi.patch1
60066_xen-x86-no-lapic.patch1
60067_xen-x86-pmd-handling.patch1
60068_xen-x86-bigmem.patch1
60053_xen-kconfig-compat.patch1
60054_xen-cpufreq-report.patch1
60055_xen-staging-build.patch1
60056_xen-sysdev-suspend.patch1
60057_xen-ipi-per-cpu-irq.patch1
60058_xen-virq-per-cpu-irq.patch1
60059_xen-configurable-guest-devices.patch1
60060_xen-netback-nr-irqs.patch1
60061_xen-netback-notify-multi.patch1
60062_xen-vmalloc_32.patch1
60063_xen-x86-panic-no-reboot.patch1
60064_xen-x86-dcr-fallback.patch1
60065_xen-x86-consistent-nmi.patch1
60066_xen-x86-no-lapic.patch1
60067_xen-x86-pmd-handling.patch1
60068_xen-x86-bigmem.patch1
60069_xen-x86-machphys-prediction.patch1
60070_xen-x86-exit-mmap.patch1
60071_xen-x86-per-cpu-vcpu-info.patch1
60072_xen-x86_64-pgd-pin.patch1
60073_xen-x86_64-pgd-alloc-order.patch1
60074_xen-x86_64-dump-user-pgt.patch1
60075_xen-x86_64-note-init-p2m.patch1


I compilied & installed the kernel (with x86_64 default config) and edit my bootloader (grub) config and got the same error message on the booting of the Xen hypervisor.

(XEN) elf_xen_note_check: ERROR: Will only load images built for the generic loader or Linux images
(XEN) Panic on CPU0:
(XEN) Could not set up DOM0 guest OS



This leads me to my question. Can someone please tell me how one might compile a custom kernel with the "xenfiy-options".



Thanks!
 
-M


> Date: Mon, 25 Jan 2010 09:58:54 +0100
> From: wg@xxxxxxxxxxxxxx
> To: pasik@xxxxxx
> Subject: Re: [Xen-users] Xen boot errors
> CC: xen-users@xxxxxxxxxxxxxxxxxxx; wg1@xxxxxxx
>
> Pasi Kärkkäinen wrote:
> > On Fri, Jan 22, 2010 at 12:33:23PM +0100, Wolf Grossi wrote:
> >> Hi,
> >>
> >> after compiling the sources xen-3.4.2 and linux-2.6.31.6-pvops, I get
> >> the following error when booting (All line prefixed with (XEN)):
> >>
> >> ---
> >> ...
> >> Brought up 2 CPUs
> >> I/O Virtualisation disabled
> >> mtrr: your CPUs had incorrect fixed MTRR settings
> >> elf_xen_note_check: ERROR: Will only load images built for the generic
> >> loadr or Linux images
> >>
> >
> > So the kernel is in wrong format?
> > How did you build it?
> >
> > -- Pasi
> >
> >> ***
> >> Panic on CPU0
> >> Could nor set up DOM0 gues OS
> >> ***
> >> Manual reset required ...
> >> ---
> >>
> >>
> >> I use the following /boot/grub/menu.lst entry:
> >>
> >> ---
> >> title Xen 3.4 / XenLinux-pvops-2.6.31.6
> >> root (hd0,1)
> >> kernel /boot/xen-3.4.2.gz noreboot console=vga
> >> module /boot/vmlinuz-2.6.31.6-pvops
> >> root=/dev/disk/by-id/ata-WDC_WD1600AABB-56PUA0_WD-WCAP9A969470-part2
> >> resume=/dev/disk/by-id/ata-WDC_WD1600AABB-56PUA0_WD-WCAP9A969470-part1
> >> splash=silent quiet showopts vga=0x31a
> >> module /boot/initrd-2.6.31.6-pvops
> >> ---
> >>
> >>
> >> I assume that the pvops-kernel is incompatibel to xen-3.4.2, what am i
> >> doing wrong?
> >>
> >>
> >> Thanks for hints,
> >> Wolf
> >>
> >> _______________________________________________
> >> Xen-users mailing list
> >> Xen-users@xxxxxxxxxxxxxxxxxxx
> >> http://lists.xensource.com/xen-users
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-users
> >
> Uups; thanks for the hint :) forgot to set the xenfiy-options.
> Wolf
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users


Spread the cheer with Messenger for mobile. Learn more.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>