From: Ewan Mellor Subject: Re: [PATCH][RESEND] Fix stale-state issue with 'xm dom{id, name}' Date: Sat, 1 Oct 2005 11:54:17 +0100 Message-ID: <20051001105416.GB11498@uk.xensource.com> References: <87psqqh4ww.fsf@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <87psqqh4ww.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: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Sep 30, 2005 at 09:54:55AM -0700, Dan Smith wrote: > > This is a resend of my stale state fix, which is yet unapplied. If > there are issues, please let me know. > > Note that this fixes the issue poked by xm-test, as shown in the > following snippet of David's latest FC3pae.report: > > > FAIL: 01_shutdown_basic_pos > > I had to run an xm list to update xend state! Sorry Dan, I didn't mean to sit on this patch. The thing is, it solves the problem by making sure that SrvDomain can cope with stale domains being returned by XendDomain, but I _really_ don't want XendDomain to be returning stale information in the first place. I've been trying to decide how easy it would be to fix the underlying problem -- if it's going to take a long time, then I'll apply your patch as a workaround, but I hope to solve the problem more definitively. If I haven't fixed it by Monday, I'll apply your patch. Thanks, Ewan.