External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-02-01 17:35:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: document that vfio is default for hostdev networks too

Browse Source 
When the default was changed from kvm to vfio, the documentation for
hostdev and interface was changed, but the documentation in <network>
was forgotten.

Also document when the default was changed from "always kvm" to "vfio
if available, else kvm" (1.0.5).
This commit is contained in:
Laine Stump 2014-04-16 12:23:02 +03:00
parent 062074c455
commit 668bf07f2c
2 changed files with 25 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/formatdomain.html.in
View File

@ -2788,12 +2788,16 @@
device assignment. Use the <code>name</code> attribute to device assignment. Use the <code>name</code> attribute to
select either "vfio" (for the new VFIO device assignment select either "vfio" (for the new VFIO device assignment
backend, which is compatible with UEFI SecureBoot) or "kvm" backend, which is compatible with UEFI SecureBoot) or "kvm"
(for the legacy device assignment handled directly by the KVM (the legacy device assignment handled directly by the KVM
kernel module)<span class="since">Since 1.0.5 (QEMU and KVM kernel module)<span class="since">Since 1.0.5 (QEMU and KVM
only, requires kernel 3.6 or newer)</span>. The default, when only, requires kernel 3.6 or newer)</span>. When specified,
the driver name is not explicitly specified, is to check whether device assignment will fail if the requested method of device
VFIO is available and use it if it's the case. If VFIO is not assignment isn't available on the host. When not specified,
available, the legacy "kvm" assignment is attempted. the default is "vfio" on systems where the VFIO driver is
available and loaded, and "kvm" on older systems, or those
where the VFIO driver hasn't been
loaded <span class="since">Since 1.1.3</span> (prior to that
the default was always "kvm").
</dd> </dd>
<dt><code>readonly</code></dt> <dt><code>readonly</code></dt>
<dd>Indicates that the device is readonly, only supported by SCSI host <dd>Indicates that the device is readonly, only supported by SCSI host

27
docs/formatnetwork.html.in
View File

@ -282,17 +282,22 @@
definition. <span class="since"> Since 0.10.0</span> definition. <span class="since"> Since 0.10.0</span>
<p> <p>
To use VFIO device assignment rather than To force use of a particular type of device assignment,
traditional/legacy KVM device assignment (VFIO is a new a &lt;forward type='hostdev'&gt; interface can have an
method of device assignment that is compatible with UEFI optional <code>driver</code> sub-element with
Secure Boot), a &lt;forward type='hostdev'&gt; interface a <code>name</code> attribute set to either "vfio" (VFIO
can have an optional <code>driver</code> sub-element is a new method of device assignment that is compatible
with a <code>name</code> attribute set to "vfio". To use with UEFI Secure Boot) or "kvm" (the legacy device
legacy KVM device assignment you can assignment handled directly by the KVM kernel module)
set <code>name</code> to "kvm" (or simply omit the <span class="since">Since 1.0.5 (QEMU and KVM only,
&lt;driver&gt; element, since "kvm" is currently the requires kernel 3.6 or newer)</span>. When specified,
default). device assignment will fail if the requested method of
<span class="since">Since 1.0.5 (QEMU and KVM only, requires kernel 3.6 or newer)</span> device assignment isn't available on the host. When not
specified, the default is "vfio" on systems where the
VFIO driver is available and loaded, and "kvm" on older
systems, or those where the VFIO driver hasn't been
loaded <span class="since">Since 1.1.3</span> (prior to
that the default was always "kvm").
</p> </p>
<p>Note that this "intelligent passthrough" of network <p>Note that this "intelligent passthrough" of network