shaba/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-26 03:21:44 +03:00
Code Releases Activity
d2d737551a
libvirt/tests/qemucapabilitiesdata/caps_2.5.0.x86_64.xml

273 lines
11 KiB
XML
Raw Normal View History

qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03: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 13:23:14 +03:00
<emulator>/usr/bin/qemu-system-x86_64</emulator>
qemucapabilitiestest: Test all capabilities Enhance the test to cover all capabilities we probe for rather than testing the flags only. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:02:38 +03:00
<qemuctime>0</qemuctime>
<selfctime>0</selfctime>
<selfvers>0</selfvers>
tests: Update capabilities for QEMU 2.5.0 Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-11-18 12:13:43 +03:00
<flag name='kvm'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
<flag name='no-hpet'/>
<flag name='spice'/>
<flag name='hda-duplex'/>
qemucapstest: update caps for qemu-2.5.0 Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2016-05-23 00:24:07 +03:00
<flag name='ccid-emulated'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
<flag name='ccid-passthru'/>
<flag name='virtio-tx-alg'/>
<flag name='virtio-blk-pci.ioeventfd'/>
<flag name='sga'/>
<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-redir'/>
<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='disable-s3'/>
<flag name='disable-s4'/>
<flag name='usb-redir.filter'/>
<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 15:46:54 +03:00
<flag name='seccomp-sandbox'/>
qemucapabilitiestest: Reorder flags in caps files The flags should follow the order in which they are defined in virQEMUCaps enum. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:27:40 +03:00
<flag name='reboot-timeout'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
<flag name='vnc'/>
<flag name='qxl'/>
<flag name='VGA'/>
<flag name='cirrus-vga'/>
<flag name='vmware-svga'/>
<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='tpm-passthrough'/>
<flag name='tpm-tis'/>
<flag name='pci-bridge'/>
<flag name='vfio-pci'/>
<flag name='mem-merge'/>
<flag name='drive-discard'/>
<flag name='dmi-to-pci-bridge'/>
<flag name='i440fx-pci-hole64-size'/>
<flag name='q35-pci-hole64-size'/>
<flag name='usb-storage'/>
<flag name='usb-storage.removable'/>
<flag name='virtio-mmio'/>
<flag name='ich9-intel-hda'/>
<flag name='kvm-pit-lost-tick-policy'/>
<flag name='boot-strict'/>
<flag name='pvpanic'/>
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 19:48:59 +03:00
<flag name='enable-fips'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
<flag name='spice-file-xfer-disable'/>
<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'/>
qemucapabilitiestest: Reorder flags in caps files The flags should follow the order in which they are defined in virQEMUCaps enum. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:27:40 +03:00
<flag name='memory-backend-file'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
<flag name='usb-audio'/>
<flag name='rtc-reset-reinjection'/>
<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='vmware-svga.vgamem_mb'/>
<flag name='qxl.vgamem_mb'/>
<flag name='pc-dimm'/>
<flag name='machine-vmport-opt'/>
qemucapstest: update caps for qemu-2.5.0 Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2016-05-23 00:24:07 +03:00
<flag name='aes-key-wrap'/>
<flag name='dea-key-wrap'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
<flag name='pci-serial'/>
<flag name='vhost-user-multiqueue'/>
<flag name='migration-event'/>
qemucapabilitiestest: Reorder flags in caps files The flags should follow the order in which they are defined in virQEMUCaps enum. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:27:40 +03:00
<flag name='ioh3420'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
<flag name='x3130-upstream'/>
<flag name='xio3130-downstream'/>
<flag name='rtl8139'/>
<flag name='e1000'/>
<flag name='virtio-net'/>
qemucapstest: update caps for qemu-2.5.0 Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2016-05-23 00:24:07 +03:00
<flag name='gic-version'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
<flag name='incoming-defer'/>
<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='ich9-disable-s3'/>
<flag name='ich9-disable-s4'/>
<flag name='vserport-change-event'/>
<flag name='virtio-balloon-pci.deflate-on-oom'/>
<flag name='qxl.vram64_size_mb'/>
<flag name='debug-threads'/>
<flag name='pxb'/>
<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-23 01:39:09 +03:00
<flag name='name-guest'/>
qemu: Check for qxl's max_outputs parameter Add capabilities for both qxl and qxl-vga devices. Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2015-12-11 16:26:24 +03:00
<flag name='qxl.max_outputs'/>
qemu_capabilites: add QEMU_CAPS_SPICE_UNIX Add a new capability to detect support of unix sockets for spice graphics. Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2016-06-08 01:21:29 +03:00
<flag name='spice-unix'/>
qemu: Add support for zero-detection writes Signed-off-by: Martin Kletzander <mkletzan@redhat.com>
2015-12-14 11:35:20 +03: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 18:28:20 +03: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 15:09:20 +03: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 17:05:27 +03:00
<flag name='virtio-pci-disable-legacy'/>
qemu: fix command line building for iommu devices The intel-iommu device has existed since QEMU 2.2.0, but it was only possible to create it with -device since QEMU 2.7.0, thanks to: commit 621d983a1f9051f4cfc3f402569b46b77d8449fc Author: Marcel Apfelbaum <marcel@redhat.com> Date: Mon Jun 27 18:38:34 2016 +0300 hw/iommu: enable iommu with -device Use the standard '-device intel-iommu' to create the IOMMU device. The legacy '-machine,iommu=on' can still be used. The libvirt capability check & command line formatting code is thus broken for all QEMU versions 2.2.0 -> 2.6.0 inclusive. This fixes it to use iommu=on instead. Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
2016-10-03 15:31:12 +03:00
<flag name='machine-iommu'/>
qemu_capabilities: check for existence of virtio-vga Commit 21373feb added support for primary virtio-vga device but it was checking for virtio-gpu. Let's check for existence of virtio-vga if we want to use it. Virtio video device is currently represented by three different models *virtio-gpu-device*, *virtio-gpu-pci* and *virtio-vga*. The first two models are tied together and if virtio video devices is compiled in they both exist. However, the *virtio-vga* model doesn't have to exist on some architectures even if the first two models exist. So we cannot group all three together. Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2016-10-11 15:07:58 +03:00
<flag name='virtio-vga'/>
qemu: capabilities: Add support for QMP schema introspection Allow detecting capabilities according to the qemu QMP schema. This is necessary as sometimes the availability of certain options depends on the presence of a field in the schema. This patch adds support for loading the QMP schema when detecting qemu capabilities and adds a very simple query language to allow traversing the schema and selecting a certain element from it. The infrastructure in this patch uses a query path to set a specific capability flag according to the availability of the given element in the schema.
2016-10-19 15:40:53 +03: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 06:58:15 +03: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 14:19:50 +03: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 11:19:02 +03: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 18:52:22 +03:00
<flag name='block-write-threshold'/>
qemu: capabilities: add capability for query-named-block-nodes qmp cmd
2017-03-15 19:21:48 +03: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 10:26:49 +03:00
<flag name='kernel-irqchip'/>
qemu: capabilities: introduce QEMU_CAPS_VNC_MULTI_SERVERS Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2017-07-21 19:44:14 +03:00
<flag name='vnc-multi-servers'/>
qemu: introduce QEMU_CAPS_CHARDEV_RECONNECT Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2017-08-09 16:06:40 +03: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 15:06:17 +03: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 19:19:46 +03:00
<flag name='isa-serial'/>
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 13:53:58 +03: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 14:12:33 +03:00
<flag name='hda-output'/>
qemu: Add capability flag for setting the extended tseg size For getting the reply I queried the newest and oldest QEMU using test/qemucapsprobe. From the differences I only extracted the reply to the new QMP command and discarded the rest. For all the versions below the one which added support for the new option I used the output from the oldest QEMU release and for those that support it I used the output from the newest one. In order to make doubly sure the reply is where it is supposed to be (the replies files are very forgiving) I added the property to all the replies files, reran the tests again and fixed the order in replies files so that all the versions are reporting the new capability. Then removed that one property. After that I used test/qemucapsfixreplies to fix the reply IDs. Signed-off-by: Martin Kletzander <mkletzan@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>
2018-05-11 00:27:57 +03:00
<flag name='mch'/>
qemu: Refuse to use "ps2" on machines that do not have this bus The "ps2" bus is only available on certain machines like x86. On machines like s390x, we should refuse to add a device to this bus instead of silently ignoring it. Looking at the QEMU sources, PS/2 is only available if the QEMU binary has the "i8042" device, so let's check for that and only allow "ps2" devices if this QEMU device is available, or if we're on x86 anyway (so we don't have to fake the QEMU_CAPS_DEVICE_I8042 capability in all the tests that use <input ... bus='ps2'/> in their xml data). Reported-by: Sebastian Mitterle <smitterl@redhat.com> Buglink: https://bugzilla.redhat.com/show_bug.cgi?id=1763191 Signed-off-by: Thomas Huth <thuth@redhat.com> Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
2020-01-15 15:23:56 +03:00
<flag name='i8042'/>
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 12:04:14 +03: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 04:55:45 +03: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 17:57:56 +03: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 19:37:54 +03:00
<flag name='dc390'/>
<flag name='am53c974'/>
qemucapstest: update caps for qemu-2.5.0 Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
2016-05-23 00:24:07 +03:00
<version>2005000</version>
qemucapabilitiestest: Test all capabilities Enhance the test to cover all capabilities we probe for rather than testing the flags only. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:02:38 +03: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 17:08:10 +03:00
<microcodeVersion>43100243</microcodeVersion>
qemucapabilitiestest: Test all capabilities Enhance the test to cover all capabilities we probe for rather than testing the flags only. Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:02:38 +03:00
<package></package>
<arch>x86_64</arch>
tests: Update capabilities for QEMU 2.5.0 Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-11-18 12:13:43 +03:00
<cpu type='kvm' name='Opteron_G5'/>
<cpu type='kvm' name='Opteron_G4'/>
<cpu type='kvm' name='Opteron_G3'/>
<cpu type='kvm' name='Opteron_G2'/>
<cpu type='kvm' name='Opteron_G1'/>
<cpu type='kvm' name='Broadwell'/>
<cpu type='kvm' name='Broadwell-noTSX'/>
<cpu type='kvm' name='Haswell'/>
<cpu type='kvm' name='Haswell-noTSX'/>
<cpu type='kvm' name='IvyBridge'/>
<cpu type='kvm' name='SandyBridge'/>
<cpu type='kvm' name='Westmere'/>
<cpu type='kvm' name='Nehalem'/>
<cpu type='kvm' name='Penryn'/>
<cpu type='kvm' name='Conroe'/>
<cpu type='kvm' name='n270'/>
<cpu type='kvm' name='athlon'/>
<cpu type='kvm' name='pentium3'/>
<cpu type='kvm' name='pentium2'/>
<cpu type='kvm' name='pentium'/>
<cpu type='kvm' name='486'/>
<cpu type='kvm' name='coreduo'/>
<cpu type='kvm' name='kvm32'/>
<cpu type='kvm' name='qemu32'/>
<cpu type='kvm' name='kvm64'/>
<cpu type='kvm' name='core2duo'/>
<cpu type='kvm' name='phenom'/>
<cpu type='kvm' name='qemu64'/>
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 14:11:01 +03:00
<machine type='kvm' name='pc-i440fx-2.5' alias='pc' maxCpus='255' default='yes' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-2.4' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-1.3' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-0.12' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-1.6' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-1.5' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-1.6' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-2.2' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-1.7' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-2.1' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-0.11' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-0.10' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-1.2' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-2.2' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='isapc' maxCpus='1' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-2.3' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-1.4' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-2.5' alias='q35' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-0.15' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-1.5' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-2.0' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-1.4' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-0.14' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-1.1' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-2.1' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-1.7' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-1.0' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-i440fx-2.0' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-2.4' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-q35-2.3' maxCpus='255' numaMemSupported='yes'/>
<machine type='kvm' name='pc-0.13' maxCpus='255' 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 10:04:58 +03:00
<cpu type='tcg' name='Opteron_G5'/>
<cpu type='tcg' name='Opteron_G4'/>
<cpu type='tcg' name='Opteron_G3'/>
<cpu type='tcg' name='Opteron_G2'/>
<cpu type='tcg' name='Opteron_G1'/>
<cpu type='tcg' name='Broadwell'/>
<cpu type='tcg' name='Broadwell-noTSX'/>
<cpu type='tcg' name='Haswell'/>
<cpu type='tcg' name='Haswell-noTSX'/>
<cpu type='tcg' name='IvyBridge'/>
<cpu type='tcg' name='SandyBridge'/>
<cpu type='tcg' name='Westmere'/>
<cpu type='tcg' name='Nehalem'/>
<cpu type='tcg' name='Penryn'/>
<cpu type='tcg' name='Conroe'/>
<cpu type='tcg' name='n270'/>
<cpu type='tcg' name='athlon'/>
<cpu type='tcg' name='pentium3'/>
<cpu type='tcg' name='pentium2'/>
<cpu type='tcg' name='pentium'/>
<cpu type='tcg' name='486'/>
<cpu type='tcg' name='coreduo'/>
<cpu type='tcg' name='kvm32'/>
<cpu type='tcg' name='qemu32'/>
<cpu type='tcg' name='kvm64'/>
<cpu type='tcg' name='core2duo'/>
<cpu type='tcg' name='phenom'/>
<cpu type='tcg' name='qemu64'/>
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 14:11:01 +03:00
<machine type='tcg' name='pc-i440fx-2.5' alias='pc' maxCpus='255' default='yes' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-2.4' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-1.3' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-0.12' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-1.6' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-1.5' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-1.6' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-2.2' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-1.7' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-2.1' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-0.11' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-0.10' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-1.2' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-2.2' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='isapc' maxCpus='1' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-2.3' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-1.4' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-2.5' alias='q35' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-0.15' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-1.5' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-2.0' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-1.4' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-0.14' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-1.1' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-2.1' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-1.7' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-1.0' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-i440fx-2.0' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-2.4' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-q35-2.3' maxCpus='255' numaMemSupported='yes'/>
<machine type='tcg' name='pc-0.13' maxCpus='255' numaMemSupported='yes'/>
qemucapabilitiestest: Reindent *.caps files Signed-off-by: Jiri Denemark <jdenemar@redhat.com>
2016-04-28 18:10:19 +03:00
</qemuCaps>
Copy Permalink