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

[Dan Smith <danms@us.ibm.com>]

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

Sounds about right :)

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.

Absolutely.  I will run it today and post my findings.  It would be
great if others "out there" could do the same to help verify that the
problem is better or fixed.  Since threads are involved, many tests
across varying platforms will be more convincing :)

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

That is excellent news.  The latest version generates an XML file of
results that it automatically submits to us for review.  It would be
great if you could use that as your data source for merging the data
into your own test infrastructure.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@us.ibm.com