External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-23 06:05:27 +00:00
Code Issues Packages Projects Releases Wiki Activity
eb7a6e4877
libvirt/tests/qemucapabilitiesdata/caps_5.0.0_riscv64.xml

127 lines
4.1 KiB
XML
Raw Normal View History

tests: Add capabilities for QEMU 5.0.0 on riscv64 The churn in the output files is caused primarily by the fact that blockdev support has been introduced. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-05-06 08:33:58 +00:00
<qemuCaps>
<emulator>/usr/bin/qemu-system-riscv64</emulator>
<qemuctime>0</qemuctime>
<selfctime>0</selfctime>
<selfvers>0</selfvers>
qemu: capabilities: Un-retire QEMU_CAPS_SDL SDL graphics can be compiled out in qemu so we need to be able to know whether the given qemu version support it. Base the capability on the presence of the 'sdl' member in 'query-display-options' or imply it if 'query-display-options' is not supported as we implied it before for all versions. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Thomas Huth <thuth@redhat.com>
2021-06-15 09:38:26 +00:00
<flag name='sdl'/>
tests: Add capabilities for QEMU 5.0.0 on riscv64 The churn in the output files is caused primarily by the fact that blockdev support has been introduced. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-05-06 08:33:58 +00:00
<flag name='spice'/>
<flag name='hda-duplex'/>
<flag name='ccid-emulated'/>
<flag name='ccid-passthru'/>
<flag name='piix3-usb-uhci'/>
<flag name='piix4-usb-uhci'/>
<flag name='usb-ehci'/>
<flag name='ich9-usb-ehci1'/>
<flag name='vt82c686b-usb-uhci'/>
<flag name='pci-ohci'/>
<flag name='usb-redir'/>
<flag name='usb-hub'/>
<flag name='ich9-ahci'/>
<flag name='virtio-blk-pci.scsi'/>
<flag name='scsi-disk.channel'/>
<flag name='scsi-block'/>
<flag name='hda-micro'/>
<flag name='nec-usb-xhci'/>
<flag name='lsi'/>
<flag name='virtio-scsi-pci'/>
<flag name='usb-redir.filter'/>
<flag name='seccomp-sandbox'/>
<flag name='vnc'/>
<flag name='VGA'/>
<flag name='cirrus-vga'/>
<flag name='vmware-svga'/>
<flag name='usb-serial'/>
<flag name='virtio-rng'/>
<flag name='rng-random'/>
<flag name='rng-egd'/>
<flag name='megasas'/>
<flag name='pci-bridge'/>
<flag name='vfio-pci'/>
<flag name='dmi-to-pci-bridge'/>
<flag name='usb-storage'/>
<flag name='virtio-mmio'/>
<flag name='ich9-intel-hda'/>
qemu: stop passing -enable-fips to QEMU >= 5.2.0 Use of the -enable-fips option is being deprecated in QEMU >= 5.2.0. If FIPS compliance is required, QEMU must be built with libcrypt which will unconditionally enforce it. Thus there is no need for libvirt to pass -enable-fips to modern QEMU. Unfortunately there was never any way to probe for -enable-fips in the first instance, it was enabled by libvirt based on version number originally, and then later unconditionally enabled when libvirt dropped support for older QEMU. Similarly we now use a version number check to decide when to stop passing -enable-fips. Note that the qemu-5.2 capabilities are currently from the pre-release version and will be updated once qemu-5.2 is released. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2020-10-20 16:48:59 +00:00
<flag name='enable-fips'/>
tests: Add capabilities for QEMU 5.0.0 on riscv64 The churn in the output files is caused primarily by the fact that blockdev support has been introduced. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-05-06 08:33:58 +00:00
<flag name='usb-kbd'/>
<flag name='usb-audio'/>
<flag name='migrate-rdma'/>
<flag name='VGA.vgamem_mb'/>
<flag name='vmware-svga.vgamem_mb'/>
<flag name='pci-serial'/>
<flag name='gpex-pcihost'/>
<flag name='ioh3420'/>
<flag name='x3130-upstream'/>
<flag name='xio3130-downstream'/>
<flag name='rtl8139'/>
<flag name='e1000'/>
<flag name='virtio-net'/>
<flag name='virtio-gpu'/>
<flag name='virtio-gpu.virgl'/>
<flag name='virtio-keyboard'/>
<flag name='virtio-mouse'/>
<flag name='virtio-tablet'/>
<flag name='virtio-input-host'/>
<flag name='virtio-balloon-pci.deflate-on-oom'/>
<flag name='mptsas1068'/>
<flag name='spice-gl'/>
<flag name='ivshmem-plain'/>
<flag name='ivshmem-doorbell'/>
<flag name='vhost-scsi'/>
<flag name='spice-rendernode'/>
<flag name='pcie-root-port'/>
<flag name='qemu-xhci'/>
<flag name='chardev-reconnect'/>
<flag name='vxhs'/>
<flag name='pcie-pci-bridge'/>
<flag name='nbd-tls'/>
<flag name='pr-manager-helper'/>
<flag name='screendump_device'/>
<flag name='hda-output'/>
<flag name='vhost-vsock'/>
qemu: capabilities: Un-retire QEMU_CAPS_EGL_HEADLESS egl-headless graphics can be compiled out in qemu so we need to be able to know whether the given qemu version support it. Base the capability on the presence of the 'egl-headless' member in 'query-display-options' or imply it if 'query-display-options' is not supported as we implied it before for all versions. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Thomas Huth <thuth@redhat.com>
2021-06-15 09:38:26 +00:00
<flag name='egl-headless'/>
tests: Add capabilities for QEMU 5.0.0 on riscv64 The churn in the output files is caused primarily by the fact that blockdev support has been introduced. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-05-06 08:33:58 +00:00
<flag name='memory-backend-memfd'/>
<flag name='memory-backend-memfd.hugetlb'/>
<flag name='egl-headless.rendernode'/>
<flag name='memory-backend-file.pmem'/>
<flag name='virtio-pci-non-transitional'/>
<flag name='nbd-bitmap'/>
<flag name='bochs-display'/>
<flag name='migration-file-drop-cache'/>
<flag name='dbus-vmstate'/>
<flag name='vhost-user-gpu'/>
<flag name='drive-nvme'/>
<flag name='smp-dies'/>
<flag name='rng-builtin'/>
<flag name='vhost-user-fs'/>
<flag name='query-named-block-nodes.flat'/>
<flag name='blockdev-snapshot.allow-write-only-overlay'/>
<flag name='fsdev.multidevs'/>
<flag name='pcie-root-port.hotplug'/>
<flag name='aio.io_uring'/>
<flag name='tcg'/>
qemu: capabilities: Introduce QEMU_CAPS_VIRTIO_BLK_SCSI_DEFAULT_DISABLED Historically the 'scsi' passthrough feature of virtio-blk-pci was enabled by default. Libvirt was disabling it due to security implications outlined in libvirt commit v0.9.9-4-g177db08775 if it was not explicitly requested. In qemu commit v2.4.0-1566-ged65fd1a27 the default value was changed to disabled in preparation for virtio-1. Starting from QEMU-5.0 the 'scsi' property was also deprecated. There replacement for the functionality is to use 'virtio-scsi' for the purpose. This isn't a direct replacement though. Add capability named QEMU_CAPS_VIRTIO_BLK_SCSI_DEFAULT_DISABLED which allows us to stop formatting the 'scsi=' property if it's disabled by default and not requested so that we don't use deprecated features. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-05-06 20:01:51 +00:00
<flag name='virtio-blk-pci.scsi.default.disabled'/>
qemu: pvscsi: Add capability This capability flags support for `-device pvscsi`, which provides the VMware paravirtual SCSI controller. Signed-off-by: Chris Jester-Young <cky@cky.nz> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
2020-05-13 01:55:45 +00:00
<flag name='pvscsi'/>
qemu: Introduce QEMU_CAPS_NUMA_HMAT capability This capability tracks whether QEMU is capable of defining HMAT ACPI table for the guest. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
2020-05-27 09:00:07 +00:00
<flag name='numa.hmat'/>
qemu: add capabilities for the three ESP family SCSI controllers Probing for the NCR53C90 controller is a little unusual. The qom-list-types QMP command returns a list of all types known to the QEMU binary. It does not distinguish devices which are user creatable from those which are built-in. Any QEMU target that supports PCI will have the DC390 / AM53C974 devices because they are PCI based. Due to code dependencies in QEMU though, existence of these two devices will also pull in the NCR53C90 device (called just 'esp' in QEMU). The NCR53C90 is not user-creatable and can only be used when built-in to the machine type. This is only the case on sparc machines, and certain mips64 and m68k machines. IOW, we don't rely on qom-list-types as a guide for existence of NCR53C90, as it shouldn't really exist in most QEMU binaries. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2020-11-18 16:37:54 +00:00
<flag name='dc390'/>
<flag name='am53c974'/>
qemu_capabilities: introduce vhost-user-blk capability Signed-off-by: Pavel Hrdina <phrdina@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
2021-02-02 12:37:02 +00:00
<flag name='vhost-user-blk'/>
qemu_capabilities: Introduce QEMU_CAPS_X_USE_CANONICAL_PATH_FOR_RAMBLOCK_ID This capability tracks whether memory-backend-file has "x-use-canonical-path-for-ramblock-id" attribute. Introduced into QEMU by commit fa0cb34d2210cc749b9a70db99bb41c56ad20831. As of QEMU commit 8db0b20415c129cf5e577a593a4a0372d90b7cc9 the property is considered stable by qemu despite the 'x-' prefix to preserve compatibility with released qemu versions. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
2021-01-11 17:15:57 +00:00
<flag name='memory-backend-file.x-use-canonical-path-for-ramblock-id'/>
qemu: implement setting of rotation rate for SCSI/IDE disks This is available in QEMU with "ide-hd" and "scsi-hd" device types. It was originally mistakenly added to the "scsi-block" device type too, but later removed. This doesn't affect libvirt since we restrict usage to device=disk. When this property is not set then QEMU's default behaviour is to not report any rotation rate information, which causes most guest OS to assume rotational storage. https://bugzilla.redhat.com/show_bug.cgi?id=1498955 Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2021-03-31 09:17:07 +00:00
<flag name='rotation-rate'/>
qemu_capabilities: Add QEMU_CAPS_INPUT_LINUX Signed-off-by: Kristina Hanicova <khanicov@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2021-05-21 11:01:06 +00:00
<flag name='input-linux'/>
qemu: add QEMU_CAPS_VIRTIO_BLK_QUEUE_SIZE capability To support virtio-blk queue-size option, this commit adds capability detection to the option. Signed-off-by: Hiroki Narukawa <hnarukaw@yahoo-corp.jp> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
2021-09-09 03:34:47 +00:00
<flag name='virtio-blk.queue-size'/>
qemu_capabilities: Detect memory-backend-*.prealloc-threads property The prealloc-threads is property of memory-backend class which is parent to the other three classes memory-backend-{ram,file,memfd}. Therefore the property is present for all, or none if QEMU is older than v5.0.0-rc0~75^2~1^2~3 which introduced the property. Anyway, the .reserve property is the same story, and we chose memory-backend-file to detect it, so stick with our earlier decision and use the same backend to detect this new property. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Martin Kletzander <mkletzan@redhat.com>
2022-03-21 15:55:05 +00:00
<flag name='memory-backend-file.prealloc-threads'/>
qemu: Introduce QEMU_CAPS_DEVICE_VIRTIO_IOMMU_PCI This capability detects the availability of the virtio-iommu-pci device. Note that, while this device is present even in somewhat old versions of QEMU, it's only some recent changes that made it actually usable for our purposes. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2021-09-22 17:15:01 +00:00
<flag name='virtio-iommu-pci'/>
qemu_capabilities: Track usb-host.guest-resets-all capability We will need two attributes of usb-host device to set: guest-reset and guest-resets-all. The former was introduced in QEMU v4.0.0-rc0~56^2 and the other in v4.2.0-rc1~9^2. Hence, track the latter only as it's only starting from that commit when QEMU has both attributes. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2022-07-12 10:19:37 +00:00
<flag name='usb-host.guest-resets-all'/>
capabilities: introduce crypto device Changes in this commit: - docs: formatdomaincaps.rst - conf: crypto related domain caps - qemu: crypto related - tests: crypto related test Signed-off-by: zhenwei pi <pizhenwei@bytedance.com> Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2023-01-17 01:46:51 +00:00
<flag name='virtio-crypto'/>
tests: Add capabilities for QEMU 5.0.0 on riscv64 The churn in the output files is caused primarily by the fact that blockdev support has been introduced. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-05-06 08:33:58 +00:00
<version>5000000</version>
<microcodeVersion>0</microcodeVersion>
<package>v5.0.0</package>
<arch>riscv64</arch>
<machine type='tcg' name='virt' maxCpus='8' defaultCPU='rv64-riscv-cpu'/>
qemu: Change default machine type for RISC-V It's quite difficult, if not impossible, to create a working RISC-V VMs using the current default machine type of 'spike_v1.10'. Change the default to the more appropriate and virtualization friendly 'virt' machine type. Signed-off-by: Jim Fehlig <jfehlig@suse.com> Reviewed-by: Andrea Bolognani <abologna@redhat.com>
2023-04-14 17:01:33 +00:00
<machine type='tcg' name='spike_v1.10' maxCpus='1'/>
tests: Add capabilities for QEMU 5.0.0 on riscv64 The churn in the output files is caused primarily by the fact that blockdev support has been introduced. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-05-06 08:33:58 +00:00
<machine type='tcg' name='spike' maxCpus='1' default='yes' defaultCPU='rv64gcsu-v1.10.0-riscv-cpu'/>
<machine type='tcg' name='sifive_e' maxCpus='1'/>
<machine type='tcg' name='sifive_u' maxCpus='5'/>
<machine type='tcg' name='spike_v1.9.1' maxCpus='1'/>
</qemuCaps>
Reference in New Issue Copy Permalink