From: David Hopwood Subject: Re: [PATCH] Prevent xend from starting duplicate domains Date: Wed, 14 Sep 2005 00:20:55 +0100 Message-ID: <43275ED7.2090709@blueyonder.co.uk> References: <87d5ncsksl.fsf@us.ibm.com> Reply-To: david.nospam.hopwood@blueyonder.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87d5ncsksl.fsf@us.ibm.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Dan Smith wrote: > The attached patch puts a simple check in domain_create() which > prevents starting a domain if there is already one of the same name in > the domain list. > > This fixes the problem of getting the following error message from xm > while creating a domain soon after destroying one with the same name: > > xen.xend.XendProtocol.XendError: (3, 'No such process') > > Signed-off-by: Dan Smith Surely there's a race condition here? The hypervisor op that creates a domain has to fail if it would result in two domains with the same name; this can't be reliably enforced by a separate check in the Python tools. -- David Hopwood