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/
Home Products Support Community News


Re: [Xen-users] How does Live Migration work

To: <xen-users@xxxxxxxxxxxxxxxxxxx>, "Thiago Vinhas" <thiago@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] How does Live Migration work
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Sun, 18 Oct 2009 17:31:01 -0600
Delivery-date: Sun, 18 Oct 2009 16:55:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 2009/10/18 at 05:40, Thiago Vinhas <thiago@xxxxxxxxxxxxxxxx>
> Hi,
> I've been testing live migration extensively, but I'm not sure how it

It's a pretty complicated process, probably better to ask on the devel
list if you really want details :-).

> Sometimes I can successfully migrate a VM from one server to another,
> other times it just fails, and I don't know the reason.

Any hints in "xm dmesg" or "xm log"?  How about symptoms?  What does it
mean that it "just fails"?  Does it give any error messages?  Does it
give no error messages at all?  Please be more detailed.

> When migrating, xen "saves" the state of the machine, and restores it
> another server, right? Does it saves files somewhere? How much
> memory do I need to run the migration?

I don't think there's actually anything saved to disk, no.  Here's my
understanding of, basically, how it works:
- The domU is created on the destination server.
- An initial copy of the domU's memory is made from source server to
destination server.
- Once the initial copy is done, an incremental copy of memory is made
to see what has changed and the changes are copied over.
- This is done repeatedly until the changes are very, very small.
- The domU is paused on the source side.
- The final incremental memory change is copied over
- The domU is started ("unpaused") on the destination side.

(I could be wrong about something there - I'm not a Xen developer, so I
don't really have a firm grasp on how it works on the code side and
could most definitely be off in my description.)

The last three steps take very little time - milliseconds.  There are
several things that could affect the ability of the domU to migrate
correctly.  Among them are things like network flakiness, speed issues,
etc., when trying to copy the memory over.  Please look at some of the
output from both source and destination systems to determine what is


> Regards,
> -- 
> Thiago Vinhas de Moraes
> ________________________________________________________
> SimpleWeb Tecnologia Inovativa
> Soluções em cloud computing e gerenciamento de TI
> Av. das Américas, 500 - Bloco 23 / Sala 215 - Rio de Janeiro - RJ
> Tel/Fax: 0800-8880-WEB / (21) 3002-0377
> Celular: .(21) 9999-0027 / Skype: tvinhas
> E-Mail: thiago@xxxxxxxxxxxxxxxx 
> Web: http://www.simpleweb.com.br 

This e-mail may contain confidential and privileged material for the sole use 
of the intended recipient.  If this email is not intended for you, or you are 
not responsible for the delivery of this message to the intended recipient, 
please note that this message may contain SEAKR Engineering (SEAKR) 
Privileged/Proprietary Information.  In such a case, you are strictly 
prohibited from downloading, photocopying, distributing or otherwise using this 
message, its contents or attachments in any way.  If you have received this 
message in error, please notify us immediately by replying to this e-mail and 
delete the message from your mailbox.  Information contained in this message 
that does not relate to the business of SEAKR is neither endorsed by nor 
attributable to SEAKR.
Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>