Re: [libvirt] [PATCH 2/5] qemu: Avoid dangling migration-in job on shutoff domains

2012-03-21 Thread Jiri Denemark
On Tue, Mar 20, 2012 at 15:56:39 -0600, Eric Blake wrote: On 03/19/2012 10:18 AM, Jiri Denemark wrote: Destination daemon should not rely on the client or source daemon (depending on the type of migration) to call Finish when migration fails, because the client may crash before it can do

Re: [libvirt] [PATCH 2/5] qemu: Avoid dangling migration-in job on shutoff domains

2012-03-21 Thread Eric Blake
On 03/21/2012 02:41 AM, Jiri Denemark wrote: On Tue, Mar 20, 2012 at 15:56:39 -0600, Eric Blake wrote: On 03/19/2012 10:18 AM, Jiri Denemark wrote: Destination daemon should not rely on the client or source daemon (depending on the type of migration) to call Finish when migration fails,

Re: [libvirt] [PATCH 2/5] qemu: Avoid dangling migration-in job on shutoff domains

2012-03-20 Thread Eric Blake
On 03/19/2012 10:18 AM, Jiri Denemark wrote: Destination daemon should not rely on the client or source daemon (depending on the type of migration) to call Finish when migration fails, because the client may crash before it can do so. The domain prepared for incoming migration is set to be

[libvirt] [PATCH 2/5] qemu: Avoid dangling migration-in job on shutoff domains

2012-03-19 Thread Jiri Denemark
Destination daemon should not rely on the client or source daemon (depending on the type of migration) to call Finish when migration fails, because the client may crash before it can do so. The domain prepared for incoming migration is set to be destroyed (and migration job cleaned up) when