HP-UX vPars and Integrity VM V6.1.5 Administrator Guide (5900-2295, April 2013)

7.1.3 Guest operating system type
Use the -O os_type option to specify the type of operating system that will run on the virtual
machine. This option is not required.
For os_type, specify hpux. For specific information about installing HP-UX guests, see Chapter 8
(page 103).
If you do not supply the operating system type, it defaults to UNKNOWN. When you install the
operating system and boot the guest, this guest configuration parameter is automatically set to the
appropriate operating system type.
When a running guest transitions from running in the machine console to running in the operating
system, the operating system type is detected. If the operating system type is different from the
information in the guest's configuration file, it is automatically updated to reflect the current operating
system.
7.1.4 Reserved resources
Use the -x resources_reserve=true to specify whether CPU, memory and device resources
should be reserved while the virtual machine is in the off state. Resource reservations attempt to
guarantee that resources will be available so that the virtual machine can be started at any time.
For more information about reserved resources, see “Reserved resources and resource
over-commitment” (page 81)
7.1.5 Virtual CPUs
Use the -c number_vcpus option to the command to specify the number of virtual CPUs (vCPUs)
that the virtual machine can use. If you do not specify the number of vCPUs, the default is 1. For
example, to set the new virtual machine host1 to have two vCPUs, enter the following command:
# hpvmcreate -P host1 -c 2
Every virtual machine has at least one vCPU. A running virtual machine cannot use more vCPUs
than the number of physical CPU-cores on the VSP system. (For the purpose of this discussion, the
term “physical CPU” refers to a processing entity on which a software thread can be scheduled.)
Do not set the number of vCPUs higher than the physical number of CPU-cores, as this can cause
undesirable behavior.
NOTE: Even if hyperthreading and lcpu_attr is turned ON in the VSP, the number of vCPUs
in a VM cannot be more than the number of physical CPU-cores on the system.
HP strongly discourages changing the hyperthreading/lcpu_attr settings on the VSP.
The following command specifies the number of virtual CPUs to set:
# hpvmcreate -c number_vcpus[:minimum[:maximum]]
The minimum and maximum values are boundary values, which are enforced if the number of
virtual CPUs this virtual machines changes in the future. The default value is one (1) virtual CPU
for the virtual machine. The number of virtual CPUs should not be set higher than physical number
of CPUs on the VSP, as this can cause undesirable behavior.
The default minimum and maximum boundary values are a minimum of one (1) virtual CPU, and
a maximum of sixteen (16) virtual CPUs.
NOTE: HP Integrity VM does not support real-time applications running in the guest. Scheduling
and precise timing properties that can be relied upon on physical hardware are not guaranteed
to be preserved in a virtual machine. In particular, changing the hires_timeout_enable(5)
HP-UX tunable may not have the desired effect.
You can change the number of enabled CPUs in HP-UX guests, using the hpvmmgmt –c num
command. This command sets the number of enabled virtual CPUs to the number indicated by
7.1 Specifying virtual machine characteristics 79