On 08/09/11 - 08:51:43AM, Chris Lalancette wrote:
However, it seems like between the time that oz determined that the
didn't shut down, and when it actually went to do the kill, the domain shut
down of its own accord. This could just mean that the guest was slow in
This is a bug in Oz. If the destroy fails, but the guest has successfully gone
away, we should just ignore the error and succeed the operation. I'll take a
look at fixing this today.
I pushed a commit (ec18386d78940cb72552) to the Oz git repository that
should take care of this problem.
I've also attached the patch to this email. It should apply to version 0.5.0
of Oz with some fuzz.
If you get a chance, could you please give it a test and let me know if it
works for you?