[Qemu-devel] [Bug 1388735] Re: QEMU no longer allows to use full TCP port range for VNC

[Michael Tokarev]

I disagree.  This is a vnc port number, and by definition it can't
really be negative.  The fact that some vnc software allows negative
port like this, or that some software uses tcp port number in place of
vnc port number, does not make it more valid.

We're talking about an issue in original vnc specification, -- maybe
they should have used tcp port in the first place.

And yes, this way we can't specify tcp port less than 5900.

In order to solve this issue for real, I think the best way is to allow
specifying tcp port somehow.  How does other vnc software deal with
this?  One example I can think of is to use double-semicolon syntax,
like this: -vnc ::443.  But we should just agree on some common way,
already used by other vnc software.

What is in use today?

Thanks,

/mjt

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1388735

Title:
  QEMU no longer allows to use full TCP port range for VNC

Status in QEMU:
  New

Bug description:
  After upgrade to QEMU version 2.1.0 (Debian 2.1+dfsg-4ubuntu6), I am no 
longer able to use any TCP port for VNC display.
  For example, if I need to assign VNC server a TCP port 443, I used to run:
  # qemu-system-x86_64 -vnc :-5457
  qemu-system-x86_64: Failed to start VNC server on `:-1000': can't convert to 
a number:-5457
  expected behavior: as any VNC software, take port base of 5900, substract 
5457 display number, and use TCP port 443

  I ask to change vnc port conversion routine to allow input values in
  range of all TCP ports, from 1 to 65535.

  I really depend on ability to use full TCP range for VNC port numbers,
  and inablity to do so in new version of QEMU is very disappointing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1388735/+subscriptions