Re: [Xen-devel] [PATCH] Fix xm save timeout with paused domains

[Keir Fraser <keir@xxxxxxxxxxxxx>]

On 8/5/07 18:14, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

>> I think xend is the obvious place to implement this type of synchronisation.
> 
> I think I agree. It would be easy if we were to just loop until the
> domain gets unpaused but that's not really quite the correct fix, since
> we ideally want 'xm save' to fail cleanly if the domain is paused (I
> vaguely remember seeing a patch for this go past?).
> 
>> The only question is how hard it will be to add in.
> 
> Maybe a xenstore entry for the domain which is written just after the
> .unpause() (the absence of this would also prevent xm pause, xm destroy,
> perhaps)

Yes, some kind of state field in xenstore to aid synchronisation wouldn't be
a bad idea. It could be set to various states depending on whether a domain
is starting, xm-paused, being saved, etc. and operation can sync on that
field by waiting for it to switch to 'running'.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel