RE: [libvirt] Virsh migrate --live fails

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

 



Hi Chris Lalancette,

 Thanks for responding to my e-mail.

 I tried the virsh migrate --live command and checked for the libvirtd service. It is still running.

[root@RHEL53Xen1 ~]# xm list
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Copy_RHELVM3                               3      511     1 -b----    134.7
Domain-0                                   0     1507     4 r----- 221921.5
[root@RHEL53Xen1 ~]# service libvirtd status
libvirtd (pid 3871) is running...
[root@RHEL53Xen1 ~]# virsh migrate --live Copy_RHELVM3 xen+ssh://15.154.102.20
error: server closed connection

[root@RHEL53Xen1 ~]# service libvirtd status
libvirtd (pid 3871) is running...
[root@RHEL53Xen1 ~]#

Thanks,
Sandeep 

-----Original Message-----
From: Chris Lalancette [mailto:clalance@xxxxxxxxxx] 
Sent: Friday, September 25, 2009 1:46 PM
To: Subba Rao, Sandeep M (STSD)
Cc: libvir-list@xxxxxxxxxx; Velayudham, Madan Ganesh (STSD / ESS SW)
Subject: Re: [libvirt] Virsh migrate --live fails

Subba Rao, Sandeep M (STSD) wrote:
> Hi,
> 
>  I'm trying to live move a domU using virsh migrate command:
> 
> [root@RHEL53Xen1 ~]# xm list
> Name                                      ID Mem(MiB) VCPUs State   Time(s)
> Copy_RHELVM3                               1      511     1 -b----    898.3
> Domain-0                                   0     1507     4 r----- 133702.5
> [root@RHEL53Xen1 ~]# virsh migrate --live Copy_RHELVM3 
> xen+ssh://15.154.102.20
> error: server closed connection

Often this is because libvirtd crashed.  After this command, check that libvirtd is still running, and if not, you might want to collect the core dump from it and get the output of "thread apply all bt".

> 
> [root@RHEL53Xen1 ~]#
> 
> However the same works using xm migrate --live.
> 
> The source and the destination are RHEL 5.3 Xen hosts.
> 
> Libvirt:
> 
> 
> [root@RHEL53Xen1 ~]# rpm -qa | grep libvirt
> libvirt-0.3.3-14.el5
> libvirt-devel-0.3.3-14.el5
> libvirt-cim-0.5.1-4.el5
> libvirt-python-0.3.3-14.el5

At this point, though, this is an ancient libvirt.  I would suggest at least upgrading to the RHEL-5.4 version of libvirt, and see if you can reproduce the issue.  If you can, then I would try again with the recently released 0.7.1, and if you are still having problems, then collect the information like I mentioned above.

--
Chris Lalancette

--
Libvir-list mailing list
Libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]