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

Re: [Xen-users] Problems starting xfrd to migrate a domain


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Miguel Gómez <elmiguelonmakinon@xxxxxxxxx>
  • Date: Fri, 8 Jul 2005 14:20:46 +0200
  • Delivery-date: Fri, 08 Jul 2005 12:19:32 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=l+vvQJQdvR/N5JchwZK3Yjz5z/zsE+d8Y/lFvzXMJkPdmSQuEZnQ/A3N+AQjyA22DQyLlT3Nwkx6+gAc51Pdb1GFKlv3xVZSSk0/EblQF6au+s6XNH2cNS0r0aoWEK6LGl1M55Gd9uqYnxkZa7OkvFiJ7Wgm4hNVndnBaQQSHwk=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Ok, it's working*!!!!!!


































(*) not really. ;)

It works, but not totally. What I've done is to create a loopback device( in the destiny machine) in the same path than the original one (in the origin machine). Not using NFS now.  It has the same size than the original one. Now, I can migrate the domain. I see, after the migration, the domain in the destiny machine and I can do "xm console" to that domain.
But something is wrong. That domain continues responding to ping but it filesystem is corrupted!!!! I can't move in the directory tree.
Furthermore, when I look at the logs, I see the memory (ram) data moving from one machine to another,  but I can not see the data in the filesystem doing that!!, and the time the migration lasts is too short to copy all the filesystem through the network.

Should I use NFS? How do you people do this?

I promise this is my last message today.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.