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 host.
It is the same 'completed' from te POV of internal migration API calls..
From the end users POV though it is the same as migration active, since we've not finished migration.
I can't tell from the code, but the virDomainJobInfo should still report that migration is active, and not completed. Is it doing so ? Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|