From: John Snow <jsnow@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, qemu-block <qemu-block@nongnu.org>
Subject: [Qemu-devel] qemu-img behavior for locating backing files
Date: Wed, 01 Apr 2015 12:16:57 -0400 [thread overview]
Message-ID: <551C19F9.3020409@redhat.com> (raw)
Kevin, what's the correct behavior for qemu-img and relative paths when
creating a new qcow2 file?
Example:
(in e.g. /home/qemu/build/ or anywhere not /home: )
qemu-img create -f qcow2 base.qcow2 32G
qemu-img create -f qcow2 -F qcow2 -b base.qcow2 /home/overlay.qcow2
In 1.7.0., this produces a warning that the base object cannot be found
(because it does not exist at that location relative to overlay.qcow2),
but qemu-img will create the qcow2 for you regardless.
2.0, 2.1 and 2.2 all will create the image successfully, with no warnings.
2.3-rc1/master as they exist now will emit an error message and create
no image.
Since this is a change in behavior for the pending release, is this the
correct/desired behavior?
next reply other threads:[~2015-04-01 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 16:16 John Snow [this message]
2015-04-01 16:28 ` [Qemu-devel] qemu-img behavior for locating backing files Eric Blake
2015-04-02 9:38 ` Kevin Wolf
2015-04-07 0:31 ` John Snow
2015-04-07 8:44 ` Kevin Wolf
2015-04-07 15:55 ` John Snow
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=551C19F9.3020409@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@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).