HP Matrix Operating Environment 7.3 and 7.3 Update 1 Logical Server Management User Guide

5 Troubleshooting
This chapter covers some of the issues that can occur when you are using logical servers, and
provides the troubleshooting steps you need to correct the problem.
Removing a Hyper-V CSV volume may not remove the volume as an
activation target
In a Hyper-V cluster environment with clustered shared volumes (CSV), if a CSV volume is removed
from the environment, Matrix OE visualization may still show the volume as an available datastore
during logical server activation.
Suggested action
To remove the volume as an activation target:
1. Unpresent the physical disk associated with the volume.
2. Refresh logical server resources.
3. Select Insight Control virtual machine management resources.
Troubleshooting use of HP-UX portable image
Boot path requirements
Logical servers experience boot problems when no long form EFI boot path exists. Symptoms
include failure to boot and physical to virtual move failures with the following error message:
Failed to Update the VM's Resources. Exception: Unable to modify the
guest - The HPVM API used to set the EFI failed, most likely an invalid
EFI passed in.
An Integrity VM and Integrity VM blades use different versions of EFI. Integrity VM blades with
Virtual Connect can boot HP-UX using the FC boot WWN and LUN specified in the server profile
created by logical server management. However, an Integrity VM does not have this capability.
As a result, a logical server with a pre-provisioned disk and an OS can be booted on a server
with Virtual Connect, but after physical to virtual moves, the logical server cannot boot as an
Integrity VM guest. This is because the boot path inserted by VC is not a long form EFI boot path
as it does not include a disk signature and a full path to the EFI boot file.
Furthermore, each time the logical server is moved back to the server with Virtual Connect from
an Integrity VM, an additional boot path might be inserted by VC. This happens because the boot
path inserted by VC is modified upon import into an Integrity VM guest so when the logical server
returns to the server with Virtual Connect, it is no longer functional. This may eventually result in a
physical to virtual move failure.
Suggested action
To resolve this, install a valid long form boot path before performing physical to virtual move and
virtual to physical move. There are several options for creating the boot path including:
• Using the EFI boot manager to add a boot path (easiest method)
• Booting HP-UX (if installed) and using the setboot -p<path> command
• Automatically adding a boot path when installing HP-UX (if not installed)
Management of an Integrity VM guest using command-line utilities
A virtual Fibre Channel HBA added to an Integrity VM guest using hpvmmodify does not add a
storage port to the guest’s associated logical server.
Typically some changes made to an Integrity VM guest are reflected in the associated logical server
on the next refresh of virtual machine management resources. However, this does not include virtual
78 Troubleshooting