HP Matrix Operating Environment Software User Manual
Page 88
VMware ESX hosts are licensed but do not show up in Insight Orchestration Unassigned pool.
Issue
The hosts with virtual machine management cannot register because they only have base ESX
licenses.
Possible cause
1.
In SIM's Deploy
→License Manager..., apply full ESX license(s).
2.
In SIM's Configure
→Insight Control virtual machine management→Register VM Host...,
re-register the VM Hosts, for example:
a. Select collection: ESX VM Hosts
b. Click View Contents
c. Click Apply
d. Click Next
e. Click Run Now (and wait for the task to complete)
Action
Create Request fails with a virtual machine customization error.
Issue
•
The environment is not completely configured
•
The virtual machine used in the VMM template was not powered off cleanly
Possible cause
•
If the environment is not completely configured, requests might fail when executing the virtual
machine customization step. Issues can include, missing the sysprep folder on the VI3 server,
insufficient licenses on the VI3 server, or attempting to customize a virtual machine with a
guest operating system that is not supported on the VI3 server. Verify that the environment
is correctly configured and be sure you are provisioning a supported guest operating system.
For more information on configuration, see HP Insight Software Installation and Configuration
Guide available at
•
To power off the virtual machine cleanly before creating the VMM template, see
.
Action
Provisioning a virtual machine failed with a VM must be powered off for customization
error message.
Issue
The Insight Control virtual machine management template that is being used was created when
the virtual machine was in a suspended state.
Possible cause
Provisioning will fail during customization with an error message if the virtual machine
management template is created when the virtual machine is in a suspended state and then used
in Insight Orchestration. To resolve this issue, you must power off the virtual machine before
creating virtual machine management template from the virtual machine.
Action
Task for logical server
load average on the source server is greater than the threshold value.
Retry the operation later.
Failure message
The load average on the source or target VMHost may be too high. You can verify this issue by
examining the virtual machine management logfile at: C:\Program Files\HP\Virtual
Machine Management\log\hpvmmsvc.log
. Look for logging messages similar to the following.
If found, this indicates that the VMHost identified with the “Source server” tag has exceed the
allowable threshold and will result in a VM failing to deploy.
2009/07/29 08:31:02 | INFO - Source server 16.92.61.30 load average for
5 Minute -> 1.85
2009/07/29 08:31:02 | INFO - Source server 16.92.61.30 load average for
15 Minute -> 2.27
2009/07/29 08:31:02 | WARN - Source server 16.92.61.30 load average
exceeded the threshold
Possible cause
The memory and CPU shares that are allocated to the VMware Service Console may be increased
to obtain better performance on the VMHost. For more information, see
Service console memory and CPU shares”
Action
88
Troubleshooting