I'm happy to announce the release of libvirt-dbus 1.4.1.
libvirt-dbus wraps libvirt API to provide high-level object-oriented
API better suited for dbus-based applications.
https://libvirt.org/sources/dbus/libvirt-dbus-1.4.1.tar.xz
* Improvements
- Generate systemd unit files
* Bug fixes
- Fix double free in domain snapshot API
- Handle APIs with unsigned long correctly
* Build-system improvements
- Honour meson ``warning_level`` setting
- Add ``git_werror`` option and only set if ``-Dwerror`` is not set
Thanks everybody who contributed!
Pavel
I have just tagged v7.5.0-rc1 in the repository and pushed signed
tarballs and source RPMs to https://libvirt.org/sources/
Please give the release candidate some testing and in case you find a
serious issue which should have a fix in the upcoming release, feel
free to reply to this thread to make sure the issue is more visible.
If you have not done so yet, please update NEWS.rst to document any
significant change you made since the last release.
Thanks,
Jirka
The 7.4.0 release of both libvirt and libvirt-python is tagged and
signed tarballs and source RPMs are available at
https://libvirt.org/sources/https://libvirt.org/sources/python/
Thanks everybody who helped with this release by sending patches,
reviewing, testing, or providing any other feedback. Your work is
greatly appreciated.
* Removed features
* qemu: Remove support for QEMU < 2.11
In accordance with our platform support policy, the oldest supported QEMU
version is now bumped from 1.5 to 2.11.
* New features
* qemu: Add support for hotplugging ``<transient/>`` disks
The disk hotplug code in the qemu driver now can handle hotplug of disks
with automatically added overlay.
* qemu: Add support for sharing base image of ``<transient/>`` disks
Users can use ``<transient shareBacking='yes'/>`` to tell the qemu driver to
never open the base image in write mode thus multiple VMs can share the
same image. Note that the disk will be hotplugged during startup.
* Improvements
* Add win-dmp crashdump format
New ``win-dmp`` format for ``virDomainCoreDumpWithFormat`` API and/or virsh
``dump --format`` was introduced.
* Bug fixes
* Allow 0 offset in XML schema for ``<slice type='storage' offset='0' size='321'/>``
Having a 0 offset so that the size of the image can be limited is a
valid configuration so it was allowed in the XML schema.
Enjoy.
Jirka
