From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] system: improve -mon deprecation warning
Date: Thu, 27 Aug 2026 11:37:16 +0100 [thread overview]
Message-ID: <apATXIypUEHy1mhh@redhat.com> (raw)
In-Reply-To: <95b7d9b3-b61b-448c-9fc3-a3d91d438a1b@oss.qualcomm.com>
On Thu, Aug 27, 2026 at 10:56:44AM +0200, Philippe Mathieu-Daudé wrote:
> On 24/8/26 14:29, Daniel P. Berrangé wrote:
> > Expand the text a bit to make the new syntax more explicit and point
> > users to the man page for further info.
> >
> > Reported-by: Peter Maydell <peter.maydell@linaro.org>
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > system/vl.c | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/system/vl.c b/system/vl.c
> > index 061cbdf860..d5b5392569 100644
> > --- a/system/vl.c
> > +++ b/system/vl.c
> > @@ -3239,8 +3239,11 @@ void qemu_init(int argc, char **argv)
> > default_monitor = 0;
> > break;
> > case QEMU_OPTION_mon:
> > - warn_report_once("'-mon' is deprecated, use '-object' with "
> > - "'monitor-hmp' or 'monitor-qmp' types instead");
> > + warn_report_once("'-mon' is deprecated. Switch to either "
> > + "'-object monitor-hmp,id=ID,chardev=CHR-ID' "
> > + "or '-object monitor-qmp,id=qmpNN,chardev=CHR-ID' "
> > + "instead. See '-object' docs in 'qemu(1)' for further "
> > + "configuration guidance.");
>
> Looking at commit 58b70f21ba6 ("docs: mark '-mon' as deprecated in
> favour of -object") I'm not sure this is a good idea to document
> '-object monitor-qmp' at all on CLI help. CLI users looking at
> help output are likely users of '-mon' for HMP. My 2 cents.
The warnings here get reported in machine use of QEMU too, not just
interactive usage. In libvirt they'll end up in
/var/log/libvirt/qemu/$GUEST.log.
I expect most end user non-managed launches of QEMU are using the
higher level -monitor for HMP, with -mon more likely machine usage.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-08-27 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 12:29 [PATCH] system: improve -mon deprecation warning Daniel P. Berrangé
2026-08-27 8:48 ` Peter Maydell
2026-08-27 10:39 ` Daniel P. Berrangé
2026-08-27 8:56 ` Philippe Mathieu-Daudé
2026-08-27 10:37 ` Daniel P. Berrangé [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=apATXIypUEHy1mhh@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@oss.qualcomm.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 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.