On 03.01.2013 00:35, Alexandre Kouznetsov wrote:
Hello.
I have made more tests and got a successful migration using Storage
XenMotion. It happened only after I have removed the destination XCP
host from the actual pool, and moved it to a new one.
It seems like "destination-sr-uuid=" option is recognized correctly
only when a "remote-master=" and other connection details are
specified. The neighbor thread
http://lists.xen.org/archives/html/xen-api/2012-12/msg00162.html was
helpful. Yes, they fly between pools like magic. The option
"live=<false|true>" does not make any visible difference: a Debian VM
with default 8GB hdd and no activity pauses for around 2 seconds and
my shell connection to it is not lost, in both cases, "live=false" and
"live=true".
live migration performs set of iterations over VM memory (you can see
details in /tmp/xenguest.log on source host), live=false performs 'pause
and copy' mode. They are almost the same for idle machines, but make a
huge difference for heavy-loaded servers, which change lot of memory
every second. (F.e. heavy loaded erlang application with work heap about
10GiB: it live migration performs all 32 iterations and still forced to
make 'pause and copy' at final round with large memory delta).
Still not clear how to migrate VM's in the following cases:
- When VM is not online (vm-migrate insists it should be "running").
- When origin and destination hosts are within the same pool.
offline croos-pool migration is not supported, AFAIK. Sad, yep.
For in-pool migration there is xe vdi-pool-migration command.
_______________________________________________
Xen-api mailing list
Xen-api@lists.xen.org
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
