mirror of https://github.com/proxmox/mirror_qemu
![]() # By Tomoki Sekiyama (10) and Paul Burton (1) # Via Michael Roth * mdroth/qga-pull-2013-9-9: QMP/qemu-ga-client: Make timeout longer for guest-fsfreeze-freeze command qemu-ga: Install Windows VSS provider on `qemu-ga -s install' qemu-ga: Call Windows VSS requester in fsfreeze command handler qemu-ga: Add Windows VSS provider and requester as DLL error: Add error_set_win32 and error_setg_win32 qemu-ga: Add configure options to specify path to Windows/VSS SDK Add a script to extract VSS SDK headers on POSIX system checkpatch.pl: Check .cpp files Add c++ keywords to QAPI helper script configure: Support configuring C++ compiler mips_malta: support up to 2GiB RAM Message-id: 1378755701-2051-1-git-send-email-mdroth@linux.vnet.ibm.com Signed-off-by: Anthony Liguori <anthony@codemonkey.ws> |
||
---|---|---|
.. | ||
README | ||
qemu-ga-client | ||
qmp | ||
qmp-events.txt | ||
qmp-shell | ||
qmp-spec.txt | ||
qmp.py | ||
qom-fuse | ||
qom-get | ||
qom-list | ||
qom-set |
README
QEMU Monitor Protocol ===================== Introduction ------------- The QEMU Monitor Protocol (QMP) allows applications to communicate with QEMU's Monitor. QMP is JSON[1] based and currently has the following features: - Lightweight, text-based, easy to parse data format - Asynchronous messages support (ie. events) - Capabilities Negotiation For detailed information on QMP's usage, please, refer to the following files: o qmp-spec.txt QEMU Monitor Protocol current specification o qmp-commands.txt QMP supported commands (auto-generated at build-time) o qmp-events.txt List of available asynchronous events There is also a simple Python script called 'qmp-shell' available. IMPORTANT: It's strongly recommended to read the 'Stability Considerations' section in the qmp-commands.txt file before making any serious use of QMP. [1] http://www.json.org Usage ----- To enable QMP, you need a QEMU monitor instance in "control mode". There are two ways of doing this. The simplest one is using the '-qmp' command-line option. The following example makes QMP available on localhost port 4444: $ qemu [...] -qmp tcp:localhost:4444,server However, in order to have more complex combinations, like multiple monitors, the '-mon' command-line option should be used along with the '-chardev' one. For instance, the following example creates one user monitor on stdio and one QMP monitor on localhost port 4444. $ qemu [...] -chardev stdio,id=mon0 -mon chardev=mon0,mode=readline \ -chardev socket,id=mon1,host=localhost,port=4444,server \ -mon chardev=mon1,mode=control Please, refer to QEMU's manpage for more information. Simple Testing -------------- To manually test QMP one can connect with telnet and issue commands by hand: $ telnet localhost 4444 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. {"QMP": {"version": {"qemu": {"micro": 50, "minor": 13, "major": 0}, "package": ""}, "capabilities": []}} { "execute": "qmp_capabilities" } {"return": {}} { "execute": "query-version" } {"return": {"qemu": {"micro": 50, "minor": 13, "major": 0}, "package": ""}} Development Process ------------------- When changing QMP's interface (by adding new commands, events or modifying existing ones) it's mandatory to update the relevant documentation, which is one (or more) of the files listed in the 'Introduction' section*. Also, it's strongly recommended to send the documentation patch first, before doing any code change. This is so because: 1. Avoids the code dictating the interface 2. Review can improve your interface. Letting that happen before you implement it can save you work. * The qmp-commands.txt file is generated from the qmp-commands.hx one, which is the file that should be edited. Homepage -------- http://wiki.qemu.org/QMP