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-devel

Re: [Xen-devel] 15142:78389dbb08bb and domain state

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] 15142:78389dbb08bb and domain state
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 13 Nov 2007 19:45:38 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Nov 2007 11:46:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071113193719.GD27927@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgmLcPGAjZ985IhEdytjwAX8io7RQ==
Thread-topic: [Xen-devel] 15142:78389dbb08bb and domain state
User-agent: Microsoft-Entourage/11.3.6.070618
On 13/11/07 19:37, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

>> I remember it being both, but it might have been - unfortunately I can
>> only create screwed domains at the moment (!).
> 
> It's both:
> 
> bash-3.00# xm list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0  6718     4     r-----    119.7
> sxc13                                           1024     1                52.0
> sxc15                                        1   900     1     ------     37.8
> 
> The domain is not listed in the 'q' output at this point. Is there another way
> to fix the bug that regressed this behaviour?

Is it explicable how this happens for you but not for me? I haven't been
seeing domains hang around in 'cm list' after domain destruction at all.

 -- Keir



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