On Mon, Apr 14, 2014 at 05:50:07PM -0600, Chris Friesen wrote: > Hi, > > I've been digging through the libvirt code and something that struck > me was that it appears that when using qemu libvirt will migrate the > instance with autostart disabled, then sit on the source host > periodically polling for migration completion, then once the host > detects that migration is completed it will tell the destination to > start up the VM. > > Why don't we let the destination autostart the VM once migration is > complete? Libvirt has to have synchronization point on the target machine, so that we can acquire any disk leases associated with the VM before the CPUs are started. 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 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list