June 2026 - Devel - libvirt List Archives

[PULL 028/106] vhost: drop backend_features field
by Michael S. Tsirkin 14 Jun '26

14 Jun '26

From: Vladimir Sementsov-Ogievskiy <vsementsov(a)yandex-team.ru> This field is mostly unused and sometimes confusing. We even have a TODO-like comment to drop it, the comment is removed in this commit. The field is used to held VHOST_USER_F_PROTOCOL_FEATURES for vhost-user and/or VHOST_NET_F_VIRTIO_NET_HDR for vhost-net (which may be vhost-user-net). But we can simply recalculate these two flags in place from hdev->features, and from net-client for VHOST_NET_F_VIRTIO_NET_HDR. Note: removing field from x-query-virtio-status result is incompatible change. We can do it because the command is unstable. Cc: devel(a)lists.libvirt.org Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov(a)yandex-team.ru> Acked-by: Markus Armbruster <armbru(a)redhat.com> Reviewed-by: Daniil Tatianin <d-tatianin(a)yandex-team.ru> Acked-by: Raphael Norwitz <raphael.s.norwitz(a)gmail.com> Reviewed-by: Michael S. Tsirkin <mst(a)redhat.com> Tested-by: Lei Yang <leiyang(a)redhat.com> Signed-off-by: Michael S. Tsirkin <mst(a)redhat.com> Message-Id: <20260420200339.708640-3-vsementsov(a)yandex-team.ru> --- hw/block/vhost-user-blk.c | 1 - hw/net/vhost_net.c | 26 ++++++++++++++------------ hw/scsi/vhost-scsi.c | 1 - hw/scsi/vhost-user-scsi.c | 1 - hw/virtio/vdpa-dev.c | 1 - hw/virtio/vhost-user.c | 17 ++++++++--------- hw/virtio/virtio-hmp-cmds.c | 2 -- hw/virtio/virtio-qmp.c | 4 ---- include/hw/virtio/vhost.h | 7 ------- qapi/virtio.json | 3 --- 10 files changed, 22 insertions(+), 41 deletions(-) diff --git a/hw/block/vhost-user-blk.c b/hw/block/vhost-user-blk.c index c151e83677..dc99de0263 100644 --- a/hw/block/vhost-user-blk.c +++ b/hw/block/vhost-user-blk.c @@ -348,7 +348,6 @@ static int vhost_user_blk_connect(DeviceState *dev, Error **errp) s->dev.nvqs = s->num_queues; s->dev.vqs = s->vhost_vqs; s->dev.vq_index = 0; - s->dev.backend_features = 0; vhost_dev_set_config_notifier(&s->dev, &blk_ops); diff --git a/hw/net/vhost_net.c b/hw/net/vhost_net.c index 25e9f1fd24..fda90e231e 100644 --- a/hw/net/vhost_net.c +++ b/hw/net/vhost_net.c @@ -52,8 +52,14 @@ int vhost_net_set_config(struct vhost_net *net, const uint8_t *data, void vhost_net_ack_features_ex(struct vhost_net *net, const uint64_t *features) { - virtio_features_copy(net->dev.acked_features_ex, - net->dev.backend_features_ex); + virtio_features_clear(net->dev.acked_features_ex); + if (net->backend == -1) { + net->dev.acked_features = + net->dev.features & (1ULL << VHOST_USER_F_PROTOCOL_FEATURES); + } else if (!qemu_has_vnet_hdr(net->nc)) { + net->dev.acked_features = 1ULL << VHOST_NET_F_VIRTIO_NET_HDR; + } + vhost_ack_features_ex(&net->dev, net->feature_bits, features); } @@ -258,12 +264,9 @@ struct vhost_net *vhost_net_init(VhostNetOptions *options) if (r < 0) { goto fail; } - net->dev.backend_features = qemu_has_vnet_hdr(options->net_backend) - ? 0 : (1ULL << VHOST_NET_F_VIRTIO_NET_HDR); net->backend = r; net->dev.protocol_features = 0; } else { - virtio_features_clear(net->dev.backend_features_ex); net->dev.protocol_features = 0; net->backend = -1; @@ -284,13 +287,12 @@ struct vhost_net *vhost_net_init(VhostNetOptions *options) net->dev.features &= ~(1ULL << VIRTIO_NET_F_MRG_RXBUF); } - if (virtio_features_andnot(missing_features, - net->dev.backend_features_ex, - net->dev.features_ex)) { - fprintf(stderr, "vhost lacks feature mask 0x" VIRTIO_FEATURES_FMT - " for backend\n", VIRTIO_FEATURES_PR(missing_features)); - goto fail; - } + if (!qemu_has_vnet_hdr(options->net_backend) && + (~net->dev.features & (1ULL << VHOST_NET_F_VIRTIO_NET_HDR))) { + fprintf(stderr, "vhost lacks feature mask 0x%llx for backend\n", + ~net->dev.features & (1ULL << VHOST_NET_F_VIRTIO_NET_HDR)); + goto fail; + } } /* Set sane init value. Override when guest acks. */ diff --git a/hw/scsi/vhost-scsi.c b/hw/scsi/vhost-scsi.c index 699863cc10..859888fdba 100644 --- a/hw/scsi/vhost-scsi.c +++ b/hw/scsi/vhost-scsi.c @@ -275,7 +275,6 @@ static void vhost_scsi_realize(DeviceState *dev, Error **errp) vqs = g_new0(struct vhost_virtqueue, vsc->dev.nvqs); vsc->dev.vqs = vqs; vsc->dev.vq_index = 0; - vsc->dev.backend_features = 0; ret = vhost_dev_init(&vsc->dev, (void *)(uintptr_t)vhostfd, VHOST_BACKEND_TYPE_KERNEL, 0, errp); diff --git a/hw/scsi/vhost-user-scsi.c b/hw/scsi/vhost-user-scsi.c index 3612897d4b..5070178dc2 100644 --- a/hw/scsi/vhost-user-scsi.c +++ b/hw/scsi/vhost-user-scsi.c @@ -159,7 +159,6 @@ static int vhost_user_scsi_connect(DeviceState *dev, Error **errp) vsc->dev.nvqs = VIRTIO_SCSI_VQ_NUM_FIXED + vs->conf.num_queues; vsc->dev.vqs = s->vhost_vqs; vsc->dev.vq_index = 0; - vsc->dev.backend_features = 0; ret = vhost_dev_init(&vsc->dev, &s->vhost_user, VHOST_BACKEND_TYPE_USER, 0, errp); diff --git a/hw/virtio/vdpa-dev.c b/hw/virtio/vdpa-dev.c index 4532d63653..06179e402e 100644 --- a/hw/virtio/vdpa-dev.c +++ b/hw/virtio/vdpa-dev.c @@ -104,7 +104,6 @@ static void vhost_vdpa_device_realize(DeviceState *dev, Error **errp) v->dev.vqs = vqs; v->dev.vq_index = 0; v->dev.vq_index_end = v->dev.nvqs; - v->dev.backend_features = 0; v->started = false; ret = vhost_vdpa_get_iova_range(v->vhostfd, &iova_range); diff --git a/hw/virtio/vhost-user.c b/hw/virtio/vhost-user.c index 13c73e7b17..7ce17c5b2d 100644 --- a/hw/virtio/vhost-user.c +++ b/hw/virtio/vhost-user.c @@ -1465,14 +1465,15 @@ static int vhost_user_set_features(struct vhost_dev *dev, int ret; /* - * We need to include any extra backend only feature bits that - * might be needed by our device. Currently this includes the - * VHOST_USER_F_PROTOCOL_FEATURES bit for enabling protocol - * features. + * Don't lose VHOST_USER_F_PROTOCOL_FEATURES, which is vhost-user + * specific. */ - ret = vhost_user_set_u64(dev, VHOST_USER_SET_FEATURES, - features | dev->backend_features, - log_enabled); + if (virtio_has_feature(dev->features, VHOST_USER_F_PROTOCOL_FEATURES)) { + features |= 1ULL << VHOST_USER_F_PROTOCOL_FEATURES; + } + + ret = vhost_user_set_u64(dev, VHOST_USER_SET_FEATURES, features, + log_enabled); if (virtio_has_feature(dev->protocol_features, VHOST_USER_PROTOCOL_F_STATUS)) { @@ -2192,8 +2193,6 @@ static int vhost_user_backend_init(struct vhost_dev *dev, void *opaque, (dev->config_ops && dev->config_ops->vhost_dev_config_notifier); uint64_t protocol_features; - dev->backend_features |= 1ULL << VHOST_USER_F_PROTOCOL_FEATURES; - err = vhost_user_get_u64(dev, VHOST_USER_GET_PROTOCOL_FEATURES, &protocol_features); if (err < 0) { diff --git a/hw/virtio/virtio-hmp-cmds.c b/hw/virtio/virtio-hmp-cmds.c index 1daae482d3..4bf9a3109d 100644 --- a/hw/virtio/virtio-hmp-cmds.c +++ b/hw/virtio/virtio-hmp-cmds.c @@ -176,8 +176,6 @@ void hmp_virtio_status(Monitor *mon, const QDict *qdict) hmp_virtio_dump_features(mon, s->vhost_dev->features); monitor_printf(mon, " Acked features:\n"); hmp_virtio_dump_features(mon, s->vhost_dev->acked_features); - monitor_printf(mon, " Backend features:\n"); - hmp_virtio_dump_features(mon, s->vhost_dev->backend_features); monitor_printf(mon, " Protocol features:\n"); hmp_virtio_dump_protocols(mon, s->vhost_dev->protocol_features); } diff --git a/hw/virtio/virtio-qmp.c b/hw/virtio/virtio-qmp.c index f9cdca50d9..71717c56a4 100644 --- a/hw/virtio/virtio-qmp.c +++ b/hw/virtio/virtio-qmp.c @@ -710,8 +710,6 @@ VirtioStatus *qmp_x_query_virtio_status(const char *path, Error **errp) vdev->guest_features_ex); status->host_features = qmp_decode_features(vdev->device_id, vdev->host_features_ex); - status->backend_features = qmp_decode_features(vdev->device_id, - vdev->backend_features_ex); switch (vdev->device_endian) { case VIRTIO_DEVICE_ENDIAN_LITTLE: @@ -752,8 +750,6 @@ VirtioStatus *qmp_x_query_virtio_status(const char *path, Error **errp) qmp_decode_features(vdev->device_id, hdev->features_ex); status->vhost_dev->acked_features = qmp_decode_features(vdev->device_id, hdev->acked_features_ex); - status->vhost_dev->backend_features = - qmp_decode_features(vdev->device_id, hdev->backend_features_ex); status->vhost_dev->protocol_features = qmp_decode_protocols(hdev->protocol_features); diff --git a/include/hw/virtio/vhost.h b/include/hw/virtio/vhost.h index 3dfec5e15c..e139e05985 100644 --- a/include/hw/virtio/vhost.h +++ b/include/hw/virtio/vhost.h @@ -100,16 +100,9 @@ struct vhost_dev { * * @features: available features provided by the backend * @acked_features: final negotiated features with front-end driver - * - * @backend_features: this is used in a couple of places to either - * store VHOST_USER_F_PROTOCOL_FEATURES to apply to - * VHOST_USER_SET_FEATURES or VHOST_NET_F_VIRTIO_NET_HDR. Its - * future use should be discouraged and the variable retired as - * its easy to confuse with the VirtIO backend_features. */ VIRTIO_DECLARE_FEATURES(features); VIRTIO_DECLARE_FEATURES(acked_features); - VIRTIO_DECLARE_FEATURES(backend_features); /** * @protocol_features: is the vhost-user only feature set by diff --git a/qapi/virtio.json b/qapi/virtio.json index 09dd0e6d05..671f1ad793 100644 --- a/qapi/virtio.json +++ b/qapi/virtio.json @@ -85,8 +85,6 @@ # # @acked-features: vhost_dev acked_features # -# @backend-features: vhost_dev backend_features -# # @protocol-features: vhost_dev protocol_features # # @max-queues: vhost_dev max_queues @@ -106,7 +104,6 @@ 'vq-index': 'int', 'features': 'VirtioDeviceFeatures', 'acked-features': 'VirtioDeviceFeatures', - 'backend-features': 'VirtioDeviceFeatures', 'protocol-features': 'VhostDeviceProtocols', 'max-queues': 'uint64', 'backend-cap': 'uint64', -- MST

1 0

[PATCH 0/4] Remove deprecated Power8E and 8NVL CPUs
by Aditya Gupta 12 Jun '26

12 Jun '26

Overview ======== 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. NOTE: PRE-REQUISITE: Requires following "Testcase improvements for PowerNV" to be merged first: https://lore.kernel.org/qemu-devel/20260610090235.3665904-1-adityag@linux.i… Aditya Gupta (4): ppc/pnv: Replace Power8E with Power11 for 'none' machine test ppc/pnv: Remove Power8E and Power8NVL pnv chips ppc/pnv: Remove Power8E and Power8NVL spapr cores ppc/pnv: Remove Power8E and Power8NVL CPUs docs/about/deprecated.rst | 9 ----- 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/qtest/machine-none-test.c | 2 +- tests/qtest/pnv-xscom.h | 9 ----- 13 files changed, 4 insertions(+), 114 deletions(-) base-commit: de5d8bfd6105d3dd3ae668df9762df244a6d1506 -- 2.54.0

3 13

[PATCH] ci: refresh with 'lcitool manifest'
by Michal Privoznik 12 Jun '26

12 Jun '26

From: Michal Privoznik <mprivozn(a)redhat.com> This switches Alpine from 3.23 to 3.24. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> --- Greenish pipeline: https://gitlab.com/MichalPrivoznik/libvirt/-/pipelines/2596746869 ci/buildenv/{alpine-323.sh => alpine-324.sh} | 0 .../{alpine-323.Dockerfile => alpine-324.Dockerfile} | 2 +- ci/gitlab/builds.yml | 8 ++++---- ci/gitlab/containers.yml | 4 ++-- ci/manifest.yml | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) rename ci/buildenv/{alpine-323.sh => alpine-324.sh} (100%) rename ci/containers/{alpine-323.Dockerfile => alpine-324.Dockerfile} (98%) diff --git a/ci/buildenv/alpine-323.sh b/ci/buildenv/alpine-324.sh similarity index 100% rename from ci/buildenv/alpine-323.sh rename to ci/buildenv/alpine-324.sh diff --git a/ci/containers/alpine-323.Dockerfile b/ci/containers/alpine-324.Dockerfile similarity index 98% rename from ci/containers/alpine-323.Dockerfile rename to ci/containers/alpine-324.Dockerfile index ee1f194808..e2022db8db 100644 --- a/ci/containers/alpine-323.Dockerfile +++ b/ci/containers/alpine-324.Dockerfile @@ -4,7 +4,7 @@ # # https://gitlab.com/libvirt/libvirt-ci -FROM docker.io/library/alpine:3.23 +FROM docker.io/library/alpine:3.24 RUN apk update && \ apk upgrade && \ diff --git a/ci/gitlab/builds.yml b/ci/gitlab/builds.yml index d947170ebe..c11c834f60 100644 --- a/ci/gitlab/builds.yml +++ b/ci/gitlab/builds.yml @@ -59,15 +59,15 @@ x86_64-almalinux-10-clang: TARGET_BASE_IMAGE: docker.io/library/almalinux:10 -x86_64-alpine-323: +x86_64-alpine-324: extends: .native_build_job needs: - - job: x86_64-alpine-323-container + - job: x86_64-alpine-324-container optional: true allow_failure: false variables: - NAME: alpine-323 - TARGET_BASE_IMAGE: docker.io/library/alpine:3.23 + NAME: alpine-324 + TARGET_BASE_IMAGE: docker.io/library/alpine:3.24 x86_64-alpine-edge: diff --git a/ci/gitlab/containers.yml b/ci/gitlab/containers.yml index c74443f565..a4b9a5f03b 100644 --- a/ci/gitlab/containers.yml +++ b/ci/gitlab/containers.yml @@ -21,11 +21,11 @@ x86_64-almalinux-10-container: NAME: almalinux-10 -x86_64-alpine-323-container: +x86_64-alpine-324-container: extends: .container_job allow_failure: false variables: - NAME: alpine-323 + NAME: alpine-324 x86_64-alpine-edge-container: diff --git a/ci/manifest.yml b/ci/manifest.yml index d36e3130d8..67a53bb3d2 100644 --- a/ci/manifest.yml +++ b/ci/manifest.yml @@ -32,7 +32,7 @@ targets: RPM: skip CC: clang - alpine-323: x86_64 + alpine-324: x86_64 alpine-edge: jobs: -- 2.53.0

2 1

[PATCH] lxc: Assign aliases to filesystem devices
by rsmigiel＠redhat.com 11 Jun '26

11 Jun '26

From: Radoslaw Smigielski <rsmigiel(a)redhat.com> From: Radoslaw Smigielski <rsmigiel(a)redhat.com> LXC domains did not assign device aliases to filesystem devices, unlike other device types (consoles, network interfaces, etc.). This change assigns aliases in the format 'fs0', 'fs1', etc. to all filesystem devices during domain startup, following the same pattern used for console devices. Related: https://gitlab.com/libvirt/libvirt/-/work_items/63 Signed-off-by: Radoslaw Smigielski <rsmigiel(a)redhat.com> --- src/lxc/lxc_process.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/lxc/lxc_process.c b/src/lxc/lxc_process.c index 2c0bcb9dd3aa..aae9fcc9dfd1 100644 --- a/src/lxc/lxc_process.c +++ b/src/lxc/lxc_process.c @@ -1350,6 +1350,12 @@ int virLXCProcessStart(virLXCDriver * driver, vm->def->consoles[i]->info.alias = g_strdup_printf("console%zu", i); } + VIR_DEBUG("Setting up filesystem aliases"); + for (i = 0; i < vm->def->nfss; i++) { + g_free(vm->def->fss[i]->info.alias); + vm->def->fss[i]->info.alias = g_strdup_printf("fs%zu", i); + } + VIR_DEBUG("Setting up Interfaces"); if (virLXCProcessSetupInterfaces(driver, vm->def, &veths) < 0) goto cleanup; -- 2.54.0

2 1

[PATCH 0/7] qemu: add async vCPU unplug coverage
by Akash Kulhalli 10 Jun '26

10 Jun '26

This series adds qemuhotplugtest coverage for async vCPU unplug. Async vCPU unplug does not complete at the device_del reply. The guest CPU remains in a pending removal state until QEMU reports DEVICE_DELETED and the QEMU driver handles the resulting process event. The new harness support lets the tests observe that intermediate state and then complete the unplug through the same process-event path used by the driver. The setvcpu coverage exercises both a single-vCPU x86 hotplug entity and a grouped ppc64 hotplug entity. These cases check the pending live XML before completion and the final live/config XML after completion, while also validating the expected vcpu-removed domain events. The setvcpus coverage adds a separate count-based x86 downscale case. This keeps the independent count-to-entity selection path covered without duplicating the grouped-entity coverage from setvcpu. The series also includes a small domain API cleanup to use the vCPU-specific flag aliases consistently in the vCPU entry points. This keeps the implementation and diagnostics aligned with the API being handled. This is a cosmetic change only, since the underlying values are all mapped to their equivalent enums. While adding this coverage, I realised that virsh was being too restrictive in its parameter combination validation; only QEMU does not support both `--async` and `--guest`. Other drivers may wish to support this behaviour. Accordingly, I've changed the behaviour so that virsh now lets the drivers reject the combination if they're unsupported. The decision now rests with the driver, which is more appropriate. Akash Kulhalli (7): qemu: expose process event handler to tests tests: add helper for DEVICE_DELETED events qemuhotplugtest: support async vcpu unplug completion qemuhotplugtest: test setvcpu async unplug qemuhotplugtest: test setvcpus async downscale domain: use vcpu-specific flag aliases consistently virsh: allow async vcpu options to reach drivers -- 2.49.0

2 16

[PATCH 0/3] qemuxmlconftest: Error out if invalid FDs will be passed
by Peter Krempa 10 Jun '26

10 Jun '26

As promised in: [PATCH 00/30] qemuxmlconftest: Use real FDs in test cases these patches make qemuxmlconftest error out if fake FDs are passed to virCommandPassFD. Peter Krempa (3): testutils: Turn 'virTestDummyFDContext' into a proper type virTestDummyFDContext: Add fields to track errors and 'virTestDummyFDContextMarkError' qemuxmlconftest: Fail if test case tried to pass STDIO or invalid fds to 'virCommandPassFD' tests/qemuxml2argvmock.c | 3 +++ tests/qemuxmlconftest.c | 12 +++++++++- tests/testutils.c | 47 ++++++++++++++++++++++++++++++++++------ tests/testutils.h | 8 ++++++- tests/testutilsqemu.h | 4 +++- 5 files changed, 64 insertions(+), 10 deletions(-) -- 2.54.0

2 4

[PATCH] qemu: validate: treat only real backing chains as NVRAM backingStore
by Efim Shevrin 10 Jun '26

10 Jun '26

qemuDomainInitializePflashStorageSource() always attaches a non-NULL src->backingStore used as an empty virStorageSource chain terminator (type VIR_STORAGE_TYPE_NONE). qemuValidateDomainDefNvram() incorrectly interpreted every non-NULL backingStore as a genuine backing overlay and reported VIR_ERR_CONFIG_UNSUPPORTED, so legitimate UEFI/NVRAM setups were rejected. Check virStorageSourceIsBacking(src->backingStore) instead of a plain pointer test so only a real backing node is rejected. Regression introduced in commit bca731d0f562f0842f56ec2206fdbd721a468f5b. Signed-off-by: Fima Shevrin <efim.shevrin(a)virtuozzo.com> --- src/qemu/qemu_validate.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/src/qemu/qemu_validate.c b/src/qemu/qemu_validate.c index 642244b62e..d8347d1964 100644 --- a/src/qemu/qemu_validate.c +++ b/src/qemu/qemu_validate.c @@ -740,7 +740,14 @@ qemuValidateDomainDefNvram(const virDomainDef *def, return -1; } - if (src->backingStore) { + /* qemuDomainInitializePflashStorageSource() always sets + * src->backingStore to a fresh empty virStorageSource as a + * chain terminator, so a plain `if (src->backingStore)` check + * is always true and rejects every UEFI/NVRAM domain after + * upstream commit that introduced the terminator. Use + * virStorageSourceIsBacking() (type != VIR_STORAGE_TYPE_NONE) + * so we only reject genuine backing chains. */ + if (virStorageSourceIsBacking(src->backingStore)) { virReportError(VIR_ERR_CONFIG_UNSUPPORTED, "%s", _("backingStore is not supported with NVRAM")); return -1; -- 2.47.1

2 3

[PATCH v2 03/16] migration/qapi: Rename MigrationStats to MigrationRAMStats
by Peter Xu 10 Jun '26

10 Jun '26

This stats is only about RAM, make it accurate. This paves way for statistics for all devices. Thanks to Markus, who pointed out that docs/devel/qapi-code-gen.rst has a section "Compatibility considerations" stated: Since type names are not visible in the Client JSON Protocol, types may be freely renamed. Even certain refactorings are invisible, such as splitting members from one type into a common base type. Hence this change is not ABI violation according to the document. While at it, touch up the lines to make it read better, correct the restriction on migration status being 'active' or 'completed': over time we grew too many new status that will also report "ram" section. Cc: Daniel P. Berrangé <berrange(a)redhat.com> Cc: devel(a)lists.libvirt.org Reviewed-by: Markus Armbruster <armbru(a)redhat.com> Reviewed-by: Juraj Marcin <jmarcin(a)redhat.com> Reviewed-by: Michal Privoznik <mprivozn(a)redhat.com> Signed-off-by: Peter Xu <peterx(a)redhat.com> --- docs/about/removed-features.rst | 2 +- qapi/migration.json | 10 +++++----- migration/migration-stats.h | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/about/removed-features.rst b/docs/about/removed-features.rst index e75db08410..626162022a 100644 --- a/docs/about/removed-features.rst +++ b/docs/about/removed-features.rst @@ -699,7 +699,7 @@ was superseded by ``sections``. ``query-migrate`` return value member ``skipped`` (removed in 9.1) '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' -Member ``skipped`` of the ``MigrationStats`` struct hasn't been used +Member ``skipped`` of the ``MigrationRAMStats`` struct hasn't been used for more than 10 years. Removed with no replacement. ``migrate`` command option ``inc`` (removed in 9.1) diff --git a/qapi/migration.json b/qapi/migration.json index 7134d4ce47..e3ad3f0604 100644 --- a/qapi/migration.json +++ b/qapi/migration.json @@ -12,7 +12,7 @@ { 'include': 'sockets.json' } ## -# @MigrationStats: +# @MigrationRAMStats: # # Detailed migration status. # @@ -64,7 +64,7 @@ # # Since: 0.14 ## -{ 'struct': 'MigrationStats', +{ 'struct': 'MigrationRAMStats', 'data': {'transferred': 'int', 'remaining': 'int', 'total': 'int' , 'duplicate': 'int', 'normal': 'int', @@ -209,8 +209,8 @@ # If this field is not returned, no migration process has been # initiated # -# @ram: `MigrationStats` containing detailed migration status, only -# returned if status is 'active' or 'completed'(since 1.2) +# @ram: Detailed migration RAM statistics, only returned if migration +# is in progress or completed (since 1.2) # # @xbzrle-cache: `XBZRLECacheStats` containing detailed XBZRLE # migration statistics, only returned if XBZRLE feature is on and @@ -309,7 +309,7 @@ # Since: 0.14 ## { 'struct': 'MigrationInfo', - 'data': {'*status': 'MigrationStatus', '*ram': 'MigrationStats', + 'data': {'*status': 'MigrationStatus', '*ram': 'MigrationRAMStats', '*vfio': 'VfioStats', '*xbzrle-cache': 'XBZRLECacheStats', '*total-time': 'int', diff --git a/migration/migration-stats.h b/migration/migration-stats.h index c0f50144c9..1153520f7a 100644 --- a/migration/migration-stats.h +++ b/migration/migration-stats.h @@ -27,7 +27,7 @@ /* * These are the ram migration statistic counters. It is loosely - * based on MigrationStats. + * based on MigrationRAMStats. */ typedef struct { /* -- 2.53.0

4 5

Reboot events
by Marek Marczykowski-Górecki 10 Jun '26

10 Jun '26

Hi, What should be the events fired when VM requests reboot? Currently the libxl driver fires VIR_DOMAIN_EVENT_STOPPED, and if on_reboot is set to restart, it fires VIR_DOMAIN_EVENT_STARTED next to it (in fact, _STARTED gets fired before _STOPPED here, but it's another issue). What I'd like to do, is to set on_reboot to destroy, but still receive information whether VM requested just shutdown or reboot, so my application (qubesd daemon) can act on it. I see VIR_DOMAIN_EVENT_ID_REBOOT, but it's not used in libxl. What's the intended semantic of it? Should it be fired next to the lifecycle event (VIR_DOMAIN_EVENT_STOPPED/VIR_DOMAIN_EVENT_STARTED)? Or instead? Is it okay to fire it even if on_reboot=destroy? -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab

2 3

[PATCH] lxc: truncate LOOP_GET_STATUS64.lo_file_name for long loop backing paths
by Radoslaw Smigielski 10 Jun '26

10 Jun '26

LXC domains with long file-backed filesystem path fail to start when the backing image path is longer than LO_NAME_SIZE (64 bytes, 63 characters plus NUL). When long file path is passed, virFileLoopDeviceAssociate() -> virStrcpy() fails and user gets missleading error and domain fails to start. Example: <filesystem type='file' accessmode='passthrough'> <driver type='loop' format='raw'/> <source file='/root/demoaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.raw'/> <target dir='/'/> </filesystem> To match losetup behavior we copy the path with virStrcpy() and allow truncation of lo_file_name only if needed, while still calling open() on the unchanged path. Finally log VIR_WARN when the path is expected to be truncated. But still report VIR_ERR_INTERNAL_ERROR for all other virStrcpy() failures. Fixes: https://gitlab.com/libvirt/libvirt/-/work_items/63 Signed-off-by: Radoslaw Smigielski <rsmigiel(a)redhat.com> --- src/util/virfile.c | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/src/util/virfile.c b/src/util/virfile.c index a0c6cb804862..ae33deb8d223 100644 --- a/src/util/virfile.c +++ b/src/util/virfile.c @@ -995,11 +995,18 @@ int virFileLoopDeviceAssociate(const char *file, lo.lo_flags = LO_FLAGS_AUTOCLEAR; - /* Set backing file name for LOOP_GET_STATUS64 queries */ + /* lo_file_name is loop device name, max length is LO_NAME_SIZE bytes. + * Truncate loop device name if file path is longer than LO_NAME_SIZE, + * and still use the full path to open backing file. */ if (virStrcpy((char *) lo.lo_file_name, file, LO_NAME_SIZE) < 0) { - virReportSystemError(errno, - _("Unable to set backing file %1$s"), file); - goto cleanup; + if (strlen(file) >= LO_NAME_SIZE) { + VIR_WARN("Loop backing device name %s truncated to %d bytes.", + file, LO_NAME_SIZE); + } else { + virReportError(VIR_ERR_INTERNAL_ERROR, + _("Unable to set loop lo_file_name for %1$s"), file); + goto cleanup; + } } if ((fsfd = open(file, O_RDWR)) < 0) { -- 2.54.0

3 7

[PATCH 1/2] bhyve: respect domain's on_poweroff action
by Roman Bogorodskiy 10 Jun '26

10 Jun '26

Currently, the bhyve driver shutdown implementation does not take into account domain's on_poweroff action. Update it so it reboots a domain on shutdown when it is configured this way. Signed-off-by: Roman Bogorodskiy <bogorodskiy(a)gmail.com> --- src/bhyve/bhyve_driver.c | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/bhyve/bhyve_driver.c b/src/bhyve/bhyve_driver.c index 2e7a534396..1f904d8958 100644 --- a/src/bhyve/bhyve_driver.c +++ b/src/bhyve/bhyve_driver.c @@ -1077,18 +1077,30 @@ bhyveDomainShutdownFlags(virDomainPtr dom, unsigned int flags) { virDomainObj *vm; int ret = -1; + bhyveDomainObjPrivate *priv; + bool isReboot = false; virCheckFlags(0, -1); if (!(vm = bhyveDomObjFromDomain(dom))) goto cleanup; + if (vm->def->onPoweroff == VIR_DOMAIN_LIFECYCLE_ACTION_RESTART || + vm->def->onPoweroff == VIR_DOMAIN_LIFECYCLE_ACTION_RESTART_RENAME) { + isReboot = true; + VIR_INFO("Domain on_poweroff setting overridden, attempting reboot"); + } + if (virDomainShutdownFlagsEnsureACL(dom->conn, vm->def, flags) < 0) goto cleanup; if (virDomainObjCheckActive(vm) < 0) goto cleanup; + if (isReboot) { + priv = vm->privateData; + bhyveMonitorSetReboot(priv->mon); + } ret = virBhyveProcessShutdown(vm); cleanup: -- 2.52.0

2 3

[PATCH] virt-aa-helper: Prevent spurious denials for AoE disks
by PUSHKARAJ PATIL 10 Jun '26

10 Jun '26

virt-aa-helper calls virStorageSourceGetMetadata before adding a disk path to a domain's apparmor profile. This probes the device and may trigger an AppArmor denial when the disk is an AoE device under /dev/etherd/. The return value of virStorageSourceGetMetadata is not checked, so the denial has no functional impact but results in noisy dmesg logs. Explicitly deny read access to /dev/etherd/e*.* in the virt-aa-helper profile to avoid these spurious denials. Co-Authored-By: Peter Krempa <pkrempa(a)redhat.com> Signed-off-by: PUSHKARAJ PATIL <pushkaraj.patil(a)in.ibm.com> --- src/security/apparmor/usr.lib.libvirt.virt-aa-helper.in | 1 + 1 file changed, 1 insertion(+) diff --git a/src/security/apparmor/usr.lib.libvirt.virt-aa-helper.in b/src/security/apparmor/usr.lib.libvirt.virt-aa-helper.in index e209a8bff7..1f1b80b9f9 100644 --- a/src/security/apparmor/usr.lib.libvirt.virt-aa-helper.in +++ b/src/security/apparmor/usr.lib.libvirt.virt-aa-helper.in @@ -38,6 +38,7 @@ profile virt-aa-helper @libexecdir@/virt-aa-helper { deny /dev/dm-* r, deny /dev/drbd[0-9]* r, deny /dev/dasd* r, + deny /dev/etherd/e*.* r, deny /dev/nvme* r, deny /dev/zd[0-9]* r, deny /dev/mapper/ r, -- 2.50.1 (Apple Git-155)

3 2

[PATCH] bhyve: support populating SMBIOS fields
by Roman Bogorodskiy 10 Jun '26

10 Jun '26

bhyve supports populating SMBIOS fields. Each field is set using the -o option, such as: -o system.product_name=Virt-Manager There are 4 groups of options: - bios.* - system.* - board.* - chassis.* As a side note, the '-o' option can be used for setting options not related to the SMBIOS fields. Extend virBhyveProcessBuildBhyveCmd() to build the appropriate arguments for what's specified in the domain's `<sysinfo type='smbios'>` section. Signed-off-by: Roman Bogorodskiy <bogorodskiy(a)gmail.com> --- src/bhyve/bhyve_command.c | 147 ++++++++++++++++++ .../x86_64/bhyvexml2argv-sysinfo-smbios.args | 29 ++++ .../bhyvexml2argv-sysinfo-smbios.ldargs | 4 + .../x86_64/bhyvexml2argv-sysinfo-smbios.xml | 52 +++++++ tests/bhyvexml2argvtest.c | 1 + 5 files changed, 233 insertions(+) create mode 100644 tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.args create mode 100644 tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.ldargs create mode 100644 tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.xml diff --git a/src/bhyve/bhyve_command.c b/src/bhyve/bhyve_command.c index 1da344f503..941b48eb66 100644 --- a/src/bhyve/bhyve_command.c +++ b/src/bhyve/bhyve_command.c @@ -928,6 +928,148 @@ bhyveBuildFSArgStr(const virDomainDef *def G_GNUC_UNUSED, return 0; } +static void +bhyveBuildSysinfoBiosArgStr(virSysinfoBIOSDef *def, + virCommand *cmd) +{ + if (def->vendor) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "bios.vendor", def->vendor); + } + + if (def->version) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "bios.version", def->version); + } + + if (def->date) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "bios.release_date", def->date); + } +} + +static void +bhyveBuildSysinfoSystemArgStr(virSysinfoSystemDef *def, + virCommand *cmd) +{ + if (def->manufacturer) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "system.manufacturer", def->manufacturer); + } + + if (def->product) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "system.product_name", def->product); + } + + if (def->serial) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "system.serial_number", def->serial); + } + + if (def->sku) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "system.sku", def->sku); + } + + if (def->version) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "system.version", def->version); + } +} + +static void +bhyveBuildSysinfoBaseBoardArgStr(virSysinfoBaseBoardDef *def, + virCommand *cmd) +{ + if (def->manufacturer) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "board.manufacturer", def->manufacturer); + } + + if (def->product) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "board.product_name", def->product); + } + + if (def->version) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "board.version", def->version); + } + + if (def->serial) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "board.serial_number", def->serial); + } + + if (def->asset) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "board.asset_tag", def->asset); + } + + if (def->location) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "board.location", def->location); + } +} + +static void +bhyveBuildSysinfoChassisArgStr(virSysinfoChassisDef *def, + virCommand *cmd) +{ + if (def->manufacturer) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "chassis.manufacturer", def->manufacturer); + } + + if (def->version) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "chassis.version", def->version); + } + + if (def->serial) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "chassis.serial_number", def->serial); + } + + if (def->asset) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "chassis.asset_tag", def->asset); + } + + if (def->sku) { + virCommandAddArg(cmd, "-o"); + virCommandAddArgPair(cmd, "chassis.sku", def->sku); + } +} + +static int +bhyveBuildSysinfoArgStr(virSysinfoDef *sysinfo, + virCommand *cmd) +{ + size_t i; + + if (sysinfo->bios) + bhyveBuildSysinfoBiosArgStr(sysinfo->bios, cmd); + + if (sysinfo->system) + bhyveBuildSysinfoSystemArgStr(sysinfo->system, cmd); + + if (sysinfo->nbaseBoard > 1) { + virReportError(VIR_ERR_CONFIG_UNSUPPORTED, "%s", + _("bhyve does not support more than one entry to Type 2 in SMBIOS table")); + return -1; + } + + for (i = 0; i < sysinfo->nbaseBoard; i++) + bhyveBuildSysinfoBaseBoardArgStr(&sysinfo->baseBoard[i], cmd); + + if (sysinfo->chassis) + bhyveBuildSysinfoChassisArgStr(sysinfo->chassis, cmd); + + return 0; +} + virCommand * virBhyveProcessBuildBhyveCmd(struct _bhyveConn *driver, virDomainDef *def, bool dryRun) @@ -1164,6 +1306,11 @@ virBhyveProcessBuildBhyveCmd(struct _bhyveConn *driver, virDomainDef *def, if (bhyveBuildHostdevArgStr(def, cmd) < 0) return NULL; + for (i = 0; i < def->nsysinfo; i++) + if (def->sysinfo[i]->type == VIR_SYSINFO_SMBIOS) + if (bhyveBuildSysinfoArgStr(def->sysinfo[i], cmd) < 0) + return NULL; + virCommandAddArg(cmd, def->name); return g_steal_pointer(&cmd); diff --git a/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.args b/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.args new file mode 100644 index 0000000000..f4894a60b0 --- /dev/null +++ b/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.args @@ -0,0 +1,29 @@ +bhyve \ +-c 1 \ +-m 214 \ +-u \ +-H \ +-P \ +-s 0:0,hostbridge \ +-s 2:0,ahci,hd:/tmp/freebsd.img \ +-s 3:0,virtio-net,faketapdev,mac=52:54:00:b9:94:02 \ +-o bios.vendor=LENOVO \ +-o bios.version=14.1 \ +-o bios.release_date=11/24/2025 \ +-o system.manufacturer=Fedora \ +-o system.product_name=Virt-Manager \ +-o system.serial_number=xxx-yyy-zzz \ +-o system.sku=0000 \ +-o system.version=0.9.4 \ +-o board.manufacturer=LENOVO \ +-o board.product_name=20BE0061MC \ +-o 'board.version=0B98401 Pro' \ +-o board.serial_number=W1KS427111E \ +-o 'board.asset_tag=Asset Tag' \ +-o board.location=Nowhere \ +-o 'chassis.manufacturer=Dell Inc.' \ +-o chassis.version=2.12 \ +-o chassis.serial_number=65X0XF2 \ +-o chassis.asset_tag=40000101 \ +-o chassis.sku=Type3Sku1 \ +bhyve diff --git a/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.ldargs b/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.ldargs new file mode 100644 index 0000000000..5905f4b3e6 --- /dev/null +++ b/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.ldargs @@ -0,0 +1,4 @@ +bhyveload \ +-m 214 \ +-d /tmp/freebsd.img \ +bhyve diff --git a/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.xml b/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.xml new file mode 100644 index 0000000000..111421211c --- /dev/null +++ b/tests/bhyvexml2argvdata/x86_64/bhyvexml2argv-sysinfo-smbios.xml @@ -0,0 +1,52 @@ +<domain type='bhyve'> + <name>bhyve</name> + <uuid>df3be7e7-a104-11e3-aeb0-50e5492bd3dc</uuid> + <memory>219136</memory> + <vcpu>1</vcpu> + <os> + <type>hvm</type> + </os> + <sysinfo type='smbios'> + <bios> + <entry name='vendor'>LENOVO</entry> + <entry name='version'>14.1</entry> + <entry name='date'>11/24/2025</entry> + </bios> + <system> + <entry name='manufacturer'>Fedora</entry> + <entry name='product'>Virt-Manager</entry> + <entry name='version'>0.9.4</entry> + <entry name='serial'>xxx-yyy-zzz</entry> + <entry name='sku'>0000</entry> + </system> + <baseBoard> + <entry name='manufacturer'>LENOVO</entry> + <entry name='product'>20BE0061MC</entry> + <entry name='version'>0B98401 Pro</entry> + <entry name='serial'>W1KS427111E</entry> + <entry name='asset'>Asset Tag</entry> + <entry name='location'>Nowhere</entry> + </baseBoard> + <chassis> + <entry name='manufacturer'>Dell Inc.</entry> + <entry name='version'>2.12</entry> + <entry name='serial'>65X0XF2</entry> + <entry name='asset'>40000101</entry> + <entry name='sku'>Type3Sku1</entry> + </chassis> + </sysinfo> + <devices> + <disk type='file'> + <driver name='file' type='raw'/> + <source file='/tmp/freebsd.img'/> + <target dev='hda' bus='sata'/> + <address type='drive' controller='0' bus='0' target='2' unit='0'/> + </disk> + <interface type='bridge'> + <mac address='52:54:00:b9:94:02'/> + <model type='virtio'/> + <source bridge="virbr0"/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> + </interface> + </devices> +</domain> diff --git a/tests/bhyvexml2argvtest.c b/tests/bhyvexml2argvtest.c index 818b51e178..71322d1330 100644 --- a/tests/bhyvexml2argvtest.c +++ b/tests/bhyvexml2argvtest.c @@ -303,6 +303,7 @@ mymain(void) DO_TEST_FAILURE("virtio-console-invalid-path"); DO_TEST("memtune"); DO_TEST_FAILURE("memtune-unsupported-params"); + DO_TEST("sysinfo-smbios"); /* Address allocation tests */ DO_TEST("addr-single-sata-disk"); -- 2.52.0

2 1

[PATCH 1/1] qemu: Inherit SCSI controller model from existing peers
by Denis V. Lunev 09 Jun '26

09 Jun '26

virDomainDefMaybeAddHostdevSCSIcontroller() already inherits the model of an existing SCSI controller when auto-adding peers driven by a hostdev whose drive address overflows the highest declared idx. virDomainDefAddDiskControllersForType(), called for the disk-driven analogue, does not -- it passes model=-1 unconditionally. The unspecified peers then arrive at qemuDomainDefaultSCSIControllerModel() and pick up whichever model the capability cascade settles on (typically lsilogic). A user-declared virtio-scsi controller at idx 0 ends up alongside auto-added lsilogic peers at idx 1+. Plug the same inheritance into qemuDomainDefaultSCSIControllerModel() itself so it covers both the disk-driven path and any other caller that arrives with an unresolved model. The function already prefers architectural defaults (PSeries, ARM virt, RISC-V virt, LoongArch, s390, built-in ESP) over capabilities; peer inheritance slots in just before the capability cascade. A virtio-scsi domain keeps the new peers as virtio-scsi; an lsisas1068 domain stays lsisas1068; a fresh domain with no SCSI controllers still gets the cap-driven default. controller-scsi-auto, the only existing test that flows through this helper, is unaffected (it has no peers to inherit from). controller-scsi-inherit-model covers the new behavior. Signed-off-by: Denis V. Lunev <den(a)openvz.org> --- src/qemu/qemu_domain.c | 15 +++++++ ...ller-scsi-inherit-model.x86_64-latest.args | 38 ++++++++++++++++ ...oller-scsi-inherit-model.x86_64-latest.xml | 45 +++++++++++++++++++ .../controller-scsi-inherit-model.xml | 20 +++++++++ tests/qemuxmlconftest.c | 1 + 5 files changed, 119 insertions(+) create mode 100644 tests/qemuxmlconfdata/controller-scsi-inherit-model.x86_64-latest.args create mode 100644 tests/qemuxmlconfdata/controller-scsi-inherit-model.x86_64-latest.xml create mode 100644 tests/qemuxmlconfdata/controller-scsi-inherit-model.xml diff --git a/src/qemu/qemu_domain.c b/src/qemu/qemu_domain.c index 84c8645259..21f2641521 100644 --- a/src/qemu/qemu_domain.c +++ b/src/qemu/qemu_domain.c @@ -4289,6 +4289,8 @@ virDomainControllerModelSCSI qemuDomainDefaultSCSIControllerModel(const virDomainDef *def, virQEMUCaps *qemuCaps) { + size_t i; + /* For machine types with built-in SCSI controllers, the choice * of model is obvious */ if (qemuDomainHasBuiltinESP(def)) @@ -4305,6 +4307,19 @@ qemuDomainDefaultSCSIControllerModel(const virDomainDef *def, if (qemuDomainIsPSeries(def)) return VIR_DOMAIN_CONTROLLER_MODEL_SCSI_IBMVSCSI; + /* Inherit the model from any peer SCSI controller already + * resolved on this domain. */ + for (i = 0; i < def->ncontrollers; i++) { + const virDomainControllerDef *peer = def->controllers[i]; + + if (peer->type != VIR_DOMAIN_CONTROLLER_TYPE_SCSI) + continue; + if (peer->model == VIR_DOMAIN_CONTROLLER_MODEL_SCSI_DEFAULT || + peer->model == VIR_DOMAIN_CONTROLLER_MODEL_SCSI_AUTO) + continue; + return peer->model; + } + /* If there is no preference, base the choice on device * availability. In this case, lsilogic is favored over * virtio-scsi for backwards compatibility reasons */ diff --git a/tests/qemuxmlconfdata/controller-scsi-inherit-model.x86_64-latest.args b/tests/qemuxmlconfdata/controller-scsi-inherit-model.x86_64-latest.args new file mode 100644 index 0000000000..2bcd9ed92f --- /dev/null +++ b/tests/qemuxmlconfdata/controller-scsi-inherit-model.x86_64-latest.args @@ -0,0 +1,38 @@ +LC_ALL=C \ +PATH=/bin \ +HOME=/var/lib/libvirt/qemu/domain--1-guest \ +USER=test \ +LOGNAME=test \ +XDG_DATA_HOME=/var/lib/libvirt/qemu/domain--1-guest/.local/share \ +XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain--1-guest/.cache \ +XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain--1-guest/.config \ +/usr/bin/qemu-system-x86_64 \ +-name guest=guest,debug-threads=on \ +-S \ +-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain--1-guest/master-key.aes"}' \ +-machine pc,usb=off,dump-guest-core=off,memory-backend=pc.ram,acpi=off \ +-accel tcg \ +-cpu qemu64 \ +-m size=219136k \ +-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":224395264}' \ +-overcommit mem-lock=off \ +-smp 8,sockets=8,cores=1,threads=1 \ +-uuid c7a5fdbd-edaf-9455-926a-d65c16db1809 \ +-display none \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=@mon-fd@,server=on,wait=off \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot strict=on \ +-device '{"driver":"virtio-scsi-pci","id":"scsi0","bus":"pci.0","addr":"0x2"}' \ +-device '{"driver":"virtio-scsi-pci","id":"scsi1","bus":"pci.0","addr":"0x3"}' \ +-device '{"driver":"virtio-scsi-pci","id":"scsi2","bus":"pci.0","addr":"0x4"}' \ +-device '{"driver":"virtio-scsi-pci","id":"scsi3","bus":"pci.0","addr":"0x5"}' \ +-blockdev '{"driver":"file","filename":"/tmp/data.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage"}' \ +-device '{"driver":"scsi-hd","bus":"scsi3.0","channel":0,"scsi-id":0,"lun":3,"device_id":"drive-scsi3-0-0-3","drive":"libvirt-1-format","id":"scsi3-0-0-3","bootindex":1}' \ +-audiodev '{"id":"audio1","driver":"none"}' \ +-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ +-msg timestamp=on diff --git a/tests/qemuxmlconfdata/controller-scsi-inherit-model.x86_64-latest.xml b/tests/qemuxmlconfdata/controller-scsi-inherit-model.x86_64-latest.xml new file mode 100644 index 0000000000..b971c89a1b --- /dev/null +++ b/tests/qemuxmlconfdata/controller-scsi-inherit-model.x86_64-latest.xml @@ -0,0 +1,45 @@ +<domain type='qemu'> + <name>guest</name> + <uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid> + <memory unit='KiB'>219136</memory> + <currentMemory unit='KiB'>219136</currentMemory> + <vcpu placement='static'>8</vcpu> + <os> + <type arch='x86_64' machine='pc'>hvm</type> + <boot dev='hd'/> + </os> + <cpu mode='custom' match='exact' check='none'> + <model fallback='forbid'>qemu64</model> + </cpu> + <clock offset='utc'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2'/> + <source file='/tmp/data.qcow2'/> + <target dev='sdy' bus='scsi'/> + <address type='drive' controller='3' bus='0' target='0' unit='3'/> + </disk> + <controller type='scsi' index='0' model='virtio-scsi'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> + </controller> + <controller type='scsi' index='1' model='virtio-scsi'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> + </controller> + <controller type='scsi' index='2' model='virtio-scsi'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> + </controller> + <controller type='scsi' index='3' model='virtio-scsi'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> + </controller> + <controller type='usb' index='0' model='none'/> + <controller type='pci' index='0' model='pci-root'/> + <input type='mouse' bus='ps2'/> + <input type='keyboard' bus='ps2'/> + <audio id='1' type='none'/> + <memballoon model='none'/> + </devices> +</domain> diff --git a/tests/qemuxmlconfdata/controller-scsi-inherit-model.xml b/tests/qemuxmlconfdata/controller-scsi-inherit-model.xml new file mode 100644 index 0000000000..45e96b7ea1 --- /dev/null +++ b/tests/qemuxmlconfdata/controller-scsi-inherit-model.xml @@ -0,0 +1,20 @@ +<domain type='qemu'> + <name>guest</name> + <uuid>c7a5fdbd-edaf-9455-926a-d65c16db1809</uuid> + <memory unit='KiB'>219136</memory> + <vcpu placement='static'>8</vcpu> + <os> + <type arch='x86_64' machine='pc'>hvm</type> + </os> + <devices> + <emulator>/usr/bin/qemu-system-x86_64</emulator> + <controller type='scsi' index='0' model='virtio-scsi'/> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2'/> + <source file='/tmp/data.qcow2'/> + <target dev='sdy' bus='scsi'/> + </disk> + <controller type='usb' index='0' model='none'/> + <memballoon model='none'/> + </devices> +</domain> diff --git a/tests/qemuxmlconftest.c b/tests/qemuxmlconftest.c index 8e0f4bcb4f..7a441c1fa2 100644 --- a/tests/qemuxmlconftest.c +++ b/tests/qemuxmlconftest.c @@ -1690,6 +1690,7 @@ mymain(void) DO_TEST_CAPS_LATEST_PARSE_ERROR("disk-scsi-product-length"); DO_TEST_CAPS_LATEST("controller-virtio-scsi"); DO_TEST_CAPS_LATEST("controller-scsi-auto"); + DO_TEST_CAPS_LATEST("controller-scsi-inherit-model"); DO_TEST_FULL("controller-scsi-default-unavailable", ".x86_64-latest", ARG_CAPS_ARCH, "x86_64", ARG_CAPS_VER, "latest", -- 2.51.0

3 2

[PATCH v3 0/2] allow migrations with the ext transport
by Mark Cave-Ayland 09 Jun '26

09 Jun '26

[MCA: I've now adopted these patches from Sergey] Hello, I have a use case for live-migration where the socket of the destination libvirtd is proxied by an mTLS WebSocket proxy. Since there is no WebSocket support in Libvirt, I've decided to use the existing ext transport and point it to a proxy binary on the source host of live-migration. While doing that, I've discovered a couple of roadblocks: 1. There is no way of passing cmdline arguments to the ext program 2. Live-migrations using ext transport fail localhost checks This short series addresses those limitations. v2 -> v3: - fix passing of extArgs v1 -> v2: - new way of passing argv Sergey Dyasli (2): remote: allow passing argv to the ext transport remote: allow migrations with the ext transport src/libvirt-domain.c | 8 +++++--- src/remote/remote_driver.c | 30 ++++++++++++++++++++++++++---- src/util/viruri.c | 32 ++++++++++++++++++++++++++++++++ src/util/viruri.h | 2 ++ 4 files changed, 65 insertions(+), 7 deletions(-) -- 2.43.0

2 5

[PATCH 0/3] implement a few guest agent based APIs
by Roman Bogorodskiy 09 Jun '26

09 Jun '26

Roman Bogorodskiy (3): bhyve: implement domain{Get,Set}Time APIs bhyve: implement domainSetUserPassword API bhyve: implement domainAuthorizedSSHKeys{Get,Set} APIs src/bhyve/bhyve_driver.c | 225 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 225 insertions(+) -- 2.52.0

2 4

[PATCH 0/2] bhyve: guest agent bugfixes
by Roman Bogorodskiy 09 Jun '26

09 Jun '26

Roman Bogorodskiy (2): bhyve: process: properly handle misconfigured agent bhyve: fix domainQemuAgentCommand src/bhyve/bhyve_driver.c | 35 +---------------------------------- src/bhyve/bhyve_process.c | 11 +++++++---- 2 files changed, 8 insertions(+), 38 deletions(-) -- 2.52.0

2 3

[PATCH] ci: refresh with 'lcitool manifest'
by Daniel P. Berrangé 09 Jun '26

09 Jun '26

From: Daniel P. Berrangé <berrange(a)redhat.com> This brings in a workaround for broken deps with OpenSUSE repos, by allowing downgrades. Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com> --- ci/buildenv/opensuse-leap-15.sh | 2 +- ci/buildenv/opensuse-tumbleweed.sh | 2 +- ci/containers/opensuse-leap-15.Dockerfile | 2 +- ci/containers/opensuse-tumbleweed.Dockerfile | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/ci/buildenv/opensuse-leap-15.sh b/ci/buildenv/opensuse-leap-15.sh index 986c27a4a7..55d9fe5974 100644 --- a/ci/buildenv/opensuse-leap-15.sh +++ b/ci/buildenv/opensuse-leap-15.sh @@ -7,7 +7,7 @@ function install_buildenv() { zypper update -y zypper addrepo -fc https://download.opensuse.org/update/leap/15.6/backports/openSUSE:Backports… - zypper install -y \ + zypper install -y --allow-downgrade \ audit-devel \ augeas \ augeas-lenses \ diff --git a/ci/buildenv/opensuse-tumbleweed.sh b/ci/buildenv/opensuse-tumbleweed.sh index a01e3c35d0..ff1c4800e4 100644 --- a/ci/buildenv/opensuse-tumbleweed.sh +++ b/ci/buildenv/opensuse-tumbleweed.sh @@ -6,7 +6,7 @@ function install_buildenv() { zypper dist-upgrade -y - zypper install -y \ + zypper install -y --allow-downgrade \ audit-devel \ augeas \ augeas-lenses \ diff --git a/ci/containers/opensuse-leap-15.Dockerfile b/ci/containers/opensuse-leap-15.Dockerfile index bf605dc22f..8857f35ce0 100644 --- a/ci/containers/opensuse-leap-15.Dockerfile +++ b/ci/containers/opensuse-leap-15.Dockerfile @@ -8,7 +8,7 @@ FROM registry.opensuse.org/opensuse/leap:15.6 RUN zypper update -y && \ zypper addrepo -fc https://download.opensuse.org/update/leap/15.6/backports/openSUSE:Backports… && \ - zypper install -y \ + zypper install -y --allow-downgrade \ audit-devel \ augeas \ augeas-lenses \ diff --git a/ci/containers/opensuse-tumbleweed.Dockerfile b/ci/containers/opensuse-tumbleweed.Dockerfile index e8062d2849..07c930b48b 100644 --- a/ci/containers/opensuse-tumbleweed.Dockerfile +++ b/ci/containers/opensuse-tumbleweed.Dockerfile @@ -7,7 +7,7 @@ FROM registry.opensuse.org/opensuse/tumbleweed:latest RUN zypper dist-upgrade -y && \ - zypper install -y \ + zypper install -y --allow-downgrade \ audit-devel \ augeas \ augeas-lenses \ -- 2.54.0

2 1

[PATCH] domaincapstest: Drop support for old qemu
by Michal Privoznik 08 Jun '26

08 Jun '26

From: Michal Privoznik <mprivozn(a)redhat.com> The aim of domaincapstest is to check domain capabilities XML with respect to qemu capabilities. And we used to have old qemu capabilities where only TPM-1.2 was supported. But as of v12.4.0-rc1~130 QEMU-7.2 or newer is required which means the code that's handling older QEMUs is required no more. Drop it. Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> --- tests/domaincapstest.c | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/tests/domaincapstest.c b/tests/domaincapstest.c index ed0210678f..ec2ac8cb36 100644 --- a/tests/domaincapstest.c +++ b/tests/domaincapstest.c @@ -298,15 +298,7 @@ doTestQemuInternal(const char *version, version, typestr, mach, arch, variant, flag); - if (STRPREFIX(version, "3.") || - STRPREFIX(version, "4.") || - STRPREFIX(version, "5.")) { - g_setenv(TEST_TPM_ENV_VAR, TPM_VER_1_2, true); - } else if (STRPREFIX(version, "6.")) { - g_setenv(TEST_TPM_ENV_VAR, TPM_VER_1_2 TPM_VER_2_0, true); - } else { - g_setenv(TEST_TPM_ENV_VAR, TPM_VER_2_0, true); - } + g_setenv(TEST_TPM_ENV_VAR, TPM_VER_2_0, true); rc = virTestRun(name, test_virDomainCapsFormat, &data); -- 2.53.0

3 2

[PATCH 0/4] qemu: add API to ammounce guest interfaces to the network
by Laine Stump 05 Jun '26

05 Jun '26

This provides a supported method of executing QEMU's "self-announce" command, which injects gratuitous ARP packets into the outgoing data stream of guest interfaces. Resolves: https://redhat.atlassian.net/browse/RHEL-7047 Laine Stump (4): qemu: new monitor function qemuMonitorAnnounceSelf() API: Introduce virDomainAnnounceInterface qemu: implement virDomainAnnounceInterface() API virsh: new command "domifannounce" docs/manpages/virsh.rst | 41 +++++++++++++++ include/libvirt/libvirt-domain.h | 46 +++++++++++++++++ src/driver-hypervisor.h | 8 +++ src/libvirt-domain.c | 65 +++++++++++++++++++++++ src/libvirt_public.syms | 5 ++ src/qemu/qemu_driver.c | 81 ++++++++++++++++++++++++++++- src/qemu/qemu_monitor.c | 13 +++++ src/qemu/qemu_monitor.h | 8 +++ src/qemu/qemu_monitor_json.c | 55 ++++++++++++++++++++ src/qemu/qemu_monitor_json.h | 8 +++ src/remote/remote_driver.c | 1 + src/remote/remote_protocol.x | 19 ++++++- src/remote_protocol-structs | 10 ++++ tools/virsh-domain.c | 88 ++++++++++++++++++++++++++++++++ 14 files changed, 446 insertions(+), 2 deletions(-) -- 2.54.0

3 14

[PATCH RFC 0/6] Add qemu-vnc support
by marcandre.lureau＠redhat.com 04 Jun '26

04 Jun '26

From: Marc-André Lureau <marcandre.lureau(a)redhat.com> Hi, This series allows to run the QEMU VNC server in a standalone process. The qemu-vnc binary is aimed to be released with QEMU 11.1. It is still being reviewed (https://patchew.org/QEMU/20260410-qemu-vnc-v2-0-231416f76dc3@redhat.com/) The standalone VNC activates automatically when a domain has both <graphics type='dbus'/> (bus mode) and <graphics type='vnc'/>, and the qemu-vnc binary is available. Comments welcome! Marc-André Lureau (6): qemu: add standalone VNC state directory qemu: add qemu-vnc configuration qemu: add qemu-vnc helper unit qemu: integrate standalone VNC in domain lifecycle qemu: wire up standalone VNC in driver APIs qemu: add tests for standalone VNC graphics po/POTFILES | 1 + src/qemu/libvirtd_qemu.aug | 1 + src/qemu/meson.build | 1 + src/qemu/qemu.conf.in | 8 + src/qemu/qemu_command.c | 2 + src/qemu/qemu_conf.c | 8 + src/qemu/qemu_conf.h | 2 + src/qemu/qemu_domain.c | 1 + src/qemu/qemu_domain.h | 2 + src/qemu/qemu_driver.c | 68 ++- src/qemu/qemu_extdevice.c | 13 +- src/qemu/qemu_hotplug.c | 12 + src/qemu/qemu_process.c | 40 +- src/qemu/qemu_vnc.c | 407 ++++++++++++++++++ src/qemu/qemu_vnc.h | 41 ++ src/qemu/test_libvirtd_qemu.aug.in | 1 + ...hics-vnc-standalone-p2p.x86_64-latest.args | 34 ++ ...phics-vnc-standalone-p2p.x86_64-latest.xml | 40 ++ .../graphics-vnc-standalone-p2p.xml | 39 ++ ...s-vnc-standalone-socket.x86_64-latest.args | 33 ++ ...cs-vnc-standalone-socket.x86_64-latest.xml | 40 ++ .../graphics-vnc-standalone-socket.xml | 40 ++ ...graphics-vnc-standalone.x86_64-latest.args | 33 ++ .../graphics-vnc-standalone.x86_64-latest.xml | 40 ++ .../graphics-vnc-standalone.xml | 40 ++ tests/qemuxmlconftest.c | 4 + tests/testutilsqemu.c | 9 + 27 files changed, 950 insertions(+), 10 deletions(-) create mode 100644 src/qemu/qemu_vnc.c create mode 100644 src/qemu/qemu_vnc.h create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-p2p.x86_64-latest.args create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-p2p.x86_64-latest.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-p2p.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-socket.x86_64-latest.args create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-socket.x86_64-latest.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone-socket.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone.x86_64-latest.args create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone.x86_64-latest.xml create mode 100644 tests/qemuxmlconfdata/graphics-vnc-standalone.xml -- 2.53.0

3 10

[PATCH 0/3] tests: Add capability dump data for the qemu-11.1 dev cycle
by Peter Krempa 03 Jun '26

03 Jun '26

Peter Krempa (3): qemublocktest: Skip schema validation on 'gluster' backend tests qemucapabilitiestest: Add data for the qemu-11.1 dev cycle (x86_64) qemucapabilitiestest: Add data for the qemu-11.1 dev cycle (aarch64) .../qemu_11.1.0-q35.x86_64-expanded.xml | 1856 + .../qemu_11.1.0-q35.x86_64-supported.xml | 1738 + .../domaincapsdata/qemu_11.1.0-q35.x86_64.xml | 1731 + .../domaincapsdata/qemu_11.1.0-tcg.x86_64.xml | 2856 + .../qemu_11.1.0-virt.aarch64.xml | 265 + tests/domaincapsdata/qemu_11.1.0.aarch64.xml | 265 + tests/domaincapsdata/qemu_11.1.0.x86_64.xml | 1729 + tests/qemublocktest.c | 31 +- .../caps_11.1.0_aarch64.replies | 39323 ++++++++++++ .../caps_11.1.0_aarch64.xml | 536 + .../caps_11.1.0_x86_64.replies | 49275 ++++++++++++++++ .../caps_11.1.0_x86_64.xml | 5767 ++ ...host-model-fallback-kvm.x86_64-11.0.0.args | 2 +- ...-host-model-fallback-kvm.x86_64-11.0.0.xml | 2 +- ...host-model-fallback-tcg.x86_64-11.0.0.args | 2 +- ...-host-model-fallback-tcg.x86_64-11.0.0.xml | 2 +- .../cpu-host-model-kvm.x86_64-11.0.0.args | 2 +- .../cpu-host-model-kvm.x86_64-11.0.0.xml | 2 +- ...st-model-nofallback-kvm.x86_64-11.0.0.args | 2 +- ...ost-model-nofallback-kvm.x86_64-11.0.0.xml | 2 +- ...st-model-nofallback-tcg.x86_64-11.0.0.args | 2 +- ...ost-model-nofallback-tcg.x86_64-11.0.0.xml | 2 +- .../cpu-host-model-tcg.x86_64-11.0.0.args | 2 +- .../cpu-host-model-tcg.x86_64-11.0.0.xml | 2 +- 24 files changed, 105373 insertions(+), 23 deletions(-) create mode 100644 tests/domaincapsdata/qemu_11.1.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0-q35.x86_64.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0-tcg.x86_64.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0-virt.aarch64.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0.aarch64.xml create mode 100644 tests/domaincapsdata/qemu_11.1.0.x86_64.xml create mode 100644 tests/qemucapabilitiesdata/caps_11.1.0_aarch64.replies create mode 100644 tests/qemucapabilitiesdata/caps_11.1.0_aarch64.xml create mode 100644 tests/qemucapabilitiesdata/caps_11.1.0_x86_64.replies create mode 100644 tests/qemucapabilitiesdata/caps_11.1.0_x86_64.xml -- 2.54.0

2 8

[PATCH 0/3] hyperv: Add support for detecting nested virtualization capability
by Jonathon Jongsma 03 Jun '26

03 Jun '26

In order to support migrating hyperv vms to kubevirt, MTV needs to detect whether the vm has a nested virtualization capabilities. This series adds basic support for identifying this scenario by exposing cpu features on the libvirt domain xml. https://redhat.atlassian.net/browse/RHEL-147662 Jonathon Jongsma (3): hyperv: fix error handling of hypervGetProcessorsByName() hyperv: Rename hypervGetProcessorsByName() to hypervGetProcessorList() hyperv: report nested virtualization setting in domain XML src/hyperv/hyperv_driver.c | 48 +++++++++++++++++++++------ src/hyperv/hyperv_wmi_generator.input | 5 +++ 2 files changed, 43 insertions(+), 10 deletions(-) -- 2.54.0

2 4

[PATCH 0/3] ci: Remove cirrus jobs
by Peter Krempa 02 Jun '26

02 Jun '26

Cirrus CI ceased operation. Our jobs now fail: https://gitlab.com/libvirt/libvirt/-/jobs/14644398990 Peter Krempa (3): ci: README: Delete section about 'Cirrus CI' ci: Drop 'Cirrus CI' job defnitions ci: Regenerate with 'lcitool' ci/README.rst | 59 ----------------------------------- ci/cirrus/freebsd-14.vars | 16 ---------- ci/cirrus/freebsd-15.vars | 16 ---------- ci/cirrus/macos-14.vars | 16 ---------- ci/gitlab/build-templates.yml | 53 ------------------------------- ci/gitlab/builds.yml | 49 ----------------------------- ci/manifest.yml | 11 ------- 7 files changed, 220 deletions(-) delete mode 100644 ci/cirrus/freebsd-14.vars delete mode 100644 ci/cirrus/freebsd-15.vars delete mode 100644 ci/cirrus/macos-14.vars -- 2.54.0

2 9

[PATCH v2 00/16] qemu: Fix CPU feature reporting on AMD CPUs
by Jiri Denemark 02 Jun '26

02 Jun '26

See the last patch for detailed description and individual patches for specific changes in v2. Important changes in version 2: - tests - the functionality uses a new flag for virConnectGetDomainCapabilities Jiri Denemark (16): cpu_conf: Introduce virCPUDefSortFeatures qemu_capabilities: Split virQEMUCapsFillDomainCPUCaps qemu: Move domain caps flags handling to virQEMUCapsFillDomainCPUHostModel qemu_capabilities: Always sort features in host-model CPU qemu_capabilities: Use g_autoptr in virQEMUCapsInitHostCPUModel qemu_capabilities: Split conditions in virQEMUCapsInitHostCPUModel qemu_capabilities: Cache expanded CPU domaincapstest: Test EXPAND_CPU_FEATURES flag util: Publish and mock virHostCPUGetMSRFromKVM cpu_x86: Introduce virCPUx86DataAddMSR cpu: Introduce virCPUUpdateFeatures Fix documentation of VIR_CONNECT_GET_DOMAIN_CAPABILITIES_EXPAND_CPU_FEATURES Introduce VIR_CONNECT_GET_DOMAIN_CAPABILITIES_SUPPORTED_CPU_FEATURES flag virsh: Add --supported-cpu-features option for domcapabilities domaincapstest: Test SUPPORTED_CPU_FEATURES flag qemu_capabilities: Fix domain capabilities on AMD CPUs docs/manpages/virsh.rst | 12 +- include/libvirt/libvirt-domain.h | 3 + src/conf/cpu_conf.c | 20 + src/conf/cpu_conf.h | 3 + src/cpu/cpu.c | 48 +- src/cpu/cpu.h | 12 + src/cpu/cpu_x86.c | 54 +- src/cpu/cpu_x86.h | 4 + src/libvirt-domain.c | 14 +- src/libvirt_private.syms | 4 + src/qemu/qemu_capabilities.c | 214 +- src/qemu/qemu_capabilities.h | 6 +- src/qemu/qemu_conf.c | 6 +- src/qemu/qemu_conf.h | 3 +- src/qemu/qemu_driver.c | 18 +- src/util/virhostcpu.c | 16 +- src/util/virhostcpu.h | 3 + ...qemu_10.0.0-q35.x86_64+amdsev-expanded.xml | 1123 ++++++++ ...emu_10.0.0-q35.x86_64+amdsev-supported.xml | 1015 +++++++ .../qemu_10.0.0-q35.x86_64+amdsev.xml | 48 +- .../qemu_10.0.0-q35.x86_64-expanded.xml | 1979 ++++++++++++++ .../qemu_10.0.0-q35.x86_64-supported.xml | 1903 ++++++++++++++ .../domaincapsdata/qemu_10.0.0-q35.x86_64.xml | 50 +- .../qemu_10.0.0-tcg.x86_64+amdsev.xml | 60 +- .../domaincapsdata/qemu_10.0.0-tcg.x86_64.xml | 60 +- tests/domaincapsdata/qemu_10.0.0.s390x.xml | 94 +- .../qemu_10.0.0.x86_64+amdsev.xml | 48 +- tests/domaincapsdata/qemu_10.0.0.x86_64.xml | 50 +- ...mu_10.1.0-q35.x86_64+inteltdx-expanded.xml | 1250 +++++++++ ...u_10.1.0-q35.x86_64+inteltdx-supported.xml | 1064 ++++++++ .../qemu_10.1.0-q35.x86_64+inteltdx.xml | 56 +- .../qemu_10.1.0-q35.x86_64-expanded.xml | 2328 +++++++++++++++++ .../qemu_10.1.0-q35.x86_64-supported.xml | 2259 ++++++++++++++++ .../domaincapsdata/qemu_10.1.0-q35.x86_64.xml | 40 +- .../qemu_10.1.0-tcg.x86_64+inteltdx.xml | 66 +- .../domaincapsdata/qemu_10.1.0-tcg.x86_64.xml | 66 +- tests/domaincapsdata/qemu_10.1.0.s390x.xml | 106 +- .../qemu_10.1.0.x86_64+inteltdx.xml | 56 +- tests/domaincapsdata/qemu_10.1.0.x86_64.xml | 40 +- .../qemu_10.2.0-q35.x86_64+mshv-expanded.xml | 237 ++ .../qemu_10.2.0-q35.x86_64+mshv-supported.xml | 237 ++ .../qemu_10.2.0-q35.x86_64-expanded.xml | 1483 +++++++++++ .../qemu_10.2.0-q35.x86_64-supported.xml | 1365 ++++++++++ .../domaincapsdata/qemu_10.2.0-q35.x86_64.xml | 24 +- .../qemu_10.2.0-tcg.x86_64+mshv.xml | 66 +- .../domaincapsdata/qemu_10.2.0-tcg.x86_64.xml | 66 +- tests/domaincapsdata/qemu_10.2.0.x86_64.xml | 24 +- .../qemu_11.0.0-q35.x86_64+sgx-expanded.xml | 1865 +++++++++++++ .../qemu_11.0.0-q35.x86_64+sgx-supported.xml | 1747 +++++++++++++ .../qemu_11.0.0-q35.x86_64+sgx.xml | 24 +- .../qemu_11.0.0-q35.x86_64-expanded.xml | 1856 +++++++++++++ .../qemu_11.0.0-q35.x86_64-supported.xml | 1738 ++++++++++++ .../domaincapsdata/qemu_11.0.0-q35.x86_64.xml | 24 +- .../qemu_11.0.0-tcg.x86_64+sgx.xml | 66 +- .../domaincapsdata/qemu_11.0.0-tcg.x86_64.xml | 66 +- tests/domaincapsdata/qemu_11.0.0.s390x.xml | 106 +- .../domaincapsdata/qemu_11.0.0.x86_64+sgx.xml | 24 +- tests/domaincapsdata/qemu_11.0.0.x86_64.xml | 24 +- .../qemu_7.2.0-hvf.x86_64+hvf.xml | 36 +- .../qemu_7.2.0-q35.x86_64-expanded.xml | 1257 +++++++++ .../qemu_7.2.0-q35.x86_64-supported.xml | 1181 +++++++++ .../domaincapsdata/qemu_7.2.0-q35.x86_64.xml | 36 +- .../qemu_7.2.0-tcg.x86_64+hvf.xml | 46 +- .../domaincapsdata/qemu_7.2.0-tcg.x86_64.xml | 46 +- tests/domaincapsdata/qemu_7.2.0.x86_64.xml | 36 +- .../qemu_8.0.0-q35.x86_64-expanded.xml | 1366 ++++++++++ .../qemu_8.0.0-q35.x86_64-supported.xml | 1290 +++++++++ .../domaincapsdata/qemu_8.0.0-q35.x86_64.xml | 36 +- .../domaincapsdata/qemu_8.0.0-tcg.x86_64.xml | 54 +- tests/domaincapsdata/qemu_8.0.0.x86_64.xml | 36 +- .../qemu_8.1.0-q35.x86_64-expanded.xml | 1624 ++++++++++++ .../qemu_8.1.0-q35.x86_64-supported.xml | 1548 +++++++++++ .../domaincapsdata/qemu_8.1.0-q35.x86_64.xml | 38 +- .../domaincapsdata/qemu_8.1.0-tcg.x86_64.xml | 60 +- tests/domaincapsdata/qemu_8.1.0.s390x.xml | 62 +- tests/domaincapsdata/qemu_8.1.0.x86_64.xml | 38 +- .../qemu_8.2.0-q35.x86_64-expanded.xml | 1626 ++++++++++++ .../qemu_8.2.0-q35.x86_64-supported.xml | 1550 +++++++++++ .../domaincapsdata/qemu_8.2.0-q35.x86_64.xml | 40 +- .../domaincapsdata/qemu_8.2.0-tcg.x86_64.xml | 58 +- tests/domaincapsdata/qemu_8.2.0.s390x.xml | 62 +- tests/domaincapsdata/qemu_8.2.0.x86_64.xml | 40 +- .../qemu_9.0.0-q35.x86_64-expanded.xml | 1627 ++++++++++++ .../qemu_9.0.0-q35.x86_64-supported.xml | 1551 +++++++++++ .../domaincapsdata/qemu_9.0.0-q35.x86_64.xml | 40 +- .../domaincapsdata/qemu_9.0.0-tcg.x86_64.xml | 62 +- tests/domaincapsdata/qemu_9.0.0.x86_64.xml | 40 +- .../qemu_9.1.0-q35.x86_64-expanded.xml | 1763 +++++++++++++ .../qemu_9.1.0-q35.x86_64-supported.xml | 1687 ++++++++++++ .../domaincapsdata/qemu_9.1.0-q35.x86_64.xml | 48 +- .../domaincapsdata/qemu_9.1.0-tcg.x86_64.xml | 60 +- tests/domaincapsdata/qemu_9.1.0.s390x.xml | 94 +- tests/domaincapsdata/qemu_9.1.0.x86_64.xml | 48 +- .../qemu_9.2.0-q35.x86_64+amdsev-expanded.xml | 1003 +++++++ ...qemu_9.2.0-q35.x86_64+amdsev-supported.xml | 895 +++++++ .../qemu_9.2.0-q35.x86_64+amdsev.xml | 48 +- .../qemu_9.2.0-q35.x86_64-expanded.xml | 1821 +++++++++++++ .../qemu_9.2.0-q35.x86_64-supported.xml | 1745 ++++++++++++ .../domaincapsdata/qemu_9.2.0-q35.x86_64.xml | 50 +- .../qemu_9.2.0-tcg.x86_64+amdsev.xml | 60 +- .../domaincapsdata/qemu_9.2.0-tcg.x86_64.xml | 60 +- tests/domaincapsdata/qemu_9.2.0.s390x.xml | 94 +- .../qemu_9.2.0.x86_64+amdsev.xml | 48 +- tests/domaincapsdata/qemu_9.2.0.x86_64.xml | 50 +- tests/domaincapstest.c | 56 +- tests/qemucpumock.c | 22 + tools/virsh-host.c | 7 + 107 files changed, 48819 insertions(+), 1569 deletions(-) create mode 100644 tests/domaincapsdata/qemu_10.0.0-q35.x86_64+amdsev-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.0.0-q35.x86_64+amdsev-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.0.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.0.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.1.0-q35.x86_64+inteltdx-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.1.0-q35.x86_64+inteltdx-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.1.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.1.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.2.0-q35.x86_64+mshv-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.2.0-q35.x86_64+mshv-supported.xml create mode 100644 tests/domaincapsdata/qemu_10.2.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_10.2.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_11.0.0-q35.x86_64+sgx-expanded.xml create mode 100644 tests/domaincapsdata/qemu_11.0.0-q35.x86_64+sgx-supported.xml create mode 100644 tests/domaincapsdata/qemu_11.0.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_11.0.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_7.2.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_7.2.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_8.0.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_8.0.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_8.1.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_8.1.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_8.2.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_8.2.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_9.0.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_9.0.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_9.1.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_9.1.0-q35.x86_64-supported.xml create mode 100644 tests/domaincapsdata/qemu_9.2.0-q35.x86_64+amdsev-expanded.xml create mode 100644 tests/domaincapsdata/qemu_9.2.0-q35.x86_64+amdsev-supported.xml create mode 100644 tests/domaincapsdata/qemu_9.2.0-q35.x86_64-expanded.xml create mode 100644 tests/domaincapsdata/qemu_9.2.0-q35.x86_64-supported.xml -- 2.54.0

2 32