178
Templates are essentially VMs with the is-a-template parameter set to true. A template is a "gold
image" that contains all the various configuration settings to instantiate a specific VM. XenServer ships
with a base set of templates, which range from generic "raw" VMs that can boot an OS vendor installation
CD (RHEL, CentOS, SLES, Windows) to complete pre-configured OS instances (the "Demo Linux VM"
template). With XenServer you can create VMs, configure them in standard forms for your particular needs,
and save a copy of them as templates for future use in VM deployment.
The template objects can be listed with the standard object listing command (xe template-list), and the
parameters manipulated with the standard parameter commands. See the section called “Low-level param
commands” for details.
Template parameters
Templates have the following parameters:
Parameter Name Description Type
uuid the unique identifier/object
reference for the template
read only
name-label the name of the template read/write
name-description the description string of the
template
read/write
user-version string for creators of VMs
and templates to put version
information
read/write
is-a-template true if this is a template.
Template VMs can never be
started, they are used only for
cloning other VMs
Note that setting is-a-
template using the CLI is not
supported.
read/write
is-control-domain true if this is a control domain
(domain 0 or a driver domain)
read only
power-state current power state; always
halted for a template
read only
power-state current power state; always
halted for a template
read only
memory-dynamic-max dynamic maximum memory
in bytes. Currently unused,
but if changed the following
constraint must be obeyed:
memory_static_max >=
memory_dynamic_max >=
memory_dynamic_min >=
memory_static_min.
read/write