Glancing at the libvirt code in git, it doesn't appear to be possible to set the iSCSI initiator name for domains which are backed with iSCSI disks. Some background: When qemu contacts the iSCSI target, it sends its own initiator name, which, if not set, defaults to 'iqn.2008-11.org.linux-kvm'. Some iSCSI targets have variable configuration keyed on the initiator name -- that is definitely the case for a userspace iscsi target that I tested (called pyTarget[1]), and for a libguestfs user's unspecified target[2]. qemu lets you override the default initiator name[3] using: qemu -iscsi initiator-name=iqn.YYYY-MM... This appears to be a global setting. I'm not clear if it makes sense or is possible to have multiple initiator names for a single qemu. I'm not missing something am I? (Note I'm not talking about storage pools which do have a way to specify initiator name). Rich. [1] https://pytarget.codeplex.com/ [2] https://www.redhat.com/archives/libguestfs/2014-July/msg00013.html [3] https://lists.gnu.org/archive/html/qemu-devel/2012-01/msg02765.html -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list