Bug 816279
Summary: | virt-manager can't connect to remote guest with a listen= address | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Cole Robinson <crobinso> |
Component: | virt-manager | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | dallan, dyasny, gkong, jwu, mzhan, rwu, syeghiay, yupzhang, zpeng |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, virt-manager was not correctly using the graphics listen address attribute in the VM configuration, and would always try to connect to the guest with an SSH tunnel. This could break graphical console connections if listen= was set to an explicit interface address. virt-manager now properly connects to these addresses.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 12:39:46 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: |
Description
Cole Robinson
2012-04-25 17:12:43 UTC
Fixed in virt-manager-0.9.0-13.el6 According to the command 10 and 11, changed the status to VERIFIED. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously, virt-manager was not correctly using the graphics listen address attribute in the VM configuration, and would always try to connect to the guest with an SSH tunnel. This could break graphical console connections if listen= was set to an explicit interface address. virt-manager now properly connects to these addresses. 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. http://rhn.redhat.com/errata/RHBA-2012-0785.html |