This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] Migration Issues

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Migration Issues
From: Dan Goscomb <dang@xxxxxxxxxxxxx>
Date: Wed, 13 Aug 2008 11:25:05 +0100
Delivery-date: Wed, 13 Aug 2008 03:19:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Hi All

I have run in to an issue when migrating VMs.

If the VM is created by the API, migration simply does not work. If it
is created by "xm create filename" then I can use the API to migrate
just fine.

The error I get when attempting to migrate is this:

[2008-08-13 11:11:26 3576] DEBUG (XendCheckpoint:91)
[xc_save]: /usr/lib64/xen/bin/xc_save 26 4 0 0 5
[2008-08-13 11:11:26 3576] INFO (XendCheckpoint:373) Saving memory
pages: iter 1   0%ERROR Internal error: Error when writing to state file
(5) (errno 104)

I can post a more complete log entry if required.

Does anyone have any ideas?



xen-api mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-API] Migration Issues, Dan Goscomb <=