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] HVM Live Migration Troubles - Xen 3.3.1

To: xen-users list <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] HVM Live Migration Troubles - Xen 3.3.1
From: Jonathan Dye <jdye@xxxxxxxxxxxxxxxxxxxx>
Date: Mon, 02 Feb 2009 12:01:02 -0700
Delivery-date: Mon, 02 Feb 2009 11:01:24 -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: Thunderbird (X11/20090105)
I'm having issues with HVM live migration and every xen version I've tried - 3.0.1, 3.1.x, 3.3.0 and 3.3.1. Migrations will fail intermittently with messages like this on the receiving hypervisor:

[2009-02-02 11:35:19 12629] DEBUG (XendCheckpoint:264) [xc_restore]: /usr/lib64/xen/bin/xc_restore 4 4 2 3 1 1 1 [2009-02-02 11:35:19 12629] INFO (XendCheckpoint:403) xc_domain_restore start: p2m_size = 100000 [2009-02-02 11:35:19 12629] INFO (XendCheckpoint:403) Reloading memory pages: 0% [2009-02-02 11:35:23 12629] INFO (XendCheckpoint:403) Received all pages (0 races) [2009-02-02 11:35:23 12629] INFO (XendCheckpoint:403) ERROR Internal error: error setting the HVM context
[2009-02-02 11:35:23 12629] INFO (XendCheckpoint:403) Restore exit with rc=1
[2009-02-02 11:35:23 12629] DEBUG (XendDomainInfo:2402) XendDomainInfo.destroy: domid=4 [2009-02-02 11:35:23 12629] ERROR (XendDomainInfo:2416) XendDomainInfo.destroy: domain destruction failed.
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2409, in destroy
Error: (3, 'No such process')
*xend appears to tear down the failed target vm*
[2009-02-02 11:35:23 12629] ERROR (XendDomain:1145) Restore failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py", line 1143, in domain_restore_fd return XendCheckpoint.restore(self, fd, paused=paused, relocating=relocating) File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 268, in restore
   forkHelper(cmd, fd, handler.handler, True)
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 391, in forkHelper
   raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_restore 4 4 2 3 1 1 1 failed

and on the sending hypervisor:

[2009-02-02 11:57:32 11768] ERROR (XendCheckpoint:157) Save failed on domain xen20 (13) - r
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 135, in save
   write_exact(fd, buf, "could not write device model state")
File "/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line 44, in write_e
   raise XendError(errmsg)
XendError: could not write device model state

what do "could not write device model state" and "error setting the HVM context" indicate?

- jonathan

Xen-users mailing list

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