Release of libvirt-6.9.0
The 6.9.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. * New features * nodedev: Add support for channel subsystem (CSS) devices on S390 A CSS device is represented as a parent device of a CCW device. This support allows to create vfio-ccw mediated devices with ``virNodeDeviceCreateXML()``. * qemu: Implement memory failure event New event is implemented that is emitted whenever a guest encounters a memory failure. * qemu: Implement support for ``<transient/>`` disks VMs based on the QEMU hypervisor now can use ``<transient/>`` option for local file-backed disks to configure a disk which discards changes made to it while the VM was active. * hyperv: implement new APIs The ``virConnectGetCapabilities()``, ``virConnectGetMaxVcpus()``, ``virConnectGetVersion()``, ``virDomainGetAutostart()``, ``virDomainSetAutostart()``, ``virNodeGetFreeMemory()``, ``virDomainReboot()``, ``virDomainReset()``, ``virDomainShutdown()``, and ``virDomainShutdownFlags()`` APIs have been implemented in the Hyper-V driver. * bhyve: implement virtio-9p filesystem support Implement virito-9p shared filesystem using the ``<filesystem/>`` element. * qemu: Add support for vDPA network devices. VMs using the QEMU hypervisor can now specify vDPA network devices using ``<interface type='vdpa'>``. The node device APIs also now list and provide XML descriptions for vDPA devices. * Improvements * Bug fixes * hyperv: ensure WQL queries work in all locales Relying on the "Description" field caused queries to fail on non-"en-US" systems. The queries have been updated to avoid using localized strings. * rpc: Fix ``virt-ssh-helper`` detection libvirt 6.8.0 failed to correctly detect the availability of the new ``virt-ssh-helper`` command on the remote host, and thus always used the fallback instead; this has now been fixed. Enjoy. Jirka
On Mon, 2020-11-02 at 11:20 +0100, Jiri Denemark wrote: [...]
* Improvements
* Bug fixes
It would have been nice if you had removed the empty "Improvement" section at the same time as you updated the release date... Can you please look for such empty sections and deal with them next time? Thanks! -- Andrea Bolognani / Red Hat / Virtualization
On Mon, Nov 02, 2020 at 12:09:13 +0100, Andrea Bolognani wrote:
On Mon, 2020-11-02 at 11:20 +0100, Jiri Denemark wrote: [...]
* Improvements
* Bug fixes
It would have been nice if you had removed the empty "Improvement" section at the same time as you updated the release date... Can you please look for such empty sections and deal with them next time?
OK, it should not happen anymore thanks to the following write-only sed command integrated into my release script :-) sed -ne '/^[^ ]/{x; s/^\* [^\n]*\n\+$//; /^$/!p; ${x; p}; d}; H' NEWS.rst Jirka
On Mon, 2020-11-02 at 19:35 +0100, Jiri Denemark wrote:
On Mon, Nov 02, 2020 at 12:09:13 +0100, Andrea Bolognani wrote:
On Mon, 2020-11-02 at 11:20 +0100, Jiri Denemark wrote: [...]
* Improvements
* Bug fixes
It would have been nice if you had removed the empty "Improvement" section at the same time as you updated the release date... Can you please look for such empty sections and deal with them next time?
OK, it should not happen anymore thanks to the following write-only sed command integrated into my release script :-)
sed -ne '/^[^ ]/{x; s/^\* [^\n]*\n\+$//; /^$/!p; ${x; p}; d}; H' NEWS.rst
Wow, that *is* write-only :D Would it make sense to include the release script in the git repository? libosinfo and friends already have something along those lines, though I'm unclear on the scope of your specific take on it. -- Andrea Bolognani / Red Hat / Virtualization
On Tue, Nov 03, 2020 at 11:11:48 +0100, Andrea Bolognani wrote:
On Mon, 2020-11-02 at 19:35 +0100, Jiri Denemark wrote:
On Mon, Nov 02, 2020 at 12:09:13 +0100, Andrea Bolognani wrote:
On Mon, 2020-11-02 at 11:20 +0100, Jiri Denemark wrote: [...]
* Improvements
* Bug fixes
It would have been nice if you had removed the empty "Improvement" section at the same time as you updated the release date... Can you please look for such empty sections and deal with them next time?
OK, it should not happen anymore thanks to the following write-only sed command integrated into my release script :-)
sed -ne '/^[^ ]/{x; s/^\* [^\n]*\n\+$//; /^$/!p; ${x; p}; d}; H' NEWS.rst
Wow, that *is* write-only :D
Would it make sense to include the release script in the git repository? libosinfo and friends already have something along those lines, though I'm unclear on the scope of your specific take on it.
I don't mind publishing it, but... - it's very tied to my environment and the way I do this kind of things (interactive, requiring confirmations with a possibility to manually change things before continuing with the next step) - it's in bash - it does both libvirt and libvirt-python at once - when I need to change something I usually need to do it immediately to be able to make the release, i.e., with no review - I don't fancy random people messing with the script without my control :-) That said, libvirt.git is definitely not the right repo for it. But I guess my personal repo could work. Jirka
On Tue, 2020-11-03 at 12:40 +0100, Jiri Denemark wrote:
On Tue, Nov 03, 2020 at 11:11:48 +0100, Andrea Bolognani wrote:
Would it make sense to include the release script in the git repository? libosinfo and friends already have something along those lines, though I'm unclear on the scope of your specific take on it.
I don't mind publishing it, but...
- it's very tied to my environment and the way I do this kind of things (interactive, requiring confirmations with a possibility to manually change things before continuing with the next step)
- it's in bash
- it does both libvirt and libvirt-python at once
- when I need to change something I usually need to do it immediately to be able to make the release, i.e., with no review
- I don't fancy random people messing with the script without my control :-)
That said, libvirt.git is definitely not the right repo for it. But I guess my personal repo could work.
Yeah you're right, that doesn't sound something that would make a lot of sense in libvirt.git. Forget I said anything :) -- Andrea Bolognani / Red Hat / Virtualization
participants (2)
-
Andrea Bolognani -
Jiri Denemark