HP Insight Control Software for Linux User Manual
Page 32
Error message Unknown to VMM appears when performing the copy operation on
a virtual machine
If the error message Unknown to VMM appears when performing the copy operation on a virtual
machine, ensure that the virtual machine exists on the host. If the virtual machine has been deleted
from the host, but the virtual machine node is still present in HP SIM, click Options
→Identify Systems
in the host HP SIM. If the virtual machine was manually discovered in HP SIM through the IP address,
the virtual machine must be deleted from the HP SIM All Systems page.
Restarting the VMM service while any guest VM lifecycle operation or guest VM
movements across hosts is in progress will result in failure
If you restart VMM service after initiating a guest VM lifecycle operation or guest VM movements
across hosts, the operation fails and displays the following error message : Communication
has been lost with the HP VMM service. Check if the HP VMM service is
running
. However, the result of the operation on the virtual machine is hypervisor dependent
and may succeed. If you encounter a failure from both VMM and from the hypervisor end, you
may need to manually remove the unwanted resources such, as virtual machine files and disks, on
the hypervisor.
Copied or moved Xen virtual machine guest does not start on the destination host
When a Xen virtual machine guest is copied or moved to another host, VMM attempts to convert
the Xen bridge of the guest to match a bridge present on the destination. When trying to start the
virtual machine guest, the following error appears on the console:
Error: Device 0 (vif) could not be connected. Could not find bridge
device xenbr<#>
To resolve this issue, modify the configuration of the virtual machine guest to use an existing Xen
bridge on the destination system.
1.
List the existing bridges on the destination host by using the command brctl show. If no
Xen bridges are created, create one with the /etc/xen/scripts/network-bridge script.
For example: /etc/xen/scripts/network-bridge start netdev=eth0 vifnum=0
2.
Dump the Xen virtual machine guest XML configuration to a file:virsh dumpxml
GUEST_NAME > guest.xml
3.
Undefine the Xen virtual machine guest on the system: virsh undefine GUEST_NAME
4.
Modify the Xen bridge in the configuration by editing the <source bridge=> XML tag.
5.
Redefine the Xen virtual machine guest on the system: virsh define guest.xml
6.
Start the Xen virtual machine guest.
Virtual machine host prefailure even handling does not progress
For VMware ESX 4.x , ESXi 4.x or VMware ESXi 5.x hosts, when Deploy
→Virtual Machine→Handle
VM Host Prefailure Events is selected, the virtual machine host is placed into maintenance mode
in vCenter Server. To enter maintenance mode, all virtual machines must be powered down or
migrated to other virtual machine hosts. Manual intervention might be required to complete this
task.
HTTP ERROR: 500 Internal Server Error
message appears during a VMM
move or copy operation
This error can occur when the network is busy during the move or copy operation.
To resolve this issue, refresh the browser window.
32
Troubleshooting