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

docs: Update documentation of CPU models in domain caps

Browse Source 
Using check='none' when starting a domain with a CPU model marked as
usable is no longer needed as libvirt will do the right thing even with
check='partial'.

Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
Reviewed-by: Andrea Bolognani <abologna@redhat.com>
This commit is contained in:
Jiri Denemark 2024-03-05 16:16:05 +01:00
parent 8132478fa0
commit 75ace65104
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/formatdomaincaps.rst
View File

@ -237,10 +237,12 @@ more details about it:
using the CPU model and no additional feature elements. Models marked as
usable (``usable='yes'``) can be safely used in domain XMLs with
``check='none'`` as the hypervisor guarantees the model can be used on the
current host and additional checks done by libvirt are redundant. In fact,
disabling libvirt checks via ``check='none'`` for such models is recommended
to avoid needless issues with starting domains when libvirt's definition of
a particular model differs from hypervisor's definition. The
current host and additional checks done by libvirt are redundant.
:since:`Since 10.2.0` libvirt automatically detects this situation and
avoids the redundant checks even when ``check='partial'`` is used, with
older releases disabling libvirt checks via ``check='none'`` for such models
is recommended to avoid needless issues with starting domains when libvirt's
definition of a particular model differs from hypervisor's definition. The
``deprecated`` attribute reflects the hypervisor's policy on usage of this
model :since:`(since 7.1.0)`. The ``vendor`` attribute :since:`(since 8.9.0)`
contains the vendor of the CPU model for users who want to use CPU models