NT_Mail List
2006-Sep-14 21:21 UTC
[Xen-users] Avoiding suspension of xen VM at source after migration.
Xen Developers: Today, we can move a VM from point A to point B. The VM ends up at point B. After that, all resources are reclaimed at point A. Is there a way we that after the migration, the VM in A continues to run. We end up with two VMs, one in A and one (its clone) in B? I assume that today''s Xen doesn''t have any feature to do this (e.g., xm clone). I wonder however if there is a specific place in the Xen code that we can comment out to make this trick work (intuitively, the clone operation requires less code than the migration). Do you have any other recommendation/present work that can making this cloning possible. thanks, Chetan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ernst Bachmann
2006-Sep-15 08:49 UTC
Re: [Xen-users] Avoiding suspension of xen VM at source after migration.
On Thursday 14 September 2006 23:21, NT_Mail List wrote:> Xen Developers:Not a devel myself, but this topic pops up over and over again on the list.> Today, we can move a VM from point A to point B. The > VM ends up at point B. After that, all resources are > reclaimed at point A. Is there a way we that > after the migration, the VM in A continues to run. We > end up with two VMs, one in A and one (its clone) in > B? > > I assume that today''s Xen doesn''t have any feature to > do this (e.g., xm clone). I wonder however if there is > a specific place in the Xen code that we can comment > out to make this trick work (intuitively, the clone > operation requires less code than the migration). > > Do you have any other recommendation/present work that > can making this cloning possible.The hard part isn''t cloning the xen domU, the hard part is cloning the filesystems it runs on. Since that is usually a lenghty operation, the way to go would probably be: xm save domU. Copy filesystems, swap, statefile, etc xm restore domU on host1 xm restore domU on host2 Network filesystems, NBD and the like won''t work well as fs for your domU, since the cloned domU will claim to have the same sockets open, the same IP and MAC etc. HTH /Ernst _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users