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] Relocation

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Relocation
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Mon, 29 Aug 2005 13:01:57 +0100
Cc: Matthijs ter Woord <matthijsterwoord@xxxxxxxxx>
Delivery-date: Mon, 29 Aug 2005 12:02:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <012901c59e89$ad74d370$0463a8c0@terwoord4>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <012901c59e89$ad74d370$0463a8c0@terwoord4>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.8
> I'm new to this list, i checked the archives but can't find anything.

I'm not sure if anyone replied to this...  but here goes.

> I downloaded some documents (powerpoint shows, pdf files), and i'm
> fascinated by the Relocation feature of Xen. How does it work? What do i
> need for that?

To run it, you need two hosts running Xen and a guest with a network-based 
filesystem (i.e. a network block device, iSCSI, NFS root, or a SAN, etc).  
The network-based filesystem is required because after the migration the 
guest can't access the disks of the origin machine.

Live migration works by pre-copying the memory image of the virtual machine 
*whilst it's running* to the destination.  Obviously some parts of the memory 
will be updated by the running guest after the data has been copied.  A 
feature of Xen called "shadow logdirty mode" is used by the migration tool to 
record *which* parts of the memory were updated.  This data can then be 
resent to the destination host.

The pre-copying phase works in a cycle: the migration code repeatedly tries to 
copy the memory the guest modified to the destination so that it'll have an 
up-to-date copy.  The copying gets faster and faster in order to "race" with 
the virtual machine to get as much data pre-copied as possible.

When the guest is modifying data as fast as the migration code can send it, 
the guest is stopped.  The live migration code then sends the remaining data 
to the other end, and tells the destination machine to start its copy of the 
guest.  Doing this typically takes a few hundred milliseconds during which 
the guest is inactive.

> Also, is there also a way to do fail-over of a virtual machine? I know I
> can build clusters using OpenSSI and OpenMosix, but then existing TCP/IP
> connections are lost.

You can use standard mechanisms (network-based heartbeats, drbd, etc) to do 
failover, as you would for normal hosts.  More advanced techniques such as 
keeping a copy of a virtual machine running in-step on another host are being 
worked on.

Cheers,
Mark

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

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