On Wed, 2006-09-27 at 14:26 -0500, Anthony Liguori wrote:
> So is there any better way to block on destroy here ? In the
clustering
> scenario its neccessary to 'fence' a misbehaving domain on a host before
> bringing it back online. From what you're saying it would appear to be
> neccessary to poll for completion of the destroy op before trying to
> restart the domain.
>
The 3.0.4 API ought to have proper async/sync semantics. Polling is an
option.
Ok, that's fine -- I'll poll until the domain's gone before returning;
on the newer API, it won't break anything.
Keep in mind, this problem isn't limited to destroy. It's
true for
reboot, shutdown, etc. There are very few ops that are actually
synchronous in Xen today.
/me wants sync reboot... :)
*wishes upon a star*
-- Lon