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] Prevent xend from starting duplicate domains

To: Dan Smith <danms@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Prevent xend from starting duplicate domains
From: Christian Limpach <christian.limpach@xxxxxxxxx>
Date: Wed, 14 Sep 2005 18:15:58 +0100
Cc: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Sep 2005 17:13:52 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Jqjgovg05ThfRuEjH45vS8eJ7io9/S424a3Hw+5/FiCZvUpsB7EIAkQOUbJKA0WuWeggvwiWkcj7dOpooX3knHHPhBPIqwT6DQyarXe2LHau99vkSUPFoElVEsOphsF2js6aegclBJM0boPBKj8+wQGgrrg6Of8CFmg3pDhZURc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <87u0gnrcu4.fsf@xxxxxxxxxx>
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: <A95E2296287EAD4EB592B5DEEFCE0E9D32DDF4@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <87u0gnrcu4.fsf@xxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 9/14/05, Dan Smith <danms@xxxxxxxxxx> 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)
> 
> 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] <name>-zombie-<domid> could work as well...
[2] or clear the name and change list to supply the uuid if there's no name...

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