From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: bleal@redhat.com, wainersm@redhat.com, f4bug@amsat.org,
crosa@redhat.com, eblake@redhat.com, armbru@redhat.com,
kraxel@redhat.com, berrange@redhat.com, vsementsov@virtuozzo.com,
marcandre.lureau@redhat.com
Subject: [PATCH v3 0/3] qapi/ui: change vnc addresses
Date: Tue, 18 Jan 2022 17:09:06 +0100 [thread overview]
Message-ID: <20220118160909.2502374-1-vsementsov@virtuozzo.com> (raw)
Hi all!
v3: - instead of creating new qmp command add an argument to existing
display-reload
- also don't touch websockets for now. I'm not sure we need it.
Additional argument for changing websockets may be added later on
demand
Recently our customer requested a possibility to change VNC listen port
dynamically.
Happily in Rhel7-based Qemu we already have this possibility: through
deprecated "change" qmp command.
But since 6.0 "change" qmp command was removed, with recommendation to
use change-vnc-password or blockdev-change-medium instead. Of course,
neither of them allow change VNC listen port.
So, let's reimplement the possibility.
Note: now, reconnecting may trigger existing deadlock, as I described
in my message "Re: [PULL 09/11] ui/vnc: clipboard support":
<973ddebe-14a9-4ba7-c389-7a97d6017237@virtuozzo.com>
Simple hack helps, but I'm not sure it's safe itself:
diff --git a/ui/vnc.c b/ui/vnc.c
index 69bbf3b6f6..8c6b378e2e 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -1354,12 +1354,12 @@ void vnc_disconnect_finish(VncState *vs)
/* last client gone */
vnc_update_server_surface(vs->vd);
}
+ vnc_unlock_output(vs);
+
if (vs->cbpeer.update.notify) {
qemu_clipboard_peer_unregister(&vs->cbpeer);
}
- vnc_unlock_output(vs);
-
qemu_mutex_destroy(&vs->output_mutex);
if (vs->bh != NULL) {
qemu_bh_delete(vs->bh);
Vladimir Sementsov-Ogievskiy (3):
ui/vnc: refactor arrays of addresses to SocketAddressList
qapi/ui: display-reload: add possibility to change listen address
avocado/vnc: add test_change_listen
docs/about/removed-features.rst | 3 +-
qapi/ui.json | 6 +-
include/ui/console.h | 2 +-
monitor/qmp-cmds.c | 4 +-
ui/vnc.c | 166 ++++++++++++++++----------------
tests/avocado/vnc.py | 10 ++
6 files changed, 100 insertions(+), 91 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-18 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 16:09 Vladimir Sementsov-Ogievskiy [this message]
2022-01-18 16:09 ` [PATCH v3 1/3] ui/vnc: refactor arrays of addresses to SocketAddressList Vladimir Sementsov-Ogievskiy
2022-02-09 18:22 ` Daniel P. Berrangé
2022-01-18 16:09 ` [PATCH v3 2/3] qapi/ui: display-reload: add possibility to change listen address Vladimir Sementsov-Ogievskiy
2022-02-09 18:33 ` Daniel P. Berrangé
2022-02-10 9:39 ` Vladimir Sementsov-Ogievskiy
2022-01-18 16:09 ` [PATCH v3 3/3] avocado/vnc: add test_change_listen Vladimir Sementsov-Ogievskiy
2022-02-09 18:38 ` Daniel P. Berrangé
2022-02-09 16:55 ` [PATCH v3 0/3] qapi/ui: change vnc addresses Vladimir Sementsov-Ogievskiy
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=20220118160909.2502374-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
/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).