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

docs: Clarify use of virtio-scsi model for SCSI controllers

Browse Source 
The current formulation can lead people to believe SCSI
controllers only allow the virtio-scsi model, but really the
only difference is that you have to use model='virtio-scsi'
where you would use model='virtio' for another device.

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
This commit is contained in:
Andrea Bolognani 2021-01-19 15:36:29 +01:00
parent 6503e1a0ee
commit 85523cfae0
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/formatdomain.rst
View File

@ -3428,8 +3428,10 @@ machine types, accept the following ``model`` values:
While the information outlined above applies to most virtio devices, there are a
few exceptions:
- for SCSI controllers, ``virtio-scsi`` must be used instead of ``virtio`` for
backwards compatibility reasons;
- for SCSI controllers, there is no ``virtio`` model available due to
historical reasons: use ``virtio-scsi`` instead, which behaves the same as
``virtio`` does for other devices. Both ``virtio-transitional`` and
``virtio-non-transitional`` work with SCSI controllers;
- 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 ``virtio``, which will result in a