When I try to use an iscsi direct pool in a "--disk" clause for
virt-install, I get error "iSCSI: Failed to connect to LUN : Failed to log
in to target. Status: Target not found(515)".
>From the libvirt debug log, it looks like qemu-system-x86_64 threw the error
libvirt.libvirtError: internal error: process exited while connecting to
monitor: 2025-02-24T01:43:33.065140Z qemu-system-x86_64: -blockdev
{"driver":"iscsi","portal":"10.1.4.3:3260","target":"iqn.1992-09.com.seagate:01.array.00c0fff6c846-lun-3","lun":0,"transport":"tcp","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}:
iSCSI: Failed to connect to LUN : Failed to log in to target. Status:
Target not found(515)
I've seen that sort of error before when the initiator name isn't used.
Same message occurs if I use --qemu-commandline to add the "-iscsi
initiator-name=..." parameter or xpath to inject it into the disk xml
definition.
The qemu log listed the disk being defined with the commands
-blockdev
'{"driver":"iscsi","portal":"10.1.4.3:3260","target":"iqn.1992-09.com.seagate:01.array.00c0fff6c846-lun-3","lun":0,"transport":"tcp","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}'
\
-blockdev
'{"node-name":"libvirt-2-format","read-only":false,"driver":"raw","file":"libvirt-2-storage"}'
\
-device
'{"driver":"virtio-blk-pci","bus":"pci.4","addr":"0x0","drive":"libvirt-2-format","id":"virtio-disk0","bootindex":1}'
\
iscsi-ls and iscsi-inq return the right things. If I use
LIBISCSI_DEBUG=10, I don't see any debug messages from libiscsi which makes
me think maybe it's using openiscsi instead.
I posted this to the libvirt-users list but not getting any responses so
looking wider.
https://lists.libvirt.org/archives/list/us...@lists.libvirt.org/thread/OJWECD3LYWE3AZDB5ASLIKZDHJP6LRS3/
any ideas welcome.
klint.
