From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [PATCH 0/3] vnc: remove "change vnc TARGET" and QMP change command, support "-vnc help"
Date: Thu, 21 Jan 2021 10:52:04 +0000 [thread overview]
Message-ID: <20210121105204.GI3125227@redhat.com> (raw)
In-Reply-To: <20210121103831.pb22ib52z5g5onjq@sirius.home.kraxel.org>
On Thu, Jan 21, 2021 at 11:38:31AM +0100, Gerd Hoffmann wrote:
> On Wed, Jan 20, 2021 at 03:42:32PM +0100, Paolo Bonzini wrote:
> > The real driver for these patches is to send all QemuOpts user input
> > to qemu_opts_parse_noisily, for consistency in the command line
> > parsing code and to effectively outlaw "help" and "?" QemuOpts
> > suboptions. vnc_parse is the only function that is still using
> > qemu_opts_parse.
>
> Should we maybe move vnc to qapi cmd line parsing instead?
>
> > In order to remove the non-command-line callers of vnc_parse,
> > I am removing the deprecated QMP change command but also its HMP
> > veneer "change vnc TARGET", whose usecase is somewhat unclear to
> > me.
>
> Hmm. It's been a few years ...
>
> IIRC back when this was added the main use case was having a way to
> enable/disable the vnc server. Not sure this is still needed/useful.
> These days you can effectively disable vnc access by expiring the
> password (or not setting one in the first place) without re-configuring
> the vnc server. Also the race where qemu allowed passwordless connects
> between start and password being set via monitor is long gone.
Yep, it was my patch back here:
https://lists.gnu.org/archive/html/qemu-devel/2007-08/msg00151.html
The original justification or design was not especially compelling
and somewhat hackish in retrospect.
These days we really ought to change VNC so that it integrates with
"-object secret" for getting its password.
Being able to live add/remove display backends is somewhat
interesting, but if we want that it should be done generically
and use qapi modelling, and covering at least SPICE and VNC.
> So, all in all I feel a bit uncomfortable dropping this without the
> usual deprecation period. No strong objections though.
Well we did deprecate the "change" command in general in 2.5.0.
https://qemu.readthedocs.io/en/latest/system/deprecated.html#change-since-2-5-0
We gave illustrations for replacement for vnc password and CD
media change, but no replacement was provided for changing
VNC server config. That's ok though, as there's no requirement
that we provide a replacement when deprecating stuff. It would
have been nice if we explicitly mentioned we were dropping the
vnc target change funcitonality, but we have none the less
followed deprecation process for the 'change' command and so
can remove it now if desired.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-01-21 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 14:42 [PATCH 0/3] vnc: remove "change vnc TARGET" and QMP change command, support "-vnc help" Paolo Bonzini
2021-01-20 14:42 ` [PATCH 1/3] hmp: remove "change vnc TARGET" command Paolo Bonzini
2021-01-20 15:24 ` Eric Blake
2021-01-20 14:42 ` [PATCH 2/3] qmp: remove deprecated "change" command Paolo Bonzini
2021-01-20 15:21 ` Philippe Mathieu-Daudé
2021-01-20 15:31 ` Eric Blake
2021-01-20 14:42 ` [PATCH 3/3] vnc: support "-vnc help" Paolo Bonzini
2021-01-20 15:44 ` Eric Blake
2021-01-21 10:38 ` [PATCH 0/3] vnc: remove "change vnc TARGET" and QMP change command, " Gerd Hoffmann
2021-01-21 10:52 ` Daniel P. Berrangé [this message]
2021-01-21 11:13 ` Gerd Hoffmann
2021-01-21 12:02 ` Paolo Bonzini
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=20210121105204.GI3125227@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@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).