November 2024 - Devel - libvirt List Archives

Entering freeze for libvirt-10.10.0
by Jiri Denemark 28 Nov '24

28 Nov '24

I have just tagged v10.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. Thanks, Jirka

1 1

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

28 Nov '24

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 | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 4b7f4e8244..65e21c4299 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -46,6 +46,12 @@ v10.10.0 (unreleased) required to keep data "raw" on disk, but the use case requires features of the QCOW2 format such as incremental backups. + * swtpm: Add support for profiles + + Upcoming swtpm release will have TPM profile support that allows to + restrict a TPM's provided set of crypto algorithms and commands. Users can + now select profile by using ``<profile/>`` in their TPM XML definition. + * **Improvements** * qemu: Support UEFI NVRAM images on block storage @@ -55,6 +61,21 @@ v10.10.0 (unreleased) qcow2 is used as the format, the images are now also auto-populated from the template. + * qemu: Automatically add IOMMU when needed + + When domain of 'qemu' or 'kvm' type has more than 255 vCPUs IOMMU with EIM + mode is required. Starting with this release libvirt automatically adds one + (or turns on the EIM mode if there's IOMMU without it). + + * ch: allow hostdevs in domain definition + + The Cloud Hypervisor driver (ch) now supports ``<hostdev/>``-s. + + * ch: Enable callbacks for ch domain events + + The Cloud Hypervisor driver (ch) now supports emitting events on domain + define, undefine, start, boot, stop and destroy. + * **Bug fixes** * qemu: Fix reversion and inactive deletion of internal snapshots with UEFI NVRAM @@ -63,6 +84,13 @@ v10.10.0 (unreleased) firmware was allowed, but certain operations such as reversion or inactive deletion didn't work properly as they didn't consider the NVRAM qcow2 file. + * virnetdevopenvswitch: Warn on unsupported QoS settings + + For OpenVSwitch vNICs libivrt does not set QoS directly using 'tc' but + offloads setting to OVS. But OVS is not as feature full as libvirt in this + regard and setting different 'peak' than 'average' results in vNIC always + sticking with 'peak'. Produce a warning if that's the case. + v10.9.0 (2024-11-01) ==================== -- 2.45.2

2 1

[PATCH 0/8] qemu: fixes for blockjobs with <dataStore>
by Peter Krempa 28 Nov '24

28 Nov '24

Couple fixes for the <dataStore> feature when used with blockjobs: - fixes for qemuBlockReopenAccess (code driving 'blockdev-reopen' in qemu) for bugs noticed during testing of <dataStore> - the 'auto-read-only' qemu feature doesn't apply od the 'data-file' blockdevs, thus libvirt needs to handle them explicitly - lookup of the node name associated with the <dataStore> volume in the chains (for block threshold event handling) Peter Krempa (8): qemuBlockReopenAccess: Add debug log entry about state of the image qemuBlockReopenAccess: Fix update of 'readonly' state qemuBlockReopenAccess: Don't require backing chain terminator for non-chained images qemu: block: Ensure that <dataStore> is in appropriate state qemu: snapshot: Change 'data-file' to read-only after snapshot qemuDomainVirStorageSourceFindByNodeName: Extract nodename matching qemuDomainVirStorageSourceFindByNodeName: Match also '<dataStore>' sources qemuDomainGetStorageSourceByDevstr: Lookup also '<dataStore>' src/qemu/qemu_block.c | 60 +++++++++++++++++++++++++++++++--------- src/qemu/qemu_blockjob.c | 16 ++++++++++- src/qemu/qemu_domain.c | 38 +++++++++++++++++++++---- src/qemu/qemu_snapshot.c | 12 ++++++-- 4 files changed, 105 insertions(+), 21 deletions(-) -- 2.47.0

2 14

[PATCH for 10.10.0 0/5] Fix broken XML schemas and 'virschematest'
by Peter Krempa 28 Nov '24

28 Nov '24

'virschematest' didn't test the majority of files for some time so some schema problems snuck in. Peter Krempa (5): schemas: domain: Make <identity> subelement of NFS disk source optional schemas: domaincaps: Add schema for 'panic' device schemas: domaincaps: Add schema for 'canonical' cpu model name schemas: domaincaps: Add schema for CPU 'blockers' virschematest: Don't skip all "directory" tests src/conf/schemas/domaincaps.rng | 29 +++++++++++++++++++++++++++++ src/conf/schemas/domaincommon.rng | 26 ++++++++++++++------------ tests/virschematest.c | 9 +++++---- 3 files changed, 48 insertions(+), 16 deletions(-) -- 2.47.0

2 7

[PATCH] NEWS: Mention qcow2 'data-file', block NVRAM, and internal snapshot reversion
by Peter Krempa 27 Nov '24

27 Nov '24

Signed-off-by: Peter Krempa <pkrempa(a)redhat.com> --- NEWS.rst | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 185880d0e8..4b7f4e8244 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -38,10 +38,31 @@ v10.10.0 (unreleased) Updates to QEMU CPU models with -vN suffix can now be used in libvirt just like any other CPU model. + * qemu: Support for the 'data-file' QCOW2 image feature + + The QEMU hypervisor driver now supports QCOW2 images with 'data-file' + feature present (both when probing form the image itself and when specified + explicitly via ``<dataStore>`` element). This can be useful when it's + required to keep data "raw" on disk, but the use case requires features + of the QCOW2 format such as incremental backups. + * **Improvements** + * qemu: Support UEFI NVRAM images on block storage + + Libvirt now allows users to use block storage as backend for UEFI NVRAM + images and allows them to be in format different than the template. When + qcow2 is used as the format, the images are now also auto-populated from the + template. + * **Bug fixes** + * qemu: Fix reversion and inactive deletion of internal snapshots with UEFI NVRAM + + In `v10.9.0 (2024-11-01)`_ creation of internal snapshots of VMs with UEFI + firmware was allowed, but certain operations such as reversion or inactive + deletion didn't work properly as they didn't consider the NVRAM qcow2 file. + v10.9.0 (2024-11-01) ==================== -- 2.47.0

2 1

[PATCH] qemu: Validate QoS values in qemuDomainSetInterfaceParameters()
by Michal Privoznik 27 Nov '24

27 Nov '24

This is similar to one of my previous commits (v10.7.0-rc1~22) which introduce a check that <bandwidth/> values fit into certain limits. My original commit validated values when parsing <bandwidth/> XML, but completely missed the case when values are set over virDomainSetInterfaceParameters() API. Solution is simple - just perform validation after bandwidth structure is reconstructed from arguments passed to the API. Resolves: https://issues.redhat.com/browse/RHEL-65372 Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com> --- src/qemu/qemu_driver.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c index d1b32de56a..09f7edda7d 100644 --- a/src/qemu/qemu_driver.c +++ b/src/qemu/qemu_driver.c @@ -9883,6 +9883,9 @@ qemuDomainSetInterfaceParameters(virDomainPtr dom, if (!bandwidth->out->average) VIR_FREE(bandwidth->out); + if (!virNetDevBandwidthValidate(bandwidth)) + goto endjob; + if (net) { newBandwidth = g_new0(virNetDevBandwidth, 1); -- 2.45.2

2 1

[PATCH] NEWS: Document support for versioned CPU models
by Jiri Denemark 27 Nov '24

27 Nov '24

Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com> --- NEWS.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/NEWS.rst b/NEWS.rst index 88ac38834a..557c5b18d3 100644 --- a/NEWS.rst +++ b/NEWS.rst @@ -33,6 +33,11 @@ v10.10.0 (unreleased) Limitation: The s390x BIOS will try to IPL up to 8 total devices, any number of which may be disks or network devices. + * qemu: Add support for versioned CPU models + + Updates to QEMU CPU models with -vN suffix can now be used in libvirt just + like any other CPU model. + * **Improvements** * **Bug fixes** -- 2.47.0

2 1

[PATCH] cpu: Check blockers in virCPUCompareUnusable only if they exist
by Jiri Denemark 27 Nov '24

27 Nov '24

