From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: Re: [PATCH] Make xend reject duplicates and rename zombies Date: Fri, 16 Sep 2005 10:45:14 -0400 Message-ID: <1126881914.3233.2.camel@pluto.linsolutions.com> References: <87br2uz5yj.fsf@us.ibm.com> <4329C366.2070006@us.ibm.com> <87mzmew38u.fsf@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <87mzmew38u.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: Dan Smith Cc: Xen Tools Developers , Xen Developers List-Id: xen-devel@lists.xenproject.org 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. Regards, Ted