Hi all,
I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze
Xen4.0 and now have problems with starting the Dom0 kernel. I always get
the error message: Kernel panic not syncing: the kernel parameter noapic
is incompatible with xen.
My grub.cfg is:
menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN
4.0-i386'' --cl$
insmod part_msdos
insmod ext2
set root=''(hd0,msdos1)''
search --no-floppy --fs-uuid --set
743d959f-5054-441f-b68d-32d9970bb8ab
echo ''Loading Linux 2.6.32-5-xen-686 ...''
multiboot /boot/xen-4.0-i386.gz noreboot placeholder
module /boot/vmlinuz-2.6.32-5-xen-686 placeholder
root=UUID=743d959f-5$
echo ''Loading initial ramdisk ...''
module /boot/initrd.img-2.6.32-5-xen-686
I already tried the boot parameters: noapic nolapic acpi=off in the line
mulitboot .... and module /boot/vmlinuz line.
What can I do to get the machine running?
On Sat, 2013-02-16 at 11:33 +0000, Martin Lang wrote:> Hi all, > > I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze > Xen4.0 and now have problems with starting the Dom0 kernel. I always get > the error message: Kernel panic not syncing: the kernel parameter noapic > is incompatible with xen.Is this the literal message? I''ve grepped the kernel and hypervisor source and cannot find it anywhere. Please can you collect the actual logs from the system. http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Host_console_logs What sort of processor does this system have?> My grub.cfg is: > > menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN > 4.0-i386'' --cl$ > insmod part_msdos > insmod ext2 > set root=''(hd0,msdos1)'' > search --no-floppy --fs-uuid --set > 743d959f-5054-441f-b68d-32d9970bb8ab > echo ''Loading Linux 2.6.32-5-xen-686 ...'' > multiboot /boot/xen-4.0-i386.gz noreboot placeholder > module /boot/vmlinuz-2.6.32-5-xen-686 placeholder > root=UUID=743d959f-5$ > echo ''Loading initial ramdisk ...'' > module /boot/initrd.img-2.6.32-5-xen-686 > > > I already tried the boot parameters: noapic nolapic acpi=off in the line > mulitboot .... and module /boot/vmlinuz line.The message is complaining about the presence of "noapic" not its absence, so I hope you also tried without. Ian.
It is an Athlon XP system running on an Elitegroup K7S5A board. Adding "lapic" as boot option did the job. Thank you On 02/18/2013 11:29 AM, Ian Campbell wrote:> On Sat, 2013-02-16 at 11:33 +0000, Martin Lang wrote: >> Hi all, >> >> I just upgraded my Debian/Etch with Xen3.3 machine to Debian/Squeeze >> Xen4.0 and now have problems with starting the Dom0 kernel. I always get >> the error message: Kernel panic not syncing: the kernel parameter noapic >> is incompatible with xen. > Is this the literal message? I''ve grepped the kernel and hypervisor > source and cannot find it anywhere. Please can you collect the actual > logs from the system. > http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen#Host_console_logs > > What sort of processor does this system have? > >> My grub.cfg is: >> >> menuentry ''Debian GNU/Linux, with Linux 2.6.32-5-xen-686 and XEN >> 4.0-i386'' --cl$ >> insmod part_msdos >> insmod ext2 >> set root=''(hd0,msdos1)'' >> search --no-floppy --fs-uuid --set >> 743d959f-5054-441f-b68d-32d9970bb8ab >> echo ''Loading Linux 2.6.32-5-xen-686 ...'' >> multiboot /boot/xen-4.0-i386.gz noreboot placeholder >> module /boot/vmlinuz-2.6.32-5-xen-686 placeholder >> root=UUID=743d959f-5$ >> echo ''Loading initial ramdisk ...'' >> module /boot/initrd.img-2.6.32-5-xen-686 >> >> >> I already tried the boot parameters: noapic nolapic acpi=off in the line >> mulitboot .... and module /boot/vmlinuz line. > The message is complaining about the presence of "noapic" not its > absence, so I hope you also tried without. > > Ian. > >