From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Pino Toscano <ptoscano@redhat.com>
Cc: Peter Lieven <pl@kamp.de>,
qemu-devel@nongnu.org, Ronnie Sahlberg <ronniesahlberg@gmail.com>
Subject: Re: [Qemu-devel] iSCSI options for IQN with colons
Date: Tue, 1 Dec 2015 14:55:34 +0100 [thread overview]
Message-ID: <565DA6D6.6020500@redhat.com> (raw)
In-Reply-To: <87si3mb7yc.fsf@blackfin.pond.sub.org>
On 01/12/2015 14:43, Markus Armbruster wrote:
> Option parameter "id" is for naming things so that other things can
> refer to them. The actual name should not matter. If it does, it's a
> bug.
>
> From my largely iSCSI-ignorant point of view, it looks like -drive
> file=iscsi *might* use the target IQN it gets from the URL to look up
> the matching -iscsi option. That would be inappropriate.
Yes, it does.
I'm not sure if it's inappropriate; "id" is the one mechanism that
QemuOpts provides for looking up things, and it makes sense to use it
even if the lookup key is not user-controlled.
Unfortunately, the limitations on ids make -iscsi almost unusable; IQNs
almost always have a colon (the syntax is
iqn.YYYY-MM.com.example:string.controlled.by.example.com.owner; the
after-colon part is optional but in practice will be there). Either we
fix it with Pino's patch, or we might as well remove it.
In 2.6 we probably should get the new secret API, and -iscsi should be
modified so that you can specify a reference to a secret directly in -drive.
Paolo
prev parent reply other threads:[~2015-12-01 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 15:31 [Qemu-devel] iSCSI options for IQN with colons Pino Toscano
2015-12-01 9:27 ` Markus Armbruster
2015-12-01 13:26 ` Pino Toscano
2015-12-01 13:43 ` Markus Armbruster
2015-12-01 13:55 ` Paolo Bonzini [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=565DA6D6.6020500@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=pl@kamp.de \
--cc=ptoscano@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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).