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

13.14.3.6 Upgrading the VirtualBase software when upgrading Integrity VM
The dynamic memory software has two components— the VSP support and the HP-UX guest support.
These two components must be at the same version level for dynamic memory to function. When
you upgrade Integrity VM, you must also install the new VirtualBase kit on the guest. (You must
also upgrade the guest operating system if it is no longer supported.) During this upgrade process,
dynamic memory might not function.
If there is a version mismatch, a message is written to the syslog file (/var/adm/syslog/
syslog.log) of the VSP when the guest starts. For example:
vmunix: (hpvmdvr) Dynamic memory version mismatch Guest 5.
Please update the guest kit
This example indicates that the VirtualBase software kit on VM number 5 is out of date. To determine
which guest is number 5, use the hpvmstatus command. In the following example, guest 5 is
named dale:
# hpvmstatus
Virtual Machine Name VM # Type OS Type State #VCPUs #Devs #Nets Memory
==================== ===== ======= ========= ====== ===== ===== ======= ========
chip 1 SH HPUX On (OS) 1 1 1 2 GB
dale 5 SH HPUX On (OS) 1 0 0 2 GB
For information about installing the VirtualBase software, see Section 2.6.2 (page 35).
13.14.4 Automatic memory reallocation
Automatic memory reallocation is an optional feature of Integrity VM that allows automated changes
in the amount of physical memory in use by VMs based on memory load conditions. Automatic
memory reallocation is available only on guests that support dynamic memory.
To use automatic memory reallocation, the VM must have the VirtualBase software installed, because
this is required for dynamic memory. For vPar or VM guest VirtualBase software installation
instructions, see Section 2.6.2 (page 35).
13.14.4.1 Enabling automatic memory reallocation on the VSP
On the VSP, the automatic memory reallocation software is included with Integrity VM. The automatic
memory reallocation daemon (hpvmamrd) is enabled by default. To disable automatic memory
reallocation, the following line must be included in the/etc/rc.config.d/hpvmconf file:
HPVMAMRENABLE=0. When HPVMAMRENABLE=0 is not set in hpvmconf, hpvmamrd is
automatically started and stopped when Integrity VM is started and stopped.
When running, hpvmamrd monitors the state of VMs that are enabled for automatic memory
reallocation. Every 10 seconds, hpvmamrd examines the state of relevant VMs, and takes action
within the parameters. It also takes action when an attempt is made to boot a VM that requires
more physical memory than is currently available.
13.14.4.2 Enabling automatic memory reallocation on a VM
By default, VMs are not enabled for automatic memory reallocation. Only VMs that support dynamic
memory can use automatic memory reallocation. Use the following -x options to enable automatic
memory reallocation on a VM:
-x amr_enable
-x ram_dyn_entitlement=minimum memory size in MB
This option is supported on running VMs. If this is executed for a VM that does not support dynamic
memory an error does not occur, but the command is ignored. A VM that does not have a value
for ram_dyn_entitlement is also ignored by automatic memory reallocation. A VM that is
enabled for automatic memory reallocation does not support manual dynamic memory operations
13.14 Managing dynamic memory from the VSP 239