Red Hat Bugzilla – Bug 464642
VMs go into Zombie state when xend is restarted
Last modified: 2009-12-14 16:11:30 EST
Description of problem:
If a VM is running when xend is restarted, and the VM is then shutdown, the VM will go to Zombie state.
Version-Release number of selected component (if applicable):
- Red Hat Enterprise Linux Server release 5.2 (Tikanga)
Steps to Reproduce:
1. Install a new RH5.2 (64-bit) host with Xen
2. Use virt-manager to create a new VM
3. Start the VM from virt-manager
4. Run "/sbin/service xend restart"
5. Shutdown the VM from virt-manager
The virt-manager GUI will display the VM constantly switching between the on and off state. The "virsh list" command will show the VM in Zombie state.
The VM should shutdown successfully without entering into a Zombie state.
I need more information as I was not able to reproduce this bug. What is the type of virtual machine you are creating? Is it a fully virtualized machine or a paravirtualized one? What operating system is running inside the VM?
Could you, please, also share exact version number of xen package?
In addition, VM's configuration file (/etc/xen/VM_name) and messages written to /var/log/xen/xend.log and /var/log/xen/xend-debug.log after you tell virt-manager to shutdown the VM would be really helpful. Please, send these as attachments to this bug.
Here are the information you need, I do this on behalf of Will.
Type of VM: Fully virtualized machine
Guest OS: Red Hat Enterprise Linux AS release 4 (Nahant Update 6) 64bits
Version number of Xen package:
$ rpm -qa | grep xen
Output of "virsh list" when this problem occurs:
$ virsh list
Id Name State
0 Domain-0 running
2 Zombie-rhel46_full_virt64 no state
I have checked there are no any messages written to /var/log/xen/xend-debug.log when this problem occurs, I will attach VM's configuration file and /var/log/xen/xend.log later.
Created attachment 323287 [details]
Xend log file
Created attachment 323288 [details]
VM config file
In the attached Xend.log, you see I started a VM at 20:33:20, restarted Xend service at 20:36:02, and shutdown the VM at 20:37:57, then this problem occured.
This bug is a duplicate of an older bug. I'm closing this one...
*** This bug has been marked as a duplicate of bug 280611 ***