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

CPU cores currently in use or reserved for later use = 0
Available VSP memory = 884 Mbytes
Available swap space = 7032 Mbytes
Total memory allocated for vPars and VMs = 12544 Mbytes
Memory in use by vPars and VMs = 13568 Mbytes
Available memory for vPars or VMs is overdrawn by 1024 Mbytes
Available memory for 0 (max avail.) CPU VM = N/A Mbytes
Available memory for 0 (max avail.) CPU vPar = N/A Mbytes
Maximum vcpus for an HP-UX virtual machine = 7
Maximum vcpus for an OpenVMS virtual machine = 7
Maximum available vcpus for a VM is overdrawn by 1
Available CPU cores for virtual partitions are overdrawn by 1
When CPU or memory resources are overdrawn, either these resources must be brought back
online, or reservations on existing virtual machines or virtual partitions must be reduced or removed.
Resource reservations can be removed using the hpvmmodify -P name -x
resources_reserved=false command. Memory reservations can be reduced by using the
hpvmmodify -r option to reduce virtual machine or virtual partition memory size. CPU reservations
can be reduced by using either the -c or -e options to reduce the CPU count or CPU entitlement.
Note -e does not apply to a virtual partition, because it always has 100% entitlement to a CPU.
Use the information provided by hpvmstatus -s to determine the amount of overcommitted
resource, and then use hpvmmodify to reduce that resource's commitments appropriately.
When virtual machines are configured to use reserved resources, and CPUs are overcommitted,
it might require a combination of reducing both CPU entitlement, and CPU counts to bring the
system back into a committed state. When determining the appropriate amount of entitlement or
CPU count to reduce, Integrity VM packs CPU entitlement as efficiently as possible. For example,
if there are two virtual machines that require 50% entitlement of three CPUs, and there are seven
CPUs available in total on the VSP, that would mean that four CPUs would be available at 100%,
if needed (however, those two virtual machines might spread across 6 CPUs if those CPUs are not
otherwise in use.)
While it is not possible to increase resources on a reserving virtual machine or virtual partition
when the VSP is in an over-committed state, it is possible to reduce resource commitments, even if
that reduction still leaves the VSP in an over-committed state.
It is still possible to change resource assignments of virtual machines and virtual partitions when
the VSP is in an overcommitted state, if those virtual machines or virtual partitions do not reserve
resources. However it is not possible to set the resources_reserved=true.
7.1.10 Virtual devices
Use the -a option to allocate virtual network switches and virtual storage devices to the virtual
machine. The VSP presents devices to the virtual machine as “virtual devices.” Attached I/O devices,
such as tape, DVD burner, and autochanger, are not presented as virtual devices; they are presented
as physical I/O devices. You specify both the physical device to allocate to the virtual machine
and the virtual device name that the virtual machine will use to access the device. The following
sections provide brief instructions for creating virtual network devices and virtual storage devices.
7.1.10.1 Creating virtual network devices
The guest virtual network consists of:
• Virtual network interface cards (vNICs)
• Virtual switches (vswitches)
For virtual machines to communicate either with other virtual machines or outside the VSP system,
each virtual machine's virtual network must be associated with a virtual switch (vswitch). If you
start a virtual machine without a vswitch, the virtual machine has no network communication
channel.
82 Creating virtual machines