Operating Environment Software User Manual

2. Create a new Integrity VM guest using SAN-based storage and a LUN that has been previously
provisioned with an OS:
a. Create an Integrity VM guest on the VM Host using the hpvmcreate command.
b. Start the Guest.
c. Boot the OS directly from EFI.
d. Import the guest into LSM using the import operation. An error message similar to the
following is displayed:
Import failed for 16.92.100.170. The HP Integrity VM guest uses
NVIP storage but has no boot path configured. A boot path is
typically inserted when HP-UX is installed, or by the HP-UX
setboot command or through the EFI Boot Maintenance Manager.
Suggested action
To resolve this, add a valid boot entry for the Integrity VM guest using EFI (if the guest is not booted)
or the setboot command (if the OS is booted). After a valid boot entry is added, you must run
an logical server management refresh and select the Insight Control virtual machine management
(VMM) entry.
Catalog storage entries are not displayed in Select Storage Type menu
If the SPM service stops running or the default storage template is no longer available when you
view the Manage Storage Pool screen, the SAN catalog or SAN pre-populated catalog storage
entry options will not be provided in the Select Storage Type menu.
If the SPM service stops running or the default storage template is no longer available while on
the page, and the you attempt to add a Catalog Storage option, a message is displayed with
instructions on how to resolve it.
Importing a Microsoft Hyper-V virtual machine with configuration file in
default location is not supported
A Hyper-V virtual machine whose configuration file is in the default location on the hard disk in
\ProgramData\Microsoft\Windows\Hyper-V is not supported by logical server management.
You cannot import a virtual machine guest as a logical server if the virtual machine's configuration
file is in this location. There is a limitation in Microsoft Hyper-V that allows HP Insight Control virtual
machine management to re-register the virtual machine if the configuration file is created in this
directory. To prevent issues with reactivation, logical server management checks the path and
rejects any virtual machines with a configuration file in the default location.
Recovery after logical server operation failures
After performing a logical server operation such as a deactivation, you may see the following error
message on the Report Logical Server Job Status screen:
Internal error occurred. This logical server might be in an
inconsistent state. HP strongly recommends that you unmanage
logical server {logical server name} and verify the status
of {resource name: profile or VM}.
Possible causes are:
• Environment configuration problems.
• The resource became unavailable during the runtime of the logical server operation.
• The resource has been changed outside of logical server management. For example, the virtual
machine was deleted or the server blade profile was changed.
78 Troubleshooting