Re: [PATCH][RESEND] Fix stale-state issue with 'xm dom{id, name}'

[Ewan Mellor <ewan@xensource.com>]

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!

Hi Dan,

I made a big change yesterday to XendDomain to make it thread-safe.  As far as
I can tell, most of the problems that you've been seeing were caused by
watches firing and modifying XendDomain internal state at the same time as
each other and as the xm commands.  This meant that it was pretty easy to
confuse Xend into thinking that domains existed when they didn't and vice
versa.

I would be grateful if you could re-run xm-test and let me know how it looks.
There might still be some bugs to iron out, but hopefully you will find that
the behaviour under xm-test is much improved.

We've got someone working right now on integrating xm-test with our automated
test/build infrastructure here, so I expect to be able to run all your tests
myself soon, but I would also appreciate your feedback on this.

Thanks,

Ewan.