From: Rami Rosen <rosenrami@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Live Migration algorithm in Xen Unstable ; tracing pre-copying stage
Date: Thu, 8 Sep 2005 20:40:37 +0200 [thread overview]
Message-ID: <ae5426fb050908114041fe165a@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1411 bytes --]
Hi,
I want to understand Migration and Live Migration in Xen and to 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 Self
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
or Self Migration ? In case it is a Managed Migration - what is the daemon
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
[-- Attachment #1.2: Type: text/html, Size: 1687 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2005-09-08 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 18:40 Rami Rosen [this message]
2005-09-09 8:14 ` Live Migration algorithm in Xen Unstable ; tracing pre-copying stage Jacob Gorm Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae5426fb050908114041fe165a@mail.gmail.com \
--to=rosenrami@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.