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: Thu, 22 Nov 2007 16:07:55 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 22 Nov 2007 08:08:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071122160455.GA4798@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: AcgtIddWFbRhypkVEdybPwAX8io7RQ==
Thread-topic: [Xen-devel] 15142:78389dbb08bb and domain state
User-agent: Microsoft-Entourage/11.3.6.070618
>> I have now, and it works for me. My domid gets zapped in cleanupDomain(). It
>> gets called twice from destroyDomain(), once via
>> XendDomain.instance.remove_domain() and the other as a direct invocation.
> 
> I don't see any code to zap domid there. BTW the call from
> remove_domain() shouldn't happen as the _stateGet will be
> DOM_STATE_HALTED at that point.

Looks like xen-unstable c/s 15587 needs backporting to 3.1 branch.

 -- Keir



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