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] Xen Migration Trouble

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen Migration Trouble
From: Joe <jnirsch@xxxxxxxxxxx>
Date: Wed, 22 Dec 2010 10:03:53 -0600
Delivery-date: Wed, 22 Dec 2010 08:05:14 -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
I am trying to perform offline and live migration with xen.

I have two identical hosts, host1 and host2, which are both RHEL5.  I have an NFS server on host1.  The NFS location is not the root of the file system.  The domU I am trying to migrate is FC14 fully virtualized.  The host environments are set up exactly the same.  I have edited the xend-config.sxp to ensure that relocation is possible.

Xen information:
# virsh version
Compiled against library: libvir 0.6.3
Using library: libvir 0.6.3
Using API: Xen 3.0.1
Running hypervisor: Xen 3.1.0

To perform these migrations, I am using using the virt-manager GUI.  I have tried CLI and had the same success.
Initially, when I did both migration techniques, I got the following error message, where 'test' was the domU I was trying to migrate.

Unable to migrate guest:
 Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/migrate.py", line 449, in _async_migrate
    vm.migrate(dstconn, migrate_uri, rate, live, secure)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1388, in migrate
    self.vm.migrate(destconn.vmm, flags, newname, interface, rate)
  File "/usr/lib/python2.4/site-packages/libvirt.py", line 378, in migrate
    if ret is None:raise libvirtError('virDomainMigrate() failed', dom=self)
libvirtError: POST operation failed: xend_post: error from xen daemon: No such domain test

Doing offline migration with CLI, I get:
# virsh migrate test xen+ssh://domain.com
error: failed to get domain 'test'
error: Domain not found: xenUnifiedDomainLookupByName

In the 'test' config file, I include nfs_root, root, and nfs_server.

Now, I still get that error with offline migration.  When I am performing live migration, it freezes on a screen saying migration in progress.  When it freezes, the target host has the vm appear but lists it as no state (from virsh list).  On the source host, the target still exists and is switching between running and shutoff (virsh list lists it as idle).  I believe what is currently happening with the live migration is just a fluke.

As far as I can tell, I have set up all the components right.  The firewall or selinux is not the issue.  User permissions are not an issue and have been addressed.  To sum up this long rant, here are a few questions.  What is xend_post?  What does "xen daemon: No such domain" mean?  I think it might be searching the wrong location, but cannot tell where that is.  Should the vm config files be on each host in /etc/xen or in the NFS location?  Where can I enable more complete logging for xen and libvirt?
Currently, unless the vm is running on one host, I do not see it in the GUI unless I created it using xm create to start a vm.  I find this odd but do not know how to correct it.

Thanks for any help.
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>