External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-26 23:55:23 +00:00
Code Issues Packages Projects Releases Wiki Activity
2642cc0f66
libvirt/tests/qemucapabilitiesdata/caps_2.6.0.aarch64.xml

283 lines
12 KiB
XML
Raw Normal View History

qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +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>
qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +00:00
<qemuctime>0</qemuctime>
<selfctime>0</selfctime>
<selfvers>0</selfvers>
tests: Update capabilities for QEMU 2.6.0 (aarch64, GICv2) Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-11-20 22:20:09 +00:00
<flag name='kvm'/>
qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +00:00
<flag name='hda-duplex'/>
<flag name='ccid-emulated'/>
<flag name='ccid-passthru'/>
<flag name='virtio-tx-alg'/>
<flag name='virtio-blk-pci.ioeventfd'/>
<flag name='virtio-blk-pci.event_idx'/>
<flag name='virtio-net-pci.event_idx'/>
<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'/>
qemu: Advertise ACPI support for aarch64 guests So far, libvirt has assumed that only x86 supports ACPI, but that's inaccurate since aarch64 supports it too. Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1429509
2017-03-02 17:57:51 +00:00
<flag name='no-acpi'/>
qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +00:00
<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'/>
Reintroduce QEMU_CAPS_SECCOMP_SANDBOX Commit 766d5c1b deprecated the capability, because we were assuming it for every QEMU binary. At the time of the introduction, there was no way to probe for this via QMP. However since QEMU 1.5.0 (which is the earliest version we support) we can rely on the query-command-line-options command to detect this feature. Signed-off-by: Ján Tomko <jtomko@redhat.com> Reviewed-by: John Ferlan <jferlan@redhat.com>
2018-05-18 12:46:54 +00:00
<flag name='seccomp-sandbox'/>
qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +00:00
<flag name='reboot-timeout'/>
<flag name='vnc'/>
<flag name='VGA'/>
<flag name='device-video-primary'/>
<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='mem-merge'/>
<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'/>
<flag name='boot-strict'/>
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'/>
qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +00:00
<flag name='usb-kbd'/>
<flag name='msg-timestamp'/>
<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='splash-timeout'/>
<flag name='iothread'/>
<flag name='migrate-rdma'/>
<flag name='ivshmem'/>
<flag name='drive-iotune-max'/>
<flag name='VGA.vgamem_mb'/>
<flag name='machine-vmport-opt'/>
<flag name='aes-key-wrap'/>
<flag name='dea-key-wrap'/>
<flag name='pci-serial'/>
<flag name='aarch64-off'/>
<flag name='vhost-user-multiqueue'/>
<flag name='migration-event'/>
<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='incoming-defer'/>
<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='debug-threads'/>
<flag name='secret'/>
<flag name='pxb'/>
<flag name='pxb-pcie'/>
<flag name='nec-usb-xhci-ports'/>
<flag name='virtio-scsi-pci.iothread'/>
qemu: command: Use -name guest= if available -name guest= is the explicit parameter for passing a VM name. Using it is required to allow a VM with an '=' in the name https://bugzilla.redhat.com/show_bug.cgi?id=1276485
2016-04-22 22:39:09 +00:00
<flag name='name-guest'/>
qemu: Add support for zero-detection writes Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2015-12-14 08:35:20 +00:00
<flag name='drive-detect-zeroes'/>
caps: Add capability for tls-x509-creds Add the capability flag and checks for the qemu object 'tls-creds-x509' Signed-off-by: John Ferlan <jferlan@redhat.com>
2016-06-07 15:28:20 +00:00
<flag name='tls-creds-x509'/>
Introduce SMM feature Since its release of 2.4.0 qemu is able to enable System Management Module in the firmware, or disable it. We should expose this capability in the XML. Unfortunately, there's no good way to determine whether the binary we are talking to supports it. I mean, if qemu's run with real machine type, the smm attribute can be seen in 'qom-list /machine' output. But it's not there when qemu's run with -M none. Therefore we're stuck with version based check. Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
2016-07-13 12:09:20 +00:00
<flag name='smm'/>
Introduce QEMU_CAPS_VIRTIO_PCI_DISABLE_LEGACY Check whether the disable-legacy property is present on the following devices: virtio-balloon-pci virtio-blk-pci virtio-scsi-pci virtio-serial-pci virtio-9p-pci virtio-net-pci virtio-rng-pci virtio-gpu-pci virtio-input-host-pci virtio-keyboard-pci virtio-mouse-pci virtio-tablet-pci Assuming that if QEMU knows other virtio devices where this property is applicable, it will have at least one of these devices. Added in QEMU by: commit e266d421490e0ae83044bbebb209b2d3650c0ba6 virtio-pci: add flags to enable/disable legacy/modern
2016-08-08 14:05:27 +00:00
<flag name='virtio-pci-disable-legacy'/>
caps: Add new capability for the bps/iops throttling length Add the capability to detect if the qemu binary can support the feature to use bps-max-length and friends.
2016-09-19 10:47:19 +00:00
<flag name='drive-iotune-max-length'/>
qemu: Add capabilities for ivshmem-{plain,doorbell} Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2016-08-02 06:48:45 +00:00
<flag name='ivshmem-plain'/>
<flag name='ivshmem-doorbell'/>
tests: qemucaps: Add QMP introspection data for qemu 2.6.0 on aarch64 gicv2 Add QMP schema data query for aarch64. The gic capabilities are unfortunately queried after the QMP schema and thus this patch needs to undo the temporary removal of the declared support for query-qmp-schema. Signed-off-by: Peter Krempa <pkrempa@redhat.com>
2016-10-19 15:36:45 +00:00
<flag name='query-qmp-schema'/>
qemu: Introduce vhost-scsi capability Do all the stuff for the vhost-scsi capability in QEMU, so it's in place for our checks later. Signed-off-by: Eric Farman <farman@linux.vnet.ibm.com> Reviewed-by: Boris Fiuczynski <fiuczy@linux.vnet.ibm.com>
2016-11-22 03:58:15 +00:00
<flag name='vhost-scsi'/>
caps: Add new capability for the iotune group name Add the capability to detect if the qemu binary can support the feature to use throttling.group.
2016-11-07 11:19:50 +00:00
<flag name='drive-iotune-group'/>
qemu: skip QMP probing of CPU definitions when missing This unbreaks emulators that don't support this command such as qemu-system-mips*. Reference: http://bugs.debian.org/854125
2017-03-16 08:19:02 +00:00
<flag name='query-cpu-definitions'/>
qemu: monitor: Add support for BLOCK_WRITE_THRESHOLD event The event is fired when a given block backend node (identified by the node name) experiences a write beyond the bound set via block-set-write-threshold QMP command. This wires up the monitor code to extract the data and allow us receiving the events and the capability.
2017-02-22 15:52:22 +00:00
<flag name='block-write-threshold'/>
qemu: capabilities: add capability for query-named-block-nodes qmp cmd
2017-03-15 16:21:48 +00:00
<flag name='query-named-block-nodes'/>
qemu: format kernel_irqchip on the command line Add kernel_irqchip=split/on to the QEMU command line and a capability that looks for it in query-command-line-options output. For the 'split' option, use a version check since it cannot be reasonably probed. https://bugzilla.redhat.com/show_bug.cgi?id=1427005
2017-03-17 07:26:49 +00:00
<flag name='kernel-irqchip'/>
<flag name='kernel-irqchip.split'/>
qemu: capabilities: introduce QEMU_CAPS_VNC_MULTI_SERVERS Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2017-07-21 16:44:14 +00:00
<flag name='vnc-multi-servers'/>
qemu: introduce QEMU_CAPS_CHARDEV_RECONNECT Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2017-08-09 13:06:40 +00:00
<flag name='chardev-reconnect'/>
qemu: Add capabilities for virtio-vga/gpu's max_outputs= parameter Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2017-08-23 12:06:17 +00:00
<flag name='virtio-gpu.max_outputs'/>
qemu: Add QEMU_CAPS_DEVICE_ISA_SERIAL All serial devices shoule have an associated capability. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
2017-11-26 16:19:46 +00:00
<flag name='isa-serial'/>
qemu: Add QEMU_CAPS_DEVICE_PL011 All serial devices shoule have an associated capability. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
2017-11-28 10:23:26 +00:00
<flag name='pl011'/>
qemu: Add dump completed event to the capabilities Add the DUMP_COMPLETED check to the capabilities. This is the mechanism used to determine whether the dump-guest-memory command can support the "-detach" option and thus be able to wait on the event and allow for a query of the progress of the dump. Reviewed-by: Jiri Denemark <jdenemar@redhat.com>
2017-11-17 13:46:27 +00:00
<flag name='dump-completed'/>
qemu: caps: Add capability for TLS transport in the NBD server The NBD server in qemu supports TLS transport. Detect this capability. Signed-off-by: Peter Krempa <pkrempa@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2018-04-26 11:11:05 +00:00
<flag name='nbd-tls'/>
qemu: Add QEMU_CAPS_SDL_GL to qemu capabilities Support OpenGL acceleration capability when using SDL graphics. Signed-off-by: Maciej Wolny <maciej.wolny@codethink.co.uk> Reviewed-by: John Ferlan <jferlan@redhat.com>
2018-05-10 10:53:58 +00:00
<flag name='sdl-gl'/>
qemu: capabilities: Add 'hda-output' sound codec to capabilities Signed-off-by: Filip Alac <filipalac@gmail.com> Reviewed-by: Erik Skultety <eskultet@redhat.com>
2018-05-22 11:12:33 +00:00
<flag name='hda-output'/>
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: Introduce fw_cfg capability This capability tracks whether QEMU supports -fw_cfg command line option, more specifically whether it allows specifying filename. There are some releases of QEMU which support -fw_cfg but not filename. If this is ever a problem we can refine the capability later on. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
2020-06-02 14:57:56 +00:00
<flag name='fw_cfg'/>
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'/>
tests: qemucaps: Update aarch64 gicv2 replies for qemu 2.6.0 release Sync up to the released version of qemu. Signed-off-by: Peter Krempa <pkrempa@redhat.com>
2016-10-19 15:36:45 +00:00
<version>2006000</version>
qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +00:00
<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>61700244</microcodeVersion>
qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +00:00
<package></package>
<arch>aarch64</arch>
tests: Update capabilities for QEMU 2.6.0 (aarch64, GICv2) Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-11-20 22:20:09 +00:00
<cpu type='kvm' name='pxa262'/>
<cpu type='kvm' name='pxa270-a0'/>
<cpu type='kvm' name='arm1136'/>
<cpu type='kvm' name='cortex-a15'/>
<cpu type='kvm' name='pxa260'/>
<cpu type='kvm' name='arm1136-r2'/>
<cpu type='kvm' name='pxa261'/>
<cpu type='kvm' name='pxa255'/>
<cpu type='kvm' name='arm926'/>
<cpu type='kvm' name='arm11mpcore'/>
<cpu type='kvm' name='pxa250'/>
<cpu type='kvm' name='ti925t'/>
<cpu type='kvm' name='cortex-a57'/>
<cpu type='kvm' name='sa1110'/>
<cpu type='kvm' name='arm1176'/>
<cpu type='kvm' name='cortex-a53'/>
<cpu type='kvm' name='host'/>
<cpu type='kvm' name='sa1100'/>
<cpu type='kvm' name='pxa270-c5'/>
<cpu type='kvm' name='cortex-a9'/>
<cpu type='kvm' name='cortex-a8'/>
<cpu type='kvm' name='pxa270-c0'/>
<cpu type='kvm' name='arm1026'/>
<cpu type='kvm' name='pxa270-b1'/>
<cpu type='kvm' name='cortex-m3'/>
<cpu type='kvm' name='cortex-m4'/>
<cpu type='kvm' name='pxa270-b0'/>
<cpu type='kvm' name='arm946'/>
<cpu type='kvm' name='cortex-r5'/>
<cpu type='kvm' name='pxa270-a1'/>
<cpu type='kvm' name='pxa270'/>
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='verdex' 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='imx25-pdk' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='spitz' maxCpus='1' 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='versatilepb' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='realview-pb-a8' maxCpus='1' 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='kzm' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='realview-eb-mpcore' maxCpus='4' 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' alias='virt' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='cubieboard' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='highbank' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='raspi2' 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='midway' maxCpus='4' 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='connex' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='xilinx-zynq-a9' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='xlnx-ep108' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='vexpress-a9' maxCpus='4' numaMemSupported='yes'/>
<machine type='kvm' name='vexpress-a15' maxCpus='4' 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'/>
<cpu type='tcg' name='pxa270-a0'/>
<cpu type='tcg' name='arm1136'/>
<cpu type='tcg' name='cortex-a15'/>
<cpu type='tcg' name='pxa260'/>
<cpu type='tcg' name='arm1136-r2'/>
<cpu type='tcg' name='pxa261'/>
<cpu type='tcg' name='pxa255'/>
<cpu type='tcg' name='arm926'/>
<cpu type='tcg' name='arm11mpcore'/>
<cpu type='tcg' name='pxa250'/>
<cpu type='tcg' name='ti925t'/>
<cpu type='tcg' name='cortex-a57'/>
<cpu type='tcg' name='sa1110'/>
<cpu type='tcg' name='arm1176'/>
<cpu type='tcg' name='cortex-a53'/>
<cpu type='tcg' name='sa1100'/>
<cpu type='tcg' name='pxa270-c5'/>
<cpu type='tcg' name='cortex-a9'/>
<cpu type='tcg' name='cortex-a8'/>
<cpu type='tcg' name='pxa270-c0'/>
<cpu type='tcg' name='arm1026'/>
<cpu type='tcg' name='pxa270-b1'/>
<cpu type='tcg' name='cortex-m3'/>
<cpu type='tcg' name='cortex-m4'/>
<cpu type='tcg' name='pxa270-b0'/>
<cpu type='tcg' name='arm946'/>
<cpu type='tcg' name='cortex-r5'/>
<cpu type='tcg' name='pxa270-a1'/>
<cpu type='tcg' name='pxa270'/>
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='verdex' 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='imx25-pdk' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='spitz' maxCpus='1' 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='versatilepb' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='realview-pb-a8' maxCpus='1' 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='kzm' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='realview-eb-mpcore' maxCpus='4' 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' alias='virt' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='cubieboard' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='highbank' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='raspi2' 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='midway' maxCpus='4' 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='connex' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='xilinx-zynq-a9' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='xlnx-ep108' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='vexpress-a9' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='vexpress-a15' maxCpus='4' numaMemSupported='yes'/>
<machine type='tcg' name='canon-a1100' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='lm3s811evb' maxCpus='1' numaMemSupported='yes'/>
qemucapabilitiestest: Add tests for aarch64 and ppc64le Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-27 14:48:56 +00:00
<gic version='3' kernel='no' emulated='no'/>
<gic version='2' kernel='yes' emulated='yes'/>
</qemuCaps>
Reference in New Issue Copy Permalink