[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Re: Migrating a 32 bit DomU from a 64 bit machine to a 32 bit machine?


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "sanjay kushwaha" <sanjay.kushwaha@xxxxxxxxx>
  • Date: Mon, 28 Apr 2008 21:27:18 -0400
  • Delivery-date: Mon, 28 Apr 2008 18:27:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=m03D1uNZ0eiiR5MZIZ0F3h+2PondUo0Opfoqmt24ZaCEsa5yUacnyrEdaN466id9FeRCIdqjXQMMDW1LF0Qd30OK7Q+DtlmF0oPbRScuK042mNCpPBliWTFp6vtYVbiIRi6Kqo1trKI4I0Jah+XV11e+fDJ/2tQ52Kp8t9PzkjE=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On the destination machine's /var/log/xen/xend.log it says

[2008-04-29 01:13:07 4237] DEBUG (XendCheckpoint:255) restore:shadow=0x0, _static_max=0x8000000, _static_min=0x0,
[2008-04-29 01:13:07 4237] DEBUG (balloon:133) Balloon: 244632 KiB free; need 131072; done.
[2008-04-29 01:13:07 4237] DEBUG (XendCheckpoint:272) [xc_restore]: /usr/lib/xen/bin/xc_restore 23 8 1 2 0 0 0
[2008-04-29 01:13:07 4237] INFO (XendCheckpoint:411) xc_domain_restore start: p2m_size = 8800
[2008-04-29 01:13:07 4237] INFO (XendCheckpoint:411) Reloading memory pages:   0%
[2008-04-29 01:13:07 4237] INFO (XendCheckpoint:411) ERROR Internal error: Max batch size exceeded. Giving up.
[2008-04-29 01:13:07 4237] INFO (XendCheckpoint:411) Restore exit with rc=1
[2008-04-29 01:13:07 4237] DEBUG (XendDomainInfo:2395) XendDomainInfo.destroy: domid=8
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:2412) XendDomainInfo.destroyDomain(8)
[2008-04-29 01:13:08 4237] ERROR (XendDomainInfo:2424) XendDomainInfo.destroy: xc.domain_destroy failed.
Traceback (most recent call last):
  File "/root/ksanjay/hp/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 2419, in destroyDomain
Error: (3, 'No such process')
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:1873) No device model
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:1875) Releasing devices
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:1881) Removing vif/0
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:872) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:1881) Removing vbd/2056
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:872) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2056
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:1881) Removing console/0
[2008-04-29 01:13:08 4237] DEBUG (XendDomainInfo:872) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2008-04-29 01:13:08 4237] ERROR (XendDomain:1138) Restore failed
Traceback (most recent call last):
  File "/root/ksanjay/hp/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendDomain.py", line 1136, in domain_restore_fd
  File "/root/ksanjay/hp/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendCheckpoint.py", line 276, in restore
  File "/root/ksanjay/hp/xen-unstable.hg/dist/install/usr/lib/python/xen/xend/XendCheckpoint.py", line 399, in forkHelper
XendError: /usr/lib/xen/bin/xc_restore 23 8 1 2 0 0 0 failed

The error seems to be ERROR Internal error: Max batch size exceeded. Giving up.

On Mon, Apr 28, 2008 at 9:12 PM, sanjay kushwaha <sanjay.kushwaha@xxxxxxxxx> wrote:
Hi Folks,
I am trying to live migrate a 32 bit linux DomU from a 64-bit machine running 64-bit dom0 to a 32 bit machine running 32-bit dom0.
Apparently the live migration fails with the following error.

[root@vt3 xen]# xm migrate --live 1 143.215.138.73
Error: /usr/lib64/xen/bin/xc_save 23 1 0 0 1 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.
-n=nodenum, --node=nodenum
                     Use specified NUMA node on target.
-r=MBIT, --resource=MBIT
                     Set level of resource usage for migration.

[root@vt3 xen]#

The /var/log/xend.log say the following

[2008-04-28 20:49:00 6254] DEBUG (XendCheckpoint:105) [xc_save]: /usr/lib64/xen/bin/xc_save 23 1 0 0 1
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) domctl ret 0
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) domctl ret 0
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) domctl ret 0
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) domctl ret 0
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) Had 0 unexplained entries in p2m table
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) domctl ret 0
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) domctl ret 0
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) Saving memory pages: iter 1   0%domctl ret 0
[2008-04-28 20:49:00 6254] INFO (XendCheckpoint:411) domctl ret 0
[2008-04-28 20:49:24 6254] INFO (XendCheckpoint:411) ERROR Internal error: Error when writing to state file (4a) (errno 104)
[2008-04-28 20:49:24 6254] INFO (XendCheckpoint:411) domctl ret 0
[2008-04-28 20:49:24 6254] INFO (XendCheckpoint:411) Save exit rc=1
[2008-04-28 20:49:24 6254] ERROR (XendCheckpoint:158) Save failed on domain DebianVM (1).
Traceback (most recent call last):
  File "//usr/lib64/python/xen/xend/XendCheckpoint.py", line 126, in save
    forkHelper(cmd, fd, saveInputHandler, False)
  File "//usr/lib64/python/xen/xend/XendCheckpoint.py", line 399, in forkHelper
    raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_save 23 1 0 0 1 failed

Could someone please let me know if it is possible to migrate VMs between 64 bit and 32 bit machines? I am using the latest xen tree.

Thanks,
Sanjay

--
----------------------
PhD Candidate, Georgia Tech
http://www.cc.gatech.edu/~ksanjay/



--
----------------------
PhD Candidate, Georgia Tech
http://www.cc.gatech.edu/~ksanjay/
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.