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,detach:b?,begin:i?,end:i?,format:s?",
842 .params = "-p protocol [-d] [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 - "detach": if specified, command will return immediately, without waiting
859 for the dump to finish. The user can track progress using
860 "query-dump". (json-bool)
861 - "begin": the starting physical address. It's optional, and should be specified
862 with length together (json-int)
863 - "length": the memory size, in bytes. It's optional, and should be specified
864 with begin together (json-int)
865 - "format": the format of guest memory dump. It's optional, and can be
866 elf|kdump-zlib|kdump-lzo|kdump-snappy, but non-elf formats will
867 conflict with paging and filter, ie. begin and length (json-string)
871 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
876 (1) All boolean arguments default to false
881 .name = "query-dump-guest-memory-capability",
883 .mhandler.cmd_new = qmp_marshal_query_dump_guest_memory_capability,
887 query-dump-guest-memory-capability
890 Show available formats for 'dump-guest-memory'
894 -> { "execute": "query-dump-guest-memory-capability" }
895 <- { "return": { "formats":
896 ["elf", "kdump-zlib", "kdump-lzo", "kdump-snappy"] }
901 .name = "query-dump",
904 .help = "query background dump status",
905 .mhandler.cmd_new = qmp_marshal_query_dump,
912 Query background dump status.
918 -> { "execute": "query-dump" }
919 <- { "return": { "status": "active", "completed": 1024000,
924 #if defined TARGET_S390X
926 .name = "dump-skeys",
927 .args_type = "filename:F",
928 .mhandler.cmd_new = qmp_marshal_dump_skeys,
936 Save guest storage keys to file.
940 - "filename": file path (json-string)
944 -> { "execute": "dump-skeys", "arguments": { "filename": "/tmp/skeys" } }
950 .name = "netdev_add",
951 .args_type = "netdev:O",
952 .mhandler.cmd_new = qmp_netdev_add,
959 Add host network device.
963 - "type": the device type, "tap", "user", ... (json-string)
964 - "id": the device's ID, must be unique (json-string)
969 -> { "execute": "netdev_add",
970 "arguments": { "type": "user", "id": "netdev1",
971 "dnssearch": "example.org" } }
974 Note: The supported device options are the same ones supported by the '-netdev'
975 command-line argument, which are listed in the '-help' output or QEMU's
981 .name = "netdev_del",
983 .mhandler.cmd_new = qmp_marshal_netdev_del,
990 Remove host network device.
994 - "id": the device's ID, must be unique (json-string)
998 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
1005 .name = "object-add",
1006 .args_type = "qom-type:s,id:s,props:q?",
1007 .mhandler.cmd_new = qmp_marshal_object_add,
1018 - "qom-type": the object's QOM type, i.e. the class name (json-string)
1019 - "id": the object's ID, must be unique (json-string)
1020 - "props": a dictionary of object property values (optional, json-dict)
1024 -> { "execute": "object-add", "arguments": { "qom-type": "rng-random", "id": "rng1",
1025 "props": { "filename": "/dev/hwrng" } } }
1031 .name = "object-del",
1032 .args_type = "id:s",
1033 .mhandler.cmd_new = qmp_marshal_object_del,
1044 - "id": the object's ID (json-string)
1048 -> { "execute": "object-del", "arguments": { "id": "rng1" } }
1056 .name = "block_resize",
1057 .args_type = "device:s?,node-name:s?,size:o",
1058 .mhandler.cmd_new = qmp_marshal_block_resize,
1065 Resize a block image while a guest is running.
1069 - "device": the device's ID, must be unique (json-string)
1070 - "node-name": the node name in the block driver state graph (json-string)
1075 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
1081 .name = "block-stream",
1082 .args_type = "device:B,base:s?,speed:o?,backing-file:s?,on-error:s?",
1083 .mhandler.cmd_new = qmp_marshal_block_stream,
1090 Copy data from a backing file into a block device.
1094 - "device": The device's ID, must be unique (json-string)
1095 - "base": The file name of the backing image above which copying starts
1096 (json-string, optional)
1097 - "backing-file": The backing file string to write into the active layer. This
1098 filename is not validated.
1100 If a pathname string is such that it cannot be resolved by
1101 QEMU, that means that subsequent QMP or HMP commands must use
1102 node-names for the image in question, as filename lookup
1105 If not specified, QEMU will automatically determine the
1106 backing file string to use, or error out if there is no
1107 obvious choice. Care should be taken when specifying the
1108 string, to specify a valid filename or protocol.
1109 (json-string, optional) (Since 2.1)
1110 - "speed": the maximum speed, in bytes per second (json-int, optional)
1111 - "on-error": the action to take on an error (default 'report'). 'stop' and
1112 'enospc' can only be used if the block device supports io-status.
1113 (json-string, optional) (Since 2.1)
1117 -> { "execute": "block-stream", "arguments": { "device": "virtio0",
1118 "base": "/tmp/master.qcow2" } }
1124 .name = "block-commit",
1125 .args_type = "device:B,base:s?,top:s?,backing-file:s?,speed:o?",
1126 .mhandler.cmd_new = qmp_marshal_block_commit,
1133 Live commit of data from overlay image nodes into backing nodes - i.e., writes
1134 data between 'top' and 'base' into 'base'.
1138 - "device": The device's ID, must be unique (json-string)
1139 - "base": The file name of the backing image to write data into.
1140 If not specified, this is the deepest backing image
1141 (json-string, optional)
1142 - "top": The file name of the backing image within the image chain,
1143 which contains the topmost data to be committed down. If
1144 not specified, this is the active layer. (json-string, optional)
1146 - backing-file: The backing file string to write into the overlay
1147 image of 'top'. If 'top' is the active layer,
1148 specifying a backing file string is an error. This
1149 filename is not validated.
1151 If a pathname string is such that it cannot be
1152 resolved by QEMU, that means that subsequent QMP or
1153 HMP commands must use node-names for the image in
1154 question, as filename lookup methods will fail.
1156 If not specified, QEMU will automatically determine
1157 the backing file string to use, or error out if
1158 there is no obvious choice. Care should be taken
1159 when specifying the string, to specify a valid
1160 filename or protocol.
1161 (json-string, optional) (Since 2.1)
1163 If top == base, that is an error.
1164 If top == active, the job will not be completed by itself,
1165 user needs to complete the job with the block-job-complete
1166 command after getting the ready event. (Since 2.0)
1168 If the base image is smaller than top, then the base image
1169 will be resized to be the same size as top. If top is
1170 smaller than the base image, the base will not be
1171 truncated. If you want the base image size to match the
1172 size of the smaller top, you can safely truncate it
1173 yourself once the commit operation successfully completes.
1175 - "speed": the maximum speed, in bytes per second (json-int, optional)
1180 -> { "execute": "block-commit", "arguments": { "device": "virtio0",
1181 "top": "/tmp/snap1.qcow2" } }
1187 .name = "drive-backup",
1188 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1189 "bitmap:s?,on-source-error:s?,on-target-error:s?",
1190 .mhandler.cmd_new = qmp_marshal_drive_backup,
1197 Start a point-in-time copy of a block device to a new destination. The
1198 status of ongoing drive-backup operations can be checked with
1199 query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1200 The operation can be stopped before it has completed using the
1201 block-job-cancel command.
1205 - "device": the name of the device which should be copied.
1207 - "target": the target of the new image. If the file exists, or if it is a
1208 device, the existing file/device will be used as the new
1209 destination. If it does not exist, a new file will be created.
1211 - "format": the format of the new destination, default is to probe if 'mode' is
1212 'existing', else the format of the source
1213 (json-string, optional)
1214 - "sync": what parts of the disk image should be copied to the destination;
1215 possibilities include "full" for all the disk, "top" for only the sectors
1216 allocated in the topmost image, "incremental" for only the dirty sectors in
1217 the bitmap, or "none" to only replicate new I/O (MirrorSyncMode).
1218 - "bitmap": dirty bitmap name for sync==incremental. Must be present if sync
1219 is "incremental", must NOT be present otherwise.
1220 - "mode": whether and how QEMU should create a new image
1221 (NewImageMode, optional, default 'absolute-paths')
1222 - "speed": the maximum speed, in bytes per second (json-int, optional)
1223 - "on-source-error": the action to take on an error on the source, default
1224 'report'. 'stop' and 'enospc' can only be used
1225 if the block device supports io-status.
1226 (BlockdevOnError, optional)
1227 - "on-target-error": the action to take on an error on the target, default
1228 'report' (no limitations, since this applies to
1229 a different block device than device).
1230 (BlockdevOnError, optional)
1233 -> { "execute": "drive-backup", "arguments": { "device": "drive0",
1235 "target": "backup.img" } }
1241 .name = "blockdev-backup",
1242 .args_type = "sync:s,device:B,target:B,speed:i?,"
1243 "on-source-error:s?,on-target-error:s?",
1244 .mhandler.cmd_new = qmp_marshal_blockdev_backup,
1251 The device version of drive-backup: this command takes an existing named device
1256 - "device": the name of the device which should be copied.
1258 - "target": the name of the backup target device. (json-string)
1259 - "sync": what parts of the disk image should be copied to the destination;
1260 possibilities include "full" for all the disk, "top" for only the
1261 sectors allocated in the topmost image, or "none" to only replicate
1262 new I/O (MirrorSyncMode).
1263 - "speed": the maximum speed, in bytes per second (json-int, optional)
1264 - "on-source-error": the action to take on an error on the source, default
1265 'report'. 'stop' and 'enospc' can only be used
1266 if the block device supports io-status.
1267 (BlockdevOnError, optional)
1268 - "on-target-error": the action to take on an error on the target, default
1269 'report' (no limitations, since this applies to
1270 a different block device than device).
1271 (BlockdevOnError, optional)
1274 -> { "execute": "blockdev-backup", "arguments": { "device": "src-id",
1276 "target": "tgt-id" } }
1282 .name = "block-job-set-speed",
1283 .args_type = "device:B,speed:o",
1284 .mhandler.cmd_new = qmp_marshal_block_job_set_speed,
1288 .name = "block-job-cancel",
1289 .args_type = "device:B,force:b?",
1290 .mhandler.cmd_new = qmp_marshal_block_job_cancel,
1293 .name = "block-job-pause",
1294 .args_type = "device:B",
1295 .mhandler.cmd_new = qmp_marshal_block_job_pause,
1298 .name = "block-job-resume",
1299 .args_type = "device:B",
1300 .mhandler.cmd_new = qmp_marshal_block_job_resume,
1303 .name = "block-job-complete",
1304 .args_type = "device:B",
1305 .mhandler.cmd_new = qmp_marshal_block_job_complete,
1308 .name = "transaction",
1309 .args_type = "actions:q,properties:q?",
1310 .mhandler.cmd_new = qmp_marshal_transaction,
1317 Atomically operate on one or more block devices. Operations that are
1318 currently supported:
1322 - blockdev-snapshot-sync
1323 - blockdev-snapshot-internal-sync
1325 - block-dirty-bitmap-add
1326 - block-dirty-bitmap-clear
1328 Refer to the qemu/qapi-schema.json file for minimum required QEMU
1329 versions for these operations. A list of dictionaries is accepted,
1330 that contains the actions to be performed. If there is any failure
1331 performing any of the operations, all operations for the group are
1334 For external snapshots, the dictionary contains the device, the file to use for
1335 the new snapshot, and the format. The default format, if not specified, is
1338 Each new snapshot defaults to being created by QEMU (wiping any
1339 contents if the file already exists), but it is also possible to reuse
1340 an externally-created file. In the latter case, you should ensure that
1341 the new image file has the same contents as the current one; QEMU cannot
1342 perform any meaningful check. Typically this is achieved by using the
1343 current image file as the backing file for the new image.
1345 On failure, the original disks pre-snapshot attempt will be used.
1347 For internal snapshots, the dictionary contains the device and the snapshot's
1348 name. If an internal snapshot matching name already exists, the request will
1349 be rejected. Only some image formats support it, for example, qcow2, rbd,
1352 On failure, qemu will try delete the newly created internal snapshot in the
1353 transaction. When an I/O error occurs during deletion, the user needs to fix
1354 it later with qemu-img or other command.
1359 - "type": the operation to perform (json-string). Possible
1360 values: "drive-backup", "blockdev-backup",
1361 "blockdev-snapshot-sync",
1362 "blockdev-snapshot-internal-sync",
1363 "abort", "block-dirty-bitmap-add",
1364 "block-dirty-bitmap-clear"
1365 - "data": a dictionary. The contents depend on the value
1366 of "type". When "type" is "blockdev-snapshot-sync":
1367 - "device": device name to snapshot (json-string)
1368 - "node-name": graph node name to snapshot (json-string)
1369 - "snapshot-file": name of new image file (json-string)
1370 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1371 - "format": format of new image (json-string, optional)
1372 - "mode": whether and how QEMU should create the snapshot file
1373 (NewImageMode, optional, default "absolute-paths")
1374 When "type" is "blockdev-snapshot-internal-sync":
1375 - "device": device name to snapshot (json-string)
1376 - "name": name of the new snapshot (json-string)
1380 -> { "execute": "transaction",
1381 "arguments": { "actions": [
1382 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd0",
1383 "snapshot-file": "/some/place/my-image",
1384 "format": "qcow2" } },
1385 { "type": "blockdev-snapshot-sync", "data" : { "node-name": "myfile",
1386 "snapshot-file": "/some/place/my-image2",
1387 "snapshot-node-name": "node3432",
1389 "format": "qcow2" } },
1390 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd1",
1391 "snapshot-file": "/some/place/my-image2",
1393 "format": "qcow2" } },
1394 { "type": "blockdev-snapshot-internal-sync", "data" : {
1395 "device": "ide-hd2",
1396 "name": "snapshot0" } } ] } }
1402 .name = "block-dirty-bitmap-add",
1403 .args_type = "node:B,name:s,granularity:i?",
1404 .mhandler.cmd_new = qmp_marshal_block_dirty_bitmap_add,
1409 block-dirty-bitmap-add
1410 ----------------------
1413 Create a dirty bitmap with a name on the device, and start tracking the writes.
1417 - "node": device/node on which to create dirty bitmap (json-string)
1418 - "name": name of the new dirty bitmap (json-string)
1419 - "granularity": granularity to track writes with (int, optional)
1423 -> { "execute": "block-dirty-bitmap-add", "arguments": { "node": "drive0",
1424 "name": "bitmap0" } }
1430 .name = "block-dirty-bitmap-remove",
1431 .args_type = "node:B,name:s",
1432 .mhandler.cmd_new = qmp_marshal_block_dirty_bitmap_remove,
1437 block-dirty-bitmap-remove
1438 -------------------------
1441 Stop write tracking and remove the dirty bitmap that was created with
1442 block-dirty-bitmap-add.
1446 - "node": device/node on which to remove dirty bitmap (json-string)
1447 - "name": name of the dirty bitmap to remove (json-string)
1451 -> { "execute": "block-dirty-bitmap-remove", "arguments": { "node": "drive0",
1452 "name": "bitmap0" } }
1458 .name = "block-dirty-bitmap-clear",
1459 .args_type = "node:B,name:s",
1460 .mhandler.cmd_new = qmp_marshal_block_dirty_bitmap_clear,
1465 block-dirty-bitmap-clear
1466 ------------------------
1469 Reset the dirty bitmap associated with a node so that an incremental backup
1470 from this point in time forward will only backup clusters modified after this
1475 - "node": device/node on which to remove dirty bitmap (json-string)
1476 - "name": name of the dirty bitmap to remove (json-string)
1480 -> { "execute": "block-dirty-bitmap-clear", "arguments": { "node": "drive0",
1481 "name": "bitmap0" } }
1487 .name = "blockdev-snapshot-sync",
1488 .args_type = "device:s?,node-name:s?,snapshot-file:s,snapshot-node-name:s?,format:s?,mode:s?",
1489 .mhandler.cmd_new = qmp_marshal_blockdev_snapshot_sync,
1493 blockdev-snapshot-sync
1494 ----------------------
1496 Synchronous snapshot of a block device. snapshot-file specifies the
1497 target of the new image. If the file exists, or if it is a device, the
1498 snapshot will be created in the existing file/device. If does not
1499 exist, a new file will be created. format specifies the format of the
1500 snapshot image, default is qcow2.
1504 - "device": device name to snapshot (json-string)
1505 - "node-name": graph node name to snapshot (json-string)
1506 - "snapshot-file": name of new image file (json-string)
1507 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1508 - "mode": whether and how QEMU should create the snapshot file
1509 (NewImageMode, optional, default "absolute-paths")
1510 - "format": format of new image (json-string, optional)
1514 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
1516 "/some/place/my-image",
1517 "format": "qcow2" } }
1523 .name = "blockdev-snapshot",
1524 .args_type = "node:s,overlay:s",
1525 .mhandler.cmd_new = qmp_marshal_blockdev_snapshot,
1533 Create a snapshot, by installing 'node' as the backing image of
1534 'overlay'. Additionally, if 'node' is associated with a block
1535 device, the block device changes to using 'overlay' as its new active
1540 - "node": device that will have a snapshot created (json-string)
1541 - "overlay": device that will have 'node' as its backing image (json-string)
1545 -> { "execute": "blockdev-add",
1546 "arguments": { "options": { "driver": "qcow2",
1547 "node-name": "node1534",
1548 "file": { "driver": "file",
1549 "filename": "hd1.qcow2" },
1554 -> { "execute": "blockdev-snapshot", "arguments": { "node": "ide-hd0",
1555 "overlay": "node1534" } }
1561 .name = "blockdev-snapshot-internal-sync",
1562 .args_type = "device:B,name:s",
1563 .mhandler.cmd_new = qmp_marshal_blockdev_snapshot_internal_sync,
1567 blockdev-snapshot-internal-sync
1568 -------------------------------
1570 Synchronously take an internal snapshot of a block device when the format of
1571 image used supports it. If the name is an empty string, or a snapshot with
1572 name already exists, the operation will fail.
1576 - "device": device name to snapshot (json-string)
1577 - "name": name of the new snapshot (json-string)
1581 -> { "execute": "blockdev-snapshot-internal-sync",
1582 "arguments": { "device": "ide-hd0",
1583 "name": "snapshot0" }
1590 .name = "blockdev-snapshot-delete-internal-sync",
1591 .args_type = "device:B,id:s?,name:s?",
1593 qmp_marshal_blockdev_snapshot_delete_internal_sync,
1597 blockdev-snapshot-delete-internal-sync
1598 --------------------------------------
1600 Synchronously delete an internal snapshot of a block device when the format of
1601 image used supports it. The snapshot is identified by name or id or both. One
1602 of name or id is required. If the snapshot is not found, the operation will
1607 - "device": device name (json-string)
1608 - "id": ID of the snapshot (json-string, optional)
1609 - "name": name of the snapshot (json-string, optional)
1613 -> { "execute": "blockdev-snapshot-delete-internal-sync",
1614 "arguments": { "device": "ide-hd0",
1615 "name": "snapshot0" }
1619 "name": "snapshot0",
1621 "date-sec": 1000012,
1623 "vm-clock-sec": 100,
1631 .name = "drive-mirror",
1632 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1633 "node-name:s?,replaces:s?,"
1634 "on-source-error:s?,on-target-error:s?,"
1636 "granularity:i?,buf-size:i?",
1637 .mhandler.cmd_new = qmp_marshal_drive_mirror,
1644 Start mirroring a block device's writes to a new destination. target
1645 specifies the target of the new image. If the file exists, or if it is
1646 a device, it will be used as the new destination for writes. If it does not
1647 exist, a new file will be created. format specifies the format of the
1648 mirror image, default is to probe if mode='existing', else the format
1653 - "device": device name to operate on (json-string)
1654 - "target": name of new image file (json-string)
1655 - "format": format of new image (json-string, optional)
1656 - "node-name": the name of the new block driver state in the node graph
1657 (json-string, optional)
1658 - "replaces": the block driver node name to replace when finished
1659 (json-string, optional)
1660 - "mode": how an image file should be created into the target
1661 file/device (NewImageMode, optional, default 'absolute-paths')
1662 - "speed": maximum speed of the streaming job, in bytes per second
1664 - "granularity": granularity of the dirty bitmap, in bytes (json-int, optional)
1665 - "buf-size": maximum amount of data in flight from source to target, in bytes
1666 (json-int, default 10M)
1667 - "sync": what parts of the disk image should be copied to the destination;
1668 possibilities include "full" for all the disk, "top" for only the sectors
1669 allocated in the topmost image, or "none" to only replicate new I/O
1671 - "on-source-error": the action to take on an error on the source
1672 (BlockdevOnError, default 'report')
1673 - "on-target-error": the action to take on an error on the target
1674 (BlockdevOnError, default 'report')
1675 - "unmap": whether the target sectors should be discarded where source has only
1676 zeroes. (json-bool, optional, default true)
1678 The default value of the granularity is the image cluster size clamped
1679 between 4096 and 65536, if the image format defines one. If the format
1680 does not define a cluster size, the default value of the granularity
1686 -> { "execute": "drive-mirror", "arguments": { "device": "ide-hd0",
1687 "target": "/some/place/my-image",
1689 "format": "qcow2" } }
1695 .name = "blockdev-mirror",
1696 .args_type = "sync:s,device:B,target:B,replaces:s?,speed:i?,"
1697 "on-source-error:s?,on-target-error:s?,"
1698 "granularity:i?,buf-size:i?",
1699 .mhandler.cmd_new = qmp_marshal_blockdev_mirror,
1706 Start mirroring a block device's writes to another block device. target
1707 specifies the target of mirror operation.
1711 - "device": device name to operate on (json-string)
1712 - "target": device name to mirror to (json-string)
1713 - "replaces": the block driver node name to replace when finished
1714 (json-string, optional)
1715 - "speed": maximum speed of the streaming job, in bytes per second
1717 - "granularity": granularity of the dirty bitmap, in bytes (json-int, optional)
1718 - "buf_size": maximum amount of data in flight from source to target, in bytes
1719 (json-int, default 10M)
1720 - "sync": what parts of the disk image should be copied to the destination;
1721 possibilities include "full" for all the disk, "top" for only the sectors
1722 allocated in the topmost image, or "none" to only replicate new I/O
1724 - "on-source-error": the action to take on an error on the source
1725 (BlockdevOnError, default 'report')
1726 - "on-target-error": the action to take on an error on the target
1727 (BlockdevOnError, default 'report')
1729 The default value of the granularity is the image cluster size clamped
1730 between 4096 and 65536, if the image format defines one. If the format
1731 does not define a cluster size, the default value of the granularity
1736 -> { "execute": "blockdev-mirror", "arguments": { "device": "ide-hd0",
1737 "target": "target0",
1743 .name = "change-backing-file",
1744 .args_type = "device:s,image-node-name:s,backing-file:s",
1745 .mhandler.cmd_new = qmp_marshal_change_backing_file,
1753 Change the backing file in the image file metadata. This does not cause
1754 QEMU to reopen the image file to reparse the backing filename (it may,
1755 however, perform a reopen to change permissions from r/o -> r/w -> r/o,
1756 if needed). The new backing file string is written into the image file
1757 metadata, and the QEMU internal strings are updated.
1761 - "image-node-name": The name of the block driver state node of the
1762 image to modify. The "device" is argument is used to
1763 verify "image-node-name" is in the chain described by
1765 (json-string, optional)
1767 - "device": The name of the device.
1770 - "backing-file": The string to write as the backing file. This string is
1771 not validated, so care should be taken when specifying
1772 the string or the image chain may not be able to be
1776 Returns: Nothing on success
1777 If "device" does not exist or cannot be determined, DeviceNotFound
1783 .args_type = "value:M",
1784 .mhandler.cmd_new = qmp_marshal_balloon,
1791 Request VM to change its memory allocation (in bytes).
1795 - "value": New memory allocation (json-int)
1799 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1806 .args_type = "name:s,up:b",
1807 .mhandler.cmd_new = qmp_marshal_set_link,
1814 Change the link status of a network adapter.
1818 - "name": network device name (json-string)
1819 - "up": status is up (json-bool)
1823 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
1831 .args_type = "name:s",
1832 .mhandler.cmd_new = qmp_marshal_get_link,
1839 Get the link status of a network adapter.
1843 - "name": network device name (json-string)
1847 -> { "execute": "get_link", "arguments": { "name": "e1000.0" } }
1848 <- { "return": {on|off} }
1854 .args_type = "fdname:s",
1855 .params = "getfd name",
1856 .help = "receive a file descriptor via SCM rights and assign it a name",
1857 .mhandler.cmd_new = qmp_marshal_getfd,
1864 Receive a file descriptor via SCM rights and assign it a name.
1868 - "fdname": file descriptor name (json-string)
1872 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1877 (1) If the name specified by the "fdname" argument already exists,
1878 the file descriptor assigned to it will be closed and replaced
1879 by the received file descriptor.
1880 (2) The 'closefd' command can be used to explicitly close the file
1881 descriptor when it is no longer needed.
1887 .args_type = "fdname:s",
1888 .params = "closefd name",
1889 .help = "close a file descriptor previously passed via SCM rights",
1890 .mhandler.cmd_new = qmp_marshal_closefd,
1897 Close a file descriptor previously passed via SCM rights.
1901 - "fdname": file descriptor name (json-string)
1905 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1912 .args_type = "fdset-id:i?,opaque:s?",
1913 .params = "add-fd fdset-id opaque",
1914 .help = "Add a file descriptor, that was passed via SCM rights, to an fd set",
1915 .mhandler.cmd_new = qmp_marshal_add_fd,
1922 Add a file descriptor, that was passed via SCM rights, to an fd set.
1926 - "fdset-id": The ID of the fd set to add the file descriptor to.
1927 (json-int, optional)
1928 - "opaque": A free-form string that can be used to describe the fd.
1929 (json-string, optional)
1931 Return a json-object with the following information:
1933 - "fdset-id": The ID of the fd set that the fd was added to. (json-int)
1934 - "fd": The file descriptor that was received via SCM rights and added to the
1939 -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1940 <- { "return": { "fdset-id": 1, "fd": 3 } }
1944 (1) The list of fd sets is shared by all monitor connections.
1945 (2) If "fdset-id" is not specified, a new fd set will be created.
1950 .name = "remove-fd",
1951 .args_type = "fdset-id:i,fd:i?",
1952 .params = "remove-fd fdset-id fd",
1953 .help = "Remove a file descriptor from an fd set",
1954 .mhandler.cmd_new = qmp_marshal_remove_fd,
1961 Remove a file descriptor from an fd set.
1965 - "fdset-id": The ID of the fd set that the file descriptor belongs to.
1967 - "fd": The file descriptor that is to be removed. (json-int, optional)
1971 -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1976 (1) The list of fd sets is shared by all monitor connections.
1977 (2) If "fd" is not specified, all file descriptors in "fdset-id" will be
1983 .name = "query-fdsets",
1985 .help = "Return information describing all fd sets",
1986 .mhandler.cmd_new = qmp_marshal_query_fdsets,
1993 Return information describing all fd sets.
1999 -> { "execute": "query-fdsets" }
2005 "opaque": "rdonly:/path/to/file"
2009 "opaque": "rdwr:/path/to/file"
2028 Note: The list of fd sets is shared by all monitor connections.
2033 .name = "block_passwd",
2034 .args_type = "device:s?,node-name:s?,password:s",
2035 .mhandler.cmd_new = qmp_marshal_block_passwd,
2042 Set the password of encrypted block devices.
2046 - "device": device name (json-string)
2047 - "node-name": name in the block driver state graph (json-string)
2048 - "password": password (json-string)
2052 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
2053 "password": "12345" } }
2059 .name = "block_set_io_throttle",
2060 .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?,bps_max_length:l?,bps_rd_max_length:l?,bps_wr_max_length:l?,iops_max_length:l?,iops_rd_max_length:l?,iops_wr_max_length:l?,iops_size:l?,group:s?",
2061 .mhandler.cmd_new = qmp_marshal_block_set_io_throttle,
2065 block_set_io_throttle
2068 Change I/O throttle limits for a block drive.
2072 - "device": device name (json-string)
2073 - "bps": total throughput limit in bytes per second (json-int)
2074 - "bps_rd": read throughput limit in bytes per second (json-int)
2075 - "bps_wr": write throughput limit in bytes per second (json-int)
2076 - "iops": total I/O operations per second (json-int)
2077 - "iops_rd": read I/O operations per second (json-int)
2078 - "iops_wr": write I/O operations per second (json-int)
2079 - "bps_max": total throughput limit during bursts, in bytes (json-int, optional)
2080 - "bps_rd_max": read throughput limit during bursts, in bytes (json-int, optional)
2081 - "bps_wr_max": write throughput limit during bursts, in bytes (json-int, optional)
2082 - "iops_max": total I/O operations per second during bursts (json-int, optional)
2083 - "iops_rd_max": read I/O operations per second during bursts (json-int, optional)
2084 - "iops_wr_max": write I/O operations per second during bursts (json-int, optional)
2085 - "bps_max_length": maximum length of the @bps_max burst period, in seconds (json-int, optional)
2086 - "bps_rd_max_length": maximum length of the @bps_rd_max burst period, in seconds (json-int, optional)
2087 - "bps_wr_max_length": maximum length of the @bps_wr_max burst period, in seconds (json-int, optional)
2088 - "iops_max_length": maximum length of the @iops_max burst period, in seconds (json-int, optional)
2089 - "iops_rd_max_length": maximum length of the @iops_rd_max burst period, in seconds (json-int, optional)
2090 - "iops_wr_max_length": maximum length of the @iops_wr_max burst period, in seconds (json-int, optional)
2091 - "iops_size": I/O size in bytes when limiting (json-int, optional)
2092 - "group": throttle group name (json-string, optional)
2096 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
2109 "bps_max_length": 60,
2116 .name = "set_password",
2117 .args_type = "protocol:s,password:s,connected:s?",
2118 .mhandler.cmd_new = qmp_marshal_set_password,
2125 Set the password for vnc/spice protocols.
2129 - "protocol": protocol name (json-string)
2130 - "password": password (json-string)
2131 - "connected": [ keep | disconnect | fail ] (json-string, optional)
2135 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
2136 "password": "secret" } }
2142 .name = "expire_password",
2143 .args_type = "protocol:s,time:s",
2144 .mhandler.cmd_new = qmp_marshal_expire_password,
2151 Set the password expire time for vnc/spice protocols.
2155 - "protocol": protocol name (json-string)
2156 - "time": [ now | never | +secs | secs ] (json-string)
2160 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
2167 .name = "add_client",
2168 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
2169 .mhandler.cmd_new = qmp_marshal_add_client,
2176 Add a graphics client
2180 - "protocol": protocol name (json-string)
2181 - "fdname": file descriptor name (json-string)
2182 - "skipauth": whether to skip authentication (json-bool, optional)
2183 - "tls": whether to perform TLS (json-bool, optional)
2187 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
2188 "fdname": "myclient" } }
2193 .name = "qmp_capabilities",
2196 .help = "enable QMP capabilities",
2197 .mhandler.cmd_new = qmp_capabilities,
2204 Enable QMP capabilities.
2210 -> { "execute": "qmp_capabilities" }
2213 Note: This command must be issued before issuing any other command.
2218 .name = "human-monitor-command",
2219 .args_type = "command-line:s,cpu-index:i?",
2220 .mhandler.cmd_new = qmp_marshal_human_monitor_command,
2224 human-monitor-command
2225 ---------------------
2227 Execute a Human Monitor command.
2231 - command-line: the command name and its arguments, just like the
2232 Human Monitor's shell (json-string)
2233 - cpu-index: select the CPU number to be used by commands which access CPU
2234 data, like 'info registers'. The Monitor selects CPU 0 if this
2235 argument is not provided (json-int, optional)
2239 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
2240 <- { "return": "kvm support: enabled\r\n" }
2244 (1) The Human Monitor is NOT an stable interface, this means that command
2245 names, arguments and responses can change or be removed at ANY time.
2246 Applications that rely on long term stability guarantees should NOT
2251 o This command is stateless, this means that commands that depend
2252 on state information (such as getfd) might not work
2254 o Commands that prompt the user for data (eg. 'cont' when the block
2255 device is encrypted) don't currently work
2260 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
2261 HXCOMM this! We will possibly move query commands definitions inside those
2262 HXCOMM sections, just like regular commands.
2272 Return a json-object with the following information:
2274 - "qemu": A json-object containing three integer values:
2275 - "major": QEMU's major version (json-int)
2276 - "minor": QEMU's minor version (json-int)
2277 - "micro": QEMU's micro version (json-int)
2278 - "package": package's version (json-string)
2282 -> { "execute": "query-version" }
2297 .name = "query-version",
2299 .mhandler.cmd_new = qmp_marshal_query_version,
2306 List QMP available commands.
2308 Each command is represented by a json-object, the returned value is a json-array
2311 Each json-object contain:
2313 - "name": command's name (json-string)
2317 -> { "execute": "query-commands" }
2321 "name":"query-balloon"
2324 "name":"system_powerdown"
2329 Note: This example has been shortened as the real response is too long.
2334 .name = "query-commands",
2336 .mhandler.cmd_new = qmp_marshal_query_commands,
2343 List QMP available events.
2345 Each event is represented by a json-object, the returned value is a json-array
2348 Each json-object contains:
2350 - "name": event's name (json-string)
2354 -> { "execute": "query-events" }
2366 Note: This example has been shortened as the real response is too long.
2371 .name = "query-events",
2373 .mhandler.cmd_new = qmp_marshal_query_events,
2380 Return the QMP wire schema. The returned value is a json-array of
2381 named schema entities. Entities are commands, events and various
2382 types. See docs/qapi-code-gen.txt for information on their structure
2388 .name = "query-qmp-schema",
2390 .mhandler.cmd_new = qmp_query_qmp_schema,
2397 Each device is represented by a json-object. The returned value is a json-array
2400 Each json-object contain the following:
2402 - "label": device's label (json-string)
2403 - "filename": device's file (json-string)
2404 - "frontend-open": open/closed state of the frontend device attached to this
2409 -> { "execute": "query-chardev" }
2413 "label": "charchannel0",
2414 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.agent,server",
2415 "frontend-open": false
2418 "label": "charmonitor",
2419 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.monitor,server",
2420 "frontend-open": true
2423 "label": "charserial0",
2424 "filename": "pty:/dev/pts/2",
2425 "frontend-open": true
2433 .name = "query-chardev",
2435 .mhandler.cmd_new = qmp_marshal_query_chardev,
2439 query-chardev-backends
2442 List available character device backends.
2444 Each backend is represented by a json-object, the returned value is a json-array
2447 Each json-object contains:
2449 - "name": backend name (json-string)
2453 -> { "execute": "query-chardev-backends" }
2474 .name = "query-chardev-backends",
2476 .mhandler.cmd_new = qmp_marshal_query_chardev_backends,
2483 Show the block devices.
2485 Each block device information is stored in a json-object and the returned value
2486 is a json-array of all devices.
2488 Each json-object contain the following:
2490 - "device": device name (json-string)
2491 - "type": device type (json-string)
2492 - deprecated, retained for backward compatibility
2493 - Possible values: "unknown"
2494 - "removable": true if the device is removable, false otherwise (json-bool)
2495 - "locked": true if the device is locked, false otherwise (json-bool)
2496 - "tray_open": only present if removable, true if the device has a tray,
2497 and it is open (json-bool)
2498 - "inserted": only present if the device is inserted, it is a json-object
2499 containing the following:
2500 - "file": device file name (json-string)
2501 - "ro": true if read-only, false otherwise (json-bool)
2502 - "drv": driver format name (json-string)
2503 - Possible values: "blkdebug", "bochs", "cloop", "dmg",
2504 "file", "file", "ftp", "ftps", "host_cdrom",
2505 "host_device", "http", "https",
2506 "nbd", "parallels", "qcow", "qcow2", "raw",
2507 "tftp", "vdi", "vmdk", "vpc", "vvfat"
2508 - "backing_file": backing file name (json-string, optional)
2509 - "backing_file_depth": number of files in the backing file chain (json-int)
2510 - "encrypted": true if encrypted, false otherwise (json-bool)
2511 - "bps": limit total bytes per second (json-int)
2512 - "bps_rd": limit read bytes per second (json-int)
2513 - "bps_wr": limit write bytes per second (json-int)
2514 - "iops": limit total I/O operations per second (json-int)
2515 - "iops_rd": limit read operations per second (json-int)
2516 - "iops_wr": limit write operations per second (json-int)
2517 - "bps_max": total max in bytes (json-int)
2518 - "bps_rd_max": read max in bytes (json-int)
2519 - "bps_wr_max": write max in bytes (json-int)
2520 - "iops_max": total I/O operations max (json-int)
2521 - "iops_rd_max": read I/O operations max (json-int)
2522 - "iops_wr_max": write I/O operations max (json-int)
2523 - "iops_size": I/O size when limiting by iops (json-int)
2524 - "detect_zeroes": detect and optimize zero writing (json-string)
2525 - Possible values: "off", "on", "unmap"
2526 - "write_threshold": write offset threshold in bytes, a event will be
2527 emitted if crossed. Zero if disabled (json-int)
2528 - "image": the detail of the image, it is a json-object containing
2530 - "filename": image file name (json-string)
2531 - "format": image format (json-string)
2532 - "virtual-size": image capacity in bytes (json-int)
2533 - "dirty-flag": true if image is not cleanly closed, not present
2534 means clean (json-bool, optional)
2535 - "actual-size": actual size on disk in bytes of the image, not
2536 present when image does not support thin
2537 provision (json-int, optional)
2538 - "cluster-size": size of a cluster in bytes, not present if image
2539 format does not support it (json-int, optional)
2540 - "encrypted": true if the image is encrypted, not present means
2541 false or the image format does not support
2542 encryption (json-bool, optional)
2543 - "backing_file": backing file name, not present means no backing
2544 file is used or the image format does not
2545 support backing file chain
2546 (json-string, optional)
2547 - "full-backing-filename": full path of the backing file, not
2548 present if it equals backing_file or no
2549 backing file is used
2550 (json-string, optional)
2551 - "backing-filename-format": the format of the backing file, not
2552 present means unknown or no backing
2553 file (json-string, optional)
2554 - "snapshots": the internal snapshot info, it is an optional list
2555 of json-object containing the following:
2556 - "id": unique snapshot id (json-string)
2557 - "name": snapshot name (json-string)
2558 - "vm-state-size": size of the VM state in bytes (json-int)
2559 - "date-sec": UTC date of the snapshot in seconds (json-int)
2560 - "date-nsec": fractional part in nanoseconds to be used with
2562 - "vm-clock-sec": VM clock relative to boot in seconds
2564 - "vm-clock-nsec": fractional part in nanoseconds to be used
2565 with vm-clock-sec (json-int)
2566 - "backing-image": the detail of the backing image, it is an
2567 optional json-object only present when a
2568 backing image present for this image
2570 - "io-status": I/O operation status, only present if the device supports it
2571 and the VM is configured to stop on errors. It's always reset
2572 to "ok" when the "cont" command is issued (json_string, optional)
2573 - Possible values: "ok", "failed", "nospace"
2577 -> { "execute": "query-block" }
2582 "device":"ide0-hd0",
2589 "file":"disks/test.qcow2",
2590 "backing_file_depth":1,
2604 "detect_zeroes": "on",
2605 "write_threshold": 0,
2607 "filename":"disks/test.qcow2",
2609 "virtual-size":2048000,
2610 "backing_file":"base.qcow2",
2611 "full-backing-filename":"disks/base.qcow2",
2612 "backing-filename-format":"qcow2",
2616 "name": "snapshot1",
2618 "date-sec": 10000200,
2620 "vm-clock-sec": 206,
2625 "filename":"disks/base.qcow2",
2627 "virtual-size":2048000
2635 "device":"ide1-cd0",
2658 .name = "query-block",
2660 .mhandler.cmd_new = qmp_marshal_query_block,
2667 Show block device statistics.
2669 Each device statistic information is stored in a json-object and the returned
2670 value is a json-array of all devices.
2672 Each json-object contain the following:
2674 - "device": device name (json-string)
2675 - "stats": A json-object with the statistics information, it contains:
2676 - "rd_bytes": bytes read (json-int)
2677 - "wr_bytes": bytes written (json-int)
2678 - "rd_operations": read operations (json-int)
2679 - "wr_operations": write operations (json-int)
2680 - "flush_operations": cache flush operations (json-int)
2681 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
2682 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
2683 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
2684 - "wr_highest_offset": The offset after the greatest byte written to the
2685 BlockDriverState since it has been opened (json-int)
2686 - "rd_merged": number of read requests that have been merged into
2687 another request (json-int)
2688 - "wr_merged": number of write requests that have been merged into
2689 another request (json-int)
2690 - "idle_time_ns": time since the last I/O operation, in
2691 nanoseconds. If the field is absent it means
2692 that there haven't been any operations yet
2693 (json-int, optional)
2694 - "failed_rd_operations": number of failed read operations
2696 - "failed_wr_operations": number of failed write operations
2698 - "failed_flush_operations": number of failed flush operations
2700 - "invalid_rd_operations": number of invalid read operations
2702 - "invalid_wr_operations": number of invalid write operations
2704 - "invalid_flush_operations": number of invalid flush operations
2706 - "account_invalid": whether invalid operations are included in
2707 the last access statistics (json-bool)
2708 - "account_failed": whether failed operations are included in the
2709 latency and last access statistics
2711 - "timed_stats": A json-array containing statistics collected in
2712 specific intervals, with the following members:
2713 - "interval_length": interval used for calculating the
2714 statistics, in seconds (json-int)
2715 - "min_rd_latency_ns": minimum latency of read operations in
2716 the defined interval, in nanoseconds
2718 - "min_wr_latency_ns": minimum latency of write operations in
2719 the defined interval, in nanoseconds
2721 - "min_flush_latency_ns": minimum latency of flush operations
2722 in the defined interval, in
2723 nanoseconds (json-int)
2724 - "max_rd_latency_ns": maximum latency of read operations in
2725 the defined interval, in nanoseconds
2727 - "max_wr_latency_ns": maximum latency of write operations in
2728 the defined interval, in nanoseconds
2730 - "max_flush_latency_ns": maximum latency of flush operations
2731 in the defined interval, in
2732 nanoseconds (json-int)
2733 - "avg_rd_latency_ns": average latency of read operations in
2734 the defined interval, in nanoseconds
2736 - "avg_wr_latency_ns": average latency of write operations in
2737 the defined interval, in nanoseconds
2739 - "avg_flush_latency_ns": average latency of flush operations
2740 in the defined interval, in
2741 nanoseconds (json-int)
2742 - "avg_rd_queue_depth": average number of pending read
2743 operations in the defined interval
2745 - "avg_wr_queue_depth": average number of pending write
2746 operations in the defined interval
2748 - "parent": Contains recursively the statistics of the underlying
2749 protocol (e.g. the host file for a qcow2 image). If there is
2750 no underlying protocol, this field is omitted
2751 (json-object, optional)
2755 -> { "execute": "query-blockstats" }
2759 "device":"ide0-hd0",
2762 "wr_highest_offset":3686448128,
2764 "wr_operations":751,
2765 "rd_bytes":122567168,
2766 "rd_operations":36772
2767 "wr_total_times_ns":313253456
2768 "rd_total_times_ns":3465673657
2769 "flush_total_times_ns":49653
2770 "flush_operations":61,
2773 "idle_time_ns":2953431879,
2774 "account_invalid":true,
2775 "account_failed":false
2779 "wr_highest_offset":2821110784,
2781 "wr_operations":692,
2782 "rd_bytes":122739200,
2783 "rd_operations":36604
2784 "flush_operations":51,
2785 "wr_total_times_ns":313253456
2786 "rd_total_times_ns":3465673657
2787 "flush_total_times_ns":49653,
2790 "idle_time_ns":2953431879,
2791 "account_invalid":true,
2792 "account_failed":false
2796 "device":"ide1-cd0",
2798 "wr_highest_offset":0,
2803 "flush_operations":0,
2804 "wr_total_times_ns":0
2805 "rd_total_times_ns":0
2806 "flush_total_times_ns":0,
2809 "account_invalid":false,
2810 "account_failed":false
2816 "wr_highest_offset":0,
2821 "flush_operations":0,
2822 "wr_total_times_ns":0
2823 "rd_total_times_ns":0
2824 "flush_total_times_ns":0,
2827 "account_invalid":false,
2828 "account_failed":false
2834 "wr_highest_offset":0,
2839 "flush_operations":0,
2840 "wr_total_times_ns":0
2841 "rd_total_times_ns":0
2842 "flush_total_times_ns":0,
2845 "account_invalid":false,
2846 "account_failed":false
2855 .name = "query-blockstats",
2856 .args_type = "query-nodes:b?",
2857 .mhandler.cmd_new = qmp_marshal_query_blockstats,
2864 Show CPU information.
2866 Return a json-array. Each CPU is represented by a json-object, which contains:
2868 - "CPU": CPU index (json-int)
2869 - "current": true if this is the current CPU, false otherwise (json-bool)
2870 - "halted": true if the cpu is halted, false otherwise (json-bool)
2871 - "qom_path": path to the CPU object in the QOM tree (json-str)
2872 - "arch": architecture of the cpu, which determines what additional
2873 keys will be present (json-str)
2874 - Current program counter. The key's name depends on the architecture:
2875 "pc": i386/x86_64 (json-int)
2876 "nip": PPC (json-int)
2877 "pc" and "npc": sparc (json-int)
2878 "PC": mips (json-int)
2879 - "thread_id": ID of the underlying host thread (json-int)
2883 -> { "execute": "query-cpus" }
2890 "qom_path":"/machine/unattached/device[0]",
2899 "qom_path":"/machine/unattached/device[2]",
2910 .name = "query-cpus",
2912 .mhandler.cmd_new = qmp_marshal_query_cpus,
2919 Returns a list of information about each iothread.
2921 Note this list excludes the QEMU main loop thread, which is not declared
2922 using the -object iothread command-line option. It is always the main thread
2925 Return a json-array. Each iothread is represented by a json-object, which contains:
2927 - "id": name of iothread (json-str)
2928 - "thread-id": ID of the underlying host thread (json-int)
2932 -> { "execute": "query-iothreads" }
2949 .name = "query-iothreads",
2951 .mhandler.cmd_new = qmp_marshal_query_iothreads,
2958 PCI buses and devices information.
2960 The returned value is a json-array of all buses. Each bus is represented by
2961 a json-object, which has a key with a json-array of all PCI devices attached
2962 to it. Each device is represented by a json-object.
2964 The bus json-object contains the following:
2966 - "bus": bus number (json-int)
2967 - "devices": a json-array of json-objects, each json-object represents a
2970 The PCI device json-object contains the following:
2972 - "bus": identical to the parent's bus number (json-int)
2973 - "slot": slot number (json-int)
2974 - "function": function number (json-int)
2975 - "class_info": a json-object containing:
2976 - "desc": device class description (json-string, optional)
2977 - "class": device class number (json-int)
2978 - "id": a json-object containing:
2979 - "device": device ID (json-int)
2980 - "vendor": vendor ID (json-int)
2981 - "irq": device's IRQ if assigned (json-int, optional)
2982 - "qdev_id": qdev id string (json-string)
2983 - "pci_bridge": It's a json-object, only present if this device is a
2984 PCI bridge, contains:
2985 - "bus": bus number (json-int)
2986 - "secondary": secondary bus number (json-int)
2987 - "subordinate": subordinate bus number (json-int)
2988 - "io_range": I/O memory range information, a json-object with the
2990 - "base": base address, in bytes (json-int)
2991 - "limit": limit address, in bytes (json-int)
2992 - "memory_range": memory range information, a json-object with the
2994 - "base": base address, in bytes (json-int)
2995 - "limit": limit address, in bytes (json-int)
2996 - "prefetchable_range": Prefetchable memory range information, a
2997 json-object with the following members:
2998 - "base": base address, in bytes (json-int)
2999 - "limit": limit address, in bytes (json-int)
3000 - "devices": a json-array of PCI devices if there's any attached, each
3001 each element is represented by a json-object, which contains
3002 the same members of the 'PCI device json-object' described
3004 - "regions": a json-array of json-objects, each json-object represents a
3005 memory region of this device
3007 The memory range json-object contains the following:
3009 - "base": base memory address (json-int)
3010 - "limit": limit value (json-int)
3012 The region json-object can be an I/O region or a memory region, an I/O region
3013 json-object contains the following:
3015 - "type": "io" (json-string, fixed)
3016 - "bar": BAR number (json-int)
3017 - "address": memory address (json-int)
3018 - "size": memory size (json-int)
3020 A memory region json-object contains the following:
3022 - "type": "memory" (json-string, fixed)
3023 - "bar": BAR number (json-int)
3024 - "address": memory address (json-int)
3025 - "size": memory size (json-int)
3026 - "mem_type_64": true or false (json-bool)
3027 - "prefetch": true or false (json-bool)
3031 -> { "execute": "query-pci" }
3043 "desc":"Host bridge"
3077 "desc":"IDE controller"
3099 "desc":"VGA controller"
3109 "mem_type_64":false,
3112 "address":4026531840,
3117 "mem_type_64":false,
3120 "address":4060086272,
3125 "mem_type_64":false,
3140 "desc":"RAM controller"
3161 Note: This example has been shortened as the real response is too long.
3166 .name = "query-pci",
3168 .mhandler.cmd_new = qmp_marshal_query_pci,
3175 Show KVM information.
3177 Return a json-object with the following information:
3179 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
3180 - "present": true if QEMU has KVM support, false otherwise (json-bool)
3184 -> { "execute": "query-kvm" }
3185 <- { "return": { "enabled": true, "present": true } }
3190 .name = "query-kvm",
3192 .mhandler.cmd_new = qmp_marshal_query_kvm,
3199 Return a json-object with the following information:
3201 - "running": true if the VM is running, or false if it is paused (json-bool)
3202 - "singlestep": true if the VM is in single step mode,
3203 false otherwise (json-bool)
3204 - "status": one of the following values (json-string)
3205 "debug" - QEMU is running on a debugger
3206 "inmigrate" - guest is paused waiting for an incoming migration
3207 "internal-error" - An internal error that prevents further guest
3208 execution has occurred
3209 "io-error" - the last IOP has failed and the device is configured
3210 to pause on I/O errors
3211 "paused" - guest has been paused via the 'stop' command
3212 "postmigrate" - guest is paused following a successful 'migrate'
3213 "prelaunch" - QEMU was started with -S and guest has not started
3214 "finish-migrate" - guest is paused to finish the migration process
3215 "restore-vm" - guest is paused to restore VM state
3216 "running" - guest is actively running
3217 "save-vm" - guest is paused to save the VM state
3218 "shutdown" - guest is shut down (and -no-shutdown is in use)
3219 "watchdog" - the watchdog action is configured to pause and
3224 -> { "execute": "query-status" }
3225 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
3230 .name = "query-status",
3232 .mhandler.cmd_new = qmp_marshal_query_status,
3239 Show VM mice information.
3241 Each mouse is represented by a json-object, the returned value is a json-array
3244 The mouse json-object contains the following:
3246 - "name": mouse's name (json-string)
3247 - "index": mouse's index (json-int)
3248 - "current": true if this mouse is receiving events, false otherwise (json-bool)
3249 - "absolute": true if the mouse generates absolute input events (json-bool)
3253 -> { "execute": "query-mice" }
3257 "name":"QEMU Microsoft Mouse",
3263 "name":"QEMU PS/2 Mouse",
3274 .name = "query-mice",
3276 .mhandler.cmd_new = qmp_marshal_query_mice,
3283 Show VNC server information.
3285 Return a json-object with server information. Connected clients are returned
3286 as a json-array of json-objects.
3288 The main json-object contains the following:
3290 - "enabled": true or false (json-bool)
3291 - "host": server's IP address (json-string)
3292 - "family": address family (json-string)
3293 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3294 - "service": server's port number (json-string)
3295 - "auth": authentication method (json-string)
3296 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
3297 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
3298 "vencrypt+plain", "vencrypt+tls+none",
3299 "vencrypt+tls+plain", "vencrypt+tls+sasl",
3300 "vencrypt+tls+vnc", "vencrypt+x509+none",
3301 "vencrypt+x509+plain", "vencrypt+x509+sasl",
3302 "vencrypt+x509+vnc", "vnc"
3303 - "clients": a json-array of all connected clients
3305 Clients are described by a json-object, each one contain the following:
3307 - "host": client's IP address (json-string)
3308 - "family": address family (json-string)
3309 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3310 - "service": client's port number (json-string)
3311 - "x509_dname": TLS dname (json-string, optional)
3312 - "sasl_username": SASL username (json-string, optional)
3316 -> { "execute": "query-vnc" }
3337 .name = "query-vnc",
3339 .mhandler.cmd_new = qmp_marshal_query_vnc,
3342 .name = "query-vnc-servers",
3344 .mhandler.cmd_new = qmp_marshal_query_vnc_servers,
3351 Show SPICE server information.
3353 Return a json-object with server information. Connected clients are returned
3354 as a json-array of json-objects.
3356 The main json-object contains the following:
3358 - "enabled": true or false (json-bool)
3359 - "host": server's IP address (json-string)
3360 - "port": server's port number (json-int, optional)
3361 - "tls-port": server's port number (json-int, optional)
3362 - "auth": authentication method (json-string)
3363 - Possible values: "none", "spice"
3364 - "channels": a json-array of all active channels clients
3366 Channels are described by a json-object, each one contain the following:
3368 - "host": client's IP address (json-string)
3369 - "family": address family (json-string)
3370 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3371 - "port": client's port number (json-string)
3372 - "connection-id": spice connection id. All channels with the same id
3373 belong to the same spice session (json-int)
3374 - "channel-type": channel type. "1" is the main control channel, filter for
3375 this one if you want track spice sessions only (json-int)
3376 - "channel-id": channel id. Usually "0", might be different needed when
3377 multiple channels of the same type exist, such as multiple
3378 display channels in a multihead setup (json-int)
3379 - "tls": whether the channel is encrypted (json-bool)
3383 -> { "execute": "query-spice" }
3396 "connection-id": 1804289383,
3397 "host": "127.0.0.1",
3405 "connection-id": 1804289383,
3406 "host": "127.0.0.1",
3410 [ ... more channels follow ... ]
3417 #if defined(CONFIG_SPICE)
3419 .name = "query-spice",
3421 .mhandler.cmd_new = qmp_marshal_query_spice,
3431 Return a json-object with the following information:
3433 - "name": VM's name (json-string, optional)
3437 -> { "execute": "query-name" }
3438 <- { "return": { "name": "qemu-name" } }
3443 .name = "query-name",
3445 .mhandler.cmd_new = qmp_marshal_query_name,
3454 Return a json-object with the following information:
3456 - "UUID": Universally Unique Identifier (json-string)
3460 -> { "execute": "query-uuid" }
3461 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
3466 .name = "query-uuid",
3468 .mhandler.cmd_new = qmp_marshal_query_uuid,
3472 query-command-line-options
3473 --------------------------
3475 Show command line option schema.
3477 Return a json-array of command line option schema for all options (or for
3478 the given option), returning an error if the given option doesn't exist.
3480 Each array entry contains the following:
3482 - "option": option name (json-string)
3483 - "parameters": a json-array describes all parameters of the option:
3484 - "name": parameter name (json-string)
3485 - "type": parameter type (one of 'string', 'boolean', 'number',
3487 - "help": human readable description of the parameter
3488 (json-string, optional)
3489 - "default": default value string for the parameter
3490 (json-string, optional)
3494 -> { "execute": "query-command-line-options", "arguments": { "option": "option-rom" } }
3503 "name": "bootindex",
3507 "option": "option-rom"
3515 .name = "query-command-line-options",
3516 .args_type = "option:s?",
3517 .mhandler.cmd_new = qmp_marshal_query_command_line_options,
3526 Return a json-object. If migration is active there will be another json-object
3527 with RAM migration status and if block migration is active another one with
3528 block migration status.
3530 The main json-object contains the following:
3532 - "status": migration status (json-string)
3533 - Possible values: "setup", "active", "completed", "failed", "cancelled"
3534 - "total-time": total amount of ms since migration started. If
3535 migration has ended, it returns the total migration
3537 - "setup-time" amount of setup time in milliseconds _before_ the
3538 iterations begin but _after_ the QMP command is issued.
3539 This is designed to provide an accounting of any activities
3540 (such as RDMA pinning) which may be expensive, but do not
3541 actually occur during the iterative migration rounds
3542 themselves. (json-int)
3543 - "downtime": only present when migration has finished correctly
3544 total amount in ms for downtime that happened (json-int)
3545 - "expected-downtime": only present while migration is active
3546 total amount in ms for downtime that was calculated on
3547 the last bitmap round (json-int)
3548 - "ram": only present if "status" is "active", it is a json-object with the
3549 following RAM information:
3550 - "transferred": amount transferred in bytes (json-int)
3551 - "remaining": amount remaining to transfer in bytes (json-int)
3552 - "total": total amount of memory in bytes (json-int)
3553 - "duplicate": number of pages filled entirely with the same
3555 These are sent over the wire much more efficiently.
3556 - "skipped": number of skipped zero pages (json-int)
3557 - "normal" : number of whole pages transferred. I.e. they
3558 were not sent as duplicate or xbzrle pages (json-int)
3559 - "normal-bytes" : number of bytes transferred in whole
3560 pages. This is just normal pages times size of one page,
3561 but this way upper levels don't need to care about page
3563 - "dirty-sync-count": times that dirty ram was synchronized (json-int)
3564 - "disk": only present if "status" is "active" and it is a block migration,
3565 it is a json-object with the following disk information:
3566 - "transferred": amount transferred in bytes (json-int)
3567 - "remaining": amount remaining to transfer in bytes json-int)
3568 - "total": total disk size in bytes (json-int)
3569 - "xbzrle-cache": only present if XBZRLE is active.
3570 It is a json-object with the following XBZRLE information:
3571 - "cache-size": XBZRLE cache size in bytes
3572 - "bytes": number of bytes transferred for XBZRLE compressed pages
3573 - "pages": number of XBZRLE compressed pages
3574 - "cache-miss": number of XBRZRLE page cache misses
3575 - "cache-miss-rate": rate of XBRZRLE page cache misses
3576 - "overflow": number of times XBZRLE overflows. This means
3577 that the XBZRLE encoding was bigger than just sent the
3578 whole page, and then we sent the whole page instead (as as
3583 1. Before the first migration
3585 -> { "execute": "query-migrate" }
3588 2. Migration is done and has succeeded
3590 -> { "execute": "query-migrate" }
3592 "status": "completed",
3602 "normal-bytes":123456,
3603 "dirty-sync-count":15
3608 3. Migration is done and has failed
3610 -> { "execute": "query-migrate" }
3611 <- { "return": { "status": "failed" } }
3613 4. Migration is being performed and is not a block migration:
3615 -> { "execute": "query-migrate" }
3625 "expected-downtime":12345,
3628 "normal-bytes":123456,
3629 "dirty-sync-count":15
3634 5. Migration is being performed and is a block migration:
3636 -> { "execute": "query-migrate" }
3642 "remaining":1053304,
3646 "expected-downtime":12345,
3649 "normal-bytes":123456,
3650 "dirty-sync-count":15
3654 "remaining":20880384,
3660 6. Migration is being performed and XBZRLE is active:
3662 -> { "execute": "query-migrate" }
3666 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
3669 "remaining":1053304,
3673 "expected-downtime":12345,
3676 "normal-bytes":3412992,
3677 "dirty-sync-count":15
3680 "cache-size":67108864,
3684 "cache-miss-rate":0.123,
3693 .name = "query-migrate",
3695 .mhandler.cmd_new = qmp_marshal_query_migrate,
3699 migrate-set-capabilities
3700 ------------------------
3702 Enable/Disable migration capabilities
3704 - "xbzrle": XBZRLE support
3705 - "rdma-pin-all": pin all pages when using RDMA during migration
3706 - "auto-converge": throttle down guest to help convergence of migration
3707 - "zero-blocks": compress zero blocks during block migration
3708 - "compress": use multiple compression threads to accelerate live migration
3709 - "events": generate events for each migration state change
3710 - "postcopy-ram": postcopy mode for live migration
3716 -> { "execute": "migrate-set-capabilities" , "arguments":
3717 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
3722 .name = "migrate-set-capabilities",
3723 .args_type = "capabilities:q",
3724 .params = "capability:s,state:b",
3725 .mhandler.cmd_new = qmp_marshal_migrate_set_capabilities,
3728 query-migrate-capabilities
3729 --------------------------
3731 Query current migration capabilities
3733 - "capabilities": migration capabilities state
3734 - "xbzrle" : XBZRLE state (json-bool)
3735 - "rdma-pin-all" : RDMA Pin Page state (json-bool)
3736 - "auto-converge" : Auto Converge state (json-bool)
3737 - "zero-blocks" : Zero Blocks state (json-bool)
3738 - "compress": Multiple compression threads state (json-bool)
3739 - "events": Migration state change event state (json-bool)
3740 - "postcopy-ram": postcopy ram state (json-bool)
3746 -> { "execute": "query-migrate-capabilities" }
3748 {"state": false, "capability": "xbzrle"},
3749 {"state": false, "capability": "rdma-pin-all"},
3750 {"state": false, "capability": "auto-converge"},
3751 {"state": false, "capability": "zero-blocks"},
3752 {"state": false, "capability": "compress"},
3753 {"state": true, "capability": "events"},
3754 {"state": false, "capability": "postcopy-ram"}
3760 .name = "query-migrate-capabilities",
3762 .mhandler.cmd_new = qmp_marshal_query_migrate_capabilities,
3766 migrate-set-parameters
3767 ----------------------
3769 Set migration parameters
3771 - "compress-level": set compression level during migration (json-int)
3772 - "compress-threads": set compression thread count for migration (json-int)
3773 - "decompress-threads": set decompression thread count for migration (json-int)
3774 - "x-cpu-throttle-initial": set initial percentage of time guest cpus are
3775 throttled for auto-converge (json-int)
3776 - "x-cpu-throttle-increment": set throttle increasing percentage for
3777 auto-converge (json-int)
3783 -> { "execute": "migrate-set-parameters" , "arguments":
3784 { "compress-level": 1 } }
3789 .name = "migrate-set-parameters",
3791 "compress-level:i?,compress-threads:i?,decompress-threads:i?,x-cpu-throttle-initial:i?,x-cpu-throttle-increment:i?",
3792 .mhandler.cmd_new = qmp_marshal_migrate_set_parameters,
3795 query-migrate-parameters
3796 ------------------------
3798 Query current migration parameters
3800 - "parameters": migration parameters value
3801 - "compress-level" : compression level value (json-int)
3802 - "compress-threads" : compression thread count value (json-int)
3803 - "decompress-threads" : decompression thread count value (json-int)
3804 - "x-cpu-throttle-initial" : initial percentage of time guest cpus are
3805 throttled (json-int)
3806 - "x-cpu-throttle-increment" : throttle increasing percentage for
3807 auto-converge (json-int)
3813 -> { "execute": "query-migrate-parameters" }
3816 "decompress-threads": 2,
3817 "x-cpu-throttle-increment": 10,
3818 "compress-threads": 8,
3819 "compress-level": 1,
3820 "x-cpu-throttle-initial": 20
3827 .name = "query-migrate-parameters",
3829 .mhandler.cmd_new = qmp_marshal_query_migrate_parameters,
3836 Show balloon information.
3838 Make an asynchronous request for balloon info. When the request completes a
3839 json-object will be returned containing the following data:
3841 - "actual": current balloon value in bytes (json-int)
3845 -> { "execute": "query-balloon" }
3848 "actual":1073741824,
3855 .name = "query-balloon",
3857 .mhandler.cmd_new = qmp_marshal_query_balloon,
3861 .name = "query-block-jobs",
3863 .mhandler.cmd_new = qmp_marshal_query_block_jobs,
3868 .args_type = "path:s",
3869 .mhandler.cmd_new = qmp_marshal_qom_list,
3874 .args_type = "path:s,property:s,value:q",
3875 .mhandler.cmd_new = qmp_marshal_qom_set,
3880 .args_type = "path:s,property:s",
3881 .mhandler.cmd_new = qmp_marshal_qom_get,
3885 .name = "nbd-server-start",
3886 .args_type = "addr:q,tls-creds:s?",
3887 .mhandler.cmd_new = qmp_marshal_nbd_server_start,
3890 .name = "nbd-server-add",
3891 .args_type = "device:B,writable:b?",
3892 .mhandler.cmd_new = qmp_marshal_nbd_server_add,
3895 .name = "nbd-server-stop",
3897 .mhandler.cmd_new = qmp_marshal_nbd_server_stop,
3901 .name = "change-vnc-password",
3902 .args_type = "password:s",
3903 .mhandler.cmd_new = qmp_marshal_change_vnc_password,
3906 .name = "qom-list-types",
3907 .args_type = "implements:s?,abstract:b?",
3908 .mhandler.cmd_new = qmp_marshal_qom_list_types,
3912 .name = "device-list-properties",
3913 .args_type = "typename:s",
3914 .mhandler.cmd_new = qmp_marshal_device_list_properties,
3918 .name = "query-machines",
3920 .mhandler.cmd_new = qmp_marshal_query_machines,
3924 .name = "query-cpu-definitions",
3926 .mhandler.cmd_new = qmp_marshal_query_cpu_definitions,
3930 .name = "query-target",
3932 .mhandler.cmd_new = qmp_marshal_query_target,
3936 .name = "query-tpm",
3938 .mhandler.cmd_new = qmp_marshal_query_tpm,
3945 Return information about the TPM device.
3951 -> { "execute": "query-tpm" }
3954 { "model": "tpm-tis",
3956 { "type": "passthrough",
3958 { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
3970 .name = "query-tpm-models",
3972 .mhandler.cmd_new = qmp_marshal_query_tpm_models,
3979 Return a list of supported TPM models.
3985 -> { "execute": "query-tpm-models" }
3986 <- { "return": [ "tpm-tis" ] }
3991 .name = "query-tpm-types",
3993 .mhandler.cmd_new = qmp_marshal_query_tpm_types,
4000 Return a list of supported TPM types.
4006 -> { "execute": "query-tpm-types" }
4007 <- { "return": [ "passthrough" ] }
4012 .name = "chardev-add",
4013 .args_type = "id:s,backend:q",
4014 .mhandler.cmd_new = qmp_marshal_chardev_add,
4025 - "id": the chardev's ID, must be unique (json-string)
4026 - "backend": chardev backend type + parameters
4030 -> { "execute" : "chardev-add",
4031 "arguments" : { "id" : "foo",
4032 "backend" : { "type" : "null", "data" : {} } } }
4035 -> { "execute" : "chardev-add",
4036 "arguments" : { "id" : "bar",
4037 "backend" : { "type" : "file",
4038 "data" : { "out" : "/tmp/bar.log" } } } }
4041 -> { "execute" : "chardev-add",
4042 "arguments" : { "id" : "baz",
4043 "backend" : { "type" : "pty", "data" : {} } } }
4044 <- { "return": { "pty" : "/dev/pty/42" } }
4049 .name = "chardev-remove",
4050 .args_type = "id:s",
4051 .mhandler.cmd_new = qmp_marshal_chardev_remove,
4063 - "id": the chardev's ID, must exist and not be in use (json-string)
4067 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }
4072 .name = "query-rx-filter",
4073 .args_type = "name:s?",
4074 .mhandler.cmd_new = qmp_marshal_query_rx_filter,
4081 Show rx-filter information.
4083 Returns a json-array of rx-filter information for all NICs (or for the
4084 given NIC), returning an error if the given NIC doesn't exist, or
4085 given NIC doesn't support rx-filter querying, or given net client
4088 The query will clear the event notification flag of each NIC, then qemu
4089 will start to emit event to QMP monitor.
4091 Each array entry contains the following:
4093 - "name": net client name (json-string)
4094 - "promiscuous": promiscuous mode is enabled (json-bool)
4095 - "multicast": multicast receive state (one of 'normal', 'none', 'all')
4096 - "unicast": unicast receive state (one of 'normal', 'none', 'all')
4097 - "vlan": vlan receive state (one of 'normal', 'none', 'all') (Since 2.0)
4098 - "broadcast-allowed": allow to receive broadcast (json-bool)
4099 - "multicast-overflow": multicast table is overflowed (json-bool)
4100 - "unicast-overflow": unicast table is overflowed (json-bool)
4101 - "main-mac": main macaddr string (json-string)
4102 - "vlan-table": a json-array of active vlan id
4103 - "unicast-table": a json-array of unicast macaddr string
4104 - "multicast-table": a json-array of multicast macaddr string
4108 -> { "execute": "query-rx-filter", "arguments": { "name": "vnet0" } }
4111 "promiscuous": true,
4113 "main-mac": "52:54:00:12:34:56",
4114 "unicast": "normal",
4122 "multicast": "normal",
4123 "multicast-overflow": false,
4124 "unicast-overflow": false,
4125 "multicast-table": [
4126 "01:00:5e:00:00:01",
4127 "33:33:00:00:00:01",
4130 "broadcast-allowed": false
4138 .name = "blockdev-add",
4139 .args_type = "options:q",
4140 .mhandler.cmd_new = qmp_marshal_blockdev_add,
4149 This command is still a work in progress. It doesn't support all
4150 block drivers among other things. Stay away from it unless you want
4151 to help with its development.
4155 - "options": block driver options
4159 -> { "execute": "blockdev-add",
4160 "arguments": { "options" : { "driver": "qcow2",
4161 "file": { "driver": "file",
4162 "filename": "test.qcow2" } } } }
4167 -> { "execute": "blockdev-add",
4179 "filename": "/tmp/test.qcow2"
4185 "filename": "/dev/fdset/4"
4197 .name = "x-blockdev-del",
4198 .args_type = "id:s?,node-name:s?",
4199 .mhandler.cmd_new = qmp_marshal_x_blockdev_del,
4207 Deletes a block device thas has been added using blockdev-add.
4208 The selected device can be either a block backend or a graph node.
4210 In the former case the backend will be destroyed, along with its
4211 inserted medium if there's any. The command will fail if the backend
4212 or its medium are in use.
4214 In the latter case the node will be destroyed. The command will fail
4215 if the node is attached to a block backend or is otherwise being
4218 One of "id" or "node-name" must be specified, but not both.
4220 This command is still a work in progress and is considered
4221 experimental. Stay away from it unless you want to help with its
4226 - "id": Name of the block backend device to delete (json-string, optional)
4227 - "node-name": Name of the graph node to delete (json-string, optional)
4231 -> { "execute": "blockdev-add",
4238 "filename": "test.qcow2"
4246 -> { "execute": "x-blockdev-del",
4247 "arguments": { "id": "drive0" }
4254 .name = "blockdev-open-tray",
4255 .args_type = "device:s,force:b?",
4256 .mhandler.cmd_new = qmp_marshal_blockdev_open_tray,
4263 Opens a block device's tray. If there is a block driver state tree inserted as a
4264 medium, it will become inaccessible to the guest (but it will remain associated
4265 to the block device, so closing the tray will make it accessible again).
4267 If the tray was already open before, this will be a no-op.
4269 Once the tray opens, a DEVICE_TRAY_MOVED event is emitted. There are cases in
4270 which no such event will be generated, these include:
4271 - if the guest has locked the tray, @force is false and the guest does not
4272 respond to the eject request
4273 - if the BlockBackend denoted by @device does not have a guest device attached
4275 - if the guest device does not have an actual tray and is empty, for instance
4276 for floppy disk drives
4280 - "device": block device name (json-string)
4281 - "force": if false (the default), an eject request will be sent to the guest if
4282 it has locked the tray (and the tray will not be opened immediately);
4283 if true, the tray will be opened regardless of whether it is locked
4284 (json-bool, optional)
4288 -> { "execute": "blockdev-open-tray",
4289 "arguments": { "device": "ide1-cd0" } }
4291 <- { "timestamp": { "seconds": 1418751016,
4292 "microseconds": 716996 },
4293 "event": "DEVICE_TRAY_MOVED",
4294 "data": { "device": "ide1-cd0",
4295 "tray-open": true } }
4302 .name = "blockdev-close-tray",
4303 .args_type = "device:s",
4304 .mhandler.cmd_new = qmp_marshal_blockdev_close_tray,
4311 Closes a block device's tray. If there is a block driver state tree associated
4312 with the block device (which is currently ejected), that tree will be loaded as
4315 If the tray was already closed before, this will be a no-op.
4319 - "device": block device name (json-string)
4323 -> { "execute": "blockdev-close-tray",
4324 "arguments": { "device": "ide1-cd0" } }
4326 <- { "timestamp": { "seconds": 1418751345,
4327 "microseconds": 272147 },
4328 "event": "DEVICE_TRAY_MOVED",
4329 "data": { "device": "ide1-cd0",
4330 "tray-open": false } }
4337 .name = "x-blockdev-remove-medium",
4338 .args_type = "device:s",
4339 .mhandler.cmd_new = qmp_marshal_x_blockdev_remove_medium,
4343 x-blockdev-remove-medium
4344 ------------------------
4346 Removes a medium (a block driver state tree) from a block device. That block
4347 device's tray must currently be open (unless there is no attached guest device).
4349 If the tray is open and there is no medium inserted, this will be a no-op.
4351 This command is still a work in progress and is considered experimental.
4352 Stay away from it unless you want to help with its development.
4356 - "device": block device name (json-string)
4360 -> { "execute": "x-blockdev-remove-medium",
4361 "arguments": { "device": "ide1-cd0" } }
4363 <- { "error": { "class": "GenericError",
4364 "desc": "Tray of device 'ide1-cd0' is not open" } }
4366 -> { "execute": "blockdev-open-tray",
4367 "arguments": { "device": "ide1-cd0" } }
4369 <- { "timestamp": { "seconds": 1418751627,
4370 "microseconds": 549958 },
4371 "event": "DEVICE_TRAY_MOVED",
4372 "data": { "device": "ide1-cd0",
4373 "tray-open": true } }
4377 -> { "execute": "x-blockdev-remove-medium",
4378 "arguments": { "device": "ide1-cd0" } }
4385 .name = "x-blockdev-insert-medium",
4386 .args_type = "device:s,node-name:s",
4387 .mhandler.cmd_new = qmp_marshal_x_blockdev_insert_medium,
4391 x-blockdev-insert-medium
4392 ------------------------
4394 Inserts a medium (a block driver state tree) into a block device. That block
4395 device's tray must currently be open (unless there is no attached guest device)
4396 and there must be no medium inserted already.
4398 This command is still a work in progress and is considered experimental.
4399 Stay away from it unless you want to help with its development.
4403 - "device": block device name (json-string)
4404 - "node-name": root node of the BDS tree to insert into the block device
4408 -> { "execute": "blockdev-add",
4409 "arguments": { "options": { "node-name": "node0",
4411 "file": { "driver": "file",
4412 "filename": "fedora.iso" } } } }
4416 -> { "execute": "x-blockdev-insert-medium",
4417 "arguments": { "device": "ide1-cd0",
4418 "node-name": "node0" } }
4425 .name = "query-named-block-nodes",
4427 .mhandler.cmd_new = qmp_marshal_query_named_block_nodes,
4431 @query-named-block-nodes
4432 ------------------------
4434 Return a list of BlockDeviceInfo for all the named block driver nodes
4438 -> { "execute": "query-named-block-nodes" }
4439 <- { "return": [ { "ro":false,
4442 "file":"disks/test.qcow2",
4443 "node-name": "my-node",
4444 "backing_file_depth":1,
4458 "write_threshold": 0,
4460 "filename":"disks/test.qcow2",
4462 "virtual-size":2048000,
4463 "backing_file":"base.qcow2",
4464 "full-backing-filename":"disks/base.qcow2",
4465 "backing-filename-format":"qcow2",
4469 "name": "snapshot1",
4471 "date-sec": 10000200,
4473 "vm-clock-sec": 206,
4478 "filename":"disks/base.qcow2",
4480 "virtual-size":2048000
4487 .name = "blockdev-change-medium",
4488 .args_type = "device:B,filename:F,format:s?,read-only-mode:s?",
4489 .mhandler.cmd_new = qmp_marshal_blockdev_change_medium,
4493 blockdev-change-medium
4494 ----------------------
4496 Changes the medium inserted into a block device by ejecting the current medium
4497 and loading a new image file which is inserted as the new medium.
4501 - "device": device name (json-string)
4502 - "filename": filename of the new image (json-string)
4503 - "format": format of the new image (json-string, optional)
4504 - "read-only-mode": new read-only mode (json-string, optional)
4505 - Possible values: "retain" (default), "read-only", "read-write"
4509 1. Change a removable medium
4511 -> { "execute": "blockdev-change-medium",
4512 "arguments": { "device": "ide1-cd0",
4513 "filename": "/srv/images/Fedora-12-x86_64-DVD.iso",
4517 2. Load a read-only medium into a writable drive
4519 -> { "execute": "blockdev-change-medium",
4520 "arguments": { "device": "isa-fd0",
4521 "filename": "/srv/images/ro.img",
4523 "read-only-mode": "retain" } }
4526 { "class": "GenericError",
4527 "desc": "Could not open '/srv/images/ro.img': Permission denied" } }
4529 -> { "execute": "blockdev-change-medium",
4530 "arguments": { "device": "isa-fd0",
4531 "filename": "/srv/images/ro.img",
4533 "read-only-mode": "read-only" } }
4540 .name = "query-memdev",
4542 .mhandler.cmd_new = qmp_marshal_query_memdev,
4549 Show memory devices information.
4554 -> { "execute": "query-memdev" }
4561 "host-nodes": [0, 1],
4569 "host-nodes": [2, 3],
4570 "policy": "preferred"
4578 .name = "query-memory-devices",
4580 .mhandler.cmd_new = qmp_marshal_query_memory_devices,
4584 @query-memory-devices
4585 --------------------
4587 Return a list of memory devices.
4590 -> { "execute": "query-memory-devices" }
4591 <- { "return": [ { "data":
4592 { "addr": 5368709120,
4593 "hotpluggable": true,
4596 "memdev": "/objects/memX",
4605 .name = "query-acpi-ospm-status",
4607 .mhandler.cmd_new = qmp_marshal_query_acpi_ospm_status,
4611 @query-acpi-ospm-status
4612 --------------------
4614 Return list of ACPIOSTInfo for devices that support status reporting
4615 via ACPI _OST method.
4618 -> { "execute": "query-acpi-ospm-status" }
4619 <- { "return": [ { "device": "d1", "slot": "0", "slot-type": "DIMM", "source": 1, "status": 0},
4620 { "slot": "1", "slot-type": "DIMM", "source": 0, "status": 0},
4621 { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
4622 { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
4626 #if defined TARGET_I386
4628 .name = "rtc-reset-reinjection",
4630 .mhandler.cmd_new = qmp_marshal_rtc_reset_reinjection,
4635 rtc-reset-reinjection
4636 ---------------------
4638 Reset the RTC interrupt reinjection backlog.
4644 -> { "execute": "rtc-reset-reinjection" }
4649 .name = "trace-event-get-state",
4650 .args_type = "name:s",
4651 .mhandler.cmd_new = qmp_marshal_trace_event_get_state,
4655 trace-event-get-state
4656 ---------------------
4658 Query the state of events.
4662 -> { "execute": "trace-event-get-state", "arguments": { "name": "qemu_memalign" } }
4663 <- { "return": [ { "name": "qemu_memalign", "state": "disabled" } ] }
4667 .name = "trace-event-set-state",
4668 .args_type = "name:s,enable:b,ignore-unavailable:b?",
4669 .mhandler.cmd_new = qmp_marshal_trace_event_set_state,
4673 trace-event-set-state
4674 ---------------------
4676 Set the state of events.
4680 -> { "execute": "trace-event-set-state", "arguments": { "name": "qemu_memalign", "enable": "true" } }
4685 .name = "input-send-event",
4686 .args_type = "console:i?,events:q",
4687 .mhandler.cmd_new = qmp_marshal_input_send_event,
4694 Send input event to guest.
4698 - "device": display device (json-string, optional)
4699 - "head": display head (json-int, optional)
4700 - "events": list of input events
4702 The consoles are visible in the qom tree, under
4703 /backend/console[$index]. They have a device link and head property, so
4704 it is possible to map which console belongs to which device and display.
4706 Note: this command is experimental, and not a stable API.
4710 Press left mouse button.
4712 -> { "execute": "input-send-event",
4713 "arguments": { "device": "video0",
4714 "events": [ { "type": "btn",
4715 "data" : { "down": true, "button": "left" } } ] } }
4718 -> { "execute": "input-send-event",
4719 "arguments": { "device": "video0",
4720 "events": [ { "type": "btn",
4721 "data" : { "down": false, "button": "left" } } ] } }
4728 -> { "execute": "input-send-event",
4729 "arguments": { "events": [
4730 { "type": "key", "data" : { "down": true,
4731 "key": {"type": "qcode", "data": "ctrl" } } },
4732 { "type": "key", "data" : { "down": true,
4733 "key": {"type": "qcode", "data": "alt" } } },
4734 { "type": "key", "data" : { "down": true,
4735 "key": {"type": "qcode", "data": "delete" } } } ] } }
4740 Move mouse pointer to absolute coordinates (20000, 400).
4742 -> { "execute": "input-send-event" ,
4743 "arguments": { "events": [
4744 { "type": "abs", "data" : { "axis": "x", "value" : 20000 } },
4745 { "type": "abs", "data" : { "axis": "y", "value" : 400 } } ] } }
4751 .name = "block-set-write-threshold",
4752 .args_type = "node-name:s,write-threshold:l",
4753 .mhandler.cmd_new = qmp_marshal_block_set_write_threshold,
4757 block-set-write-threshold
4760 Change the write threshold for a block drive. The threshold is an offset,
4761 thus must be non-negative. Default is no write threshold.
4762 Setting the threshold to zero disables it.
4766 - "node-name": the node name in the block driver state graph (json-string)
4767 - "write-threshold": the write threshold in bytes (json-int)
4771 -> { "execute": "block-set-write-threshold",
4772 "arguments": { "node-name": "mydev",
4773 "write-threshold": 17179869184 } }
4779 .name = "query-rocker",
4780 .args_type = "name:s",
4781 .mhandler.cmd_new = qmp_marshal_query_rocker,
4790 - "name": switch name
4794 -> { "execute": "query-rocker", "arguments": { "name": "sw1" } }
4795 <- { "return": {"name": "sw1", "ports": 2, "id": 1327446905938}}
4800 .name = "query-rocker-ports",
4801 .args_type = "name:s",
4802 .mhandler.cmd_new = qmp_marshal_query_rocker_ports,
4806 Show rocker switch ports
4807 ------------------------
4811 - "name": switch name
4815 -> { "execute": "query-rocker-ports", "arguments": { "name": "sw1" } }
4816 <- { "return": [ {"duplex": "full", "enabled": true, "name": "sw1.1",
4817 "autoneg": "off", "link-up": true, "speed": 10000},
4818 {"duplex": "full", "enabled": true, "name": "sw1.2",
4819 "autoneg": "off", "link-up": true, "speed": 10000}
4825 .name = "query-rocker-of-dpa-flows",
4826 .args_type = "name:s,tbl-id:i?",
4827 .mhandler.cmd_new = qmp_marshal_query_rocker_of_dpa_flows,
4831 Show rocker switch OF-DPA flow tables
4832 -------------------------------------
4836 - "name": switch name
4837 - "tbl-id": (optional) flow table ID
4841 -> { "execute": "query-rocker-of-dpa-flows", "arguments": { "name": "sw1" } }
4842 <- { "return": [ {"key": {"in-pport": 0, "priority": 1, "tbl-id": 0},
4845 "action": {"goto-tbl": 10},
4846 "mask": {"in-pport": 4294901760}
4854 .name = "query-rocker-of-dpa-groups",
4855 .args_type = "name:s,type:i?",
4856 .mhandler.cmd_new = qmp_marshal_query_rocker_of_dpa_groups,
4860 Show rocker OF-DPA group tables
4861 -------------------------------
4865 - "name": switch name
4866 - "type": (optional) group type
4870 -> { "execute": "query-rocker-of-dpa-groups", "arguments": { "name": "sw1" } }
4871 <- { "return": [ {"type": 0, "out-pport": 2, "pport": 2, "vlan-id": 3841,
4872 "pop-vlan": 1, "id": 251723778},
4873 {"type": 0, "out-pport": 0, "pport": 0, "vlan-id": 3841,
4874 "pop-vlan": 1, "id": 251723776},
4875 {"type": 0, "out-pport": 1, "pport": 1, "vlan-id": 3840,
4876 "pop-vlan": 1, "id": 251658241},
4877 {"type": 0, "out-pport": 0, "pport": 0, "vlan-id": 3840,
4878 "pop-vlan": 1, "id": 251658240}
4883 #if defined TARGET_ARM
4885 .name = "query-gic-capabilities",
4887 .mhandler.cmd_new = qmp_marshal_query_gic_capabilities,
4892 query-gic-capabilities
4895 Return a list of GICCapability objects, describing supported GIC
4896 (Generic Interrupt Controller) versions.
4902 -> { "execute": "query-gic-capabilities" }
4903 <- { "return": [{ "version": 2, "emulated": true, "kernel": false },
4904 { "version": 3, "emulated": false, "kernel": true } ] }