Re: [libvirt] [PATCH v2 04/15] qemu: Handle postcopy-active migration state

2016-01-22 Thread Daniel P. Berrange
On Thu, Jan 21, 2016 at 11:20:49AM +0100, Jiri Denemark wrote: > Migration enters "postcopy-active" state after QEMU switches to > post-copy and pauses guest CPUs. From libvirt's point of view this state > is similar to "completed" because we need to transfer guest execution to > the destination

Re: [libvirt] [PATCH v2 04/15] qemu: Handle postcopy-active migration state

2016-01-22 Thread Jiri Denemark
On Fri, Jan 22, 2016 at 15:15:03 +, Daniel P. Berrange wrote: > On Thu, Jan 21, 2016 at 11:20:49AM +0100, Jiri Denemark wrote: > > Migration enters "postcopy-active" state after QEMU switches to > > post-copy and pauses guest CPUs. From libvirt's point of view this state > > is similar to

[libvirt] [PATCH v2 04/15] qemu: Handle postcopy-active migration state

2016-01-21 Thread Jiri Denemark
Migration enters "postcopy-active" state after QEMU switches to post-copy and pauses guest CPUs. From libvirt's point of view this state is similar to "completed" because we need to transfer guest execution to the destination host. Signed-off-by: Jiri Denemark --- Notes: