Package: qemu.qmp
Welcome!qemu.qmpis aQEMU Monitor Protocol(“QMP”) library written in Python, usingasyncio. It is used to send
QMP messages to runningQEMUemulators. It
requires Python 3.7+ and has no mandatory dependencies.This library can be used to communicate with QEMU emulators, theQEMU
Guest Agent(QGA),
theQEMU Storage Daemon(QSD), or any other utility or application thatspeaks QMP.This library makes as few assumptions as possible about the actual
version or what type of endpoint it will be communicating with;
i.e. this library does not contain command definitions and does not seek
to be an SDK or a replacement for tools likelibvirtorvirsh. It is “simply” the protocol
(QMP) and not the vocabulary (QAPI). It is up
to the library user (you!) to know which commands and arguments you want
to send.Who is this library for?It is firstly for developers of QEMU themselves; as the test
infrastructure of QEMU itself needs a convenient and scriptable
interface for testing QEMU. This library was split out of the QEMU
source tree in order to share a reference version of a QMP library that
was usable both within and outside of the QEMU source tree.Second, it’s for those who are developingforQEMU by adding new
architectures, devices, or functionality; as well as targeting those who
are developingwithQEMU, i.e. developers working on integrating QEMU
features into other projects such as libvirt, KubeVirt, Kata Containers,
etc. Occasionally, using existing virtual-machine (VM) management stacks
that integrate QEMU+KVM can make developing, testing, and debugging
features difficult. In these cases, having more ‘raw’ access to QEMU is
beneficial. This library is for you.Lastly, it’s for power users who already use QEMU directly without the
aid of libvirt because they require the raw control and power this
affords them.Who isn’t this library for?It is not designed for anyone looking for a turn-key solution for VM
management. QEMU is a low-level component that resembles a particularly
impressive Swiss Army knife. This library does not manage that
complexity and is largely “VM-ignorant”. It’s not a replacement for
projects likelibvirt,virt-manager,GNOME Boxes, etc.InstallingThis package can be installed from PyPI with pip:> pip3 install qemu.qmpUsageLaunch QEMU with a monitor, e.g.:> qemu-system-x86_64 -qmp unix:qmp.sock,server=on,wait=offThen, at its simplest, script-style usage looks like this:import asyncio
from qemu.qmp import QMPClient

async def main():
    qmp = QMPClient('my-vm-nickname')
    await qmp.connect('qmp.sock')

    res = await qmp.execute('query-status')
    print(f"VM status: {res['status']}")

    await qmp.disconnect()

asyncio.run(main())The above script will connect to the UNIX socket located atqmp.sock, query the VM’s runstate, then print it out
to the terminal:> python3 example.py
VM status: runningFor more complex usages, especially those that make full advantage of
monitoring asynchronous events, refer to theonline documentationor
typeimport qemu.qmp; help(qemu.qmp)in your Python terminal of
choice.ContributingContributions are quite welcome! Please file bugs using theGitLab
issue tracker. This
project will accept GitLab merge requests, but due to the close
association with the QEMU project, there are some additional guidelines:Please use the “Signed-off-by” tag in your commit messages. Seehttps://wiki.linuxfoundation.org/dcofor more information on this
requirement.This repository won’t squash merge requests into a single commit on
pull; each commit should seek to be self-contained (within reason).Owing to the above, each commit sent as part of a merge request
should not introduce any temporary regressions, even if fixed later
in the same merge request. This is done to preserve bisectability.Please associate every merge request with at least oneGitLab issue. This
helps with generating Changelog text and staying organized. Thank you
🙇DevelopingOptional packages necessary for running code quality analysis for this
package can be installed with the optional dependency group “devel”:pip install qemu.qmp[devel].make developcan be used to install this package in editable mode
(to the current environment)andbring in testing dependencies in one
command.make checkcan be used to run the available tests. Consultmake helpfor other targets and tests that make sense for different
occasions.Before submitting a pull request, consider runningmakecheck-tox&& makecheck-minreqslocally to spot any issues that will
cause the CI to fail. These checks use their ownvirtual environmentsand won’t pollute your working
space.Stability and VersioningThis package uses a major.minor.microSemVer versioning, with the following additional semantics during
the alpha/beta period (Major version 0):This package treats 0.0.z versions as “alpha” versions. Each micro
version update may change the API incompatibly. Early users are advised
to pin against explicit versions, but check for updates often.A planned 0.1.z version will introduce the first “beta”, whereafter each
micro update will be backwards compatible, but each minor update will
not be. The first beta version will be released after legacy.py is
removed, and the API is tentatively “stable”.Thereafter, normalSemVer/PEP440rules will apply; micro updates
will always be bugfixes, and minor updates will be reserved for
backwards compatible feature changes.Changelog0.0.3 (2023-07-10)This release addresses packaging issues associated with the forthcoming
release of Python 3.12. This release adds Python 3.12 support, drops
Python 3.6 support, and switches to PEP-517 native packaging.!25:
Drop Python 3.6 support#30:
The read buffer limit has been increased from 256KiB to 10MiB for
parity with libvirt’s default and to accommodate real-world replies
that may exceed the current limit.#29:
The connect() call now accepts existing sockets as an ‘address’,
allowing for easier use of socketpairs to create client/server pairs.
This functionality was revised in!22.!23:
Fix deadlock on disconnect under CPython 3.12.
See alsohttps://github.com/python/cpython/issues/104344.!24:
Switch to PEP517 native packaging to coincide with Python 3.12
dropping distutils, setuptools from ensurepip, etc.0.0.2 (2022-08-26)This release primarily fixes development tooling, documentation, and
packaging issues that have no impact on the library itself. A handful of
small, runtime visible changes were added as polish.#28:
Added manual pages and web docs for qmp-shell[-wrap]#27:
Support building Sphinx docs from SDist files#26:
Add coverage.py support to GitLab merge requests#25:
qmp-shell-wrap now exits gracefully when qemu-system not found.#24:
Minor packaging fixes.#10:
qmp-tui exits gracefully when [tui] extras are not installed.#09:
__repr__ methods have been improved for all custom classes.#04:
Mutating QMPClient.name now also changes logging messages.0.0.1 (2022-07-20)Initial public release. (API is still subject to change!)