qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Zhang Haoyu" <zhanghy@sangfor.com.cn>
To: Paolo Bonzini <pbonzini@redhat.com>, 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 10:41:05 +0800	[thread overview]
Message-ID: <201501141041046517018@sangfor.com.cn> (raw)
In-Reply-To: 201501131002532239699@sangfor.com.cn


On 2015-01-13 17:45:45, Paolo Bonzini wrote:
> 
> On 13/01/2015 03:03, Zhang Haoyu wrote:
> > >I want to live migrate a vm with storage, with regard to the migration of storage,
> > >should I use drive_mirror or traditional mechanism implemented in block-migration.c ?
> > 
> > Because I don't use libvirtd to manage vm,
> > if I want to use drive_mirror to perform live migration with storage,
> > how to organize the flow via script?
> 
> The same as libvirt does.
> 
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?

Thanks,
Zhang Haoyu
> Paolo

  parent reply	other threads:[~2015-01-14  2:41 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 [this message]
2015-01-14  7:34     ` Paolo Bonzini
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=201501141041046517018@sangfor.com.cn \
    --to=zhanghy@sangfor.com.cn \
    --cc=gleb@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).