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

Percent Cumulative
Virtual Machine Name VM # #VCPUs Entitlement Maximum Usage Usage
==================== ===== ====== =========== ======= ======= ================
guest0 1 2 10.0% 100.0% 2.0% 21637
guest1 2 2 10.0% 100.0% 2.5% 28863
linux0 4 2 10.0% 100.0% 0.8% 10318
win0 6 2 10.0% 100.0% 0.0% 0
[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
linux0 4 512MB 0B 64GB 3072MB 3072MB 0MB 3GB 0MB 0MB 0
0B DISABLED
win0 6 512MB 0B 64GB 2048MB 2048MB 0MB 2GB 0MB 0MB 0
0B DISABLED
9.8 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.
9.9 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.
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.
9.9.1 The Device Database File
Integrity VM device management stored Integrity VM device mapping information in the device
database file (/var/opt/hpvm/common/hpvm_mgmtdb). This file is divided into three sections:
• The header, which states that the file cannot be hand edited.
• The restricted device section, which contains a list of host devices that guests are not allowed
to access.
• The guest devices section, which contains devices, both storage and network, that guests
are configured to use.
Do not edit the hpvm_mgmtdb file directly unless you are specifically advised to do so. Always
use a supported Integrity VM commands (such as hpvmmodify or hpvmdevmgmt) to modify
virtual devices.
9.8 Integrity VM Log Files 161