From: "Richard W.M. Jones" <rjones@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, armbru@redhat.com,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [RFC 0/2] Parse 'filename' option for RBD/iSCSI
Date: Mon, 12 Jun 2017 14:51:29 +0100 [thread overview]
Message-ID: <20170612135129.GA32008@redhat.com> (raw)
In-Reply-To: <cover.1497240079.git.jcody@redhat.com>
On Mon, Jun 12, 2017 at 12:05:12AM -0400, Jeff Cody wrote:
> We need to be able to parse the 'filename' option for both rbd and iscsi,
> because there may exist images in the wild that have json backing files,
> that specify the filename argument.
>
> Marking the series as RFC at least partially for the precedence given to
> arguments; as written, these patches will give preference to the 'filename'
> parameter over passed options.
I tested this as follows:
(1) Prepare a test image. By using the ‘qemu-img rebase -u’ option we
can set the formerly correct / now incorrect backing option to an
arbitrary json string of our choosing:
$ qemu-img create test.img -f qcow2 10M
$ qemu-img rebase -u -b 'json:{"file.driver":"rbd","file.filename":"rbd:rbd/rbd.img:mon_host=127.0.0.0"}' test.img
(2) With upstream qemu:
$ qemu-system-x86_64 -hda test.img
qemu-system-x86_64: -hda test.img: Could not open backing file: Parameters 'pool' and 'image' are required
(3) With upstream qemu + these two patches:
$ ~/d/qemu/x86_64-softmmu/qemu-system-x86_64 -hda test.img
[hangs and eventually reports a timeout because I don't really
have a Ceph server]
So I would say that these patches, superficially at least, do seem to
work. Although I wasn't able to test them against a real Ceph server.
Tested-by: Richard W.M. Jones <rjones@redhat.com>
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html
prev parent reply other threads:[~2017-06-12 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 4:05 [Qemu-devel] [RFC 0/2] Parse 'filename' option for RBD/iSCSI Jeff Cody
2017-06-12 4:05 ` [Qemu-devel] [RFC 1/2] block/rbd: enable filename option and parsing Jeff Cody
2017-06-12 4:05 ` [Qemu-devel] [RFC 2/2] block/iscsi: " Jeff Cody
2017-06-12 13:51 ` Richard W.M. Jones [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=20170612135129.GA32008@redhat.com \
--to=rjones@redhat.com \
--cc=armbru@redhat.com \
--cc=jcody@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).