Re: [libvirt] [PATCH 02/16] Add public APIs for post-copy migration

On Tue, Jan 19, 2016 at 10:50:07AM +0100, Jiri Denemark wrote: The VIR_MIGRATE_POSTCOPY_AFTER_PRECOPY flag is something that feels a little wrong to me. It is not something QEMU directly supports, but rather it is implementing a very specific usage policy in libvirt. I can see it could be considered convenient, but we have always tried to stay away from implementing specific policies in libvirt since inevitably they will not serve everyone else. Since we have ability to report to apps how many iterations we've done, and apps generally monitor migration progress anyway (even virsh does), it doesn't seem like it is hard for apps to make the decision to switch to postcopy and avoid this policy in libvirt 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 :|