June 2026 - Devel - libvirt List Archives

[PATCH 0/2] Properly handle tri-state for KVM options
by Chris Riches 30 Jun '26

30 Jun '26

Two of the qemu kvm_features (kvm-poll-control and kvm-pv-ipi) were only emitted when on or when off respectively, rather than handling the full tri-state for each (on, off, absent). This meant that config like <poll-control state='off'/> was a no-op, equivalent to not specifying poll-control at all, which fails to prevent QEMU from enabling it based on its own internal defaults. In particular, this meant that having both <cpu mode='host-passthrough'> and <poll-control state='off'/> would cause the latter to be ignored, since libvirt would emit no explicit kvm-poll-control arg, and QEMU defaults to enabling most KVM features when CPU passthrough is enabled. Fix these two cases such that explicit on/off are both respected. The `hidden` and `hint-dedicated` options are left as-is, since these really do only make sense in the `on` direction; QEMU will never automatically enable them. Chris Riches (2): qemu: Emit explicit kvm-poll-control=off when disabled qemu: Emit explicit kvm-pv-ipi=on when enabled src/qemu/qemu_command.c | 14 ++++++++++---- .../kvm-features-off.x86_64-latest.args | 2 +- .../kvm-features.x86_64-latest.args | 2 +- 3 files changed, 12 insertions(+), 6 deletions(-) -- 2.43.0

2 4

[PATCH v2 0/8] Testcase improvements and Power8E/NVL removal
by Aditya Gupta 29 Jun '26

29 Jun '26

Overview ======== This patch series merged two patch series sent earlier: "Testcase improvements for PowerNV" "Remove deprecated Power8E and 8NVL CPUs" since the Power8E removal series depended on the former due to pnv-spi test Broadly contains 3 changes: 1. Testcase improvements: Add a testcase to detect regression in remote interrupts when XIVE changes, since such regression had occurred during Power11 XIVE changes: https://lore.kernel.org/qemu-devel/baf6c854-832b-4a2e-922f-d34e6dadf821@red… Also add Power11 chip and testcase in qtests, and fadump functional test 2. Power8E/Power8NVL removal Power8E and Power8NVL were deprecated since QEMU 10.1, with commit 264a604e7163 ("target/ppc: Deprecate Power8E and Power8NVL") Hence, remove usage (chip and core types) of Power8E and 8NVL from PowerNV, PSeries as well as testcases. 3. Maintainer changes Add myself as maintainer for PowerNV machine Testing ======= * Git tree for testing: https://gitlab.com/adi-g15-ibm/qemu/tree/feat_maintainer-v2 * Gitlab pipeline: https://gitlab.com/adi-g15-ibm/qemu/-/pipelines/2627063408 * Successful ppc64 functional tests, qtests, boot tests, builds at all commits Changelog ========= v2: + #1: put e1000e on socket 1, and disable it's cpu, as suggested by cedric + #1: pull out command fail checks into a helper, as suggested by shivang + #2: use g_autofree, suggested by cedric + #3: use g_autofree in tests updated + #8: remove G:, as suggested by daniel + rebased to upstream from previous split series: + #1: added checks to see if network is up and interrupts happened, based on shivang's review + #3: replaced common if-else-if check for machine type with pnv_get_machine_type + #7: added doc in removed-features, as suggested by cedric + #6,7: added rb from philippe + #8: new patch, maintainer change Aditya Gupta (8): tests/functional: Add remote interrupts test for PowerNV tests/qtest/pnv_spi: Test Power11 PNV_SPI tests/qtest: Add Power11 chip & machine to qtests tests/functional: Use default powernv machine instead of power10 ppc/pnv: Replace Power8E with Power11 for 'none' machine test ppc/pnv: Remove Power8E and Power8NVL pnv chips ppc/pnv: Remove Power8E and Power8NVL CPUs MAINTAINERS: Add self as maintainer for PowerNV MAINTAINERS | 2 +- docs/about/deprecated.rst | 9 --- docs/about/removed-features.rst | 8 +++ docs/system/ppc/powernv.rst | 2 +- docs/system/ppc/pseries.rst | 2 +- hw/ppc/pnv.c | 62 ----------------- hw/ppc/pnv_core.c | 2 - hw/ppc/spapr_cpu_core.c | 2 - include/hw/ppc/pnv.h | 8 --- target/ppc/cpu-models.c | 6 -- target/ppc/cpu-models.h | 4 -- target/ppc/cpu_init.c | 6 -- target/ppc/kvm.c | 4 +- tests/functional/ppc64/test_fadump.py | 2 +- tests/functional/ppc64/test_powernv.py | 95 ++++++++++++++++++++++++++ tests/qtest/machine-none-test.c | 2 +- tests/qtest/pnv-host-i2c-test.c | 10 ++- tests/qtest/pnv-spi-seeprom-test.c | 20 ++++-- tests/qtest/pnv-xive2-test.c | 2 +- tests/qtest/pnv-xscom-test.c | 22 ++---- tests/qtest/pnv-xscom.h | 42 ++++++++---- 21 files changed, 163 insertions(+), 149 deletions(-) base-commit: b83371668192a705b878e909c5ae9c1233cbd5fb -- 2.54.0

4 11

[PATCH] Replace if_tap check with pf check
by Nimish Jain 29 Jun '26

29 Jun '26

if_tap is bundled with if_tuntap and usually included in the kernel. Instead, check whether a firewall is present, otherwise network driver will not work. Signed-off-by: Nimish Jain <unauthorizen(a)gmail.com> --- tools/virt-host-validate-bhyve.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tools/virt-host-validate-bhyve.c b/tools/virt-host-validate-bhyve.c index d7a409db9d..539c6f85f3 100644 --- a/tools/virt-host-validate-bhyve.c +++ b/tools/virt-host-validate-bhyve.c @@ -51,7 +51,7 @@ int virHostValidateBhyve(void) int fileid = 0; g_autofree struct kld_file_stat *stat = g_new0(struct kld_file_stat, 1); bool vmm_loaded = false; - bool if_tap_loaded = false; + bool pf_loaded = false; bool if_bridge_loaded = false; bool nmdm_loaded = false; @@ -62,8 +62,8 @@ int virHostValidateBhyve(void) if (STREQ(stat->name, "vmm.ko")) vmm_loaded = true; - else if (STREQ(stat->name, "if_tap.ko")) - if_tap_loaded = true; + else if (STREQ(stat->name, "pf.ko")) + pf_loaded = true; else if (STREQ(stat->name, "if_bridge.ko")) if_bridge_loaded = true; else if (STREQ(stat->name, "nmdm.ko")) @@ -71,7 +71,7 @@ int virHostValidateBhyve(void) } MODULE_STATUS_FAIL(vmm, "will not be able to start VMs"); - MODULE_STATUS_WARN(if_tap, "networking will not work"); + MODULE_STATUS_WARN(pf, "network driver will not work"); MODULE_STATUS_WARN(if_bridge, "bridged networking will not work"); MODULE_STATUS_WARN(nmdm, "nmdm console will not work"); -- 2.39.5 (Apple Git-154)

2 1

Entering freeze for libvirt-12.5.0
by Jiri Denemark 29 Jun '26

29 Jun '26

I have just tagged v12.5.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] NEWS: document bhyve changes for 12.5.0
by Roman Bogorodskiy 29 Jun '26

29 Jun '26

Signed-off-by: Roman Bogorodskiy <bogorodskiy(a)gmail.com> --- NEWS.rst | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index a05fd43120..5a50f15912 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -17,10 +17,37 @@ v12.5.0 (unreleased) * **New features** + * bhyve: Extend the guest agent support + + The bhyve driver now supports several APIs on top of the guest agent: + + * Getting and setting guest OS SSH keys + * Setting guest OS user's password + * Getting and setting guest OS time + + Additionally, domain rebooting and shutting down using the agent + is now supported. + + * bhyve: Support ``on_reboot`` and ``on_poweroff`` actions + + The bhyve driver now respects the domain's + ``on_reboot`` and ``on_poweroff`` actions. + + * bhyve: Support populating SMBIOS fields + + Add support for populating the SMBIOS fields as defined + by the ``<sysinfo type='smbios'>`` section of the domain's XML. + * **Improvements** * **Bug fixes** + * bhyve: Guest agent related fixes + + A few bugs related to the guest agent communication are fixed, from + not properly initializing an agent to crashing when the agent + socket cannot be opened. + v12.4.0 (2026-06-01) ==================== -- 2.52.0

