On Wed, Jan 25, 2017 at 05:59:44PM +, Daniel P. Berrange wrote:
> On Wed, Jan 25, 2017 at 12:38:09PM -0500, Frediano Ziglio wrote:
> > >
> > > On Wed, Jan 25, 2017 at 12:23:35PM -0500, Frediano Ziglio wrote:
> > > > >
> > > > > When used with QEMU at least, both SPICE and VNC live in the
On Wed, Jan 25, 2017 at 12:38:09PM -0500, Frediano Ziglio wrote:
> >
> > On Wed, Jan 25, 2017 at 12:23:35PM -0500, Frediano Ziglio wrote:
> > > >
> > > > When used with QEMU at least, both SPICE and VNC live in the same port
> > > > range (5900+). It is thus not entirely uncommon for a user to
>
> On Wed, Jan 25, 2017 at 12:23:35PM -0500, Frediano Ziglio wrote:
> > >
> > > When used with QEMU at least, both SPICE and VNC live in the same port
> > > range (5900+). It is thus not entirely uncommon for a user to mistakenly
> > > connect to a SPICE server with a VNC client, or vica-verca.
On Wed, Jan 25, 2017 at 12:23:35PM -0500, Frediano Ziglio wrote:
> >
> > When used with QEMU at least, both SPICE and VNC live in the same port
> > range (5900+). It is thus not entirely uncommon for a user to mistakenly
> > connect to a SPICE server with a VNC client, or vica-verca.
> >
> >
When used with QEMU at least, both SPICE and VNC live in the same port
range (5900+). It is thus not entirely uncommon for a user to mistakenly
connect to a SPICE server with a VNC client, or vica-verca.
When connecting to VNC server with a SPICE client, you quickly get an
error. This is because
