Description of problem:
currently, two uris can be given to libvirt as migrate command options: dst libvirt uri ("desturi") and where qemu listens for incoming migration (migrateuri). This is not sufficient in more complex topologies (with proxies involved) where host name/ip/port/sport as seen by libvirt may not match the one seen by the client.
remote-viewer already uses spice:// uris but the code handling them resides in spice-gtk library and uses glib functions heavily: http://cgit.freedesktop.org/spice/spice-gtk/tree/gtk/spice-session.c?id=fcbbc248a8f885f9a9a6e7c47d7aae0c1ab3cd1b#n245
Version-Release number of selected component (if applicable):
libvirt-0.10.2-10.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. misconfigure hostname on destination host (in /etc/sysconfig/hostname; reboot)
2. connect to the libvirt VM from any other host than destination host
3. migrate the VM using virsh migrate command with an option to give client correct dst host address
Actual results:
address can not be given, client fails to connect to dst host
Expected results:
address can be given, client connects to dst host and client console survives migration.
Additional info:
Virt "Display address override" feature depends on this RFE: http://wiki.ovirt.org/Features/Display_Address_Override
Description of problem: currently, two uris can be given to libvirt as migrate command options: dst libvirt uri ("desturi") and where qemu listens for incoming migration (migrateuri). This is not sufficient in more complex topologies (with proxies involved) where host name/ip/port/sport as seen by libvirt may not match the one seen by the client. remote-viewer already uses spice:// uris but the code handling them resides in spice-gtk library and uses glib functions heavily: http://cgit.freedesktop.org/spice/spice-gtk/tree/gtk/spice-session.c?id=fcbbc248a8f885f9a9a6e7c47d7aae0c1ab3cd1b#n245 Version-Release number of selected component (if applicable): libvirt-0.10.2-10.el6.x86_64 How reproducible: always Steps to Reproduce: 1. misconfigure hostname on destination host (in /etc/sysconfig/hostname; reboot) 2. connect to the libvirt VM from any other host than destination host 3. migrate the VM using virsh migrate command with an option to give client correct dst host address Actual results: address can not be given, client fails to connect to dst host Expected results: address can be given, client connects to dst host and client console survives migration. Additional info: Virt "Display address override" feature depends on this RFE: http://wiki.ovirt.org/Features/Display_Address_Override