All of lore.kernel.org
 help / color / mirror / Atom feed
From: Launchpad Bug Tracker <1388735@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1388735] Re: QEMU no longer allows to use full TCP port range for VNC
Date: Tue, 22 Jun 2021 04:17:25 -0000	[thread overview]
Message-ID: <162433544590.20423.5653406776405997248.malone@loganberry.canonical.com> (raw)
In-Reply-To: 20141103075552.9513.99504.malonedeb@chaenomeles.canonical.com

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
       Status: Incomplete => Expired

-- 
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:
  Expired

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


      parent reply	other threads:[~2021-06-22  5:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  7:55 [Qemu-devel] [Bug 1388735] [NEW] QEMU no longer allows to use full TCP port range for VNC Sergey
2014-11-03  9:08 ` [Qemu-devel] [Bug 1388735] " Michael Tokarev
2014-11-03 11:00 ` Sergey
2021-04-22  4:33 ` Thomas Huth
2021-06-22  4:17 ` Launchpad Bug Tracker [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162433544590.20423.5653406776405997248.malone@loganberry.canonical.com \
    --to=1388735@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.