WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] xm migrate headache

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] xm migrate headache
From: Rainer Sokoll <rainer@xxxxxxxxxx>
Date: Tue, 3 Mar 2009 12:28:38 +0100
Delivery-date: Tue, 03 Mar 2009 03:29:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
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

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

<Prev in Thread] Current Thread [Next in Thread>