External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-23 14:15:28 +00:00
Code Issues Packages Projects Releases Wiki Activity
425886ea99
libvirt/tests/qemucapabilitiesdata/caps_4.0.0.aarch64.xml

364 lines
19 KiB
XML
Raw Normal View History

tests: Add capabilities for QEMU 4.0.0 on aarch64 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-04-29 12:06:02 +00:00
<qemuCaps>
qemu: store the emulator name in the capabilities XML We don't need this for any functional purpose, but when debugging hosts it is useful to know what binary a given capabilities XML document is associated with. Reviewed-by: Michal Privoznik <mprivozn@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2019-12-10 10:23:14 +00:00
<emulator>/usr/bin/qemu-system-aarch64</emulator>
tests: Add capabilities for QEMU 4.0.0 on aarch64 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-04-29 12:06:02 +00:00
<qemuctime>0</qemuctime>
<selfctime>0</selfctime>
<selfvers>0</selfvers>
<flag name='kvm'/>
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 4.0.0 on aarch64 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-04-29 12:06:02 +00:00
<flag name='hda-duplex'/>
<flag name='virtio-tx-alg'/>
<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-hub'/>
<flag name='ich9-ahci'/>
<flag name='no-acpi'/>
<flag name='virtio-blk-pci.scsi'/>
<flag name='scsi-disk.channel'/>
<flag name='scsi-block'/>
<flag name='hda-micro'/>
<flag name='dump-guest-memory'/>
<flag name='nec-usb-xhci'/>
<flag name='lsi'/>
<flag name='virtio-scsi-pci'/>
<flag name='blockio'/>
<flag name='ide-drive.wwn'/>
<flag name='scsi-disk.wwn'/>
<flag name='seccomp-sandbox'/>
<flag name='vnc'/>
<flag name='VGA'/>
<flag name='cirrus-vga'/>
<flag name='vmware-svga'/>
<flag name='usb-serial'/>
<flag name='nbd-server'/>
<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='drive-discard'/>
<flag name='dmi-to-pci-bridge'/>
<flag name='usb-storage'/>
<flag name='usb-storage.removable'/>
<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 4.0.0 on aarch64 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-04-29 12:06:02 +00:00
<flag name='usb-kbd'/>
<flag name='active-commit'/>
<flag name='change-backing-file'/>
<flag name='memory-backend-ram'/>
<flag name='numa'/>
<flag name='memory-backend-file'/>
<flag name='usb-audio'/>
<flag name='iothread'/>
<flag name='migrate-rdma'/>
<flag name='VGA.vgamem_mb'/>
<flag name='vmware-svga.vgamem_mb'/>
<flag name='pci-serial'/>
<flag name='aarch64-off'/>
<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='gic-version'/>
<flag name='virtio-gpu'/>
<flag name='virtio-keyboard'/>
<flag name='virtio-mouse'/>
<flag name='virtio-tablet'/>
<flag name='virtio-input-host'/>
<flag name='chardev-file-append'/>
<flag name='vserport-change-event'/>
<flag name='virtio-balloon-pci.deflate-on-oom'/>
<flag name='mptsas1068'/>
<flag name='chardev-logfile'/>
<flag name='nec-usb-xhci-ports'/>
<flag name='virtio-scsi-pci.iothread'/>
<flag name='drive-detect-zeroes'/>
<flag name='virtio-pci-disable-legacy'/>
<flag name='query-hotpluggable-cpus'/>
<flag name='virtio-net.rx_queue_size'/>
<flag name='ivshmem-plain'/>
<flag name='ivshmem-doorbell'/>
<flag name='gluster.debug_level'/>
<flag name='vhost-scsi'/>
<flag name='virtio-net.host_mtu'/>
<flag name='pcie-root-port'/>
<flag name='query-cpu-definitions'/>
<flag name='block-write-threshold'/>
<flag name='query-named-block-nodes'/>
<flag name='qemu-xhci'/>
<flag name='virtio-net.tx_queue_size'/>
<flag name='chardev-reconnect'/>
<flag name='vxhs'/>
<flag name='virtio-blk.num-queues'/>
<flag name='vmcoreinfo'/>
<flag name='disk-share-rw'/>
<flag name='pl011'/>
<flag name='dump-completed'/>
<flag name='qcow2-luks'/>
<flag name='pcie-pci-bridge'/>
<flag name='query-cpus-fast'/>
<flag name='disk-write-cache'/>
<flag name='nbd-tls'/>
<flag name='pr-manager-helper'/>
<flag name='qom-list-properties'/>
<flag name='memory-backend-file.discard-data'/>
<flag name='screendump_device'/>
<flag name='hda-output'/>
<flag name='blockdev-del'/>
<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 4.0.0 on aarch64 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-04-29 12:06:02 +00:00
<flag name='vfio-pci.display'/>
<flag name='memory-backend-memfd'/>
<flag name='memory-backend-memfd.hugetlb'/>
<flag name='iothread.poll-max-ns'/>
<flag name='egl-headless.rendernode'/>
<flag name='memory-backend-file.align'/>
<flag name='memory-backend-file.pmem'/>
<flag name='scsi-disk.device_id'/>
<flag name='virtio-pci-non-transitional'/>
<flag name='query-current-machine'/>
qemu: Introduce QEMU_CAPS_MACHINE_VIRT_IOMMU This capability can be used to figure out whether the QEMU binary at hand supports the machine type property we need in order to enable SMMUv3 IOMMU support. Unfortunately we can't avoid probing the RISC-V binaries along with the ARM ones, since both architectures have their own 'virt' machine type. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2019-05-17 07:15:27 +00:00
<flag name='machine.virt.iommu'/>
backup: Add two new qemu capabilities Add two capabilities for testing features required for the upcoming virDomainBackupBegin: use block-dirty-bitmap-merge as the generic witness of bitmap support needed for checkpoints (since all of the bitmap management functionalities were finalized in the same qemu 4.0 release), and the bitmap parameter to nbd-server-add for pull-mode backup support. Even though both capabilities are likely to be present or absent together (that is, it is unlikely to encounter a qemu that backports only one of the two), it still makes sense to keep two capabilities as the two uses are orthogonal (full backups don't require checkpoints, push mode backups don't require NBD bitmap support, and checkpoints can be used for more than just incremental backups). Existing code is not affected by the new capabilities. Signed-off-by: Eric Blake <eblake@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-06-06 02:25:05 +00:00
<flag name='bitmap-merge'/>
<flag name='nbd-bitmap'/>
qemu: Add bochs-display capability Check whether qemu supports the bochs-display device and set a capability. Update tests. Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com> Signed-off-by: Ján Tomko <jtomko@redhat.com>
2019-07-12 20:12:15 +00:00
<flag name='bochs-display'/>
qemu: Check for drop-cache capability QEMU 4.0.0 and newer automatically drops caches at the end of migration. Let's check for this capability so that we can allow migration when disk cache is turned on. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Acked-By: Peter Krempa <pkrempa@redhat.com>
2019-08-13 13:17:36 +00:00
<flag name='migration-file-drop-cache'/>
qemu: add ramfb capability Add a qemu capbility to see if the standalone ramfb device is available. Reviewed-by: Cole Robinson <crobinso@redhat.com> Signed-off-by: Jonathon Jongsma <jjongsma@redhat.com>
2019-09-13 21:20:28 +00:00
<flag name='ramfb'/>
qemu: Introduce QEMU_CAPS_ARM_MAX_CPU Mirrors the existing QEMU_CAPS_X86_MAX_CPU. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Tested-by: Andrew Jones <drjones@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2019-07-08 11:21:00 +00:00
<flag name='arm-max-cpu'/>
qemu_capabilities: Introduce QEMU_CAPS_DRIVE_NVME This capability tracks if qemu is capable of: -drive file.driver=nvme The feature was added in QEMU's commit of v2.12.0-rc0~104^2~2. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Cole Robinson <crobinso@redhat.com>
2019-06-05 14:11:03 +00:00
<flag name='drive-nvme'/>
qemu: Introduce QEMU_CAPS_TCG Since QEMU 2.10 it is possible to disable TCG when building QEMU. Introduce a capability that reflects this. Signed-off-by: Tobin Feldman-Fitzthum <tobin@linux.vnet.ibm.com> Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-04-28 09:04:14 +00:00
<flag name='tcg'/>
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: Probe for a few params supported by migrate-set-parameters These parameters were originally set via dedicated commands which are now deprecated. We want to use migrate-set-parameters instead if possible. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Peter Krempa <pkrempa@redhat.com>
2020-06-10 13:09:00 +00:00
<flag name='migration-param.bandwidth'/>
<flag name='migration-param.downtime'/>
<flag name='migration-param.xbzrle-cache-size'/>
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: 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
<flag name='cpu-max'/>
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: capabilities: Introduce QEMU_CAPS_QUERY_DISPLAY_OPTIONS The command allows to query various display-related options. The absence of the command will be used to imply certain video-related capabilities before we would be able to detect them. 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:31:35 +00:00
<flag name='query-display-options'/>
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'/>
tests: Add capabilities for QEMU 4.0.0 on aarch64 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-04-29 12:06:02 +00:00
<version>4000000</version>
<kvmVersion>0</kvmVersion>
tests: testQemuCapsIterate: Pass prefix and version to callback Right now we're passing a "base" string that contains both, separated by an underscore. Some changes that we're going to introduce later will require us to have the version number on its own, and instead of delegating the task of splitting the two apart to the callback it make more sense to perform it upfront. This change results in quite a bit of churn because we're now using the version number only, without the prefix, to calculate the dummy microcodeVersion. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
2019-10-22 14:08:10 +00:00
<microcodeVersion>61700240</microcodeVersion>
tests: Add capabilities for QEMU 4.0.0 on aarch64 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-04-29 12:06:02 +00:00
<package>v4.0.0</package>
<arch>aarch64</arch>
qemu: Store typename from query-cpu-definitions in qemuCaps We need to create a mapping between CPU model names and their corresponding QOM types. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2019-09-19 18:47:37 +00:00
<cpu type='kvm' name='pxa262' typename='pxa262-arm-cpu'/>
<cpu type='kvm' name='pxa270-a0' typename='pxa270-a0-arm-cpu'/>
<cpu type='kvm' name='arm1136' typename='arm1136-arm-cpu'/>
<cpu type='kvm' name='cortex-a15' typename='cortex-a15-arm-cpu'/>
<cpu type='kvm' name='pxa260' typename='pxa260-arm-cpu'/>
<cpu type='kvm' name='arm1136-r2' typename='arm1136-r2-arm-cpu'/>
<cpu type='kvm' name='pxa261' typename='pxa261-arm-cpu'/>
<cpu type='kvm' name='pxa255' typename='pxa255-arm-cpu'/>
<cpu type='kvm' name='cortex-a72' typename='cortex-a72-arm-cpu'/>
<cpu type='kvm' name='cortex-m33' typename='cortex-m33-arm-cpu'/>
<cpu type='kvm' name='arm926' typename='arm926-arm-cpu'/>
<cpu type='kvm' name='cortex-r5f' typename='cortex-r5f-arm-cpu'/>
<cpu type='kvm' name='arm11mpcore' typename='arm11mpcore-arm-cpu'/>
<cpu type='kvm' name='pxa250' typename='pxa250-arm-cpu'/>
<cpu type='kvm' name='ti925t' typename='ti925t-arm-cpu'/>
<cpu type='kvm' name='cortex-a57' typename='cortex-a57-arm-cpu'/>
<cpu type='kvm' name='sa1110' typename='sa1110-arm-cpu'/>
<cpu type='kvm' name='host' typename='host-arm-cpu'/>
<cpu type='kvm' name='arm1176' typename='arm1176-arm-cpu'/>
<cpu type='kvm' name='cortex-a53' typename='cortex-a53-arm-cpu'/>
<cpu type='kvm' name='sa1100' typename='sa1100-arm-cpu'/>
<cpu type='kvm' name='pxa270-c5' typename='pxa270-c5-arm-cpu'/>
<cpu type='kvm' name='cortex-a9' typename='cortex-a9-arm-cpu'/>
<cpu type='kvm' name='cortex-a8' typename='cortex-a8-arm-cpu'/>
<cpu type='kvm' name='cortex-a7' typename='cortex-a7-arm-cpu'/>
<cpu type='kvm' name='pxa270-c0' typename='pxa270-c0-arm-cpu'/>
<cpu type='kvm' name='arm1026' typename='arm1026-arm-cpu'/>
<cpu type='kvm' name='pxa270-b1' typename='pxa270-b1-arm-cpu'/>
<cpu type='kvm' name='cortex-m3' typename='cortex-m3-arm-cpu'/>
<cpu type='kvm' name='max' typename='max-arm-cpu'/>
<cpu type='kvm' name='cortex-m4' typename='cortex-m4-arm-cpu'/>
<cpu type='kvm' name='pxa270-b0' typename='pxa270-b0-arm-cpu'/>
<cpu type='kvm' name='arm946' typename='arm946-arm-cpu'/>
<cpu type='kvm' name='cortex-m0' typename='cortex-m0-arm-cpu'/>
<cpu type='kvm' name='cortex-r5' typename='cortex-r5-arm-cpu'/>
<cpu type='kvm' name='pxa270-a1' typename='pxa270-a1-arm-cpu'/>
<cpu type='kvm' name='pxa270' typename='pxa270-arm-cpu'/>
qemu: Track numa-mem-supported machine attribute There is 'numa-mem-supported' machine attribute which specifies whether '-numa mem=' is supported. Store it in our capabilities as it will be used in later commits when building the command line. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2020-05-14 11:11:01 +00:00
<machine type='kvm' name='integratorcp' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='nuri' maxCpus='2' numaMemSupported='yes'/>
<machine type='kvm' name='mps2-an511' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='verdex' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='mps2-an505' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='virt-3.0' maxCpus='512' numaMemSupported='yes'/>
<machine type='kvm' name='ast2500-evb' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='smdkc210' maxCpus='2' numaMemSupported='yes'/>
<machine type='kvm' name='collie' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='xlnx-versal-virt' maxCpus='2' numaMemSupported='yes'/>
<machine type='kvm' name='imx25-pdk' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='spitz' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='musca-b1' maxCpus='2' numaMemSupported='yes'/>
<machine type='kvm' name='realview-pbx-a9' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='realview-eb' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='realview-pb-a8' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='versatilepb' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='emcraft-sf2' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='virt-2.9' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='musicpal' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='z2' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='akita' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='virt-2.7' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='kzm' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='virt-2.8' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='realview-eb-mpcore' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='musca-a' maxCpus='2' numaMemSupported='yes'/>
<machine type='kvm' name='mcimx7d-sabre' maxCpus='2' numaMemSupported='yes'/>
<machine type='kvm' name='sx1' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='sx1-v1' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='virt-2.6' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='cubieboard' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='virt-4.0' alias='virt' maxCpus='512' numaMemSupported='yes'/>
<machine type='kvm' name='highbank' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='raspi2' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='raspi3' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='netduino2' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='terrier' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='n810' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='mainstone' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='palmetto-bmc' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='sabrelite' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='midway' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='romulus-bmc' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='cheetah' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='tosa' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='borzoi' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='versatileab' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='lm3s6965evb' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='n800' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='virt-2.10' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='virt-2.11' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='connex' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='virt-2.12' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='microbit' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='witherspoon-bmc' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='xilinx-zynq-a9' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='mps2-an385' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='vexpress-a9' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='mps2-an521' maxCpus='2' numaMemSupported='yes'/>
<machine type='kvm' name='mcimx6ul-evk' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='vexpress-a15' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='xlnx-zcu102' maxCpus='6' numaMemSupported='yes'/>
<machine type='kvm' name='virt-3.1' maxCpus='512' numaMemSupported='yes'/>
<machine type='kvm' name='canon-a1100' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='lm3s811evb' maxCpus='1' numaMemSupported='yes'/>
qemu: Move machine type data in capabilities cache In preparation for making machine types dependent on the accelerator, the <machine> elements are formatted between <cpu type='kvm'> and <cpu type='tcg'>. Signed-off-by: Jiri Denemark <jdenemar@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2019-10-24 07:04:58 +00:00
<cpu type='tcg' name='pxa262' typename='pxa262-arm-cpu'/>
<cpu type='tcg' name='pxa270-a0' typename='pxa270-a0-arm-cpu'/>
<cpu type='tcg' name='arm1136' typename='arm1136-arm-cpu'/>
<cpu type='tcg' name='cortex-a15' typename='cortex-a15-arm-cpu'/>
<cpu type='tcg' name='pxa260' typename='pxa260-arm-cpu'/>
<cpu type='tcg' name='arm1136-r2' typename='arm1136-r2-arm-cpu'/>
<cpu type='tcg' name='pxa261' typename='pxa261-arm-cpu'/>
<cpu type='tcg' name='pxa255' typename='pxa255-arm-cpu'/>
<cpu type='tcg' name='cortex-a72' typename='cortex-a72-arm-cpu'/>
<cpu type='tcg' name='cortex-m33' typename='cortex-m33-arm-cpu'/>
<cpu type='tcg' name='arm926' typename='arm926-arm-cpu'/>
<cpu type='tcg' name='cortex-r5f' typename='cortex-r5f-arm-cpu'/>
<cpu type='tcg' name='arm11mpcore' typename='arm11mpcore-arm-cpu'/>
<cpu type='tcg' name='pxa250' typename='pxa250-arm-cpu'/>
<cpu type='tcg' name='ti925t' typename='ti925t-arm-cpu'/>
<cpu type='tcg' name='cortex-a57' typename='cortex-a57-arm-cpu'/>
<cpu type='tcg' name='sa1110' typename='sa1110-arm-cpu'/>
<cpu type='tcg' name='host' typename='host-arm-cpu'/>
<cpu type='tcg' name='arm1176' typename='arm1176-arm-cpu'/>
<cpu type='tcg' name='cortex-a53' typename='cortex-a53-arm-cpu'/>
<cpu type='tcg' name='sa1100' typename='sa1100-arm-cpu'/>
<cpu type='tcg' name='pxa270-c5' typename='pxa270-c5-arm-cpu'/>
<cpu type='tcg' name='cortex-a9' typename='cortex-a9-arm-cpu'/>
<cpu type='tcg' name='cortex-a8' typename='cortex-a8-arm-cpu'/>
<cpu type='tcg' name='cortex-a7' typename='cortex-a7-arm-cpu'/>
<cpu type='tcg' name='pxa270-c0' typename='pxa270-c0-arm-cpu'/>
<cpu type='tcg' name='arm1026' typename='arm1026-arm-cpu'/>
<cpu type='tcg' name='pxa270-b1' typename='pxa270-b1-arm-cpu'/>
<cpu type='tcg' name='cortex-m3' typename='cortex-m3-arm-cpu'/>
<cpu type='tcg' name='max' typename='max-arm-cpu'/>
<cpu type='tcg' name='cortex-m4' typename='cortex-m4-arm-cpu'/>
<cpu type='tcg' name='pxa270-b0' typename='pxa270-b0-arm-cpu'/>
<cpu type='tcg' name='arm946' typename='arm946-arm-cpu'/>
<cpu type='tcg' name='cortex-m0' typename='cortex-m0-arm-cpu'/>
<cpu type='tcg' name='cortex-r5' typename='cortex-r5-arm-cpu'/>
<cpu type='tcg' name='pxa270-a1' typename='pxa270-a1-arm-cpu'/>
<cpu type='tcg' name='pxa270' typename='pxa270-arm-cpu'/>
qemu: Track numa-mem-supported machine attribute There is 'numa-mem-supported' machine attribute which specifies whether '-numa mem=' is supported. Store it in our capabilities as it will be used in later commits when building the command line. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2020-05-14 11:11:01 +00:00
<machine type='tcg' name='integratorcp' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='nuri' maxCpus='2' numaMemSupported='yes'/>
<machine type='tcg' name='mps2-an511' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='verdex' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='mps2-an505' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='virt-3.0' maxCpus='512' numaMemSupported='yes'/>
<machine type='tcg' name='ast2500-evb' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='smdkc210' maxCpus='2' numaMemSupported='yes'/>
<machine type='tcg' name='collie' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='xlnx-versal-virt' maxCpus='2' numaMemSupported='yes'/>
<machine type='tcg' name='imx25-pdk' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='spitz' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='musca-b1' maxCpus='2' numaMemSupported='yes'/>
<machine type='tcg' name='realview-pbx-a9' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='realview-eb' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='realview-pb-a8' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='versatilepb' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='emcraft-sf2' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='virt-2.9' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='musicpal' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='z2' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='akita' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='virt-2.7' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='kzm' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='virt-2.8' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='realview-eb-mpcore' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='musca-a' maxCpus='2' numaMemSupported='yes'/>
<machine type='tcg' name='mcimx7d-sabre' maxCpus='2' numaMemSupported='yes'/>
<machine type='tcg' name='sx1' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='sx1-v1' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='virt-2.6' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='cubieboard' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='virt-4.0' alias='virt' maxCpus='512' numaMemSupported='yes'/>
<machine type='tcg' name='highbank' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='raspi2' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='raspi3' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='netduino2' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='terrier' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='n810' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='mainstone' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='palmetto-bmc' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='sabrelite' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='midway' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='romulus-bmc' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='cheetah' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='tosa' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='borzoi' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='versatileab' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='lm3s6965evb' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='n800' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='virt-2.10' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='virt-2.11' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='connex' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='virt-2.12' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='microbit' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='witherspoon-bmc' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='xilinx-zynq-a9' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='mps2-an385' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='vexpress-a9' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='mps2-an521' maxCpus='2' numaMemSupported='yes'/>
<machine type='tcg' name='mcimx6ul-evk' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='vexpress-a15' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='xlnx-zcu102' maxCpus='6' numaMemSupported='yes'/>
<machine type='tcg' name='virt-3.1' maxCpus='512' numaMemSupported='yes'/>
<machine type='tcg' name='canon-a1100' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='lm3s811evb' maxCpus='1' numaMemSupported='yes'/>
tests: Add capabilities for QEMU 4.0.0 on aarch64 Signed-off-by: Andrea Bolognani <abologna@redhat.com> Acked-by: Peter Krempa <pkrempa@redhat.com>
2019-04-29 12:06:02 +00:00
<gic version='3' kernel='yes' emulated='yes'/>
<gic version='2' kernel='no' emulated='yes'/>
</qemuCaps>
Reference in New Issue Copy Permalink