The original NEWS entry for the vTPM transient VM crash was rather vague and non-actionable. As the bug is still actively experienced by users [1] of distros that didn't yet ship an update to v11.0.0 and is hit by relatively common usage improve the entry to mention situations when it happens and link to upstream bug reports containing workarounds. [1]: https://gitlab.com/libvirt/libvirt/-/issues/746 Signed-off-by: Peter Krempa <pkrempa(a)redhat.com&gt; --- v2: Instead of listing the workarounds link to the upstream issues. NEWS.rst | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/NEWS.rst b/NEWS.rst index 7984f358f3..96e6ee9ada 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -116,10 +116,17 @@ v11.0.0 (2025-01-15) * **Bug fixes** - * qemu: tpm: do not update profile name for transient domains + * qemu: tpm: Fix crash on startup of transient domains with vTPM - Fix a possible crash when starting a transient domain which was - introduced in the previous release. + A bug was introduced in `v10.10.0 (2024-12-02)`_ when a transient VM with + a vTPM device is started either via ``virsh create domain.xml`` or when + creating VMs via ``virt-manager`` which uses transient definition for the + initial installation the libvirt daemon (``virtqemud`` or ``libvirtd``) can + crash. + + More information and workarounds were documented in upstream issues + `#746 <https://gitlab.com/libvirt/libvirt/-/issues/746>`__ and + `#715 <https://gitlab.com/libvirt/libvirt/-/issues/715>`__. * qemu: Fix snapshot to not delete disk image with internal snapshot -- 2.48.1