qemu / VNC / vino

Cole Robinson crobinso at redhat.com
Tue Mar 25 21:51:50 UTC 2014


On 03/25/2014 05:43 PM, Nathanael D. Noblet wrote:
> On Tue, 2014-03-25 at 18:24 +0000, Daniel P. Berrange wrote:
> 
>> In /etc/libvirt/qemu.conf you can set  remote_display_port_{min,max}
>> to control the port range used
> 
> So that is awesome thank you. 
> 
> Given that by default virt-manager/libvirt/qemu listens to
> 127.0.0.0:PORT as opposed to 0.0.0.0:PORT. Should this be filed as a
> bug? As in could the default port qemu started on be 6900 instead of
> 5900 so that this doesn't happen? I realize that 5900 is the standard
> vnc port... I'm just wondering if there is a use case where changing
> that config breaks anything?
> 

There was a bug about that in the past, but we rejected changing the default
range. Libvirt and xen and qemu have all used the assumption of starting at
port 5900 for too long, we didn't want to deal with any potential fallout for
something that affects a small number of users, and that nowadays has a manual
workaround.

vino could always be extended to try a little harder/smarter to find a free
port, which libvirt has done for years.

- Cole


More information about the cloud mailing list