Bug 1085210
| Summary: | virt-viewer --direct fails to connect to remote guest configured with listen="0.0.0.0" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | tingting zheng <tzheng> |
| Component: | virt-viewer | Assignee: | Virt Viewer Maint <virt-viewer-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.6 | CC: | cfergeau, dblechte, dyuan, jjongsma, juzhou, marcandre.lureau, mzhan, rbalakri |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-viewer-2.0-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
No doc needed
|
Story Points: | --- |
| Clone Of: | 1079211 | Environment: | |
| Last Closed: | 2015-07-22 06:31:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1079211, 1179477 | ||
| Bug Blocks: | |||
|
Comment 2
Christophe Fergeau
2014-09-12 13:59:37 UTC
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 |