From: Ali Shirvani via <qemu-devel@nongnu.org>
The mode=control argument configures a QMP monitor.
Signed-off-by: Ali Shirvani <alis...@routerhosting.com>
Reviewed-by: Stefan Hajnoczi <stefa...@redhat.com>
Message-Id:
<0799f0de89ad2482672b5d61d0de61e6eba782da.1621407918.git.alis...@routerhosting.com>
Signed-off-by: Paolo Bonzini <pbonz...@redhat.com>
---
qemu-options.hx | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 8116f79818..14258784b3 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -3799,8 +3799,11 @@ DEF("mon", HAS_ARG, QEMU_OPTION_mon, \
"-mon [chardev=]name[,mode=readline|control][,pretty[=on|off]]\n",
QEMU_ARCH_ALL)
SRST
``-mon [chardev=]name[,mode=readline|control][,pretty[=on|off]]``
- Setup monitor on chardev name. ``pretty`` is only valid when
- ``mode=control``, turning on JSON pretty printing to ease
+ Setup monitor on chardev name. ``mode=control`` configures
+ a QMP monitor (a JSON RPC-style protocol) and it is not the
+ same as HMP, the human monitor that has a "(qemu)" prompt.
+ ``pretty`` is only valid when ``mode=control``,
+ turning on JSON pretty printing to ease
human reading and debugging.
ERST
--
2.31.1
