NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: Remove references to "cpu_map.xml" in the documentation

Browse Source 
"cpu_map.xml" was moved to a directory "cpu_map" and split up into
several files.

Signed-off-by: Tim Wiederhake <twiederh@redhat.com>
Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
This commit is contained in:
Tim Wiederhake 2020-10-09 12:47:19 +02:00 committed by Jiri Denemark
parent b763fbbd55
commit cc5b1a562d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/formatdomain.rst
View File

@ -1361,7 +1361,7 @@ In case no restrictions need to be put on CPU model and its features, a simpler
``model`` ``model``
The content of the ``model`` element specifies CPU model requested by the The content of the ``model`` element specifies CPU model requested by the
guest. The list of available CPU models and their definition can be found in guest. The list of available CPU models and their definition can be found in
``cpu_map.xml`` file installed in libvirt's data directory. If a hypervisor directory ``cpu_map``, installed in libvirt's data directory. If a hypervisor
is not able to use the exact CPU model, libvirt automatically falls back to a is not able to use the exact CPU model, libvirt automatically falls back to a
closest model supported by the hypervisor while maintaining the list of CPU closest model supported by the hypervisor while maintaining the list of CPU
features. :since:`Since 0.9.10` , an optional ``fallback`` attribute can be features. :since:`Since 0.9.10` , an optional ``fallback`` attribute can be
@ -1376,7 +1376,7 @@ In case no restrictions need to be put on CPU model and its features, a simpler
:since:`Since 0.8.3` the content of the ``vendor`` element specifies CPU :since:`Since 0.8.3` the content of the ``vendor`` element specifies CPU
vendor requested by the guest. If this element is missing, the guest can be vendor requested by the guest. If this element is missing, the guest can be
run on a CPU matching given features regardless on its vendor. The list of run on a CPU matching given features regardless on its vendor. The list of
supported vendors can be found in ``cpu_map.xml``. supported vendors can be found in ``cpu_map/*_vendors.xml``.
``topology`` ``topology``
The ``topology`` element specifies requested topology of virtual CPU provided The ``topology`` element specifies requested topology of virtual CPU provided
to the guest. Four attributes, ``sockets``, ``dies``, ``cores``, and to the guest. Four attributes, ``sockets``, ``dies``, ``cores``, and