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-users

Re: [Xen-users] Distributed xen or cluster?

To: lists@xxxxxxxxxxxx
Subject: Re: [Xen-users] Distributed xen or cluster?
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Date: Wed, 21 Jan 2009 14:31:05 +0700
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 20 Jan 2009 23:32:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <2009120235154.539023@leena>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <2009120235154.539023@leena>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.19 (X11/20090105)
lists@xxxxxxxxxxxx wrote:
>   
>>  What IS possible, though, is LIVE migration. For this to work :
>>  - backend storage for domU is stored in shared block device (SAN LUN,
>>     
>
> Speaking of this, while I understand that this is not redundancy, it would be 
> interesting to know how quickly such a migration could occur as this sounds 
> like the immediate solution at least.
>
>   

During migration, the longest process is copying domU's memory. In
general it'd be as fast as your dom0's link. For example, on my test,
migrating a Linux PV with 500MB memory using 100Mbps link between dom0s
took about 48s. During most of this time domU can keep on doing its job
(i.e. the down time is NOT 48s, it's much shorter). Pinging domU from
outside during the migration process shows 0% packet loss. ssh
connection to domU stops responding for a while but resumes normally
after a few seconds (mostly due to TCP retransmits, which is the same
thing you'd get if you yank the network cable and plug it back in).

So if you're interested in using live migration (using Xen, VMware, or
any other products) you should make sure that dom0s has fast private
network.

Regads,

Fajar

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

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