Lines Matching +full:suspend +full:- +full:to +full:- +full:ram
1 # -*- Mode: Python -*-
5 # See the COPYING file in the top-level directory.
14 { 'include': 'machine-common.json' }
20 # targets. Run "./configure --help" in the project root directory,
21 # and look for the \*-softmmu targets near the "--target-list" option.
31 # .. note:: The resulting QMP strings can be appended to the
32 # "qemu-system-" prefix to produce the corresponding QEMU
33 # executable name. This is true even for "qemu-system-x86_64".
54 'data': [ 'uninitialized', 'stopped', 'check-stop', 'operating', 'load' ] }
61 # @cpu-state: the virtual CPU's state
70 'data': { 'cpu-state': 'S390CpuState',
79 # @cpu-index: index of the virtual CPU
81 # @qom-type: QOM type name of the CPU (since 10.1)
83 # @qom-path: path to the CPU object in the QOM tree
85 # @thread-id: ID of the underlying host thread
95 'base' : { 'cpu-index' : 'int',
96 'qom-type' : 'str',
97 'qom-path' : 'str',
98 'thread-id' : 'int',
105 # @query-cpus-fast:
111 # .. qmp-example::
113 # -> { "execute": "query-cpus-fast" }
114 # <- { "return": [
116 # "thread-id": 25627,
118 # "core-id": 0,
119 # "thread-id": 0,
120 # "socket-id": 0
122 # "qom-path": "/machine/unattached/device[0]",
124 # "cpu-index": 0
127 # "thread-id": 25628,
129 # "core-id": 0,
130 # "thread-id": 0,
131 # "socket-id": 1
133 # "qom-path": "/machine/unattached/device[2]",
135 # "cpu-index": 1
140 { 'command': 'query-cpus-fast', 'returns': [ 'CpuInfoFast' ] }
145 # Property default values specific to a machine type, for use by
146 # scripts/compare-machine-types.
148 # @qom-type: name of the QOM type to which the default applies
150 # @property: name of its property to which the default applies
152 # @value: the default value (machine-specific default can overwrite
153 # the "default" default, to avoid this use -machine none)
158 'data': { 'qom-type': 'str',
171 # @is-default: whether the machine is default
173 # @cpu-max: maximum number of CPUs supported by the machine type
176 # @hotpluggable-cpus: cpu hotplug via -device is supported (since 2.7)
178 # @numa-mem-supported: true if '-numa node,mem' option is supported by
182 # removed in future versions of QEMU according to the QEMU
185 # @default-cpu-type: default CPU model typename if none is requested
186 # via the -cpu argument. (since 4.2)
188 # @default-ram-id: the default ID of initial RAM memory backend
193 # @compat-props: The machine type's compatibility properties. Only
194 # present when `query-machines` argument @compat-props is true.
199 # @unstable: Member @compat-props is experimental.
205 '*is-default': 'bool', 'cpu-max': 'int',
206 'hotpluggable-cpus': 'bool', 'numa-mem-supported': 'bool',
207 'deprecated': 'bool', '*default-cpu-type': 'str',
208 '*default-ram-id': 'str', 'acpi': 'bool',
209 '*compat-props': { 'type': ['CompatProperty'],
213 # @query-machines:
217 # @compat-props: if true, also return compatibility properties.
222 # @unstable: Argument @compat-props is experimental.
226 # .. qmp-example::
228 # -> { "execute": "query-machines", "arguments": { "compat-props": true } }
229 # <- { "return": [
231 # "hotpluggable-cpus": true,
232 # "name": "pc-q35-6.2",
233 # "compat-props": [
235 # "qom-type": "virtio-mem",
236 # "property": "unplugged-inaccessible",
240 # "numa-mem-supported": false,
241 # "default-cpu-type": "qemu64-x86_64-cpu",
242 # "cpu-max": 288,
244 # "default-ram-id": "pc.ram"
249 { 'command': 'query-machines',
250 'data': { '*compat-props': { 'type': 'bool',
259 # @wakeup-suspend-support: true if the machine supports wake up from
260 # suspend
265 'data': { 'wakeup-suspend-support': 'bool'} }
268 # @query-current-machine:
274 { 'command': 'query-current-machine', 'returns': 'CurrentMachineParams' }
289 # @query-target:
295 { 'command': 'query-target', 'returns': 'QemuTargetInfo' }
312 # @query-uuid:
318 # .. qmp-example::
320 # -> { "execute": "query-uuid" }
321 # <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
323 { 'command': 'query-uuid', 'returns': 'UuidInfo', 'allow-preconfig': true }
337 # @query-vm-generation-id:
343 { 'command': 'query-vm-generation-id', 'returns': 'GuidInfo' }
352 # .. qmp-example::
354 # -> { "execute": "system_reset" }
355 # <- { "return": {} }
366 # .. note:: A guest may or may not respond to this command. This
368 # request or that it has shut down. Many guests will respond to
371 # .. qmp-example::
373 # -> { "execute": "system_powerdown" }
374 # <- { "return": {} }
381 # Wake up guest from suspend. If the guest has wake-up from suspend
382 # support enabled (wakeup-suspend-support flag from
383 # `query-current-machine`), wake-up guest from suspend if the guest is
388 # .. note:: Prior to 4.0, this command does nothing in case the guest
391 # .. qmp-example::
393 # -> { "execute": "system_wakeup" }
394 # <- { "return": {} }
407 # intervening chunk of time had simply not existed; needless to
409 # not specifically prepared to deal with it. Assuming the guest
413 # @delay: continue to deliver ticks at the normal rate. The guest OS
415 # time will have continued to flow normally. The time in the
419 # @slew: deliver ticks at a higher rate to catch up with the missed
421 # its point of view time will have continued to flow normally.
422 # Once the timer has managed to catch up with all the missing
431 # @inject-nmi:
433 # Injects a Non-Maskable Interrupt into the default CPU (x86/s390) or
439 # .. note:: Prior to 2.1, this command was only supported for x86 and
442 # .. qmp-example::
444 # -> { "execute": "inject-nmi" }
445 # <- { "return": {} }
447 { 'command': 'inject-nmi' }
456 # @cpu: property based CPU(s) to node mapping (Since: 2.10)
458 # @hmat-lb: memory latency and bandwidth information (Since: 5.0)
460 # @hmat-cache: memory side cache information (Since: 5.0)
465 'data': [ 'node', 'dist', 'cpu', 'hmat-lb', 'hmat-cache' ] }
483 'hmat-lb': 'NumaHmatLBOptions',
484 'hmat-cache': 'NumaHmatCacheOptions' }}
493 # @cpus: VCPUs belonging to this node (assign VCPUS round-robin if
503 # @initiator: defined in ACPI 6.3 Chapter 5.2.27.3 Table 5-145, points
504 # to the nodeid which has the memory controller responsible for
506 # to the initiator node that is closest (as in directly attached)
507 # to this node, and therefore has the best performance (since 5.0)
528 # @val: NUMA distance from source node to destination node. When a
530 # them to 255.
548 # @interleave-granularity: Number of contiguous bytes for which
549 # accesses will go to a given interleave target. Accepted values
552 # @targets: Target root bridge IDs from -device ...,id=<ID> for each
560 '*interleave-granularity': 'size',
568 # @cxl-fmw: List of `CXLFixedMemoryWindowOptions`
573 'data': { 'cxl-fmw': ['CXLFixedMemoryWindowOptions'] }
579 # A X86 32-bit register
591 # @cpuid-input-eax: Input EAX value for CPUID instruction for that
594 # @cpuid-input-ecx: Input ECX value for CPUID instruction for that
597 # @cpuid-register: Output register containing the feature bits
604 'data': { 'cpuid-input-eax': 'int',
605 '*cpuid-input-ecx': 'int',
606 'cpuid-register': 'X86CPURegister32',
612 # Not used by QMP; hack to let us use X86CPUFeatureWordInfoList
623 # Option "-numa cpu" overrides default cpu to node mapping. It accepts
625 # `query-hotpluggable-cpus[].props <query-hotpluggable-cpus>`, where
626 # node-id could be used to override default node mapping.
641 # 5.2.27.4: Table 5-146: Field "Flags" of ACPI 6.3 spec.
645 # @first-level: first level of memory side cache
647 # @second-level: second level of memory side cache
649 # @third-level: third level of memory side cache
654 'data': [ 'memory', 'first-level', 'second-level', 'third-level' ] }
663 # Table 5-146: Field "Data Type" of ACPI 6.3 spec.
665 # @access-latency: access latency (nanoseconds)
667 # @read-latency: read latency (nanoseconds)
669 # @write-latency: write latency (nanoseconds)
671 # @access-bandwidth: access bandwidth (Bytes per second)
673 # @read-bandwidth: read bandwidth (Bytes per second)
675 # @write-bandwidth: write bandwidth (Bytes per second)
680 'data': [ 'access-latency', 'read-latency', 'write-latency',
681 'access-bandwidth', 'read-bandwidth', 'write-bandwidth' ] }
690 # Table 5-146 of ACPI 6.3 spec.
699 # @data-type: presents the type of data, access/read/write latency or
702 # @latency: the value of latency from @initiator to @target proximity
715 'data-type': 'HmatLBDataType',
726 # 5.2.27.5: Table 5-147 of ACPI 6.3 spec.
747 # Table 5-147: Field "Cache Attributes" of ACPI 6.3 spec.
752 # @write-back: Write Back (WB)
754 # @write-through: Write Through (WT)
759 'data': [ 'none', 'write-back', 'write-through' ] }
767 # Table 5-147: Field "Cache Attributes" of ACPI 6.3 spec.
769 # @node-id: the memory proximity domain to which the memory belongs.
776 # none/direct-mapped/complex(complex cache indexing).
778 # @policy: the write policy, none/write-back/write-through.
786 'node-id': 'uint32',
796 # Save a portion of guest memory to a file.
798 # @val: the virtual address of the guest to start from
800 # @size: the size of memory region to save
802 # @filename: the file to save the memory to as binary data
804 # @cpu-index: the index of the virtual CPU to use for translating the
805 # virtual address (defaults to CPU 0)
811 # .. qmp-example::
813 # -> { "execute": "memsave",
816 # "filename": "/tmp/virtual-mem-dump" } }
817 # <- { "return": {} }
824 '*cpu-index': 'int' } }
829 # Save a portion of guest physical memory to a file.
831 # @val: the physical address of the guest to start from
833 # @size: the size of memory region to save
835 # @filename: the file to save the memory to as binary data
841 # .. qmp-example::
843 # -> { "execute": "pmemsave",
846 # "filename": "/tmp/physical-mem-dump" } }
847 # <- { "return": {} }
870 # @share: whether memory is private to QEMU or shared (since 6.1)
873 # applicable. This corresponds to the user configuration and not
874 # the actual behavior implemented in the OS to perform the
878 # @host-nodes: host nodes for its memory policy
893 'host-nodes': ['uint16'],
897 # @query-memdev:
903 # .. qmp-example::
905 # -> { "execute": "query-memdev" }
906 # <- { "return": [
914 # "host-nodes": [0, 1],
923 # "host-nodes": [2, 3],
929 { 'command': 'query-memdev', 'returns': ['Memdev'], 'allow-preconfig': true }
939 # For s390x see :ref:`cpu-topology-s390x`.
941 # The ids other than the node-id specify the position of the CPU
945 # @node-id: NUMA node ID the CPU belongs to
947 # @drawer-id: drawer number within CPU topology the CPU belongs to
950 # @book-id: book number within parent container the CPU belongs to
953 # @socket-id: socket number within parent container the CPU belongs to
955 # @die-id: die number within the parent container the CPU belongs to
958 # @cluster-id: cluster number within the parent container the CPU
959 # belongs to (since 7.1)
961 # @module-id: module number within the parent container the CPU
962 # belongs to (since 9.1)
964 # @core-id: core number within the parent container the CPU belongs to
966 # @thread-id: thread number within the core the CPU belongs to
972 'data': { '*node-id': 'int',
973 '*drawer-id': 'int',
974 '*book-id': 'int',
975 '*socket-id': 'int',
976 '*die-id': 'int',
977 '*cluster-id': 'int',
978 '*module-id': 'int',
979 '*core-id': 'int',
980 '*thread-id': 'int'
989 # @props: list of properties to pass for hotplugging a CPU with
992 # @vcpus-count: number of logical VCPU threads `HotpluggableCPU`
995 # @qom-path: link to existing CPU object if CPU is present or omitted
998 # .. note:: Management should be prepared to pass through additional
1005 'vcpus-count': 'int',
1007 '*qom-path': 'str'
1012 # @query-hotpluggable-cpus:
1018 # .. qmp-example::
1022 # ``-smp 2,cores=2,maxcpus=4 -cpu POWER8``::
1024 # -> { "execute": "query-hotpluggable-cpus" }
1025 # <- {"return": [
1026 # { "props": { "core-id": 8 }, "type": "POWER8-spapr-cpu-core",
1027 # "vcpus-count": 1 },
1028 # { "props": { "core-id": 0 }, "type": "POWER8-spapr-cpu-core",
1029 # "vcpus-count": 1, "qom-path": "/machine/unattached/device[0]"}
1032 # .. qmp-example::
1035 # For pc machine type started with ``-smp 1,maxcpus=2``::
1037 # -> { "execute": "query-hotpluggable-cpus" }
1038 # <- {"return": [
1040 # "type": "qemu64-x86_64-cpu", "vcpus-count": 1,
1041 # "props": {"core-id": 0, "socket-id": 1, "thread-id": 0}
1044 # "qom-path": "/machine/unattached/device[0]",
1045 # "type": "qemu64-x86_64-cpu", "vcpus-count": 1,
1046 # "props": {"core-id": 0, "socket-id": 0, "thread-id": 0}
1050 # .. qmp-example::
1053 # For s390x-virtio-ccw machine type started with
1054 # ``-smp 1,maxcpus=2 -cpu qemu``::
1056 # -> { "execute": "query-hotpluggable-cpus" }
1057 # <- {"return": [
1059 # "type": "qemu-s390x-cpu", "vcpus-count": 1,
1060 # "props": { "core-id": 1 }
1063 # "qom-path": "/machine/unattached/device[0]",
1064 # "type": "qemu-s390x-cpu", "vcpus-count": 1,
1065 # "props": { "core-id": 0 }
1069 { 'command': 'query-hotpluggable-cpus', 'returns': ['HotpluggableCPU'],
1070 'allow-preconfig': true }
1073 # @set-numa-node:
1075 # Runtime equivalent of '-numa' CLI option, available at preconfigure
1076 # stage to configure numa mapping before initializing machine.
1080 { 'command': 'set-numa-node', 'boxed': true,
1082 'allow-preconfig': true
1088 # Request the balloon driver to change its balloon size.
1093 # logical_vm_size = vm_ram_size - balloon_size
1095 # From it we have: balloon_size = vm_ram_size - @value
1098 # - If the balloon driver is enabled but not functional because
1100 # - If no balloon device is present, DeviceNotActive
1102 # .. note:: This command just issues a request to the guest. When it
1108 # .. qmp-example::
1113 # -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1114 # <- { "return": {} }
1116 # With a 2.5GiB guest this command inflated the ballon to 3GiB.
1126 # logical_vm_size = vm_ram_size - balloon_size
1133 # @query-balloon:
1138 # - If the balloon driver is enabled but not functional because
1140 # - If no balloon device is present, DeviceNotActive
1144 # .. qmp-example::
1146 # -> { "execute": "query-balloon" }
1147 # <- { "return": {
1152 { 'command': 'query-balloon', 'returns': 'BalloonInfo' }
1158 # is equivalent to the @actual field return by the `query-balloon`
1162 # logical_vm_size = vm_ram_size - balloon_size
1164 # .. note:: This event is rate-limited.
1168 # .. qmp-example::
1170 # <- { "event": "BALLOON_CHANGE",
1180 # hv-balloon guest-provided memory status information.
1195 # @query-hv-balloon-status-report:
1197 # Return the hv-balloon driver data contained in the last received
1201 # - If no hv-balloon device is present, guest memory status
1207 # .. qmp-example::
1209 # -> { "execute": "query-hv-balloon-status-report" }
1210 # <- { "return": {
1216 { 'command': 'query-hv-balloon-status-report', 'returns': 'HvBalloonInfo' }
1221 # Emitted when the hv-balloon driver receives a "STATUS" message from
1224 # .. note:: This event is rate-limited.
1228 # .. qmp-example::
1230 # <- { "event": "HV_BALLOON_STATUS_REPORT",
1242 # @base-memory: size of "base" memory specified with command line
1243 # option -m.
1245 # @plugged-memory: size of memory that can be hot-unplugged. This
1252 'data' : { 'base-memory': 'size', '*plugged-memory': 'size' } }
1255 # @query-memory-size-summary:
1260 # TODO: This line is a hack to separate the example from the body
1262 # .. qmp-example::
1264 # -> { "execute": "query-memory-size-summary" }
1265 # <- { "return": { "base-memory": 4294967296, "plugged-memory": 0 } }
1269 { 'command': 'query-memory-size-summary', 'returns': 'MemoryInfo' }
1339 # @requested-size: the user requested size of the device
1343 # @max-size: the maximum size of memory that the device can provide
1345 # @block-size: the block size of memory that the device provides
1347 # @node: NUMA node number where device is assigned to
1356 'requested-size': 'size',
1358 'max-size': 'size',
1359 'block-size': 'size',
1394 # hv-balloon provided memory state information
1400 # @max-size: the maximum size of memory that the device can provide
1409 'max-size': 'size',
1419 # @virtio-pmem: since 4.1
1421 # @virtio-mem: since 5.1
1423 # @sgx-epc: since 6.2.
1425 # @hv-balloon: since 8.2.
1430 'data': [ 'dimm', 'nvdimm', 'virtio-pmem', 'virtio-mem', 'sgx-epc',
1431 'hv-balloon' ] }
1476 # @data: hv-balloon provided memory state information
1497 'virtio-pmem': 'VirtioPMEMDeviceInfoWrapper',
1498 'virtio-mem': 'VirtioMEMDeviceInfoWrapper',
1499 'sgx-epc': 'SgxEPCDeviceInfoWrapper',
1500 'hv-balloon': 'HvBalloonDeviceInfoWrapper'
1526 # @sgx-epc: list of ids of memory-backend-epc objects.
1531 'data': { 'sgx-epc': ['SgxEPC'] }
1535 # @query-memory-devices:
1541 # .. qmp-example::
1543 # -> { "execute": "query-memory-devices" }
1544 # <- { "return": [ { "data":
1556 { 'command': 'query-memory-devices', 'returns': ['MemoryDeviceInfo'] }
1562 # memory devices that can actually change the size (e.g., virtio-mem
1563 # due to guest action).
1569 # @qom-path: path to the device object in the QOM tree (since 6.2)
1571 # .. note:: This event is rate-limited.
1575 # .. qmp-example::
1577 # <- { "event": "MEMORY_DEVICE_SIZE_CHANGE",
1579 # "qom-path": "/machine/unattached/device[2]" },
1583 'data': { '*id': 'str', 'size': 'size', 'qom-path' : 'str'} }
1590 # @order: Boot order (a=floppy, c=hard disk, d=CD-ROM, n=network)
1592 # @once: Boot order to apply on first boot
1594 # @menu: Whether to show a boot menu
1596 # @splash: The name of the file to be passed to the firmware as logo
1599 # @splash-time: How long to show the logo picture, in milliseconds
1601 # @reboot-timeout: Timeout before guest reboots after boot fails
1603 # @strict: Whether to attempt booting from devices not included in the
1613 '*splash-time': 'int',
1614 '*reboot-timeout': 'int',
1626 # The ordering from highest/coarsest to lowest/finest is: @drawers,
1671 # @x-query-irq:
1683 { 'command': 'x-query-irq',
1688 # @x-query-jit:
1700 { 'command': 'x-query-jit',
1706 # @x-query-numa:
1718 { 'command': 'x-query-numa',
1723 # @x-query-ramblock:
1735 { 'command': 'x-query-ramblock',
1740 # @x-query-roms:
1752 { 'command': 'x-query-roms',
1757 # @x-query-usb:
1769 { 'command': 'x-query-usb',
1776 # @32: SMBIOS version 2.1 (32-bit) Entry Point
1778 # @64: SMBIOS version 3.0 (64-bit) Entry Point
1795 # @max-size: maximum hotpluggable memory size in bytes
1803 '*max-size': 'size',
1811 # @filename: name of the dtb file to be created
1815 # .. qmp-example::
1817 # -> { "execute": "dumpdtb" }
1819 # <- { "return": {} }
1826 # @x-query-interrupt-controllers:
1838 { 'command': 'x-query-interrupt-controllers',
1843 # @dump-skeys:
1847 # @filename: the path to the file to dump to
1851 # .. qmp-example::
1853 # -> { "execute": "dump-skeys",
1855 # <- { "return": {} }
1857 { 'command': 'dump-skeys',
1865 # A CPU model consists of the name of a CPU definition, to which delta
1873 # @props: a dictionary of QOM properties to be applied
1886 # @static: Expand to a static CPU model, a combination of a static
1891 # model can be used by tooling without having to specify a
1892 # compatibility machine - e.g. when displaying the "host" model.
1893 # The @static CPU models are migration-safe.
1896 # to be migration-safe, but allows tooling to get an insight and
1899 # .. note:: When a non-migration-safe CPU model is expanded in static
1904 # enabled by a non-migration-safe CPU model, use @full. If you
1906 # even when changing QEMU version or machine-type, use @static (but
1920 # @incompatible: If model A is incompatible to model B, model A is not
1921 # guaranteed to run where model B runs and the other way around.
1923 # @identical: If model A is identical to model B, model A is
1924 # guaranteed to run where model B runs and the other way around.
1927 # guaranteed to run where model A runs. There are no guarantees
1930 # @subset: If model A is a subset of model B, model A is guaranteed to
1958 # @responsible-properties: List of properties that led to the
1961 # @responsible-properties is a list of QOM property names that led to
1963 # this list is empty. If a QOM property is read-only, that means
1964 # there's no known way to make the CPU models identical. If the
1972 'responsible-properties': ['str'] } }
1975 # @query-cpu-model-comparison:
1980 # used by tooling to make decisions if a certain CPU model will
1982 # to be created by baselining.
1993 # `query-cpu-definitions`.)
1994 # * machine-type: CPU model may look different depending on the
1995 # machine-type. (Except for CPU models reported as "static" in
1996 # `query-cpu-definitions`.)
2000 # `query-cpu-definitions`.)
2001 # * "-cpu" arguments and global properties: arguments to the -cpu
2003 # Using `query-cpu-model-expansion` while using these is not advised.
2008 # @modela: description of the first CPU model to compare, referred to
2011 # @modelb: description of the second CPU model to compare, referred to
2018 # - if comparing CPU models is not supported by the target
2019 # - if a model cannot be used
2020 # - if a model contains an unknown cpu definition name, unknown
2025 { 'command': 'query-cpu-model-comparison',
2030 # @query-cpu-model-baseline:
2034 # migration-safe CPU model (see "static" CPU model expansion for
2037 # This interface can be used by tooling to create a compatible CPU
2039 # to or a subset of both CPU models when comparing them. Therefore,
2040 # the created CPU model is guaranteed to run where the given CPU
2047 # `query-cpu-definitions`.)
2048 # * machine-type: CPU model may look different depending on the
2049 # machine-type. (Except for CPU models reported as "static" in
2050 # `query-cpu-definitions`.)
2054 # `query-cpu-definitions`.)
2055 # * "-cpu" arguments and global properties: arguments to the -cpu
2057 # Using `query-cpu-model-expansion` while using these is not advised.
2062 # @modela: description of the first CPU model to baseline
2064 # @modelb: description of the second CPU model to baseline
2069 # - if baselining CPU models is not supported by the target
2070 # - if a model cannot be used
2071 # - if a model contains an unknown cpu definition name, unknown
2076 { 'command': 'query-cpu-model-baseline',
2088 # @deprecated-props: an optional list of properties that are flagged as
2091 # enabled-properties for the expanded model; "full" properties are
2093 # the architecture. (since: 10.1 -- since 9.1 on s390x --).
2099 '*deprecated-props' : ['str'] } }
2102 # @query-cpu-model-expansion:
2105 # additional options) to different granularities, specified by @type,
2106 # allowing tooling to get an understanding what a specific CPU model
2109 # This interface can be used to query the "host" CPU model.
2115 # `query-cpu-definitions`.)
2116 # * machine-type: CPU model may look different depending on the
2117 # machine-type. (Except for CPU models reported as "static" in
2118 # `query-cpu-definitions`.)
2122 # `query-cpu-definitions`.)
2123 # * "-cpu" arguments and global properties: arguments to the -cpu
2125 # Using `query-cpu-model-expansion` while using these is not advised.
2130 # @model: description of the CPU model to expand
2132 # @type: expansion type, specifying how to expand the CPU model
2137 # - if expanding CPU models is not supported
2138 # - if the model cannot be expanded
2139 # - if the model contains an unknown CPU definition name, unknown
2141 # - if an expansion type is not supported
2145 { 'command': 'query-cpu-model-expansion',
2157 # @migration-safe: whether a CPU definition can be safely used for
2162 # assume the CPU definition to be migration-safe. (since 2.8)
2166 # accelerator options. A static model is always migration-safe.
2169 # @unavailable-features: List of properties that prevent the CPU model
2172 # @typename: Type name that can be used as argument to
2173 # `device-list-properties`, to introspect properties configurable
2174 # using -cpu or -global. (since 2.9)
2176 # @alias-of: Name of CPU model this model is an alias for. The target
2178 # Management software is supposed to translate CPU model aliases
2180 # migration-safe in the future (since 4.1)
2183 # removed in some future version of QEMU according to the QEMU
2186 # @unavailable-features is a list of QOM property names that represent
2188 # property is read-only, that means there's no known way to make the
2190 # to provide specific information return the property name "type". If
2191 # the property is read-write, it means that it MAY be possible to run
2193 # Management software can use it as hints to suggest or choose an
2194 # alternative for the user, or just to generate meaningful error
2196 # @unavailable-features is an empty list, the CPU model is runnable
2197 # using the current host and machine-type. If @unavailable-features
2205 '*migration-safe': 'bool',
2207 '*unavailable-features': [ 'str' ],
2209 '*alias-of' : 'str',
2213 # @query-cpu-definitions:
2219 { 'command': 'query-cpu-definitions', 'returns': ['CpuDefinitionInfo'] }