External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-27 08:05:24 +00:00
Code Issues Packages Projects Releases Wiki Activity
d1385232a0
libvirt/tests/domaincapsdata/qemu_6.0.0-tcg.x86_64.xml

253 lines
8.3 KiB
XML
Raw Normal View History

tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<domainCapabilities>
<path>/usr/bin/qemu-system-x86_64</path>
<domain>qemu</domain>
<machine>pc-i440fx-6.0</machine>
<arch>x86_64</arch>
<vcpu max='255'/>
<iothreads supported='yes'/>
<os supported='yes'>
<enum name='firmware'>
<value>bios</value>
<value>efi</value>
</enum>
<loader supported='yes'>
<value>/usr/share/AAVMF/AAVMF_CODE.fd</value>
<value>/usr/share/AAVMF/AAVMF32_CODE.fd</value>
<value>/usr/share/OVMF/OVMF_CODE.fd</value>
<enum name='type'>
<value>rom</value>
<value>pflash</value>
</enum>
<enum name='readonly'>
<value>yes</value>
<value>no</value>
</enum>
<enum name='secure'>
<value>no</value>
</enum>
</loader>
</os>
<cpu>
<mode name='host-passthrough' supported='no'/>
qemu: wire up support for maximum CPU model The "max" model can be treated the same way as "host" model in general. Reviewed-by: Pavel Hrdina <phrdina@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-02-05 18:35:10 +00:00
<mode name='maximum' supported='yes'>
<enum name='maximumMigratable'>
<value>on</value>
<value>off</value>
</enum>
</mode>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<mode name='host-model' supported='yes'>
cpu_x86: Penalize disabled features when computing CPU model For finding the best matching CPU model for a given set of features while we don't know the CPU signature (i.e., when computing a baseline CPU model) we've been using a "shortest list of features" heuristics. This works well if new CPU models are supersets of older models, but that's not always the case. As a result it may actually select a new CPU model as a baseline while removing some features from it to make it compatible with older models. This is in general worse than using an old CPU model with a bunch of added features as a guest OS or apps may crash when using features that were disabled. On the other hand we don't want to end up with a very old model which would guarantee no disabled features as it could stop a guest OS or apps from using some features provided by the CPU because they would not expect them on such an old CPU. This patch changes the heuristics to something in between. Enabled and disabled features are counted separately so that a CPU model requiring some features to be disabled looks worse than a model with fewer disabled features even if its complete list of features is longer. The penalty given for each additional disabled feature gets bigger to make longer list of disabled features look even worse. https://bugzilla.redhat.com/show_bug.cgi?id=1851227 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-04-26 13:06:30 +00:00
<model fallback='forbid'>Opteron_G3</model>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<vendor>AMD</vendor>
<feature policy='require' name='acpi'/>
<feature policy='require' name='ss'/>
cpu_x86: Penalize disabled features when computing CPU model For finding the best matching CPU model for a given set of features while we don't know the CPU signature (i.e., when computing a baseline CPU model) we've been using a "shortest list of features" heuristics. This works well if new CPU models are supersets of older models, but that's not always the case. As a result it may actually select a new CPU model as a baseline while removing some features from it to make it compatible with older models. This is in general worse than using an old CPU model with a bunch of added features as a guest OS or apps may crash when using features that were disabled. On the other hand we don't want to end up with a very old model which would guarantee no disabled features as it could stop a guest OS or apps from using some features provided by the CPU because they would not expect them on such an old CPU. This patch changes the heuristics to something in between. Enabled and disabled features are counted separately so that a CPU model requiring some features to be disabled looks worse than a model with fewer disabled features even if its complete list of features is longer. The penalty given for each additional disabled feature gets bigger to make longer list of disabled features look even worse. https://bugzilla.redhat.com/show_bug.cgi?id=1851227 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-04-26 13:06:30 +00:00
<feature policy='require' name='pclmuldq'/>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<feature policy='require' name='monitor'/>
cpu_x86: Penalize disabled features when computing CPU model For finding the best matching CPU model for a given set of features while we don't know the CPU signature (i.e., when computing a baseline CPU model) we've been using a "shortest list of features" heuristics. This works well if new CPU models are supersets of older models, but that's not always the case. As a result it may actually select a new CPU model as a baseline while removing some features from it to make it compatible with older models. This is in general worse than using an old CPU model with a bunch of added features as a guest OS or apps may crash when using features that were disabled. On the other hand we don't want to end up with a very old model which would guarantee no disabled features as it could stop a guest OS or apps from using some features provided by the CPU because they would not expect them on such an old CPU. This patch changes the heuristics to something in between. Enabled and disabled features are counted separately so that a CPU model requiring some features to be disabled looks worse than a model with fewer disabled features even if its complete list of features is longer. The penalty given for each additional disabled feature gets bigger to make longer list of disabled features look even worse. https://bugzilla.redhat.com/show_bug.cgi?id=1851227 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-04-26 13:06:30 +00:00
<feature policy='require' name='ssse3'/>
<feature policy='require' name='sse4.1'/>
<feature policy='require' name='sse4.2'/>
<feature policy='require' name='movbe'/>
<feature policy='require' name='aes'/>
<feature policy='require' name='xsave'/>
<feature policy='require' name='rdrand'/>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<feature policy='require' name='hypervisor'/>
cpu_x86: Penalize disabled features when computing CPU model For finding the best matching CPU model for a given set of features while we don't know the CPU signature (i.e., when computing a baseline CPU model) we've been using a "shortest list of features" heuristics. This works well if new CPU models are supersets of older models, but that's not always the case. As a result it may actually select a new CPU model as a baseline while removing some features from it to make it compatible with older models. This is in general worse than using an old CPU model with a bunch of added features as a guest OS or apps may crash when using features that were disabled. On the other hand we don't want to end up with a very old model which would guarantee no disabled features as it could stop a guest OS or apps from using some features provided by the CPU because they would not expect them on such an old CPU. This patch changes the heuristics to something in between. Enabled and disabled features are counted separately so that a CPU model requiring some features to be disabled looks worse than a model with fewer disabled features even if its complete list of features is longer. The penalty given for each additional disabled feature gets bigger to make longer list of disabled features look even worse. https://bugzilla.redhat.com/show_bug.cgi?id=1851227 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-04-26 13:06:30 +00:00
<feature policy='require' name='arat'/>
<feature policy='require' name='fsgsbase'/>
<feature policy='require' name='bmi1'/>
<feature policy='require' name='smep'/>
<feature policy='require' name='bmi2'/>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<feature policy='require' name='erms'/>
<feature policy='require' name='mpx'/>
cpu_x86: Penalize disabled features when computing CPU model For finding the best matching CPU model for a given set of features while we don't know the CPU signature (i.e., when computing a baseline CPU model) we've been using a "shortest list of features" heuristics. This works well if new CPU models are supersets of older models, but that's not always the case. As a result it may actually select a new CPU model as a baseline while removing some features from it to make it compatible with older models. This is in general worse than using an old CPU model with a bunch of added features as a guest OS or apps may crash when using features that were disabled. On the other hand we don't want to end up with a very old model which would guarantee no disabled features as it could stop a guest OS or apps from using some features provided by the CPU because they would not expect them on such an old CPU. This patch changes the heuristics to something in between. Enabled and disabled features are counted separately so that a CPU model requiring some features to be disabled looks worse than a model with fewer disabled features even if its complete list of features is longer. The penalty given for each additional disabled feature gets bigger to make longer list of disabled features look even worse. https://bugzilla.redhat.com/show_bug.cgi?id=1851227 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-04-26 13:06:30 +00:00
<feature policy='require' name='adx'/>
<feature policy='require' name='smap'/>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<feature policy='require' name='pcommit'/>
cpu_x86: Penalize disabled features when computing CPU model For finding the best matching CPU model for a given set of features while we don't know the CPU signature (i.e., when computing a baseline CPU model) we've been using a "shortest list of features" heuristics. This works well if new CPU models are supersets of older models, but that's not always the case. As a result it may actually select a new CPU model as a baseline while removing some features from it to make it compatible with older models. This is in general worse than using an old CPU model with a bunch of added features as a guest OS or apps may crash when using features that were disabled. On the other hand we don't want to end up with a very old model which would guarantee no disabled features as it could stop a guest OS or apps from using some features provided by the CPU because they would not expect them on such an old CPU. This patch changes the heuristics to something in between. Enabled and disabled features are counted separately so that a CPU model requiring some features to be disabled looks worse than a model with fewer disabled features even if its complete list of features is longer. The penalty given for each additional disabled feature gets bigger to make longer list of disabled features look even worse. https://bugzilla.redhat.com/show_bug.cgi?id=1851227 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-04-26 13:06:30 +00:00
<feature policy='require' name='clflushopt'/>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<feature policy='require' name='clwb'/>
<feature policy='require' name='pku'/>
<feature policy='require' name='la57'/>
cpu_x86: Penalize disabled features when computing CPU model For finding the best matching CPU model for a given set of features while we don't know the CPU signature (i.e., when computing a baseline CPU model) we've been using a "shortest list of features" heuristics. This works well if new CPU models are supersets of older models, but that's not always the case. As a result it may actually select a new CPU model as a baseline while removing some features from it to make it compatible with older models. This is in general worse than using an old CPU model with a bunch of added features as a guest OS or apps may crash when using features that were disabled. On the other hand we don't want to end up with a very old model which would guarantee no disabled features as it could stop a guest OS or apps from using some features provided by the CPU because they would not expect them on such an old CPU. This patch changes the heuristics to something in between. Enabled and disabled features are counted separately so that a CPU model requiring some features to be disabled looks worse than a model with fewer disabled features even if its complete list of features is longer. The penalty given for each additional disabled feature gets bigger to make longer list of disabled features look even worse. https://bugzilla.redhat.com/show_bug.cgi?id=1851227 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-04-26 13:06:30 +00:00
<feature policy='require' name='xsaveopt'/>
<feature policy='require' name='xgetbv1'/>
<feature policy='require' name='mmxext'/>
<feature policy='require' name='pdpe1gb'/>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<feature policy='require' name='3dnowext'/>
<feature policy='require' name='3dnow'/>
cpu_x86: Penalize disabled features when computing CPU model For finding the best matching CPU model for a given set of features while we don't know the CPU signature (i.e., when computing a baseline CPU model) we've been using a "shortest list of features" heuristics. This works well if new CPU models are supersets of older models, but that's not always the case. As a result it may actually select a new CPU model as a baseline while removing some features from it to make it compatible with older models. This is in general worse than using an old CPU model with a bunch of added features as a guest OS or apps may crash when using features that were disabled. On the other hand we don't want to end up with a very old model which would guarantee no disabled features as it could stop a guest OS or apps from using some features provided by the CPU because they would not expect them on such an old CPU. This patch changes the heuristics to something in between. Enabled and disabled features are counted separately so that a CPU model requiring some features to be disabled looks worse than a model with fewer disabled features even if its complete list of features is longer. The penalty given for each additional disabled feature gets bigger to make longer list of disabled features look even worse. https://bugzilla.redhat.com/show_bug.cgi?id=1851227 Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2022-04-26 13:06:30 +00:00
<feature policy='require' name='cr8legacy'/>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<feature policy='require' name='npt'/>
<feature policy='disable' name='misalignsse'/>
</mode>
<mode name='custom' supported='yes'>
<model usable='yes'>qemu64</model>
<model usable='yes'>qemu32</model>
<model usable='no'>phenom</model>
<model usable='yes'>pentium3</model>
<model usable='yes'>pentium2</model>
<model usable='yes'>pentium</model>
<model usable='yes'>n270</model>
<model usable='yes'>kvm64</model>
<model usable='yes'>kvm32</model>
<model usable='yes'>coreduo</model>
<model usable='yes'>core2duo</model>
<model usable='yes'>athlon</model>
<model usable='no'>Westmere-IBRS</model>
<model usable='yes'>Westmere</model>
<model usable='no'>Snowridge</model>
<model usable='no'>Skylake-Server-noTSX-IBRS</model>
<model usable='no'>Skylake-Server-IBRS</model>
<model usable='no'>Skylake-Server</model>
<model usable='no'>Skylake-Client-noTSX-IBRS</model>
<model usable='no'>Skylake-Client-IBRS</model>
<model usable='no'>Skylake-Client</model>
<model usable='no'>SandyBridge-IBRS</model>
<model usable='no'>SandyBridge</model>
<model usable='yes'>Penryn</model>
<model usable='no'>Opteron_G5</model>
<model usable='no'>Opteron_G4</model>
<model usable='no'>Opteron_G3</model>
<model usable='yes'>Opteron_G2</model>
<model usable='yes'>Opteron_G1</model>
<model usable='no'>Nehalem-IBRS</model>
<model usable='yes'>Nehalem</model>
<model usable='no'>IvyBridge-IBRS</model>
<model usable='no'>IvyBridge</model>
<model usable='no'>Icelake-Server-noTSX</model>
<model usable='no'>Icelake-Server</model>
qemu: report whether a CPU model is deprecated in dom capabilities QEMU has the ability to mark CPUs as deprecated. This should be exposed to management applications in the domain capabilities. This attribute is only set when the model is actually deprecated. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-01-22 11:15:08 +00:00
<model usable='no' deprecated='yes'>Icelake-Client-noTSX</model>
<model usable='no' deprecated='yes'>Icelake-Client</model>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<model usable='no'>Haswell-noTSX-IBRS</model>
<model usable='no'>Haswell-noTSX</model>
<model usable='no'>Haswell-IBRS</model>
<model usable='no'>Haswell</model>
<model usable='no'>EPYC-Rome</model>
tests: qemucapabilities: Update qemu caps for object-add qapification qemu qapified object-add, which means that it's introspectable via query-qmp-schema. Update the qemu-6.0 capabilities to commit v5.2.0-3205-g92566947b3 Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2021-02-24 15:40:45 +00:00
<model usable='no'>EPYC-Milan</model>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<model usable='no'>EPYC-IBPB</model>
<model usable='no'>EPYC</model>
<model usable='no'>Dhyana</model>
<model usable='no'>Cooperlake</model>
<model usable='yes'>Conroe</model>
<model usable='no'>Cascadelake-Server-noTSX</model>
<model usable='no'>Cascadelake-Server</model>
<model usable='no'>Broadwell-noTSX-IBRS</model>
<model usable='no'>Broadwell-noTSX</model>
<model usable='no'>Broadwell-IBRS</model>
<model usable='no'>Broadwell</model>
<model usable='yes'>486</model>
</mode>
</cpu>
qemu: capabilities: fill in domcaps <memoryBacking> Signed-off-by: Kristina Hanicova <khanicov@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2021-07-15 12:18:05 +00:00
<memoryBacking supported='yes'>
<enum name='sourceType'>
<value>file</value>
<value>anonymous</value>
<value>memfd</value>
</enum>
</memoryBacking>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
<devices>
<disk supported='yes'>
<enum name='diskDevice'>
<value>disk</value>
<value>cdrom</value>
<value>floppy</value>
<value>lun</value>
</enum>
<enum name='bus'>
<value>ide</value>
<value>fdc</value>
<value>scsi</value>
<value>virtio</value>
<value>usb</value>
<value>sata</value>
</enum>
<enum name='model'>
<value>virtio</value>
<value>virtio-transitional</value>
<value>virtio-non-transitional</value>
</enum>
</disk>
<graphics supported='yes'>
<enum name='type'>
<value>sdl</value>
<value>vnc</value>
<value>spice</value>
<value>egl-headless</value>
</enum>
</graphics>
<video supported='yes'>
<enum name='modelType'>
<value>vga</value>
<value>cirrus</value>
<value>vmvga</value>
<value>qxl</value>
<value>virtio</value>
<value>none</value>
<value>bochs</value>
<value>ramfb</value>
</enum>
</video>
<hostdev supported='yes'>
<enum name='mode'>
<value>subsystem</value>
</enum>
<enum name='startupPolicy'>
<value>default</value>
<value>mandatory</value>
<value>requisite</value>
<value>optional</value>
</enum>
<enum name='subsysType'>
<value>usb</value>
<value>pci</value>
<value>scsi</value>
</enum>
<enum name='capsType'/>
<enum name='pciBackend'>
<value>default</value>
<value>vfio</value>
</enum>
</hostdev>
<rng supported='yes'>
<enum name='model'>
<value>virtio</value>
<value>virtio-transitional</value>
<value>virtio-non-transitional</value>
</enum>
<enum name='backendModel'>
<value>random</value>
<value>egd</value>
<value>builtin</value>
</enum>
</rng>
qemu: capabilities: fill in domcaps <filesystem> Signed-off-by: Kristina Hanicova <khanicov@redhat.com> Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2021-05-18 12:50:51 +00:00
<filesystem supported='yes'>
<enum name='driverType'>
<value>path</value>
<value>handle</value>
<value>virtiofs</value>
</enum>
</filesystem>
qemu: fill in domain capabilities for TPMs This reports what TPM features QEMU supports, provided that swtpm is installed in the host. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-11-23 17:18:36 +00:00
<tpm supported='yes'>
<enum name='model'>
<value>tpm-tis</value>
<value>tpm-crb</value>
</enum>
<enum name='backendModel'>
<value>passthrough</value>
qemu: mock swtpm initialization in tests The domain capabilities won't report TPM support unless SWTPM can be initialized. To avoid relying on the swtpm install in the host, mock the entire initialization method, since all it needs todo is return a non-error value. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-11-23 17:39:16 +00:00
<value>emulator</value>
qemu: fill in domain capabilities for TPMs This reports what TPM features QEMU supports, provided that swtpm is installed in the host. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-11-23 17:18:36 +00:00
</enum>
testutilsqemu: Fake TPM versions Because of v8.5.0-rc1~25 we are already faking TPM support for domaincaps. Might as well fake supported TPM versions. The swtpm binary supports both TPM versions since its first release, but pretend it isn't the case. For QEMU-5.2 and older pretend only TPM-1.2 is available, QEMU-6.* has both TPM-1.2 and TPM-2.0 and QEMU-7.0 and newer has only TPM-2.0 available. This way, domaincaps are more dispersed. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Kristina Hanicova <khanicov@redhat.com>
2022-07-20 07:51:55 +00:00
<enum name='backendVersion'>
<value>1.2</value>
<value>2.0</value>
</enum>
qemu: fill in domain capabilities for TPMs This reports what TPM features QEMU supports, provided that swtpm is installed in the host. Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-11-23 17:18:36 +00:00
</tpm>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
</devices>
<features>
<gic supported='no'/>
<vmcoreinfo supported='yes'/>
<genid supported='yes'/>
<backingStoreInput supported='yes'/>
<backup supported='no'/>
tests: add AMD SEV bits into qemu-6.0.0 replies Currently we only have AMD SEV bits in qemu-2.12.0 replies which is way too old to test new features that require AMD SEV as well. Signed-off-by: Pavel Hrdina <phrdina@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
2021-06-10 13:54:59 +00:00
<sev supported='yes'>
<cbitpos>47</cbitpos>
<reducedPhysBits>1</reducedPhysBits>
qemu: report max number of SEV guests Different CPU generations have different limits on the number of SEV/SEV-ES guests that can be run. Since both limits come from the same overall set, there is typically also BIOS config to set the tradeoff betweeen SEV and SEV-ES guest limits. This is important information to expose for a mgmt application scheduling guests to hosts. Reviewed-by: Peter Krempa <pkrempa@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-12-08 19:53:45 +00:00
<maxGuests>59</maxGuests>
<maxESGuests>450</maxESGuests>
tests: add AMD SEV bits into qemu-6.0.0 replies Currently we only have AMD SEV bits in qemu-2.12.0 replies which is way too old to test new features that require AMD SEV as well. Signed-off-by: Pavel Hrdina <phrdina@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
2021-06-10 13:54:59 +00:00
</sev>
tests: qemucapabilities: Add test data for qemu-6.0 release cycle Add the capabilities test data for the next qemu development cycle so that we stay up to date. Based on v5.2.0-1374-g9cd69f1a27 Notable changes detected by libvirt are the new machine types and 'intel-pt-lip', 'avx512-fp16', 'kvm-msi-ext-dest-id' cpu features reported by qemu. Other qemu changes not detected by libvirt include removal of the 'change' command, addition of 'sev-inject-launch-secret', 'yank', 'query-yank' commands and other device properties. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-01-12 14:48:59 +00:00
</features>
</domainCapabilities>
Reference in New Issue Copy Permalink