|
|
|
|
|
|
|
|
|
|
xen-users
RE: [Xen-users] Xen boot errors
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@xxxxxxxxxxxxxxx To: xen-users@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxx > To: mike.viau@xxxxxxxxxxxxxxx > CC: xen-users@xxxxxxxxxxxxxxxxxxx > > On Sun, Jan 31, 2010 at 11:04 PM, Mike Viau <viaum@xxxxxxxxxxxxxxx> 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=y
No 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@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-users
Tell the whole story with photos, right from your Messenger window. Learn how!
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|