Re: [Xen-users] xm migrate headache

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

I've had issues like this, as well, and have never been able to pin down what exactly causes it.  In my experience, the (live) migration works most of the time, but occasionally I get something exactly like what you're seeing here.  Is the hardware (specifically the CPUs) very similar on your hosta and hostb machines?  What kind of shared storage are you using?

-Nick


-----Original Message-----
From: Rainer Sokoll <rainer@xxxxxxxxxx>
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xm migrate headache
Date: Tue, 3 Mar 2009 12:28:38 +0100

Hi,

I am trying to (live-)migrate a paravirtualized machine from hosta to
hostb:

-----8<----
hosta:~ # xm list pvm
Name                                        ID   Mem VCPUs      State Time(s)
pvm                                         64   384     1     -b----    0.5

hostb:~ # xm list pvm
Error: Domain 'pvm' does not exist.

hosta:~ # xm migrate pvm 192.168.0.2
Error: /usr/lib64/xen/bin/xc_save 4 64 0 0 0 failed
Usage: xm migrate <Domain> <Host>

Migrate a domain to another machine.

Options:

-h, --help           Print this help.
-l, --live           Use live migration.
-p=portnum, --port=portnum
                     Use specified port for migration.
-r=MBIT, --resource=MBIT
                     Set level of resource usage for migration.

hosta:~ # xm list pvm
Name                                        ID   Mem VCPUs      State Time(s)
pvm                                         64   384     1     ---s--    0.6

hostb:~ # xm list pvm
Name                                        ID   Mem VCPUs      State Time(s)
pvm                                         61   384     1     --p---    0.0
-----8<----

As you can see, the machine (called "pvm" got migrated, but on hosta
the status is still "s", which should not happen, as far as I see.
Both VMs are in logical volumes, and the volumes are connected via drbd
in primary/primary mode.
The hosts are OpenSUse 11.0 with xen 3.2.
Since I am a newbie to Xen, I might have missed something - but what?
Any hint is appreciated,

Rainer

---

This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users