From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Zhanghaoyu (A)" <haoyu.zhang@huawei.com>
Cc: "Huangweidong (C)" <weidong.huang@huawei.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Michal Privoznik <mprivozn@redhat.com>,
Linqiangmin <linqiangmin@huawei.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
"paolo.bonzini@gmail.com" <paolo.bonzini@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Xiahai <xiahai@huawei.com>,
"quintela@redhat.com" <quintela@redhat.com>,
Zanghongyong <zanghongyong@huawei.com>,
Luonengjun <luonengjun@huawei.com>,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>
Subject: Re: [Qemu-devel] [migration] questions about removing the old block-migration code
Date: Tue, 5 Nov 2013 14:34:12 +0100 [thread overview]
Message-ID: <20131105133412.GD16457@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <D3E216785288A145B7BC975F83A2ED1043EEDBB3@szxeml556-mbx.china.huawei.com>
On Sun, Nov 03, 2013 at 04:01:36AM +0000, Zhanghaoyu (A) wrote:
> I read below words on the report of <KVM Live Migration: Weather forecast (May 29, 2013)>,
> We were going to remove the old block-migration code
> Then people fixed it
> Good: it works now
> Bad: We have to maintain both
> It uses the same port than migration
> You need to migrate all/none of block devices
>
> The old block-migration code said above is that in block-migration.c?
Yes.
> What are the reasons of removing the old block-migration code? Buggy implementation? Or need to migrate all/none of block devices?
Buggy and tightly coupled with the live migration code, making it hard
to modify either area independently.
> What's the substitutional method? drive_mirror?
drive_mirror over NBD is an alternative. There are security and
integration challenges with those approaches but libvirt has added
drive-mirror block migration support.
Stefan
next prev parent reply other threads:[~2013-11-05 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 4:01 [Qemu-devel] [migration] questions about removing the old block-migration code Zhanghaoyu (A)
2013-11-05 13:34 ` Stefan Hajnoczi [this message]
2013-11-08 1:17 ` Zhanghaoyu (A)
2013-11-15 15:33 ` Stefan Hajnoczi
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=20131105133412.GD16457@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=haoyu.zhang@huawei.com \
--cc=linqiangmin@huawei.com \
--cc=luonengjun@huawei.com \
--cc=mprivozn@redhat.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=paolo.bonzini@gmail.com \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=weidong.huang@huawei.com \
--cc=xiahai@huawei.com \
--cc=zanghongyong@huawei.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).