From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60403) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3lPA-0000Ti-TF for qemu-devel@nongnu.org; Tue, 01 Dec 2015 08:55:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a3lP7-0002jl-KC for qemu-devel@nongnu.org; Tue, 01 Dec 2015 08:55:40 -0500 Received: from mail-wm0-x231.google.com ([2a00:1450:400c:c09::231]:36563) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3lP7-0002jf-8d for qemu-devel@nongnu.org; Tue, 01 Dec 2015 08:55:37 -0500 Received: by wmww144 with SMTP id w144so173908577wmw.1 for ; Tue, 01 Dec 2015 05:55:36 -0800 (PST) Sender: Paolo Bonzini References: <2757099.oMy77gOrqp@pendragon.usersys.redhat.com> <871tb6tt6n.fsf@blackfin.pond.sub.org> <2538292.Alk3jII4Z9@pendragon.usersys.redhat.com> <87si3mb7yc.fsf@blackfin.pond.sub.org> From: Paolo Bonzini Message-ID: <565DA6D6.6020500@redhat.com> Date: Tue, 1 Dec 2015 14:55:34 +0100 MIME-Version: 1.0 In-Reply-To: <87si3mb7yc.fsf@blackfin.pond.sub.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] iSCSI options for IQN with colons List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster , Pino Toscano Cc: Peter Lieven , qemu-devel@nongnu.org, Ronnie Sahlberg 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