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

Re: [Xen-API] Fail to migrate vm with snapshot twice

  • To: blackstn10 <blackstn10@xxxxxxxxx>, xen-api <xen-api@xxxxxxxxxxxxxxxxxxx>
  • From: Bob Ball <bob.ball@xxxxxxxxxx>
  • Date: Fri, 31 May 2013 10:53:49 +0000
  • Accept-language: en-GB, en-US
  • Deferred-delivery: Fri, 31 May 2013 10:53:00 +0000
  • Delivery-date: Fri, 31 May 2013 10:54:01 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>
  • Thread-index: AQHOXabNuHWIoEBzo0WV1Wvmvobc5pkfHK+w
  • Thread-topic: [Xen-API] Fail to migrate vm with snapshot twice


This is a bug that we’re aiming to fix for the next version of XenServer.

You can use the API to work around this by populating the VDI map directly – an example is attached (note, you cannot work around this by specifying the VDI map on the command line).



From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxx] On Behalf Of ??
Sent: 31 May 2013 03:25
To: xen-api
Subject: [Xen-API] Fail to migrate vm with snapshot twice


Hello Experts,

When I migrate a vm with snapshot from HostA to HostB, it is successful. But, When I want to migrate it back, it failed and prompted

"No SR specified in VDI map for VDI 28d47598-e3b0-403a-a99d-147a1fceab0d ".

Yes, with vm-list params=parent, I can see the parent points to its snapshot, it will be ok once I delete the parent (its snapshot). But why can the live migration be successful at first time?

Is it by design or a bug? Do you have any workaround except deleting snapshot?

I will appreciate your help.




Attachment: vm_migrate.py
Description: vm_migrate.py

Xen-api mailing list



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