qemu/qapi
Daniel P. Berrangé 04109957d4 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>
2019-09-03 14:39:46 -03:00
..
audio.json
authz.json
block-core.json
block.json
char.json
common.json
crypto.json
dump.json
error.json
introspect.json
job.json
machine-target.json
machine.json qapi: report the default CPU type for each machine 2019-09-03 14:39:46 -03:00
Makefile.objs
migration.json
misc-target.json
misc.json
net.json
opts-visitor.c
qapi-clone-visitor.c
qapi-dealloc-visitor.c
qapi-schema.json
qapi-util.c
qapi-visit-core.c
qdev.json
qmp-dispatch.c
qmp-event.c
qmp-registry.c
qobject-input-visitor.c
qobject-output-visitor.c
qom.json
rdma.json
rocker.json
run-state.json
sockets.json
string-input-visitor.c
string-output-visitor.c
tpm.json
trace-events
trace.json
transaction.json
ui.json