"Further" clarification (and testing) shows that using a SCSI Fibre Channel NPIV device/lun from a storage pool as a <disk type='volume' device'lun'> will work. So just add that to the allowable options Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1230179 Signed-off-by: John Ferlan <jferlan@xxxxxxxxxx> --- docs/formatdomain.html.in | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index d0c1741..cf697f3 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -1972,8 +1972,10 @@ Using "lun" (<span class="since">since 0.9.10</span>) is only valid when the <code>type</code> is "block" or "network" for <code>protocol='iscsi'</code> or when the <code>type</code> - is "volume" when using an iSCSI source <code>pool</code> - for <code>mode</code> "host". + is "volume" when using an iSCSI storage <code>pool</code> + for <code>mode</code> "host" or as an + <a href="http://wiki.libvirt.org/page/NPIV_in_libvirt";>NPIV</a> + virtual Host Bus Adapter (vHBA) using a Fibre Channel storage pool. Configured in this manner, the LUN behaves identically to "disk", except that generic SCSI commands from the guest are accepted and passed through to the physical device. Also note that -- 2.1.0 -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list