HP Integrity Virtual Machines 4.2.5 - HP Business Support Center

3.2.4 Do Not Run hpvmstart in Background When Starting Multiple Guests With
Resource Conflicts
Do not run the hpvmstart command in the background when starting multiple guests that have
resource conflicts. The locking that would normally catch and report the resource conflicts does
not always work properly in this situation.
3.2.5 Numbers Reported by Glance 4.6 or Later Running on VM Host Depend on
Context
Glance 4.6 or later is supported running in a VM Host or in a guest; however, certain measurements
might not apply in a particular context or report limited results. For example, measuring CPU
utilization on the VM Host reports all the time spent running in guests as "system time"; to receive
"user time" or "nice time" for a given guest, you must run Glance in that guest. Similarly,
memory-related faults, or system calls for a guest, are not visible from Glance running in the VM
Host, from Glance running in that guest. Glance also offers a number of virtualization-related
measurements. Note, Glance refers to virtual machines as logical systems.
3.2.6 Increasing Guest Default SCSI Queue Depths for MPT Virtual Devices can Lead
to I/O Failures
MPT virtual storage devices (VIO) have a maximum SCSI queue depth of 8. This is sufficient for
the default SCSI queue depth of all guest types that have applied their guest kits. Increasing SCSI
queue depths beyond the defaults might result in some I/O failures due to exhaustion of guest I/O
retries.
38 Creating Virtual Machines