From: Osier Yang Date: Thu, 12 May 2011 10:48:23 +0000 (+0800) Subject: docs: Fix documentation for cputune parameters X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=81cfe719981d62727b2e87b5361b6805e6f99218;p=libvirt.git docs: Fix documentation for cputune parameters This re-adds the example section originally written by Osier Yang, and indicates the version in which the cputune parameters became available in libvirt. Signed-off-by: Igor Serebryany --- diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in index dcfcd9424e..989dcf6317 100644 --- a/docs/formatdomain.html.in +++ b/docs/formatdomain.html.in @@ -288,6 +288,13 @@ <min_guarantee>65536</min_guarantee> </memtune> <vcpu cpuset="1-4,^3,6" current="1">2</vcpu> + <cputune> + <vcpupin vcpu="0" cpuset="1-4,^2"> + <vcpupin vcpu="1" cpuset="0,1"> + <vcpupin vcpu="2" cpuset="2,3"> + <vcpupin vcpu="3" cpuset="0,4"> + <cpushares>2048</cpushares> + </cputune> ...
@@ -351,21 +358,30 @@ virtual CPUs should be enabled.
cputune
-
The optional cputune element provides details - regarding the cpu tunable parameters for the domain.
+
+ The optional cputune element provides details + regarding the cpu tunable parameters for the domain. + Since 0.9.0 +
vcpupin
-
The optional vcpupin element specifies which of host +
+ The optional vcpupin element specifies which of host physical CPUS the domain VCPU will be pinned to. If this is ommited, each VCPU pinned to all the physical CPUS by default. It contains two required attributes, the attribute vcpu specifies vcpu id, and the attribute cpuset is same as attribute cpuset - of element vcpu. NB, Only qemu driver supports
+ of element vcpu. (NB: Only qemu driver support) + Since 0.9.0 +
shares
-
The optional shares element specifies the proportional +
+ The optional shares element specifies the proportional weighted share for the domain. If this is ommited, it defaults to the OS provided defaults. NB, There is no unit for the value, it's a relative measure based on the setting of other VM, e.g. A VM configured with value - 2048 will get twice as much CPU time as a VM configured with value 1024.
+ 2048 will get twice as much CPU time as a VM configured with value 1024. + Since 0.9.0 +

CPU model and topology