A few examples for <interface> had a type='direct' interface with no
sub-elements. This is not allowed - a type='direct' interface must
have at least a source element. (Most likely the example was copied
from the type='user' or type='ethernet' examples - they *do* allow an
instance with no sub-elements).
There was also one place that mistakenly used %lt; ... %gt; instead of
< ... > (for some reason, I make that typo all the time).
---
Pushed under the trivial rule.
docs/formatdomain.html.in | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index 95c3edc..b2e5db9 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -2364,7 +2364,6 @@
<pre>
...
<devices>
- <interface type='direct'/>
...
<interface type='direct'>
<source dev='eth0' mode='vepa'/>
@@ -2413,7 +2412,6 @@
<pre>
...
<devices>
- <interface type='direct'/>
...
<interface type='direct'>
<source dev='eth0.2' mode='vepa'/>
@@ -2441,7 +2439,6 @@
<pre>
...
<devices>
- <interface type='direct'/>
...
<interface type='direct'>
<source dev='eth0' mode='private'/>
@@ -2462,7 +2459,7 @@
passthrough, after first optionally setting the device's MAC
address to the configured value, and associating the device with
an 802.1Qgh capable switch using an optionally specified
- %lt;virtualport%gt; element (see the examples of virtualport
+ <virtualport> element (see the examples of virtualport
given above for type='direct' network devices). Note that - due
to limitations in standard single-port PCI ethernet card driver
design - only SR-IOV (Single Root I/O Virtualization) virtual
--
1.7.10.2