| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Problems starting xfrd to migrate a domain
Miguel Gómez wrote:
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.
:-) Nice try.
Xen does not (currently) support synchronization of disk content. It relies
on you to do that. So you have to use NFS, or some other distributed system
like GFS or drbd to synchronize disks.
I am sorry I can't answer why the NFS setup does not work for you. I have
not yet tried myself.
Can you create the vm on both nodes (without migration) with the same config
file? Trying that would be the first thing to do for me.
Is the NFS file system mounted on both hosts in the same place?
Best Regards,
Michael Paesold
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home