On a Monday in 2020, Peter Krempa wrote:
The machine types for this cycle were already added and qemu also added a property for the machine type object called "default-ram-id".
Also "block-bitmap-mapping" is supported as a migration parameter.
Signed-off-by: Peter Krempa <pkrempa@redhat.com> --- .../domaincapsdata/qemu_5.2.0-q35.x86_64.xml | 206 + .../domaincapsdata/qemu_5.2.0-tcg.x86_64.xml | 200 + tests/domaincapsdata/qemu_5.2.0.x86_64.xml | 206 + .../caps_5.2.0.x86_64.replies | 29846 ++++++++++++++++ .../caps_5.2.0.x86_64.xml | 3193 ++ 5 files changed, 33651 insertions(+) create mode 100644 tests/domaincapsdata/qemu_5.2.0-q35.x86_64.xml create mode 100644 tests/domaincapsdata/qemu_5.2.0-tcg.x86_64.xml create mode 100644 tests/domaincapsdata/qemu_5.2.0.x86_64.xml create mode 100644 tests/qemucapabilitiesdata/caps_5.2.0.x86_64.replies create mode 100644 tests/qemucapabilitiesdata/caps_5.2.0.x86_64.xml
Note that I've trimmed out the basically unreviewable qemu replies.
You can view the full patch here:
https://gitlab.com/pipo.sk/libvirt/-/commit/95b9ca6ce5c3d8458d3f85c547c4f152...
This patch can be postponed after the release, but I wanted to see whether anything new was added after the start of the dev cycle.
Reviewed-by: Ján Tomko <jtomko@redhat.com> Jano