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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] 15142:78389dbb08bb and domain state
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Tue, 13 Nov 2007 20:02:57 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 13 Nov 2007 12:03:44 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C35FAF62.185CA%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <20071113193719.GD27927@xxxxxxxxxxxxxxxxxxxxxxx> <C35FAF62.185CA%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Nov 13, 2007 at 07:45:38PM +0000, Keir Fraser 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.

I presume that there's something slightly different due to being Solaris
dom0/domU. I would presume it's our bug except that we don't have
changes to this area of the code, and by inspection I can't see why
anything would be different. One notable point is that this domU is
still not using hvcopy for its networking.

I still haven't figured out the exact path: destroyDomain() is called,
but something goes wrong later on

regards
john

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