From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Smith Subject: Re: [PATCH][RESEND] Fix stale-state issue with 'xm dom{id, name}' Date: Tue, 04 Oct 2005 10:35:04 -0700 Message-ID: <871x31yylz.fsf@us.ibm.com> References: <87psqqh4ww.fsf@us.ibm.com> <20051004073630.GC4104@linford.intra> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <20051004073630.GC4104@linford.intra> (Ewan Mellor's message of "Tue, 4 Oct 2005 08:36:30 +0100") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ewan Mellor Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org EM> I would be grateful if you could re-run xm-test and let me know EM> how it looks. There might still be some bugs to iron out, but EM> hopefully you will find that the behaviour under xm-test is much EM> improved. After two runs of xm-test, I'm not seeing failures on either of the tests that poke specific stale-state issues. That's good news :) I'll see about writing some more tests targeted at stale-state detection, just to make sure ;) -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com