[PATCH] NEWS: Document my contributions for upcoming release
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- NEWS.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index b5893627e3..32ab0c801e 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -90,6 +90,24 @@ v8.0.0 (unreleased) </qemu:capabilities> </domain> + * Fix sparse streams with split daemon + + In split daemon scenario, when a client connected to a hypervisor driver + using sparse streams (e.g. ``virsh vol-download --sparse``) would make the + hypervisor daemon enter an infinite loop without any data transfer. This is + now fixed. + + * Build no longer requires RPC library + + Code and its cross dependencies were fixed so that build without remote + driver and thus an RPC library (like ``tirpc``) fails no more. + + * virnetdevopenvswitch: Fix 'burst' value passed to ovs-vsctl + + When a ``<bandwidth/>`` was defined for an TAP device that's plugged into an + OvS bridge values passed to the OvS were incorrectly recalculated resulting + in slightly different limits being applied. + v7.10.0 (2021-12-01) ==================== -- 2.34.1
On Wed, Jan 12, 2022 at 15:53:03 +0100, Michal Privoznik wrote:
Signed-off-by: Michal Privoznik <mprivozn@redhat.com> --- NEWS.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
diff --git a/NEWS.rst b/NEWS.rst index b5893627e3..32ab0c801e 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -90,6 +90,24 @@ v8.0.0 (unreleased) </qemu:capabilities> </domain>
+ * Fix sparse streams with split daemon + + In split daemon scenario, when a client connected to a hypervisor driver
What about In split daemon scenario, a client connected to a hypervisor driver and
+ using sparse streams (e.g. ``virsh vol-download --sparse``) would make the + hypervisor daemon enter an infinite loop without any data transfer. This is + now fixed. + + * Build no longer requires RPC library + + Code and its cross dependencies were fixed so that build without remote + driver and thus an RPC library (like ``tirpc``) fails no more. + + * virnetdevopenvswitch: Fix 'burst' value passed to ovs-vsctl + + When a ``<bandwidth/>`` was defined for an TAP device that's plugged into an
s/an TAP/a TAP/
+ OvS bridge values passed to the OvS were incorrectly recalculated resulting + in slightly different limits being applied. +
v7.10.0 (2021-12-01) ====================
Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
participants (2)
-
Jiri Denemark -
Michal Privoznik