HP Insight Control Software for Linux - 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 Systems Insight Manager, run the Identify Systems task on the
virtual machine host from Options
→Identify Systems in Systems Insight Manager. If the virtual machine
was manually discovered in Systems Insight Manager using the IP address, then the virtual machine must be
deleted from the Systems Insight Manager All Systems page.
Transport operation fails after restarting virtual machine management
If you restart virtual machine management after initiating the transport operation, the transport operation
will fail. However, the result of the transport operation on the virtual machine host is hypervisor-dependent.
This might require removing 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, virtual machine management 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 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