From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhang Haoyu <zhanghy@sangfor.com.cn>, qemu-devel <qemu-devel@nongnu.org>
Cc: Gleb Natapov <gleb@kernel.org>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] question about live migration with storage
Date: Wed, 14 Jan 2015 08:34:43 +0100 [thread overview]
Message-ID: <54B61C13.9070207@redhat.com> (raw)
In-Reply-To: <201501141041046517018@sangfor.com.cn>
On 14/01/2015 03:41, Zhang Haoyu wrote:
> Hi, Paolo,
> what's advantages of drive_mirror over traditional mechanism implemented in block-migration.c ?
> Why libvirt use drive_mirror instead of traditional iterative mechanism as the default way
> of live migration with non-shared storage?
1) Being able to choose which block devices are migrated, and whether
they are migrated incrementally or not.
2) Finer-grain control the parameters of block migration (dirty bitmap
granularity).
3) Block and RAM migration do not share the same socket and thus can
more easily be parallelized.
Note that 1-2 are not yet supported by libvirt as far as I remember.
Paolo
next prev parent reply other threads:[~2015-01-14 7:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 1:48 [Qemu-devel] question about live migration with storage Zhang Haoyu
2015-01-13 2:03 ` Zhang Haoyu
2015-01-13 9:45 ` Paolo Bonzini
2015-01-14 2:41 ` Zhang Haoyu
2015-01-14 7:34 ` Paolo Bonzini [this message]
2015-01-14 7:58 ` Zhang Haoyu
2015-01-14 9:06 ` Paolo Bonzini
2015-01-15 3:54 ` Zhang Haoyu
2015-01-15 9:11 ` Paolo Bonzini
2015-01-15 9:56 ` Zhang Haoyu
2015-01-15 10:08 ` Paolo Bonzini
2015-03-10 2:01 ` Zhang Haoyu
2015-03-25 13:07 ` Paolo Bonzini
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=54B61C13.9070207@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=zhanghy@sangfor.com.cn \
/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.