Re: [libvirt] [PATCH] Explicitly set VM state to paused after migration completes

2011-06-02 Thread Eric Blake
On 06/02/2011 09:42 AM, Daniel P. Berrange wrote: > In v3 migration, once migration is completed, the VM needs > to be left in a paused state until after Finish3 has been > executed on the target. Only then will the VM be killed > off. When using non-JSON QEMU monitor though, we don't > receive any

[libvirt] [PATCH] Explicitly set VM state to paused after migration completes

2011-06-02 Thread Daniel P. Berrange
In v3 migration, once migration is completed, the VM needs to be left in a paused state until after Finish3 has been executed on the target. Only then will the VM be killed off. When using non-JSON QEMU monitor though, we don't receive any 'STOP' event from QEMU, so we need to manually set our stat