From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Rami Rosen <rosenrami@gmail.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Live Migration algorithm in Xen Unstable ; tracing pre-copying stage
Date: Fri, 09 Sep 2005 10:14:56 +0200 [thread overview]
Message-ID: <43214480.1050603@diku.dk> (raw)
In-Reply-To: <ae5426fb050908114041fe165a@mail.gmail.com>
Rami Rosen wrote:
> 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.
Hi,
I am currently rewriting self-migration in Linux for Xen 3. Right now it
is at a stage where it can live-checkpoint itself to disk, and resume
from the checkpoint with my cstrap bootloader. I will post the code when
it is ready.
The managed migration is (if it works right now) in the normal Xen tree.
Jacob
prev parent reply other threads:[~2005-09-09 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 18:40 Live Migration algorithm in Xen Unstable ; tracing pre-copying stage Rami Rosen
2005-09-09 8:14 ` Jacob Gorm Hansen [this message]
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=43214480.1050603@diku.dk \
--to=jacobg@diku.dk \
--cc=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.