External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-10-30 09:53:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document configuration quirks for virtio devices

Browse Source 
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>
Reviewed-by: Cole Robinson <crobinso@redhat.com>
This commit is contained in:
Andrea Bolognani 2019-03-06 12:10:05 +01:00
parent ff3f22e0ec
commit 73bc4f185e
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/formatdomain.html.in
View File

@ -4132,6 +4132,24 @@
</dd> </dd>
</dl> </dl>
<p>
While the information outlined above applies 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> <p>
For more details see the 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 <a href="https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg00923.html">qemu patch posting</a> and the