HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
chip 1 HPUX On (OS) 2 1 1 3 GB 0
dale 5 HPUX On (OS) 2 1 1 3 GB 0
For information about installing the HP-UX guest management software, see Section 4.2 (page 54).
9.7 Integrity VM Log Files
Each guest has a log file named /var/opt/hpvm/guests/guestname/log.
The VM Host log files are stored as /var/opt/hpvm/common/command.log and
hpvm_mon_log.
9.8 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/rdsk/c0t1d2 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/rdsk/c3t2d0 and /
dev/rdsk/c4t2d0, 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
or disk partitions 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.8.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 should not 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 those devices, both storage and network, that
guests have been 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.2 Using the hpvmdevmgmt Command
To list and modify the devices used by the VM Host and the virtual machines, use the
hpvmdevmgmt command.
Table 9-6 describes the options to the hpvmdevmgmt command.
138 Managing Guests