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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Make xend reject duplicates and rename zombies

To: Dan Smith <danms@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Make xend reject duplicates and rename zombies
From: Ted Kaczmarek <tedkaz@xxxxxxxxx>
Date: Fri, 16 Sep 2005 10:45:14 -0400
Cc: Xen Tools Developers <xen-tools@xxxxxxxxxxxxxxxxxxx>, Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 16 Sep 2005 14:42:59 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=WuyBiSH8XoO1LL9xGADwi885UB0uJ5rubcsRObaXDF8cF830rlKesaW1V6P1eJ+6fY9zbNQmyHclQsgUoRXm12CvtGhbOE1a3AC0nNRj+zXBf/+ql45Qr4PV+Pds267hAJQhUZL0jq8cvadOxq+8PzS/94SPhpHzMUioTAfBNKE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <87mzmew38u.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: <87br2uz5yj.fsf@xxxxxxxxxx> <4329C366.2070006@xxxxxxxxxx> <87mzmew38u.fsf@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2005-09-15 at 12:16 -0700, Dan Smith wrote:
> AL> This patch renames the domain name which prevents a name class but
> AL> does not solve the general problem.
> I agree.  This is why in my original patch, I simply had the create
> routine reject attempts to create domains with duplicate names.
> Further, I will point out that what I meant by my comment attached to
> this patch was not that it solved the general problem, but that it
> seemed to make the problem not get in the way of some of my existing
> tests :)
> AL> I think the right solution is to make xm destroy not return until
> AL> the domain has actually gone away and add a flag to xm destroy to
> AL> return immediately if that behavior is ever desired.
> Yep, I think that's a much better solution.  So, I think my original
> patch should still be applied: xend should do its own checking for
> duplicates, so that we don't rely on whatever tool is asking us to do
> so.
Has this been applied yet?

I still have this exact issue with change set 6884.


Xen-devel mailing list