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


Re: [Xen-users] Xen Migration Trouble

To: Joe <jnirsch@xxxxxxxxxxx>
Subject: Re: [Xen-users] Xen Migration Trouble
From: Todd Deshane <todd.deshane@xxxxxxx>
Date: Wed, 22 Dec 2010 11:14:06 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 22 Dec 2010 08:15:42 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=47Ml0IYHM8wCckxzNNdpP7mcCY3nWQA4m+XwGS46Jec=; b=IwdAE3IJe8qF9uazlxzcu2ENVNzF5KlMoCaCicNR5dLSAtwv6rMhR8Mld8U7EXnszb /h+5riv4vQXYokS6J5Oe0lb7bhKDU2AA2+igxA+kpkw6IMe8S+8kD7YLOnqFrIbV4kvI hQzAmcNZzWMdpZ8khaeY5ULffRDtVuaULJUGE=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; b=c3oQeGqXcaGlp/GKKGC//yU4UOWBX/Yfof6qfqE6fRm0n6z5Q8BnRMwvt3ArfBktxj ohnJl343H87D+qDmV6Qs9icVVxCBNQ4F8r4SKGT5favPA2G2WEwMKM2U8gKQNy0PLYFF mphFh+PG0+XRCnOd/muX3JN+xz8I4l9uaQCtg=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTimfmdCOL9FRUUcsgLLkaSYTr_-jK9zHDqnyE6tR@xxxxxxxxxxxxxx>
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>
References: <AANLkTimfmdCOL9FRUUcsgLLkaSYTr_-jK9zHDqnyE6tR@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, Dec 22, 2010 at 11:03 AM, Joe <jnirsch@xxxxxxxxxxx> wrote:
> 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.

I would recommend using the xm commands directly to try to narrow down
the problem.

For example you can do xm save, copy the file and do xm restore on the
other host to see if that work.

Hope that helps.


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>