From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com,
"Benoît Canet" <benoit.canet@irqsave.net>,
imain@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v6 00/10] Drop in_use from BlockDriverState and enable point-in-time snapshot exporting over NBD
Date: Wed, 11 Dec 2013 10:46:49 +0800 [thread overview]
Message-ID: <52A7D219.1070703@redhat.com> (raw)
In-Reply-To: <1385627982-14675-1-git-send-email-famz@redhat.com>
On 2013年11月28日 16:39, Fam Zheng wrote:
> This series adds for point-in-time snapshot NBD exporting based on
> blockdev-backup (variant of drive-backup with existing device as target).
>
> We get a thin point-in-time snapshot by COW mechanism of drive-backup, and
> export it through built in NBD server. The steps are as below:
>
> 1. (SHELL) qemu-img create -f qcow2 BACKUP.qcow2 <source size here>
>
> (Alternatively we can use -o backing_file=RUNNING-VM.img to omit explicitly
> providing the size by ourselves, but it's risky because RUNNING-VM.qcow2 is
> used r/w by guest. Whether or not setting backing file in the image file
> doesn't matter, as we are going to override the backing hd in the next
> step)
>
> 2. (QMP) blockdev-add backing=source-drive file.driver=file file.filename=BACKUP.qcow2 id=target0 if=none driver=qcow2
>
> (where ide0-hd0 is the running BlockDriverState name for
> RUNNING-VM.img. This patch implements "backing=" option to override
> backing_hd for added drive)
>
> 3. (QMP) blockdev-backup device=source-drive sync=none target=target0
>
> (this is the QMP command introduced by this series, which use a named
> device as target of drive-backup)
>
> 4. (QMP) nbd-server-add device=target0
>
> When image fleecing done:
>
> 1. (QMP) block-job-complete device=ide0-hd0
>
> 2. (HMP) drive_del target0
>
> 3. (SHELL) rm BACKUP.qcow2
>
> v6: Address Paolo's comments, (except for bitmask):
> - Add blocker for all backing_hd references, a relatively big change, some
> patches are reordered.
> - Introduce a few other necessary patches.
> - Move two snapshot checks into bdrv_snapshot_*.
>
> The interface is unchanged.
>
Hi,
Based on the size of change, this series needs some more review before
merging. And I'd like to know if there is any concern or objection with
op_blocker introduced here. I would like to base my next series
(incremental backup with dirty bitmap) on it.
Any more reviews/comments?
Thanks!
Fam
next prev parent reply other threads:[~2013-12-11 2:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 8:39 [Qemu-devel] [PATCH v6 00/10] Drop in_use from BlockDriverState and enable point-in-time snapshot exporting over NBD Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 01/10] qapi: Add BlockOperationType enum Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 02/10] block: Introduce op_blockers to BlockDriverState Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 03/10] block: Parse "backing" option to reference existing BDS Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 04/10] block: support dropping active in bdrv_drop_intermediate Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 05/10] stream: Use bdrv_drop_intermediate and drop close_unused_images Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 06/10] block: Replace in_use with operation blocker Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 07/10] block: Pass error in bdrv_snapshot_create Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 08/10] block: Add checks of blocker in block operations Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 09/10] qmp: add command 'blockdev-backup' Fam Zheng
2013-11-28 8:39 ` [Qemu-devel] [PATCH v6 10/10] block: Allow backup on referenced named BlockDriverState Fam Zheng
2013-12-11 2:46 ` Fam Zheng [this message]
2013-12-12 3:22 ` [Qemu-devel] [PATCH v6 00/10] Drop in_use from BlockDriverState and enable point-in-time snapshot exporting over NBD Ian Main
2013-12-12 8:14 ` Markus Armbruster
2013-12-12 8:16 ` Fam Zheng
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=52A7D219.1070703@redhat.com \
--to=famz@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=imain@redhat.com \
--cc=kwolf@redhat.com \
--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).