On Tue, Jun 23, 2026 at 05:58:43PM +0000, Dr. David Alan Gilbert wrote: > * Daniel P. Berrangé ([email protected]) wrote: > > Add new docs for the `-object monitor-hmp` and `-object monitor-qmp` > > options, updating `-mon` to state that it is legacy syntax sugar > > for the new `-object` args. > > > > Signed-off-by: Daniel P. Berrangé <[email protected]> > > --- > > qemu-options.hx | 50 +++++++++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 50 insertions(+) > > > > diff --git a/qemu-options.hx b/qemu-options.hx > > index c799286153..98c74cc9ff 100644 > > --- a/qemu-options.hx > > +++ b/qemu-options.hx > > <snip> > > > @@ -5730,6 +5740,46 @@ SRST > > they are specified. Note that the 'id' property must be set. These > > objects are placed in the '/objects' path. > > > > + ``-object monitor-hmp,id=id,chardev=chardev_id,readline=on|off`` > > + Set up a monitor running the Human Monitor Protocol, > > + connected to the chardev ``chardev_id``. > > + > > + The ``id`` parameter is a unique ID that can be used > > + to dynamically delete the monitor at runtime. Note > > + that monitors created using the historical syntax > > + will be allocated IDs following the pattern ``hmpcompatNN``. > > + Mixing ``-object`` with the historical monitor syntax is > > + discouraged. > > + > > + The ``readline`` parameter, which defaults to ``on``, > > + controls whether the monitor provides interactive > > + prompts > > Missing full stop. > So are you allowing a mode that I don't think was previously possible; > HMP syntax but without readline?
Yeah, I guess that's true - the non-interactive mode was always there internally but only accessible via the gdb stub. > 'interactive prompts' seems a strange way of putting it - 'line editing' > is more normal isn't it? Sure, I can change that. 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 :|
