From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rami Rosen Subject: Live Migration algorithm in Xen Unstable ; tracing pre-copying stage Date: Thu, 8 Sep 2005 20:40:37 +0200 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1364123570==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1364123570== Content-Type: multipart/alternative; boundary="----=_Part_15911_5851525.1126204837994" ------=_Part_15911_5851525.1126204837994 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I want to understand Migration and Live Migration in Xen and to trace the= =20 code which implements it. I had read the "Live Migration of Virtual Machines" doc=20 from the Architecture page of Xen WebSite. http://www.cl.cam.ac.uk/netos/papers/2005-migration-nsdi-pre.pdf Two Migrations methods are being dealt with: Managed Migration and Self=20 Migration. The work of Managed Migration is done with daemons weheras the work of Self= =20 Migration is being done mostly on the OS which is being migrated. I remeber I saw in some 2.0.* version an xfrd daemon which handled live=20 migration (if I am not wrong). I assume that it was a implementation of=20 Managed Migration. In xen-unstable the xfrd it is removed. I have two questions: 1) Is the live migration in xen-unstable implemented via Managed Migration or Self Migration ? In case it is a Managed Migration - what is the daemon who is managing this ?=20 2) Show me the code:=20 As I understand , much of the live migration process is based on using=20 shadow pages and a dirty bitmap vector (shadow.c, shadow_guest32.c=20 ,shadow_public in arch/x86 in the case of intel x386).=20 Where is the migration implementation in Xen-unstable ? I mean , for a=20 start, where is the code for the pre-copying stage ,which is the first stag= e=20 in migration,=20 and is used by both methods, Managed and Self Migration ?=20 Regards, Rami Rosen ------=_Part_15911_5851525.1126204837994 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,

   I want to understand Migration and Live Migration in Xen and t= o trace the code
which implements it.

  I had read the "Live Migration of Virtual Machines" doc from the  Architecture page of Xen WebSite.
http://www.cl.cam.ac.uk/netos/papers/2005-migration-nsdi-pre.pdf

 Two Migrations methods are being dealt with: Managed Migration and Se= lf Migration.

The work of Managed Migration is done with daemons weheras the work of Self Migration is being done mostly on the OS which is being migrated.

I remeber I saw in some 2.0.* version an xfrd daemon which handled live migration (if I am not wrong). I assume that it was a implementation of Managed Migration.

In xen-unstable the xfrd it is removed.

I have two questions:

1) Is the live migration in xen-unstable implemented via Managed Migration<= br> or Self Migration ? In case it is a Managed Migration - what is the daemon<= br> who is managing this ?

2) Show me the code:
   As I understand , much of the live migration process is based = on using
shadow pages and a dirty bitmap vector (shadow.c, shadow_guest32.c ,shadow_= public in arch/x86 in the case of intel x386).

   Where is the migration implementation in Xen-unstable ? I mean , for a start, where is the code  for the pre-copying stage ,which is the first stage in migration,
and is used by both methods, Managed and Self Migration ?

Regards,
Rami Rosen

------=_Part_15911_5851525.1126204837994-- --===============1364123570== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1364123570==--