Bugs item #2796640, was opened at 2009-05-25 21:00
Message generated for change (Comment added) made by bobmanners
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2796640&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bob Manners (bobmanners)
Assigned to: Nobody/Anonymous (nobody)
Summary: KVM Regression from 2.6.28-11 to 2.6.30-rc5
Initial Comment:
Changing from the Ubuntu 09.04 stock kernel 2.6.28-11 to the current 'alpha'
kernel in the Ubuntu development repository for 'Karmic' 2.6.30-rc5, some (but
not all) of my KVM guests stop booting.
I have the following guest OSs installed as KVM virtual machines: Ubuntu 09.04,
FreeBSD 7.1, Minix 3, OpenSolaris 08.11, Windows XP and Windows 7RC
Under 2.6.28-11 these all boot and run OK. With kernel 2.6.30-rc5, Ubuntu,
FreeBSD and Minix boot and run OK, but OpenSolaris 08.11, Windows XP and
Windows 7RC fail to boot. They appear to freeze very early in the boot
process, after the boot loader is done and the OS kernel itself starts loading.
There are no strange messages in the host system logs that I am aware of.
When the guest OS freezes, it pins one of my CPUs at 100% utilization (I have
KVM set to only give one CPU to the guest).
This looks like a regression under 2.6.30-rc5. It is possible that it is
caused by a Ubuntu patch, and I have filed a bug in Launchpad, but I suspect
that this is an upstream problem, and so I am reporting it here also.
Please let me know what I can do to assist in debugging this.
----------------------------------------------------------------------
>Comment By: Bob Manners (bobmanners)
Date: 2009-05-27 20:22
Message:
In response to kelu6's question, actually I am running 32 bit host / 32 bit
guest. My CPU is Intel Core Duo (not Core2 Duo) which is a 32 bit CPU:
b...@gecko2:~$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2400 @ 1.83GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc
arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm
bogomips : 3658.94
clflush size : 64
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 14
model name : Genuine Intel(R) CPU T2400 @ 1.83GHz
stepping : 8
cpu MHz : 1000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc
arch_perfmon bts pni monitor vmx est tm2 xtpr pdcm
bogomips : 3658.93
clflush size : 64
power management:
----------------------------------------------------------------------
Comment By: Kenni (kelu6)
Date: 2009-05-27 17:00
Message:
Do you run with a 32bit host on a 64bit CPU? It sounds like it could be the
same issue I had when changing from kernel 2.6.28.x to 2.6.29:
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/31206/focus=31206
If it's the same issue, then adding the argument '-cpu qemu32' or '-cpu
qemu64,-nx' to the qemu-command, should fix the issue. Also, Avi Kivity
created some patches which fixes the issue in KVM-86.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2796640&group_id=180599
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
