MonitorProtocol: Difference between revisions
No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
* Error framework ('''under discussion''') | * Error framework ('''under discussion''') | ||
=== Command handlers | === Command handlers conversion work === | ||
* Input through QDict ('''merged''') | * Input through QDict ('''merged''') | ||
| Line 37: | Line 37: | ||
* Error handling ('''not started''') | * Error handling ('''not started''') | ||
== | == Libqmp == | ||
Although this is still under discussion, we are also going to provide a C library with a stable ABI. | Although this is still under discussion, we are also going to provide a C library with a stable ABI. | ||
| Line 51: | Line 51: | ||
http://repo.or.cz/w/qemu/qmp-unstable.git | http://repo.or.cz/w/qemu/qmp-unstable.git | ||
''' | '''NOTE''': all branches in this repository are constantly rebased. | ||
The current | The ''master'' branch contains a functional QMP implementation for emission only (includes asynchronous messages). The current specification draft and other documentation can be found in the [http://repo.or.cz/w/qemu/qmp-unstable.git?a=tree;f=QMP;h=290262119cc6c9e07a6ef7a078384ef12c491e51;hb=HEAD QMP directory ] of the same branch. | ||
== History == | == History == | ||
Revision as of 11:31, 23 October 2009
Monitor Protocol
The QEMU Monitor Protocol (QMP) project goal is to implement a JSON based protocol for QEMU.
Problem
QEMU does not provide a way for applications to control it at the "machine level", that is, the current existing interface (called Monitor) was designed for human interaction only.
This is very problematic for applications, for the following reasons:
- It is needed to parse output meant to be read by humans
- It is not reliable, because it is not always possible to know whether a command has been successfully executed or not
- It lacks support for asynchronous events
Solution
Improve QEMU's Monitor to support a JSON based stable protocol.
Project status (2009-10-20)
Most of the infrastructure has been merged, a JSON decoder should be merged in the next days. The important missing parts are the error framework and the JSON encoder.
Additionally, all command handlers need to be converted to use QObjects. This work is in progress, but several handlers depend on the JSON decoder.
Main building blocks
- QObject Layer (merged)
- QObject Monitor infrastructure (merged)
- JSON decoder (under review)
- JSON encoder (not started)
- Error framework (under discussion)
Command handlers conversion work
- Input through QDict (merged)
- Output in QObject style (in progress)
- Error handling (not started)
Libqmp
Although this is still under discussion, we are also going to provide a C library with a stable ABI.
The short-term plan is to have a simple API to send commands and receive responses, this way C clients do not need to have their own JSON implementation.
The long-term plan is to provide a full management API for QEMU.
Development
The development takes place in the QMP unstable tree:
http://repo.or.cz/w/qemu/qmp-unstable.git
NOTE: all branches in this repository are constantly rebased.
The master branch contains a functional QMP implementation for emission only (includes asynchronous messages). The current specification draft and other documentation can be found in the QMP directory of the same branch.
History
This is the fourth proposal for a machine protocol, past discussions can be found in the following links: