From: Max Reitz <mreitz@redhat.com>
To: Alberto Garcia <berto@igalia.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] Don't allow snapshots if the overlay has parent nodes
Date: Fri, 30 Oct 2015 19:22:11 +0100 [thread overview]
Message-ID: <5633B553.7080600@redhat.com> (raw)
In-Reply-To: <cover.1446123576.git.berto@igalia.com>
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]
On 29.10.2015 14:00, Alberto Garcia wrote:
> There are several sanity checks for the 'blockdev-snapshot' command,
> but none covers the use of a file BDS as the overlay node.
>
> { 'execute': 'blockdev-add', 'arguments':
> { 'options': { 'driver': 'qcow2',
> 'node-name': 'new0',
> 'file': { 'driver': 'file',
> 'filename': 'new.qcow2',
> 'node-name': 'file0' } } } }
>
> { 'execute': 'blockdev-snapshot', 'arguments':
> { 'node': 'virtio0',
> 'overlay': 'file0' } }
Well, I don't think the problem here is that file0 has a parent. For
instance, you might want to use a qcow2 child node of a quorum BDS as
the new overlay; or in the future, you may want to use a snapshot node
which has some filters on top of it.
To me, the problem is that file0 is driven by the driver "file" which
does not support backing files. I think that's what should be fixed.
Max
> This series fixes that and adds a new test case. This of course
> depends on the 'blockdev-snapshot' series:
>
> https://lists.gnu.org/archive/html/qemu-block/2015-10/msg00974.html
>
> I anyway wonder if it wouldn't be a good idea to have regular op
> blockers in all file BDSs?
>
> Regards,
>
> Berto
>
> Alberto Garcia (2):
> block: Don't allow snapshots if the overlay has parent nodes
> block: test 'blockdev-snapshot' using a file BDS as the overlay
>
> blockdev.c | 5 +++++
> tests/qemu-iotests/085 | 12 +++++++++++-
> tests/qemu-iotests/085.out | 4 ++++
> 3 files changed, 20 insertions(+), 1 deletion(-)
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-10-30 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 13:00 [Qemu-devel] [PATCH 0/2] Don't allow snapshots if the overlay has parent nodes Alberto Garcia
2015-10-29 13:00 ` [Qemu-devel] [PATCH 1/2] block: " Alberto Garcia
2015-10-29 13:00 ` [Qemu-devel] [PATCH 2/2] block: test 'blockdev-snapshot' using a file BDS as the overlay Alberto Garcia
2015-10-30 18:22 ` Max Reitz [this message]
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=5633B553.7080600@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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).