qemu / VNC / vino

Daniel P. Berrange berrange at redhat.com
Tue Mar 25 18:24:33 UTC 2014

On Tue, Mar 25, 2014 at 12:06:31PM -0600, Nathanael D. Noblet wrote:
> Hello,
>   So I've found a 'bug'. I have a group of developers who use
> vagrant/libvirt to develop against. We use VNC since we are a
> distributed team to connect to each other's desktops/workstations for
> when we're at the 'huh this makes no sense'.
>   If libvirt/qemu-system-x86_64 starts before vino-server (which is
> common since we don't leave the vnc access on all the time). Then vino
> only listens on ipv6 instead of ipv4 and ipv6. At that point no one can
> connect to the workstation over vnc since we are all ipv4 connected.
>   I'm not sure where the bug is and it isn't really a big bug as much as
> I need to be able to tell either vino or qemu-system-x what ports to
> use. 
>   Thoughts? What should I look at/report?

In /etc/libvirt/qemu.conf you can set  remote_display_port_{min,max}
to control the port range used

|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

More information about the cloud mailing list