qemu / VNC / vino
crobinso at redhat.com
Tue Mar 25 18:09:04 UTC 2014
On 03/25/2014 02:06 PM, Nathanael D. Noblet wrote:
> 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
> Thoughts? What should I look at/report?
On Fedora 20, /etc/libvirt/qemu.conf allows you to set a port range that
libvirt will allocate for VMs. You can use that to avoid the vino collision.
More information about the cloud