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

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



Does an xm save / xm restore on the 64-bit machine work correctly?

If you try and xm save on the 64-bit machine and then an xm restore of that 
image on the 32-bit machine, does that work?

Are both machines running the latest unstable, or a recent release?  If you 
got them from hg, a changeset ID would be helpful (i.e. hg tip) to make it 
clear how recent your version is.

Cheers,
Mark

On Tuesday 29 April 2008, sanjay kushwaha 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



-- 
Push Me Pull You - Distributed SCM tool (http://www.cl.cam.ac.uk/~maw48/pmpu/)

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