Ming Chen
2010-Jan-20 16:07 UTC
[Xen-users] VM migration problem: server 1 to server 2 is ok, but does not work if from server 2 to server 1
Hello,
I have a problem of migration between two servers.
Both servers use xen 3.3.1 which is compiled on fc7. I used one single VM.
If I create VM on server 1, and migrate it from server 1 to server 2 is OK,
and it is also OK to migrate it back to server 1. However, if I create the
VM on server 2 and migrate it to server 1, the VM always disappears. When it
fails, the log message on server 1 is as follows:
[2010-01-20 10:39:18 12474] DEBUG (XendCheckpoint:264) [xc_restore]:
/usr/lib/xen/bin/xc_restore 34 29 1 2 0 0 0
[2010-01-20 10:39:18 12474] INFO (XendCheckpoint:403) xc_domain_restore
start: p2m_size = 10800
[2010-01-20 10:39:18 12474] INFO (XendCheckpoint:403) Reloading memory
pages: 0%
[2010-01-20 10:39:44 12474] INFO (XendCheckpoint:403) Received all pages (0
races)
[2010-01-20 10:39:44 12474] INFO (XendCheckpoint:403) ERROR Internal error:
Failed to pin batch of 47 page tables
[2010-01-20 10:39:44 12474] INFO (XendCheckpoint:403) Restore exit with rc=1
[2010-01-20 10:39:44 12474] DEBUG (XendDomainInfo:2402)
XendDomainInfo.destroy: domid=29
[2010-01-20 10:39:44 12474] ERROR (XendDomainInfo:2416)
XendDomainInfo.destroy: domain destruction failed.
Traceback (most recent call last):
File "//usr/lib/python/xen/xend/XendDomainInfo.py", line 2409, in
destroy
xc.domain_pause(self.domid)
Error: (3, ''No such process'')
[2010-01-20 10:39:44 12474] DEBUG (XendDomainInfo:1944) No device model
[2010-01-20 10:39:44 12474] DEBUG (XendDomainInfo:1946) Releasing devices
[2010-01-20 10:39:44 12474] DEBUG (XendDomainInfo:1959) Removing vif/0
[2010-01-20 10:39:44 12474] DEBUG (XendDomainInfo:910)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-01-20 10:39:45 12474] DEBUG (XendDomainInfo:1959) Removing vbd/51713
[2010-01-20 10:39:45 12474] DEBUG (XendDomainInfo:910)
XendDomainInfo.destroyDevice: deviceClass = tap, device = vbd/51713
[2010-01-20 10:39:45 12474] DEBUG (XendDomainInfo:1959) Removing vbd/51714
[2010-01-20 10:39:45 12474] DEBUG (XendDomainInfo:910)
XendDomainInfo.destroyDevice: deviceClass = tap, device = vbd/51714
[2010-01-20 10:39:45 12474] DEBUG (XendDomainInfo:1959) Removing console/0
[2010-01-20 10:39:45 12474] DEBUG (XendDomainInfo:910)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-01-20 10:39:46 12474] ERROR (XendDomain:1145) Restore failed
Traceback (most recent call last):
File "//usr/lib/python/xen/xend/XendDomain.py", line 1143, in
domain_restore_fd
return XendCheckpoint.restore(self, fd, paused=paused,
relocating=relocating)
File "//usr/lib/python/xen/xend/XendCheckpoint.py", line 268, in
restore
forkHelper(cmd, fd, handler.handler, True)
File "//usr/lib/python/xen/xend/XendCheckpoint.py", line 391, in
forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib/xen/bin/xc_restore 34 29 1 2 0 0 0 failed
Could you pls give me some hints to solve this problem? Thanks a lot.
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Keith Coleman
2010-Jan-20 16:26 UTC
Re: [Xen-users] VM migration problem: server 1 to server 2 is ok, but does not work if from server 2 to server 1
On Wed, Jan 20, 2010 at 11:07 AM, Ming Chen <kingming0811@gmail.com> wrote:> Both servers use xen 3.3.1 which is compiled on fc7. I used one single VM. > If I create VM on server 1, and migrate it from server 1 to server 2 is OK, > and it is also OK to migrate it back to server 1. However, if I create the > VM on server 2 and migrate it to server 1, the VM always disappears. When it > fails, the log message on server 1 is as follows:Sounds like server 2 cpu may have features that server 1 cpu lacks. In your domU config set the cpuid to match server 1 cpu. Keith Coleman _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-Jan-20 22:08 UTC
Re: [Xen-users] VM migration problem: server 1 to server 2 is ok, but does not work if from server 2 to server 1
On Wed, Jan 20, 2010 at 11:26 PM, Keith Coleman <list.keith@scaltro.com> wrote:> Sounds like server 2 cpu may have features that server 1 cpu lacks. In > your domU config set the cpuid to match server 1 cpu.Is there a ready-to-use cpuid examples that we can use for this purpose? James Harper posted an example that he used for AMD <-> Intel migration on a different thread, but it also disable sse feature. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2010-Jan-21 04:07 UTC
Re: [Xen-users] VM migration problem: server 1 to server 2 is ok, but does not work if from server 2 to server 1
On Thu, Jan 21, 2010 at 10:16 AM, Ming Chen <kingming0811@gmail.com> wrote:> what do you mean by "ready-to-use cpuid example that..."?Something that you can copy-and-paste directly to your domU config. Like this: http://old.nabble.com/amd-<->-intel-migration-and-silverlight-td27196401.html -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users