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

formatdomain.html.in: document the NUMA cpus auto fill feature

Browse Source 
We're not mentioning that we're replicating QEMU behavior on purpose.
First because QEMU will one day, maybe, change the behavior and
start to refuse incomplete NUMA setups, and then our documentation
is now deprecated. Second, auto filling the CPUs in the first
cell will work regardless of QEMU changes in the future.

The idea is to encourage the user to provide a complete NUMA CPU topology,
not relying on the CPU auto fill mechanic.

Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Daniel Henrique Barboza 2020-06-10 15:35:53 -03:00 committed by Michal Privoznik
parent 6c380dea61
commit 07e1a18acc
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/formatdomain.html.in
View File

@ -1829,7 +1829,16 @@
<p>
Each <code>cell</code> element specifies a NUMA cell or a NUMA node.
<code>cpus</code> specifies the CPU or range of CPUs that are
part of the node. <code>memory</code> specifies the node memory
part of the node. <span class="since">Since 6.5.0</span> For the qemu
driver, if the emulator binary supports disjointed <code>cpus</code> ranges
in each <code>cell</code>, the sum of all CPUs declared in each <code>cell</code>
will be matched with the maximum number of virtual CPUs declared in the
<code>vcpu</code> element. This is done by filling any remaining CPUs
into the first NUMA <code>cell</code>. Users are encouraged to supply a
complete NUMA topology, where the sum of the NUMA CPUs matches the maximum
virtual CPUs number declared in <code>vcpus</code>, to make the domain
consistent across qemu and libvirt versions.
<code>memory</code> specifies the node memory
in kibibytes (i.e. blocks of 1024 bytes).
<span class="since">Since 1.2.11</span> one can use an additional <a
href="#elementsMemoryAllocation"><code>unit</code></a> attribute to