HP-UX vPars and Integrity VM V6.3 Administrator Guide

information in the configuration file of the guest, it is automatically updated to reflect the current
operating system.
13.8 Creating VM labels
The -l option of the hpvmcreate or hpvmmodify command specifies the label of the VM. The
VM label is a descriptive label unique to a VM or vPar. The label can be useful in identifying a
specific VM in the output displayed by the hpvmstatus -V command. The label can contain up
to 255 alphanumeric characters, including A-Z, a-z, 0-9, the dash (—), the underscore (_), and
the period (.). If white space is desired, the label must be quoted ("").
For example, to create a VM with a label “Virtual Machine number one”, run the following
command:
# hpvmcreate -P vm001 -l "Virtual Machine number One"
# hpvmstatus -P vm001 -V
[Virtual Machines Details]
Virtual Machine Name : vm001
Virtual Machine UUID : 24a7bfa4-b1b2-11e2-8400-b499ba6430e0
Virtual Machine ID : 1
Virtual Machine Label : Virtual Machine number One
..
..
13.9 Specifying the VM boot attribute
The -B option of the hpvmcreate or hpvmmodify command specifies the startup behavior of
the VM. The start_attr attribute can have the following (case-insensitive) values:
• auto: Automatically start the VM when Integrity VM is initialized on the host.
• manual: Manually start the VM.
For example, to create a VM with start_attr attribute as manual, run the following:
# hpvmcreate -P vm001 –B manual
Alternatively, you can modify the start_attr attribute of an existing VM or vPar using the
hpvmmodify command:
# hpvmmodify -P vm001 –B auto
If the start_attr attribute is set to auto, the VM is started when Integrity VM is initialized. This
is the default. This occurs when the VSP system is booted, and when the Integrity VM software is
stopped and restarted on a running VSP. For example, when you upgrade Integrity VM to a new
version on a running system, the software is started automatically. The VSP attempts to start all
VMs for which the attribute is set to auto. If the resources are insufficient, some VMs might fail to
start.
If the attribute is set to manual, the VM is not started automatically when Integrity VM is initialized
on the VSP. You can start the VM manually with the hpvmstart command or through its virtual
console.
The -B option does not set the console of the VM to enable booting when the VM is started. This
function must be set with the console of the VM.
In addition to automatically starting guests when Integrity VM starts, this feature also determines
a startup order to best utilize VSP processor and memory resources. On cellular systems with CLM
configured, the goal is to start the guests so that CLM is utilized first. For each guest with the
start_attr attribute set to auto, the startup order is based on resources_reserved attribute
and a memory weight and a processor weight added together. A guest with
resources_reserved attribute set to true, gets the highest priority while deciding the boot
order.
A rough estimate of the memory weight calculation is:
224 Managing vPars and VMs using CLI