From: Kashyap Chamarthy <kchamart@redhat.com>
To: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
Cc: qemu devel <qemu-devel@nongnu.org>,
qemu block <qemu-block@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Fam Zheng <famz@redhat.com>, Max Reitz <mreitz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
Wang Weiwei <wangww.fnst@cn.fujitsu.com>,
zhanghailiang <zhang.zhanghailiang@huawei.com>,
Jiang Yunhong <yunhong.jiang@intel.com>,
Dong Eddie <eddie.dong@intel.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Gonglei <arei.gonglei@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v24 01/12] unblock backup operations in backing file
Date: Tue, 16 Aug 2016 15:13:49 +0200 [thread overview]
Message-ID: <20160816131349.t44nbsovmlrrhnx6@eukaryote> (raw)
In-Reply-To: <1469602913-20979-2-git-send-email-xiecl.fnst@cn.fujitsu.com>
[I erroneously gave a Tested-by to the next patch (02/12) in this
series, instead of this one.]
On Wed, Jul 27, 2016 at 03:01:42PM +0800, Changlong Xie wrote:
> From: Wen Congyang <wency@cn.fujitsu.com>
>
> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
> Signed-off-by: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
> Signed-off-by: Wang WeiWei <wangww.fnst@cn.fujitsu.com>
> ---
> block.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
Tested-by: Kashyap Chamarthy <address@hidden>
Test case:
Without this patch applied
==========================
Create an empty target image:
$ qemu-img create -f qcow2 target.qcow2 1G
$ ./qmp-shell -v -p ./qmp-sock
(QEMU) blockdev-add
options={"id":"drive-ide1-0-0","driver":"qcow2","file":{"driver":"file","filename":"/export/target.qcow2"},"backing":"drive-ide0-0-0"}
(QEMU) blockdev-backup device=drive-ide0-0-0 target=drive-ide1-0-0 sync=none
{
"execute": "blockdev-backup",
"arguments": {
"device": "drive-ide0-0-0",
"target": "drive-ide1-0-0",
"sync": "none"
}
}
{
"error": {
"class": "GenericError",
"desc": "Node 'drive-ide0-0-0' is busy: node is used as backing hd of
'#block360'"
}
}
With this patch applied
=======================
`blockdev-backup` of an image to its immediate overlay succeds:
-----------------------------------------------------------------------
(QEMU) blockdev-backup device=drive-ide0-0-0 target=drive-ide1-0-0 sync=none
{
"execute": "blockdev-backup",
"arguments": {
"device": "drive-ide0-0-0",
"target": "drive-ide1-0-0",
"sync": "none"
}
}
{
"return": {}
}
(QEMU) query-block-jobs
{
"execute": "query-block-jobs",
"arguments": {}
}
{
"return": [
{
"busy": false,
"type": "backup",
"len": 41126400,
"paused": false,
"ready": false,
"io-status": "ok",
"offset": 0,
"device": "drive-ide0-0-0",
"speed": 0
}
]
}
-----------------------------------------------------------------------
--
/kashyap
next prev parent reply other threads:[~2016-08-16 13:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 7:01 [Qemu-devel] [PATCH v24 00/12] Block replication for continuous checkpoints Changlong Xie
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 01/12] unblock backup operations in backing file Changlong Xie
2016-08-04 9:46 ` Stefan Hajnoczi
2016-08-16 13:13 ` Kashyap Chamarthy [this message]
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 02/12] Backup: clear all bitmap when doing block checkpoint Changlong Xie
2016-08-04 9:47 ` Stefan Hajnoczi
2016-08-16 12:55 ` Kashyap Chamarthy
2016-08-16 13:10 ` Kashyap Chamarthy
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 03/12] Backup: export interfaces for extra serialization Changlong Xie
2016-08-04 9:53 ` Stefan Hajnoczi
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 04/12] Link backup into block core Changlong Xie
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 05/12] docs: block replication's description Changlong Xie
2016-08-04 9:55 ` Stefan Hajnoczi
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 06/12] auto complete active commit Changlong Xie
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 07/12] configure: support replication Changlong Xie
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 08/12] Introduce new APIs to do replication operation Changlong Xie
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 09/12] Implement new driver for block replication Changlong Xie
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 10/12] tests: add unit test case for replication Changlong Xie
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 11/12] support replication driver in blockdev-add Changlong Xie
2016-08-09 9:08 ` Kevin Wolf
2016-08-15 1:49 ` Changlong Xie
2016-08-15 8:37 ` Kevin Wolf
2016-08-15 9:32 ` Changlong Xie
2016-09-12 14:01 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2016-09-28 1:53 ` wangweiwei
2016-07-27 7:01 ` [Qemu-devel] [PATCH v24 12/12] MAINTAINERS: add maintainer for replication Changlong Xie
2016-08-08 14:50 ` [Qemu-devel] [Qemu-block] [PATCH v24 00/12] Block replication for continuous checkpoints Stefan Hajnoczi
2016-09-12 14:11 ` Stefan Hajnoczi
2016-09-28 1:30 ` wangweiwei
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=20160816131349.t44nbsovmlrrhnx6@eukaryote \
--to=kchamart@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eddie.dong@intel.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wangww.fnst@cn.fujitsu.com \
--cc=xiecl.fnst@cn.fujitsu.com \
--cc=yunhong.jiang@intel.com \
--cc=zhang.zhanghailiang@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).