qemu / VNC / vino

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?
-- 
Nathanael

_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Big List of Linux Books]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux