On Sat, Jan 09, 2010 at 03:45:15PM +0200, Pasi Kärkkäinen wrote:
On Fri, Jan 08, 2010 at 10:08:25AM -0500, Tait Clarridge wrote:
Also please try running "xm console" for the guest and see what it does and where it crashes..
Make sure your domU kernel has these kernel cmdline options: "console=hvc0 earlyprintk=xen"
Do these options work with the F11 guest kernel (2.6.30) as well?
Also, what hardware was this? There has been some fixes to the incorrect cpuid masking causing guest kernel crashes on new cpus, and some of those are fixed in upcoming EL 5.5 Xen.
Are these going to be in 5.4?
I'm running 2.6.18-164.11.1.el5xen and the fedora kernels for F11 and F12 are not very stable for me. Dom0 is a Centos 5.4 2.6.18-164.9.1.el5xen kernel.
These fedora kernels seem to lockup (processes get stuck in D state) whenever put under any load:
kernel-2.6.30.10-105.fc11.x86_64 kernel-2.6.31.6-166.fc12.x86_64 kernel-2.6.31.9-174.fc12.x86_64
Yes, I tried a fedora 11 kernel on a fedora 12 system. This is the most stable for me.
Here are some bugzilla entries (one posted by me) that point to this problem:
kernel 2.6.31 processes lock up in D state https://bugzilla.redhat.com/show_bug.cgi?id=550724
FC12 2.6.31.9-174.fc12.x86_64 hangs under heavy disk I/O https://bugzilla.redhat.com/show_bug.cgi?id=551552
Any help appreciated.