On 07/17/2015 03:55 PM, nshirokovs...@virtuozzo.com wrote:
NOTE that minimal command to migrate vz domain is like next:
virsh -c vz:///system migrate 200 vz+ssh://shiny0/system -p2p --live
--persistent
--compressed
Difference from v1:
1. Patch is quite different. First patchset implements migration thru managed
migration scheme. This one goes thru p2p scheme. I belive this is a better
approach. Vz migration is done via vz sdk and first patchset uses 5 phased
migration only to get a token from destination on prepare phase which is kind a
misuse. This patch just adds vz specific function to driver interface
to archive the same goal.
What was the problem with previous approach? I think using cookies for
transferring session id is better, than extending remote protocol.
2. Offline migration is supported as there is no more dependency on current
flow of managed migration scheme.
daemon/remote.c | 30 +++++
docs/apibuild.py | 1 +
docs/hvsupport.pl | 1 +
src/driver-hypervisor.h | 4 +
src/libvirt-domain.c | 30 +++++
src/libvirt_internal.h | 2 +
src/libvirt_private.syms | 1 +
src/remote/remote_driver.c | 26 +++++
src/remote/remote_protocol.x | 12 ++-
src/remote_protocol-structs | 1 +
src/vz/vz_driver.c | 256 ++++++++++++++++++++++++++++++++++++++++++
src/vz/vz_sdk.c | 86 ++++++++++++---
src/vz/vz_sdk.h | 6 +
src/vz/vz_utils.h | 4 +-
14 files changed, 444 insertions(+), 16 deletions(-)
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
