HP Matrix Operating Environment Software - Manual (Page 207)

Provisioning virtual machine failed with a VM must be powered off for customization error message
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 fails 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 infrastructure Action
orchestration. To resolve this issue, power off the virtual machine before creating virtual machine
management template from the virtual machine.
Provisioned VMs fail due to improper VM Host hardware configuration
Provisioned VMs fail due to improper VM Host hardware configuration. The customization of the
provisioned VMs fail and the HP Matrix infrastructure orchestration service request fails. Issue
Virtual network manager fails to load during rapid provisioning of VMs on ProLiant servers with
Microsoft Hyper-V 2008 R2 SP1/SP2. The following error message is displayed:
Task for logical server has failed, failure virtual machine hardware
was not configured correctly.
Possible cause
Action 1. Install HP NCU 10.10. See HP Network Configuration Utility for Windows Server 2008 R2 for
installation instructions.
2. Enable the TCP offload feature in the Hyper-V host.
• Access the Network Adapter Properties window for the VM Host.
• Click the Advanced tab.
• Select the TCP offload options in the Property list and select Enable as the Value.
• Click OK.
VM Host server blade is not returned to server pool as Unused when VM Host service is deleted
VM Host server blade is not returned to server pool as Unused when VM Host service is deleted.
The server blade remains marked as an In-Use VM Host, and is not available for other deployments. Issue
The VM Host HP Matrix infrastructure orchestration service was deleted without first unregistering
the VM Host from Insight Control virtual machine management. Possible cause
Use the Insight Control virtual machine management client API to unregister the VM Host. Action
1. Login:
..\Program Files\HP\Insight Control virtual machine
management\clientapi\bin>adminlogin
2. Unregister the VM Host:
..\Program Files\HP\Insight Control virtual machine
management\clientapi\bin>cli unregisterAgent -host <VM_host_IP_address>
3. Retrieve the list of IP addresses registered as VM Hosts:
..\Program Files\HP\Insight Control virtual machine
management\clientapi\bin>cli getHostIds
4. Verify that the VM Host IP address is no longer listed.
Service creation 207