Bug 1038963
| Summary: | [RFE] qemu can't listen on both IPv6 and IPv4 localhost for VNC | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Ján Tomko <jtomko> | |
| Component: | qemu-kvm-rhev | Assignee: | Gerd Hoffmann <kraxel> | |
| Status: | CLOSED ERRATA | QA Contact: | Guo, Zhiyi <zhguo> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.0 | CC: | berrange, chayang, hhuang, huding, jinzhao, jtomko, juzhang, kraxel, michen, mrezanin, mtessun, nyechiel, rbalakri, virt-maint | |
| Target Milestone: | rc | Keywords: | FutureFeature | |
| Target Release: | 7.4 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | qemu-kvm-rhev-2.9.0-1.el7 | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1014422 | |||
| : | 1038965 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-01 23:27:12 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: | ||||
| Bug Blocks: | 1038965, 1083896 | |||
|
Description
Ján Tomko
2013-12-06 09:07:35 UTC
Not going to happen for 7.0. As correctly stated above IPV6_V6ONLY=0 can only be used with the wildcard address. So fixing this implies going from a single listening socket to multiple listening sockets, one for 127.0.0.1:$port and one for [::1]:$port. Which is a non-trivial change inside qemu and it also has implications for the external interfaces. 'info vnc' monitor command will have to report multiple listening addresses then for example. Daniel? I remember we discussed that, but I think iochannels don't support listening on two file handles (one v4, one v6), correct? Yeah, that's correct - I had a plan to introduce a separate generic abstraction for representing a network service with multiple independent socket listeners & multiple clients which we could reuse in all areas of qemu with this need. Fix depends on getting these two series into qemu 2.9: https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg00574.html https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg00582.html The first series is pretty much ready. The second series needs a bit more work It is doable for 2.9 as long as no unexpected hurdles appear. > https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg00574.html
> https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg00582.html
Patches are in, yay!
upstream commit 396f935a9aff3cefd288bdb2b20024fb9dcfa062 & parents
Test against qemu-kvm-rhev-2.8.0-6.el7.x86_64, start qemu and check port qemu-kvm listened:
# /usr/libexec/qemu-kvm -monitor stdio
QEMU 2.8.0 monitor - type 'help' for more information
(qemu) info vnc
Server:
address: ::1:5900
auth: none
Client: none
# netstat -tnap | grep qemu
tcp6 0 0 ::1:5900 :::* LISTEN 2433/qemu-kvm
Follow same steps against qemu-kvm-rhev-2.9.0-1.el7.x86_64
# /usr/libexec/qemu-kvm -monitor stdio
QEMU 2.9.0 monitor - type 'help' for more information
(qemu) VNC server running on ::1:5900
(qemu) info vnc
Server:
address: ::1:5900
auth: none
Client: none
# netstat -tnap | grep qemu
tcp 0 0 127.0.0.1:5900 0.0.0.0:* LISTEN 2076/qemu-kvm
tcp6 0 0 ::1:5900 :::* LISTEN 2076/qemu-kvm
Hi Gerd, Can you comment whether this bug is verified per comment 19? Many thanks! BR/ Guo, Zhiyi > Can you comment whether this bug is verified per comment 19? Many thanks!
Looks good.
Verified per comment 19 & 21 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://access.redhat.com/errata/RHSA-2017:2392 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://access.redhat.com/errata/RHSA-2017:2392 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://access.redhat.com/errata/RHSA-2017:2392 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://access.redhat.com/errata/RHSA-2017:2392 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://access.redhat.com/errata/RHSA-2017:2392 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://access.redhat.com/errata/RHSA-2017:2392 |