Description of problem:
I'm having a problem where my virtual machines hang. The console and network
are unresponsive. It has happens to several different guests but they are ALL
running an update to date instance of 32-bit rhel5.5.
Version-Release number of selected component (if applicable):
I've seen this happen with both rhel5.5, rhel6 and f13 hypervisors.
The vm will hang within a few hours. Virt-manager shows the vm is still running with the cpu usage bouncing between 49-50%.
Steps to Reproduce:
1. virsh start guest
The vm console and network become unresponsive.
vm should stay up.
What information can I provide to help debug this? I am running rhel6 on
my laptop and f13 on a server in my lab. I've seen the problem on both
systems. I am only seeing the 32-bit rhel guests hang. I've never seen a windows or 64-bit rhel vm hang.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
We're not familiar with such a bug.
Please state the qemu-kvm, kernel, seaBios versions.
I just updated today against http://download.devel.redhat.com/nightly/latest-RHEL6.0 and still have the problem.
Can you retest with .43 host kernel, we have a fix there for smp guests
What's guest kernel version?
Guest kernel is:
Linux server.example.com 2.6.18-194.8.1.el5 #1 SMP Wed Jun 23 10:58:38 EDT 2010 i686 i686 i386 GNU/Linux
I just updated my host to 2.6.32-43 - so far, so good.
Let me know if you need anything else.
I have not seen a hang since upgrading to 2.6.32-43 almost 24 hours ago so this is good news.
My config is now:
[root@fugue ~]# uname -a
Linux fugue.example.com 2.6.32-43.el6.x86_64 #1 SMP Tue Jul 6 13:50:10 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
[root@fugue ~]# rpm -q qemu-kvm
[root@fugue ~]# rpm -q seabios
Will you folks take care of pushing this upstream or should I file a Fedora bug?
The problem still exists on my F13 system (184.108.40.206-124) and fails quickly.
Closing as dup of the previous bug.
The fix for the kernel hasn't yet been submitted, so Fedora doesn't yet have it. Feel free to open a bug with the Fedora kernel so that it's backported with priority.
*** This bug has been marked as a duplicate of bug 609082 ***