WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Zombie VMs cannot be destroyed

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Zombie VMs cannot be destroyed
From: Michael Froh <mike@xxxxxxxxxxx>
Date: Fri, 1 Dec 2006 12:57:03 -0500
Delivery-date: Fri, 01 Dec 2006 09:57:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
This sounds like a B rate horror movie. Has anyone else seen Zombie VMs?

I had a number of VMs running and used the following script to destroy them:

for vm in `xm list | awk '{print $1}' | grep -v Name | grep -v Domain-0`; do xm destroy $vm; done

This destroyed all of the para-virtualized domains running (4 of them) but turned all the HVM VMs into Zombies as shown here:

[root@vm0 ~]# xm list
Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 5074 4 r----- 4912.8 Zombie-dsl0 25 256 1 -b---d 552.1 Zombie-dsl1 26 256 1 -b---d 552.2 Zombie-dsl2 27 256 1 -b---d 550.0 Zombie-dsl3 28 256 1 -b---d 554.5 Zombie-knoppix0 17 256 1 -b---d 4459.9 Zombie-knoppix1 18 256 1 -----d 4425.9 Zombie-knoppix2 19 256 1 -b---d 4530.9 Zombie-knoppix3 20 256 1 -b---d 4493.7


Subsequent attempts to destroy the VMs using "xm destroy 25" or "xm destroy Zombie-dsl0" don't do anything.

It's curious that the VMs are shown as booting and being destroyed (- b----d).

The para-virtualized VMs were named centos[0-3] so it might be a timing issue where only 4 destroys were properly handled and the para- virtualized VMs happened to be the first 4 domains in xm list.

I will play around a bit to see if I can recreate consistently and if there options to really destroy the domains. This is not an issue for me since my VM environment is a lab, but in production this might be very problematic.

Mike.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users