[libvirt] [PATCH 2/2] docs: Document configuration quirks for virtio devices

Andrea Bolognani posted 2 patches 6 years, 11 months ago
[libvirt] [PATCH 2/2] docs: Document configuration quirks for virtio devices
Posted by Andrea Bolognani 6 years, 11 months ago
Some devices (namely virtio-scsi, virtio-gpu, virtio-keyboard,
virtio-tablet and virtio-mouse, plus virtio-crypto which is
not supported by libvirt) don't follow the same rules as all
other virtio devices, which is something that ought to be
documented.

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
---
 docs/formatdomain.html.in | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index eb00c01d96..a9a8cfcd46 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -4132,6 +4132,24 @@
       </dd>
     </dl>
 
+    <p>
+      While the information outlined above apply to most virtio devices,
+      there are a few exceptions:
+    </p>
+
+    <ul>
+      <li>
+        for SCSI controllers, <code>virtio-scsi</code> must be used instead
+        of <code>virtio</code> for backwards compatibility reasons;
+      </li>
+      <li>
+        some devices, such as GPUs and input devices (keyboard, tablet and
+        mouse), are only defined in the virtio 1.0 spec and as such don't
+        have a transitional variant: the only accepted model is
+        <code>virtio</code>, which will result in a non-transitional device.
+      </li>
+    </ul>
+
     <p>
       For more details see the
       <a href="https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg00923.html">qemu patch posting</a> and the
-- 
2.20.1

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] [PATCH 2/2] docs: Document configuration quirks for virtio devices
Posted by Cole Robinson 6 years, 11 months ago
On 3/6/19 7:17 AM, Andrea Bolognani wrote:
> Some devices (namely virtio-scsi, virtio-gpu, virtio-keyboard,
> virtio-tablet and virtio-mouse, plus virtio-crypto which is
> not supported by libvirt) don't follow the same rules as all
> other virtio devices, which is something that ought to be
> documented.
> 
> Signed-off-by: Andrea Bolognani <abologna@redhat.com>
> ---
>  docs/formatdomain.html.in | 18 ++++++++++++++++++
>  1 file changed, 18 insertions(+)
> 
> diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
> index eb00c01d96..a9a8cfcd46 100644
> --- a/docs/formatdomain.html.in
> +++ b/docs/formatdomain.html.in
> @@ -4132,6 +4132,24 @@
>        </dd>
>      </dl>
>  
> +    <p>
> +      While the information outlined above apply to most virtio devices,

*applies

> +      there are a few exceptions:
> +    </p>
> +
> +    <ul>
> +      <li>
> +        for SCSI controllers, <code>virtio-scsi</code> must be used instead
> +        of <code>virtio</code> for backwards compatibility reasons;
> +      </li>
> +      <li>
> +        some devices, such as GPUs and input devices (keyboard, tablet and
> +        mouse), are only defined in the virtio 1.0 spec and as such don't
> +        have a transitional variant: the only accepted model is
> +        <code>virtio</code>, which will result in a non-transitional device.
> +      </li>
> +    </ul>
> +
>      <p>
>        For more details see the
>        <a href="https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg00923.html">qemu patch posting</a> and the
> 

Reviewed-by: Cole Robinson <crobinso@redhat.com>

- Cole

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