mirror of
https://github.com/libvirt/libvirt.git
synced 2025-02-25 18:55:26 -06:00
docs: Clarify semantics of model/@usable attribute in dom caps
The documentation could confuse people to expect that CPU models with usable='no' attribute are not usable at all on the current host. But they cannot be only used without explicitly disabling some features. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
This commit is contained in:
parent
c360ea28dc
commit
e4bf03b8ff
@ -249,9 +249,11 @@
|
|||||||
The <code>mode</code> element contains a list of supported CPU
|
The <code>mode</code> element contains a list of supported CPU
|
||||||
models, each described by a dedicated <code>model</code> element.
|
models, each described by a dedicated <code>model</code> element.
|
||||||
The <code>usable</code> attribute specifies whether the model can
|
The <code>usable</code> attribute specifies whether the model can
|
||||||
be used on the host. A special value <code>unknown</code> indicates
|
be used directly on the host. When usable='no' the corresponding model
|
||||||
libvirt does not have enough information to provide the usability
|
cannot be used without disabling some features that the CPU of such
|
||||||
data.
|
model is expected to have. A special value <code>unknown</code>
|
||||||
|
indicates libvirt does not have enough information to provide the
|
||||||
|
usability data.
|
||||||
</dd>
|
</dd>
|
||||||
</dl>
|
</dl>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user