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

Re: [Xen-users] xm shutdown & xm destroy won't get rid of VM

To: Eric Brown <yogieric@xxxxxxx>
Subject: Re: [Xen-users] xm shutdown & xm destroy won't get rid of VM
From: "Michael J. Baysek" <mjbaysek@xxxxxxxxxx>
Date: Wed, 14 Sep 2005 14:21:20 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Sep 2005 18:19:10 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <51611D7C-9436-4D44-93C3-C770446ED643@xxxxxxx>
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>
References: <51611D7C-9436-4D44-93C3-C770446ED643@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.4 (X11/20050908)
I too have this problem:

   # xm list

   Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
   Domain-0           0       91    0      1   r----   6753.9
   lick              11        0    0      1   ----c      0.3
   lick              11        0    0      1   ----c      0.3
   lmon               4      255    0      1   -b---  34997.5
   lots               5      191    0      1   -b---   5210.1
   loud               6      511    0      1   -----   6138.4

In my case this happened after I ran out of memory in the lick domU (no swap was setup yet). The oom-killer hosed the domU. Even the console. So I tried to destroy and start another. It was then that I did an xm list, to my horror.



Eric Brown wrote:
I tried "xm shutdown" and then "xm destroy", my listing still shows:

$ xm list
Name Id Mem(MB) CPU State Time(s) Console
Domain-0 0 156 0 r---- 766.2
asgtest0 9 0 3 -b--- 1.2 9609
debianarchive 15 255 1 -b--- 6.4 9615

What should i do to get rid of asgtest0?

Thanks!


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


--

Michael J. Baysek Systems Analyst
Carnegie Mellon University, Auton Lab
http://www.autonlab.org
mjbaysek@xxxxxxxxxx


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