Re: [Xen-devel] Cloning(making copies) of VMs

[Deepak Manohar <mjdeepak@xxxxxxxxx>]

A more generic approach would probably question if one should save the
IP address and such information when saving a VM. This is because
information such as IP addresses are "perishable" ie they may not be
valid when restoring the VM.

 Probably one should identify such information and selectively save
such information?? -- thinking out aloud.


DM

On 11/9/05, Mark Williamson <mark.williamson@xxxxxxxxxxxx> wrote:
> > The problem is that while you are probably sucessful in telling the
> > host environment (xen + linux in domain0) that your cloned VM has IP
> > 10.10.10.2, the Linux inside VM2 does not know that it is supposed to
> > answer the new IP rather than 10.10.10.1, and will just silently drop
> > all traffic on 10.10.10.2. It would probably be quite simple (and
> > useful, see the Potemkin paper for instance) to have your domain
> > answer any incoming IP, or to rewrite all ingoing and outgoing packets
> > with a generic address, but you will need to hack either your guest
> > Linux or the networking scripts in dom0 to make that happen.
>
> I guess it might be nice (eventually) to have a set of "Xen guest tools",
> including a hotplug script that gets run on restore, enabling this sort of
> thing to be configured.  The domain would be told about the new IP using
> xenstore.
>
> Of course, this doesn't solve the immediate problem of making it work without
> hacking the code ;-)
>
> Cheers,
> Mark
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel