mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-22 17:34:18 +03:00
NEWS: note new passt feature & bugfix for 9.1.0 release
This also adds a sentence pointing out that SELinux must be disabled in order for passt support to work. I didn't think to put that info in the NEWS file last month when reporting the addition of passt support. Signed-off-by: Laine Stump <laine@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
This commit is contained in:
parent
f5966651e7
commit
a2929d4b38
18
NEWS.rst
18
NEWS.rst
@ -38,6 +38,13 @@ v9.1.0 (unreleased)
|
||||
A pvpanic device can be now defined as a PCI device (the original is an ISA
|
||||
device) with ``<panic model='pvpanic'/>``.
|
||||
|
||||
* qemu: support automatic restart of inadvertently terminated passt process
|
||||
|
||||
If the passt process that is serving as the backend of a -netdev
|
||||
stream is terminated unexpectedly, libvirt now listens to QEMU's
|
||||
notification of this, and starts up a new passt instance, thus
|
||||
preserving network connectivity.
|
||||
|
||||
* **Improvements**
|
||||
|
||||
* RPM packaging changes
|
||||
@ -63,6 +70,17 @@ v9.1.0 (unreleased)
|
||||
snapshot when it existed. In addition when external memory only snapshot
|
||||
was created libvirt failed without producing any error.
|
||||
|
||||
* QEMU: properly report passt startup errors
|
||||
|
||||
Due to how the child passt process was started, the initial
|
||||
support for passt (added in 9.0.0) would not see errors
|
||||
encountered during startup, so libvirt would continue to setup and
|
||||
start the guest; this led to a running guest with no network
|
||||
connectivity.
|
||||
|
||||
(NB: On systems that use them, it is still necessary to disable
|
||||
SELinux/AppArmor to start passt.)
|
||||
|
||||
|
||||
v9.0.0 (2023-01-16)
|
||||
===================
|
||||
|
Loading…
Reference in New Issue
Block a user