virCPUCompareUnusable can be called with blockers == NULL in case the CPU model itself is usable (i.e., QEMU reports an empty list of blockers), but the CPU definition contains some additional features which have to be checked. Fixes: v10.8.0-129-g5f8abbb7d0 Reported-by: Han Han <hhan(a)redhat.com> Signed-off-by: Jiri Denemark <jdenemar(a)redhat.com> --- src/cpu/cpu.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/src/cpu/cpu.c b/src/cpu/cpu.c index 2b0d641e78..58fba3781c 100644 --- a/src/cpu/cpu.c +++ b/src/cpu/cpu.c @@ -201,11 +201,13 @@ virCPUCompareUnusable(virArch arch, char **blocker; size_t i; - for (blocker = blockers; *blocker; blocker++) { - if (!(feat = virCPUDefFindFeature(cpu, *blocker)) || - feat->policy != VIR_CPU_FEATURE_DISABLE) { - virBufferAddStr(&features, *blocker); - virBufferAddLit(&features, ", "); + if (blockers) { + for (blocker = blockers; *blocker; blocker++) { + if (!(feat = virCPUDefFindFeature(cpu, *blocker)) || + feat->policy != VIR_CPU_FEATURE_DISABLE) { + virBufferAddStr(&features, *blocker); + virBufferAddLit(&features, ", "); + } } } -- 2.47.0

3 2

[PATCH v2 00/36] Add support for versioned CPU models
by Jiri Denemark 27 Nov '24

27 Nov '24

Each CPU model with -v* suffix is defined as a standalone model copying all attributes of the previous version although CPU model versions with an alias are handled differently. The full definition is used for the alias and the versioned model is created as an identical copy of the alias. To avoid breaking migration compatibility of host-model CPUs all versioned models are marked with <decode guest='off'/> so that they are ignored when selecting candidates for host-model. It's not ideal but not doing so would break almost all host-model CPUs as the new versioned CPU models have all vmx-* features included since their introduction while existing CPU models were updated later. This meas existing models would be accompanied with a long list of vmx-* features to properly describe a host CPU while the newly added CPU models would have those features enabled implicitly and their list of features would be significantly shorter. Thus the new models would always be better candidates for host-model than the existing models. Version 2: - removed patches - cpu_x86: Copy added and removed features from ancestor - qemu: Canonicalize CPU models - new patches - cpu_x86: Annotate virCPUx86Model fields - cpu_x86: Promote added/removed from ancestor - cpu_x86: Record relations between CPU models - cpu: Introduce virCPUGetCanonicalModel - domain_capabilities: Report canonical names of CPU models - cpu_map: Add Denverton CPU model - cpu_map: Add KnightsMill CPU model - make -v? variants linked to their corresponding non-versioned models (such as -noTSX, -IBRS, etc.) - all -v? variants are marked with <decode host='on' guest='off'/> - do not add absolute path to CPU model XMLs to index.xml - use <group name='...'> for all groups rather than a strange mix of <group name='...'> and <group vendor='...'> Jiri Denemark (36): cpu_x86: Annotate virCPUx86Model fields cpu_x86: Promote added/removed from ancestor sync_qemu_features_i386: Add some removed features back sync_qemu_models_i386: Use f-strings sync_qemu_models_i386: Do not overwrite existing models sync_qemu_models_i386: Do not require full path to QEMU's cpu.c sync_qemu_models_i386: Add support for versioned CPU models sync_qemu_models_i386: Store extra info in a separate file sync_qemu_models_i386: Switch to lxml cpu_map: Properly group models in index.xml sync_qemu_models_i386: Update index.xml sync_qemu_models_i386: Copy signatures from base model cpu_x86: Record relations between CPU models cpu: Introduce virCPUGetCanonicalModel domain_capabilities: Report canonical names of CPU models cpu_map: Add versions of SierraForest CPU model cpu_map: Add versions of GraniteRapids CPU model cpu_map: Add versions of SapphireRapids CPU model cpu_map: Add versions of Snowridge CPU model cpu_map: Add versions of Cooperlake CPU model cpu_map: Add versions of Icelake-Server CPU model cpu_map: Add versions of Cascadelake-Server CPU model cpu_map: Add versions of Skylake-Server CPU model cpu_map: Add versions of Skylake-Client CPU model cpu_map: Add versions of Broadwell CPU model cpu_map: Add versions of Haswell CPU model cpu_map: Add versions of IvyBridge CPU model cpu_map: Add versions of SandyBridge CPU model cpu_map: Add versions of Westmere CPU model cpu_map: Add versions of Nehalem CPU model cpu_map: Add versions of EPYC-Milan CPU model cpu_map: Add versions of EPYC-Rome CPU model cpu_map: Add versions of EPYC CPU model cpu_map: Add versions of Dhyana CPU model cpu_map: Add Denverton CPU model cpu_map: Add KnightsMill CPU model docs/formatdomaincaps.rst | 8 +- src/conf/domain_capabilities.c | 11 +- src/conf/domain_capabilities.h | 4 +- src/cpu/cpu.c | 25 + src/cpu/cpu.h | 8 + src/cpu/cpu_map.c | 2 +- src/cpu/cpu_x86.c | 88 +- src/cpu_map/index.xml | 291 ++-- src/cpu_map/meson.build | 60 + src/cpu_map/sync_qemu_features_i386.py | 3 + src/cpu_map/sync_qemu_models_i386.py | 184 +- src/cpu_map/x86_Broadwell-v1.xml | 6 + src/cpu_map/x86_Broadwell-v2.xml | 6 + src/cpu_map/x86_Broadwell-v3.xml | 6 + src/cpu_map/x86_Broadwell-v4.xml | 6 + src/cpu_map/x86_Cascadelake-Server-v1.xml | 6 + src/cpu_map/x86_Cascadelake-Server-v2.xml | 157 ++ src/cpu_map/x86_Cascadelake-Server-v3.xml | 6 + src/cpu_map/x86_Cascadelake-Server-v4.xml | 156 ++ src/cpu_map/x86_Cascadelake-Server-v5.xml | 158 ++ src/cpu_map/x86_Cooperlake-v1.xml | 6 + src/cpu_map/x86_Cooperlake-v2.xml | 164 ++ src/cpu_map/x86_Denverton-v1.xml | 6 + src/cpu_map/x86_Denverton-v2.xml | 137 ++ src/cpu_map/x86_Denverton-v3.xml | 139 ++ src/cpu_map/x86_Denverton.xml | 138 ++ src/cpu_map/x86_Dhyana-v1.xml | 6 + src/cpu_map/x86_Dhyana-v2.xml | 73 + src/cpu_map/x86_EPYC-Milan-v1.xml | 6 + src/cpu_map/x86_EPYC-Milan-v2.xml | 99 ++ src/cpu_map/x86_EPYC-Rome-v1.xml | 6 + src/cpu_map/x86_EPYC-Rome-v2.xml | 86 + src/cpu_map/x86_EPYC-Rome-v3.xml | 86 + src/cpu_map/x86_EPYC-Rome-v4.xml | 85 + src/cpu_map/x86_EPYC-v1.xml | 6 + src/cpu_map/x86_EPYC-v2.xml | 6 + src/cpu_map/x86_EPYC-v3.xml | 79 + src/cpu_map/x86_EPYC-v4.xml | 79 + src/cpu_map/x86_GraniteRapids-v1.xml | 6 + src/cpu_map/x86_Haswell-v1.xml | 6 + src/cpu_map/x86_Haswell-v2.xml | 6 + src/cpu_map/x86_Haswell-v3.xml | 6 + src/cpu_map/x86_Haswell-v4.xml | 6 + src/cpu_map/x86_Icelake-Server-v1.xml | 6 + src/cpu_map/x86_Icelake-Server-v2.xml | 6 + src/cpu_map/x86_Icelake-Server-v3.xml | 165 ++ src/cpu_map/x86_Icelake-Server-v4.xml | 172 ++ src/cpu_map/x86_Icelake-Server-v5.xml | 174 ++ src/cpu_map/x86_Icelake-Server-v6.xml | 175 ++ src/cpu_map/x86_Icelake-Server-v7.xml | 177 ++ src/cpu_map/x86_IvyBridge-v1.xml | 6 + src/cpu_map/x86_IvyBridge-v2.xml | 6 + src/cpu_map/x86_KnightsMill.xml | 71 + src/cpu_map/x86_Nehalem-v1.xml | 6 + src/cpu_map/x86_Nehalem-v2.xml | 6 + src/cpu_map/x86_SandyBridge-v1.xml | 6 + src/cpu_map/x86_SandyBridge-v2.xml | 6 + src/cpu_map/x86_SapphireRapids-v1.xml | 6 + src/cpu_map/x86_SapphireRapids-v2.xml | 193 +++ src/cpu_map/x86_SapphireRapids-v3.xml | 198 +++ src/cpu_map/x86_SierraForest-v1.xml | 6 + src/cpu_map/x86_Skylake-Client-v1.xml | 6 + src/cpu_map/x86_Skylake-Client-v2.xml | 6 + src/cpu_map/x86_Skylake-Client-v3.xml | 6 + src/cpu_map/x86_Skylake-Client-v4.xml | 141 ++ src/cpu_map/x86_Skylake-Server-v1.xml | 6 + src/cpu_map/x86_Skylake-Server-v2.xml | 6 + src/cpu_map/x86_Skylake-Server-v3.xml | 6 + src/cpu_map/x86_Skylake-Server-v4.xml | 148 ++ src/cpu_map/x86_Skylake-Server-v5.xml | 150 ++ src/cpu_map/x86_Snowridge-v1.xml | 6 + src/cpu_map/x86_Snowridge-v2.xml | 143 ++ src/cpu_map/x86_Snowridge-v3.xml | 145 ++ src/cpu_map/x86_Snowridge-v4.xml | 143 ++ src/cpu_map/x86_Westmere-v1.xml | 6 + src/cpu_map/x86_Westmere-v2.xml | 6 + src/libvirt_private.syms | 1 + src/qemu/qemu_capabilities.c | 10 +- tests/cputest.c | 5 +- .../x86_64-cpuid-Atom-P5362-host.xml | 2 +- .../x86_64-cpuid-Cooperlake-host.xml | 2 +- .../x86_64-cpuid-Core-i5-2500-host.xml | 2 +- .../x86_64-cpuid-Core-i5-2540M-host.xml | 2 +- .../x86_64-cpuid-Core-i5-4670T-host.xml | 2 +- .../x86_64-cpuid-Core-i5-650-host.xml | 2 +- .../x86_64-cpuid-Core-i5-6600-host.xml | 2 +- .../x86_64-cpuid-Core-i7-2600-host.xml | 2 +- ...86_64-cpuid-Core-i7-2600-xsaveopt-host.xml | 2 +- .../x86_64-cpuid-Core-i7-3520M-host.xml | 2 +- .../x86_64-cpuid-Core-i7-3740QM-host.xml | 2 +- .../x86_64-cpuid-Core-i7-3770-host.xml | 2 +- .../x86_64-cpuid-Core-i7-4510U-host.xml | 2 +- .../x86_64-cpuid-Core-i7-4600U-host.xml | 2 +- .../x86_64-cpuid-Core-i7-5600U-arat-host.xml | 2 +- .../x86_64-cpuid-Core-i7-5600U-host.xml | 2 +- .../x86_64-cpuid-Core-i7-5600U-ibrs-host.xml | 2 +- .../x86_64-cpuid-Core-i7-7600U-host.xml | 2 +- .../x86_64-cpuid-Core-i7-7700-host.xml | 2 +- .../x86_64-cpuid-Core-i7-8550U-host.xml | 2 +- .../x86_64-cpuid-Core-i7-8700-host.xml | 2 +- .../x86_64-cpuid-EPYC-7502-32-Core-host.xml | 5 +- .../x86_64-cpuid-EPYC-7601-32-Core-host.xml | 2 +- ...6_64-cpuid-EPYC-7601-32-Core-ibpb-host.xml | 8 +- ...6_64-cpuid-Hygon-C86-7185-32-core-host.xml | 5 +- .../x86_64-cpuid-Ice-Lake-Server-host.xml | 2 +- ...64-cpuid-Ryzen-7-1800X-Eight-Core-host.xml | 2 +- ...86_64-cpuid-Ryzen-9-3900X-12-Core-host.xml | 2 +- .../x86_64-cpuid-Xeon-E3-1225-v5-host.xml | 2 +- .../x86_64-cpuid-Xeon-E3-1245-v5-host.xml | 2 +- .../x86_64-cpuid-Xeon-E5-2609-v3-host.xml | 2 +- .../x86_64-cpuid-Xeon-E5-2623-v4-host.xml | 2 +- .../x86_64-cpuid-Xeon-E5-2630-v3-host.xml | 2 +- .../x86_64-cpuid-Xeon-E5-2630-v4-host.xml | 2 +- .../x86_64-cpuid-Xeon-E5-2650-host.xml | 2 +- .../x86_64-cpuid-Xeon-E5-2650-v3-host.xml | 2 +- .../x86_64-cpuid-Xeon-E5-2650-v4-host.xml | 2 +- .../x86_64-cpuid-Xeon-E7-4820-host.xml | 2 +- .../x86_64-cpuid-Xeon-E7-4830-host.xml | 2 +- .../x86_64-cpuid-Xeon-E7-8890-v3-host.xml | 2 +- .../x86_64-cpuid-Xeon-E7540-host.xml | 2 +- .../x86_64-cpuid-Xeon-Gold-5115-host.xml | 2 +- .../x86_64-cpuid-Xeon-Gold-6130-host.xml | 2 +- .../x86_64-cpuid-Xeon-Gold-6148-host.xml | 2 +- .../x86_64-cpuid-Xeon-Platinum-8268-host.xml | 2 +- .../x86_64-cpuid-Xeon-Platinum-9242-host.xml | 2 +- .../x86_64-cpuid-Xeon-W3520-host.xml | 2 +- .../domaincapsdata/qemu_5.2.0-q35.x86_64.xml | 462 ++++- .../domaincapsdata/qemu_5.2.0-tcg.x86_64.xml | 836 +++++++++- tests/domaincapsdata/qemu_5.2.0.x86_64.xml | 462 ++++- .../domaincapsdata/qemu_6.0.0-q35.x86_64.xml | 477 +++++- .../domaincapsdata/qemu_6.0.0-tcg.x86_64.xml | 896 +++++++++- tests/domaincapsdata/qemu_6.0.0.x86_64.xml | 477 +++++- .../domaincapsdata/qemu_6.1.0-q35.x86_64.xml | 576 ++++++- .../domaincapsdata/qemu_6.1.0-tcg.x86_64.xml | 1458 +++++++++++++--- tests/domaincapsdata/qemu_6.1.0.x86_64.xml | 576 ++++++- .../domaincapsdata/qemu_6.2.0-q35.x86_64.xml | 583 ++++++- .../domaincapsdata/qemu_6.2.0-tcg.x86_64.xml | 1461 +++++++++++++--- tests/domaincapsdata/qemu_6.2.0.x86_64.xml | 583 ++++++- .../domaincapsdata/qemu_7.0.0-q35.x86_64.xml | 609 ++++++- .../domaincapsdata/qemu_7.0.0-tcg.x86_64.xml | 1485 ++++++++++++++--- tests/domaincapsdata/qemu_7.0.0.x86_64.xml | 609 ++++++- .../domaincapsdata/qemu_7.1.0-q35.x86_64.xml | 609 ++++++- .../domaincapsdata/qemu_7.1.0-tcg.x86_64.xml | 1425 +++++++++++++--- tests/domaincapsdata/qemu_7.1.0.x86_64.xml | 609 ++++++- .../domaincapsdata/qemu_7.2.0-q35.x86_64.xml | 609 ++++++- .../qemu_7.2.0-tcg.x86_64+hvf.xml | 979 ++++++++++- .../domaincapsdata/qemu_7.2.0-tcg.x86_64.xml | 979 ++++++++++- tests/domaincapsdata/qemu_7.2.0.x86_64.xml | 609 ++++++- .../domaincapsdata/qemu_8.0.0-q35.x86_64.xml | 652 +++++++- .../domaincapsdata/qemu_8.0.0-tcg.x86_64.xml | 1015 ++++++++++- tests/domaincapsdata/qemu_8.0.0.x86_64.xml | 652 +++++++- .../domaincapsdata/qemu_8.1.0-q35.x86_64.xml | 815 ++++++++- .../domaincapsdata/qemu_8.1.0-tcg.x86_64.xml | 1063 +++++++++++- tests/domaincapsdata/qemu_8.1.0.x86_64.xml | 815 ++++++++- .../domaincapsdata/qemu_8.2.0-q35.x86_64.xml | 815 ++++++++- .../domaincapsdata/qemu_8.2.0-tcg.x86_64.xml | 959 ++++++++++- tests/domaincapsdata/qemu_8.2.0.x86_64.xml | 815 ++++++++- .../domaincapsdata/qemu_9.0.0-q35.x86_64.xml | 815 ++++++++- .../domaincapsdata/qemu_9.0.0-tcg.x86_64.xml | 915 +++++++++- tests/domaincapsdata/qemu_9.0.0.x86_64.xml | 815 ++++++++- .../domaincapsdata/qemu_9.1.0-q35.x86_64.xml | 922 +++++++++- .../domaincapsdata/qemu_9.1.0-tcg.x86_64.xml | 1139 +++++++++++-- tests/domaincapsdata/qemu_9.1.0.x86_64.xml | 922 +++++++++- .../domaincapsdata/qemu_9.2.0-q35.x86_64.xml | 922 +++++++++- .../domaincapsdata/qemu_9.2.0-tcg.x86_64.xml | 1139 +++++++++++-- tests/domaincapsdata/qemu_9.2.0.x86_64.xml | 922 +++++++++- 166 files changed, 35711 insertions(+), 2629 deletions(-) create mode 100644 src/cpu_map/x86_Broadwell-v1.xml create mode 100644 src/cpu_map/x86_Broadwell-v2.xml create mode 100644 src/cpu_map/x86_Broadwell-v3.xml create mode 100644 src/cpu_map/x86_Broadwell-v4.xml create mode 100644 src/cpu_map/x86_Cascadelake-Server-v1.xml create mode 100644 src/cpu_map/x86_Cascadelake-Server-v2.xml create mode 100644 src/cpu_map/x86_Cascadelake-Server-v3.xml create mode 100644 src/cpu_map/x86_Cascadelake-Server-v4.xml create mode 100644 src/cpu_map/x86_Cascadelake-Server-v5.xml create mode 100644 src/cpu_map/x86_Cooperlake-v1.xml create mode 100644 src/cpu_map/x86_Cooperlake-v2.xml create mode 100644 src/cpu_map/x86_Denverton-v1.xml create mode 100644 src/cpu_map/x86_Denverton-v2.xml create mode 100644 src/cpu_map/x86_Denverton-v3.xml create mode 100644 src/cpu_map/x86_Denverton.xml create mode 100644 src/cpu_map/x86_Dhyana-v1.xml create mode 100644 src/cpu_map/x86_Dhyana-v2.xml create mode 100644 src/cpu_map/x86_EPYC-Milan-v1.xml create mode 100644 src/cpu_map/x86_EPYC-Milan-v2.xml create mode 100644 src/cpu_map/x86_EPYC-Rome-v1.xml create mode 100644 src/cpu_map/x86_EPYC-Rome-v2.xml create mode 100644 src/cpu_map/x86_EPYC-Rome-v3.xml create mode 100644 src/cpu_map/x86_EPYC-Rome-v4.xml create mode 100644 src/cpu_map/x86_EPYC-v1.xml create mode 100644 src/cpu_map/x86_EPYC-v2.xml create mode 100644 src/cpu_map/x86_EPYC-v3.xml create mode 100644 src/cpu_map/x86_EPYC-v4.xml create mode 100644 src/cpu_map/x86_GraniteRapids-v1.xml create mode 100644 src/cpu_map/x86_Haswell-v1.xml create mode 100644 src/cpu_map/x86_Haswell-v2.xml create mode 100644 src/cpu_map/x86_Haswell-v3.xml create mode 100644 src/cpu_map/x86_Haswell-v4.xml create mode 100644 src/cpu_map/x86_Icelake-Server-v1.xml create mode 100644 src/cpu_map/x86_Icelake-Server-v2.xml create mode 100644 src/cpu_map/x86_Icelake-Server-v3.xml create mode 100644 src/cpu_map/x86_Icelake-Server-v4.xml create mode 100644 src/cpu_map/x86_Icelake-Server-v5.xml create mode 100644 src/cpu_map/x86_Icelake-Server-v6.xml create mode 100644 src/cpu_map/x86_Icelake-Server-v7.xml create mode 100644 src/cpu_map/x86_IvyBridge-v1.xml create mode 100644 src/cpu_map/x86_IvyBridge-v2.xml create mode 100644 src/cpu_map/x86_KnightsMill.xml create mode 100644 src/cpu_map/x86_Nehalem-v1.xml create mode 100644 src/cpu_map/x86_Nehalem-v2.xml create mode 100644 src/cpu_map/x86_SandyBridge-v1.xml create mode 100644 src/cpu_map/x86_SandyBridge-v2.xml create mode 100644 src/cpu_map/x86_SapphireRapids-v1.xml create mode 100644 src/cpu_map/x86_SapphireRapids-v2.xml create mode 100644 src/cpu_map/x86_SapphireRapids-v3.xml create mode 100644 src/cpu_map/x86_SierraForest-v1.xml create mode 100644 src/cpu_map/x86_Skylake-Client-v1.xml create mode 100644 src/cpu_map/x86_Skylake-Client-v2.xml create mode 100644 src/cpu_map/x86_Skylake-Client-v3.xml create mode 100644 src/cpu_map/x86_Skylake-Client-v4.xml create mode 100644 src/cpu_map/x86_Skylake-Server-v1.xml create mode 100644 src/cpu_map/x86_Skylake-Server-v2.xml create mode 100644 src/cpu_map/x86_Skylake-Server-v3.xml create mode 100644 src/cpu_map/x86_Skylake-Server-v4.xml create mode 100644 src/cpu_map/x86_Skylake-Server-v5.xml create mode 100644 src/cpu_map/x86_Snowridge-v1.xml create mode 100644 src/cpu_map/x86_Snowridge-v2.xml create mode 100644 src/cpu_map/x86_Snowridge-v3.xml create mode 100644 src/cpu_map/x86_Snowridge-v4.xml create mode 100644 src/cpu_map/x86_Westmere-v1.xml create mode 100644 src/cpu_map/x86_Westmere-v2.xml -- 2.47.0

3 56

Re: [PATCH v2 4/5] virsh: add --disable-deprecated-features flag to domcapabilities
by Boris Fiuczynski 26 Nov '24

26 Nov '24

On 11/26/24 16:14, Boris Fiuczynski wrote: > Reviewed-by: Boris Fiuczynski <fiuczy(a)linux.ibm.com> > > On 11/25/24 20:46, Collin Walling wrote: >> Add a new flag, --disable-deprecated-features, to the domcapabilities >> command. This will modify the output to show the 'host-model' CPU >> with features flagged as deprecated paired with the 'disable' policy. >> >> virsh domcapabilities --disable-deprecated-features >> >> Signed-off-by: Collin Walling <walling(a)linux.ibm.com> >> --- >> docs/manpages/virsh.rst | 6 ++++++ >> include/libvirt/libvirt-domain.h | 12 ++++++++++++ >> src/libvirt-domain.c | 2 +- >> src/qemu/qemu_capabilities.c | 20 ++++++++++++++++++++ >> src/qemu/qemu_capabilities.h | 3 +++ >> src/qemu/qemu_driver.c | 8 +++++++- >> tools/virsh-host.c | 9 ++++++++- >> 7 files changed, 57 insertions(+), 3 deletions(-) >> >> diff --git a/docs/manpages/virsh.rst b/docs/manpages/virsh.rst >> index 2e525d3fac..d3b8ff4e1c 100644 >> --- a/docs/manpages/virsh.rst >> +++ b/docs/manpages/virsh.rst >> @@ -568,6 +568,7 @@ domcapabilities >> domcapabilities [virttype] [emulatorbin] [arch] [machine] >> [--xpath EXPRESSION] [--wrap] >> + [--disabled-deprecated-features] >> Print an XML document describing the domain capabilities for the >> @@ -609,6 +610,11 @@ a standalone document, however, for ease of >> additional processing, >> the **--wrap** argument will cause the matching node to be wrapped >> in a common root node. >> +The **--disabled-deprecated-features** argument will modify the contents >> +of host-model CPU XML, updating the features list with any features >> +flagged as deprecated for the CPU model by the hypervisor. These >> +features will be paired with the "disable" policy. >> + >> pool-capabilities >> ----------------- >> diff --git a/include/libvirt/libvirt-domain.h b/include/libvirt/ >> libvirt-domain.h >> index d4f1573954..0d7e54a3dc 100644 >> --- a/include/libvirt/libvirt-domain.h >> +++ b/include/libvirt/libvirt-domain.h >> @@ -1491,6 +1491,18 @@ int virDomainMigrateGetMaxSpeed(virDomainPtr >> domain, >> int virDomainMigrateStartPostCopy(virDomainPtr domain, >> unsigned int flags); >> +/** >> + * virConnectGetDomainCapabilitiesFlags: >> + * >> + * Domain capabilities flags. >> + * >> + * Since: 10.10.0 >> + */ >> +typedef enum { >> + /* Report host model with deprecated features disabled. (Since: >> 10.10.0) */ >> + VIR_CONNECT_GET_DOMAIN_CAPABILITIES_DISABLE_DEPRECATED_FEATURES = >> (1 << 0), >> +} virConnectGetDomainCapabilitiesFlags; >> + >> char * virConnectGetDomainCapabilities(virConnectPtr conn, >> const char *emulatorbin, >> const char *arch, >> diff --git a/src/libvirt-domain.c b/src/libvirt-domain.c >> index 7c6b93963c..e8e5379672 100644 >> --- a/src/libvirt-domain.c >> +++ b/src/libvirt-domain.c >> @@ -12166,7 +12166,7 @@ virDomainSetUserPassword(virDomainPtr dom, >> * @arch: domain architecture >> * @machine: machine type >> * @virttype: virtualization type >> - * @flags: extra flags; not used yet, so callers should always pass 0 >> + * @flags: extra flags; bitwise-OR of >> virConnectGetDomainCapabilitiesFlags >> * >> * Prior creating a domain (for instance via virDomainCreateXML >> * or virDomainDefineXML) it may be suitable to know what the >> diff --git a/src/qemu/qemu_capabilities.c b/src/qemu/qemu_capabilities.c >> index 50905750fb..0701b2f4b0 100644 >> --- a/src/qemu/qemu_capabilities.c >> +++ b/src/qemu/qemu_capabilities.c >> @@ -3326,6 +3326,26 @@ virQEMUCapsGetCPUFeatures(virQEMUCaps *qemuCaps, >> } >> +void >> +virQEMUCapsUpdateCPUDeprecatedFeatures(virQEMUCaps *qemuCaps, >> + virDomainVirtType virtType, >> + virCPUDef *cpu) >> +{ >> + qemuMonitorCPUModelInfo *modelInfo; >> + size_t i; >> + >> + modelInfo = virQEMUCapsGetCPUModelInfo(qemuCaps, virtType); >> + >> + if (!modelInfo || !modelInfo->deprecated_props) >> + return; >> + >> + for (i = 0; i < g_strv_length(modelInfo->deprecated_props); i++) { >> + virCPUDefUpdateFeature(cpu, modelInfo->deprecated_props[i], >> + VIR_CPU_FEATURE_DISABLE); >> + } >> +} >> + >> + >> struct tpmTypeToCaps { >> int type; >> virQEMUCapsFlags caps; >> diff --git a/src/qemu/qemu_capabilities.h b/src/qemu/qemu_capabilities.h >> index 8347fd7fbb..6bfe99fce4 100644 >> --- a/src/qemu/qemu_capabilities.h >> +++ b/src/qemu/qemu_capabilities.h >> @@ -764,6 +764,9 @@ int virQEMUCapsGetCPUFeatures(virQEMUCaps *qemuCaps, >> virDomainVirtType virtType, >> bool migratable, >> char ***features); >> +void virQEMUCapsUpdateCPUDeprecatedFeatures(virQEMUCaps *qemuCaps, >> + virDomainVirtType virtType, >> + virCPUDef *cpu); >> virDomainVirtType virQEMUCapsGetVirtType(virQEMUCaps *qemuCaps); >> diff --git a/src/qemu/qemu_driver.c b/src/qemu/qemu_driver.c >> index 5b9c55f704..86ab0bd39a 100644 >> --- a/src/qemu/qemu_driver.c >> +++ b/src/qemu/qemu_driver.c >> @@ -16521,7 +16521,8 @@ qemuConnectGetDomainCapabilities(virConnectPtr >> conn, >> virDomainVirtType virttype; >> g_autoptr(virDomainCaps) domCaps = NULL; >> - virCheckFlags(0, NULL); >> + >> virCheckFlags(VIR_CONNECT_GET_DOMAIN_CAPABILITIES_DISABLE_DEPRECATED_FEATURES, >> + NULL); >> if (virConnectGetDomainCapabilitiesEnsureACL(conn) < 0) >> return NULL; >> @@ -16540,6 +16541,11 @@ >> qemuConnectGetDomainCapabilities(virConnectPtr conn, >> arch, >> virttype))) >> return NULL; >> + if (flags & >> VIR_CONNECT_GET_DOMAIN_CAPABILITIES_DISABLE_DEPRECATED_FEATURES) { >> + virQEMUCapsUpdateCPUDeprecatedFeatures(qemuCaps, virttype, >> + domCaps->cpu.hostModel); >> + } >> + >> return virDomainCapsFormat(domCaps); >> } >> diff --git a/tools/virsh-host.c b/tools/virsh-host.c >> index 2fe64e415f..f4e7324f42 100644 >> --- a/tools/virsh-host.c >> +++ b/tools/virsh-host.c >> @@ -114,6 +114,10 @@ static const vshCmdOptDef opts_domcapabilities[] = { >> .type = VSH_OT_BOOL, >> .help = N_("wrap xpath results in an common root element"), >> }, >> + {.name = "disable-deprecated-features", >> + .type = VSH_OT_BOOL, >> + .help = N_("report host CPU model with deprecated features >> disabled"), >> + }, >> {.name = NULL} >> }; >> @@ -126,10 +130,13 @@ cmdDomCapabilities(vshControl *ctl, const vshCmd >> *cmd) >> const char *arch = NULL; >> const char *machine = NULL; >> const char *xpath = NULL; >> - const unsigned int flags = 0; /* No flags so far */ >> + unsigned int flags = 0; >> bool wrap = vshCommandOptBool(cmd, "wrap"); >> virshControl *priv = ctl->privData; >> + if (vshCommandOptBool(cmd, "disable-deprecated-features")) >> + flags |= >> VIR_CONNECT_GET_DOMAIN_CAPABILITIES_DISABLE_DEPRECATED_FEATURES; >> + >> if (vshCommandOptString(ctl, cmd, "virttype", &virttype) < 0 || >> vshCommandOptString(ctl, cmd, "emulatorbin", &emulatorbin) < >> 0 || >> vshCommandOptString(ctl, cmd, "arch", &arch) < 0 || > > -- Mit freundlichen Grüßen/Kind regards Boris Fiuczynski IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Wolfgang Wendt Geschäftsführung: David Faller Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294

1 0