Comment 6 for bug 791850
Revision history for this message
| Stefan Bader (smb) wrote Re: oneiric cluster compute instances do not boot | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
The good news is, that this can be reproduced on my CentOS test system. Bad news, there really does not seem to be much more hints than we already got. Dom0 console only shows one message about "Bad HVM op 9", but that happens between grub and os boot and has no impact. And vlapic reports a few write accesses to read-only registers 0x20 and 0x30, but those are not a problem either.
I am able to make a successful boot with vcpu=1 and a modified 64bit oneiric-server installation that force-loads all of the xen drivers (its not verified yet, but I think it is mainly the blkfront driver I need). This also shows the dom0 messages above but boots sucessfully. However, it seems there is something weird with the ide controller emulation as well. While boot and grub in HVM recognize the disk, the Oneiric kernel does not seem to find it (boot only succeeds because it finds the xvd device).
When booting with more than one CPU, the boot stops in a tight loop, right after printing out
Brought up x CPUs
Total of x processors activated (y BogoMIPS).
Neither xm dmesg nor xm log contain more useful data. Increasing the debugging level within the guest also has no more to say. Feels like something completing the SMP/CPU init gets stuck. I will try to get a crash-dump of the system and see whether that has a bit more to say. Though it is sometimes hard to find the right combo of util versions to look into that.