Hi all,
I've observed a guest hang after putting a little stress testing on
it. It basically hangs in ~10 secs after running several trinity
instances inside a KVM tools guest.
The hang is easy to describe and reproduce:
1. No userspace exits observed
2. kvm_stat looks as follows (with all other fields at 0):
kvm_entry 3631869 11819
kvm_apic_accept_irq 1078688 11819
kvm_exit 3631844 11819
I've bisected it down to:
9b72d3b07dd99ac8ab2b84de5004a295af460536 is the first bad commit
commit 9b72d3b07dd99ac8ab2b84de5004a295af460536
Author: Gleb Natapov <gleb@xxxxxxxxxx>
Date: Mon Apr 30 14:45:49 2012 +0300
KVM guest: make kvm_para_available() check hypervisor bit reading cpuid leaf
This cpuid range does not exist on real HW and Intel spec says that
"Information returned for highest basic information leaf" will be
returned. Not very well defined.
Signed-off-by: Gleb Natapov <gleb@xxxxxxxxxx>
Signed-off-by: Avi Kivity <avi@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
