live migrate VM from xen-3.4(i686 )to xen-4.1(x86_64)
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
live migrate VM from xen-3.4(i686 )to xen-4.1(x86_64)
Hi folks,
Is there any way to live migrate VMs hosted on hypervisor with 32-bit DOM0 running xen-3.4 to 64-bit DOM0 running xen-4.1? I tried to do this, but it failed:
Code:
[root@ovs2 ]# xm migrate -l testvm01 xen4-server
Error: /usr/lib/xen/bin/xc_save 37 10 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.
-s, --ssl Use ssl connection for migration.
When a VM is started, it has a specific configuration, that belong in the process, which really pertains to the features available in the hypervisor. When you live migrate, this metadata gets replicated on the destination hypervisor. So if you live migrate to a newer hypervisor that supports it, you gain nothing because the VM remains in the old state with none of the improvements. And if the new hypervisor removed or changed some of the old features, live migration will not even be possible. Same reason you can't live migrate between Intel and AMD CPUs really.
So, while I am not a Xen expert, I suspect you will definitely be better off starting the VMs cold on the new host.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.