[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] XCP 1.6 Storage XenMotion cannot move virtual disks between local SRs

  • To: xen-api@xxxxxxxxxxxxx
  • From: Alexandre Kouznetsov <alk@xxxxxxxxxx>
  • Date: Thu, 03 Jan 2013 18:32:56 -0600
  • Delivery-date: Fri, 04 Jan 2013 00:33:09 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

El 02/01/13 21:19, George Shuklin escribió:
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).
Thanks for reference, I'll take this into account. Right now I'm still in proof-of-concept stage.

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.
That's what I thought vdi-pool-migration was for, judging by it's name!
(migrate vdi between pools)

But no, vdi-pool-migration does not migrates the VM within the same pool:

[root@xcp48 ~]# xe vdi-pool-migrate \
  uuid=e2021c93-95f4-47d7-9018-b2221d9de51b \
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Storage_interface.Internal_error("Storage_interface.Sr_not_attached(\"590510e6-074e-47a2-bc76-04e4fb83148f\")")

e2021c93-95f4-47d7-9018-b2221d9de51b is the uuid of the VDI, attached to the VM I'm trying to migrate from one host to another within the same pool.

590510e6-074e-47a2-bc76-04e4fb83148f is the Local Storage of the destination host.

I guess this should work to migrate the VDI between storages, while the host system has access to both SRs. Seems like a indirect way to do the move machines from one local storage to another:
1. Move storage from local storage to a shared one.
2. Move the VM from one host to another, while the storage is shared
3. Move the storage from shared to local on the destination host.

(would be great if someone can confirm)

Alexandre Kouznetsov

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.