HP Matrix Operating Environment Software - Manual (Page 81)

Suggested action
To resolve this situation, adjust the above steps so that the following is done directly after the
physical to physical move (
Step 7 ) of the VM Host and before the reactivation of the VM logical
server ( Step 9 ) as follows:
1. After the physical to physical move of the VM Host, edit the portability group of the logical
server and remove the VM Host that was moved.
2. Rediscover and re-license the VM Host that was moved.
3. Edit the portability group and add the VM Host again.
Importing an Integrity VM guest with no boot path
An Integrity VM guest configured with SAN-based storage fails during an import operation with
an error message similar to the following:
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.
This issue can occur in the following example scenarios:
1.
Create a new Integrity VM guest using SAN-based storage and a LUN that has not been
provisioned with an OS.
a.
Create an Integrity VM guest on the VM Host using the hpvmcreate command.
b. Start the guest.
c. 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.
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
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.
Catalog storage entries are not displayed in Select Storage Type menu 81