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.

This is fixed upstream by commit v0.6.0-40-ge214d6b

Will be fixed by rebase to 2.0

I can reproduce this issue with package:
virt-viewer-0.6.0-11.el6.x86_64

Steps to reproduce as bug Comment 0.


Then try to verify with new package:
virt-viewer-2.0-2.el6.x86_64

steps to verify this bug:
Env setup:
Prepare 2 hosts:

1.On host A(ip:10.66.7.91),prepare a vnc guest.

# virsh dumpxml s1-clone
     <graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'/>

2.On host B(ip:10.66.70.126), use virt-viewer --direct to launch the guest on host A

# virt-viewer --direct -c qemu+ssh://10.66.7.91/system s1-clone
root.7.91's password: 

Result: After input password for 1 time, guest can be connected and no error shows.

Tested the above steps for spice guest and get the same results, so move the bug to VERIFIED.

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/RHBA-2015-1322.html