Re: [PATCH] docs: document that vfio is default for hostdev networks too

[Martin Kletzander <mkletzan@xxxxxxxxxx>]

On Thu, Apr 17, 2014 at 04:53:50PM +0300, Laine Stump wrote:
> When the default was changed from kvm to vfio, the documentation for
> hostdev and interface was changed, but the documentation in <network>
> was forgotten.

When was that done?  I'd suggest adjusting that <span class="since">
to match versions when KVM was added and/or the switch to VFIO was
made; that's if there's a difference since v1.0.5.

ACK with that changed (or even without if the version doesn't need to
be changed)

Martin

> ---
> docs/formatnetwork.html.in | 23 +++++++++++++----------
> 1 file changed, 13 insertions(+), 10 deletions(-)
>
> diff --git a/docs/formatnetwork.html.in b/docs/formatnetwork.html.in
> index fc56b42..aeafbd9 100644
> --- a/docs/formatnetwork.html.in
> +++ b/docs/formatnetwork.html.in
> @@ -282,16 +282,19 @@
>             definition. <span class="since"> Since 0.10.0</span>
>
>             <p>
> -              To use VFIO device assignment rather than
> -              traditional/legacy KVM device assignment (VFIO is a new
> -              method of device assignment that is compatible with UEFI
> -              Secure Boot), a &lt;forward type='hostdev'&gt; interface
> -              can have an optional <code>driver</code> sub-element
> -              with a <code>name</code> attribute set to "vfio". To use
> -              legacy KVM device assignment you can
> -              set <code>name</code> to "kvm" (or simply omit the
> -              &lt;driver&gt; element, since "kvm" is currently the
> -              default).
> +              To force use of a particular type of device assignment,
> +              a &lt;forward type='hostdev'&gt; interface can have an
> +              optional <code>driver</code> sub-element with
> +              a <code>name</code> attribute set to either "vfio" (VFIO
> +              is a new method of device assignment that is compatible
> +              with UEFI Secure Boot) or "kvm" (the legacy device
> +              assignment handled directly by the KVM kernel
> +              module). 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. When specified, device assignment will fail if
> +              the requested method of device assignment isn't
> +              available on the host.
>               <span class="since">Since 1.0.5 (QEMU and KVM only, requires kernel 3.6 or newer)</span>
>             </p>
>
> --
> 1.9.0
>
> --
> libvir-list mailing list
> libvir-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/libvir-list

Attachment: signature.asc
Description: Digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list