Bug 1118334 - RFE: qemu: support -iscsi initiator-name=
Summary: RFE: qemu: support -iscsi initiator-name=
Keywords:
Status: NEW
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: TRACKER-bugs-affecting-libguestfs 1118305
TreeView+ depends on / blocked
 
Reported: 2014-07-10 13:07 UTC by Richard W.M. Jones
Modified: 2018-07-18 14:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1118305
Environment:
Last Closed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2014-07-10 13:07:06 UTC
+++ This bug was initially created as a clone of Bug #1118305 +++

Original description of problem (against libguestfs):

libguestfs has no means to set an explicit initiator IQN for iSCSI connections.  A default intiator IQN  ( incase of LIBGUESTFS-BACKEND=direct ) or a random IQN ( in case of libvirt backend ) is used for iSCSI connections. 
This creates problems when storage systems expect a preconfigured initiator IQN to be used while establishing iSCSI connections.

The underlying QEMU command has an option (`-iscsi initiator-name=<initiator-iqn>' to set initiator IQN string explicitly. But currently libguestfs has no option to set this parameter and pass it on to QEMU.

------

To implement this fully, we will also need support in libvirt.

I posted a message to libvir-list which contains fuller details:

https://www.redhat.com/archives/libvir-list/2014-July/thread.html#00281

Comment 1 Cole Robinson 2016-04-10 19:04:03 UTC
Since this is a global setting and not a per-disk setting, figuring out what the XML would look like is a bit tricky since we probably need a new top level element like <domain> <iscsi XXX/> </domain> or similar

Comment 2 Pino Toscano 2016-04-11 09:00:41 UTC
Theoretically qemu allows to set per-drive iscsi properties, although the system for this does not work for IQNs containing colons:
http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg06501.html
http://lists.nongnu.org/archive/html/qemu-devel/2015-12/msg00025.html (continuation of the above)

I'm currently playing with qemu's -drive to allow settings better per-drive iscsi properties.

Comment 3 Richard W.M. Jones 2016-04-11 09:47:00 UTC
(In reply to Pino Toscano from comment #2)
> Theoretically qemu allows to set per-drive iscsi properties, although the
> system for this does not work for IQNs containing colons:
> http://lists.nongnu.org/archive/html/qemu-devel/2015-11/msg06501.html
> http://lists.nongnu.org/archive/html/qemu-devel/2015-12/msg00025.html
> (continuation of the above)
> 
> I'm currently playing with qemu's -drive to allow settings better per-drive
> iscsi properties.

Can't you use a json: URL to specify an IQN with a colon in it?

Search the qemu man page for "json:" for examples.


Note You need to log in before you can comment on or make changes to this bug.