HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

The value of HPVMAMRCHUNKSIZE is the default number of MB by which the guest attempts
to grow when it encounters memory pressure. The higher this value is, the more quickly a VM
attempts to grow when it encounters memory pressure. HP recommends that chunk-size values
be a multiple of the dynamic memory chunk size. For a description of dynamic memory chunk
size, see Section 9.7.1 (page 152).
The value of HPVMAMRWAITTIME is the maximum number of seconds that the VM startup
process waits for memory to become available before reporting failure due to insufficient memory.
This value can be set up to a maximum of 600.
If the values of HPVMAMRENABLE, HPVMAMRCHUNKSIZE, or HPVMAMRWAITTIME in
the hpvmconf file have been changed, sending SIGNUP to the hpvmamrd process causes it to
obtain the new values.
9.7.4.2.1 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. No error occurs if this is executed for a VM that does
not support dynamic memory, but it is ignored. A VM that does not have a value for
ram_dyn_entitlement is also ignored by automatic memory reallocation. A VM that has been
enabled for automatic memory reallocation does not support manual dynamic memory operations
from the VM. It does not support manual dynamic memory operations from the VM Host that
would cause the VM to shrink below its entitlement.
9.7.4.2.2 Managing Automatic Memory Reallocation on a VM
By default, a VM with automatic memory reallocation enabled has no additional constraints
placed on its physical memory. It does not go below its ram_dyn_min dynamic memory setting,
nor does it go below the "Comfortable minimum" described in Section 9.7.1 (page 152). An
additional minimum constraint can be set with the following -x option, which is supported on
running VMs.:
-x ram_dyn_entitlement=minimum memory size in MB
The following rules apply:
• If it is impossible to grow the running VM to the specified entitlement, this additional
minimum contraint specification fails.
• A VM cannot have its physical memory grow beyond its maximum memory.
• A VM cannot have its physical memory modified beyond a lower boundary of ram_dyn_min
or an upper boundary of ram_dyn_max.
By default, a VM uses the system-wide HPVMAMRCHUNKSIZE value as the number of MB
by which it attempts to grow when it encounters memory pressure. If a value other than the
system-wide default is preferred, a per-VM chunk size can be set with the following -x option:
-x amr_chunk_size=chunk size in MB
HP recommends that chunk-size values be a multiple of the dynamic memory chunk size, as
described in Section 9.7.1.2 (page 153). This option is supported on running VMs.
9.7.4.3 Viewing Automatic Memory Reallocation
Automatic memory reallocation parameters and status are displayed for each VM using the
standard Integrity VM commands. The hpvmstatus command displays the following information
about automatic memory reallocation:
# hpvmstatus -r
[Virtual Machine Resource Entitlement]
[Virtual CPU entitlement]
160 Managing Guests