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@redhat.com] Sent: Friday, September 25, 2009 1:46 PM To: Subba Rao, Sandeep M (STSD) Cc: libvir-list(a)redhat.com; Velayudham, Madan Ganesh (STSD / ESS SW) Subject: Re: [libvirt] Virsh migrate --live fails Subba Rao, Sandeep M (STSD) wrote: 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". 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