Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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