When Compute is configured to only set up VNC/SPICE servers on a specific network interface, the host's IP address is recorded in the libvirt guest XML. Previously, if the guest was migrated to a different host, the IP address of the source host remained in the guest XML and the guest failed to launch on the target host because the IP address was incorrect.
With this fix, the libvirt guest XML is now updated during migration to refer to the IP address of the target host. Migration can be performed for guests, even when the VNC/SPICE servers are configured to only bind to the IP address of a specific network interface.
Created attachment 1013929[details]
test steps
live migration is working both when explicitly specifying the host, and when letting the scheduler decide
This ticket has a mirror ticket on RHOS5-RHEL7 #1180600 which was verified.
As agreed we are moving this ticket to verify since on RHEL7 it is working correctly and we run automation on RHOS5-RHE6 with no issues found.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-0844.html
Created attachment 1013929 [details] test steps live migration is working both when explicitly specifying the host, and when letting the scheduler decide