1 HXCOMM QMP dispatch table and documentation
2 HXCOMM Text between SQMP and EQMP is copied to the QMP documention file and
3 HXCOMM does not show up
in the other formats
.
9 This document describes all commands currently supported by QMP
.
11 Most of the time their usage is exactly the same as
in the user Monitor
, this
12 means that any other document which also describe
commands (the manpage
,
13 QEMU
's manual, etc) can and should be consulted.
15 QMP has two types of commands: regular and query commands. Regular commands
16 usually change the Virtual Machine's state someway
, while query commands just
17 return information
. The sections below are divided accordingly
.
19 It
's important to observe that all communication examples are formatted in
20 a reader-friendly way, so that they're easier to understand
. However
, in real
21 protocol usage
, they
're emitted as a single line.
23 Also, the following notation is used to denote data flow:
25 -> data issued by the Client
26 <- Server data response
28 Please, refer to the QMP specification (QMP/qmp-spec.txt) for detailed
29 information on the Server command and response formats.
31 NOTE: This document is temporary and will be replaced soon.
33 1. Stability Considerations
34 ===========================
36 The current QMP command set (described in this file) may be useful for a
37 number of use cases, however it's limited and several commands have bad
38 defined semantics
, specially with regard to command completion
.
40 These problems are going to be solved incrementally
in the next QEMU releases
41 and we
're going to establish a deprecation policy for badly defined commands.
43 If you're planning to adopt QMP
, please observe the following
:
45 1. The deprecation policy will take effect and be documented soon
, please
46 check the documentation of each used command as soon as a
new release of
49 2. DO NOT rely on anything which is not explicit documented
51 3. Errors
, in special
, are not documented
. Applications should NOT check
52 for specific errors classes or
data (it
's strongly recommended to only
53 check for the "error" key)
58 Server's responses
in the examples below are always a success response
, please
59 refer to the QMP specification
for more details on error responses
.
66 .mhandler
.cmd_new
= qmp_marshal_input_quit
,
79 -> { "execute": "quit" }
86 .args_type
= "force:-f,device:B",
87 .mhandler
.cmd_new
= qmp_marshal_input_eject
,
94 Eject a removable medium
.
98 - force
: force
ejection (json
-bool
, optional
)
99 - device
: device
name (json
-string
)
103 -> { "execute": "eject", "arguments": { "device": "ide1-cd0" } }
106 Note
: The
"force" argument defaults to
false.
112 .args_type
= "device:B,target:F,arg:s?",
113 .mhandler
.cmd_new
= qmp_marshal_input_change
,
120 Change a removable medium or VNC configuration
.
124 - "device": device
name (json
-string
)
125 - "target": filename or
item (json
-string
)
126 - "arg": additional
argument (json
-string
, optional
)
130 1. Change a removable medium
132 -> { "execute": "change",
133 "arguments": { "device": "ide1-cd0",
134 "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } }
137 2. Change VNC password
139 -> { "execute": "change",
140 "arguments": { "device": "vnc", "target": "password",
147 .name
= "screendump",
148 .args_type
= "filename:F",
149 .mhandler
.cmd_new
= qmp_marshal_input_screendump
,
156 Save screen into PPM image
.
160 - "filename": file
path (json
-string
)
164 -> { "execute": "screendump", "arguments": { "filename": "/tmp/image" } }
172 .mhandler
.cmd_new
= qmp_marshal_input_stop
,
185 -> { "execute": "stop" }
193 .mhandler
.cmd_new
= qmp_marshal_input_cont
,
206 -> { "execute": "cont" }
212 .name
= "system_wakeup",
214 .mhandler
.cmd_new
= qmp_marshal_input_system_wakeup
,
221 Wakeup guest from suspend
.
227 -> { "execute": "system_wakeup" }
233 .name
= "system_reset",
235 .mhandler
.cmd_new
= qmp_marshal_input_system_reset
,
248 -> { "execute": "system_reset" }
254 .name
= "system_powerdown",
256 .mhandler
.cmd_new
= qmp_marshal_input_system_powerdown
,
263 Send system power down event
.
269 -> { "execute": "system_powerdown" }
275 .name
= "device_add",
276 .args_type
= "device:O",
277 .params
= "driver[,prop=value][,...]",
278 .help
= "add device, like -device on the command line",
279 .user_print
= monitor_user_noop
,
280 .mhandler
.cmd_new
= do_device_add
,
291 - "driver": the name of the
new device
's driver (json-string)
292 - "bus": the device's parent
bus (device tree path
, json
-string
, optional
)
293 - "id": the device
's ID, must be unique (json-string)
298 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
303 (1) For detailed information about this command, please refer to the
304 'docs
/qdev
-device
-use
.txt
' file.
306 (2) It's possible to list device properties by running QEMU with the
307 "-device DEVICE,\?" command
-line argument
, where DEVICE is the device
's name
312 .name = "device_del",
314 .mhandler.cmd_new = qmp_marshal_input_device_del,
325 - "id": the device's
ID (json
-string
)
329 -> { "execute": "device_del", "arguments": { "id": "net1" } }
336 .args_type
= "keys:O,hold-time:i?",
337 .mhandler
.cmd_new
= qmp_marshal_input_send_key
,
349 - "key": key
sequence (a json
-array of key union values
,
350 union can be number or qcode
enum)
352 - hold
-time
: time to delay key up events
, milliseconds
. Defaults to
100
357 -> { "execute": "send-key",
358 "arguments": { "keys": [ { "type": "qcode", "data": "ctrl" },
359 { "type": "qcode", "data": "alt" },
360 { "type": "qcode", "data": "delete" } ] } }
367 .args_type
= "index:i",
368 .mhandler
.cmd_new
= qmp_marshal_input_cpu
,
379 - "index": the CPU
's index (json-int)
383 -> { "execute": "cpu", "arguments": { "index": 0 } }
386 Note: CPUs' indexes are obtained with the
'query-cpus' command
.
393 .mhandler
.cmd_new
= qmp_marshal_input_cpu_add
,
404 - "id": cpu
id (json
-int
)
408 -> { "execute": "cpu-add", "arguments": { "id": 2 } }
415 .args_type
= "val:l,size:i,filename:s,cpu:i?",
416 .mhandler
.cmd_new
= qmp_marshal_input_memsave
,
423 Save to disk virtual memory dump starting at
'val' of size
'size'.
427 - "val": the starting
address (json
-int
)
428 - "size": the memory size
, in bytes (json
-int
)
429 - "filename": file
path (json
-string
)
430 - "cpu": virtual CPU
index (json
-int
, optional
)
434 -> { "execute": "memsave",
435 "arguments": { "val": 10,
437 "filename": "/tmp/virtual-mem-dump" } }
444 .args_type
= "val:l,size:i,filename:s",
445 .mhandler
.cmd_new
= qmp_marshal_input_pmemsave
,
452 Save to disk physical memory dump starting at
'val' of size
'size'.
456 - "val": the starting
address (json
-int
)
457 - "size": the memory size
, in bytes (json
-int
)
458 - "filename": file
path (json
-string
)
462 -> { "execute": "pmemsave",
463 "arguments": { "val": 10,
465 "filename": "/tmp/physical-mem-dump" } }
471 .name
= "inject-nmi",
473 .mhandler
.cmd_new
= qmp_marshal_input_inject_nmi
,
480 Inject an NMI on the
default CPU (x86
/s390
) or all
CPUs (ppc64
).
486 -> { "execute": "inject-nmi" }
489 Note
: inject
-nmi fails when the guest doesn
't support injecting.
494 .name = "ringbuf-write",
495 .args_type = "device:s,data:s,format:s?",
496 .mhandler.cmd_new = qmp_marshal_input_ringbuf_write,
503 Write to a ring buffer character device.
507 - "device": ring buffer character device name (json-string)
508 - "data": data to write (json-string)
509 - "format": data format (json-string, optional)
510 - Possible values: "utf8" (default), "base64"
511 Bug: invalid base64 is currently not rejected.
512 Whitespace *is* invalid.
516 -> { "execute": "ringbuf-write",
517 "arguments": { "device": "foo",
525 .name = "ringbuf-read",
526 .args_type = "device:s,size:i,format:s?",
527 .mhandler.cmd_new = qmp_marshal_input_ringbuf_read,
534 Read from a ring buffer character device.
538 - "device": ring buffer character device name (json-string)
539 - "size": how many bytes to read at most (json-int)
540 - Number of data bytes, not number of characters in encoded data
541 - "format": data format (json-string, optional)
542 - Possible values: "utf8" (default), "base64"
543 - Naturally, format "utf8" works only when the ring buffer
544 contains valid UTF-8 text. Invalid UTF-8 sequences get
545 replaced. Bug: replacement doesn't work
. Bug
: can screw
546 up on encountering NUL characters
, after the ring buffer
547 lost data
, and when reading stops because the size limit
552 -> { "execute": "ringbuf-read",
553 "arguments": { "device": "foo",
556 <- {"return": "abcdefgh"}
561 .name
= "xen-save-devices-state",
562 .args_type
= "filename:F",
563 .mhandler
.cmd_new
= qmp_marshal_input_xen_save_devices_state
,
567 xen
-save
-devices
-state
570 Save the state of all devices to file
. The RAM and the block devices
571 of the VM are not saved by
this command
.
575 - "filename": the file to save the state of the devices to as binary
576 data
. See xen
-save
-devices
-state
.txt
for a description of the binary
581 -> { "execute": "xen-save-devices-state",
582 "arguments": { "filename": "/tmp/save" } }
588 .name
= "xen-set-global-dirty-log",
589 .args_type
= "enable:b",
590 .mhandler
.cmd_new
= qmp_marshal_input_xen_set_global_dirty_log
,
594 xen
-set
-global
-dirty
-log
597 Enable or disable the global dirty log mode
.
601 - "enable": Enable it or disable it
.
605 -> { "execute": "xen-set-global-dirty-log",
606 "arguments": { "enable": true } }
613 .args_type
= "detach:-d,blk:-b,inc:-i,uri:s",
614 .mhandler
.cmd_new
= qmp_marshal_input_migrate
,
625 - "blk": block migration
, full disk
copy (json
-bool
, optional
)
626 - "inc": incremental disk
copy (json
-bool
, optional
)
627 - "uri": Destination
URI (json
-string
)
631 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
636 (1) The
'query-migrate' command should be used to check migration
's progress
637 and final result (this information is provided by the 'status
' member)
638 (2) All boolean arguments default to false
639 (3) The user Monitor's
"detach" argument is invalid
in QMP and should not
645 .name
= "migrate_cancel",
647 .mhandler
.cmd_new
= qmp_marshal_input_migrate_cancel
,
654 Cancel the current migration
.
660 -> { "execute": "migrate_cancel" }
665 .name
= "migrate-set-cache-size",
666 .args_type
= "value:o",
667 .mhandler
.cmd_new
= qmp_marshal_input_migrate_set_cache_size
,
671 migrate
-set
-cache
-size
672 ----------------------
674 Set cache size to be used by XBZRLE migration
, the cache size will be rounded
675 down to the nearest power of
2
679 - "value": cache size
in bytes (json
-int
)
683 -> { "execute": "migrate-set-cache-size", "arguments": { "value": 536870912 } }
688 .name
= "query-migrate-cache-size",
690 .mhandler
.cmd_new
= qmp_marshal_input_query_migrate_cache_size
,
694 query
-migrate
-cache
-size
695 ------------------------
697 Show cache size to be used by XBZRLE migration
699 returns a json
-object with the following information
:
704 -> { "execute": "query-migrate-cache-size" }
705 <- { "return": 67108864 }
710 .name
= "migrate_set_speed",
711 .args_type
= "value:o",
712 .mhandler
.cmd_new
= qmp_marshal_input_migrate_set_speed
,
719 Set maximum speed
for migrations
.
723 - "value": maximum speed
, in bytes per
second (json
-int
)
727 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
733 .name
= "migrate_set_downtime",
734 .args_type
= "value:T",
735 .mhandler
.cmd_new
= qmp_marshal_input_migrate_set_downtime
,
742 Set maximum tolerated
downtime (in seconds
) for migrations
.
746 - "value": maximum
downtime (json
-number
)
750 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
756 .name
= "client_migrate_info",
757 .args_type
= "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
758 .params
= "protocol hostname port tls-port cert-subject",
759 .help
= "send migration info to spice/vnc client",
760 .user_print
= monitor_user_noop
,
761 .mhandler
.cmd_async
= client_migrate_info
,
762 .flags
= MONITOR_CMD_ASYNC
,
769 Set the spice
/vnc connection info
for the migration target
. The spice
/vnc
770 server will ask the spice
/vnc client to automatically reconnect
using the
771 new parameters (if specified
) once the vm migration finished successfully
.
775 - "protocol": protocol
: "spice" or
"vnc" (json
-string
)
776 - "hostname": migration target
hostname (json
-string
)
777 - "port": spice
/vnc tcp port
for plaintext
channels (json
-int
, optional
)
778 - "tls-port": spice tcp port
for tls
-secured
channels (json
-int
, optional
)
779 - "cert-subject": server certificate
subject (json
-string
, optional
)
783 -> { "execute": "client_migrate_info",
784 "arguments": { "protocol": "spice",
785 "hostname": "virt42.lab.kraxel.org",
792 .name
= "dump-guest-memory",
793 .args_type
= "paging:b,protocol:s,begin:i?,end:i?,format:s?",
794 .params
= "-p protocol [begin] [length] [format]",
795 .help
= "dump guest memory to file",
796 .user_print
= monitor_user_noop
,
797 .mhandler
.cmd_new
= qmp_marshal_input_dump_guest_memory
,
804 Dump guest memory to file
. The file can be processed with crash or gdb
.
808 - "paging": do paging to get guest
's memory mapping (json-bool)
809 - "protocol": destination file(started with "file:") or destination file
810 descriptor (started with "fd:") (json-string)
811 - "begin": the starting physical address. It's optional
, and should be specified
812 with length
together (json
-int
)
813 - "length": the memory size
, in bytes
. It
's optional, and should be specified
814 with begin together (json-int)
815 - "format": the format of guest memory dump. It's optional
, and can be
816 elf|kdump
-zlib|kdump
-lzo|kdump
-snappy
, but non
-elf formats will
817 conflict with paging and filter
, ie
. begin and
length (json
-string
)
821 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
826 (1) All boolean arguments
default to
false
831 .name
= "query-dump-guest-memory-capability",
833 .mhandler
.cmd_new
= qmp_marshal_input_query_dump_guest_memory_capability
,
837 query
-dump
-guest
-memory
-capability
840 Show available formats
for 'dump-guest-memory'
844 -> { "execute": "query-dump-guest-memory-capability" }
845 <- { "return": { "formats":
846 ["elf", "kdump-zlib", "kdump-lzo", "kdump-snappy"] }
851 .name
= "netdev_add",
852 .args_type
= "netdev:O",
853 .mhandler
.cmd_new
= qmp_netdev_add
,
860 Add host network device
.
864 - "type": the device type
, "tap", "user", ... (json
-string
)
865 - "id": the device
's ID, must be unique (json-string)
870 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
873 Note: The supported device options are the same ones supported by the '-netdev
'
874 command-line argument, which are listed in the '-help
' output or QEMU's
880 .name
= "netdev_del",
882 .mhandler
.cmd_new
= qmp_marshal_input_netdev_del
,
889 Remove host network device
.
893 - "id": the device
's ID, must be unique (json-string)
897 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
904 .name = "object-add",
905 .args_type = "qom-type:s,id:s,props:q?",
906 .mhandler.cmd_new = qmp_object_add,
917 - "qom-type": the object's QOM type
, i
.e
. the
class name (json
-string
)
918 - "id": the object
's ID, must be unique (json-string)
919 - "props": a dictionary of object property values (optional, json-dict)
923 -> { "execute": "object-add", "arguments": { "qom-type": "rng-random", "id": "rng1",
924 "props": { "filename": "/dev/hwrng" } } }
930 .name = "object-del",
932 .mhandler.cmd_new = qmp_marshal_input_object_del,
943 - "id": the object's
ID (json
-string
)
947 -> { "execute": "object-del", "arguments": { "id": "rng1" } }
955 .name
= "block_resize",
956 .args_type
= "device:s?,node-name:s?,size:o",
957 .mhandler
.cmd_new
= qmp_marshal_input_block_resize
,
964 Resize a block image
while a guest is running
.
968 - "device": the device
's ID, must be unique (json-string)
969 - "node-name": the node name in the block driver state graph (json-string)
974 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
980 .name = "block-stream",
981 .args_type = "device:B,base:s?,speed:o?,backing-file:s?,on-error:s?",
982 .mhandler.cmd_new = qmp_marshal_input_block_stream,
986 .name = "block-commit",
987 .args_type = "device:B,base:s?,top:s?,backing-file:s?,speed:o?",
988 .mhandler.cmd_new = qmp_marshal_input_block_commit,
995 Live commit of data from overlay image nodes into backing nodes - i.e., writes
996 data between 'top
' and 'base
' into 'base
'.
1000 - "device": The device's ID
, must be
unique (json
-string
)
1001 - "base": The file name of the backing image to write data into
.
1002 If not specified
, this is the deepest backing image
1003 (json
-string
, optional
)
1004 - "top": The file name of the backing image within the image chain
,
1005 which contains the topmost data to be committed down
. If
1006 not specified
, this is the active layer
. (json
-string
, optional
)
1008 - backing
-file
: The backing file string to write into the overlay
1009 image of
'top'. If
'top' is the active layer
,
1010 specifying a backing file string is an error
. This
1011 filename is not validated
.
1013 If a pathname string is such that it cannot be
1014 resolved by QEMU
, that means that subsequent QMP or
1015 HMP commands must use node
-names
for the image
in
1016 question
, as filename lookup methods will fail
.
1018 If not specified
, QEMU will automatically determine
1019 the backing file string to use
, or error out
if
1020 there is no obvious choice
. Care should be taken
1021 when specifying the string
, to specify a valid
1022 filename or protocol
.
1023 (json
-string
, optional
) (Since
2.1)
1025 If top
== base
, that is an error
.
1026 If top
== active
, the job will not be completed by itself
,
1027 user needs to complete the job with the block
-job
-complete
1028 command after getting the ready event
. (Since
2.0)
1030 If the base image is smaller than top
, then the base image
1031 will be resized to be the same size as top
. If top is
1032 smaller than the base image
, the base will not be
1033 truncated
. If you want the base image size to match the
1034 size of the smaller top
, you can safely truncate it
1035 yourself once the commit operation successfully completes
.
1037 - "speed": the maximum speed
, in bytes per
second (json
-int
, optional
)
1042 -> { "execute": "block-commit", "arguments": { "device": "virtio0",
1043 "top": "/tmp/snap1.qcow2" } }
1049 .name
= "drive-backup",
1050 .args_type
= "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1051 "on-source-error:s?,on-target-error:s?",
1052 .mhandler
.cmd_new
= qmp_marshal_input_drive_backup
,
1059 Start a point
-in-time copy of a block device to a
new destination
. The
1060 status of ongoing drive
-backup operations can be checked with
1061 query
-block
-jobs where the BlockJobInfo
.type field has the value
'backup'.
1062 The operation can be stopped before it has completed
using the
1063 block
-job
-cancel command
.
1067 - "device": the name of the device which should be copied
.
1069 - "target": the target of the
new image
. If the file exists
, or
if it is a
1070 device
, the existing file
/device will be used as the
new
1071 destination
. If it does not exist
, a
new file will be created
.
1073 - "format": the format of the
new destination
, default is to probe
if 'mode' is
1074 'existing', else the format of the source
1075 (json
-string
, optional
)
1076 - "sync": what parts of the disk image should be copied to the destination
;
1077 possibilities include
"full" for all the disk
, "top" for only the sectors
1078 allocated
in the topmost image
, or
"none" to only replicate
new I
/O
1080 - "mode": whether and how QEMU should create a
new image
1081 (NewImageMode
, optional
, default 'absolute-paths')
1082 - "speed": the maximum speed
, in bytes per
second (json
-int
, optional
)
1083 - "on-source-error": the action to take on an error on the source
, default
1084 'report'. 'stop' and
'enospc' can only be used
1085 if the block device supports io
-status
.
1086 (BlockdevOnError
, optional
)
1087 - "on-target-error": the action to take on an error on the target
, default
1088 'report' (no limitations
, since
this applies to
1089 a different block device than device
).
1090 (BlockdevOnError
, optional
)
1093 -> { "execute": "drive-backup", "arguments": { "device": "drive0",
1095 "target": "backup.img" } }
1100 .name
= "block-job-set-speed",
1101 .args_type
= "device:B,speed:o",
1102 .mhandler
.cmd_new
= qmp_marshal_input_block_job_set_speed
,
1106 .name
= "block-job-cancel",
1107 .args_type
= "device:B,force:b?",
1108 .mhandler
.cmd_new
= qmp_marshal_input_block_job_cancel
,
1111 .name
= "block-job-pause",
1112 .args_type
= "device:B",
1113 .mhandler
.cmd_new
= qmp_marshal_input_block_job_pause
,
1116 .name
= "block-job-resume",
1117 .args_type
= "device:B",
1118 .mhandler
.cmd_new
= qmp_marshal_input_block_job_resume
,
1121 .name
= "block-job-complete",
1122 .args_type
= "device:B",
1123 .mhandler
.cmd_new
= qmp_marshal_input_block_job_complete
,
1126 .name
= "transaction",
1127 .args_type
= "actions:q",
1128 .mhandler
.cmd_new
= qmp_marshal_input_transaction
,
1135 Atomically operate on one or more block devices
. The only supported operations
1136 for now are drive
-backup
, internal and external snapshotting
. A list of
1137 dictionaries is accepted
, that contains the actions to be performed
.
1138 If there is any failure performing any of the operations
, all operations
1139 for the group are abandoned
.
1141 For external snapshots
, the dictionary contains the device
, the file to use
for
1142 the
new snapshot
, and the format
. The
default format
, if not specified
, is
1145 Each
new snapshot defaults to being created by
QEMU (wiping any
1146 contents
if the file already exists
), but it is also possible to reuse
1147 an externally
-created file
. In the latter
case, you should ensure that
1148 the
new image file has the same contents as the current one
; QEMU cannot
1149 perform any meaningful check
. Typically
this is achieved by
using the
1150 current image file as the backing file
for the
new image
.
1152 On failure
, the original disks pre
-snapshot attempt will be used
.
1154 For internal snapshots
, the dictionary contains the device and the snapshot
's
1155 name. If an internal snapshot matching name already exists, the request will
1156 be rejected. Only some image formats support it, for example, qcow2, rbd,
1159 On failure, qemu will try delete the newly created internal snapshot in the
1160 transaction. When an I/O error occurs during deletion, the user needs to fix
1161 it later with qemu-img or other command.
1166 - "type": the operation to perform. The only supported
1167 value is "blockdev-snapshot-sync". (json-string)
1168 - "data": a dictionary. The contents depend on the value
1169 of "type". When "type" is "blockdev-snapshot-sync":
1170 - "device": device name to snapshot (json-string)
1171 - "node-name": graph node name to snapshot (json-string)
1172 - "snapshot-file": name of new image file (json-string)
1173 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1174 - "format": format of new image (json-string, optional)
1175 - "mode": whether and how QEMU should create the snapshot file
1176 (NewImageMode, optional, default "absolute-paths")
1177 When "type" is "blockdev-snapshot-internal-sync":
1178 - "device": device name to snapshot (json-string)
1179 - "name": name of the new snapshot (json-string)
1183 -> { "execute": "transaction",
1184 "arguments": { "actions": [
1185 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd0",
1186 "snapshot-file": "/some/place/my-image",
1187 "format": "qcow2" } },
1188 { "type": "blockdev-snapshot-sync", "data" : { "node-name": "myfile",
1189 "snapshot-file": "/some/place/my-image2",
1190 "snapshot-node-name": "node3432",
1192 "format": "qcow2" } },
1193 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd1",
1194 "snapshot-file": "/some/place/my-image2",
1196 "format": "qcow2" } },
1197 { "type": "blockdev-snapshot-internal-sync", "data" : {
1198 "device": "ide-hd2",
1199 "name": "snapshot0" } } ] } }
1205 .name = "blockdev-snapshot-sync",
1206 .args_type = "device:s?,node-name:s?,snapshot-file:s,snapshot-node-name:s?,format:s?,mode:s?",
1207 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
1211 blockdev-snapshot-sync
1212 ----------------------
1214 Synchronous snapshot of a block device. snapshot-file specifies the
1215 target of the new image. If the file exists, or if it is a device, the
1216 snapshot will be created in the existing file/device. If does not
1217 exist, a new file will be created. format specifies the format of the
1218 snapshot image, default is qcow2.
1222 - "device": device name to snapshot (json-string)
1223 - "node-name": graph node name to snapshot (json-string)
1224 - "snapshot-file": name of new image file (json-string)
1225 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1226 - "mode": whether and how QEMU should create the snapshot file
1227 (NewImageMode, optional, default "absolute-paths")
1228 - "format": format of new image (json-string, optional)
1232 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
1234 "/some/place/my-image",
1235 "format": "qcow2" } }
1241 .name = "blockdev-snapshot-internal-sync",
1242 .args_type = "device:B,name:s",
1243 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_internal_sync,
1247 blockdev-snapshot-internal-sync
1248 -------------------------------
1250 Synchronously take an internal snapshot of a block device when the format of
1251 image used supports it. If the name is an empty string, or a snapshot with
1252 name already exists, the operation will fail.
1256 - "device": device name to snapshot (json-string)
1257 - "name": name of the new snapshot (json-string)
1261 -> { "execute": "blockdev-snapshot-internal-sync",
1262 "arguments": { "device": "ide-hd0",
1263 "name": "snapshot0" }
1270 .name = "blockdev-snapshot-delete-internal-sync",
1271 .args_type = "device:B,id:s?,name:s?",
1273 qmp_marshal_input_blockdev_snapshot_delete_internal_sync,
1277 blockdev-snapshot-delete-internal-sync
1278 --------------------------------------
1280 Synchronously delete an internal snapshot of a block device when the format of
1281 image used supports it. The snapshot is identified by name or id or both. One
1282 of name or id is required. If the snapshot is not found, the operation will
1287 - "device": device name (json-string)
1288 - "id": ID of the snapshot (json-string, optional)
1289 - "name": name of the snapshot (json-string, optional)
1293 -> { "execute": "blockdev-snapshot-delete-internal-sync",
1294 "arguments": { "device": "ide-hd0",
1295 "name": "snapshot0" }
1299 "name": "snapshot0",
1301 "date-sec": 1000012,
1303 "vm-clock-sec": 100,
1311 .name = "drive-mirror",
1312 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1313 "node-name:s?,replaces:s?,"
1314 "on-source-error:s?,on-target-error:s?,"
1315 "granularity:i?,buf-size:i?",
1316 .mhandler.cmd_new = qmp_marshal_input_drive_mirror,
1323 Start mirroring a block device's writes to a
new destination
. target
1324 specifies the target of the
new image
. If the file exists
, or
if it is
1325 a device
, it will be used as the
new destination
for writes
. If it does not
1326 exist
, a
new file will be created
. format specifies the format of the
1327 mirror image
, default is to probe
if mode
='existing', else the format
1332 - "device": device name to operate
on (json
-string
)
1333 - "target": name of
new image
file (json
-string
)
1334 - "format": format of
new image (json
-string
, optional
)
1335 - "node-name": the name of the
new block driver state
in the node graph
1336 (json
-string
, optional
)
1337 - "replaces": the block driver node name to replace when finished
1338 (json
-string
, optional
)
1339 - "mode": how an image file should be created into the target
1340 file
/device (NewImageMode
, optional
, default 'absolute-paths')
1341 - "speed": maximum speed of the streaming job
, in bytes per second
1343 - "granularity": granularity of the dirty bitmap
, in bytes (json
-int
, optional
)
1344 - "buf_size": maximum amount of data
in flight from source to target
, in bytes
1345 (json
-int
, default 10M
)
1346 - "sync": what parts of the disk image should be copied to the destination
;
1347 possibilities include
"full" for all the disk
, "top" for only the sectors
1348 allocated
in the topmost image
, or
"none" to only replicate
new I
/O
1350 - "on-source-error": the action to take on an error on the source
1351 (BlockdevOnError
, default 'report')
1352 - "on-target-error": the action to take on an error on the target
1353 (BlockdevOnError
, default 'report')
1355 The
default value of the granularity is the image cluster size clamped
1356 between
4096 and
65536, if the image format defines one
. If the format
1357 does not define a cluster size
, the
default value of the granularity
1363 -> { "execute": "drive-mirror", "arguments": { "device": "ide-hd0",
1364 "target": "/some/place/my-image",
1366 "format": "qcow2" } }
1372 .name
= "change-backing-file",
1373 .args_type
= "device:s,image-node-name:s,backing-file:s",
1374 .mhandler
.cmd_new
= qmp_marshal_input_change_backing_file
,
1382 Change the backing file
in the image file metadata
. This does not cause
1383 QEMU to reopen the image file to reparse the backing
filename (it may
,
1384 however
, perform a reopen to change permissions from r
/o
-> r
/w
-> r
/o
,
1385 if needed
). The
new backing file string is written into the image file
1386 metadata
, and the QEMU internal strings are updated
.
1390 - "image-node-name": The name of the block driver state node of the
1391 image to modify
. The
"device" is argument is used to
1392 verify
"image-node-name" is
in the chain described by
1394 (json
-string
, optional
)
1396 - "device": The name of the device
.
1399 - "backing-file": The string to write as the backing file
. This string is
1400 not validated
, so care should be taken when specifying
1401 the string or the image chain may not be able to be
1405 Returns
: Nothing on success
1406 If
"device" does not exist or cannot be determined
, DeviceNotFound
1412 .args_type
= "value:M",
1413 .mhandler
.cmd_new
= qmp_marshal_input_balloon
,
1420 Request VM to change its memory
allocation (in bytes
).
1424 - "value": New memory
allocation (json
-int
)
1428 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1435 .args_type
= "name:s,up:b",
1436 .mhandler
.cmd_new
= qmp_marshal_input_set_link
,
1443 Change the link status of a network adapter
.
1447 - "name": network device
name (json
-string
)
1448 - "up": status is
up (json
-bool
)
1452 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
1459 .args_type
= "fdname:s",
1460 .params
= "getfd name",
1461 .help
= "receive a file descriptor via SCM rights and assign it a name",
1462 .mhandler
.cmd_new
= qmp_marshal_input_getfd
,
1469 Receive a file descriptor via SCM rights and assign it a name
.
1473 - "fdname": file descriptor
name (json
-string
)
1477 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1482 (1) If the name specified by the
"fdname" argument already exists
,
1483 the file descriptor assigned to it will be closed and replaced
1484 by the received file descriptor
.
1485 (2) The
'closefd' command can be used to explicitly close the file
1486 descriptor when it is no longer needed
.
1492 .args_type
= "fdname:s",
1493 .params
= "closefd name",
1494 .help
= "close a file descriptor previously passed via SCM rights",
1495 .mhandler
.cmd_new
= qmp_marshal_input_closefd
,
1502 Close a file descriptor previously passed via SCM rights
.
1506 - "fdname": file descriptor
name (json
-string
)
1510 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1517 .args_type
= "fdset-id:i?,opaque:s?",
1518 .params
= "add-fd fdset-id opaque",
1519 .help
= "Add a file descriptor, that was passed via SCM rights, to an fd set",
1520 .mhandler
.cmd_new
= qmp_marshal_input_add_fd
,
1527 Add a file descriptor
, that was passed via SCM rights
, to an fd set
.
1531 - "fdset-id": The ID of the fd set to add the file descriptor to
.
1532 (json
-int
, optional
)
1533 - "opaque": A free
-form string that can be used to describe the fd
.
1534 (json
-string
, optional
)
1536 Return a json
-object with the following information
:
1538 - "fdset-id": The ID of the fd set that the fd was added to
. (json
-int
)
1539 - "fd": The file descriptor that was received via SCM rights and added to the
1544 -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1545 <- { "return": { "fdset-id": 1, "fd": 3 } }
1549 (1) The list of fd sets is shared by all monitor connections
.
1550 (2) If
"fdset-id" is not specified
, a
new fd set will be created
.
1555 .name
= "remove-fd",
1556 .args_type
= "fdset-id:i,fd:i?",
1557 .params
= "remove-fd fdset-id fd",
1558 .help
= "Remove a file descriptor from an fd set",
1559 .mhandler
.cmd_new
= qmp_marshal_input_remove_fd
,
1566 Remove a file descriptor from an fd set
.
1570 - "fdset-id": The ID of the fd set that the file descriptor belongs to
.
1572 - "fd": The file descriptor that is to be removed
. (json
-int
, optional
)
1576 -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1581 (1) The list of fd sets is shared by all monitor connections
.
1582 (2) If
"fd" is not specified
, all file descriptors
in "fdset-id" will be
1588 .name
= "query-fdsets",
1590 .help
= "Return information describing all fd sets",
1591 .mhandler
.cmd_new
= qmp_marshal_input_query_fdsets
,
1598 Return information describing all fd sets
.
1604 -> { "execute": "query-fdsets" }
1610 "opaque": "rdonly:/path/to/file"
1614 "opaque": "rdwr:/path/to/file"
1633 Note
: The list of fd sets is shared by all monitor connections
.
1638 .name
= "block_passwd",
1639 .args_type
= "device:s?,node-name:s?,password:s",
1640 .mhandler
.cmd_new
= qmp_marshal_input_block_passwd
,
1647 Set the password of encrypted block devices
.
1651 - "device": device
name (json
-string
)
1652 - "node-name": name
in the block driver state
graph (json
-string
)
1653 - "password": password (json
-string
)
1657 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
1658 "password": "12345" } }
1664 .name
= "block_set_io_throttle",
1665 .args_type
= "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l,bps_max:l?,bps_rd_max:l?,bps_wr_max:l?,iops_max:l?,iops_rd_max:l?,iops_wr_max:l?,iops_size:l?",
1666 .mhandler
.cmd_new
= qmp_marshal_input_block_set_io_throttle
,
1670 block_set_io_throttle
1673 Change I
/O throttle limits
for a block drive
.
1677 - "device": device
name (json
-string
)
1678 - "bps": total throughput limit
in bytes per
second (json
-int
)
1679 - "bps_rd": read throughput limit
in bytes per
second (json
-int
)
1680 - "bps_wr": write throughput limit
in bytes per
second (json
-int
)
1681 - "iops": total I
/O operations per
second (json
-int
)
1682 - "iops_rd": read I
/O operations per
second (json
-int
)
1683 - "iops_wr": write I
/O operations per
second (json
-int
)
1684 - "bps_max": total max
in bytes (json
-int
)
1685 - "bps_rd_max": read max
in bytes (json
-int
)
1686 - "bps_wr_max": write max
in bytes (json
-int
)
1687 - "iops_max": total I
/O operations
max (json
-int
)
1688 - "iops_rd_max": read I
/O operations
max (json
-int
)
1689 - "iops_wr_max": write I
/O operations
max (json
-int
)
1690 - "iops_size": I
/O size
in bytes when
limiting (json
-int
)
1694 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
1713 .name
= "set_password",
1714 .args_type
= "protocol:s,password:s,connected:s?",
1715 .mhandler
.cmd_new
= qmp_marshal_input_set_password
,
1722 Set the password
for vnc
/spice protocols
.
1726 - "protocol": protocol
name (json
-string
)
1727 - "password": password (json
-string
)
1728 - "connected": [ keep | disconnect | fail
] (josn
-string
, optional
)
1732 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
1733 "password": "secret" } }
1739 .name
= "expire_password",
1740 .args_type
= "protocol:s,time:s",
1741 .mhandler
.cmd_new
= qmp_marshal_input_expire_password
,
1748 Set the password expire time
for vnc
/spice protocols
.
1752 - "protocol": protocol
name (json
-string
)
1753 - "time": [ now |
never |
+secs | secs
] (json
-string
)
1757 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
1764 .name
= "add_client",
1765 .args_type
= "protocol:s,fdname:s,skipauth:b?,tls:b?",
1766 .mhandler
.cmd_new
= qmp_marshal_input_add_client
,
1773 Add a graphics client
1777 - "protocol": protocol
name (json
-string
)
1778 - "fdname": file descriptor
name (json
-string
)
1779 - "skipauth": whether to skip
authentication (json
-bool
, optional
)
1780 - "tls": whether to perform
TLS (json
-bool
, optional
)
1784 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
1785 "fdname": "myclient" } }
1790 .name
= "qmp_capabilities",
1793 .help
= "enable QMP capabilities",
1794 .user_print
= monitor_user_noop
,
1795 .mhandler
.cmd_new
= do_qmp_capabilities
,
1802 Enable QMP capabilities
.
1808 -> { "execute": "qmp_capabilities" }
1811 Note
: This command must be issued before issuing any other command
.
1816 .name
= "human-monitor-command",
1817 .args_type
= "command-line:s,cpu-index:i?",
1818 .mhandler
.cmd_new
= qmp_marshal_input_human_monitor_command
,
1822 human
-monitor
-command
1823 ---------------------
1825 Execute a Human Monitor command
.
1829 - command
-line
: the command name and its arguments
, just like the
1830 Human Monitor
's shell (json-string)
1831 - cpu-index: select the CPU number to be used by commands which access CPU
1832 data, like 'info registers
'. The Monitor selects CPU 0 if this
1833 argument is not provided (json-int, optional)
1837 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1838 <- { "return": "kvm support: enabled\r\n" }
1842 (1) The Human Monitor is NOT an stable interface, this means that command
1843 names, arguments and responses can change or be removed at ANY time.
1844 Applications that rely on long term stability guarantees should NOT
1849 o This command is stateless, this means that commands that depend
1850 on state information (such as getfd) might not work
1852 o Commands that prompt the user for data (eg. 'cont
' when the block
1853 device is encrypted) don't currently work
1858 HXCOMM Each query command below is inside a SQMP
/EQMP section
, do NOT change
1859 HXCOMM
this! We will possibly move query commands definitions inside those
1860 HXCOMM sections
, just like regular commands
.
1870 Return a json
-object with the following information
:
1872 - "qemu": A json
-object containing three integer values
:
1873 - "major": QEMU
's major version (json-int)
1874 - "minor": QEMU's minor
version (json
-int
)
1875 - "micro": QEMU
's micro version (json-int)
1876 - "package": package's
version (json
-string
)
1880 -> { "execute": "query-version" }
1895 .name
= "query-version",
1897 .mhandler
.cmd_new
= qmp_marshal_input_query_version
,
1904 List QMP available commands
.
1906 Each command is represented by a json
-object
, the returned value is a json
-array
1909 Each json
-object contain
:
1911 - "name": command
's name (json-string)
1915 -> { "execute": "query-commands" }
1919 "name":"query-balloon"
1922 "name":"system_powerdown"
1927 Note: This example has been shortened as the real response is too long.
1932 .name = "query-commands",
1934 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1941 List QMP available events.
1943 Each event is represented by a json-object, the returned value is a json-array
1946 Each json-object contains:
1948 - "name": event's
name (json
-string
)
1952 -> { "execute": "query-events" }
1964 Note
: This example has been shortened as the real response is too long
.
1969 .name
= "query-events",
1971 .mhandler
.cmd_new
= qmp_marshal_input_query_events
,
1978 Each device is represented by a json
-object
. The returned value is a json
-array
1981 Each json
-object contain the following
:
1983 - "label": device
's label (json-string)
1984 - "filename": device's
file (json
-string
)
1985 - "frontend-open": open
/closed state of the frontend device attached to
this
1990 -> { "execute": "query-chardev" }
1994 "label": "charchannel0",
1995 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.agent,server",
1996 "frontend-open": false
1999 "label": "charmonitor",
2000 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.monitor,server",
2001 "frontend-open": true
2004 "label": "charserial0",
2005 "filename": "pty:/dev/pts/2",
2006 "frontend-open": true
2014 .name
= "query-chardev",
2016 .mhandler
.cmd_new
= qmp_marshal_input_query_chardev
,
2020 query
-chardev
-backends
2023 List available character device backends
.
2025 Each backend is represented by a json
-object
, the returned value is a json
-array
2028 Each json
-object contains
:
2030 - "name": backend
name (json
-string
)
2034 -> { "execute": "query-chardev-backends" }
2055 .name
= "query-chardev-backends",
2057 .mhandler
.cmd_new
= qmp_marshal_input_query_chardev_backends
,
2064 Show the block devices
.
2066 Each block device information is stored
in a json
-object and the returned value
2067 is a json
-array of all devices
.
2069 Each json
-object contain the following
:
2071 - "device": device
name (json
-string
)
2072 - "type": device
type (json
-string
)
2073 - deprecated
, retained
for backward compatibility
2074 - Possible values
: "unknown"
2075 - "removable": true if the device is removable
, false otherwise (json
-bool
)
2076 - "locked": true if the device is locked
, false otherwise (json
-bool
)
2077 - "tray_open": only present
if removable
, true if the device has a tray
,
2078 and it is
open (json
-bool
)
2079 - "inserted": only present
if the device is inserted
, it is a json
-object
2080 containing the following
:
2081 - "file": device file
name (json
-string
)
2082 - "ro": true if read
-only
, false otherwise (json
-bool
)
2083 - "drv": driver format
name (json
-string
)
2084 - Possible values
: "blkdebug", "bochs", "cloop", "dmg",
2085 "file", "file", "ftp", "ftps", "host_cdrom",
2086 "host_device", "host_floppy", "http", "https",
2087 "nbd", "parallels", "qcow", "qcow2", "raw",
2088 "tftp", "vdi", "vmdk", "vpc", "vvfat"
2089 - "backing_file": backing file
name (json
-string
, optional
)
2090 - "backing_file_depth": number of files
in the backing file
chain (json
-int
)
2091 - "encrypted": true if encrypted
, false otherwise (json
-bool
)
2092 - "bps": limit total bytes per
second (json
-int
)
2093 - "bps_rd": limit read bytes per
second (json
-int
)
2094 - "bps_wr": limit write bytes per
second (json
-int
)
2095 - "iops": limit total I
/O operations per
second (json
-int
)
2096 - "iops_rd": limit read operations per
second (json
-int
)
2097 - "iops_wr": limit write operations per
second (json
-int
)
2098 - "bps_max": total max
in bytes (json
-int
)
2099 - "bps_rd_max": read max
in bytes (json
-int
)
2100 - "bps_wr_max": write max
in bytes (json
-int
)
2101 - "iops_max": total I
/O operations
max (json
-int
)
2102 - "iops_rd_max": read I
/O operations
max (json
-int
)
2103 - "iops_wr_max": write I
/O operations
max (json
-int
)
2104 - "iops_size": I
/O size when limiting by
iops (json
-int
)
2105 - "detect_zeroes": detect and optimize zero
writing (json
-string
)
2106 - Possible values
: "off", "on", "unmap"
2107 - "image": the detail of the image
, it is a json
-object containing
2109 - "filename": image file
name (json
-string
)
2110 - "format": image
format (json
-string
)
2111 - "virtual-size": image capacity
in bytes (json
-int
)
2112 - "dirty-flag": true if image is not cleanly closed
, not present
2113 means
clean (json
-bool
, optional
)
2114 - "actual-size": actual size on disk
in bytes of the image
, not
2115 present when image does not support thin
2116 provision (json
-int
, optional
)
2117 - "cluster-size": size of a cluster
in bytes
, not present
if image
2118 format does not support
it (json
-int
, optional
)
2119 - "encrypted": true if the image is encrypted
, not present means
2120 false or the image format does not support
2121 encryption (json
-bool
, optional
)
2122 - "backing_file": backing file name
, not present means no backing
2123 file is used or the image format does not
2124 support backing file chain
2125 (json
-string
, optional
)
2126 - "full-backing-filename": full path of the backing file
, not
2127 present
if it equals backing_file or no
2128 backing file is used
2129 (json
-string
, optional
)
2130 - "backing-filename-format": the format of the backing file
, not
2131 present means unknown or no backing
2132 file (json
-string
, optional
)
2133 - "snapshots": the internal snapshot info
, it is an optional list
2134 of json
-object containing the following
:
2135 - "id": unique snapshot
id (json
-string
)
2136 - "name": snapshot
name (json
-string
)
2137 - "vm-state-size": size of the VM state
in bytes (json
-int
)
2138 - "date-sec": UTC date of the snapshot
in seconds (json
-int
)
2139 - "date-nsec": fractional part
in nanoseconds to be used with
2141 - "vm-clock-sec": VM clock relative to boot
in seconds
2143 - "vm-clock-nsec": fractional part
in nanoseconds to be used
2144 with vm
-clock
-sec (json
-int
)
2145 - "backing-image": the detail of the backing image
, it is an
2146 optional json
-object only present when a
2147 backing image present
for this image
2149 - "io-status": I
/O operation status
, only present
if the device supports it
2150 and the VM is configured to stop on errors
. It
's always reset
2151 to "ok" when the "cont" command is issued (json_string, optional)
2152 - Possible values: "ok", "failed", "nospace"
2156 -> { "execute": "query-block" }
2161 "device":"ide0-hd0",
2168 "file":"disks/test.qcow2",
2169 "backing_file_depth":1,
2183 "detect_zeroes": "on",
2185 "filename":"disks/test.qcow2",
2187 "virtual-size":2048000,
2188 "backing_file":"base.qcow2",
2189 "full-backing-filename":"disks/base.qcow2",
2190 "backing-filename-format:"qcow2",
2194 "name": "snapshot1",
2196 "date-sec": 10000200,
2198 "vm-clock-sec": 206,
2203 "filename":"disks/base.qcow2",
2205 "virtual-size":2048000
2213 "device":"ide1-cd0",
2236 .name = "query-block",
2238 .mhandler.cmd_new = qmp_marshal_input_query_block,
2245 Show block device statistics.
2247 Each device statistic information is stored in a json-object and the returned
2248 value is a json-array of all devices.
2250 Each json-object contain the following:
2252 - "device": device name (json-string)
2253 - "stats": A json-object with the statistics information, it contains:
2254 - "rd_bytes": bytes read (json-int)
2255 - "wr_bytes": bytes written (json-int)
2256 - "rd_operations": read operations (json-int)
2257 - "wr_operations": write operations (json-int)
2258 - "flush_operations": cache flush operations (json-int)
2259 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
2260 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
2261 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
2262 - "wr_highest_offset": Highest offset of a sector written since the
2263 BlockDriverState has been opened (json-int)
2264 - "parent": Contains recursively the statistics of the underlying
2265 protocol (e.g. the host file for a qcow2 image). If there is
2266 no underlying protocol, this field is omitted
2267 (json-object, optional)
2271 -> { "execute": "query-blockstats" }
2275 "device":"ide0-hd0",
2278 "wr_highest_offset":3686448128,
2280 "wr_operations":751,
2281 "rd_bytes":122567168,
2282 "rd_operations":36772
2283 "wr_total_times_ns":313253456
2284 "rd_total_times_ns":3465673657
2285 "flush_total_times_ns":49653
2286 "flush_operations":61,
2290 "wr_highest_offset":2821110784,
2292 "wr_operations":692,
2293 "rd_bytes":122739200,
2294 "rd_operations":36604
2295 "flush_operations":51,
2296 "wr_total_times_ns":313253456
2297 "rd_total_times_ns":3465673657
2298 "flush_total_times_ns":49653
2302 "device":"ide1-cd0",
2304 "wr_highest_offset":0,
2309 "flush_operations":0,
2310 "wr_total_times_ns":0
2311 "rd_total_times_ns":0
2312 "flush_total_times_ns":0
2318 "wr_highest_offset":0,
2323 "flush_operations":0,
2324 "wr_total_times_ns":0
2325 "rd_total_times_ns":0
2326 "flush_total_times_ns":0
2332 "wr_highest_offset":0,
2337 "flush_operations":0,
2338 "wr_total_times_ns":0
2339 "rd_total_times_ns":0
2340 "flush_total_times_ns":0
2349 .name = "query-blockstats",
2350 .args_type = "query-nodes:b?",
2351 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
2358 Show CPU information.
2360 Return a json-array. Each CPU is represented by a json-object, which contains:
2362 - "CPU": CPU index (json-int)
2363 - "current": true if this is the current CPU, false otherwise (json-bool)
2364 - "halted": true if the cpu is halted, false otherwise (json-bool)
2365 - Current program counter. The key's name depends on the architecture
:
2366 "pc": i386
/x86_64 (json
-int
)
2367 "nip": PPC (json
-int
)
2368 "pc" and
"npc": sparc (json
-int
)
2369 "PC": mips (json
-int
)
2370 - "thread_id": ID of the underlying host
thread (json
-int
)
2374 -> { "execute": "query-cpus" }
2397 .name
= "query-cpus",
2399 .mhandler
.cmd_new
= qmp_marshal_input_query_cpus
,
2406 Returns a list of information about each iothread
.
2408 Note
this list excludes the QEMU main loop thread
, which is not declared
2409 using the
-object iothread command
-line option
. It is always the main thread
2412 Return a json
-array
. Each iothread is represented by a json
-object
, which contains
:
2414 - "id": name of
iothread (json
-str
)
2415 - "thread-id": ID of the underlying host
thread (json
-int
)
2419 -> { "execute": "query-iothreads" }
2436 .name
= "query-iothreads",
2438 .mhandler
.cmd_new
= qmp_marshal_input_query_iothreads
,
2445 PCI buses and devices information
.
2447 The returned value is a json
-array of all buses
. Each bus is represented by
2448 a json
-object
, which has a key with a json
-array of all PCI devices attached
2449 to it
. Each device is represented by a json
-object
.
2451 The bus json
-object contains the following
:
2453 - "bus": bus
number (json
-int
)
2454 - "devices": a json
-array of json
-objects
, each json
-object represents a
2457 The PCI device json
-object contains the following
:
2459 - "bus": identical to the parent
's bus number (json-int)
2460 - "slot": slot number (json-int)
2461 - "function": function number (json-int)
2462 - "class_info": a json-object containing:
2463 - "desc": device class description (json-string, optional)
2464 - "class": device class number (json-int)
2465 - "id": a json-object containing:
2466 - "device": device ID (json-int)
2467 - "vendor": vendor ID (json-int)
2468 - "irq": device's IRQ
if assigned (json
-int
, optional
)
2469 - "qdev_id": qdev id
string (json
-string
)
2470 - "pci_bridge": It
's a json-object, only present if this device is a
2471 PCI bridge, contains:
2472 - "bus": bus number (json-int)
2473 - "secondary": secondary bus number (json-int)
2474 - "subordinate": subordinate bus number (json-int)
2475 - "io_range": I/O memory range information, a json-object with the
2477 - "base": base address, in bytes (json-int)
2478 - "limit": limit address, in bytes (json-int)
2479 - "memory_range": memory range information, a json-object with the
2481 - "base": base address, in bytes (json-int)
2482 - "limit": limit address, in bytes (json-int)
2483 - "prefetchable_range": Prefetchable memory range information, a
2484 json-object with the following members:
2485 - "base": base address, in bytes (json-int)
2486 - "limit": limit address, in bytes (json-int)
2487 - "devices": a json-array of PCI devices if there's any attached
, each
2488 each element is represented by a json
-object
, which contains
2489 the same members of the
'PCI device json-object' described
2491 - "regions": a json
-array of json
-objects
, each json
-object represents a
2492 memory region of
this device
2494 The memory range json
-object contains the following
:
2496 - "base": base memory
address (json
-int
)
2497 - "limit": limit
value (json
-int
)
2499 The region json
-object can be an I
/O region or a memory region
, an I
/O region
2500 json
-object contains the following
:
2502 - "type": "io" (json
-string
, fixed
)
2503 - "bar": BAR
number (json
-int
)
2504 - "address": memory
address (json
-int
)
2505 - "size": memory
size (json
-int
)
2507 A memory region json
-object contains the following
:
2509 - "type": "memory" (json
-string
, fixed
)
2510 - "bar": BAR
number (json
-int
)
2511 - "address": memory
address (json
-int
)
2512 - "size": memory
size (json
-int
)
2513 - "mem_type_64": true or
false (json
-bool
)
2514 - "prefetch": true or
false (json
-bool
)
2518 -> { "execute": "query-pci" }
2530 "desc":"Host bridge"
2564 "desc":"IDE controller"
2586 "desc":"VGA controller"
2596 "mem_type_64":false,
2599 "address":4026531840,
2604 "mem_type_64":false,
2607 "address":4060086272,
2612 "mem_type_64":false,
2627 "desc":"RAM controller"
2648 Note
: This example has been shortened as the real response is too long
.
2653 .name
= "query-pci",
2655 .mhandler
.cmd_new
= qmp_marshal_input_query_pci
,
2662 Show KVM information
.
2664 Return a json
-object with the following information
:
2666 - "enabled": true if KVM support is enabled
, false otherwise (json
-bool
)
2667 - "present": true if QEMU has KVM support
, false otherwise (json
-bool
)
2671 -> { "execute": "query-kvm" }
2672 <- { "return": { "enabled": true, "present": true } }
2677 .name
= "query-kvm",
2679 .mhandler
.cmd_new
= qmp_marshal_input_query_kvm
,
2686 Return a json
-object with the following information
:
2688 - "running": true if the VM is running
, or
false if it is
paused (json
-bool
)
2689 - "singlestep": true if the VM is
in single step mode
,
2690 false otherwise (json
-bool
)
2691 - "status": one of the following
values (json
-string
)
2692 "debug" - QEMU is running on a debugger
2693 "inmigrate" - guest is paused waiting
for an incoming migration
2694 "internal-error" - An internal error that prevents further guest
2695 execution has occurred
2696 "io-error" - the last IOP has failed and the device is configured
2697 to pause on I
/O errors
2698 "paused" - guest has been paused via the
'stop' command
2699 "postmigrate" - guest is paused following a successful
'migrate'
2700 "prelaunch" - QEMU was started with
-S and guest has not started
2701 "finish-migrate" - guest is paused to finish the migration process
2702 "restore-vm" - guest is paused to restore VM state
2703 "running" - guest is actively running
2704 "save-vm" - guest is paused to save the VM state
2705 "shutdown" - guest is shut
down (and
-no
-shutdown is
in use
)
2706 "watchdog" - the watchdog action is configured to pause and
2711 -> { "execute": "query-status" }
2712 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
2717 .name
= "query-status",
2719 .mhandler
.cmd_new
= qmp_marshal_input_query_status
,
2726 Show VM mice information
.
2728 Each mouse is represented by a json
-object
, the returned value is a json
-array
2731 The mouse json
-object contains the following
:
2733 - "name": mouse
's name (json-string)
2734 - "index": mouse's
index (json
-int
)
2735 - "current": true if this mouse is receiving events
, false otherwise (json
-bool
)
2736 - "absolute": true if the mouse generates absolute input
events (json
-bool
)
2740 -> { "execute": "query-mice" }
2744 "name":"QEMU Microsoft Mouse",
2750 "name":"QEMU PS/2 Mouse",
2761 .name
= "query-mice",
2763 .mhandler
.cmd_new
= qmp_marshal_input_query_mice
,
2770 Show VNC server information
.
2772 Return a json
-object with server information
. Connected clients are returned
2773 as a json
-array of json
-objects
.
2775 The main json
-object contains the following
:
2777 - "enabled": true or
false (json
-bool
)
2778 - "host": server
's IP address (json-string)
2779 - "family": address family (json-string)
2780 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2781 - "service": server's port
number (json
-string
)
2782 - "auth": authentication
method (json
-string
)
2783 - Possible values
: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
2784 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
2785 "vencrypt+plain", "vencrypt+tls+none",
2786 "vencrypt+tls+plain", "vencrypt+tls+sasl",
2787 "vencrypt+tls+vnc", "vencrypt+x509+none",
2788 "vencrypt+x509+plain", "vencrypt+x509+sasl",
2789 "vencrypt+x509+vnc", "vnc"
2790 - "clients": a json
-array of all connected clients
2792 Clients are described by a json
-object
, each one contain the following
:
2794 - "host": client
's IP address (json-string)
2795 - "family": address family (json-string)
2796 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2797 - "service": client's port
number (json
-string
)
2798 - "x509_dname": TLS
dname (json
-string
, optional
)
2799 - "sasl_username": SASL
username (json
-string
, optional
)
2803 -> { "execute": "query-vnc" }
2824 .name
= "query-vnc",
2826 .mhandler
.cmd_new
= qmp_marshal_input_query_vnc
,
2833 Show SPICE server information
.
2835 Return a json
-object with server information
. Connected clients are returned
2836 as a json
-array of json
-objects
.
2838 The main json
-object contains the following
:
2840 - "enabled": true or
false (json
-bool
)
2841 - "host": server
's IP address (json-string)
2842 - "port": server's port
number (json
-int
, optional
)
2843 - "tls-port": server
's port number (json-int, optional)
2844 - "auth": authentication method (json-string)
2845 - Possible values: "none", "spice"
2846 - "channels": a json-array of all active channels clients
2848 Channels are described by a json-object, each one contain the following:
2850 - "host": client's IP
address (json
-string
)
2851 - "family": address
family (json
-string
)
2852 - Possible values
: "ipv4", "ipv6", "unix", "unknown"
2853 - "port": client
's port number (json-string)
2854 - "connection-id": spice connection id. All channels with the same id
2855 belong to the same spice session (json-int)
2856 - "channel-type": channel type. "1" is the main control channel, filter for
2857 this one if you want track spice sessions only (json-int)
2858 - "channel-id": channel id. Usually "0", might be different needed when
2859 multiple channels of the same type exist, such as multiple
2860 display channels in a multihead setup (json-int)
2861 - "tls": whevener the channel is encrypted (json-bool)
2865 -> { "execute": "query-spice" }
2878 "connection-id": 1804289383,
2879 "host": "127.0.0.1",
2887 "connection-id": 1804289383,
2888 "host": "127.0.0.1",
2892 [ ... more channels follow ... ]
2899 #if defined(CONFIG_SPICE)
2901 .name = "query-spice",
2903 .mhandler.cmd_new = qmp_marshal_input_query_spice,
2913 Return a json-object with the following information:
2915 - "name": VM's
name (json
-string
, optional
)
2919 -> { "execute": "query-name" }
2920 <- { "return": { "name": "qemu-name" } }
2925 .name
= "query-name",
2927 .mhandler
.cmd_new
= qmp_marshal_input_query_name
,
2936 Return a json
-object with the following information
:
2938 - "UUID": Universally Unique
Identifier (json
-string
)
2942 -> { "execute": "query-uuid" }
2943 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
2948 .name
= "query-uuid",
2950 .mhandler
.cmd_new
= qmp_marshal_input_query_uuid
,
2954 query
-command
-line
-options
2955 --------------------------
2957 Show command line option schema
.
2959 Return a json
-array of command line option schema
for all
options (or
for
2960 the given option
), returning an error
if the given option doesn
't exist.
2962 Each array entry contains the following:
2964 - "option": option name (json-string)
2965 - "parameters": a json-array describes all parameters of the option:
2966 - "name": parameter name (json-string)
2967 - "type": parameter type (one of 'string
', 'boolean
', 'number
',
2969 - "help": human readable description of the parameter
2970 (json-string, optional)
2971 - "default": default value string for the parameter
2972 (json-string, optional)
2976 -> { "execute": "query-command-line-options", "arguments": { "option": "option-rom" } }
2985 "name": "bootindex",
2989 "option": "option-rom"
2997 .name = "query-command-line-options",
2998 .args_type = "option:s?",
2999 .mhandler.cmd_new = qmp_marshal_input_query_command_line_options,
3008 Return a json-object. If migration is active there will be another json-object
3009 with RAM migration status and if block migration is active another one with
3010 block migration status.
3012 The main json-object contains the following:
3014 - "status": migration status (json-string)
3015 - Possible values: "setup", "active", "completed", "failed", "cancelled"
3016 - "total-time": total amount of ms since migration started. If
3017 migration has ended, it returns the total migration
3019 - "setup-time" amount of setup time in milliseconds _before_ the
3020 iterations begin but _after_ the QMP command is issued.
3021 This is designed to provide an accounting of any activities
3022 (such as RDMA pinning) which may be expensive, but do not
3023 actually occur during the iterative migration rounds
3024 themselves. (json-int)
3025 - "downtime": only present when migration has finished correctly
3026 total amount in ms for downtime that happened (json-int)
3027 - "expected-downtime": only present while migration is active
3028 total amount in ms for downtime that was calculated on
3029 the last bitmap round (json-int)
3030 - "ram": only present if "status" is "active", it is a json-object with the
3031 following RAM information:
3032 - "transferred": amount transferred in bytes (json-int)
3033 - "remaining": amount remaining to transfer in bytes (json-int)
3034 - "total": total amount of memory in bytes (json-int)
3035 - "duplicate": number of pages filled entirely with the same
3037 These are sent over the wire much more efficiently.
3038 - "skipped": number of skipped zero pages (json-int)
3039 - "normal" : number of whole pages transferred. I.e. they
3040 were not sent as duplicate or xbzrle pages (json-int)
3041 - "normal-bytes" : number of bytes transferred in whole
3042 pages. This is just normal pages times size of one page,
3043 but this way upper levels don't need to care about page
3045 - "dirty-sync-count": times that dirty ram was
synchronized (json
-int
)
3046 - "disk": only present
if "status" is
"active" and it is a block migration
,
3047 it is a json
-object with the following disk information
:
3048 - "transferred": amount transferred
in bytes (json
-int
)
3049 - "remaining": amount remaining to transfer
in bytes json
-int
)
3050 - "total": total disk size
in bytes (json
-int
)
3051 - "xbzrle-cache": only present
if XBZRLE is active
.
3052 It is a json
-object with the following XBZRLE information
:
3053 - "cache-size": XBZRLE cache size
in bytes
3054 - "bytes": number of bytes transferred
for XBZRLE compressed pages
3055 - "pages": number of XBZRLE compressed pages
3056 - "cache-miss": number of XBRZRLE page cache misses
3057 - "cache-miss-rate": rate of XBRZRLE page cache misses
3058 - "overflow": number of times XBZRLE overflows
. This means
3059 that the XBZRLE encoding was bigger than just sent the
3060 whole page
, and then we sent the whole page
instead (as as
3065 1. Before the first migration
3067 -> { "execute": "query-migrate" }
3070 2. Migration is done and has succeeded
3072 -> { "execute": "query-migrate" }
3074 "status": "completed",
3084 "normal-bytes":123456,
3085 "dirty-sync-count":15
3090 3. Migration is done and has failed
3092 -> { "execute": "query-migrate" }
3093 <- { "return": { "status": "failed" } }
3095 4. Migration is being performed and is not a block migration
:
3097 -> { "execute": "query-migrate" }
3107 "expected-downtime":12345,
3110 "normal-bytes":123456,
3111 "dirty-sync-count":15
3116 5. Migration is being performed and is a block migration
:
3118 -> { "execute": "query-migrate" }
3124 "remaining":1053304,
3128 "expected-downtime":12345,
3131 "normal-bytes":123456,
3132 "dirty-sync-count":15
3136 "remaining":20880384,
3142 6. Migration is being performed and XBZRLE is active
:
3144 -> { "execute": "query-migrate" }
3148 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
3151 "remaining":1053304,
3155 "expected-downtime":12345,
3158 "normal-bytes":3412992,
3159 "dirty-sync-count":15
3162 "cache-size":67108864,
3166 "cache-miss-rate":0.123,
3175 .name
= "query-migrate",
3177 .mhandler
.cmd_new
= qmp_marshal_input_query_migrate
,
3181 migrate
-set
-capabilities
3182 ------------------------
3184 Enable
/Disable migration capabilities
3186 - "xbzrle": XBZRLE support
3192 -> { "execute": "migrate-set-capabilities" , "arguments":
3193 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
3198 .name
= "migrate-set-capabilities",
3199 .args_type
= "capabilities:O",
3200 .params
= "capability:s,state:b",
3201 .mhandler
.cmd_new
= qmp_marshal_input_migrate_set_capabilities
,
3204 query
-migrate
-capabilities
3205 --------------------------
3207 Query current migration capabilities
3209 - "capabilities": migration capabilities state
3210 - "xbzrle" : XBZRLE
state (json
-bool
)
3216 -> { "execute": "query-migrate-capabilities" }
3217 <- { "return": [ { "state": false, "capability": "xbzrle" } ] }
3222 .name
= "query-migrate-capabilities",
3224 .mhandler
.cmd_new
= qmp_marshal_input_query_migrate_capabilities
,
3231 Show balloon information
.
3233 Make an asynchronous request
for balloon info
. When the request completes a
3234 json
-object will be returned containing the following data
:
3236 - "actual": current balloon value
in bytes (json
-int
)
3240 -> { "execute": "query-balloon" }
3243 "actual":1073741824,
3250 .name
= "query-balloon",
3252 .mhandler
.cmd_new
= qmp_marshal_input_query_balloon
,
3256 .name
= "query-block-jobs",
3258 .mhandler
.cmd_new
= qmp_marshal_input_query_block_jobs
,
3263 .args_type
= "path:s",
3264 .mhandler
.cmd_new
= qmp_marshal_input_qom_list
,
3269 .args_type
= "path:s,property:s,value:q",
3270 .mhandler
.cmd_new
= qmp_qom_set
,
3275 .args_type
= "path:s,property:s",
3276 .mhandler
.cmd_new
= qmp_qom_get
,
3280 .name
= "nbd-server-start",
3281 .args_type
= "addr:q",
3282 .mhandler
.cmd_new
= qmp_marshal_input_nbd_server_start
,
3285 .name
= "nbd-server-add",
3286 .args_type
= "device:B,writable:b?",
3287 .mhandler
.cmd_new
= qmp_marshal_input_nbd_server_add
,
3290 .name
= "nbd-server-stop",
3292 .mhandler
.cmd_new
= qmp_marshal_input_nbd_server_stop
,
3296 .name
= "change-vnc-password",
3297 .args_type
= "password:s",
3298 .mhandler
.cmd_new
= qmp_marshal_input_change_vnc_password
,
3301 .name
= "qom-list-types",
3302 .args_type
= "implements:s?,abstract:b?",
3303 .mhandler
.cmd_new
= qmp_marshal_input_qom_list_types
,
3307 .name
= "device-list-properties",
3308 .args_type
= "typename:s",
3309 .mhandler
.cmd_new
= qmp_marshal_input_device_list_properties
,
3313 .name
= "query-machines",
3315 .mhandler
.cmd_new
= qmp_marshal_input_query_machines
,
3319 .name
= "query-cpu-definitions",
3321 .mhandler
.cmd_new
= qmp_marshal_input_query_cpu_definitions
,
3325 .name
= "query-target",
3327 .mhandler
.cmd_new
= qmp_marshal_input_query_target
,
3331 .name
= "query-tpm",
3333 .mhandler
.cmd_new
= qmp_marshal_input_query_tpm
,
3340 Return information about the TPM device
.
3346 -> { "execute": "query-tpm" }
3349 { "model": "tpm-tis",
3351 { "type": "passthrough",
3353 { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
3365 .name
= "query-tpm-models",
3367 .mhandler
.cmd_new
= qmp_marshal_input_query_tpm_models
,
3374 Return a list of supported TPM models
.
3380 -> { "execute": "query-tpm-models" }
3381 <- { "return": [ "tpm-tis" ] }
3386 .name
= "query-tpm-types",
3388 .mhandler
.cmd_new
= qmp_marshal_input_query_tpm_types
,
3395 Return a list of supported TPM types
.
3401 -> { "execute": "query-tpm-types" }
3402 <- { "return": [ "passthrough" ] }
3407 .name
= "chardev-add",
3408 .args_type
= "id:s,backend:q",
3409 .mhandler
.cmd_new
= qmp_marshal_input_chardev_add
,
3420 - "id": the chardev
's ID, must be unique (json-string)
3421 - "backend": chardev backend type + parameters
3425 -> { "execute" : "chardev-add",
3426 "arguments" : { "id" : "foo",
3427 "backend" : { "type" : "null", "data" : {} } } }
3430 -> { "execute" : "chardev-add",
3431 "arguments" : { "id" : "bar",
3432 "backend" : { "type" : "file",
3433 "data" : { "out" : "/tmp/bar.log" } } } }
3436 -> { "execute" : "chardev-add",
3437 "arguments" : { "id" : "baz",
3438 "backend" : { "type" : "pty", "data" : {} } } }
3439 <- { "return": { "pty" : "/dev/pty/42" } }
3444 .name = "chardev-remove",
3445 .args_type = "id:s",
3446 .mhandler.cmd_new = qmp_marshal_input_chardev_remove,
3458 - "id": the chardev's ID
, must exist and not be
in use (json
-string
)
3462 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }
3467 .name
= "query-rx-filter",
3468 .args_type
= "name:s?",
3469 .mhandler
.cmd_new
= qmp_marshal_input_query_rx_filter
,
3476 Show rx
-filter information
.
3478 Returns a json
-array of rx
-filter information
for all
NICs (or
for the
3479 given NIC
), returning an error
if the given NIC doesn
't exist, or
3480 given NIC doesn't support rx
-filter querying
, or given net client
3483 The query will clear the event notification flag of each NIC, then qemu
3484 will start to emit event to QMP monitor.
3486 Each array entry contains the following:
3488 - "name": net client name (json-string)
3489 - "promiscuous": promiscuous mode is enabled (json-bool)
3490 - "multicast": multicast receive state (one of 'normal
', 'none
', 'all
')
3491 - "unicast": unicast receive state (one of 'normal
', 'none
', 'all
')
3492 - "vlan": vlan receive state (one of 'normal
', 'none
', 'all
') (Since 2.0)
3493 - "broadcast-allowed": allow to receive broadcast (json-bool)
3494 - "multicast-overflow": multicast table is overflowed (json-bool)
3495 - "unicast-overflow": unicast table is overflowed (json-bool)
3496 - "main-mac": main macaddr string (json-string)
3497 - "vlan-table": a json-array of active vlan id
3498 - "unicast-table": a json-array of unicast macaddr string
3499 - "multicast-table": a json-array of multicast macaddr string
3503 -> { "execute": "query-rx-filter", "arguments": { "name": "vnet0" } }
3506 "promiscuous": true,
3508 "main-mac": "52:54:00:12:34:56",
3509 "unicast": "normal",
3517 "multicast": "normal",
3518 "multicast-overflow": false,
3519 "unicast-overflow": false,
3520 "multicast-table": [
3521 "01:00:5e:00:00:01",
3522 "33:33:00:00:00:01",
3525 "broadcast-allowed": false
3533 .name = "blockdev-add",
3534 .args_type = "options:q",
3535 .mhandler.cmd_new = qmp_marshal_input_blockdev_add,
3546 - "options": block driver options
3550 -> { "execute": "blockdev-add",
3551 "arguments": { "options" : { "driver": "qcow2",
3552 "file": { "driver": "file",
3553 "filename": "test.qcow2" } } } }
3558 -> { "execute": "blockdev-add",
3570 "filename": "/tmp/test.qcow2"
3576 "filename": "/dev/fdset/4"
3588 .name = "query-named-block-nodes",
3590 .mhandler.cmd_new = qmp_marshal_input_query_named_block_nodes,
3594 @query-named-block-nodes
3595 ------------------------
3597 Return a list of BlockDeviceInfo for all the named block driver nodes
3601 -> { "execute": "query-named-block-nodes" }
3602 <- { "return": [ { "ro":false,
3605 "file":"disks/test.qcow2",
3606 "node-name": "my-node",
3607 "backing_file_depth":1,
3622 "filename":"disks/test.qcow2",
3624 "virtual-size":2048000,
3625 "backing_file":"base.qcow2",
3626 "full-backing-filename":"disks/base.qcow2",
3627 "backing-filename-format:"qcow2",
3631 "name": "snapshot1",
3633 "date-sec": 10000200,
3635 "vm-clock-sec": 206,
3640 "filename":"disks/base.qcow2",
3642 "virtual-size":2048000
3649 .name = "query-memdev",
3651 .mhandler.cmd_new = qmp_marshal_input_query_memdev,
3658 Show memory devices information.
3663 -> { "execute": "query-memdev" }
3670 "host-nodes": [0, 1],
3678 "host-nodes": [2, 3],
3679 "policy": "preferred"
3687 .name = "query-memory-devices",
3689 .mhandler.cmd_new = qmp_marshal_input_query_memory_devices,
3693 @query-memory-devices
3694 --------------------
3696 Return a list of memory devices.
3699 -> { "execute": "query-memory-devices" }
3700 <- { "return": [ { "data":
3701 { "addr": 5368709120,
3702 "hotpluggable": true,
3705 "memdev": "/objects/memX",
3714 .name = "query-acpi-ospm-status",
3716 .mhandler.cmd_new = qmp_marshal_input_query_acpi_ospm_status,
3720 @query-acpi-ospm-status
3721 --------------------
3723 Return list of ACPIOSTInfo for devices that support status reporting
3724 via ACPI _OST method.
3727 -> { "execute": "query-acpi-ospm-status" }
3728 <- { "return": [ { "device": "d1", "slot": "0", "slot-type": "DIMM", "source": 1, "status": 0},
3729 { "slot": "1", "slot-type": "DIMM", "source": 0, "status": 0},
3730 { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
3731 { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
3735 #if defined TARGET_I386
3737 .name = "rtc-reset-reinjection",
3739 .mhandler.cmd_new = qmp_marshal_input_rtc_reset_reinjection,
3744 rtc-reset-reinjection
3745 ---------------------
3747 Reset the RTC interrupt reinjection backlog.
3753 -> { "execute": "rtc-reset-reinjection" }
3758 .name = "trace-event-get-state",
3759 .args_type = "name:s",
3760 .mhandler.cmd_new = qmp_marshal_input_trace_event_get_state,
3764 trace-event-get-state
3765 ---------------------
3767 Query the state of events.
3771 -> { "execute": "trace-event-get-state", "arguments": { "name": "qemu_memalign" } }
3772 <- { "return": [ { "name": "qemu_memalign", "state": "disabled" } ] }
3776 .name = "trace-event-set-state",
3777 .args_type = "name:s,enable:b,ignore-unavailable:b?",
3778 .mhandler.cmd_new = qmp_marshal_input_trace_event_set_state,
3782 trace-event-set-state
3783 ---------------------
3785 Set the state of events.
3789 -> { "execute": "trace-event-set-state", "arguments": { "name": "qemu_memalign", "enable": "true" } }
3794 .name = "x-input-send-event",
3795 .args_type = "console:i?,events:q",
3796 .mhandler.cmd_new = qmp_marshal_input_x_input_send_event,
3803 Send input event to guest.
3807 - "console": console index. (json-int, optional)
3808 - "events": list of input events.
3810 The consoles are visible in the qom tree, under
3811 /backend/console[$index]. They have a device link and head property, so
3812 it is possible to map which console belongs to which device and display.
3814 Note: this command is experimental, and not a stable API.
3818 Press left mouse button.
3820 -> { "execute": "x-input-send-event",
3821 "arguments": { "console": 0,
3822 "events": [ { "type": "btn",
3823 "data" : { "down": true, "button": "Left" } } } }
3826 -> { "execute": "x-input-send-event",
3827 "arguments": { "console": 0,
3828 "events": [ { "type": "btn",
3829 "data" : { "down": false, "button": "Left" } } } }
3836 -> { "execute": "x-input-send-event",
3837 "arguments": { "console": 0, "events": [
3838 { "type": "key", "data" : { "down": true,
3839 "key": {"type": "qcode", "data": "ctrl" } } },
3840 { "type": "key", "data" : { "down": true,
3841 "key": {"type": "qcode", "data": "alt" } } },
3842 { "type": "key", "data" : { "down": true,
3843 "key": {"type": "qcode", "data": "delete" } } } ] } }
3848 Move mouse pointer to absolute coordinates (20000, 400).
3850 -> { "execute": "x-input-send-event" ,
3851 "arguments": { "console": 0, "events": [
3852 { "type": "abs", "data" : { "axis": "X", "value" : 20000 } },
3853 { "type": "abs", "data" : { "axis": "Y", "value" : 400 } } ] } }