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:
virt-viewer connect to the remote guest with address=0.0.0.0 need twice authorization.
Version-Release number of selected component (if applicable):
virt-viewer-0.5.2-6.el6.x86_64
libvirt-0.9.10-16.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. prepared local host and remote host.
2. prepared a remote guest with address=0.0.0.0
# virsh dumpxml T1
...
<graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
</graphics>
...
3. logon on local host, lauch virt-viewer to connect the remote guest.
# virt-viewer -c qemu+ssh://10.66.5.65/system T1
root.5.65's password:
root.5.65's password:
4. through twice authorization, virt-viewer display the remote guest.
Actual results
As above
Expected results
virt-viewer can display the remote guest with address=0.0.0.0 by only once authorization.
You need to authenticate once to connect to libvirt & once to connect to VNC since you requested SSH tunnelling.
If you want to avoid the SSH tunnelling for VNC, then pass the '--direct' flag.
Description of problem: virt-viewer connect to the remote guest with address=0.0.0.0 need twice authorization. Version-Release number of selected component (if applicable): virt-viewer-0.5.2-6.el6.x86_64 libvirt-0.9.10-16.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepared local host and remote host. 2. prepared a remote guest with address=0.0.0.0 # virsh dumpxml T1 ... <graphics type='vnc' port='5900' autoport='yes' listen='0.0.0.0'> <listen type='address' address='0.0.0.0'/> </graphics> ... 3. logon on local host, lauch virt-viewer to connect the remote guest. # virt-viewer -c qemu+ssh://10.66.5.65/system T1 root.5.65's password: root.5.65's password: 4. through twice authorization, virt-viewer display the remote guest. Actual results As above Expected results virt-viewer can display the remote guest with address=0.0.0.0 by only once authorization.