Hi, Today I saw the guest OS hung and was no responsive. In the host, I found the guest was running via virsh command. But I couldn't use ssh to connect the guest, and even couldn't ping it. I could use VNC saw the desktop of VNC, but I couldn't move the mouse pointer. In the host, the qemu-kvm process occupied almost 100% CPU. The host was Redhat Enterprise Linux 6 64bit (not SP1). The CPU was Intel quad-core Q9550S. The guest was SUSE Linux Enterprise Server 11 SP1 64bit. The guest had been running for two weeks before it hung. Here are some KVM trace messages: qemu-kvm-32604 [002] 3252503.178924: kvm_exit: reason ext_irq rip 0xffffffff81396eb8 qemu-kvm-32604 [002] 3252503.178924: kvm_entry: vcpu 1 qemu-kvm-32606 [003] 3252503.179049: kvm_exit: reason ext_irq rip 0xffffffff81396ebb qemu-kvm-32606 [003] 3252503.179049: kvm_entry: vcpu 3 <...>-32603 [000] 3252503.179673: kvm_exit: reason ext_irq rip 0xffffffff810578c6 <...>-32603 [000] 3252503.179673: kvm_entry: vcpu 0 <...>-32605 [001] 3252503.179797: kvm_exit: reason ext_irq rip 0xffffffff81396ebb <...>-32605 [001] 3252503.179798: kvm_entry: vcpu 2 qemu-kvm-32604 [002] 3252503.179923: kvm_exit: reason ext_irq rip 0xffffffff81396ebb qemu-kvm-32604 [002] 3252503.179923: kvm_entry: vcpu 1 qemu-kvm-32606 [003] 3252503.180047: kvm_exit: reason ext_irq rip 0xffffffff81396ebb qemu-kvm-32606 [003] 3252503.180048: kvm_entry: vcpu 3 <...>-32603 [000] 3252503.180672: kvm_exit: reason ext_irq rip 0xffffffff8105788c <...>-32603 [000] 3252503.180672: kvm_entry: vcpu 0 <...>-32605 [001] 3252503.180796: kvm_exit: reason ext_irq rip 0xffffffff81396ebb <...>-32605 [001] 3252503.180797: kvm_entry: vcpu 2 qemu-kvm-32604 [002] 3252503.180921: kvm_exit: reason ext_irq rip 0xffffffff81396ebb qemu-kvm-32604 [002] 3252503.180922: kvm_entry: vcpu 1 qemu-kvm-32606 [003] 3252503.181046: kvm_exit: reason ext_irq rip 0xffffffff81396ebb qemu-kvm-32606 [003] 3252503.181047: kvm_entry: vcpu 3 <...>-32603 [000] 3252503.181670: kvm_exit: reason ext_irq rip 0xffffffff81057878 <...>-32603 [000] 3252503.181671: kvm_entry: vcpu 0 <...>-32605 [001] 3252503.181795: kvm_exit: reason ext_irq rip 0xffffffff81396ebb <...>-32605 [001] 3252503.181795: kvm_entry: vcpu 2 qemu-kvm-32604 [002] 3252503.181920: kvm_exit: reason ext_irq rip 0xffffffff81396ebb qemu-kvm-32604 [002] 3252503.181921: kvm_entry: vcpu 1 qemu-kvm-32606 [003] 3252503.182045: kvm_exit: reason ext_irq rip 0xffffffff81396ebb qemu-kvm-32606 [003] 3252503.182046: kvm_entry: vcpu 3 Was it interrupt storm? Or the guest entered some dead loop? Are latest KVM code solve the similar problems? Thanks, Paul -- 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
