diff options
author | Daniel P. Berrangé <berrange@redhat.com> | 2019-08-22 11:04:12 +0100 |
---|---|---|
committer | Eduardo Habkost <ehabkost@redhat.com> | 2019-09-03 14:39:46 -0300 |
commit | 04109957d47307cdedd19afc3687bd6307466b53 (patch) | |
tree | 48f966977ad79468f953ea51e54141e62ffb1e73 /qapi | |
parent | fea374e7c8079563bca7c8fac895c6a880f76adc (diff) | |
download | qemu-04109957d47307cdedd19afc3687bd6307466b53.zip qemu-04109957d47307cdedd19afc3687bd6307466b53.tar.gz qemu-04109957d47307cdedd19afc3687bd6307466b53.tar.bz2 |
qapi: report the default CPU type for each machine
When user doesn't request any explicit CPU model with libvirt or QEMU,
a machine type specific CPU model is picked. Currently there is no way
to determine what this QEMU built-in default is, so libvirt cannot
report this back to the user in the XML config.
This extends the "query-machines" QMP command so that it reports the
default CPU model typename for each machine.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20190822100412.23746-1-berrange@redhat.com>
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Diffstat (limited to 'qapi')
-rw-r--r-- | qapi/machine.json | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/qapi/machine.json b/qapi/machine.json index de5c742..ca26779 100644 --- a/qapi/machine.json +++ b/qapi/machine.json @@ -348,13 +348,16 @@ # in future versions of QEMU according to the QEMU deprecation # policy (since 4.1.0) # +# @default-cpu-type: default CPU model typename if none is requested via +# the -cpu argument. (since 4.2) +# # Since: 1.2.0 ## { 'struct': 'MachineInfo', 'data': { 'name': 'str', '*alias': 'str', '*is-default': 'bool', 'cpu-max': 'int', 'hotpluggable-cpus': 'bool', 'numa-mem-supported': 'bool', - 'deprecated': 'bool' } } + 'deprecated': 'bool', '*default-cpu-type': 'str' } } ## # @query-machines: |