From: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
To: Haydn Solomon <haydn.solomon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Disk migration
Date: Fri, 14 Sep 2007 16:08:41 -0500 [thread overview]
Message-ID: <46EAF859.7010102@codemonkey.ws> (raw)
In-Reply-To: <b75785ba0709141350w18a25d20td2ef306aa35ca6d4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Haydn Solomon wrote:
> I see that vmware just demonstrated migration of virtual disks. I know
> that kvm is very young but I think has come a long way in a very short
> period. I just wanted to get some feedback/discussion on how difficult
> this would be to implement in kvm/qemu and if this would be anywhere
> in future plans for development? Would this be less complicated than
> live migration of memory?
Disk migration is super easy to implement in KVM. There are two basic
models you can follow to do disk migration. In a push model, you would
apply a similar algorithm to the memory migration algorithm whereas you
pushed the whole disk over in chunks keeping track of what bits on disk
have been dirtied. You'd converge after a certain number of iterations
and then perform the memory migration.
A pull model would immediately do the memory migration and allow QEMU to
continue running on the source node acting as an IO server. Any disk IO
from the guest would either go directly to disk if the block was present
or would be fetched from the QEMU instance on the source node. The only
trick here is that you'd want to continue transferring blocks even when
the guest isn't accessing the disk.
The push model may require parallelization of the disk and memory
convergence depending on how much disk activity the guest is doing.
That's a pretty interesting problem but it shouldn't be too hard to solve.
The push model has the advantage of having the smallest performance
impact over time. The pull model has an advantage of immediately
reducing CPU usage on the source node at the expense of a potentially
severe degradation in performance of the guest. Both models probably
require roughly the same amount of time for migration completion.
Very good thing for someone looking for a fun task in KVM :-)
Regards,
Anthony Liguori
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> ------------------------------------------------------------------------
>
> _______________________________________________
> kvm-devel mailing list
> kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-14 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 20:50 Disk migration Haydn Solomon
[not found] ` <b75785ba0709141350w18a25d20td2ef306aa35ca6d4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-14 21:08 ` Anthony Liguori [this message]
[not found] ` <46EAF859.7010102-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-09-15 0:25 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A0215ABD1-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-15 18:25 ` Anthony Liguori
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=46EAF859.7010102@codemonkey.ws \
--to=anthony-rdkfgonbjusknkdkm+me6a@public.gmane.org \
--cc=haydn.solomon-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox