HP-UX vPars and Integrity VM V6.3 Administrator Guide

• Previous Dynamic I/O operations or PCI OLR operations are in progress.
• The target of the operation is an Integrity VM guest that is being or has been suspended
or
• The target of the operation is an Integrity VM guest being migrated.
NOTE: Dynamic addition of DMP device as backing store is not supported. Adding DMP device
on the running guest fails with the following error:
# hpvmmodify -p1 -a disk:avio_stor::disk:/dev/vx/rdmp/c513t16d5
Error: Online Addition of DMP device /dev/vx/rdmp/c513t16d5 is not supported.
hpvmmodify: Unable to modify the vPar or VM.
When you attempt a DMP device addition online, the new device addition does not get saved to
the guest configuration to be applied when the guest is next restarted. You have to repeat the
device addition after the vPar or VM guest is shut down.
13.17.2 Errors and failure logs
Errors in the command parameters or conditions which prevent the operation from being initiated
is reported immediately in the output of hpvmmodify(1M) and vparmodify(1M). Operational failures
is logged in the guest log file at /var/opt/hpvm/guests/<Guest Name>/log.
13.18 vPar or VM log files
Each vPar or VM guest has a log file named /var/opt/hpvm/guests/<Guest Name>/log
on each VSP.
The VSP log files are stored as /var/opt/hpvm/common/command.log and hpvm_mon_log.
The command.log file contains the entries in the following formats:
mm/dd/yy hh:mm:ss|process_id|message_type|owner|user|Message
process_id field captures the process id of the program which logs the message
Message_type indicates the nature of message, such as "ERROR", "WARNING", SUMMARY,
NOTE, CHANGE
Owner indicates whether it is running on behalf of host or guest. This field usually
logs the guestname when hpvm* command is executed on particularguest
user indicates the user-name of the process which has logged the message
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.
13.19 Managing the device database
A vPar or VM guest cannot detect all potential backing store conflicts, and does not always prevent
misconfigured vPars or VM guests 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, such as /dev/rdisk/disk0 and /dev/
rdisk/disk4, only one path must be specified for a disk:avio_stor or dvd:avio_stor
248 Managing vPars and VMs using CLI