Filter
Top Products
153
Parameter Name Description Type
VCPUs-params configuration parameters for
the selected VCPU policy.
You can tune a VCPU's pinning
with
xe template-param-set \
uuid=<template_uuid> \
VCPUs-params:mask=1,2,3
A VM created from this
template will then run on
physical CPUs 1, 2, and 3 only.
You can also tune the VCPU
priority (xen scheduling) with
the cap and weight parameters;
for example
xe template-param-set \
uuid=<template_uuid> \
VCPUs-params:weight=512
xe template-param-set \
uuid=<template_uuid> \
VCPUs-params:cap=100
A VM based on this template
with a weight of 512 will
get twice as much CPU as a
domain with a weight of 256
on a contended XenServer host.
Legal weights range from 1 to
65535 and the default is 256.
The cap optionally fixes the
maximum amount of CPU a VM
based on this template will be
able to consume, even if the
XenServer host has idle CPU
cycles. The cap is expressed in
percentage of one physical CPU:
100 is 1 physical CPU, 50 is half
a CPU, 400 is 4 CPUs, etc. The
default, 0, means there is no
upper cap.
read/write map parameter
VCPUs-max maximum number of VCPUs read/write
VCPUs-at-startup boot number of VCPUs read/write
actions-after-crash action to take if a VM based on
this template crashes
read/write
console-uuids virtual console devices read only set parameter
platform platform-specific configuration read/write map parameter