From: Nir Soffer <nsoffer@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"open list:Block layer core" <qemu-block@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Max Reitz <mreitz@redhat.com>, Eric Blake <eblake@redhat.com>
Subject: Re: [PATCH v2 2/1] qemu-img: Add "backing":true to unallocated map segments
Date: Tue, 15 Jun 2021 16:09:15 +0300 [thread overview]
Message-ID: <CAMRbyyvCrAcV9EeSgaZRfNoEondXpZn1jgphMgSDZFe_ce=Y0g@mail.gmail.com> (raw)
In-Reply-To: <6e5ca689-cc2d-067a-7299-dd2813c1db2b@virtuozzo.com>
On Tue, Jun 15, 2021 at 11:54 AM Vladimir Sementsov-Ogievskiy
<vsementsov@virtuozzo.com> wrote:
>
> 11.06.2021 22:03, Eric Blake wrote:
> > To save the user from having to check 'qemu-img info --backing-chain'
> > or other followup command to determine which "depth":n goes beyond the
> > chain, add a boolean field "backing" that is set only for unallocated
> > portions of the disk.
> >
> > Signed-off-by: Eric Blake<eblake@redhat.com>
> > ---
> >
> > Touches the same iotest output as 1/1. If we decide that switching to
> > "depth":n+1 is too risky, and that the mere addition of "backing":true
> > while keeping "depth":n is good enough, then we'd have just one patch,
> > instead of this double churn. Preferences?
>
> If change something, this one patch seems safer. Still, Nir said he don't use qemu-img map, so probably we don't need to modify qemu-img at all? Even our iotests change shows that this change may be incompatible with at least tests..
>
> I'm not against the patch and don't have strict opinion.
>
> And what I really think, is that qemu-img is outdated thing and we'd better develop QMP interface, which can be used with qemu binary or with qemu-storage-daemon.
I don't think qemu-storage-daemon can replace qemu-img. Having an easy
to use command
line tool is important. Using qmp with qemu-storage-daemon sounds like
a better option
for programs that want ultimate control.
Adding only "backing: true" seems a safe change that should not break
existing users
and make qemu-img map better.
The tests are broken because they compare strings instead of parsing
the json. A program
parsing qemu-img json output will not be broken by adding a new key.
Nir
next prev parent reply other threads:[~2021-06-15 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 14:01 [PATCH v2] qemu-img: Make unallocated part of backing chain obvious in map Eric Blake
2021-06-11 14:35 ` Vladimir Sementsov-Ogievskiy
2021-06-11 14:59 ` Eric Blake
2021-06-11 18:13 ` Nir Soffer
2021-06-11 19:03 ` [PATCH v2 2/1] qemu-img: Add "backing":true to unallocated map segments Eric Blake
2021-06-15 8:54 ` Vladimir Sementsov-Ogievskiy
2021-06-15 13:09 ` Nir Soffer [this message]
2021-06-22 15:38 ` Kevin Wolf
2021-06-22 16:56 ` Nir Soffer
2021-06-23 8:57 ` Kevin Wolf
2021-06-23 13:58 ` Nir Soffer
2021-06-23 16:04 ` Kevin Wolf
2021-06-23 16:35 ` Nir Soffer
2021-06-28 17:42 ` Eric Blake
2021-06-29 7:23 ` Vladimir Sementsov-Ogievskiy
2021-06-29 14:40 ` Kevin Wolf
2021-06-29 15:53 ` Nir Soffer
2021-06-22 17:51 ` Vladimir Sementsov-Ogievskiy
2021-06-22 17:04 ` Nir Soffer
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='CAMRbyyvCrAcV9EeSgaZRfNoEondXpZn1jgphMgSDZFe_ce=Y0g@mail.gmail.com' \
--to=nsoffer@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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 read-only IMAP folder(s) and NNTP newsgroup(s).