2 1

[PATCH] NEWS: Mention systemd unit dependency fixes and virtio video device model selection
by Peter Krempa 29 Jun '26

29 Jun '26

From: Peter Krempa <pkrempa(a)redhat.com> Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> --- NEWS.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index a05fd43120..8ec9f31a29 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -21,6 +21,22 @@ v12.5.0 (unreleased) * **Bug fixes** + * Ensure proper shutdown ordering of ``virtlogd`` and ``virtlockd`` + + The logging and locking helper daemons now shutdown after the daemon running + the ``qemu`` hypervisor driver since their services may be needed to shutdown + the VMs run by the qemu driver. + + * qemu: Record selected ``virtio`` video device model into the XML + + The ``qemu`` driver may depending on platform and installed QEMU modules + pick one of two distinct virtio video device types for the primary device. + + The choice was not recorded in the XML and since the devices are incompatible + it can cause failures on migration when the destination picks the wrong + device. This version thus records the picked device both for running VMs + on upgrade and for new devices to prevent this problem in the future. + v12.4.0 (2026-06-01) ==================== -- 2.54.0

2 1

[PATCHv2] Bring back if_tap check
by Nimish Jain 27 Jun '26

27 Jun '26

Signed-off-by: Nimish Jain <unauthorizen(a)gmail.com> --- tools/virt-host-validate-bhyve.c | 6 ++++++ 1 file changed, 6 insertions(+) As per suggestions on GitHub by Roman. Since if_tuntap is statically loaded, kldstat -m must be used. diff --git a/tools/virt-host-validate-bhyve.c b/tools/virt-host-validate-bhyve.c index 539c6f85f3..d3913dc046 100644 --- a/tools/virt-host-validate-bhyve.c +++ b/tools/virt-host-validate-bhyve.c @@ -22,6 +22,7 @@ #include <config.h> #include <sys/param.h> +#include <sys/module.h> #include <sys/linker.h> #include "virt-host-validate-bhyve.h" @@ -51,6 +52,7 @@ int virHostValidateBhyve(void) int fileid = 0; g_autofree struct kld_file_stat *stat = g_new0(struct kld_file_stat, 1); bool vmm_loaded = false; + bool if_tap_loaded = false; bool pf_loaded = false; bool if_bridge_loaded = false; bool nmdm_loaded = false; @@ -70,7 +72,11 @@ int virHostValidateBhyve(void) nmdm_loaded = true; } + if (modfind("if_tuntap") > 0) + if_tap_loaded = true; + MODULE_STATUS_FAIL(vmm, "will not be able to start VMs"); + MODULE_STATUS_WARN(if_tap, "networking will not work"); MODULE_STATUS_WARN(pf, "network driver will not work"); MODULE_STATUS_WARN(if_bridge, "bridged networking will not work"); MODULE_STATUS_WARN(nmdm, "nmdm console will not work"); -- 2.39.5 (Apple Git-154)

1 0

[PATCH v2] qemu: stop silently narrowing the guest CPU during live migration
by Denis V. Lunev 24 Jun '26

24 Jun '26

qemuDomainMakeCPUMigratable() strips the features that a CPU model marks as added (in src/cpu_map/x86_*.xml) from the migratable definition unless the user requested them explicitly. This keeps a custom CPU migratable to an older destination libvirt whose copy of the model does not know those features yet. A host-model CPU gains nothing from this and is actively harmed by it. By the time it reaches this function host-model has already been expanded into an explicit custom model that is exactly what we ask QEMU for on the source, and host-model is not guaranteed to migrate to an older libvirt in the first place. Stripping the added features only narrows the guest CPU silently on the destination. Every Intel model from Westmere through Sapphire Rapids marks vmx-exit-load-perf-global-ctrl and vmx-entry-load-perf-global-ctrl as added. These control the LOAD_IA32_PERF_GLOBAL_CTRL allowed-1 bits of the MSR_IA32_VMX_{EXIT,ENTRY}_CTLS MSRs, which modern QEMU only advertises when the features are present on the -cpu command line. After a host-model live migration the destination QEMU is started without them, so a nested guest observes different VMX capability MSRs than it did before the migration. A guest that snapshots those MSRs at kvm_intel module load and validates every newly onlined CPU against the snapshot -- Linux does exactly that -- then refuses to bring up a vCPU hot-plugged after the migration: kvm_intel: Inconsistent VMCS config on CPU N kvm: enabling virtualization on CPUN failed smpboot: CPU N is now offline and the guest agent's online attempt returns -EIO. Treat a host-model CPU's features as explicitly requested by building the keep list from the already expanded definition rather than from origCPU. Custom CPUs are unaffected, so their migration compatibility with older destinations is preserved. Signed-off-by: Denis V. Lunev <den(a)openvz.org> --- v1 -> v2: instead of dropping the added-feature stripping altogether (v1), keep it and only stop applying it to a host-model CPU. Custom CPUs still rely on the stripping to stay migratable to an older destination libvirt, which v1 regressed. src/qemu/qemu_domain.c | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c index a43a5c0e4f..e1b805d906 100644 --- a/src/qemu/qemu_domain.c +++ b/src/qemu/qemu_domain.c @@ -5373,12 +5373,18 @@ qemuDomainMakeCPUMigratable(virArch arch, if (virCPUx86GetAddedFeatures(cpu->model, &data.added) < 0) return -1; - /* Drop features marked as added in a cpu model, but only - * when they are not mentioned in origCPU, i.e., when they were not - * explicitly mentioned by the user. - */ + /* Drop features marked as added in a CPU model unless they were + * explicitly requested, so the migratable definition stays + * compatible with destinations that do not know them. For host-model + * the expanded definition is itself the requested CPU, so keep all of + * its features; for a custom CPU keep only those listed in origCPU. */ if (data.added) { - g_auto(GStrv) keep = virCPUDefListExplicitFeatures(origCPU); + g_auto(GStrv) keep = NULL; + + if (origCPU->mode == VIR_CPU_MODE_HOST_MODEL) + keep = virCPUDefListExplicitFeatures(cpu); + else + keep = virCPUDefListExplicitFeatures(origCPU); data.keep = keep; virCPUDefFilterFeatures(cpu, qemuDomainDropAddedCPUFeatures, &data); -- 2.53.0

2 1

[libvirt PATCH 0/3] hyperv: return void more often
by Ján Tomko 24 Jun '26

24 Jun '26

*** BLURB HERE *** Ján Tomko (3): hyperv: return void from hypervAddSimpleParam hyperv: return void from hypervAddEprParam hyperv: return void from hypervAddEmbeddedParam src/hyperv/hyperv_driver.c | 34 +++++++++++++--------------------- src/hyperv/hyperv_wmi.c | 38 ++++++++++---------------------------- src/hyperv/hyperv_wmi.h | 20 ++++++++++---------- 3 files changed, 33 insertions(+), 59 deletions(-) -- 2.54.0

2 4

[PATCH] spec: Enable hyperv driver on RHEL
by Michal Privoznik 24 Jun '26

24 Jun '26

From: Michal Privoznik <mprivozn(a)redhat.com> Resolves: https://redhat.atlassian.net/browse/RHEL-187057 Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> --- Green pipeline: https://gitlab.com/MichalPrivoznik/libvirt/-/pipelines/2625120614 libvirt.spec.in | 1 - 1 file changed, 1 deletion(-) diff --git a/libvirt.spec.in b/libvirt.spec.in index 2fddfcd606..f7f683e1c5 100644 --- a/libvirt.spec.in +++ b/libvirt.spec.in @@ -145,7 +145,6 @@ %define with_vbox 0 %define with_vmware 0 %define with_libxl 0 - %define with_hyperv 0 %define with_lxc 0 %define with_ch 0 %endif -- 2.53.0

2 1