v44.0 #6941
likebreath
started this conversation in
General
v44.0
#6941
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
v44.0
This release has been tracked in our roadmap project as iteration
v44.0. The following user visible changes have been made:
Configurable
virtio-iommuAddress WidthThe
iommu_address_widthoption has been added to--platformto allow usersto limit the
virtio-iommuaddress space in the guest. (#6900)Notable Performance Improvements
The
VIRTIO_BLK_F_SEG_MAXfeature has been enabled forvirtio-blockdevices,which brings significant performance improvements on throughput. (#6885)
The
io_uringentries are no longer forced to use async helper workers,delegating the decision to the kernel. This change resolved the issue of having
excessive amount of worker threads when
io_uringis being used, which isexpected to improve performance, such as reducing memory usage and reduce CPU
contention.
New Fuzzers
Our continuous fuzzing infrastructure is augmented with two new fuzzers to cover
x86 instruction emulator and
virtio-vsock.Notable Bug Fixes
Contributors
Many thanks to everyone who has contributed to our release:
v43.0
This release has been tracked in our roadmap
project as iteration
v43.0. The following user visible changes have been made:
Live Migration over TCP Connections
Support has been added to enable direct live migration from two hosts via TCP
connections. This supplements the existing support for migrating over a UNIX
socket which can then be tunnelled as desired. The documentation has been
updated. (#6850)
Notable Performance Improvements
The
VIRTIO_RING_F_INDIRECT_DESCfeature has been enabled forvirtio-blockdevices. This significantly increases the throughput of the devices with a
small negative impact on latency. (#6826)
Notable Bug Fixes
architectures. Whether they function depends on the host PCI host bridge
support - previously they would be rejected even if the driver did not use
these BARs. (vmm: support PCI I/O regions on all architectures #6871)
parameter was provided if any other VM parameters provided. (Require payload argument when parsing any other VM argument #6832)
Contributors
Many thanks to everyone who has contributed to our release:
This discussion was created from the release v44.0.
Beta Was this translation helpful? Give feedback.
All reactions