From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, Eric Blake <eblake@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH v3 0/8] Support multiple listening sockets per VNC server
Date: Fri, 3 Feb 2017 12:06:41 +0000 [thread overview]
Message-ID: <20170203120649.15637-1-berrange@redhat.com> (raw)
Followup to
v2: https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg04951.html
There are two core feature changes in this series
- If a DNS name resolves to multiple distinct IP addresses,
the VNC server is now able to listen on all of them
- The -vnc argument syntax is extended to allow the 'vnc'
and 'websocket' arguments to be listed multiple times.
This allows a single VNC server to listen on multiple
different names / addresses.
The io/ patch series that this previously depended on is now merged
in git master.
Changed in v3:
- Resolve conflicts with master for qapi schema
- Remove left-over debug statement (Eric)
Changed in v2:
- Fix qapi version annotation (Eric)
- Fix misc typos in docs/commit message (Eric)
- Replace qemu_opt_get_all() with generic QemuOpt iterator API
to avoid needless mem allocations
Daniel P. Berrange (8):
ui: fix regression handling bare 'websocket' option to -vnc
ui: fix reporting of VNC auth in query-vnc-servers
ui: refactor VncDisplay to allow multiple listening sockets
ui: refactor code for populating SocketAddress from vnc_display_open
ui: extract code to connect/listen from vnc_display_open
ui: let VNC server listen on all resolved IP addresses
util: add iterators for QemuOpts values
ui: add ability to specify multiple VNC listen addresses
include/qemu/option.h | 9 +
qapi-schema.json | 28 ++-
qemu-options.hx | 12 +-
ui/vnc.c | 655 +++++++++++++++++++++++++++++++++++---------------
ui/vnc.h | 10 +-
util/qemu-option.c | 19 ++
6 files changed, 531 insertions(+), 202 deletions(-)
--
2.9.3
next reply other threads:[~2017-02-03 12:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 12:06 Daniel P. Berrange [this message]
2017-02-03 12:06 ` [Qemu-devel] [PATCH v3 1/8] ui: fix regression handling bare 'websocket' option to -vnc Daniel P. Berrange
2017-02-03 12:06 ` [Qemu-devel] [PATCH v3 2/8] ui: fix reporting of VNC auth in query-vnc-servers Daniel P. Berrange
2017-02-03 12:06 ` [Qemu-devel] [PATCH v3 3/8] ui: refactor VncDisplay to allow multiple listening sockets Daniel P. Berrange
2017-02-03 12:06 ` [Qemu-devel] [PATCH v3 4/8] ui: refactor code for populating SocketAddress from vnc_display_open Daniel P. Berrange
2017-02-03 12:06 ` [Qemu-devel] [PATCH v3 5/8] ui: extract code to connect/listen " Daniel P. Berrange
2017-02-03 12:06 ` [Qemu-devel] [PATCH v3 6/8] ui: let VNC server listen on all resolved IP addresses Daniel P. Berrange
2017-02-03 12:06 ` [Qemu-devel] [PATCH v3 7/8] util: add iterators for QemuOpts values Daniel P. Berrange
2017-02-03 12:06 ` [Qemu-devel] [PATCH v3 8/8] ui: add ability to specify multiple VNC listen addresses Daniel P. Berrange
2017-02-03 13:29 ` [Qemu-devel] [PATCH v3 0/8] Support multiple listening sockets per VNC server Michael Tokarev
2017-02-03 13:41 ` Daniel P. Berrange
2017-02-06 14:27 ` Gerd Hoffmann
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=20170203120649.15637-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).