HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

8.10.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
8.11 Integrity VM Log Files
Each guest has a log file named /var/opt/hpvm/guests/guestname/log on each host.
The VM Host 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.
8.12 Managing the Device Database
Integrity VM cannot detect all potential backing store conflicts, and does not always prevent
misconfigured guests from booting. Conflicts can arise from the following:
• Specifying the same backing store for more than one virtual device.
If you add disk:scsi::disk:/dev/rdisk/disk2 for guest A, do not add the same
device to another guest or to the list of VM Host restricted devices.
• Specifying multiple backing store parameters that lead to the same physical storage.
If the VM Host has multiple paths to a storage device, like /dev/rdisk/disk0 and /
dev/rdisk/disk4, only one path should be specified for a disk:scsi or dvd:scsi in
guest A. The other path should not be used as a backing store by guest A or by any other
guest or the VM Host.
• Overlapping physical storage allocated for different backing store types.
If a guest uses a logical volume (for example, rlvol1) as a backing store device, the disks
used by the volume group on which the logical volume is made (for example, /dev/vg01)
cannot be used as backing stores.
• Veritas VxVM DMP device files (files under /dev/vx/rdmp/) are not supported by Symantec
for whole disk backing stores for virtual machines.
You can use the ioscan and sam commands to detect these conflicts. If you force guests
configured with these conflicts to start, data corruption might occur.
On the VM Host, do not extend a logical volume (LVM or VxVM) used as a backing store for a
guest root disk. If you do this, the guest panics on its next reboot with the following error:
System panic: all VFS_MOUNTROOTs failed: Need DRIVERS.
8.11 Integrity VM Log Files 169