[Xen-devel] Avoiding Xen suspension at source after migrate.

[NT_Mail List <nt_at_list@xxxxxxxxx>]

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 could 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-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel