e355ea422d
Make the tool useful also for non-testing purposes by adding 'dump' mode, which will process the data and output information about the qemu version. The first 'dump' mode produces all possible valid query strings per virQEMUQAPISchemaPathGet/virQEMUCapsQMPSchemaQueries. This is useful for users to look up a query string via 'grep' rather than trying to come up with it manually. Additionally the data as represented by qemu changes naming very often and that makes it un-reviewable to find changes between two qemu builds. By using the dump mode, which produces results in stable order we can use it to 'diff' two .replies file without churn. Sample output '[...]' denotes an arbitrary trim: $ ./scripts/qemu-replies-tool.py tests/qemucapabilitiesdata/caps_9.0.0_x86_64.replies --dump-qmp-query-strings [...] (qmp) blockdev-add (qmp) blockdev-add/arg-type/auto-read-only (qmp) blockdev-add/arg-type/auto-read-only/!bool (qmp) blockdev-add/arg-type/cache (qmp) blockdev-add/arg-type/cache/direct (qmp) blockdev-add/arg-type/cache/direct/!bool (qmp) blockdev-add/arg-type/cache/no-flush (qmp) blockdev-add/arg-type/cache/no-flush/!bool (qmp) blockdev-add/arg-type/detect-zeroes (qmp) blockdev-add/arg-type/detect-zeroes/^off (qmp) blockdev-add/arg-type/detect-zeroes/^on (qmp) blockdev-add/arg-type/detect-zeroes/^unmap [...] (qmp) blockdev-add/arg-type/driver (qmp) blockdev-add/arg-type/driver/^blkdebug (qmp) blockdev-add/arg-type/driver/^blklogwrites (qmp) blockdev-add/arg-type/driver/^blkreplay (qmp) blockdev-add/arg-type/driver/^blkverify (qmp) blockdev-add/arg-type/driver/^bochs (qmp) blockdev-add/arg-type/driver/^cloop [...] (qmp) blockdev-add/arg-type/+blkdebug (qmp) blockdev-add/arg-type/+blkdebug/align (qmp) blockdev-add/arg-type/+blkdebug/align/!int (qmp) blockdev-add/arg-type/+blkdebug/config (qmp) blockdev-add/arg-type/+blkdebug/config/!str (qmp) blockdev-add/arg-type/+blkdebug/image (qmp) blockdev-add/arg-type/+blkdebug/image (recursion) (qmp) blockdev-add/arg-type/+blkdebug/image/!str (qmp) blockdev-add/arg-type/+blkdebug/inject-error Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
Libvirt API for virtualization
Libvirt provides a portable, long term stable C API for managing the virtualization technologies provided by many operating systems. It includes support for QEMU, KVM, Xen, LXC, bhyve, Virtuozzo, VMware vCenter and ESX, VMware Desktop, Hyper-V, VirtualBox and the POWER Hypervisor.
For some of these hypervisors, it provides a stateful management daemon which runs on the virtualization host allowing access to the API both by non-privileged local users and remote users.
Layered packages provide bindings of the libvirt C API into other languages including Python, Perl, PHP, Go, Java, OCaml, as well as mappings into object systems such as GObject, CIM and SNMP.
Further information about the libvirt project can be found on the website:
License
The libvirt C API is distributed under the terms of GNU Lesser General Public License, version 2.1 (or later). Some parts of the code that are not part of the C library may have the more restrictive GNU General Public License, version 2.0 (or later). See the files COPYING.LESSER and COPYING for full license terms & conditions.
Installation
Instructions on building and installing libvirt can be found on the website:
https://libvirt.org/compiling.html
Contributing
The libvirt project welcomes contributions in many ways. For most components the best way to contribute is to send patches to the primary development mailing list. Further guidance on this can be found on the website:
https://libvirt.org/contribute.html
Contact
The libvirt project has two primary mailing lists:
- users@lists.libvirt.org (for user discussions)
- devel@lists.libvirt.org (for development only)
Further details on contacting the project are available on the website: