November 2025 - Devel - libvirt List Archives

[PATCH] NEWS: Fix incoming migration to QEMU 10.0.0
by Jiri Denemark 28 Nov '25

28 Nov '25

From: Jiri Denemark <jdenemar(a)redhat.com> Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com> --- NEWS.rst | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index c742954091..d5028d230d 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -43,6 +43,13 @@ v11.10.0 (unreleased) subdirectory, the ESX driver would have failed to parse that and an error was reported when obtaining domain XML. This is now fixed. + * qemu: Fix incoming migration to QEMU 10.0.0 and newer + + Due to a change in the way QEMU 10.0.0 reports the state of "ht" CPU + feature, incoming migration of a domain with multiple CPU threads would + fail with "guest CPU doesn't match specification: extra features: ht" + error. + v11.9.0 (2025-11-03) ==================== -- 2.51.1

2 1

[PATCH] NEWS: Add CVE-2025-12748
by Martin Kletzander 28 Nov '25

28 Nov '25

From: Martin Kletzander <mkletzan(a)redhat.com> Signed-off-by: Martin Kletzander <mkletzan(a)redhat.com> --- NEWS.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index c742954091df..8cc6e698ca25 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -13,6 +13,22 @@ v11.10.0 (unreleased) * **Security** + * CVE-2025-12748: Denial of service by some ACL-limited accounts + + Parsing of user provided XMLs in APIs which needed the identification + information from those XML definitions was done in full before ACL checks + were performed. Some valid, but useless, definitions could cause allocation + of too much memory, leading to denial of service. APIs which do equate to + full root access (such as ``domain:write``), and were parsing XML + definitions in full before performing ACL checks could, potentially, be + exploited in a way that would allow users (which were about to be denied the + API call) to cause aforementioned overallocation even before the ACL checks + were performed. + + A change was made so that parsing before ACL checks are done only for the + identification parts of the XML definition (which is needed to perform the + checks) and full parsing is done only after checking all ACLs. + * **Removed features** * **New features** -- 2.52.0

2 2

[PATCH] news: document improved certs, host validate details & TDX fix
by Daniel P. Berrangé 28 Nov '25

28 Nov '25

From: Daniel P. Berrangé <berrange(a)redhat.com> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> --- NEWS.rst | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 7c3a6c01e7..a41f53e00d 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -30,8 +30,25 @@ v11.10.0 (unreleased) Bhyve guests can now be configured to wait for a VNC connection before booting. + * remote: multiple certificate support + + The remote daemon and client can be configured to load multiple x509 + certificate identities. This facilitates a transition to certificates + supporting Post-Quantum Crytographic algorithms. + + * tools: improved virt-host-validate output + + The virt-host-validate tool will now report extra details when certain + checks pass. + * **Bug fixes** + * qemu: fix incorrect reporting of the TDX launch security type + + The TDX launch security type was incorrectly reported on all platforms + if the QEMU binary had it built-in. It is now limited to only platforms + with the TDX kernel feature available for use. + v11.9.0 (2025-11-03) ==================== -- 2.51.1

2 1

[PATCH] rpm: disable QEMU driver on non-64-bit arches for Fedora >= 44
by Daniel P. Berrangé 28 Nov '25

28 Nov '25

From: Daniel P. Berrangé <berrange(a)redhat.com> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> --- libvirt.spec.in | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/libvirt.spec.in b/libvirt.spec.in index 62af7fb517..8b3bc9884f 100644 --- a/libvirt.spec.in +++ b/libvirt.spec.in @@ -32,12 +32,22 @@ %define arches_ch x86_64 aarch64 # The hypervisor drivers that run in libvirtd -%define with_qemu 0%{!?_without_qemu:1} %define with_lxc 0%{!?_without_lxc:1} %define with_libxl 0%{!?_without_libxl:1} %define with_vbox 0%{!?_without_vbox:1} %define with_ch 0%{!?_without_ch:1} +%ifarch %{arches_64bit} + %define with_qemu 0%{!?_without_qemu:1} +%else + # QEMU drops 32-bit in Fedora 44 + %if %{?fedora} > 43 + %define with_qemu 0 + %else + %define with_qemu 0%{!?_without_qemu:1} + %endif +%endif + %ifarch %{arches_qemu_kvm} %define with_qemu_kvm %{with_qemu} %else -- 2.51.1

2 1

[PATCH] rpm: disable QEMU driver on non-64-bit arches for Fedora >= 44
by Daniel P. Berrangé 28 Nov '25

28 Nov '25

From: Daniel P. Berrangé <berrange(a)redhat.com> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> --- libvirt.spec.in | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/libvirt.spec.in b/libvirt.spec.in index 62af7fb517..8b3bc9884f 100644 --- a/libvirt.spec.in +++ b/libvirt.spec.in @@ -32,12 +32,22 @@ %define arches_ch x86_64 aarch64 # The hypervisor drivers that run in libvirtd -%define with_qemu 0%{!?_without_qemu:1} %define with_lxc 0%{!?_without_lxc:1} %define with_libxl 0%{!?_without_libxl:1} %define with_vbox 0%{!?_without_vbox:1} %define with_ch 0%{!?_without_ch:1} +%ifarch %{arches_64bit} + %define with_qemu 0%{!?_without_qemu:1} +%else + # QEMU drops 32-bit in Fedora 44 + %if %{?fedora} > 43 + %define with_qemu 0 + %else + %define with_qemu 0%{!?_without_qemu:1} + %endif +%endif + %ifarch %{arches_qemu_kvm} %define with_qemu_kvm %{with_qemu} %else -- 2.51.1

1 0

[PATCH] NEWS: Document features/improvements/bug fixes I've participated in
by Michal Privoznik 28 Nov '25

28 Nov '25

From: Michal Privoznik <mprivozn(a)redhat.com> There are some features/improvements/bug fixes I've either contributed or reviewed/merged. Document them for upcoming release. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> --- NEWS.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 7c3a6c01e7..4d9b98f93c 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -32,6 +32,17 @@ v11.10.0 (unreleased) * **Bug fixes** + * ch: Use correct domain definition in chDomainGetXMLDesc() + + Cloud-Hyper driver claims to support ``VIR_DOMAIN_XML_INACTIVE`` but in + fact it never formatted the inactive XML. This is now fixed. + + * esx: Allow disk images in subdirectories + + If a domain has a disk image that's not in a datastore path but in a + subdirectory, the ESX driver would have failed to parse that and an error + was reported when obtaining domain XML. This is now fixed. + v11.9.0 (2025-11-03) ==================== -- 2.51.2

2 1

Entering freeze for libvirt-11.10.0
by Jiri Denemark 27 Nov '25

27 Nov '25

I have just tagged v11.10.0-rc1 in the repository and pushed signed tarballs to https://download.libvirt.org/ Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible. If you have not done so yet, please update NEWS.rst to document any significant change you made since the last release. Jirka

1 1

[PATCH] virCgroupSetValueRaw: Use 'const' temporary variable
by Peter Krempa 26 Nov '25

26 Nov '25

From: Peter Krempa <pkrempa(a)redhat.com> 'char *tmp' is assigned from calling 'strrchr' on a 'const char *'. New clang in fedora doesn't like it. Make 'tmp' const. Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> --- https://gitlab.com/MichalPrivoznik/libvirt/-/jobs/12208300313 src/util/vircgroup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/util/vircgroup.c b/src/util/vircgroup.c index 532a7e5690..3d66d3acb2 100644 --- a/src/util/vircgroup.c +++ b/src/util/vircgroup.c @@ -517,7 +517,7 @@ int virCgroupSetValueRaw(const char *path, const char *value) { - char *tmp; + const char *tmp; VIR_DEBUG("Set path '%s' to value '%s'", path, value); if (virFileWriteStr(path, value, 0) < 0) { -- 2.52.0

4 10

[PATCH] docs/deprecated: Remove undeprecated SMP description
by Zhao Liu 26 Nov '25

26 Nov '25

"Unsupported 'parameter=1' SMP configuration" was proposed to be deprecated in the commit 54c4ea8f3ae6 ("hw/core/machine-smp: Deprecate unsupported "parameter=1" SMP configurations"). But the related code was reverted later in the commit 9d7950edb0cd ("hw/core: allow parameter=1 for SMP topology on any machine"). Thus, this SMP behavior is still valid and is not actually deprecated. Remove outdated document descriptions. Reported-by: Markus Armbruster <armbru(a)redhat.com> Signed-off-by: Zhao Liu <zhao1.liu(a)intel.com> --- docs/about/deprecated.rst | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst index 03e29915f0aa..bbfcce4a1ab3 100644 --- a/docs/about/deprecated.rst +++ b/docs/about/deprecated.rst @@ -54,20 +54,6 @@ as short-form boolean values, and passed to plugins as ``arg_name=on``. However, short-form booleans are deprecated and full explicit ``arg_name=on`` form is preferred. -``-smp`` (Unsupported "parameter=1" SMP configurations) (since 9.0) -''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' - -Specified CPU topology parameters must be supported by the machine. - -In the SMP configuration, users should provide the CPU topology parameters that -are supported by the target machine. - -However, historically it was allowed for users to specify the unsupported -topology parameter as "1", which is meaningless. So support for this kind of -configurations (e.g. -smp drawers=1,books=1,clusters=1 for x86 PC machine) is -marked deprecated since 9.0, users have to ensure that all the topology members -described with -smp are supported by the target machine. - QEMU Machine Protocol (QMP) commands ------------------------------------ -- 2.34.1

3 2

git tags for CVEs
by Peter Krempa 26 Nov '25

26 Nov '25

We've recently tagged a few patches fixing CVEs with signed git tags. We also in the past tagged patches fixing CVEs. I've identified a list of CVEs (including commit hashes) that weren't tagged yet. The list below was first compiled using this "simple one liner": git log | grep -o 'CVE-[0-9]\+-[0-9]\+\|^commit [0-9a-z]\+' | grep -B 1 'CVE-' | grep -v '^--' | tr "\n" " " | sed 's/commit/\ncommit/g' | grep -v "$(git tag ' | sed -e 's/|$//' -e 's/|/\\|/g')" > cves (Basically looking for 'CVE-' strings in the commit log and cross-referencing it with the list of tags (badly for that matter I halfway realized that I pasted in the sub-command supposed to find CVEs wrong but was too far in to re-try)) And then manually going trhough the list. I've identified the following commits: (single commits) commit 8dfb12cb77996519901b8d52c754ab564ebd10e8 CVE-2024-8235 commit 8074d64dc2eca846d6a61efe1a9b7428a0ce1dd1 CVE-2024-4418 commit 8a3f8d957507c1f8223fdcf25a3ff885b15557f2 CVE-2024-2494 commit c664015fe3a7bf59db26686e9ed69af011c6ebb8 CVE-2024-1441 commit 9a47442366fcf8a7b6d7422016d7bbb6764a1098 CVE-2023-3750 commit a4947e8f63c3e6b7b067b444f3d6cf674c0d7f36 CVE-2022-0897 commit 15073504dbb624d3f6c911e85557019d3620fdb2 CVE-2021-3631 commit 22494556542c676d1b9e7f1c1f2ea13ac17e1e3e CVE-2020-14339 commit bf6c2830b6c338b1f5699b095df36f374777b291 CVE-2019-10168 commit 8afa68bac0cf99d1f8aaa6566685c43c22622f26 CVE-2019-10167 commit db0b78457f183e4c7ac45bc94de86044a1e2056a CVE-2019-10166 commit aed6a032cead4386472afb24b16196579e239580 CVE-2019-10161 commit fbf31e1a4cd19d6f6e33e0937a009775cd7d9513 CVE-2018-1064 commit bc251ea91bcfddd2622fce6bce701a438b2e7276 CVE-2018-5748 commit 57023c0a3af4af1c547189c1f6712ed5edeb0c0b CVE-2014-8131 commit c567853089a2764c964002dd752e09e318524a38 CVE-2010-2242 commit 53611889ff93c442028828c70472151a7cf1bf4d CVE-2008-5086 (patchsets, where multiple patches bear CVE number, histrically we've tagged all of them with numbered tags) commit a63b48c5ecef077bf0f909a85f453a605600cf05 CVE-2020-25637 commit e4116eaa44cb366b59f7fe98f4b88d04c04970ad CVE-2020-25637 commit 50864dcda191eb35732dbd80fb6ca251a6bba923 CVE-2020-25637 commit 955029bd0ad7ef96000f529ac38204a8f4a96401 CVE-2020-25637 commit e37bd65f9948c1185456b2cdaa3bd6e875af680f CVE-2019-10132 commit f111e09468693909b1f067aa575efdafd9a262a1 CVE-2019-10132 commit 96f41cd765c9e525fe28ee5abbfbf4a79b3720c7 CVE-2019-10132 commit ae076bb40e0e150aef41361b64001138d04d6c60 CVE-2019-3886 commit 2a07c990bd9143d7a0fe8d1b6b7c763c52185240 CVE-2019-3886 commit c2dc6698c88fb591639e542c8ecb0076c54f3dfb CVE-2018-6764 commit 759b4d1b0fe5f4d84d98b99153dfa7ac289dd167 CVE-2018-6764 commit b347c0c2a321ec5c20aae214927949832a288c5a CVE-2015-0236 commit 03c3c0c874c84dfa51ef17556062b095c6e1c0a3 CVE-2015-0236 commit 5fc590ad9f4071350a8df4d567ba88baacc8334d CVE-2013-6456 commit 1cadeafcaa422844a27ef622e2a7041d0235bcb3 CVE-2013-6456 commit 1754c7f0ab1407dcf7c89636a35711dd9b1febe1 CVE-2013-6456 commit 7fba01c15c1f886b4235825692b4c13e88dd9f7b CVE-2013-6456 commit 4dd3a7d5bc44980135a1b11810ba9aeab42a4a59 CVE-2013-6456 commit aebbcdd33c8c18891f0bdbbf8924599a28152c9c CVE-2013-6456 And finally few manually synthetized entries based on CVE references. commit 447f69dec47e1b0bd15ecd7cd49a9fd3b050fb87 CVE-2021-3667 commit 68719c4bddb85fbcc931a5b7d99ac7c8a0af09b0 CVE-2010-2238 Thus if we want to keep tagging CVEs the above list ought to be tagged. I've also got a few work in progress patches/branches which will e.g. add a CI job to do (a more robust) cross-check of the CVE numbers with the commitlog and NEWS file, etc. In addition our commit log also references non-libvirt cves: CVE-2022-24765 - git permission issue when repo is shared between users CVE-2020-15708 - bug in Ubuntu's packaging of libvirt CVE-2013-0242 - memory corruption in gnulib's regex() CVE-2012-3386 - bug in automake's distcheck rules giving world-writable perms CVE-2011-4127 - qemu allowing SCSI/SG_IO command passthrough CPU vulnerabllities: CVE-2019-11135 - TSX Asynchronous Abort condition on some CPUs CVE-2018-12127, CVE-2018-12130, CVE-2019-11091 - Microarchitectural Store Buffer Data Sampling (MSBDS) cpu vulnerabilities CVE-2018-3639 - Speculative Store Bypass (SSB), Variant 4. CVE-2017-5715 - speculative execution by utilizing branch target injection

1 1