From: John Ferlan <jferlan@redhat.com>
Date: Fri, 26 Jun 2015 18:09:59 +0000 (-0400)
Subject: docs: Clarification for when allowed to use 'lun' for "volume"
X-Git-Tag: v1.2.17-rc1~4
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=91b9643845062047ffa2c53130468fa3a8a66323;p=thirdparty%2Flibvirt.git

docs: Clarification for when allowed to use 'lun' for "volume"

While re-reading what I wrote for commit id '785a8940e', I realized
I needed to clarify that being able to present as a 'lun', the mode
property for the pool source element needed to be "host" (or empty)
and not "direct".

It was described correctly later in the mode host description, but
this just ensures it's not missed here as well.

Signed-off-by: John Ferlan <jferlan@redhat.com>
---

diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index 824297482c..0f5a41b9bd 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -1972,7 +1972,8 @@
             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>.
+            is "volume" when using an iSCSI source <code>pool</code>
+            for <code>mode</code> "host".
             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