From: Kevin Wolf <kwolf@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-block@nongnu.org, eblake@redhat.com, qemu-devel@nongnu.org,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 0/2] qemu-img: Check for backing image if specified during create
Date: Tue, 18 Jul 2017 15:31:08 +0200 [thread overview]
Message-ID: <20170718133108.GA4320@noname.str.redhat.com> (raw)
In-Reply-To: <20170718003422.4497-1-jsnow@redhat.com>
Am 18.07.2017 um 02:34 hat John Snow geschrieben:
> We do not currently guarantee that QEMU will or will not open a
> backing file when creating a new overlay file. Presently, QEMU will
> not open that file if you provide a filesize, because it has no reason
> to want to open it in that case.
>
> This series makes the contract more explicit: if '-u' is provided to
> create, we will not open the backing image regardless, erroring out if
> a size was not provided.
>
> In the other case, if '-u' is not provided, we now endeavor to open the
> backing image if possible to check that it exists. For now, if a size
> is provided and the image does not exist, QEMU will only warn to maintain
> compatibility with legacy behavior.
>
> In the future, QEMU may treat the operation as a failure if '-u' was not
> provided.
>
> Tests are amended primarily to pass the '-u' flag where it makes sense;
> which is when creating overlays for objects already open by QEMU. These
> will now generally fail to succeed because of image locking. In this
> case, they only warn instead of fail, but this keeps the output cleaner.
>
> Test 111 is updated to accommodate a new error message.
> 082, 085, 139, 156 and 158 add '-u' just to suppress warnings.
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2017-07-18 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 0:34 [Qemu-devel] [PATCH v5 0/2] qemu-img: Check for backing image if specified during create John Snow
2017-07-18 0:34 ` [Qemu-devel] [PATCH v5 1/2] blockdev: move BDRV_O_NO_BACKING option forward John Snow
2017-07-18 12:27 ` Eric Blake
2017-07-18 0:34 ` [Qemu-devel] [PATCH v5 2/2] qemu-img: Check for backing image if specified during create John Snow
2017-07-18 12:51 ` Eric Blake
2017-07-18 15:33 ` John Snow
2017-07-18 15:44 ` Eric Blake
2017-07-18 0:38 ` [Qemu-devel] [PATCH v5 0/2] " John Snow
2017-07-18 12:25 ` no-reply
2017-07-18 13:31 ` 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=20170718133108.GA4320@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).