From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] qemu-img: Allow rebase with no input base
Date: Wed, 8 May 2019 16:48:09 +0200 [thread overview]
Message-ID: <20190508144809.GI15525@dhcp-200-226.str.redhat.com> (raw)
In-Reply-To: <20190508140139.32722-1-mreitz@redhat.com>
Am 08.05.2019 um 16:01 hat Max Reitz geschrieben:
> This series allows using qemu-img rebase (without -u) on images that do
> not have a backing file. Right now, this fails with the rather cryptic
> error message:
>
> $ qemu-img rebase -b base.qcow2 foo.qcow2
> qemu-img: Could not open old backing file '': The 'file' block driver requires a file name
>
> Yeah, well, OK.
>
> With how rebase currently works, this would lead to the overlay being
> filled with zeroes, however. This is where patch 2 comes in and instead
> makes rebase use blk_pwrite_zeroes() whenever it handles an area past
> the input’s backing file’s EOF.
>
> (Note that additionally we could try to punch holes in the overlay
> whenever it matches the new backing file, but that’s something I’ll put
> off for later. (We don’t even have a reliable method for punching holes
> into an overlay yet, although I would like to have such because it could
> make active commit more efficient.))
>
> And patch 3 adds the usual test.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2019-05-08 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 14:01 [Qemu-devel] [PATCH v2 0/3] qemu-img: Allow rebase with no input base Max Reitz
2019-05-08 14:01 ` [Qemu-devel] [PATCH v2 1/3] " Max Reitz
2019-05-08 14:01 ` [Qemu-devel] [PATCH v2 2/3] qemu-img: Use zero writes after source backing EOF Max Reitz
2019-05-08 14:01 ` [Qemu-devel] [PATCH v2 3/3] iotests: Add test for rebase without input base Max Reitz
2019-05-08 14:46 ` Kevin Wolf
2019-05-09 16:45 ` Max Reitz
2019-05-08 14:48 ` Kevin Wolf [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=20190508144809.GI15525@dhcp-200-226.str.redhat.com \
--to=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 NNTP newsgroup(s).