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-users] problem with migration of some domU's

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] problem with migration of some domU's
From: "Sebastian Reitenbach" <sebastia@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 02 Nov 2007 17:47:08 +0100
Delivery-date: Fri, 02 Nov 2007 09:47:51 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: L00 bugdead prods.
Reply-to: Sebastian Reitenbach <sebastia@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I have two sles10sp1 dom0, and 4 domUs. Two of the domU's can xm 
migrate --live without problem, the other two cannot.
It ends up with the following error message:

ppsnfs101:~ # xm migrate --live FIS_DB ppsnfs101
Error: /usr/lib64/xen/bin/xc_save 24 24 0 0 1 failed
Usage: xm migrate <Domain> <Host>

Migrate a domain to another machine.


-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.

and in /var/log/xend.log I see the following:
[2007-11-02 17:15:51 xend 5502] DEBUG (balloon:146) Balloon: 891920 KiB 
free; need 15360; done.
[2007-11-02 17:15:51 xend 5502] DEBUG (XendCheckpoint:80) 
[xc_save]: /usr/lib64/xen/bin/xc_save 23 11 0 0 1
[2007-11-02 17:15:51 xend.XendDomainInfo 5502] DEBUG (XendDomainInfo:781) 
Storing domain details: 
{'console/ring-ref': '289933', 'console/port': '2', 'name': 'migrating-NFS_SW',
'console/limit': '1048576', 'vm': '/vm/9276a2ea-8276-a249-fe44-8f0e3ebca334',
'domid': '11', 'cpu/0/availability': 'online', 'memory/target': '873472',
'store/ring-ref': '289934', 'store/port': '1'}
[2007-11-02 17:15:51 xend 5502] INFO (XendCheckpoint:247) XXXXXXXX: Bad 
[2007-11-02 17:15:51 xend 5502] INFO (XendCheckpoint:247) ERROR Internal 
error: Couldn't map p2m table
[2007-11-02 17:15:51 xend 5502] INFO (XendCheckpoint:247) Save exit rc=1
[2007-11-02 17:15:51 xend 5502] ERROR (XendCheckpoint:111) Save failed on 
domain NFS_SW (11).
Traceback (most recent call last):
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 
97, in save
    forkHelper(cmd, fd, saveInputHandler, False)
  File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 
235, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 23 11 0 0 1 failed
[2007-11-02 17:15:51 xend.XendDomainInfo 5502] DEBUG (XendDomainInfo:781) 
Storing domain details: 
{'console/ring-ref': '289933', 'console/port': '2', 'name': 'NFS_SW',
'console/limit': '1048576', 'vm': '/vm/9276a2ea-8276-a249-fe44-8f0e3ebca334',
'domid': '11', 'cpu/0/availability': 'online', 'memory/target': '873472',
'store/ring-ref': '289934', 'store/port': '1'}

both dom0 machines have more or less the same configuration, the domU hosts 
too. any idea why two of the domUs can migrate well, but the others not?

kind regards

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] problem with migration of some domU's, Sebastian Reitenbach <=