HP Integrity Virtual Machines 4.3: Release Notes (5900-2265, May 2012)

3 Creating Virtual Machines
This chapter contains notes about creating and configuring virtual machines on the VM Host system.
3.1 Changes and Issues in the V4.3 Release
This section describes virtual machine creation or configuration issues in the V4.3 release.
3.1.1 Pass-Through Devices Used by Guest Devices Might Not be Valid After Recovery
Using Ignite
After performing a recovery of the host using Ignite, pass-through devices found in /dev/pt/*
might be invalid, which in turn might prevent guests from recognizing tape or disk devices. Symptoms
of this problem might include error messages like the following in the guest log file
(/var/opt/hpvm/guests/vm-name/log):
UsrMapScsiDevice: Opened failed on /dev/pt/pt_tape1: No such device or address
You might receive messages like the following in the /var/opt/hpvm/common/command.log
file:
mksf: Couldn't find driver matching arguments
hpvmdevmgmt: ERROR (host): system() failed on command '/usr/sbin/mksf -P -C disk -I 44 2>&1 >/dev/null' - No
such file or directory.
These messages can be caused by pass-through files being stale and in need of re-creation,
pass-through files pointing to devices that no longer correspond to devices that their names suggest,
or device special file names (DSFs) for devices that no longer exist for which hpvmdevmgmt -I
attempts to create pass-through devices.
To correct /dev/pt/* files that might be stale or which might point to the wrong device, do the
following on the VM Host to re-create them:
# rm /dev/pt/*
# rm /var/opt/hpvm/common/hpvm_devinit
# hpvmdevmgmt -I
To correct failed attempts by hpvmdevmgmt -I to create pass-through devices for devices that
no longer exist, use lssf to verify the validity of devices that no longer appear to exist:
# lssf -s
Verify that your guests are not configured to use those DSFs, and then remove them using rmsf:
# rmsf -x
3.1.2 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.1 Changes and Issues in the V4.3 Release 21