From: Hanna Reitz <hreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, Fabian Ebner <f.ebner@proxmox.com>
Cc: kwolf@redhat.com, w.bumiller@proxmox.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, aderumier@odiso.com,
t.lamprecht@proxmox.com
Subject: Re: [PATCH 0/4] Make qemu-img dd more flexible
Date: Fri, 11 Feb 2022 17:42:57 +0100 [thread overview]
Message-ID: <c0415413-9692-c284-3858-a62178078ab0@redhat.com> (raw)
In-Reply-To: <20220211163100.lhqrztyrr2a4akji@redhat.com>
On 11.02.22 17:31, Eric Blake wrote:
> On Thu, Feb 10, 2022 at 02:31:19PM +0100, Fabian Ebner wrote:
>> Adds support for reading from stdin and writing to stdout (when raw
>> format is used), as well as overriding the size of the output and
>> input image/stream.
>>
>> Additionally, the options -n for skipping output image creation and -l
>> for loading a snapshot are made available like for convert.
> Without looking at the series itself, I want to refer back to earlier
> times that someone proposed improving 'qemu-img dd':
>
> https://lists.gnu.org/archive/html/qemu-devel/2021-02/msg00636.html
> https://lists.gnu.org/archive/html/qemu-devel/2018-08/msg02618.html
>
> As well as the observation that when we originally allowed 'qemu-img
> dd' to be added, the end goal was that if 'qemu-img dd' can't operate
> as a thin wrapper around 'qemu-img convert', then 'qemu-img convert'
> needs to be made more powerful first. Every time we diverge on what
> the two uses can do, rather than keeping dd as a thin wrapper, we add
> to our maintenance burden.
>
> Sadly, there is a lot of technical debt in this area ('qemu-img dd
> skip= count=' is STILL broken, more than 4 years after I first
> proposed a potential patch), where no one has spent the necessary time
> to improve the situation.
Note that by now (in contrast to 2018), we have FUSE disk exports, and I
even have a script that uses them to let you run dd on any image:
https://gitlab.com/hreitz/qemu-scripts/-/blob/main/qemu-dd.py
Which is nice, because it gives you feature parity with dd, because it
simply runs dd.
(The main problem with the script is that it lives in that personal repo
of mine and so nobody but me knows about it. Suggestions to improve
that situation are more than welcome.)
Now, the qemu storage daemon does not support loading qcow2 snapshots
(as far as I’m aware), which is proposed in patch 4 of this series. But
I think that just means that it would be nice if the QSD could support that.
Hanna
next prev parent reply other threads:[~2022-02-11 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 13:31 [PATCH 0/4] Make qemu-img dd more flexible Fabian Ebner
2022-02-10 13:31 ` [PATCH 1/4] qemu-img: dd: add osize and read from/to stdin/stdout Fabian Ebner
2022-02-10 13:31 ` [PATCH 2/4] qemu-img: dd: add isize parameter Fabian Ebner
2022-02-10 13:31 ` [PATCH 3/4] qemu-img: dd: add -n option (skip target volume creation) Fabian Ebner
2022-02-10 13:31 ` [PATCH 4/4] qemu-img: dd: add -l option for loading a snapshot Fabian Ebner
2022-02-11 16:31 ` [PATCH 0/4] Make qemu-img dd more flexible Eric Blake
2022-02-11 16:42 ` Hanna Reitz [this message]
2022-02-15 8:49 ` Fabian Ebner
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=c0415413-9692-c284-3858-a62178078ab0@redhat.com \
--to=hreitz@redhat.com \
--cc=aderumier@odiso.com \
--cc=eblake@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=t.lamprecht@proxmox.com \
--cc=w.bumiller@proxmox.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).