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

Memory
During type conversion, the base and floating memory values for vPar or VM guest are as follows:
Case 1: Memory parameters for shared or VM guest.
For any memory modification for shared guest, the entire memory is considered as base memory.
Therefore, you cannot specify base and floating memory values. However, when an offline vPar
is converted to a VM guest, the base and floating memory configuration values are retained until
the values are modified.
Case 2: Memory parameters for vPar.
By default, entire memory for vPar is treated as base memory, with the following exceptions:
• Exception 1 – User explicitly specifies separate values for base and floating memory at the
time of create or modify.
• Exception 2 – When an offline vPar is converted to a VM guest, and again converted back
to vPar. In such a case, the base and floating memory configuration values are retained only
if the values are not modified on the VM guest.
Dynamic memory
The dynamic memory parameters of a VM will not be retained when a VM is transformed to vPar
and the same is transformed back to VM. The dynamic memory will be enabled by default after
transforming a vPar to VM and making resources_reserved attribute to “false”. If you keep
the value of resources_reserved attribute to “true” for a VM then dynamic memory will be
disabled.
Guest hardware paths
After the transformation between VM and vPar, the new vPar or VM guest might not have the same
hardware paths for network and storage devices. This can change the LAN instance number. To
preserve the LAN instance number, Matrix OE Portable Image product must be installed and
enabled on the guest OS before making the transformation.
Guest OS Power state management
Power state management is not supported on a VM. However, it is supported on vPar. This feature
gets enabled or disabled during the first boot depending on the Guest type. After transforming
VM into a vPar, the pstatectl command does not work. It gives the following error message:
# pstatectl info
pstaatectl: Could not open /dev/pwr (No such file or directory)
Missing device special file or unsupported platform
This issue is resolved in HP-UX 11i v3 March 2013 release and also available in PHCO_43231.
Guest OS version
VM supports HP-UX 11i v2 and 11i v3 as guest OS, where as vPar supports only HP-UX 11i v3
version. Transforming a VM, which is installed with HP-UX 11i v2 version, requires an guest OS
upgrade from HP-UX 11i v2 to HP-UX 11i v3.
13.6 Mix mode support for VM and vPar environment
Starting V6.2, mixed mode support is provided in the virtualized environment. VM and vPars can
be configured and run on the VSP at the same time. All the resources on the VSP are available for
both VM and vPars configuration. You can use the hpvmstatus -s to view the resources available
for VMs and vPars, and it also shows the vPar or VM types supported by the VSP.
# hpvmstatus -s
[HPVM Server System Resources]
vPar/VM types supported by this VSP = vPar, Shared
222 Managing vPars and VMs using CLI