HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

11.9.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. 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 VSP that would
cause the VM to shrink below its entitlement.
11.9.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]
Percent Cumulative
Virtual Machine Name VM # #VCPUs Entitlement Maximum Usage Usage
==================== ===== ====== =========== ======= ======= ================
guest0 1 2 10.0% 100.0% 2.0% 237
guest1 2 2 10.0% 100.0% 2.5% 28863
[Virtual Machine Memory Entitlement]
DynMem Memory DynMem DynMem DynMem Comfort Total Free Avail Mem AMR
AMR
Virtual Machine Name VM # Min Entitle Max Target Current Min Memory Memory Memory Press Chunk
State
==================== ===== ======= ======= ======= ======= ======= ======= ======= ======= ======= ===== =======
========
guest0 1 512MB 2GB 5GB 5114MB 5114MB 1722MB 5GB 3534MB 324MB 0
0B DISABLED
guest1 2 1GB 2GB 4GB 2106MB 2106MB 1594MB 4GB 801MB 282MB 0 400MB
ENABLED
11.10 vPar/VM log files
Each vPar/VM has a log file named /var/opt/hpvm/guests/guestname/log on each VSP.
The VSP log files are stored as /var/opt/hpvm/common/command.log and hpvm_mon_log.
NOTE: A Failed API access to local running guest. message in the command.log
is a notification that a communication attempt with the hpvmapp process has failed. This message
is not an indication of a problem and can be ignored.
11.11 Managing the device database
vPar/VM cannot detect all potential backing store conflicts, and does not always prevent
misconfigured vPars/VMs from booting. Conflicts can arise from the following:
Specifying the same backing store for more than one virtual device.
If you add disk:avio_stor::disk:/dev/rdisk/disk2 for guest A, do not add the
same device to another guest or to the list of VSP restricted devices.
Specifying multiple backing store parameters that lead to the same physical storage.
If the VSP has multiple paths to a storage device, like /dev/rdisk/disk0 and /dev/
rdisk/disk4, only one path should be specified for a disk:avio_stor or
dvd:avio_stor in guest A. The other path should not be used as a backing store by guest
A or by any other guest or the VSP.
11.10 vPar/VM log files 189