1 HXCOMM QMP dispatch table and documentation
2 HXCOMM Text between SQMP and EQMP is copied to the QMP documentation 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_quit
,
79 -> { "execute": "quit" }
86 .args_type
= "force:-f,device:B",
87 .mhandler
.cmd_new
= qmp_marshal_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_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_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_stop
,
185 -> { "execute": "stop" }
193 .mhandler
.cmd_new
= qmp_marshal_cont
,
206 -> { "execute": "cont" }
212 .name
= "system_wakeup",
214 .mhandler
.cmd_new
= qmp_marshal_system_wakeup
,
221 Wakeup guest from suspend
.
227 -> { "execute": "system_wakeup" }
233 .name
= "system_reset",
235 .mhandler
.cmd_new
= qmp_marshal_system_reset
,
248 -> { "execute": "system_reset" }
254 .name
= "system_powerdown",
256 .mhandler
.cmd_new
= qmp_marshal_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 .mhandler
.cmd_new
= qmp_device_add
,
290 - "driver": the name of the
new device
's driver (json-string)
291 - "bus": the device's parent
bus (device tree path
, json
-string
, optional
)
292 - "id": the device
's ID, must be unique (json-string)
297 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
302 (1) For detailed information about this command, please refer to the
303 'docs
/qdev
-device
-use
.txt
' file.
305 (2) It's possible to list device properties by running QEMU with the
306 "-device DEVICE,\?" command
-line argument
, where DEVICE is the device
's name
311 .name = "device_del",
313 .mhandler.cmd_new = qmp_marshal_device_del,
324 - "id": the device's ID or QOM
path (json
-string
)
328 -> { "execute": "device_del", "arguments": { "id": "net1" } }
333 -> { "execute": "device_del", "arguments": { "id": "/machine/peripheral-anon/device[0]" } }
340 .args_type
= "keys:q,hold-time:i?",
341 .mhandler
.cmd_new
= qmp_marshal_send_key
,
353 - "key": key
sequence (a json
-array of key union values
,
354 union can be number or qcode
enum)
356 - hold
-time
: time to delay key up events
, milliseconds
. Defaults to
100
361 -> { "execute": "send-key",
362 "arguments": { "keys": [ { "type": "qcode", "data": "ctrl" },
363 { "type": "qcode", "data": "alt" },
364 { "type": "qcode", "data": "delete" } ] } }
371 .args_type
= "index:i",
372 .mhandler
.cmd_new
= qmp_marshal_cpu
,
383 - "index": the CPU
's index (json-int)
387 -> { "execute": "cpu", "arguments": { "index": 0 } }
390 Note: CPUs' indexes are obtained with the
'query-cpus' command
.
397 .mhandler
.cmd_new
= qmp_marshal_cpu_add
,
408 - "id": cpu
id (json
-int
)
412 -> { "execute": "cpu-add", "arguments": { "id": 2 } }
419 .args_type
= "val:l,size:i,filename:s,cpu:i?",
420 .mhandler
.cmd_new
= qmp_marshal_memsave
,
427 Save to disk virtual memory dump starting at
'val' of size
'size'.
431 - "val": the starting
address (json
-int
)
432 - "size": the memory size
, in bytes (json
-int
)
433 - "filename": file
path (json
-string
)
434 - "cpu": virtual CPU
index (json
-int
, optional
)
438 -> { "execute": "memsave",
439 "arguments": { "val": 10,
441 "filename": "/tmp/virtual-mem-dump" } }
448 .args_type
= "val:l,size:i,filename:s",
449 .mhandler
.cmd_new
= qmp_marshal_pmemsave
,
456 Save to disk physical memory dump starting at
'val' of size
'size'.
460 - "val": the starting
address (json
-int
)
461 - "size": the memory size
, in bytes (json
-int
)
462 - "filename": file
path (json
-string
)
466 -> { "execute": "pmemsave",
467 "arguments": { "val": 10,
469 "filename": "/tmp/physical-mem-dump" } }
475 .name
= "inject-nmi",
477 .mhandler
.cmd_new
= qmp_marshal_inject_nmi
,
484 Inject an NMI on the
default CPU (x86
/s390
) or all
CPUs (ppc64
).
490 -> { "execute": "inject-nmi" }
493 Note
: inject
-nmi fails when the guest doesn
't support injecting.
498 .name = "ringbuf-write",
499 .args_type = "device:s,data:s,format:s?",
500 .mhandler.cmd_new = qmp_marshal_ringbuf_write,
507 Write to a ring buffer character device.
511 - "device": ring buffer character device name (json-string)
512 - "data": data to write (json-string)
513 - "format": data format (json-string, optional)
514 - Possible values: "utf8" (default), "base64"
518 -> { "execute": "ringbuf-write",
519 "arguments": { "device": "foo",
527 .name = "ringbuf-read",
528 .args_type = "device:s,size:i,format:s?",
529 .mhandler.cmd_new = qmp_marshal_ringbuf_read,
536 Read from a ring buffer character device.
540 - "device": ring buffer character device name (json-string)
541 - "size": how many bytes to read at most (json-int)
542 - Number of data bytes, not number of characters in encoded data
543 - "format": data format (json-string, optional)
544 - Possible values: "utf8" (default), "base64"
545 - Naturally, format "utf8" works only when the ring buffer
546 contains valid UTF-8 text. Invalid UTF-8 sequences get
547 replaced. Bug: replacement doesn't work
. Bug
: can screw
548 up on encountering NUL characters
, after the ring buffer
549 lost data
, and when reading stops because the size limit
554 -> { "execute": "ringbuf-read",
555 "arguments": { "device": "foo",
558 <- {"return": "abcdefgh"}
563 .name
= "xen-save-devices-state",
564 .args_type
= "filename:F",
565 .mhandler
.cmd_new
= qmp_marshal_xen_save_devices_state
,
569 xen
-save
-devices
-state
572 Save the state of all devices to file
. The RAM and the block devices
573 of the VM are not saved by
this command
.
577 - "filename": the file to save the state of the devices to as binary
578 data
. See xen
-save
-devices
-state
.txt
for a description of the binary
583 -> { "execute": "xen-save-devices-state",
584 "arguments": { "filename": "/tmp/save" } }
590 .name
= "xen-set-global-dirty-log",
591 .args_type
= "enable:b",
592 .mhandler
.cmd_new
= qmp_marshal_xen_set_global_dirty_log
,
596 xen
-set
-global
-dirty
-log
599 Enable or disable the global dirty log mode
.
603 - "enable": Enable it or disable it
.
607 -> { "execute": "xen-set-global-dirty-log",
608 "arguments": { "enable": true } }
615 .args_type
= "detach:-d,blk:-b,inc:-i,uri:s",
616 .mhandler
.cmd_new
= qmp_marshal_migrate
,
627 - "blk": block migration
, full disk
copy (json
-bool
, optional
)
628 - "inc": incremental disk
copy (json
-bool
, optional
)
629 - "uri": Destination
URI (json
-string
)
633 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
638 (1) The
'query-migrate' command should be used to check migration
's progress
639 and final result (this information is provided by the 'status
' member)
640 (2) All boolean arguments default to false
641 (3) The user Monitor's
"detach" argument is invalid
in QMP and should not
647 .name
= "migrate_cancel",
649 .mhandler
.cmd_new
= qmp_marshal_migrate_cancel
,
656 Cancel the current migration
.
662 -> { "execute": "migrate_cancel" }
668 .name
= "migrate-incoming",
669 .args_type
= "uri:s",
670 .mhandler
.cmd_new
= qmp_marshal_migrate_incoming
,
677 Continue an incoming migration
681 - "uri": Source
/listening
URI (json
-string
)
685 -> { "execute": "migrate-incoming", "arguments": { "uri": "tcp::4446" } }
690 (1) QEMU must be started with
-incoming defer to allow migrate
-incoming to
692 (2) The uri format is the same as
for -incoming
696 .name
= "migrate-set-cache-size",
697 .args_type
= "value:o",
698 .mhandler
.cmd_new
= qmp_marshal_migrate_set_cache_size
,
702 migrate
-set
-cache
-size
703 ----------------------
705 Set cache size to be used by XBZRLE migration
, the cache size will be rounded
706 down to the nearest power of
2
710 - "value": cache size
in bytes (json
-int
)
714 -> { "execute": "migrate-set-cache-size", "arguments": { "value": 536870912 } }
719 .name
= "migrate-start-postcopy",
721 .mhandler
.cmd_new
= qmp_marshal_migrate_start_postcopy
,
725 migrate
-start
-postcopy
726 ----------------------
728 Switch an
in-progress migration to postcopy mode
. Ignored after the end of
729 migration (or once already
in postcopy
).
732 -> { "execute": "migrate-start-postcopy" }
738 .name
= "query-migrate-cache-size",
740 .mhandler
.cmd_new
= qmp_marshal_query_migrate_cache_size
,
744 query
-migrate
-cache
-size
745 ------------------------
747 Show cache size to be used by XBZRLE migration
749 returns a json
-object with the following information
:
754 -> { "execute": "query-migrate-cache-size" }
755 <- { "return": 67108864 }
760 .name
= "migrate_set_speed",
761 .args_type
= "value:o",
762 .mhandler
.cmd_new
= qmp_marshal_migrate_set_speed
,
769 Set maximum speed
for migrations
.
773 - "value": maximum speed
, in bytes per
second (json
-int
)
777 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
783 .name
= "migrate_set_downtime",
784 .args_type
= "value:T",
785 .mhandler
.cmd_new
= qmp_marshal_migrate_set_downtime
,
792 Set maximum tolerated
downtime (in seconds
) for migrations
.
796 - "value": maximum
downtime (json
-number
)
800 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
806 .name
= "client_migrate_info",
807 .args_type
= "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
808 .params
= "protocol hostname port tls-port cert-subject",
809 .help
= "set migration information for remote display",
810 .mhandler
.cmd_new
= qmp_marshal_client_migrate_info
,
817 Set migration information
for remote display
. This makes the server
818 ask the client to automatically reconnect
using the
new parameters
819 once migration finished successfully
. Only implemented
for SPICE
.
823 - "protocol": must be
"spice" (json
-string
)
824 - "hostname": migration target
hostname (json
-string
)
825 - "port": spice tcp port
for plaintext
channels (json
-int
, optional
)
826 - "tls-port": spice tcp port
for tls
-secured
channels (json
-int
, optional
)
827 - "cert-subject": server certificate
subject (json
-string
, optional
)
831 -> { "execute": "client_migrate_info",
832 "arguments": { "protocol": "spice",
833 "hostname": "virt42.lab.kraxel.org",
840 .name
= "dump-guest-memory",
841 .args_type
= "paging:b,protocol:s,begin:i?,end:i?,format:s?",
842 .params
= "-p protocol [begin] [length] [format]",
843 .help
= "dump guest memory to file",
844 .mhandler
.cmd_new
= qmp_marshal_dump_guest_memory
,
851 Dump guest memory to file
. The file can be processed with crash or gdb
.
855 - "paging": do paging to get guest
's memory mapping (json-bool)
856 - "protocol": destination file(started with "file:") or destination file
857 descriptor (started with "fd:") (json-string)
858 - "begin": the starting physical address. It's optional
, and should be specified
859 with length
together (json
-int
)
860 - "length": the memory size
, in bytes
. It
's optional, and should be specified
861 with begin together (json-int)
862 - "format": the format of guest memory dump. It's optional
, and can be
863 elf|kdump
-zlib|kdump
-lzo|kdump
-snappy
, but non
-elf formats will
864 conflict with paging and filter
, ie
. begin and
length (json
-string
)
868 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
873 (1) All boolean arguments
default to
false
878 .name
= "query-dump-guest-memory-capability",
880 .mhandler
.cmd_new
= qmp_marshal_query_dump_guest_memory_capability
,
884 query
-dump
-guest
-memory
-capability
887 Show available formats
for 'dump-guest-memory'
891 -> { "execute": "query-dump-guest-memory-capability" }
892 <- { "return": { "formats":
893 ["elf", "kdump-zlib", "kdump-lzo", "kdump-snappy"] }
897 #
if defined TARGET_S390X
899 .name
= "dump-skeys",
900 .args_type
= "filename:F",
901 .mhandler
.cmd_new
= qmp_marshal_dump_skeys
,
909 Save guest storage keys to file
.
913 - "filename": file
path (json
-string
)
917 -> { "execute": "dump-skeys", "arguments": { "filename": "/tmp/skeys" } }
923 .name
= "netdev_add",
924 .args_type
= "netdev:O",
925 .mhandler
.cmd_new
= qmp_netdev_add
,
932 Add host network device
.
936 - "type": the device type
, "tap", "user", ... (json
-string
)
937 - "id": the device
's ID, must be unique (json-string)
942 -> { "execute": "netdev_add",
943 "arguments": { "type": "user", "id": "netdev1",
944 "dnssearch": "example.org" } }
947 Note: The supported device options are the same ones supported by the '-netdev
'
948 command-line argument, which are listed in the '-help
' output or QEMU's
954 .name
= "netdev_del",
956 .mhandler
.cmd_new
= qmp_marshal_netdev_del
,
963 Remove host network device
.
967 - "id": the device
's ID, must be unique (json-string)
971 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
978 .name = "object-add",
979 .args_type = "qom-type:s,id:s,props:q?",
980 .mhandler.cmd_new = qmp_marshal_object_add,
991 - "qom-type": the object's QOM type
, i
.e
. the
class name (json
-string
)
992 - "id": the object
's ID, must be unique (json-string)
993 - "props": a dictionary of object property values (optional, json-dict)
997 -> { "execute": "object-add", "arguments": { "qom-type": "rng-random", "id": "rng1",
998 "props": { "filename": "/dev/hwrng" } } }
1004 .name = "object-del",
1005 .args_type = "id:s",
1006 .mhandler.cmd_new = qmp_marshal_object_del,
1017 - "id": the object's
ID (json
-string
)
1021 -> { "execute": "object-del", "arguments": { "id": "rng1" } }
1029 .name
= "block_resize",
1030 .args_type
= "device:s?,node-name:s?,size:o",
1031 .mhandler
.cmd_new
= qmp_marshal_block_resize
,
1038 Resize a block image
while a guest is running
.
1042 - "device": the device
's ID, must be unique (json-string)
1043 - "node-name": the node name in the block driver state graph (json-string)
1048 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
1054 .name = "block-stream",
1055 .args_type = "device:B,base:s?,speed:o?,backing-file:s?,on-error:s?",
1056 .mhandler.cmd_new = qmp_marshal_block_stream,
1063 Copy data from a backing file into a block device.
1067 - "device": The device's ID
, must be
unique (json
-string
)
1068 - "base": The file name of the backing image above which copying starts
1069 (json
-string
, optional
)
1070 - "backing-file": The backing file string to write into the active layer
. This
1071 filename is not validated
.
1073 If a pathname string is such that it cannot be resolved by
1074 QEMU
, that means that subsequent QMP or HMP commands must use
1075 node
-names
for the image
in question
, as filename lookup
1078 If not specified
, QEMU will automatically determine the
1079 backing file string to use
, or error out
if there is no
1080 obvious choice
. Care should be taken when specifying the
1081 string
, to specify a valid filename or protocol
.
1082 (json
-string
, optional
) (Since
2.1)
1083 - "speed": the maximum speed
, in bytes per
second (json
-int
, optional
)
1084 - "on-error": the action to take on an
error (default 'report'). 'stop' and
1085 'enospc' can only be used
if the block device supports io
-status
.
1086 (json
-string
, optional
) (Since
2.1)
1090 -> { "execute": "block-stream", "arguments": { "device": "virtio0",
1091 "base": "/tmp/master.qcow2" } }
1097 .name
= "block-commit",
1098 .args_type
= "device:B,base:s?,top:s?,backing-file:s?,speed:o?",
1099 .mhandler
.cmd_new
= qmp_marshal_block_commit
,
1106 Live commit of data from overlay image nodes into backing nodes
- i
.e
., writes
1107 data between
'top' and
'base' into
'base'.
1111 - "device": The device
's ID, must be unique (json-string)
1112 - "base": The file name of the backing image to write data into.
1113 If not specified, this is the deepest backing image
1114 (json-string, optional)
1115 - "top": The file name of the backing image within the image chain,
1116 which contains the topmost data to be committed down. If
1117 not specified, this is the active layer. (json-string, optional)
1119 - backing-file: The backing file string to write into the overlay
1120 image of 'top
'. If 'top
' is the active layer,
1121 specifying a backing file string is an error. This
1122 filename is not validated.
1124 If a pathname string is such that it cannot be
1125 resolved by QEMU, that means that subsequent QMP or
1126 HMP commands must use node-names for the image in
1127 question, as filename lookup methods will fail.
1129 If not specified, QEMU will automatically determine
1130 the backing file string to use, or error out if
1131 there is no obvious choice. Care should be taken
1132 when specifying the string, to specify a valid
1133 filename or protocol.
1134 (json-string, optional) (Since 2.1)
1136 If top == base, that is an error.
1137 If top == active, the job will not be completed by itself,
1138 user needs to complete the job with the block-job-complete
1139 command after getting the ready event. (Since 2.0)
1141 If the base image is smaller than top, then the base image
1142 will be resized to be the same size as top. If top is
1143 smaller than the base image, the base will not be
1144 truncated. If you want the base image size to match the
1145 size of the smaller top, you can safely truncate it
1146 yourself once the commit operation successfully completes.
1148 - "speed": the maximum speed, in bytes per second (json-int, optional)
1153 -> { "execute": "block-commit", "arguments": { "device": "virtio0",
1154 "top": "/tmp/snap1.qcow2" } }
1160 .name = "drive-backup",
1161 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1162 "bitmap:s?,on-source-error:s?,on-target-error:s?",
1163 .mhandler.cmd_new = qmp_marshal_drive_backup,
1170 Start a point-in-time copy of a block device to a new destination. The
1171 status of ongoing drive-backup operations can be checked with
1172 query-block-jobs where the BlockJobInfo.type field has the value 'backup
'.
1173 The operation can be stopped before it has completed using the
1174 block-job-cancel command.
1178 - "device": the name of the device which should be copied.
1180 - "target": the target of the new image. If the file exists, or if it is a
1181 device, the existing file/device will be used as the new
1182 destination. If it does not exist, a new file will be created.
1184 - "format": the format of the new destination, default is to probe if 'mode
' is
1185 'existing
', else the format of the source
1186 (json-string, optional)
1187 - "sync": what parts of the disk image should be copied to the destination;
1188 possibilities include "full" for all the disk, "top" for only the sectors
1189 allocated in the topmost image, "incremental" for only the dirty sectors in
1190 the bitmap, or "none" to only replicate new I/O (MirrorSyncMode).
1191 - "bitmap": dirty bitmap name for sync==incremental. Must be present if sync
1192 is "incremental", must NOT be present otherwise.
1193 - "mode": whether and how QEMU should create a new image
1194 (NewImageMode, optional, default 'absolute
-paths
')
1195 - "speed": the maximum speed, in bytes per second (json-int, optional)
1196 - "on-source-error": the action to take on an error on the source, default
1197 'report
'. 'stop
' and 'enospc
' can only be used
1198 if the block device supports io-status.
1199 (BlockdevOnError, optional)
1200 - "on-target-error": the action to take on an error on the target, default
1201 'report
' (no limitations, since this applies to
1202 a different block device than device).
1203 (BlockdevOnError, optional)
1206 -> { "execute": "drive-backup", "arguments": { "device": "drive0",
1208 "target": "backup.img" } }
1214 .name = "blockdev-backup",
1215 .args_type = "sync:s,device:B,target:B,speed:i?,"
1216 "on-source-error:s?,on-target-error:s?",
1217 .mhandler.cmd_new = qmp_marshal_blockdev_backup,
1224 The device version of drive-backup: this command takes an existing named device
1229 - "device": the name of the device which should be copied.
1231 - "target": the name of the backup target device. (json-string)
1232 - "sync": what parts of the disk image should be copied to the destination;
1233 possibilities include "full" for all the disk, "top" for only the
1234 sectors allocated in the topmost image, or "none" to only replicate
1235 new I/O (MirrorSyncMode).
1236 - "speed": the maximum speed, in bytes per second (json-int, optional)
1237 - "on-source-error": the action to take on an error on the source, default
1238 'report
'. 'stop
' and 'enospc
' can only be used
1239 if the block device supports io-status.
1240 (BlockdevOnError, optional)
1241 - "on-target-error": the action to take on an error on the target, default
1242 'report
' (no limitations, since this applies to
1243 a different block device than device).
1244 (BlockdevOnError, optional)
1247 -> { "execute": "blockdev-backup", "arguments": { "device": "src-id",
1249 "target": "tgt-id" } }
1255 .name = "block-job-set-speed",
1256 .args_type = "device:B,speed:o",
1257 .mhandler.cmd_new = qmp_marshal_block_job_set_speed,
1261 .name = "block-job-cancel",
1262 .args_type = "device:B,force:b?",
1263 .mhandler.cmd_new = qmp_marshal_block_job_cancel,
1266 .name = "block-job-pause",
1267 .args_type = "device:B",
1268 .mhandler.cmd_new = qmp_marshal_block_job_pause,
1271 .name = "block-job-resume",
1272 .args_type = "device:B",
1273 .mhandler.cmd_new = qmp_marshal_block_job_resume,
1276 .name = "block-job-complete",
1277 .args_type = "device:B",
1278 .mhandler.cmd_new = qmp_marshal_block_job_complete,
1281 .name = "transaction",
1282 .args_type = "actions:q,properties:q?",
1283 .mhandler.cmd_new = qmp_marshal_transaction,
1290 Atomically operate on one or more block devices. Operations that are
1291 currently supported:
1295 - blockdev-snapshot-sync
1296 - blockdev-snapshot-internal-sync
1298 - block-dirty-bitmap-add
1299 - block-dirty-bitmap-clear
1301 Refer to the qemu/qapi-schema.json file for minimum required QEMU
1302 versions for these operations. A list of dictionaries is accepted,
1303 that contains the actions to be performed. If there is any failure
1304 performing any of the operations, all operations for the group are
1307 For external snapshots, the dictionary contains the device, the file to use for
1308 the new snapshot, and the format. The default format, if not specified, is
1311 Each new snapshot defaults to being created by QEMU (wiping any
1312 contents if the file already exists), but it is also possible to reuse
1313 an externally-created file. In the latter case, you should ensure that
1314 the new image file has the same contents as the current one; QEMU cannot
1315 perform any meaningful check. Typically this is achieved by using the
1316 current image file as the backing file for the new image.
1318 On failure, the original disks pre-snapshot attempt will be used.
1320 For internal snapshots, the dictionary contains the device and the snapshot's
1321 name
. If an internal snapshot matching name already exists
, the request will
1322 be rejected
. Only some image formats support it
, for example
, qcow2
, rbd
,
1325 On failure
, qemu will
try delete the newly created internal snapshot
in the
1326 transaction
. When an I
/O error occurs during deletion
, the user needs to fix
1327 it later with qemu
-img or other command
.
1332 - "type": the operation to
perform (json
-string
). Possible
1333 values
: "drive-backup", "blockdev-backup",
1334 "blockdev-snapshot-sync",
1335 "blockdev-snapshot-internal-sync",
1336 "abort", "block-dirty-bitmap-add",
1337 "block-dirty-bitmap-clear"
1338 - "data": a dictionary
. The contents depend on the value
1339 of
"type". When
"type" is
"blockdev-snapshot-sync":
1340 - "device": device name to
snapshot (json
-string
)
1341 - "node-name": graph node name to
snapshot (json
-string
)
1342 - "snapshot-file": name of
new image
file (json
-string
)
1343 - "snapshot-node-name": graph node name of the
new snapshot (json
-string
)
1344 - "format": format of
new image (json
-string
, optional
)
1345 - "mode": whether and how QEMU should create the snapshot file
1346 (NewImageMode
, optional
, default "absolute-paths")
1347 When
"type" is
"blockdev-snapshot-internal-sync":
1348 - "device": device name to
snapshot (json
-string
)
1349 - "name": name of the
new snapshot (json
-string
)
1353 -> { "execute": "transaction",
1354 "arguments": { "actions": [
1355 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd0",
1356 "snapshot-file": "/some/place/my-image",
1357 "format": "qcow2" } },
1358 { "type": "blockdev-snapshot-sync", "data" : { "node-name": "myfile",
1359 "snapshot-file": "/some/place/my-image2",
1360 "snapshot-node-name": "node3432",
1362 "format": "qcow2" } },
1363 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd1",
1364 "snapshot-file": "/some/place/my-image2",
1366 "format": "qcow2" } },
1367 { "type": "blockdev-snapshot-internal-sync", "data" : {
1368 "device": "ide-hd2",
1369 "name": "snapshot0" } } ] } }
1375 .name
= "block-dirty-bitmap-add",
1376 .args_type
= "node:B,name:s,granularity:i?",
1377 .mhandler
.cmd_new
= qmp_marshal_block_dirty_bitmap_add
,
1382 block
-dirty
-bitmap
-add
1383 ----------------------
1386 Create a dirty bitmap with a name on the device
, and start tracking the writes
.
1390 - "node": device
/node on which to create dirty
bitmap (json
-string
)
1391 - "name": name of the
new dirty
bitmap (json
-string
)
1392 - "granularity": granularity to track writes
with (int
, optional
)
1396 -> { "execute": "block-dirty-bitmap-add", "arguments": { "node": "drive0",
1397 "name": "bitmap0" } }
1403 .name
= "block-dirty-bitmap-remove",
1404 .args_type
= "node:B,name:s",
1405 .mhandler
.cmd_new
= qmp_marshal_block_dirty_bitmap_remove
,
1410 block
-dirty
-bitmap
-remove
1411 -------------------------
1414 Stop write tracking and remove the dirty bitmap that was created with
1415 block
-dirty
-bitmap
-add
.
1419 - "node": device
/node on which to remove dirty
bitmap (json
-string
)
1420 - "name": name of the dirty bitmap to
remove (json
-string
)
1424 -> { "execute": "block-dirty-bitmap-remove", "arguments": { "node": "drive0",
1425 "name": "bitmap0" } }
1431 .name
= "block-dirty-bitmap-clear",
1432 .args_type
= "node:B,name:s",
1433 .mhandler
.cmd_new
= qmp_marshal_block_dirty_bitmap_clear
,
1438 block
-dirty
-bitmap
-clear
1439 ------------------------
1442 Reset the dirty bitmap associated with a node so that an incremental backup
1443 from
this point
in time forward will only backup clusters modified after
this
1448 - "node": device
/node on which to remove dirty
bitmap (json
-string
)
1449 - "name": name of the dirty bitmap to
remove (json
-string
)
1453 -> { "execute": "block-dirty-bitmap-clear", "arguments": { "node": "drive0",
1454 "name": "bitmap0" } }
1460 .name
= "blockdev-snapshot-sync",
1461 .args_type
= "device:s?,node-name:s?,snapshot-file:s,snapshot-node-name:s?,format:s?,mode:s?",
1462 .mhandler
.cmd_new
= qmp_marshal_blockdev_snapshot_sync
,
1466 blockdev
-snapshot
-sync
1467 ----------------------
1469 Synchronous snapshot of a block device
. snapshot
-file specifies the
1470 target of the
new image
. If the file exists
, or
if it is a device
, the
1471 snapshot will be created
in the existing file
/device
. If does not
1472 exist
, a
new file will be created
. format specifies the format of the
1473 snapshot image
, default is qcow2
.
1477 - "device": device name to
snapshot (json
-string
)
1478 - "node-name": graph node name to
snapshot (json
-string
)
1479 - "snapshot-file": name of
new image
file (json
-string
)
1480 - "snapshot-node-name": graph node name of the
new snapshot (json
-string
)
1481 - "mode": whether and how QEMU should create the snapshot file
1482 (NewImageMode
, optional
, default "absolute-paths")
1483 - "format": format of
new image (json
-string
, optional
)
1487 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
1489 "/some/place/my-image",
1490 "format": "qcow2" } }
1496 .name
= "blockdev-snapshot",
1497 .args_type
= "node:s,overlay:s",
1498 .mhandler
.cmd_new
= qmp_marshal_blockdev_snapshot
,
1506 Create a snapshot
, by installing
'node' as the backing image of
1507 'overlay'. Additionally
, if 'node' is associated with a block
1508 device
, the block device changes to
using 'overlay' as its
new active
1513 - "node": device that will have a snapshot
created (json
-string
)
1514 - "overlay": device that will have
'node' as its backing
image (json
-string
)
1518 -> { "execute": "blockdev-add",
1519 "arguments": { "options": { "driver": "qcow2",
1520 "node-name": "node1534",
1521 "file": { "driver": "file",
1522 "filename": "hd1.qcow2" },
1527 -> { "execute": "blockdev-snapshot", "arguments": { "node": "ide-hd0",
1528 "overlay": "node1534" } }
1534 .name
= "blockdev-snapshot-internal-sync",
1535 .args_type
= "device:B,name:s",
1536 .mhandler
.cmd_new
= qmp_marshal_blockdev_snapshot_internal_sync
,
1540 blockdev
-snapshot
-internal
-sync
1541 -------------------------------
1543 Synchronously take an internal snapshot of a block device when the format of
1544 image used supports it
. If the name is an empty string
, or a snapshot with
1545 name already exists
, the operation will fail
.
1549 - "device": device name to
snapshot (json
-string
)
1550 - "name": name of the
new snapshot (json
-string
)
1554 -> { "execute": "blockdev-snapshot-internal-sync",
1555 "arguments": { "device": "ide-hd0",
1556 "name": "snapshot0" }
1563 .name
= "blockdev-snapshot-delete-internal-sync",
1564 .args_type
= "device:B,id:s?,name:s?",
1566 qmp_marshal_blockdev_snapshot_delete_internal_sync
,
1570 blockdev
-snapshot
-delete
-internal
-sync
1571 --------------------------------------
1573 Synchronously delete an internal snapshot of a block device when the format of
1574 image used supports it
. The snapshot is identified by name or id or both
. One
1575 of name or id is required
. If the snapshot is not found
, the operation will
1580 - "device": device
name (json
-string
)
1581 - "id": ID of the
snapshot (json
-string
, optional
)
1582 - "name": name of the
snapshot (json
-string
, optional
)
1586 -> { "execute": "blockdev-snapshot-delete-internal-sync",
1587 "arguments": { "device": "ide-hd0",
1588 "name": "snapshot0" }
1592 "name": "snapshot0",
1594 "date-sec": 1000012,
1596 "vm-clock-sec": 100,
1604 .name
= "drive-mirror",
1605 .args_type
= "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1606 "node-name:s?,replaces:s?,"
1607 "on-source-error:s?,on-target-error:s?,"
1609 "granularity:i?,buf-size:i?",
1610 .mhandler
.cmd_new
= qmp_marshal_drive_mirror
,
1617 Start mirroring a block device
's writes to a new destination. target
1618 specifies the target of the new image. If the file exists, or if it is
1619 a device, it will be used as the new destination for writes. If it does not
1620 exist, a new file will be created. format specifies the format of the
1621 mirror image, default is to probe if mode='existing
', else the format
1626 - "device": device name to operate on (json-string)
1627 - "target": name of new image file (json-string)
1628 - "format": format of new image (json-string, optional)
1629 - "node-name": the name of the new block driver state in the node graph
1630 (json-string, optional)
1631 - "replaces": the block driver node name to replace when finished
1632 (json-string, optional)
1633 - "mode": how an image file should be created into the target
1634 file/device (NewImageMode, optional, default 'absolute
-paths
')
1635 - "speed": maximum speed of the streaming job, in bytes per second
1637 - "granularity": granularity of the dirty bitmap, in bytes (json-int, optional)
1638 - "buf-size": maximum amount of data in flight from source to target, in bytes
1639 (json-int, default 10M)
1640 - "sync": what parts of the disk image should be copied to the destination;
1641 possibilities include "full" for all the disk, "top" for only the sectors
1642 allocated in the topmost image, or "none" to only replicate new I/O
1644 - "on-source-error": the action to take on an error on the source
1645 (BlockdevOnError, default 'report
')
1646 - "on-target-error": the action to take on an error on the target
1647 (BlockdevOnError, default 'report
')
1648 - "unmap": whether the target sectors should be discarded where source has only
1649 zeroes. (json-bool, optional, default true)
1651 The default value of the granularity is the image cluster size clamped
1652 between 4096 and 65536, if the image format defines one. If the format
1653 does not define a cluster size, the default value of the granularity
1659 -> { "execute": "drive-mirror", "arguments": { "device": "ide-hd0",
1660 "target": "/some/place/my-image",
1662 "format": "qcow2" } }
1668 .name = "blockdev-mirror",
1669 .args_type = "sync:s,device:B,target:B,replaces:s?,speed:i?,"
1670 "on-source-error:s?,on-target-error:s?,"
1671 "granularity:i?,buf-size:i?",
1672 .mhandler.cmd_new = qmp_marshal_blockdev_mirror,
1679 Start mirroring a block device's writes to another block device
. target
1680 specifies the target of mirror operation
.
1684 - "device": device name to operate
on (json
-string
)
1685 - "target": device name to mirror
to (json
-string
)
1686 - "replaces": the block driver node name to replace when finished
1687 (json
-string
, optional
)
1688 - "speed": maximum speed of the streaming job
, in bytes per second
1690 - "granularity": granularity of the dirty bitmap
, in bytes (json
-int
, optional
)
1691 - "buf_size": maximum amount of data
in flight from source to target
, in bytes
1692 (json
-int
, default 10M
)
1693 - "sync": what parts of the disk image should be copied to the destination
;
1694 possibilities include
"full" for all the disk
, "top" for only the sectors
1695 allocated
in the topmost image
, or
"none" to only replicate
new I
/O
1697 - "on-source-error": the action to take on an error on the source
1698 (BlockdevOnError
, default 'report')
1699 - "on-target-error": the action to take on an error on the target
1700 (BlockdevOnError
, default 'report')
1702 The
default value of the granularity is the image cluster size clamped
1703 between
4096 and
65536, if the image format defines one
. If the format
1704 does not define a cluster size
, the
default value of the granularity
1709 -> { "execute": "blockdev-mirror", "arguments": { "device": "ide-hd0",
1710 "target": "target0",
1716 .name
= "change-backing-file",
1717 .args_type
= "device:s,image-node-name:s,backing-file:s",
1718 .mhandler
.cmd_new
= qmp_marshal_change_backing_file
,
1726 Change the backing file
in the image file metadata
. This does not cause
1727 QEMU to reopen the image file to reparse the backing
filename (it may
,
1728 however
, perform a reopen to change permissions from r
/o
-> r
/w
-> r
/o
,
1729 if needed
). The
new backing file string is written into the image file
1730 metadata
, and the QEMU internal strings are updated
.
1734 - "image-node-name": The name of the block driver state node of the
1735 image to modify
. The
"device" is argument is used to
1736 verify
"image-node-name" is
in the chain described by
1738 (json
-string
, optional
)
1740 - "device": The name of the device
.
1743 - "backing-file": The string to write as the backing file
. This string is
1744 not validated
, so care should be taken when specifying
1745 the string or the image chain may not be able to be
1749 Returns
: Nothing on success
1750 If
"device" does not exist or cannot be determined
, DeviceNotFound
1756 .args_type
= "value:M",
1757 .mhandler
.cmd_new
= qmp_marshal_balloon
,
1764 Request VM to change its memory
allocation (in bytes
).
1768 - "value": New memory
allocation (json
-int
)
1772 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1779 .args_type
= "name:s,up:b",
1780 .mhandler
.cmd_new
= qmp_marshal_set_link
,
1787 Change the link status of a network adapter
.
1791 - "name": network device
name (json
-string
)
1792 - "up": status is
up (json
-bool
)
1796 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
1803 .args_type
= "fdname:s",
1804 .params
= "getfd name",
1805 .help
= "receive a file descriptor via SCM rights and assign it a name",
1806 .mhandler
.cmd_new
= qmp_marshal_getfd
,
1813 Receive a file descriptor via SCM rights and assign it a name
.
1817 - "fdname": file descriptor
name (json
-string
)
1821 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1826 (1) If the name specified by the
"fdname" argument already exists
,
1827 the file descriptor assigned to it will be closed and replaced
1828 by the received file descriptor
.
1829 (2) The
'closefd' command can be used to explicitly close the file
1830 descriptor when it is no longer needed
.
1836 .args_type
= "fdname:s",
1837 .params
= "closefd name",
1838 .help
= "close a file descriptor previously passed via SCM rights",
1839 .mhandler
.cmd_new
= qmp_marshal_closefd
,
1846 Close a file descriptor previously passed via SCM rights
.
1850 - "fdname": file descriptor
name (json
-string
)
1854 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1861 .args_type
= "fdset-id:i?,opaque:s?",
1862 .params
= "add-fd fdset-id opaque",
1863 .help
= "Add a file descriptor, that was passed via SCM rights, to an fd set",
1864 .mhandler
.cmd_new
= qmp_marshal_add_fd
,
1871 Add a file descriptor
, that was passed via SCM rights
, to an fd set
.
1875 - "fdset-id": The ID of the fd set to add the file descriptor to
.
1876 (json
-int
, optional
)
1877 - "opaque": A free
-form string that can be used to describe the fd
.
1878 (json
-string
, optional
)
1880 Return a json
-object with the following information
:
1882 - "fdset-id": The ID of the fd set that the fd was added to
. (json
-int
)
1883 - "fd": The file descriptor that was received via SCM rights and added to the
1888 -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1889 <- { "return": { "fdset-id": 1, "fd": 3 } }
1893 (1) The list of fd sets is shared by all monitor connections
.
1894 (2) If
"fdset-id" is not specified
, a
new fd set will be created
.
1899 .name
= "remove-fd",
1900 .args_type
= "fdset-id:i,fd:i?",
1901 .params
= "remove-fd fdset-id fd",
1902 .help
= "Remove a file descriptor from an fd set",
1903 .mhandler
.cmd_new
= qmp_marshal_remove_fd
,
1910 Remove a file descriptor from an fd set
.
1914 - "fdset-id": The ID of the fd set that the file descriptor belongs to
.
1916 - "fd": The file descriptor that is to be removed
. (json
-int
, optional
)
1920 -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1925 (1) The list of fd sets is shared by all monitor connections
.
1926 (2) If
"fd" is not specified
, all file descriptors
in "fdset-id" will be
1932 .name
= "query-fdsets",
1934 .help
= "Return information describing all fd sets",
1935 .mhandler
.cmd_new
= qmp_marshal_query_fdsets
,
1942 Return information describing all fd sets
.
1948 -> { "execute": "query-fdsets" }
1954 "opaque": "rdonly:/path/to/file"
1958 "opaque": "rdwr:/path/to/file"
1977 Note
: The list of fd sets is shared by all monitor connections
.
1982 .name
= "block_passwd",
1983 .args_type
= "device:s?,node-name:s?,password:s",
1984 .mhandler
.cmd_new
= qmp_marshal_block_passwd
,
1991 Set the password of encrypted block devices
.
1995 - "device": device
name (json
-string
)
1996 - "node-name": name
in the block driver state
graph (json
-string
)
1997 - "password": password (json
-string
)
2001 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
2002 "password": "12345" } }
2008 .name
= "block_set_io_throttle",
2009 .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?,group:s?",
2010 .mhandler
.cmd_new
= qmp_marshal_block_set_io_throttle
,
2014 block_set_io_throttle
2017 Change I
/O throttle limits
for a block drive
.
2021 - "device": device
name (json
-string
)
2022 - "bps": total throughput limit
in bytes per
second (json
-int
)
2023 - "bps_rd": read throughput limit
in bytes per
second (json
-int
)
2024 - "bps_wr": write throughput limit
in bytes per
second (json
-int
)
2025 - "iops": total I
/O operations per
second (json
-int
)
2026 - "iops_rd": read I
/O operations per
second (json
-int
)
2027 - "iops_wr": write I
/O operations per
second (json
-int
)
2028 - "bps_max": total max
in bytes (json
-int
)
2029 - "bps_rd_max": read max
in bytes (json
-int
)
2030 - "bps_wr_max": write max
in bytes (json
-int
)
2031 - "iops_max": total I
/O operations
max (json
-int
)
2032 - "iops_rd_max": read I
/O operations
max (json
-int
)
2033 - "iops_wr_max": write I
/O operations
max (json
-int
)
2034 - "iops_size": I
/O size
in bytes when
limiting (json
-int
)
2035 - "group": throttle group
name (json
-string
)
2039 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
2058 .name
= "set_password",
2059 .args_type
= "protocol:s,password:s,connected:s?",
2060 .mhandler
.cmd_new
= qmp_marshal_set_password
,
2067 Set the password
for vnc
/spice protocols
.
2071 - "protocol": protocol
name (json
-string
)
2072 - "password": password (json
-string
)
2073 - "connected": [ keep | disconnect | fail
] (json
-string
, optional
)
2077 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
2078 "password": "secret" } }
2084 .name
= "expire_password",
2085 .args_type
= "protocol:s,time:s",
2086 .mhandler
.cmd_new
= qmp_marshal_expire_password
,
2093 Set the password expire time
for vnc
/spice protocols
.
2097 - "protocol": protocol
name (json
-string
)
2098 - "time": [ now |
never |
+secs | secs
] (json
-string
)
2102 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
2109 .name
= "add_client",
2110 .args_type
= "protocol:s,fdname:s,skipauth:b?,tls:b?",
2111 .mhandler
.cmd_new
= qmp_marshal_add_client
,
2118 Add a graphics client
2122 - "protocol": protocol
name (json
-string
)
2123 - "fdname": file descriptor
name (json
-string
)
2124 - "skipauth": whether to skip
authentication (json
-bool
, optional
)
2125 - "tls": whether to perform
TLS (json
-bool
, optional
)
2129 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
2130 "fdname": "myclient" } }
2135 .name
= "qmp_capabilities",
2138 .help
= "enable QMP capabilities",
2139 .mhandler
.cmd_new
= qmp_capabilities
,
2146 Enable QMP capabilities
.
2152 -> { "execute": "qmp_capabilities" }
2155 Note
: This command must be issued before issuing any other command
.
2160 .name
= "human-monitor-command",
2161 .args_type
= "command-line:s,cpu-index:i?",
2162 .mhandler
.cmd_new
= qmp_marshal_human_monitor_command
,
2166 human
-monitor
-command
2167 ---------------------
2169 Execute a Human Monitor command
.
2173 - command
-line
: the command name and its arguments
, just like the
2174 Human Monitor
's shell (json-string)
2175 - cpu-index: select the CPU number to be used by commands which access CPU
2176 data, like 'info registers
'. The Monitor selects CPU 0 if this
2177 argument is not provided (json-int, optional)
2181 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
2182 <- { "return": "kvm support: enabled\r\n" }
2186 (1) The Human Monitor is NOT an stable interface, this means that command
2187 names, arguments and responses can change or be removed at ANY time.
2188 Applications that rely on long term stability guarantees should NOT
2193 o This command is stateless, this means that commands that depend
2194 on state information (such as getfd) might not work
2196 o Commands that prompt the user for data (eg. 'cont
' when the block
2197 device is encrypted) don't currently work
2202 HXCOMM Each query command below is inside a SQMP
/EQMP section
, do NOT change
2203 HXCOMM
this! We will possibly move query commands definitions inside those
2204 HXCOMM sections
, just like regular commands
.
2214 Return a json
-object with the following information
:
2216 - "qemu": A json
-object containing three integer values
:
2217 - "major": QEMU
's major version (json-int)
2218 - "minor": QEMU's minor
version (json
-int
)
2219 - "micro": QEMU
's micro version (json-int)
2220 - "package": package's
version (json
-string
)
2224 -> { "execute": "query-version" }
2239 .name
= "query-version",
2241 .mhandler
.cmd_new
= qmp_marshal_query_version
,
2248 List QMP available commands
.
2250 Each command is represented by a json
-object
, the returned value is a json
-array
2253 Each json
-object contain
:
2255 - "name": command
's name (json-string)
2259 -> { "execute": "query-commands" }
2263 "name":"query-balloon"
2266 "name":"system_powerdown"
2271 Note: This example has been shortened as the real response is too long.
2276 .name = "query-commands",
2278 .mhandler.cmd_new = qmp_marshal_query_commands,
2285 List QMP available events.
2287 Each event is represented by a json-object, the returned value is a json-array
2290 Each json-object contains:
2292 - "name": event's
name (json
-string
)
2296 -> { "execute": "query-events" }
2308 Note
: This example has been shortened as the real response is too long
.
2313 .name
= "query-events",
2315 .mhandler
.cmd_new
= qmp_marshal_query_events
,
2322 Return the QMP wire schema
. The returned value is a json
-array of
2323 named schema entities
. Entities are commands
, events and various
2324 types
. See docs
/qapi
-code
-gen
.txt
for information on their structure
2330 .name
= "query-qmp-schema",
2332 .mhandler
.cmd_new
= qmp_query_qmp_schema
,
2339 Each device is represented by a json
-object
. The returned value is a json
-array
2342 Each json
-object contain the following
:
2344 - "label": device
's label (json-string)
2345 - "filename": device's
file (json
-string
)
2346 - "frontend-open": open
/closed state of the frontend device attached to
this
2351 -> { "execute": "query-chardev" }
2355 "label": "charchannel0",
2356 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.agent,server",
2357 "frontend-open": false
2360 "label": "charmonitor",
2361 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.monitor,server",
2362 "frontend-open": true
2365 "label": "charserial0",
2366 "filename": "pty:/dev/pts/2",
2367 "frontend-open": true
2375 .name
= "query-chardev",
2377 .mhandler
.cmd_new
= qmp_marshal_query_chardev
,
2381 query
-chardev
-backends
2384 List available character device backends
.
2386 Each backend is represented by a json
-object
, the returned value is a json
-array
2389 Each json
-object contains
:
2391 - "name": backend
name (json
-string
)
2395 -> { "execute": "query-chardev-backends" }
2416 .name
= "query-chardev-backends",
2418 .mhandler
.cmd_new
= qmp_marshal_query_chardev_backends
,
2425 Show the block devices
.
2427 Each block device information is stored
in a json
-object and the returned value
2428 is a json
-array of all devices
.
2430 Each json
-object contain the following
:
2432 - "device": device
name (json
-string
)
2433 - "type": device
type (json
-string
)
2434 - deprecated
, retained
for backward compatibility
2435 - Possible values
: "unknown"
2436 - "removable": true if the device is removable
, false otherwise (json
-bool
)
2437 - "locked": true if the device is locked
, false otherwise (json
-bool
)
2438 - "tray_open": only present
if removable
, true if the device has a tray
,
2439 and it is
open (json
-bool
)
2440 - "inserted": only present
if the device is inserted
, it is a json
-object
2441 containing the following
:
2442 - "file": device file
name (json
-string
)
2443 - "ro": true if read
-only
, false otherwise (json
-bool
)
2444 - "drv": driver format
name (json
-string
)
2445 - Possible values
: "blkdebug", "bochs", "cloop", "dmg",
2446 "file", "file", "ftp", "ftps", "host_cdrom",
2447 "host_device", "http", "https",
2448 "nbd", "parallels", "qcow", "qcow2", "raw",
2449 "tftp", "vdi", "vmdk", "vpc", "vvfat"
2450 - "backing_file": backing file
name (json
-string
, optional
)
2451 - "backing_file_depth": number of files
in the backing file
chain (json
-int
)
2452 - "encrypted": true if encrypted
, false otherwise (json
-bool
)
2453 - "bps": limit total bytes per
second (json
-int
)
2454 - "bps_rd": limit read bytes per
second (json
-int
)
2455 - "bps_wr": limit write bytes per
second (json
-int
)
2456 - "iops": limit total I
/O operations per
second (json
-int
)
2457 - "iops_rd": limit read operations per
second (json
-int
)
2458 - "iops_wr": limit write operations per
second (json
-int
)
2459 - "bps_max": total max
in bytes (json
-int
)
2460 - "bps_rd_max": read max
in bytes (json
-int
)
2461 - "bps_wr_max": write max
in bytes (json
-int
)
2462 - "iops_max": total I
/O operations
max (json
-int
)
2463 - "iops_rd_max": read I
/O operations
max (json
-int
)
2464 - "iops_wr_max": write I
/O operations
max (json
-int
)
2465 - "iops_size": I
/O size when limiting by
iops (json
-int
)
2466 - "detect_zeroes": detect and optimize zero
writing (json
-string
)
2467 - Possible values
: "off", "on", "unmap"
2468 - "write_threshold": write offset threshold
in bytes
, a event will be
2469 emitted
if crossed
. Zero
if disabled (json
-int
)
2470 - "image": the detail of the image
, it is a json
-object containing
2472 - "filename": image file
name (json
-string
)
2473 - "format": image
format (json
-string
)
2474 - "virtual-size": image capacity
in bytes (json
-int
)
2475 - "dirty-flag": true if image is not cleanly closed
, not present
2476 means
clean (json
-bool
, optional
)
2477 - "actual-size": actual size on disk
in bytes of the image
, not
2478 present when image does not support thin
2479 provision (json
-int
, optional
)
2480 - "cluster-size": size of a cluster
in bytes
, not present
if image
2481 format does not support
it (json
-int
, optional
)
2482 - "encrypted": true if the image is encrypted
, not present means
2483 false or the image format does not support
2484 encryption (json
-bool
, optional
)
2485 - "backing_file": backing file name
, not present means no backing
2486 file is used or the image format does not
2487 support backing file chain
2488 (json
-string
, optional
)
2489 - "full-backing-filename": full path of the backing file
, not
2490 present
if it equals backing_file or no
2491 backing file is used
2492 (json
-string
, optional
)
2493 - "backing-filename-format": the format of the backing file
, not
2494 present means unknown or no backing
2495 file (json
-string
, optional
)
2496 - "snapshots": the internal snapshot info
, it is an optional list
2497 of json
-object containing the following
:
2498 - "id": unique snapshot
id (json
-string
)
2499 - "name": snapshot
name (json
-string
)
2500 - "vm-state-size": size of the VM state
in bytes (json
-int
)
2501 - "date-sec": UTC date of the snapshot
in seconds (json
-int
)
2502 - "date-nsec": fractional part
in nanoseconds to be used with
2504 - "vm-clock-sec": VM clock relative to boot
in seconds
2506 - "vm-clock-nsec": fractional part
in nanoseconds to be used
2507 with vm
-clock
-sec (json
-int
)
2508 - "backing-image": the detail of the backing image
, it is an
2509 optional json
-object only present when a
2510 backing image present
for this image
2512 - "io-status": I
/O operation status
, only present
if the device supports it
2513 and the VM is configured to stop on errors
. It
's always reset
2514 to "ok" when the "cont" command is issued (json_string, optional)
2515 - Possible values: "ok", "failed", "nospace"
2519 -> { "execute": "query-block" }
2524 "device":"ide0-hd0",
2531 "file":"disks/test.qcow2",
2532 "backing_file_depth":1,
2546 "detect_zeroes": "on",
2547 "write_threshold": 0,
2549 "filename":"disks/test.qcow2",
2551 "virtual-size":2048000,
2552 "backing_file":"base.qcow2",
2553 "full-backing-filename":"disks/base.qcow2",
2554 "backing-filename-format":"qcow2",
2558 "name": "snapshot1",
2560 "date-sec": 10000200,
2562 "vm-clock-sec": 206,
2567 "filename":"disks/base.qcow2",
2569 "virtual-size":2048000
2577 "device":"ide1-cd0",
2600 .name = "query-block",
2602 .mhandler.cmd_new = qmp_marshal_query_block,
2609 Show block device statistics.
2611 Each device statistic information is stored in a json-object and the returned
2612 value is a json-array of all devices.
2614 Each json-object contain the following:
2616 - "device": device name (json-string)
2617 - "stats": A json-object with the statistics information, it contains:
2618 - "rd_bytes": bytes read (json-int)
2619 - "wr_bytes": bytes written (json-int)
2620 - "rd_operations": read operations (json-int)
2621 - "wr_operations": write operations (json-int)
2622 - "flush_operations": cache flush operations (json-int)
2623 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
2624 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
2625 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
2626 - "wr_highest_offset": The offset after the greatest byte written to the
2627 BlockDriverState since it has been opened (json-int)
2628 - "rd_merged": number of read requests that have been merged into
2629 another request (json-int)
2630 - "wr_merged": number of write requests that have been merged into
2631 another request (json-int)
2632 - "idle_time_ns": time since the last I/O operation, in
2633 nanoseconds. If the field is absent it means
2634 that there haven't been any operations yet
2635 (json
-int
, optional
)
2636 - "failed_rd_operations": number of failed read operations
2638 - "failed_wr_operations": number of failed write operations
2640 - "failed_flush_operations": number of failed flush operations
2642 - "invalid_rd_operations": number of invalid read operations
2644 - "invalid_wr_operations": number of invalid write operations
2646 - "invalid_flush_operations": number of invalid flush operations
2648 - "account_invalid": whether invalid operations are included
in
2649 the last access
statistics (json
-bool
)
2650 - "account_failed": whether failed operations are included
in the
2651 latency and last access statistics
2653 - "timed_stats": A json
-array containing statistics collected
in
2654 specific intervals
, with the following members
:
2655 - "interval_length": interval used
for calculating the
2656 statistics
, in seconds (json
-int
)
2657 - "min_rd_latency_ns": minimum latency of read operations
in
2658 the defined interval
, in nanoseconds
2660 - "min_wr_latency_ns": minimum latency of write operations
in
2661 the defined interval
, in nanoseconds
2663 - "min_flush_latency_ns": minimum latency of flush operations
2664 in the defined interval
, in
2665 nanoseconds (json
-int
)
2666 - "max_rd_latency_ns": maximum latency of read operations
in
2667 the defined interval
, in nanoseconds
2669 - "max_wr_latency_ns": maximum latency of write operations
in
2670 the defined interval
, in nanoseconds
2672 - "max_flush_latency_ns": maximum latency of flush operations
2673 in the defined interval
, in
2674 nanoseconds (json
-int
)
2675 - "avg_rd_latency_ns": average latency of read operations
in
2676 the defined interval
, in nanoseconds
2678 - "avg_wr_latency_ns": average latency of write operations
in
2679 the defined interval
, in nanoseconds
2681 - "avg_flush_latency_ns": average latency of flush operations
2682 in the defined interval
, in
2683 nanoseconds (json
-int
)
2684 - "avg_rd_queue_depth": average number of pending read
2685 operations
in the defined interval
2687 - "avg_wr_queue_depth": average number of pending write
2688 operations
in the defined interval
2690 - "parent": Contains recursively the statistics of the underlying
2691 protocol (e
.g
. the host file
for a qcow2 image
). If there is
2692 no underlying protocol
, this field is omitted
2693 (json
-object
, optional
)
2697 -> { "execute": "query-blockstats" }
2701 "device":"ide0-hd0",
2704 "wr_highest_offset":3686448128,
2706 "wr_operations":751,
2707 "rd_bytes":122567168,
2708 "rd_operations":36772
2709 "wr_total_times_ns":313253456
2710 "rd_total_times_ns":3465673657
2711 "flush_total_times_ns":49653
2712 "flush_operations":61,
2715 "idle_time_ns":2953431879,
2716 "account_invalid":true,
2717 "account_failed":false
2721 "wr_highest_offset":2821110784,
2723 "wr_operations":692,
2724 "rd_bytes":122739200,
2725 "rd_operations":36604
2726 "flush_operations":51,
2727 "wr_total_times_ns":313253456
2728 "rd_total_times_ns":3465673657
2729 "flush_total_times_ns":49653,
2732 "idle_time_ns":2953431879,
2733 "account_invalid":true,
2734 "account_failed":false
2738 "device":"ide1-cd0",
2740 "wr_highest_offset":0,
2745 "flush_operations":0,
2746 "wr_total_times_ns":0
2747 "rd_total_times_ns":0
2748 "flush_total_times_ns":0,
2751 "account_invalid":false,
2752 "account_failed":false
2758 "wr_highest_offset":0,
2763 "flush_operations":0,
2764 "wr_total_times_ns":0
2765 "rd_total_times_ns":0
2766 "flush_total_times_ns":0,
2769 "account_invalid":false,
2770 "account_failed":false
2776 "wr_highest_offset":0,
2781 "flush_operations":0,
2782 "wr_total_times_ns":0
2783 "rd_total_times_ns":0
2784 "flush_total_times_ns":0,
2787 "account_invalid":false,
2788 "account_failed":false
2797 .name
= "query-blockstats",
2798 .args_type
= "query-nodes:b?",
2799 .mhandler
.cmd_new
= qmp_marshal_query_blockstats
,
2806 Show CPU information
.
2808 Return a json
-array
. Each CPU is represented by a json
-object
, which contains
:
2810 - "CPU": CPU
index (json
-int
)
2811 - "current": true if this is the current CPU
, false otherwise (json
-bool
)
2812 - "halted": true if the cpu is halted
, false otherwise (json
-bool
)
2813 - "qom_path": path to the CPU object
in the QOM
tree (json
-str
)
2814 - "arch": architecture of the cpu
, which determines what additional
2815 keys will be
present (json
-str
)
2816 - Current program counter
. The key
's name depends on the architecture:
2817 "pc": i386/x86_64 (json-int)
2818 "nip": PPC (json-int)
2819 "pc" and "npc": sparc (json-int)
2820 "PC": mips (json-int)
2821 - "thread_id": ID of the underlying host thread (json-int)
2825 -> { "execute": "query-cpus" }
2832 "qom_path":"/machine/unattached/device[0]",
2841 "qom_path":"/machine/unattached/device[2]",
2852 .name = "query-cpus",
2854 .mhandler.cmd_new = qmp_marshal_query_cpus,
2861 Returns a list of information about each iothread.
2863 Note this list excludes the QEMU main loop thread, which is not declared
2864 using the -object iothread command-line option. It is always the main thread
2867 Return a json-array. Each iothread is represented by a json-object, which contains:
2869 - "id": name of iothread (json-str)
2870 - "thread-id": ID of the underlying host thread (json-int)
2874 -> { "execute": "query-iothreads" }
2891 .name = "query-iothreads",
2893 .mhandler.cmd_new = qmp_marshal_query_iothreads,
2900 PCI buses and devices information.
2902 The returned value is a json-array of all buses. Each bus is represented by
2903 a json-object, which has a key with a json-array of all PCI devices attached
2904 to it. Each device is represented by a json-object.
2906 The bus json-object contains the following:
2908 - "bus": bus number (json-int)
2909 - "devices": a json-array of json-objects, each json-object represents a
2912 The PCI device json-object contains the following:
2914 - "bus": identical to the parent's bus
number (json
-int
)
2915 - "slot": slot
number (json
-int
)
2916 - "function": function number (json
-int
)
2917 - "class_info": a json
-object containing
:
2918 - "desc": device
class description (json
-string
, optional
)
2919 - "class": device
class number (json
-int
)
2920 - "id": a json
-object containing
:
2921 - "device": device
ID (json
-int
)
2922 - "vendor": vendor
ID (json
-int
)
2923 - "irq": device
's IRQ if assigned (json-int, optional)
2924 - "qdev_id": qdev id string (json-string)
2925 - "pci_bridge": It's a json
-object
, only present
if this device is a
2926 PCI bridge
, contains
:
2927 - "bus": bus
number (json
-int
)
2928 - "secondary": secondary bus
number (json
-int
)
2929 - "subordinate": subordinate bus
number (json
-int
)
2930 - "io_range": I
/O memory range information
, a json
-object with the
2932 - "base": base address
, in bytes (json
-int
)
2933 - "limit": limit address
, in bytes (json
-int
)
2934 - "memory_range": memory range information
, a json
-object with the
2936 - "base": base address
, in bytes (json
-int
)
2937 - "limit": limit address
, in bytes (json
-int
)
2938 - "prefetchable_range": Prefetchable memory range information
, a
2939 json
-object with the following members
:
2940 - "base": base address
, in bytes (json
-int
)
2941 - "limit": limit address
, in bytes (json
-int
)
2942 - "devices": a json
-array of PCI devices
if there
's any attached, each
2943 each element is represented by a json-object, which contains
2944 the same members of the 'PCI device json
-object
' described
2946 - "regions": a json-array of json-objects, each json-object represents a
2947 memory region of this device
2949 The memory range json-object contains the following:
2951 - "base": base memory address (json-int)
2952 - "limit": limit value (json-int)
2954 The region json-object can be an I/O region or a memory region, an I/O region
2955 json-object contains the following:
2957 - "type": "io" (json-string, fixed)
2958 - "bar": BAR number (json-int)
2959 - "address": memory address (json-int)
2960 - "size": memory size (json-int)
2962 A memory region json-object contains the following:
2964 - "type": "memory" (json-string, fixed)
2965 - "bar": BAR number (json-int)
2966 - "address": memory address (json-int)
2967 - "size": memory size (json-int)
2968 - "mem_type_64": true or false (json-bool)
2969 - "prefetch": true or false (json-bool)
2973 -> { "execute": "query-pci" }
2985 "desc":"Host bridge"
3019 "desc":"IDE controller"
3041 "desc":"VGA controller"
3051 "mem_type_64":false,
3054 "address":4026531840,
3059 "mem_type_64":false,
3062 "address":4060086272,
3067 "mem_type_64":false,
3082 "desc":"RAM controller"
3103 Note: This example has been shortened as the real response is too long.
3108 .name = "query-pci",
3110 .mhandler.cmd_new = qmp_marshal_query_pci,
3117 Show KVM information.
3119 Return a json-object with the following information:
3121 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
3122 - "present": true if QEMU has KVM support, false otherwise (json-bool)
3126 -> { "execute": "query-kvm" }
3127 <- { "return": { "enabled": true, "present": true } }
3132 .name = "query-kvm",
3134 .mhandler.cmd_new = qmp_marshal_query_kvm,
3141 Return a json-object with the following information:
3143 - "running": true if the VM is running, or false if it is paused (json-bool)
3144 - "singlestep": true if the VM is in single step mode,
3145 false otherwise (json-bool)
3146 - "status": one of the following values (json-string)
3147 "debug" - QEMU is running on a debugger
3148 "inmigrate" - guest is paused waiting for an incoming migration
3149 "internal-error" - An internal error that prevents further guest
3150 execution has occurred
3151 "io-error" - the last IOP has failed and the device is configured
3152 to pause on I/O errors
3153 "paused" - guest has been paused via the 'stop
' command
3154 "postmigrate" - guest is paused following a successful 'migrate
'
3155 "prelaunch" - QEMU was started with -S and guest has not started
3156 "finish-migrate" - guest is paused to finish the migration process
3157 "restore-vm" - guest is paused to restore VM state
3158 "running" - guest is actively running
3159 "save-vm" - guest is paused to save the VM state
3160 "shutdown" - guest is shut down (and -no-shutdown is in use)
3161 "watchdog" - the watchdog action is configured to pause and
3166 -> { "execute": "query-status" }
3167 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
3172 .name = "query-status",
3174 .mhandler.cmd_new = qmp_marshal_query_status,
3181 Show VM mice information.
3183 Each mouse is represented by a json-object, the returned value is a json-array
3186 The mouse json-object contains the following:
3188 - "name": mouse's
name (json
-string
)
3189 - "index": mouse
's index (json-int)
3190 - "current": true if this mouse is receiving events, false otherwise (json-bool)
3191 - "absolute": true if the mouse generates absolute input events (json-bool)
3195 -> { "execute": "query-mice" }
3199 "name":"QEMU Microsoft Mouse",
3205 "name":"QEMU PS/2 Mouse",
3216 .name = "query-mice",
3218 .mhandler.cmd_new = qmp_marshal_query_mice,
3225 Show VNC server information.
3227 Return a json-object with server information. Connected clients are returned
3228 as a json-array of json-objects.
3230 The main json-object contains the following:
3232 - "enabled": true or false (json-bool)
3233 - "host": server's IP
address (json
-string
)
3234 - "family": address
family (json
-string
)
3235 - Possible values
: "ipv4", "ipv6", "unix", "unknown"
3236 - "service": server
's port number (json-string)
3237 - "auth": authentication method (json-string)
3238 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
3239 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
3240 "vencrypt+plain", "vencrypt+tls+none",
3241 "vencrypt+tls+plain", "vencrypt+tls+sasl",
3242 "vencrypt+tls+vnc", "vencrypt+x509+none",
3243 "vencrypt+x509+plain", "vencrypt+x509+sasl",
3244 "vencrypt+x509+vnc", "vnc"
3245 - "clients": a json-array of all connected clients
3247 Clients are described by a json-object, each one contain the following:
3249 - "host": client's IP
address (json
-string
)
3250 - "family": address
family (json
-string
)
3251 - Possible values
: "ipv4", "ipv6", "unix", "unknown"
3252 - "service": client
's port number (json-string)
3253 - "x509_dname": TLS dname (json-string, optional)
3254 - "sasl_username": SASL username (json-string, optional)
3258 -> { "execute": "query-vnc" }
3279 .name = "query-vnc",
3281 .mhandler.cmd_new = qmp_marshal_query_vnc,
3284 .name = "query-vnc-servers",
3286 .mhandler.cmd_new = qmp_marshal_query_vnc_servers,
3293 Show SPICE server information.
3295 Return a json-object with server information. Connected clients are returned
3296 as a json-array of json-objects.
3298 The main json-object contains the following:
3300 - "enabled": true or false (json-bool)
3301 - "host": server's IP
address (json
-string
)
3302 - "port": server
's port number (json-int, optional)
3303 - "tls-port": server's port
number (json
-int
, optional
)
3304 - "auth": authentication
method (json
-string
)
3305 - Possible values
: "none", "spice"
3306 - "channels": a json
-array of all active channels clients
3308 Channels are described by a json
-object
, each one contain the following
:
3310 - "host": client
's IP address (json-string)
3311 - "family": address family (json-string)
3312 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3313 - "port": client's port
number (json
-string
)
3314 - "connection-id": spice connection id
. All channels with the same id
3315 belong to the same spice
session (json
-int
)
3316 - "channel-type": channel type
. "1" is the main control channel
, filter
for
3317 this one
if you want track spice sessions
only (json
-int
)
3318 - "channel-id": channel id
. Usually
"0", might be different needed when
3319 multiple channels of the same type exist
, such as multiple
3320 display channels
in a multihead
setup (json
-int
)
3321 - "tls": whether the channel is
encrypted (json
-bool
)
3325 -> { "execute": "query-spice" }
3338 "connection-id": 1804289383,
3339 "host": "127.0.0.1",
3347 "connection-id": 1804289383,
3348 "host": "127.0.0.1",
3352 [ ... more channels follow
... ]
3359 #
if defined(CONFIG_SPICE
)
3361 .name
= "query-spice",
3363 .mhandler
.cmd_new
= qmp_marshal_query_spice
,
3373 Return a json
-object with the following information
:
3375 - "name": VM
's name (json-string, optional)
3379 -> { "execute": "query-name" }
3380 <- { "return": { "name": "qemu-name" } }
3385 .name = "query-name",
3387 .mhandler.cmd_new = qmp_marshal_query_name,
3396 Return a json-object with the following information:
3398 - "UUID": Universally Unique Identifier (json-string)
3402 -> { "execute": "query-uuid" }
3403 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
3408 .name = "query-uuid",
3410 .mhandler.cmd_new = qmp_marshal_query_uuid,
3414 query-command-line-options
3415 --------------------------
3417 Show command line option schema.
3419 Return a json-array of command line option schema for all options (or for
3420 the given option), returning an error if the given option doesn't exist
.
3422 Each array entry contains the following
:
3424 - "option": option
name (json
-string
)
3425 - "parameters": a json
-array describes all parameters of the option
:
3426 - "name": parameter
name (json
-string
)
3427 - "type": parameter
type (one of
'string', 'boolean', 'number',
3429 - "help": human readable description of the parameter
3430 (json
-string
, optional
)
3431 - "default": default value string
for the parameter
3432 (json
-string
, optional
)
3436 -> { "execute": "query-command-line-options", "arguments": { "option": "option-rom" } }
3445 "name": "bootindex",
3449 "option": "option-rom"
3457 .name
= "query-command-line-options",
3458 .args_type
= "option:s?",
3459 .mhandler
.cmd_new
= qmp_marshal_query_command_line_options
,
3468 Return a json
-object
. If migration is active there will be another json
-object
3469 with RAM migration status and
if block migration is active another one with
3470 block migration status
.
3472 The main json
-object contains the following
:
3474 - "status": migration
status (json
-string
)
3475 - Possible values
: "setup", "active", "completed", "failed", "cancelled"
3476 - "total-time": total amount of ms since migration started
. If
3477 migration has ended
, it returns the total migration
3479 - "setup-time" amount of setup time
in milliseconds _before_ the
3480 iterations begin but _after_ the QMP command is issued
.
3481 This is designed to provide an accounting of any activities
3482 (such as RDMA pinning
) which may be expensive
, but
do not
3483 actually occur during the iterative migration rounds
3484 themselves
. (json
-int
)
3485 - "downtime": only present when migration has finished correctly
3486 total amount
in ms
for downtime that
happened (json
-int
)
3487 - "expected-downtime": only present
while migration is active
3488 total amount
in ms
for downtime that was calculated on
3489 the last bitmap
round (json
-int
)
3490 - "ram": only present
if "status" is
"active", it is a json
-object with the
3491 following RAM information
:
3492 - "transferred": amount transferred
in bytes (json
-int
)
3493 - "remaining": amount remaining to transfer
in bytes (json
-int
)
3494 - "total": total amount of memory
in bytes (json
-int
)
3495 - "duplicate": number of pages filled entirely with the same
3497 These are sent over the wire much more efficiently
.
3498 - "skipped": number of skipped zero
pages (json
-int
)
3499 - "normal" : number of whole pages transferred
. I
.e
. they
3500 were not sent as duplicate or xbzrle
pages (json
-int
)
3501 - "normal-bytes" : number of bytes transferred
in whole
3502 pages
. This is just normal pages times size of one page
,
3503 but
this way upper levels don
't need to care about page
3505 - "dirty-sync-count": times that dirty ram was synchronized (json-int)
3506 - "disk": only present if "status" is "active" and it is a block migration,
3507 it is a json-object with the following disk information:
3508 - "transferred": amount transferred in bytes (json-int)
3509 - "remaining": amount remaining to transfer in bytes json-int)
3510 - "total": total disk size in bytes (json-int)
3511 - "xbzrle-cache": only present if XBZRLE is active.
3512 It is a json-object with the following XBZRLE information:
3513 - "cache-size": XBZRLE cache size in bytes
3514 - "bytes": number of bytes transferred for XBZRLE compressed pages
3515 - "pages": number of XBZRLE compressed pages
3516 - "cache-miss": number of XBRZRLE page cache misses
3517 - "cache-miss-rate": rate of XBRZRLE page cache misses
3518 - "overflow": number of times XBZRLE overflows. This means
3519 that the XBZRLE encoding was bigger than just sent the
3520 whole page, and then we sent the whole page instead (as as
3525 1. Before the first migration
3527 -> { "execute": "query-migrate" }
3530 2. Migration is done and has succeeded
3532 -> { "execute": "query-migrate" }
3534 "status": "completed",
3544 "normal-bytes":123456,
3545 "dirty-sync-count":15
3550 3. Migration is done and has failed
3552 -> { "execute": "query-migrate" }
3553 <- { "return": { "status": "failed" } }
3555 4. Migration is being performed and is not a block migration:
3557 -> { "execute": "query-migrate" }
3567 "expected-downtime":12345,
3570 "normal-bytes":123456,
3571 "dirty-sync-count":15
3576 5. Migration is being performed and is a block migration:
3578 -> { "execute": "query-migrate" }
3584 "remaining":1053304,
3588 "expected-downtime":12345,
3591 "normal-bytes":123456,
3592 "dirty-sync-count":15
3596 "remaining":20880384,
3602 6. Migration is being performed and XBZRLE is active:
3604 -> { "execute": "query-migrate" }
3608 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
3611 "remaining":1053304,
3615 "expected-downtime":12345,
3618 "normal-bytes":3412992,
3619 "dirty-sync-count":15
3622 "cache-size":67108864,
3626 "cache-miss-rate":0.123,
3635 .name = "query-migrate",
3637 .mhandler.cmd_new = qmp_marshal_query_migrate,
3641 migrate-set-capabilities
3642 ------------------------
3644 Enable/Disable migration capabilities
3646 - "xbzrle": XBZRLE support
3647 - "rdma-pin-all": pin all pages when using RDMA during migration
3648 - "auto-converge": throttle down guest to help convergence of migration
3649 - "zero-blocks": compress zero blocks during block migration
3650 - "events": generate events for each migration state change
3656 -> { "execute": "migrate-set-capabilities" , "arguments":
3657 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
3662 .name = "migrate-set-capabilities",
3663 .args_type = "capabilities:q",
3664 .params = "capability:s,state:b",
3665 .mhandler.cmd_new = qmp_marshal_migrate_set_capabilities,
3668 query-migrate-capabilities
3669 --------------------------
3671 Query current migration capabilities
3673 - "capabilities": migration capabilities state
3674 - "xbzrle" : XBZRLE state (json-bool)
3675 - "rdma-pin-all" : RDMA Pin Page state (json-bool)
3676 - "auto-converge" : Auto Converge state (json-bool)
3677 - "zero-blocks" : Zero Blocks state (json-bool)
3683 -> { "execute": "query-migrate-capabilities" }
3684 <- { "return": [ { "state": false, "capability": "xbzrle" } ] }
3689 .name = "query-migrate-capabilities",
3691 .mhandler.cmd_new = qmp_marshal_query_migrate_capabilities,
3695 migrate-set-parameters
3696 ----------------------
3698 Set migration parameters
3700 - "compress-level": set compression level during migration (json-int)
3701 - "compress-threads": set compression thread count for migration (json-int)
3702 - "decompress-threads": set decompression thread count for migration (json-int)
3708 -> { "execute": "migrate-set-parameters" , "arguments":
3709 { "compress-level": 1 } }
3714 .name = "migrate-set-parameters",
3716 "compress-level:i?,compress-threads:i?,decompress-threads:i?",
3717 .mhandler.cmd_new = qmp_marshal_migrate_set_parameters,
3720 query-migrate-parameters
3721 ------------------------
3723 Query current migration parameters
3725 - "parameters": migration parameters value
3726 - "compress-level" : compression level value (json-int)
3727 - "compress-threads" : compression thread count value (json-int)
3728 - "decompress-threads" : decompression thread count value (json-int)
3734 -> { "execute": "query-migrate-parameters" }
3737 "decompress-threads", 2,
3738 "compress-threads", 8,
3746 .name = "query-migrate-parameters",
3748 .mhandler.cmd_new = qmp_marshal_query_migrate_parameters,
3755 Show balloon information.
3757 Make an asynchronous request for balloon info. When the request completes a
3758 json-object will be returned containing the following data:
3760 - "actual": current balloon value in bytes (json-int)
3764 -> { "execute": "query-balloon" }
3767 "actual":1073741824,
3774 .name = "query-balloon",
3776 .mhandler.cmd_new = qmp_marshal_query_balloon,
3780 .name = "query-block-jobs",
3782 .mhandler.cmd_new = qmp_marshal_query_block_jobs,
3787 .args_type = "path:s",
3788 .mhandler.cmd_new = qmp_marshal_qom_list,
3793 .args_type = "path:s,property:s,value:q",
3794 .mhandler.cmd_new = qmp_marshal_qom_set,
3799 .args_type = "path:s,property:s",
3800 .mhandler.cmd_new = qmp_marshal_qom_get,
3804 .name = "nbd-server-start",
3805 .args_type = "addr:q",
3806 .mhandler.cmd_new = qmp_marshal_nbd_server_start,
3809 .name = "nbd-server-add",
3810 .args_type = "device:B,writable:b?",
3811 .mhandler.cmd_new = qmp_marshal_nbd_server_add,
3814 .name = "nbd-server-stop",
3816 .mhandler.cmd_new = qmp_marshal_nbd_server_stop,
3820 .name = "change-vnc-password",
3821 .args_type = "password:s",
3822 .mhandler.cmd_new = qmp_marshal_change_vnc_password,
3825 .name = "qom-list-types",
3826 .args_type = "implements:s?,abstract:b?",
3827 .mhandler.cmd_new = qmp_marshal_qom_list_types,
3831 .name = "device-list-properties",
3832 .args_type = "typename:s",
3833 .mhandler.cmd_new = qmp_marshal_device_list_properties,
3837 .name = "query-machines",
3839 .mhandler.cmd_new = qmp_marshal_query_machines,
3843 .name = "query-cpu-definitions",
3845 .mhandler.cmd_new = qmp_marshal_query_cpu_definitions,
3849 .name = "query-target",
3851 .mhandler.cmd_new = qmp_marshal_query_target,
3855 .name = "query-tpm",
3857 .mhandler.cmd_new = qmp_marshal_query_tpm,
3864 Return information about the TPM device.
3870 -> { "execute": "query-tpm" }
3873 { "model": "tpm-tis",
3875 { "type": "passthrough",
3877 { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
3889 .name = "query-tpm-models",
3891 .mhandler.cmd_new = qmp_marshal_query_tpm_models,
3898 Return a list of supported TPM models.
3904 -> { "execute": "query-tpm-models" }
3905 <- { "return": [ "tpm-tis" ] }
3910 .name = "query-tpm-types",
3912 .mhandler.cmd_new = qmp_marshal_query_tpm_types,
3919 Return a list of supported TPM types.
3925 -> { "execute": "query-tpm-types" }
3926 <- { "return": [ "passthrough" ] }
3931 .name = "chardev-add",
3932 .args_type = "id:s,backend:q",
3933 .mhandler.cmd_new = qmp_marshal_chardev_add,
3944 - "id": the chardev's ID
, must be
unique (json
-string
)
3945 - "backend": chardev backend type
+ parameters
3949 -> { "execute" : "chardev-add",
3950 "arguments" : { "id" : "foo",
3951 "backend" : { "type" : "null", "data" : {} } } }
3954 -> { "execute" : "chardev-add",
3955 "arguments" : { "id" : "bar",
3956 "backend" : { "type" : "file",
3957 "data" : { "out" : "/tmp/bar.log" } } } }
3960 -> { "execute" : "chardev-add",
3961 "arguments" : { "id" : "baz",
3962 "backend" : { "type" : "pty", "data" : {} } } }
3963 <- { "return": { "pty" : "/dev/pty/42" } }
3968 .name
= "chardev-remove",
3969 .args_type
= "id:s",
3970 .mhandler
.cmd_new
= qmp_marshal_chardev_remove
,
3982 - "id": the chardev
's ID, must exist and not be in use (json-string)
3986 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }
3991 .name = "query-rx-filter",
3992 .args_type = "name:s?",
3993 .mhandler.cmd_new = qmp_marshal_query_rx_filter,
4000 Show rx-filter information.
4002 Returns a json-array of rx-filter information for all NICs (or for the
4003 given NIC), returning an error if the given NIC doesn't exist
, or
4004 given NIC doesn
't support rx-filter querying, or given net client
4007 The query will clear the event notification flag of each NIC
, then qemu
4008 will start to emit event to QMP monitor
.
4010 Each array entry contains the following
:
4012 - "name": net client
name (json
-string
)
4013 - "promiscuous": promiscuous mode is
enabled (json
-bool
)
4014 - "multicast": multicast receive
state (one of
'normal', 'none', 'all')
4015 - "unicast": unicast receive
state (one of
'normal', 'none', 'all')
4016 - "vlan": vlan receive
state (one of
'normal', 'none', 'all') (Since
2.0)
4017 - "broadcast-allowed": allow to receive
broadcast (json
-bool
)
4018 - "multicast-overflow": multicast table is
overflowed (json
-bool
)
4019 - "unicast-overflow": unicast table is
overflowed (json
-bool
)
4020 - "main-mac": main macaddr
string (json
-string
)
4021 - "vlan-table": a json
-array of active vlan id
4022 - "unicast-table": a json
-array of unicast macaddr string
4023 - "multicast-table": a json
-array of multicast macaddr string
4027 -> { "execute": "query-rx-filter", "arguments": { "name": "vnet0" } }
4030 "promiscuous": true,
4032 "main-mac": "52:54:00:12:34:56",
4033 "unicast": "normal",
4041 "multicast": "normal",
4042 "multicast-overflow": false,
4043 "unicast-overflow": false,
4044 "multicast-table": [
4045 "01:00:5e:00:00:01",
4046 "33:33:00:00:00:01",
4049 "broadcast-allowed": false
4057 .name
= "blockdev-add",
4058 .args_type
= "options:q",
4059 .mhandler
.cmd_new
= qmp_marshal_blockdev_add
,
4068 This command is still a work
in progress
. It doesn
't support all
4069 block drivers among other things. Stay away from it unless you want
4070 to help with its development.
4074 - "options": block driver options
4078 -> { "execute": "blockdev-add",
4079 "arguments": { "options" : { "driver": "qcow2",
4080 "file": { "driver": "file",
4081 "filename": "test.qcow2" } } } }
4086 -> { "execute": "blockdev-add",
4098 "filename": "/tmp/test.qcow2"
4104 "filename": "/dev/fdset/4"
4116 .name = "x-blockdev-del",
4117 .args_type = "id:s?,node-name:s?",
4118 .mhandler.cmd_new = qmp_marshal_x_blockdev_del,
4126 Deletes a block device thas has been added using blockdev-add.
4127 The selected device can be either a block backend or a graph node.
4129 In the former case the backend will be destroyed, along with its
4130 inserted medium if there's any
. The command will fail
if the backend
4131 or its medium are
in use
.
4133 In the latter
case the node will be destroyed
. The command will fail
4134 if the node is attached to a block backend or is otherwise being
4137 One of
"id" or
"node-name" must be specified
, but not both
.
4139 This command is still a work
in progress and is considered
4140 experimental
. Stay away from it unless you want to help with its
4145 - "id": Name of the block backend device to
delete (json
-string
, optional
)
4146 - "node-name": Name of the graph node to
delete (json
-string
, optional
)
4150 -> { "execute": "blockdev-add",
4157 "filename": "test.qcow2"
4165 -> { "execute": "x-blockdev-del",
4166 "arguments": { "id": "drive0" }
4173 .name
= "blockdev-open-tray",
4174 .args_type
= "device:s,force:b?",
4175 .mhandler
.cmd_new
= qmp_marshal_blockdev_open_tray
,
4182 Opens a block device
's tray. If there is a block driver state tree inserted as a
4183 medium, it will become inaccessible to the guest (but it will remain associated
4184 to the block device, so closing the tray will make it accessible again).
4186 If the tray was already open before, this will be a no-op.
4188 Once the tray opens, a DEVICE_TRAY_MOVED event is emitted. There are cases in
4189 which no such event will be generated, these include:
4190 - if the guest has locked the tray, @force is false and the guest does not
4191 respond to the eject request
4192 - if the BlockBackend denoted by @device does not have a guest device attached
4194 - if the guest device does not have an actual tray and is empty, for instance
4195 for floppy disk drives
4199 - "device": block device name (json-string)
4200 - "force": if false (the default), an eject request will be sent to the guest if
4201 it has locked the tray (and the tray will not be opened immediately);
4202 if true, the tray will be opened regardless of whether it is locked
4203 (json-bool, optional)
4207 -> { "execute": "blockdev-open-tray",
4208 "arguments": { "device": "ide1-cd0" } }
4210 <- { "timestamp": { "seconds": 1418751016,
4211 "microseconds": 716996 },
4212 "event": "DEVICE_TRAY_MOVED",
4213 "data": { "device": "ide1-cd0",
4214 "tray-open": true } }
4221 .name = "blockdev-close-tray",
4222 .args_type = "device:s",
4223 .mhandler.cmd_new = qmp_marshal_blockdev_close_tray,
4230 Closes a block device's tray
. If there is a block driver state tree associated
4231 with the block
device (which is currently ejected
), that tree will be loaded as
4234 If the tray was already closed before
, this will be a no
-op
.
4238 - "device": block device
name (json
-string
)
4242 -> { "execute": "blockdev-close-tray",
4243 "arguments": { "device": "ide1-cd0" } }
4245 <- { "timestamp": { "seconds": 1418751345,
4246 "microseconds": 272147 },
4247 "event": "DEVICE_TRAY_MOVED",
4248 "data": { "device": "ide1-cd0",
4249 "tray-open": false } }
4256 .name
= "x-blockdev-remove-medium",
4257 .args_type
= "device:s",
4258 .mhandler
.cmd_new
= qmp_marshal_x_blockdev_remove_medium
,
4262 x
-blockdev
-remove
-medium
4263 ------------------------
4265 Removes a
medium (a block driver state tree
) from a block device
. That block
4266 device
's tray must currently be open (unless there is no attached guest device).
4268 If the tray is open and there is no medium inserted, this will be a no-op.
4270 This command is still a work in progress and is considered experimental.
4271 Stay away from it unless you want to help with its development.
4275 - "device": block device name (json-string)
4279 -> { "execute": "x-blockdev-remove-medium",
4280 "arguments": { "device": "ide1-cd0" } }
4282 <- { "error": { "class": "GenericError",
4283 "desc": "Tray of device 'ide1
-cd0
' is not open" } }
4285 -> { "execute": "blockdev-open-tray",
4286 "arguments": { "device": "ide1-cd0" } }
4288 <- { "timestamp": { "seconds": 1418751627,
4289 "microseconds": 549958 },
4290 "event": "DEVICE_TRAY_MOVED",
4291 "data": { "device": "ide1-cd0",
4292 "tray-open": true } }
4296 -> { "execute": "x-blockdev-remove-medium",
4297 "arguments": { "device": "ide1-cd0" } }
4304 .name = "x-blockdev-insert-medium",
4305 .args_type = "device:s,node-name:s",
4306 .mhandler.cmd_new = qmp_marshal_x_blockdev_insert_medium,
4310 x-blockdev-insert-medium
4311 ------------------------
4313 Inserts a medium (a block driver state tree) into a block device. That block
4314 device's tray must currently be
open (unless there is no attached guest device
)
4315 and there must be no medium inserted already
.
4317 This command is still a work
in progress and is considered experimental
.
4318 Stay away from it unless you want to help with its development
.
4322 - "device": block device
name (json
-string
)
4323 - "node-name": root node of the BDS tree to insert into the block device
4327 -> { "execute": "blockdev-add",
4328 "arguments": { "options": { "node-name": "node0",
4330 "file": { "driver": "file",
4331 "filename": "fedora.iso" } } } }
4335 -> { "execute": "x-blockdev-insert-medium",
4336 "arguments": { "device": "ide1-cd0",
4337 "node-name": "node0" } }
4344 .name
= "query-named-block-nodes",
4346 .mhandler
.cmd_new
= qmp_marshal_query_named_block_nodes
,
4350 @query
-named
-block
-nodes
4351 ------------------------
4353 Return a list of BlockDeviceInfo
for all the named block driver nodes
4357 -> { "execute": "query-named-block-nodes" }
4358 <- { "return": [ { "ro":false,
4361 "file":"disks/test.qcow2",
4362 "node-name": "my-node",
4363 "backing_file_depth":1,
4377 "write_threshold": 0,
4379 "filename":"disks/test.qcow2",
4381 "virtual-size":2048000,
4382 "backing_file":"base.qcow2",
4383 "full-backing-filename":"disks/base.qcow2",
4384 "backing-filename-format":"qcow2",
4388 "name": "snapshot1",
4390 "date-sec": 10000200,
4392 "vm-clock-sec": 206,
4397 "filename":"disks/base.qcow2",
4399 "virtual-size":2048000
4406 .name
= "blockdev-change-medium",
4407 .args_type
= "device:B,filename:F,format:s?,read-only-mode:s?",
4408 .mhandler
.cmd_new
= qmp_marshal_blockdev_change_medium
,
4412 blockdev
-change
-medium
4413 ----------------------
4415 Changes the medium inserted into a block device by ejecting the current medium
4416 and loading a
new image file which is inserted as the
new medium
.
4420 - "device": device
name (json
-string
)
4421 - "filename": filename of the
new image (json
-string
)
4422 - "format": format of the
new image (json
-string
, optional
)
4423 - "read-only-mode": new read
-only
mode (json
-string
, optional
)
4424 - Possible values
: "retain" (default), "read-only", "read-write"
4428 1. Change a removable medium
4430 -> { "execute": "blockdev-change-medium",
4431 "arguments": { "device": "ide1-cd0",
4432 "filename": "/srv/images/Fedora-12-x86_64-DVD.iso",
4436 2. Load a read
-only medium into a writable drive
4438 -> { "execute": "blockdev-change-medium",
4439 "arguments": { "device": "isa-fd0",
4440 "filename": "/srv/images/ro.img",
4442 "read-only-mode": "retain" } }
4445 { "class": "GenericError",
4446 "desc": "Could not open '/srv/images/ro.img': Permission denied" } }
4448 -> { "execute": "blockdev-change-medium",
4449 "arguments": { "device": "isa-fd0",
4450 "filename": "/srv/images/ro.img",
4452 "read-only-mode": "read-only" } }
4459 .name
= "query-memdev",
4461 .mhandler
.cmd_new
= qmp_marshal_query_memdev
,
4468 Show memory devices information
.
4473 -> { "execute": "query-memdev" }
4480 "host-nodes": [0, 1],
4488 "host-nodes": [2, 3],
4489 "policy": "preferred"
4497 .name
= "query-memory-devices",
4499 .mhandler
.cmd_new
= qmp_marshal_query_memory_devices
,
4503 @query
-memory
-devices
4504 --------------------
4506 Return a list of memory devices
.
4509 -> { "execute": "query-memory-devices" }
4510 <- { "return": [ { "data":
4511 { "addr": 5368709120,
4512 "hotpluggable": true,
4515 "memdev": "/objects/memX",
4524 .name
= "query-acpi-ospm-status",
4526 .mhandler
.cmd_new
= qmp_marshal_query_acpi_ospm_status
,
4530 @query
-acpi
-ospm
-status
4531 --------------------
4533 Return list of ACPIOSTInfo
for devices that support status reporting
4534 via ACPI _OST method
.
4537 -> { "execute": "query-acpi-ospm-status" }
4538 <- { "return": [ { "device": "d1", "slot": "0", "slot-type": "DIMM", "source": 1, "status": 0},
4539 { "slot": "1", "slot-type": "DIMM", "source": 0, "status": 0},
4540 { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
4541 { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
4545 #
if defined TARGET_I386
4547 .name
= "rtc-reset-reinjection",
4549 .mhandler
.cmd_new
= qmp_marshal_rtc_reset_reinjection
,
4554 rtc
-reset
-reinjection
4555 ---------------------
4557 Reset the RTC interrupt reinjection backlog
.
4563 -> { "execute": "rtc-reset-reinjection" }
4568 .name
= "trace-event-get-state",
4569 .args_type
= "name:s",
4570 .mhandler
.cmd_new
= qmp_marshal_trace_event_get_state
,
4574 trace-event
-get
-state
4575 ---------------------
4577 Query the state of events
.
4581 -> { "execute": "trace-event-get-state", "arguments": { "name": "qemu_memalign" } }
4582 <- { "return": [ { "name": "qemu_memalign", "state": "disabled" } ] }
4586 .name
= "trace-event-set-state",
4587 .args_type
= "name:s,enable:b,ignore-unavailable:b?",
4588 .mhandler
.cmd_new
= qmp_marshal_trace_event_set_state
,
4592 trace-event
-set
-state
4593 ---------------------
4595 Set the state of events
.
4599 -> { "execute": "trace-event-set-state", "arguments": { "name": "qemu_memalign", "enable": "true" } }
4604 .name
= "x-input-send-event",
4605 .args_type
= "console:i?,events:q",
4606 .mhandler
.cmd_new
= qmp_marshal_x_input_send_event
,
4613 Send input event to guest
.
4617 - "console": console index
. (json
-int
, optional
)
4618 - "events": list of input events
.
4620 The consoles are visible
in the qom tree
, under
4621 /backend
/console
[$index
]. They have a device link and head property
, so
4622 it is possible to map which console belongs to which device and display
.
4624 Note
: this command is experimental
, and not a stable API
.
4628 Press left mouse button
.
4630 -> { "execute": "x-input-send-event",
4631 "arguments": { "console": 0,
4632 "events": [ { "type": "btn",
4633 "data" : { "down": true, "button": "Left" } } ] } }
4636 -> { "execute": "x-input-send-event",
4637 "arguments": { "console": 0,
4638 "events": [ { "type": "btn",
4639 "data" : { "down": false, "button": "Left" } } ] } }
4646 -> { "execute": "x-input-send-event",
4647 "arguments": { "console": 0, "events": [
4648 { "type": "key", "data" : { "down": true,
4649 "key": {"type": "qcode", "data": "ctrl" } } },
4650 { "type": "key", "data" : { "down": true,
4651 "key": {"type": "qcode", "data": "alt" } } },
4652 { "type": "key", "data" : { "down": true,
4653 "key": {"type": "qcode", "data": "delete" } } } ] } }
4658 Move mouse pointer to absolute
coordinates (20000, 400).
4660 -> { "execute": "x-input-send-event" ,
4661 "arguments": { "console": 0, "events": [
4662 { "type": "abs", "data" : { "axis": "X", "value" : 20000 } },
4663 { "type": "abs", "data" : { "axis": "Y", "value" : 400 } } ] } }
4669 .name
= "block-set-write-threshold",
4670 .args_type
= "node-name:s,write-threshold:l",
4671 .mhandler
.cmd_new
= qmp_marshal_block_set_write_threshold
,
4675 block
-set
-write
-threshold
4678 Change the write threshold
for a block drive
. The threshold is an offset
,
4679 thus must be non
-negative
. Default is no write threshold
.
4680 Setting the threshold to zero disables it
.
4684 - "node-name": the node name
in the block driver state
graph (json
-string
)
4685 - "write-threshold": the write threshold
in bytes (json
-int
)
4689 -> { "execute": "block-set-write-threshold",
4690 "arguments": { "node-name": "mydev",
4691 "write-threshold": 17179869184 } }
4697 .name
= "query-rocker",
4698 .args_type
= "name:s",
4699 .mhandler
.cmd_new
= qmp_marshal_query_rocker
,
4708 - "name": switch name
4712 -> { "execute": "query-rocker", "arguments": { "name": "sw1" } }
4713 <- { "return": {"name": "sw1", "ports": 2, "id": 1327446905938}}
4718 .name
= "query-rocker-ports",
4719 .args_type
= "name:s",
4720 .mhandler
.cmd_new
= qmp_marshal_query_rocker_ports
,
4724 Show rocker
switch ports
4725 ------------------------
4729 - "name": switch name
4733 -> { "execute": "query-rocker-ports", "arguments": { "name": "sw1" } }
4734 <- { "return": [ {"duplex": "full", "enabled": true, "name": "sw1.1",
4735 "autoneg": "off", "link-up": true, "speed": 10000},
4736 {"duplex": "full", "enabled": true, "name": "sw1.2",
4737 "autoneg": "off", "link-up": true, "speed": 10000}
4743 .name
= "query-rocker-of-dpa-flows",
4744 .args_type
= "name:s,tbl-id:i?",
4745 .mhandler
.cmd_new
= qmp_marshal_query_rocker_of_dpa_flows
,
4749 Show rocker
switch OF
-DPA flow tables
4750 -------------------------------------
4754 - "name": switch name
4755 - "tbl-id": (optional
) flow table ID
4759 -> { "execute": "query-rocker-of-dpa-flows", "arguments": { "name": "sw1" } }
4760 <- { "return": [ {"key": {"in-pport": 0, "priority": 1, "tbl-id": 0},
4763 "action": {"goto-tbl": 10},
4764 "mask": {"in-pport": 4294901760}
4772 .name
= "query-rocker-of-dpa-groups",
4773 .args_type
= "name:s,type:i?",
4774 .mhandler
.cmd_new
= qmp_marshal_query_rocker_of_dpa_groups
,
4778 Show rocker OF
-DPA group tables
4779 -------------------------------
4783 - "name": switch name
4784 - "type": (optional
) group type
4788 -> { "execute": "query-rocker-of-dpa-groups", "arguments": { "name": "sw1" } }
4789 <- { "return": [ {"type": 0, "out-pport": 2, "pport": 2, "vlan-id": 3841,
4790 "pop-vlan": 1, "id": 251723778},
4791 {"type": 0, "out-pport": 0, "pport": 0, "vlan-id": 3841,
4792 "pop-vlan": 1, "id": 251723776},
4793 {"type": 0, "out-pport": 1, "pport": 1, "vlan-id": 3840,
4794 "pop-vlan": 1, "id": 251658241},
4795 {"type": 0, "out-pport": 0, "pport": 0, "vlan-id": 3840,
4796 "pop-vlan": 1, "id": 251658240}