From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: [PATCH] Prevent xend from starting duplicate domains Date: Wed, 14 Sep 2005 18:15:58 +0100 Message-ID: <3d8eece2050914101511890182@mail.gmail.com> References: <87u0gnrcu4.fsf@us.ibm.com> Reply-To: Christian.Limpach@cl.cam.ac.uk Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <87u0gnrcu4.fsf@us.ibm.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Dan Smith Cc: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 9/14/05, Dan Smith wrote: > IP> That way, even if something has gone wrong and we're left with a > IP> shell domain we'll still be able to restart one with the same > IP> name. (obviously we should only do the rename once) >=20 > In xm-test, this problem starts showing up towards the end of the test > run, and increases in frequency. My guess is that if we were to do > the rename once, it would occasionally allow another domain to be > created, but under high load, would not help that much. How about we rename the domain to its uuid[1][2] and don't display those in xm list unless a verbose option is given? christian [1] -zombie- could work as well... [2] or clear the name and change list to supply the uuid if there's no name= ...