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] [PATCH][XEND] Don't call destroy() on exception instart(

On Sat, Feb 17, 2007 at 05:36:52PM -0500, Puthiyaparambil, Aravindh wrote:

> The problem we were running into was that if we try to start a domain
> for which there is not enough memory we get an "Error: an integer is
> required" message. Please see the attached xend log. On debugging
> further I saw that the destroy() in start() was happening with Null
> domain id because it was already destroyed in create(). 

This has been fixed in xen-unstable

changeset:   13949:82f66bc01da2cb14062c0651a63dbf7286cfd1e7
user:        Wim Colgate <wim@xxxxxxxxxxxxx>
date:        Wed Feb 14 12:18:32 2007 -0800
files:       tools/python/xen/xend/XendDomainInfo.py
description:
Protect self.domid from being empty

Cheers,

Ewan.

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

<Prev in Thread] Current Thread [Next in Thread>