Bug 772290
| Summary: | RFE: Configurable VNC start port or ability to exclude use of specific ports | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Alex Williamson <alex.williamson> |
| Component: | libvirt | Assignee: | Martin Kletzander <mkletzan> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3 | CC: | acathrow, berrange, clalancette, crobinso, dallan, dougsland, dyasny, dyuan, itamar, jforbes, kparal, laine, libvirt-maint, mzhan, rwu, veillard, virt-maint, ydu, zpeng |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-0.10.2-0rc1.el6 | Doc Type: | Enhancement |
| Doc Text: |
Feature:
Starting port for SPICE/VNC port allocations was made configurable.
Reason:
By default the automatically allocated ports for SPICE/VNC started on port 5900 which wasn't always wanted.
Result (if any):
Guests can have SPICE/VNC on other ports than 5900 without explicitly specifying them, thus keeping the automatic allocation in place.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 07:07:38 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Alex Williamson
2012-01-06 17:16:39 UTC
It wouldn't be a big deal to extend the <listen> element to supply a list of ports to exclude, although maybe there's a better way to do it that I'm not thinking of atm. *** Bug 782814 has been marked as a duplicate of this bug. *** I don't think that the <listen> element should have a range of ports - apps would just have to end up specifying the same range over & over in every guest. This is something that should be configurable in the global qemu.conf file. *** Bug 782814 has been marked as a duplicate of this bug. *** Bug 782814, which has been marked as a duplicate of this bug, asks libvirt developers to change the default port 5900 to some other port. That would also solve some other bugs. Read the bug description for more details. (In reply to comment #3) > I don't think that the <listen> element should have a range of ports - apps > would just have to end up specifying the same range over & over in every guest. > This is something that should be configurable in the global qemu.conf file. I've pretty much only heard people asking for XML; I'm fine with a global config option, but I think we should provide both. Patches are waiting for review upstream. For reference (since someone asked me about this issue) this is the latest rev of the patches I see upstream: https://www.redhat.com/archives/libvir-list/2012-August/msg00807.html Actually, only one patch is missing review (last minor changes to the patch were added after Daniel's proposal): https://www.redhat.com/archives/libvir-list/2012-August/msg00930.html Default start port for both VNC and SPICE is now configurable in /etc/libvirt/qemu.conf, thus moving to POST (based on these commits):
commit a14b4aea512d6c3a42af56207a65ef10ac4a12a1
Author: Martin Kletzander <mkletzan>
Date: Mon Jun 18 09:58:31 2012 +0200
qemu: Unify port-wise SPICE and VNC behavior
commit 29226beefe2ae9698443b5ebe9d94df64c94c923
Author: Martin Kletzander <mkletzan>
Date: Mon Jun 18 10:22:07 2012 +0200
qemu: configurable remote display port boundaries
Has the default VNC port changed? Not yet. It most probably will, but because this is very sensitive issue for some people, it hasn't happened yet. However that shouldn't be a problem for this bug to be solved. Thanks. In that case I'm reopening bug 782814. So sorry Martin, it works now, maybe my pc have some problem, thanks.
verify with build: libvirt-0.10.2-0rc1.el6.x86_64
step:
1. edit /etc/libvirt/qemu.conf
....
remote_display_port_min = 5904
remote_display_port_max = 65535
....
and start the guest with:
.....
<graphics type='vnc' port='-1' autoport='yes'/>
.....
when guest started, check vnc port:
#virsh dumpxml $guest
.......
<graphics type='spice' port='5904' autoport='yes' listen='0.0.0.0'>
<listen type='address' address='0.0.0.0'/>
check ports:
#netstat -apn| grep 590
tcp 0 0 127.0.0.1:5904 0.0.0.0:* LISTEN 17849/qemu-kvm
tcp 0 0 0.0.0.0:5905 0.0.0.0:* LISTEN 17988/qemu-kvm
tcp 0 0 :::5901 :::* LISTEN 3175/vino-server
the start port become to 5904. verification passed.
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/RHSA-2013-0276.html |