HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

Possible causes
• The UUID is null or missing.
• The VM hosts do not have the proper licenses installed.
• The target VM host is not discovered during the host Discovery phase.
• Integrity VM targets: The private network between the source and target servers does not have
SSH set up properly.
Suggested actions
• Verify that the VM host is properly configured and has a UUID. To perform this check, view
the HP SIM system page for the VM host and look for the UUID field.
Perform the following steps if vselog.lsm.log contains the error:
2010-03-05 12:58:41,675 [pool-8-thread-9] WARN app - (LSM) Populate VM Host
(15.2.9.3) failed with exception: LSM_ADPT_VMM_ERR_NO_VM_HOST_UUID
1. Identify the system using HP SIM.
2. Check the VM host status in HP SIM.
3. Unregister the host, then register it again.
4. When the VM status is green, refresh Insight Control virtual machine management resources
using the Tools→Logical Servers→Refresh... menu selection.
For more information, see the HP Insight Control virtual machine management documentation
at Enterprise Information Library.
• Run the Insight managed system setup wizard to verify that the licenses are properly installed
on all of the managed servers.
• Verify the credential settings are properly configured on the VM host and rerun the host
Discovery process.
• Integrity VM targets: To enable secure communication between the source and target hosts,
generate SSH keys on both systems. You need root privileges to generate and set up the SSH
keys required for guest migration. Use the secsetup script provided by Integrity VM. Execute
the following command on both the source and target hosts:
# /opt/hpvm/bin/secsetup -r otherhost
For more information, see HP Integrity Virtual Machines 4.3: Installation, Configuration, and
Administration at http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/
c02752979/c02752979.pdf .
Failure during VM deletion leaves active but unpowered logical server
Issue
The deletion of a virtual machine requires that it be registered; therefore, part of the delete operation
is to register the virtual machine.
Possible causes
The Report→Logical Server Job Status... screen shows the progression of job detail messages for
a delete operation. If a virtual machine failure occurs for any reason during the interval between
registration and actual deletion, when the virtual machine is restarted, logical server management
sees a registered virtual machine and marks the associated logical server as active.
After the failure, the delete job appears to be incomplete, and the logical server is active, but not
powered on.
Troubleshooting procedures 159