WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "Jacob Gorm Hansen" <jacobg@xxxxxxx>, "sowmya dayanand" <sowmyad@xxxxxxxxx>
Subject: RE: [Xen-devel] Cloning(making copies) of VMs
From: "Yu, Ping Y" <ping.y.yu@xxxxxxxxx>
Date: Wed, 9 Nov 2005 11:30:09 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Nov 2005 03:30:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcXkNwljC28Mgk86ShG5f8kv+GJ7nAApia8w
Thread-topic: [Xen-devel] Cloning(making copies) of VMs
A very interesting test for save/restore. :-)
As I tested in 7695 without modifying IP address for VM2, I found that 
VM1 and VM2 could be sucessfully restored, and each owns a 
different MAC address, though IP address is the same. 
In that way, maybe we can run "service network restart" to enable network.

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
>Jacob Gorm Hansen
>Sent: Tuesday, November 08, 2005 3:34 PM
>To: sowmya dayanand
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] Cloning(making copies) of VMs
>
>On 11/8/05, sowmya dayanand <sowmyad@xxxxxxxxx> wrote:
>
>> (VM1 is a virtual machine, with ip addr 10.10.10.1, and we 
>want to clone it
>> as VM2, with ip addr 10.10.10.2) both running on the same 
>physical machine.
>>
>> 1) Save VM1 as VM1_save (using xm save)
>> 2) copy VM1_save to VM2_save
>> 3) Change the vmid and the IP address info in the saved file 
>to that of VM2
>> (Any other information to be changed ?)
>> 4) Restore VM1_save and VM2_save (using xm restore)
>
>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.
>
>Best,
>Jacob
>
>_______________________________________________
>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

<Prev in Thread] Current Thread [Next in Thread>