HP Insight Control Virtual Machine Management 7.3 User Guide

Virtual machine devices might not be available after a copy or move
Reconfigure the virtual network connections on the moved or copied virtual machine guest.
Launching the remote console from VMM console might fail
All virtual machine host port numbers are changed when you modify the configuration setting.
Verify the installation of VMware Management Interface software, indicated by the presence of
the VMware Management Interface directory within the VMware installation directory. For
information, see the VMware Knowledge Base Answer ID 793 at http://www.vmware.com/
support/kb.
Also, verify that the Web port is 8222, the default port. If it is not, update the Web port in VMM
configuration setting:
1. In the C:\Program Files\HP\VMM\bin directory, locate the hpvmm.conf file.
2. Modify the port number specified in the VMwaregsxport to the default port.
3. Save the file, and then restart VMM services.
• VMware ESX Server—Verify that the VMware ESX Server Web port is 80, the default port. If
it is not, then update the Web port in VMM configuration setting:
1. In the C:\Program Files\HP\VMM\bin directory, locate the hpvmm.conf file.
2. Modify the port number specified in the VMwareesxport to the default port.
3. Save the file, and then restart VMM services.
Insight Control virtual machine management does not display the Quick Move option
for HA-configured Microsoft Hyper-V server virtual machines in the Move wizard
Ensure the HA-configured Microsoft Hyper-V server virtual machine is listed in the Microsoft Failover
Cluster Management tool.
Check whether domain credentials are provided in system sign-in credentials of the HP SIM
credentials settings, and the Microsoft Hyper-V server host is registered properly. If the credentials
are not entered, enter them in the system sign-in credentials of the HP SIM credentials settings and
reregister the Microsoft Hyper-V server host.
Virtual machine cannot be made highly available unless all the VM files reside on
Cluster Shared Volume (CSV).
If a VM is added to a failover cluster manager directly from the Hyper V host, the VM can be made
highly available. But, if the VM files are on a non-CSV path and the related VM is added from the
Hyper V host, a warning is displayed.
To make the VM highly available from VMM, all the VM files must reside on CSV.
VM status of the already registered vCenter in all Systems page temporarily becomes
critical
If a server is already registered with VMM as a vCenter server and the same is also tried to register
as an SCVMM server with VMM, and if SCVMM is not installed on the server, then the VM status
of the vCenter in the All Systems page temporarily shows critical for some time. After a while,
it returns to the original status. However, the status of the VME server is correct in the View VME
Settings page.
Empty folders are created when deploy template operation fails for SCVMM HA
template on a standalone HyperV host
MS SCVMM does not allow HA-enabled template to deploy on a standalone HyperV host. An
attempt to deploy HA-enabled template using HP VMM causes deployment failure. It creates an
empty folder on the target host at the destination location.
Insight Control virtual machine management functions 35