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

[Xen-users] Live Migration and how exactly it works

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Live Migration and how exactly it works
From: "Nikola K. Zahariev" <nirangor@xxxxxxxxx>
Date: Thu, 18 Jun 2009 13:50:48 +0200
Cc:
Delivery-date: Thu, 18 Jun 2009 04:51:44 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=rAmG+8c39d760aSHhkBFYpD2px0AOl59LQBdf8oojrU=; b=mTOrZBA1uAgaRifmCXhJ4nfIODxVnpsafFyDg+wqezKzJFxg97+DMzelsKc/+3y4nQ e+jJsSFIACQ4YVSXybd7Q/U84S+EcAgCU6rW0O5767h6SBA38sa7RpiZd8+cn/l4v/iV 2uAeF97bMX8vwuBQBEaGj2y+/aHkk/24MBa4A=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=E4SCnH1a5Bzbhu3NIzbydWbEVIr9p+R7ZTCPWH/HNOsRiSbSqVkVoVyBBpaVO9KxHT UqNgZF5gN87g41BGbgPPrrsQpkmAJ0hL/aruSUmngPDxWkPPtsG2KP0aIHVBiBxAIYWk o5slO1y82Ayr40D2qxDCQFD8g7elCSFq340C4=
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
Hello everybody!

I have a couple of questions regarding the live migration feature in
XEN. How exactly does it work? I have read in a paper on the Internet
that there are three phases of the live migration process:

1. Push phase: iteratively copy the memory of the VM from the old host
to the new host
2. Stop-and-copy phase: when XEN sees that there is a certain amount
of pages that get dirtied very often it freezes the VM and copies
these pages to the new host
3. Pull phase: the VM starts on the new host and if it needs any page
that was not copied, it pulls it over the network

Is this the way XEN handles Live Migration?

If so, how is the length of the Push phase determined?
When exactly does XEN say "okay, now let's freeze the VM and copy the memory"?
Is there maybe an upper limit of iterations and a threshold of dirty
pages after which the VM gets stopped?
Does the length of the phase depend on the amount pages which get
dirtied? How fast should the pages change so that they get dubbed
"dirty"?

I looked in the official XEN Documentation, googled around the
Internet but couldn't find any information on the topic...

Maybe someone knows the answers?

Thanks in advance for any replies!

Best regards,
Nikola

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Live Migration and how exactly it works, Nikola K. Zahariev <=