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
***
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@lists.xensource.com
http://lists.xensource.com/xen-users
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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@lists.xensource.com >> http://lists.xensource.com/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >Uups; thanks for the hint :) forgot to set the xenfiy-options. Wolf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@magro-soft.com > To: pasik@iki.fi > Subject: Re: [Xen-users] Xen boot errors > CC: xen-users@lists.xensource.com; wg1@gmx.net > > 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@lists.xensource.com > >> http://lists.xensource.com/xen-users > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > Uups; thanks for the hint :) forgot to set the xenfiy-options. > Wolf > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_________________________________________________________________ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Sun, Jan 31, 2010 at 11:04 PM, Mike Viau <viaum@sheridanc.on.ca> wrote:> I compilied & installed the kernel (with x86_64 default config)which 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 OSDid you enable Xen-specific options? For example, Opensuse 11.2''s kernel-xen has these options enabled: CONFIG_X86_64_XEN=y CONFIG_X86_XEN_MCE=y CONFIG_XEN_PCIDEV_FRONTEND=y CONFIG_NETXEN_NIC=m CONFIG_TCG_XEN=m CONFIG_XEN=y CONFIG_XEN_INTERFACE_VERSION=0x00030207 CONFIG_XEN_PRIVILEGED_GUEST=y CONFIG_XEN_PRIVCMD=y CONFIG_XEN_XENBUS_DEV=y CONFIG_XEN_NETDEV_ACCEL_SFC_UTIL=m CONFIG_XEN_BACKEND=m CONFIG_XEN_BLKDEV_BACKEND=m CONFIG_XEN_BLKDEV_TAP=m CONFIG_XEN_BLKDEV_TAP2=m CONFIG_XEN_BLKBACK_PAGEMAP=m CONFIG_XEN_NETDEV_BACKEND=m CONFIG_XEN_NETDEV_TX_SHIFT=10 CONFIG_XEN_NETDEV_ACCEL_SFC_BACKEND=m CONFIG_XEN_NETDEV_LOOPBACK=m CONFIG_XEN_PCIDEV_BACKEND=m CONFIG_XEN_PCIDEV_BACKEND_VPCI=y CONFIG_XEN_TPMDEV_BACKEND=m CONFIG_XEN_SCSI_BACKEND=m CONFIG_XEN_USB_BACKEND=m CONFIG_XEN_BLKDEV_FRONTEND=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_NETDEV_ACCEL_SFC_FRONTEND=m CONFIG_XEN_SCSI_FRONTEND=m CONFIG_XEN_USB_FRONTEND=m CONFIG_XEN_GRANT_DEV=m CONFIG_XEN_FRAMEBUFFER=y CONFIG_XEN_KEYBOARD=y CONFIG_XEN_SYSFS=y CONFIG_XEN_NR_GUEST_DEVICES=2048 CONFIG_XEN_COMPAT_030300_AND_LATER=y CONFIG_XEN_COMPAT=0x030300 CONFIG_XEN_VCPU_INFO_PLACEMENT=y CONFIG_XEN_SMPBOOT=y CONFIG_XEN_DEVMEM=y CONFIG_XEN_BALLOON=y CONFIG_XEN_SCRUB_PAGES=y -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Date: Sun, 31 Jan 2010 23:15:39 +0700 > Subject: Re: [Xen-users] Xen boot errors > From: fajar@fajar.net > To: mike.viau@sheridanc.on.ca > CC: xen-users@lists.xensource.com > > On Sun, Jan 31, 2010 at 11:04 PM, Mike Viau <viaum@sheridanc.on.ca> wrote: > > I compilied & installed the kernel (with x86_64 default config) > > which default config?In the tar.gz source snapshot I downloaded there was a default x86_64 config at ./arch/x86/configs/x86_64_defconfig> > > 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 > > Did you enable Xen-specific options? For example, Opensuse 11.2''s > kernel-xen has these options enabled: > > CONFIG_X86_64_XEN=y > CONFIG_X86_XEN_MCE=y > CONFIG_XEN_PCIDEV_FRONTEND=y > CONFIG_NETXEN_NIC=m > CONFIG_TCG_XEN=m > CONFIG_XEN=y > CONFIG_XEN_INTERFACE_VERSION=0x00030207 > CONFIG_XEN_PRIVILEGED_GUEST=y > CONFIG_XEN_PRIVCMD=y > CONFIG_XEN_XENBUS_DEV=y > CONFIG_XEN_NETDEV_ACCEL_SFC_UTIL=m > CONFIG_XEN_BACKEND=m > CONFIG_XEN_BLKDEV_BACKEND=m > CONFIG_XEN_BLKDEV_TAP=m > CONFIG_XEN_BLKDEV_TAP2=m > CONFIG_XEN_BLKBACK_PAGEMAP=m > CONFIG_XEN_NETDEV_BACKEND=m > CONFIG_XEN_NETDEV_TX_SHIFT=10 > CONFIG_XEN_NETDEV_ACCEL_SFC_BACKEND=m > CONFIG_XEN_NETDEV_LOOPBACK=m > CONFIG_XEN_PCIDEV_BACKEND=m > CONFIG_XEN_PCIDEV_BACKEND_VPCI=y > CONFIG_XEN_TPMDEV_BACKEND=m > CONFIG_XEN_SCSI_BACKEND=m > CONFIG_XEN_USB_BACKEND=m > CONFIG_XEN_BLKDEV_FRONTEND=m > CONFIG_XEN_NETDEV_FRONTEND=m > CONFIG_XEN_NETDEV_ACCEL_SFC_FRONTEND=m > CONFIG_XEN_SCSI_FRONTEND=m > CONFIG_XEN_USB_FRONTEND=m > CONFIG_XEN_GRANT_DEV=m > CONFIG_XEN_FRAMEBUFFER=y > CONFIG_XEN_KEYBOARD=y > CONFIG_XEN_SYSFS=y > CONFIG_XEN_NR_GUEST_DEVICES=2048 > CONFIG_XEN_COMPAT_030300_AND_LATER=y > CONFIG_XEN_COMPAT=0x030300 > CONFIG_XEN_VCPU_INFO_PLACEMENT=y > CONFIG_XEN_SMPBOOT=y > CONFIG_XEN_DEVMEM=y > CONFIG_XEN_BALLOON=y > CONFIG_XEN_SCRUB_PAGES=yNo I did not put these lines in the config file, I did not see any CONFIG_XEN options in the default config so I thought that the xen-patchs might have enabled these options by default. I will added these line to the current .config and recompile & test...> > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_________________________________________________________________ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Firstly thanks for the help thus far :) With the addition of the Xen-specific options referenced (below) by Opensuse 11.2''s kernel-xen additional options in the .config, more dialog occurs during the kernel compilation now. I am fairly sure that the ''debug'' releated options (relating to the network and pci backends) are not required to operate a stable XEN system. I was hoping to confirm that those options would just make error reporting more detailed (verbose) and not change the way XEN itself will operate? -Will all the XEN features work without the debugging support compilied into the kernel? -Also would someone like to weigh in as to how performance might be impacted by leaving these options enabled? Any other XEN kernel configuration tips would be much apprecaited. Although I have not mentioned previously my system is x86_64 Debian Lenny. Hardware is an Intel Core i7 860, 8GB RAM, Intel VT-d and VT-d I/O enabled at the bios level. Please correct me if I am incorrect with my assumption, thanks. -M From: mike.viau@sheridanc.on.ca To: xen-users@lists.xensource.com Subject: RE: [Xen-users] Xen boot errors Date: Sun, 31 Jan 2010 11:35:06 -0500> Date: Sun, 31 Jan 2010 23:15:39 +0700 > Subject: Re: [Xen-users] Xen boot errors > From: fajar@fajar.net > To: mike.viau@sheridanc.on.ca > CC: xen-users@lists.xensource.com > > On Sun, Jan 31, 2010 at 11:04 PM, Mike Viau <viaum@sheridanc.on.ca> wrote: > > I compilied & installed the kernel (with x86_64 default config) > > which default config?In the tar.gz source snapshot I downloaded there was a default x86_64 config at ./arch/x86/configs/x86_64_defconfig> > > 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 > > Did you enable Xen-specific options? For example, Opensuse 11.2''s > kernel-xen has these options enabled: > > CONFIG_X86_64_XEN=y > CONFIG_X86_XEN_MCE=y > CONFIG_XEN_PCIDEV_FRONTEND=y > CONFIG_NETXEN_NIC=m > CONFIG_TCG_XEN=m > CONFIG_XEN=y > CONFIG_XEN_INTERFACE_VERSION=0x00030207 > CONFIG_XEN_PRIVILEGED_GUEST=y > CONFIG_XEN_PRIVCMD=y > CONFIG_XEN_XENBUS_DEV=y > CONFIG_XEN_NETDEV_ACCEL_SFC_UTIL=m > CONFIG_XEN_BACKEND=m > CONFIG_XEN_BLKDEV_BACKEND=m > CONFIG_XEN_BLKDEV_TAP=m > CONFIG_XEN_BLKDEV_TAP2=m > CONFIG_XEN_BLKBACK_PAGEMAP=m > CONFIG_XEN_NETDEV_BACKEND=m > CONFIG_XEN_NETDEV_TX_SHIFT=10 > CONFIG_XEN_NETDEV_ACCEL_SFC_BACKEND=m > CONFIG_XEN_NETDEV_LOOPBACK=m > CONFIG_XEN_PCIDEV_BACKEND=m > CONFIG_XEN_PCIDEV_BACKEND_VPCI=y > CONFIG_XEN_TPMDEV_BACKEND=m > CONFIG_XEN_SCSI_BACKEND=m > CONFIG_XEN_USB_BACKEND=m > CONFIG_XEN_BLKDEV_FRONTEND=m > CONFIG_XEN_NETDEV_FRONTEND=m > CONFIG_XEN_NETDEV_ACCEL_SFC_FRONTEND=m > CONFIG_XEN_SCSI_FRONTEND=m > CONFIG_XEN_USB_FRONTEND=m > CONFIG_XEN_GRANT_DEV=m > CONFIG_XEN_FRAMEBUFFER=y > CONFIG_XEN_KEYBOARD=y > CONFIG_XEN_SYSFS=y > CONFIG_XEN_NR_GUEST_DEVICES=2048 > CONFIG_XEN_COMPAT_030300_AND_LATER=y > CONFIG_XEN_COMPAT=0x030300 > CONFIG_XEN_VCPU_INFO_PLACEMENT=y > CONFIG_XEN_SMPBOOT=y > CONFIG_XEN_DEVMEM=y > CONFIG_XEN_BALLOON=y > CONFIG_XEN_SCRUB_PAGES=yNo I did not put these lines in the config file, I did not see any CONFIG_XEN options in the default config so I thought that the xen-patchs might have enabled these options by default. I will added these line to the current .config and recompile & test...> > -- > Fajar > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_________________________________________________________________ Reinvent how you stay in touch with the new Windows Live Messenger. http://go.microsoft.com/?linkid=9706116 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
HI, i got the same error. (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 My xen was working, i just change the hardware to a new one, and it stop working. Any help? -- View this message in context: http://xen.1045712.n5.nabble.com/Xen-boot-errors-tp2610637p2651285.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Do you using Xen for AMD64? What was Xen version, CPU before upgrade and after? В Втр, 24/08/2010 в 07:19 -0700, lopb пишет:> HI, > i got the same error. > (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 > > My xen was working, i just change the hardware to a new one, and it stop > working. > Any help?_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users