The API can be used to query current state of an interface to VMM used
to control a domain.
In QEMU world this translates into monitor connection and one can use the API,
e.g., to check whether (and for how long) libvirtd is currently waiting for a
reply from qemu process.
Jiri Denemark (6):
Introduce virTimeMs for getting current time in ms
Use virTimeMs when appropriate
Introduce virDomainGetControlInfo API
Wire protocol and remote driver for virDomainGetControlInfo
qemu: Implement virDomainGetControlInfo
virsh: Add support for virDomainGetControlInfo
daemon/remote_generator.pl | 20 +++++++---
include/libvirt/libvirt.h.in | 40 +++++++++++++++++++++
python/generator.py | 1 +
python/libvirt-override-api.xml | 6 +++
src/driver.h | 5 +++
src/libvirt.c | 48 ++++++++++++++++++++++++++
src/libvirt_private.syms | 1 +
src/libvirt_public.syms | 5 +++
src/qemu/qemu_domain.c | 28 ++++++---------
src/qemu/qemu_domain.h | 2 +
src/qemu/qemu_driver.c | 72 ++++++++++++++++++++++++++++++++++-----
src/qemu/qemu_migration.c | 31 +++++-----------
src/qemu/qemu_process.c | 3 ++
src/remote/remote_driver.c | 1 +
src/remote/remote_protocol.x | 14 +++++++-
src/remote_protocol-structs | 9 +++++
src/util/event_poll.c | 45 +++++++++---------------
src/util/util.c | 24 +++++++++++++
src/util/util.h | 2 +
tools/virsh.c | 66 +++++++++++++++++++++++++++++++++++
tools/virsh.pod | 7 ++++
21 files changed, 348 insertions(+), 82 deletions(-)
--
1.7.5.3