Hi
On 2014-03-25 12:06, Nathanael D. Noblet wrote:
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.
You can change the default port which Vino listens on by changing the
value of the "alternative
On Tue, Mar 25, 2014 at 12:06:31PM -0600, Nathanael D. Noblet wrote:
> 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
On Tue, 2014-03-25 at 17:51 -0400, Cole Robinson wrote:
> 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
> some
On 03/25/2014 05:43 PM, Nathanael D. Noblet wrote:
> On Tue, 2014-03-25 at 18:24 +, 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/
On Tue, 2014-03-25 at 18:24 +, 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
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 th
On 03/25/2014 02:06 PM, 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
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-
