On Thu, Apr 21, 2011 at 09:33:42AM -0400, Stefan Berger wrote:
On 04/21/2011 07:43 AM, Daniel P. Berrange wrote:
>On Thu, Apr 21, 2011 at 07:37:30AM -0400, Stefan Berger wrote:
>>
>>and simply doesn't start the VM. After this function is called all
>>sockets are closed and the communication with the source host is
>>cut. I don't think it allows for fall-back at this point.
>Sure it does. As long as the destination QEMU CPUs have not been
>started, you can fallback by simply killing the dest QEMU and
>restarting CPUs on the src QEMU.
>
FWIW, I did a test and disabled the starting of the CPUs on the
destination side and
did a sleep() instead. Before the sleep() was over the Qemu on the
source side had already disappeared.
That is with the old v2 migration protocol. In the new v3 protocol
that has changed to work as I described.
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 :|