1 HXCOMM QMP dispatch table and documentation
2 HXCOMM Text between SQMP and EQMP is copied to the QMP documention file and
3 HXCOMM does not show up in the other formats.
9 This document describes all commands currently supported by QMP.
11 Most of the time their usage is exactly the same as in the user Monitor, this
12 means that any other document which also describe commands (the manpage,
13 QEMU's manual, etc) can and should be consulted.
15 QMP has two types of commands: regular and query commands. Regular commands
16 usually change the Virtual Machine's state someway, while query commands just
17 return information. The sections below are divided accordingly.
19 It's important to observe that all communication examples are formatted in
20 a reader-friendly way, so that they're easier to understand. However, in real
21 protocol usage, they're emitted as a single line.
23 Also, the following notation is used to denote data flow:
25 -> data issued by the Client
26 <- Server data response
28 Please, refer to the QMP specification (QMP/qmp-spec.txt) for detailed
29 information on the Server command and response formats.
31 NOTE: This document is temporary and will be replaced soon.
33 1. Stability Considerations
34 ===========================
36 The current QMP command set (described in this file) may be useful for a
37 number of use cases, however it's limited and several commands have bad
38 defined semantics, specially with regard to command completion.
40 These problems are going to be solved incrementally in the next QEMU releases
41 and we're going to establish a deprecation policy for badly defined commands.
43 If you're planning to adopt QMP, please observe the following:
45 1. The deprecation policy will take effect and be documented soon, please
46 check the documentation of each used command as soon as a new release of
49 2. DO NOT rely on anything which is not explicit documented
51 3. Errors, in special, are not documented. Applications should NOT check
52 for specific errors classes or data (it's strongly recommended to only
53 check for the "error" key)
58 Server's responses in the examples below are always a success response, please
59 refer to the QMP specification for more details on error responses.
66 .mhandler.cmd_new = qmp_marshal_input_quit,
79 -> { "execute": "quit" }
86 .args_type = "force:-f,device:B",
87 .mhandler.cmd_new = qmp_marshal_input_eject,
94 Eject a removable medium.
98 - force: force ejection (json-bool, optional)
99 - device: device name (json-string)
103 -> { "execute": "eject", "arguments": { "device": "ide1-cd0" } }
106 Note: The "force" argument defaults to false.
112 .args_type = "device:B,target:F,arg:s?",
113 .mhandler.cmd_new = qmp_marshal_input_change,
120 Change a removable medium or VNC configuration.
124 - "device": device name (json-string)
125 - "target": filename or item (json-string)
126 - "arg": additional argument (json-string, optional)
130 1. Change a removable medium
132 -> { "execute": "change",
133 "arguments": { "device": "ide1-cd0",
134 "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } }
137 2. Change VNC password
139 -> { "execute": "change",
140 "arguments": { "device": "vnc", "target": "password",
147 .name = "screendump",
148 .args_type = "filename:F",
149 .mhandler.cmd_new = qmp_marshal_input_screendump,
156 Save screen into PPM image.
160 - "filename": file path (json-string)
164 -> { "execute": "screendump", "arguments": { "filename": "/tmp/image" } }
172 .mhandler.cmd_new = qmp_marshal_input_stop,
185 -> { "execute": "stop" }
193 .mhandler.cmd_new = qmp_marshal_input_cont,
206 -> { "execute": "cont" }
212 .name = "system_wakeup",
214 .mhandler.cmd_new = qmp_marshal_input_system_wakeup,
221 Wakeup guest from suspend.
227 -> { "execute": "system_wakeup" }
233 .name = "system_reset",
235 .mhandler.cmd_new = qmp_marshal_input_system_reset,
248 -> { "execute": "system_reset" }
254 .name = "system_powerdown",
256 .mhandler.cmd_new = qmp_marshal_input_system_powerdown,
263 Send system power down event.
269 -> { "execute": "system_powerdown" }
275 .name = "device_add",
276 .args_type = "device:O",
277 .params = "driver[,prop=value][,...]",
278 .help = "add device, like -device on the command line",
279 .user_print = monitor_user_noop,
280 .mhandler.cmd_new = do_device_add,
291 - "driver": the name of the new device's driver (json-string)
292 - "bus": the device's parent bus (device tree path, json-string, optional)
293 - "id": the device's ID, must be unique (json-string)
298 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
303 (1) For detailed information about this command, please refer to the
304 'docs/qdev-device-use.txt' file.
306 (2) It's possible to list device properties by running QEMU with the
307 "-device DEVICE,\?" command-line argument, where DEVICE is the device's name
312 .name = "device_del",
314 .mhandler.cmd_new = qmp_marshal_input_device_del,
325 - "id": the device's ID (json-string)
329 -> { "execute": "device_del", "arguments": { "id": "net1" } }
336 .args_type = "keys:O,hold-time:i?",
337 .mhandler.cmd_new = qmp_marshal_input_send_key,
349 - "key": key sequence (a json-array of key union values,
350 union can be number or qcode enum)
352 - hold-time: time to delay key up events, milliseconds. Defaults to 100
357 -> { "execute": "send-key",
358 "arguments": { "keys": [ { "type": "qcode", "data": "ctrl" },
359 { "type": "qcode", "data": "alt" },
360 { "type": "qcode", "data": "delete" } ] } }
367 .args_type = "index:i",
368 .mhandler.cmd_new = qmp_marshal_input_cpu,
379 - "index": the CPU's index (json-int)
383 -> { "execute": "cpu", "arguments": { "index": 0 } }
386 Note: CPUs' indexes are obtained with the 'query-cpus' command.
393 .mhandler.cmd_new = qmp_marshal_input_cpu_add,
404 - "id": cpu id (json-int)
408 -> { "execute": "cpu-add", "arguments": { "id": 2 } }
415 .args_type = "val:l,size:i,filename:s,cpu:i?",
416 .mhandler.cmd_new = qmp_marshal_input_memsave,
423 Save to disk virtual memory dump starting at 'val' of size 'size'.
427 - "val": the starting address (json-int)
428 - "size": the memory size, in bytes (json-int)
429 - "filename": file path (json-string)
430 - "cpu": virtual CPU index (json-int, optional)
434 -> { "execute": "memsave",
435 "arguments": { "val": 10,
437 "filename": "/tmp/virtual-mem-dump" } }
444 .args_type = "val:l,size:i,filename:s",
445 .mhandler.cmd_new = qmp_marshal_input_pmemsave,
452 Save to disk physical memory dump starting at 'val' of size 'size'.
456 - "val": the starting address (json-int)
457 - "size": the memory size, in bytes (json-int)
458 - "filename": file path (json-string)
462 -> { "execute": "pmemsave",
463 "arguments": { "val": 10,
465 "filename": "/tmp/physical-mem-dump" } }
471 .name = "inject-nmi",
473 .mhandler.cmd_new = qmp_marshal_input_inject_nmi,
480 Inject an NMI on guest's CPUs.
486 -> { "execute": "inject-nmi" }
489 Note: inject-nmi fails when the guest doesn't support injecting.
490 Currently, only x86 (NMI) and s390x (RESTART) guests do.
495 .name = "ringbuf-write",
496 .args_type = "device:s,data:s,format:s?",
497 .mhandler.cmd_new = qmp_marshal_input_ringbuf_write,
504 Write to a ring buffer character device.
508 - "device": ring buffer character device name (json-string)
509 - "data": data to write (json-string)
510 - "format": data format (json-string, optional)
511 - Possible values: "utf8" (default), "base64"
512 Bug: invalid base64 is currently not rejected.
513 Whitespace *is* invalid.
517 -> { "execute": "ringbuf-write",
518 "arguments": { "device": "foo",
526 .name = "ringbuf-read",
527 .args_type = "device:s,size:i,format:s?",
528 .mhandler.cmd_new = qmp_marshal_input_ringbuf_read,
535 Read from a ring buffer character device.
539 - "device": ring buffer character device name (json-string)
540 - "size": how many bytes to read at most (json-int)
541 - Number of data bytes, not number of characters in encoded data
542 - "format": data format (json-string, optional)
543 - Possible values: "utf8" (default), "base64"
544 - Naturally, format "utf8" works only when the ring buffer
545 contains valid UTF-8 text. Invalid UTF-8 sequences get
546 replaced. Bug: replacement doesn't work. Bug: can screw
547 up on encountering NUL characters, after the ring buffer
548 lost data, and when reading stops because the size limit
553 -> { "execute": "ringbuf-read",
554 "arguments": { "device": "foo",
557 <- {"return": "abcdefgh"}
562 .name = "xen-save-devices-state",
563 .args_type = "filename:F",
564 .mhandler.cmd_new = qmp_marshal_input_xen_save_devices_state,
568 xen-save-devices-state
571 Save the state of all devices to file. The RAM and the block devices
572 of the VM are not saved by this command.
576 - "filename": the file to save the state of the devices to as binary
577 data. See xen-save-devices-state.txt for a description of the binary
582 -> { "execute": "xen-save-devices-state",
583 "arguments": { "filename": "/tmp/save" } }
589 .name = "xen-set-global-dirty-log",
590 .args_type = "enable:b",
591 .mhandler.cmd_new = qmp_marshal_input_xen_set_global_dirty_log,
595 xen-set-global-dirty-log
598 Enable or disable the global dirty log mode.
602 - "enable": Enable it or disable it.
606 -> { "execute": "xen-set-global-dirty-log",
607 "arguments": { "enable": true } }
614 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
615 .mhandler.cmd_new = qmp_marshal_input_migrate,
626 - "blk": block migration, full disk copy (json-bool, optional)
627 - "inc": incremental disk copy (json-bool, optional)
628 - "uri": Destination URI (json-string)
632 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
637 (1) The 'query-migrate' command should be used to check migration's progress
638 and final result (this information is provided by the 'status' member)
639 (2) All boolean arguments default to false
640 (3) The user Monitor's "detach" argument is invalid in QMP and should not
646 .name = "migrate_cancel",
648 .mhandler.cmd_new = qmp_marshal_input_migrate_cancel,
655 Cancel the current migration.
661 -> { "execute": "migrate_cancel" }
666 .name = "migrate-set-cache-size",
667 .args_type = "value:o",
668 .mhandler.cmd_new = qmp_marshal_input_migrate_set_cache_size,
672 migrate-set-cache-size
673 ----------------------
675 Set cache size to be used by XBZRLE migration, the cache size will be rounded
676 down to the nearest power of 2
680 - "value": cache size in bytes (json-int)
684 -> { "execute": "migrate-set-cache-size", "arguments": { "value": 536870912 } }
689 .name = "query-migrate-cache-size",
691 .mhandler.cmd_new = qmp_marshal_input_query_migrate_cache_size,
695 query-migrate-cache-size
696 ------------------------
698 Show cache size to be used by XBZRLE migration
700 returns a json-object with the following information:
705 -> { "execute": "query-migrate-cache-size" }
706 <- { "return": 67108864 }
711 .name = "migrate_set_speed",
712 .args_type = "value:o",
713 .mhandler.cmd_new = qmp_marshal_input_migrate_set_speed,
720 Set maximum speed for migrations.
724 - "value": maximum speed, in bytes per second (json-int)
728 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
734 .name = "migrate_set_downtime",
735 .args_type = "value:T",
736 .mhandler.cmd_new = qmp_marshal_input_migrate_set_downtime,
743 Set maximum tolerated downtime (in seconds) for migrations.
747 - "value": maximum downtime (json-number)
751 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
757 .name = "client_migrate_info",
758 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
759 .params = "protocol hostname port tls-port cert-subject",
760 .help = "send migration info to spice/vnc client",
761 .user_print = monitor_user_noop,
762 .mhandler.cmd_async = client_migrate_info,
763 .flags = MONITOR_CMD_ASYNC,
770 Set the spice/vnc connection info for the migration target. The spice/vnc
771 server will ask the spice/vnc client to automatically reconnect using the
772 new parameters (if specified) once the vm migration finished successfully.
776 - "protocol": protocol: "spice" or "vnc" (json-string)
777 - "hostname": migration target hostname (json-string)
778 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
779 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
780 - "cert-subject": server certificate subject (json-string, optional)
784 -> { "execute": "client_migrate_info",
785 "arguments": { "protocol": "spice",
786 "hostname": "virt42.lab.kraxel.org",
793 .name = "dump-guest-memory",
794 .args_type = "paging:b,protocol:s,begin:i?,end:i?",
795 .params = "-p protocol [begin] [length]",
796 .help = "dump guest memory to file",
797 .user_print = monitor_user_noop,
798 .mhandler.cmd_new = qmp_marshal_input_dump_guest_memory,
805 Dump guest memory to file. The file can be processed with crash or gdb.
809 - "paging": do paging to get guest's memory mapping (json-bool)
810 - "protocol": destination file(started with "file:") or destination file
811 descriptor (started with "fd:") (json-string)
812 - "begin": the starting physical address. It's optional, and should be specified
813 with length together (json-int)
814 - "length": the memory size, in bytes. It's optional, and should be specified
815 with begin together (json-int)
819 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
824 (1) All boolean arguments default to false
829 .name = "netdev_add",
830 .args_type = "netdev:O",
831 .mhandler.cmd_new = qmp_netdev_add,
838 Add host network device.
842 - "type": the device type, "tap", "user", ... (json-string)
843 - "id": the device's ID, must be unique (json-string)
848 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
851 Note: The supported device options are the same ones supported by the '-netdev'
852 command-line argument, which are listed in the '-help' output or QEMU's
858 .name = "netdev_del",
860 .mhandler.cmd_new = qmp_marshal_input_netdev_del,
867 Remove host network device.
871 - "id": the device's ID, must be unique (json-string)
875 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
882 .name = "object-del",
884 .mhandler.cmd_new = qmp_marshal_input_object_del,
895 - "id": the object's ID (json-string)
899 -> { "execute": "object-del", "arguments": { "id": "rng1" } }
907 .name = "block_resize",
908 .args_type = "device:B,size:o",
909 .mhandler.cmd_new = qmp_marshal_input_block_resize,
916 Resize a block image while a guest is running.
920 - "device": the device's ID, must be unique (json-string)
925 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
931 .name = "block-stream",
932 .args_type = "device:B,base:s?,speed:o?,on-error:s?",
933 .mhandler.cmd_new = qmp_marshal_input_block_stream,
937 .name = "block-commit",
938 .args_type = "device:B,base:s?,top:s,speed:o?",
939 .mhandler.cmd_new = qmp_marshal_input_block_commit,
943 .name = "drive-backup",
944 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
945 "on-source-error:s?,on-target-error:s?",
946 .mhandler.cmd_new = qmp_marshal_input_drive_backup,
953 Start a point-in-time copy of a block device to a new destination. The
954 status of ongoing drive-backup operations can be checked with
955 query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
956 The operation can be stopped before it has completed using the
957 block-job-cancel command.
961 - "device": the name of the device which should be copied.
963 - "target": the target of the new image. If the file exists, or if it is a
964 device, the existing file/device will be used as the new
965 destination. If it does not exist, a new file will be created.
967 - "format": the format of the new destination, default is to probe if 'mode' is
968 'existing', else the format of the source
969 (json-string, optional)
970 - "sync": what parts of the disk image should be copied to the destination;
971 possibilities include "full" for all the disk, "top" for only the sectors
972 allocated in the topmost image, or "none" to only replicate new I/O
974 - "mode": whether and how QEMU should create a new image
975 (NewImageMode, optional, default 'absolute-paths')
976 - "speed": the maximum speed, in bytes per second (json-int, optional)
977 - "on-source-error": the action to take on an error on the source, default
978 'report'. 'stop' and 'enospc' can only be used
979 if the block device supports io-status.
980 (BlockdevOnError, optional)
981 - "on-target-error": the action to take on an error on the target, default
982 'report' (no limitations, since this applies to
983 a different block device than device).
984 (BlockdevOnError, optional)
987 -> { "execute": "drive-backup", "arguments": { "device": "drive0",
989 "target": "backup.img" } }
994 .name = "block-job-set-speed",
995 .args_type = "device:B,speed:o",
996 .mhandler.cmd_new = qmp_marshal_input_block_job_set_speed,
1000 .name = "block-job-cancel",
1001 .args_type = "device:B,force:b?",
1002 .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
1005 .name = "block-job-pause",
1006 .args_type = "device:B",
1007 .mhandler.cmd_new = qmp_marshal_input_block_job_pause,
1010 .name = "block-job-resume",
1011 .args_type = "device:B",
1012 .mhandler.cmd_new = qmp_marshal_input_block_job_resume,
1015 .name = "block-job-complete",
1016 .args_type = "device:B",
1017 .mhandler.cmd_new = qmp_marshal_input_block_job_complete,
1020 .name = "transaction",
1021 .args_type = "actions:q",
1022 .mhandler.cmd_new = qmp_marshal_input_transaction,
1029 Atomically operate on one or more block devices. The only supported operations
1030 for now are drive-backup, internal and external snapshotting. A list of
1031 dictionaries is accepted, that contains the actions to be performed.
1032 If there is any failure performing any of the operations, all operations
1033 for the group are abandoned.
1035 For external snapshots, the dictionary contains the device, the file to use for
1036 the new snapshot, and the format. The default format, if not specified, is
1039 Each new snapshot defaults to being created by QEMU (wiping any
1040 contents if the file already exists), but it is also possible to reuse
1041 an externally-created file. In the latter case, you should ensure that
1042 the new image file has the same contents as the current one; QEMU cannot
1043 perform any meaningful check. Typically this is achieved by using the
1044 current image file as the backing file for the new image.
1046 On failure, the original disks pre-snapshot attempt will be used.
1048 For internal snapshots, the dictionary contains the device and the snapshot's
1049 name. If an internal snapshot matching name already exists, the request will
1050 be rejected. Only some image formats support it, for example, qcow2, rbd,
1053 On failure, qemu will try delete the newly created internal snapshot in the
1054 transaction. When an I/O error occurs during deletion, the user needs to fix
1055 it later with qemu-img or other command.
1060 - "type": the operation to perform. The only supported
1061 value is "blockdev-snapshot-sync". (json-string)
1062 - "data": a dictionary. The contents depend on the value
1063 of "type". When "type" is "blockdev-snapshot-sync":
1064 - "device": device name to snapshot (json-string)
1065 - "snapshot-file": name of new image file (json-string)
1066 - "format": format of new image (json-string, optional)
1067 - "mode": whether and how QEMU should create the snapshot file
1068 (NewImageMode, optional, default "absolute-paths")
1069 When "type" is "blockdev-snapshot-internal-sync":
1070 - "device": device name to snapshot (json-string)
1071 - "name": name of the new snapshot (json-string)
1075 -> { "execute": "transaction",
1076 "arguments": { "actions": [
1077 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd0",
1078 "snapshot-file": "/some/place/my-image",
1079 "format": "qcow2" } },
1080 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd1",
1081 "snapshot-file": "/some/place/my-image2",
1083 "format": "qcow2" } },
1084 { 'type': 'blockdev-snapshot-internal-sync', 'data' : {
1085 "device": "ide-hd2",
1086 "name": "snapshot0" } } ] } }
1092 .name = "blockdev-snapshot-sync",
1093 .args_type = "device:B,snapshot-file:s,format:s?,mode:s?",
1094 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
1098 blockdev-snapshot-sync
1099 ----------------------
1101 Synchronous snapshot of a block device. snapshot-file specifies the
1102 target of the new image. If the file exists, or if it is a device, the
1103 snapshot will be created in the existing file/device. If does not
1104 exist, a new file will be created. format specifies the format of the
1105 snapshot image, default is qcow2.
1109 - "device": device name to snapshot (json-string)
1110 - "snapshot-file": name of new image file (json-string)
1111 - "mode": whether and how QEMU should create the snapshot file
1112 (NewImageMode, optional, default "absolute-paths")
1113 - "format": format of new image (json-string, optional)
1117 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
1119 "/some/place/my-image",
1120 "format": "qcow2" } }
1126 .name = "blockdev-snapshot-internal-sync",
1127 .args_type = "device:B,name:s",
1128 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_internal_sync,
1132 blockdev-snapshot-internal-sync
1133 -------------------------------
1135 Synchronously take an internal snapshot of a block device when the format of
1136 image used supports it. If the name is an empty string, or a snapshot with
1137 name already exists, the operation will fail.
1141 - "device": device name to snapshot (json-string)
1142 - "name": name of the new snapshot (json-string)
1146 -> { "execute": "blockdev-snapshot-internal-sync",
1147 "arguments": { "device": "ide-hd0",
1148 "name": "snapshot0" }
1155 .name = "blockdev-snapshot-delete-internal-sync",
1156 .args_type = "device:B,id:s?,name:s?",
1158 qmp_marshal_input_blockdev_snapshot_delete_internal_sync,
1162 blockdev-snapshot-delete-internal-sync
1163 --------------------------------------
1165 Synchronously delete an internal snapshot of a block device when the format of
1166 image used supports it. The snapshot is identified by name or id or both. One
1167 of name or id is required. If the snapshot is not found, the operation will
1172 - "device": device name (json-string)
1173 - "id": ID of the snapshot (json-string, optional)
1174 - "name": name of the snapshot (json-string, optional)
1178 -> { "execute": "blockdev-snapshot-delete-internal-sync",
1179 "arguments": { "device": "ide-hd0",
1180 "name": "snapshot0" }
1184 "name": "snapshot0",
1186 "date-sec": 1000012,
1188 "vm-clock-sec": 100,
1196 .name = "drive-mirror",
1197 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1198 "on-source-error:s?,on-target-error:s?,"
1199 "granularity:i?,buf-size:i?",
1200 .mhandler.cmd_new = qmp_marshal_input_drive_mirror,
1207 Start mirroring a block device's writes to a new destination. target
1208 specifies the target of the new image. If the file exists, or if it is
1209 a device, it will be used as the new destination for writes. If it does not
1210 exist, a new file will be created. format specifies the format of the
1211 mirror image, default is to probe if mode='existing', else the format
1216 - "device": device name to operate on (json-string)
1217 - "target": name of new image file (json-string)
1218 - "format": format of new image (json-string, optional)
1219 - "mode": how an image file should be created into the target
1220 file/device (NewImageMode, optional, default 'absolute-paths')
1221 - "speed": maximum speed of the streaming job, in bytes per second
1223 - "granularity": granularity of the dirty bitmap, in bytes (json-int, optional)
1224 - "buf_size": maximum amount of data in flight from source to target, in bytes
1225 (json-int, default 10M)
1226 - "sync": what parts of the disk image should be copied to the destination;
1227 possibilities include "full" for all the disk, "top" for only the sectors
1228 allocated in the topmost image, or "none" to only replicate new I/O
1230 - "on-source-error": the action to take on an error on the source
1231 (BlockdevOnError, default 'report')
1232 - "on-target-error": the action to take on an error on the target
1233 (BlockdevOnError, default 'report')
1235 The default value of the granularity is the image cluster size clamped
1236 between 4096 and 65536, if the image format defines one. If the format
1237 does not define a cluster size, the default value of the granularity
1243 -> { "execute": "drive-mirror", "arguments": { "device": "ide-hd0",
1244 "target": "/some/place/my-image",
1246 "format": "qcow2" } }
1253 .args_type = "value:M",
1254 .mhandler.cmd_new = qmp_marshal_input_balloon,
1261 Request VM to change its memory allocation (in bytes).
1265 - "value": New memory allocation (json-int)
1269 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1276 .args_type = "name:s,up:b",
1277 .mhandler.cmd_new = qmp_marshal_input_set_link,
1284 Change the link status of a network adapter.
1288 - "name": network device name (json-string)
1289 - "up": status is up (json-bool)
1293 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
1300 .args_type = "fdname:s",
1301 .params = "getfd name",
1302 .help = "receive a file descriptor via SCM rights and assign it a name",
1303 .mhandler.cmd_new = qmp_marshal_input_getfd,
1310 Receive a file descriptor via SCM rights and assign it a name.
1314 - "fdname": file descriptor name (json-string)
1318 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1323 (1) If the name specified by the "fdname" argument already exists,
1324 the file descriptor assigned to it will be closed and replaced
1325 by the received file descriptor.
1326 (2) The 'closefd' command can be used to explicitly close the file
1327 descriptor when it is no longer needed.
1333 .args_type = "fdname:s",
1334 .params = "closefd name",
1335 .help = "close a file descriptor previously passed via SCM rights",
1336 .mhandler.cmd_new = qmp_marshal_input_closefd,
1343 Close a file descriptor previously passed via SCM rights.
1347 - "fdname": file descriptor name (json-string)
1351 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1358 .args_type = "fdset-id:i?,opaque:s?",
1359 .params = "add-fd fdset-id opaque",
1360 .help = "Add a file descriptor, that was passed via SCM rights, to an fd set",
1361 .mhandler.cmd_new = qmp_marshal_input_add_fd,
1368 Add a file descriptor, that was passed via SCM rights, to an fd set.
1372 - "fdset-id": The ID of the fd set to add the file descriptor to.
1373 (json-int, optional)
1374 - "opaque": A free-form string that can be used to describe the fd.
1375 (json-string, optional)
1377 Return a json-object with the following information:
1379 - "fdset-id": The ID of the fd set that the fd was added to. (json-int)
1380 - "fd": The file descriptor that was received via SCM rights and added to the
1385 -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1386 <- { "return": { "fdset-id": 1, "fd": 3 } }
1390 (1) The list of fd sets is shared by all monitor connections.
1391 (2) If "fdset-id" is not specified, a new fd set will be created.
1396 .name = "remove-fd",
1397 .args_type = "fdset-id:i,fd:i?",
1398 .params = "remove-fd fdset-id fd",
1399 .help = "Remove a file descriptor from an fd set",
1400 .mhandler.cmd_new = qmp_marshal_input_remove_fd,
1407 Remove a file descriptor from an fd set.
1411 - "fdset-id": The ID of the fd set that the file descriptor belongs to.
1413 - "fd": The file descriptor that is to be removed. (json-int, optional)
1417 -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1422 (1) The list of fd sets is shared by all monitor connections.
1423 (2) If "fd" is not specified, all file descriptors in "fdset-id" will be
1429 .name = "query-fdsets",
1431 .help = "Return information describing all fd sets",
1432 .mhandler.cmd_new = qmp_marshal_input_query_fdsets,
1439 Return information describing all fd sets.
1445 -> { "execute": "query-fdsets" }
1451 "opaque": "rdonly:/path/to/file"
1455 "opaque": "rdwr:/path/to/file"
1474 Note: The list of fd sets is shared by all monitor connections.
1479 .name = "block_passwd",
1480 .args_type = "device:B,password:s",
1481 .mhandler.cmd_new = qmp_marshal_input_block_passwd,
1488 Set the password of encrypted block devices.
1492 - "device": device name (json-string)
1493 - "password": password (json-string)
1497 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
1498 "password": "12345" } }
1504 .name = "block_set_io_throttle",
1505 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l,bps_max:l?,bps_rd_max:l?,bps_wr_max:l?,iops_max:l?,iops_rd_max:l?,iops_wr_max:l?,iops_size:l?",
1506 .mhandler.cmd_new = qmp_marshal_input_block_set_io_throttle,
1510 block_set_io_throttle
1513 Change I/O throttle limits for a block drive.
1517 - "device": device name (json-string)
1518 - "bps": total throughput limit in bytes per second (json-int)
1519 - "bps_rd": read throughput limit in bytes per second (json-int)
1520 - "bps_wr": write throughput limit in bytes per second (json-int)
1521 - "iops": total I/O operations per second (json-int)
1522 - "iops_rd": read I/O operations per second (json-int)
1523 - "iops_wr": write I/O operations per second (json-int)
1524 - "bps_max": total max in bytes (json-int)
1525 - "bps_rd_max": read max in bytes (json-int)
1526 - "bps_wr_max": write max in bytes (json-int)
1527 - "iops_max": total I/O operations max (json-int)
1528 - "iops_rd_max": read I/O operations max (json-int)
1529 - "iops_wr_max": write I/O operations max (json-int)
1530 - "iops_size": I/O size in bytes when limiting (json-int)
1534 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
1553 .name = "set_password",
1554 .args_type = "protocol:s,password:s,connected:s?",
1555 .mhandler.cmd_new = qmp_marshal_input_set_password,
1562 Set the password for vnc/spice protocols.
1566 - "protocol": protocol name (json-string)
1567 - "password": password (json-string)
1568 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
1572 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
1573 "password": "secret" } }
1579 .name = "expire_password",
1580 .args_type = "protocol:s,time:s",
1581 .mhandler.cmd_new = qmp_marshal_input_expire_password,
1588 Set the password expire time for vnc/spice protocols.
1592 - "protocol": protocol name (json-string)
1593 - "time": [ now | never | +secs | secs ] (json-string)
1597 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
1604 .name = "add_client",
1605 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
1606 .mhandler.cmd_new = qmp_marshal_input_add_client,
1613 Add a graphics client
1617 - "protocol": protocol name (json-string)
1618 - "fdname": file descriptor name (json-string)
1619 - "skipauth": whether to skip authentication (json-bool, optional)
1620 - "tls": whether to perform TLS (json-bool, optional)
1624 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
1625 "fdname": "myclient" } }
1630 .name = "qmp_capabilities",
1633 .help = "enable QMP capabilities",
1634 .user_print = monitor_user_noop,
1635 .mhandler.cmd_new = do_qmp_capabilities,
1642 Enable QMP capabilities.
1648 -> { "execute": "qmp_capabilities" }
1651 Note: This command must be issued before issuing any other command.
1656 .name = "human-monitor-command",
1657 .args_type = "command-line:s,cpu-index:i?",
1658 .mhandler.cmd_new = qmp_marshal_input_human_monitor_command,
1662 human-monitor-command
1663 ---------------------
1665 Execute a Human Monitor command.
1669 - command-line: the command name and its arguments, just like the
1670 Human Monitor's shell (json-string)
1671 - cpu-index: select the CPU number to be used by commands which access CPU
1672 data, like 'info registers'. The Monitor selects CPU 0 if this
1673 argument is not provided (json-int, optional)
1677 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1678 <- { "return": "kvm support: enabled\r\n" }
1682 (1) The Human Monitor is NOT an stable interface, this means that command
1683 names, arguments and responses can change or be removed at ANY time.
1684 Applications that rely on long term stability guarantees should NOT
1689 o This command is stateless, this means that commands that depend
1690 on state information (such as getfd) might not work
1692 o Commands that prompt the user for data (eg. 'cont' when the block
1693 device is encrypted) don't currently work
1698 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1699 HXCOMM this! We will possibly move query commands definitions inside those
1700 HXCOMM sections, just like regular commands.
1710 Return a json-object with the following information:
1712 - "qemu": A json-object containing three integer values:
1713 - "major": QEMU's major version (json-int)
1714 - "minor": QEMU's minor version (json-int)
1715 - "micro": QEMU's micro version (json-int)
1716 - "package": package's version (json-string)
1720 -> { "execute": "query-version" }
1735 .name = "query-version",
1737 .mhandler.cmd_new = qmp_marshal_input_query_version,
1744 List QMP available commands.
1746 Each command is represented by a json-object, the returned value is a json-array
1749 Each json-object contain:
1751 - "name": command's name (json-string)
1755 -> { "execute": "query-commands" }
1759 "name":"query-balloon"
1762 "name":"system_powerdown"
1767 Note: This example has been shortened as the real response is too long.
1772 .name = "query-commands",
1774 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1781 List QMP available events.
1783 Each event is represented by a json-object, the returned value is a json-array
1786 Each json-object contains:
1788 - "name": event's name (json-string)
1792 -> { "execute": "query-events" }
1804 Note: This example has been shortened as the real response is too long.
1809 .name = "query-events",
1811 .mhandler.cmd_new = qmp_marshal_input_query_events,
1818 Each device is represented by a json-object. The returned value is a json-array
1821 Each json-object contain the following:
1823 - "label": device's label (json-string)
1824 - "filename": device's file (json-string)
1828 -> { "execute": "query-chardev" }
1845 .name = "query-chardev",
1847 .mhandler.cmd_new = qmp_marshal_input_query_chardev,
1854 Show the block devices.
1856 Each block device information is stored in a json-object and the returned value
1857 is a json-array of all devices.
1859 Each json-object contain the following:
1861 - "device": device name (json-string)
1862 - "type": device type (json-string)
1863 - deprecated, retained for backward compatibility
1864 - Possible values: "unknown"
1865 - "removable": true if the device is removable, false otherwise (json-bool)
1866 - "locked": true if the device is locked, false otherwise (json-bool)
1867 - "tray_open": only present if removable, true if the device has a tray,
1868 and it is open (json-bool)
1869 - "inserted": only present if the device is inserted, it is a json-object
1870 containing the following:
1871 - "file": device file name (json-string)
1872 - "ro": true if read-only, false otherwise (json-bool)
1873 - "drv": driver format name (json-string)
1874 - Possible values: "blkdebug", "bochs", "cloop", "cow", "dmg",
1875 "file", "file", "ftp", "ftps", "host_cdrom",
1876 "host_device", "host_floppy", "http", "https",
1877 "nbd", "parallels", "qcow", "qcow2", "raw",
1878 "tftp", "vdi", "vmdk", "vpc", "vvfat"
1879 - "backing_file": backing file name (json-string, optional)
1880 - "backing_file_depth": number of files in the backing file chain (json-int)
1881 - "encrypted": true if encrypted, false otherwise (json-bool)
1882 - "bps": limit total bytes per second (json-int)
1883 - "bps_rd": limit read bytes per second (json-int)
1884 - "bps_wr": limit write bytes per second (json-int)
1885 - "iops": limit total I/O operations per second (json-int)
1886 - "iops_rd": limit read operations per second (json-int)
1887 - "iops_wr": limit write operations per second (json-int)
1888 - "bps_max": total max in bytes (json-int)
1889 - "bps_rd_max": read max in bytes (json-int)
1890 - "bps_wr_max": write max in bytes (json-int)
1891 - "iops_max": total I/O operations max (json-int)
1892 - "iops_rd_max": read I/O operations max (json-int)
1893 - "iops_wr_max": write I/O operations max (json-int)
1894 - "iops_size": I/O size when limiting by iops (json-int)
1895 - "image": the detail of the image, it is a json-object containing
1897 - "filename": image file name (json-string)
1898 - "format": image format (json-string)
1899 - "virtual-size": image capacity in bytes (json-int)
1900 - "dirty-flag": true if image is not cleanly closed, not present
1901 means clean (json-bool, optional)
1902 - "actual-size": actual size on disk in bytes of the image, not
1903 present when image does not support thin
1904 provision (json-int, optional)
1905 - "cluster-size": size of a cluster in bytes, not present if image
1906 format does not support it (json-int, optional)
1907 - "encrypted": true if the image is encrypted, not present means
1908 false or the image format does not support
1909 encryption (json-bool, optional)
1910 - "backing_file": backing file name, not present means no backing
1911 file is used or the image format does not
1912 support backing file chain
1913 (json-string, optional)
1914 - "full-backing-filename": full path of the backing file, not
1915 present if it equals backing_file or no
1916 backing file is used
1917 (json-string, optional)
1918 - "backing-filename-format": the format of the backing file, not
1919 present means unknown or no backing
1920 file (json-string, optional)
1921 - "snapshots": the internal snapshot info, it is an optional list
1922 of json-object containing the following:
1923 - "id": unique snapshot id (json-string)
1924 - "name": snapshot name (json-string)
1925 - "vm-state-size": size of the VM state in bytes (json-int)
1926 - "date-sec": UTC date of the snapshot in seconds (json-int)
1927 - "date-nsec": fractional part in nanoseconds to be used with
1929 - "vm-clock-sec": VM clock relative to boot in seconds
1931 - "vm-clock-nsec": fractional part in nanoseconds to be used
1932 with vm-clock-sec (json-int)
1933 - "backing-image": the detail of the backing image, it is an
1934 optional json-object only present when a
1935 backing image present for this image
1937 - "io-status": I/O operation status, only present if the device supports it
1938 and the VM is configured to stop on errors. It's always reset
1939 to "ok" when the "cont" command is issued (json_string, optional)
1940 - Possible values: "ok", "failed", "nospace"
1944 -> { "execute": "query-block" }
1949 "device":"ide0-hd0",
1956 "file":"disks/test.qcow2",
1957 "backing_file_depth":1,
1972 "filename":"disks/test.qcow2",
1974 "virtual-size":2048000,
1975 "backing_file":"base.qcow2",
1976 "full-backing-filename":"disks/base.qcow2",
1977 "backing-filename-format:"qcow2",
1981 "name": "snapshot1",
1983 "date-sec": 10000200,
1985 "vm-clock-sec": 206,
1990 "filename":"disks/base.qcow2",
1992 "virtual-size":2048000
2000 "device":"ide1-cd0",
2023 .name = "query-block",
2025 .mhandler.cmd_new = qmp_marshal_input_query_block,
2032 Show block device statistics.
2034 Each device statistic information is stored in a json-object and the returned
2035 value is a json-array of all devices.
2037 Each json-object contain the following:
2039 - "device": device name (json-string)
2040 - "stats": A json-object with the statistics information, it contains:
2041 - "rd_bytes": bytes read (json-int)
2042 - "wr_bytes": bytes written (json-int)
2043 - "rd_operations": read operations (json-int)
2044 - "wr_operations": write operations (json-int)
2045 - "flush_operations": cache flush operations (json-int)
2046 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
2047 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
2048 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
2049 - "wr_highest_offset": Highest offset of a sector written since the
2050 BlockDriverState has been opened (json-int)
2051 - "parent": Contains recursively the statistics of the underlying
2052 protocol (e.g. the host file for a qcow2 image). If there is
2053 no underlying protocol, this field is omitted
2054 (json-object, optional)
2058 -> { "execute": "query-blockstats" }
2062 "device":"ide0-hd0",
2065 "wr_highest_offset":3686448128,
2067 "wr_operations":751,
2068 "rd_bytes":122567168,
2069 "rd_operations":36772
2070 "wr_total_times_ns":313253456
2071 "rd_total_times_ns":3465673657
2072 "flush_total_times_ns":49653
2073 "flush_operations":61,
2077 "wr_highest_offset":2821110784,
2079 "wr_operations":692,
2080 "rd_bytes":122739200,
2081 "rd_operations":36604
2082 "flush_operations":51,
2083 "wr_total_times_ns":313253456
2084 "rd_total_times_ns":3465673657
2085 "flush_total_times_ns":49653
2089 "device":"ide1-cd0",
2091 "wr_highest_offset":0,
2096 "flush_operations":0,
2097 "wr_total_times_ns":0
2098 "rd_total_times_ns":0
2099 "flush_total_times_ns":0
2105 "wr_highest_offset":0,
2110 "flush_operations":0,
2111 "wr_total_times_ns":0
2112 "rd_total_times_ns":0
2113 "flush_total_times_ns":0
2119 "wr_highest_offset":0,
2124 "flush_operations":0,
2125 "wr_total_times_ns":0
2126 "rd_total_times_ns":0
2127 "flush_total_times_ns":0
2136 .name = "query-blockstats",
2138 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
2145 Show CPU information.
2147 Return a json-array. Each CPU is represented by a json-object, which contains:
2149 - "CPU": CPU index (json-int)
2150 - "current": true if this is the current CPU, false otherwise (json-bool)
2151 - "halted": true if the cpu is halted, false otherwise (json-bool)
2152 - Current program counter. The key's name depends on the architecture:
2153 "pc": i386/x86_64 (json-int)
2154 "nip": PPC (json-int)
2155 "pc" and "npc": sparc (json-int)
2156 "PC": mips (json-int)
2157 - "thread_id": ID of the underlying host thread (json-int)
2161 -> { "execute": "query-cpus" }
2184 .name = "query-cpus",
2186 .mhandler.cmd_new = qmp_marshal_input_query_cpus,
2193 PCI buses and devices information.
2195 The returned value is a json-array of all buses. Each bus is represented by
2196 a json-object, which has a key with a json-array of all PCI devices attached
2197 to it. Each device is represented by a json-object.
2199 The bus json-object contains the following:
2201 - "bus": bus number (json-int)
2202 - "devices": a json-array of json-objects, each json-object represents a
2205 The PCI device json-object contains the following:
2207 - "bus": identical to the parent's bus number (json-int)
2208 - "slot": slot number (json-int)
2209 - "function": function number (json-int)
2210 - "class_info": a json-object containing:
2211 - "desc": device class description (json-string, optional)
2212 - "class": device class number (json-int)
2213 - "id": a json-object containing:
2214 - "device": device ID (json-int)
2215 - "vendor": vendor ID (json-int)
2216 - "irq": device's IRQ if assigned (json-int, optional)
2217 - "qdev_id": qdev id string (json-string)
2218 - "pci_bridge": It's a json-object, only present if this device is a
2219 PCI bridge, contains:
2220 - "bus": bus number (json-int)
2221 - "secondary": secondary bus number (json-int)
2222 - "subordinate": subordinate bus number (json-int)
2223 - "io_range": I/O memory range information, a json-object with the
2225 - "base": base address, in bytes (json-int)
2226 - "limit": limit address, in bytes (json-int)
2227 - "memory_range": memory range information, a json-object with the
2229 - "base": base address, in bytes (json-int)
2230 - "limit": limit address, in bytes (json-int)
2231 - "prefetchable_range": Prefetchable memory range information, a
2232 json-object with the following members:
2233 - "base": base address, in bytes (json-int)
2234 - "limit": limit address, in bytes (json-int)
2235 - "devices": a json-array of PCI devices if there's any attached, each
2236 each element is represented by a json-object, which contains
2237 the same members of the 'PCI device json-object' described
2239 - "regions": a json-array of json-objects, each json-object represents a
2240 memory region of this device
2242 The memory range json-object contains the following:
2244 - "base": base memory address (json-int)
2245 - "limit": limit value (json-int)
2247 The region json-object can be an I/O region or a memory region, an I/O region
2248 json-object contains the following:
2250 - "type": "io" (json-string, fixed)
2251 - "bar": BAR number (json-int)
2252 - "address": memory address (json-int)
2253 - "size": memory size (json-int)
2255 A memory region json-object contains the following:
2257 - "type": "memory" (json-string, fixed)
2258 - "bar": BAR number (json-int)
2259 - "address": memory address (json-int)
2260 - "size": memory size (json-int)
2261 - "mem_type_64": true or false (json-bool)
2262 - "prefetch": true or false (json-bool)
2266 -> { "execute": "query-pci" }
2278 "desc":"Host bridge"
2312 "desc":"IDE controller"
2334 "desc":"VGA controller"
2344 "mem_type_64":false,
2347 "address":4026531840,
2352 "mem_type_64":false,
2355 "address":4060086272,
2360 "mem_type_64":false,
2375 "desc":"RAM controller"
2396 Note: This example has been shortened as the real response is too long.
2401 .name = "query-pci",
2403 .mhandler.cmd_new = qmp_marshal_input_query_pci,
2410 Show KVM information.
2412 Return a json-object with the following information:
2414 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
2415 - "present": true if QEMU has KVM support, false otherwise (json-bool)
2419 -> { "execute": "query-kvm" }
2420 <- { "return": { "enabled": true, "present": true } }
2425 .name = "query-kvm",
2427 .mhandler.cmd_new = qmp_marshal_input_query_kvm,
2434 Return a json-object with the following information:
2436 - "running": true if the VM is running, or false if it is paused (json-bool)
2437 - "singlestep": true if the VM is in single step mode,
2438 false otherwise (json-bool)
2439 - "status": one of the following values (json-string)
2440 "debug" - QEMU is running on a debugger
2441 "inmigrate" - guest is paused waiting for an incoming migration
2442 "internal-error" - An internal error that prevents further guest
2443 execution has occurred
2444 "io-error" - the last IOP has failed and the device is configured
2445 to pause on I/O errors
2446 "paused" - guest has been paused via the 'stop' command
2447 "postmigrate" - guest is paused following a successful 'migrate'
2448 "prelaunch" - QEMU was started with -S and guest has not started
2449 "finish-migrate" - guest is paused to finish the migration process
2450 "restore-vm" - guest is paused to restore VM state
2451 "running" - guest is actively running
2452 "save-vm" - guest is paused to save the VM state
2453 "shutdown" - guest is shut down (and -no-shutdown is in use)
2454 "watchdog" - the watchdog action is configured to pause and
2459 -> { "execute": "query-status" }
2460 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
2465 .name = "query-status",
2467 .mhandler.cmd_new = qmp_marshal_input_query_status,
2474 Show VM mice information.
2476 Each mouse is represented by a json-object, the returned value is a json-array
2479 The mouse json-object contains the following:
2481 - "name": mouse's name (json-string)
2482 - "index": mouse's index (json-int)
2483 - "current": true if this mouse is receiving events, false otherwise (json-bool)
2484 - "absolute": true if the mouse generates absolute input events (json-bool)
2488 -> { "execute": "query-mice" }
2492 "name":"QEMU Microsoft Mouse",
2498 "name":"QEMU PS/2 Mouse",
2509 .name = "query-mice",
2511 .mhandler.cmd_new = qmp_marshal_input_query_mice,
2518 Show VNC server information.
2520 Return a json-object with server information. Connected clients are returned
2521 as a json-array of json-objects.
2523 The main json-object contains the following:
2525 - "enabled": true or false (json-bool)
2526 - "host": server's IP address (json-string)
2527 - "family": address family (json-string)
2528 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2529 - "service": server's port number (json-string)
2530 - "auth": authentication method (json-string)
2531 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
2532 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
2533 "vencrypt+plain", "vencrypt+tls+none",
2534 "vencrypt+tls+plain", "vencrypt+tls+sasl",
2535 "vencrypt+tls+vnc", "vencrypt+x509+none",
2536 "vencrypt+x509+plain", "vencrypt+x509+sasl",
2537 "vencrypt+x509+vnc", "vnc"
2538 - "clients": a json-array of all connected clients
2540 Clients are described by a json-object, each one contain the following:
2542 - "host": client's IP address (json-string)
2543 - "family": address family (json-string)
2544 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2545 - "service": client's port number (json-string)
2546 - "x509_dname": TLS dname (json-string, optional)
2547 - "sasl_username": SASL username (json-string, optional)
2551 -> { "execute": "query-vnc" }
2572 .name = "query-vnc",
2574 .mhandler.cmd_new = qmp_marshal_input_query_vnc,
2581 Show SPICE server information.
2583 Return a json-object with server information. Connected clients are returned
2584 as a json-array of json-objects.
2586 The main json-object contains the following:
2588 - "enabled": true or false (json-bool)
2589 - "host": server's IP address (json-string)
2590 - "port": server's port number (json-int, optional)
2591 - "tls-port": server's port number (json-int, optional)
2592 - "auth": authentication method (json-string)
2593 - Possible values: "none", "spice"
2594 - "channels": a json-array of all active channels clients
2596 Channels are described by a json-object, each one contain the following:
2598 - "host": client's IP address (json-string)
2599 - "family": address family (json-string)
2600 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2601 - "port": client's port number (json-string)
2602 - "connection-id": spice connection id. All channels with the same id
2603 belong to the same spice session (json-int)
2604 - "channel-type": channel type. "1" is the main control channel, filter for
2605 this one if you want track spice sessions only (json-int)
2606 - "channel-id": channel id. Usually "0", might be different needed when
2607 multiple channels of the same type exist, such as multiple
2608 display channels in a multihead setup (json-int)
2609 - "tls": whevener the channel is encrypted (json-bool)
2613 -> { "execute": "query-spice" }
2626 "connection-id": 1804289383,
2627 "host": "127.0.0.1",
2635 "connection-id": 1804289383,
2636 "host": "127.0.0.1",
2640 [ ... more channels follow ... ]
2647 #if defined(CONFIG_SPICE)
2649 .name = "query-spice",
2651 .mhandler.cmd_new = qmp_marshal_input_query_spice,
2661 Return a json-object with the following information:
2663 - "name": VM's name (json-string, optional)
2667 -> { "execute": "query-name" }
2668 <- { "return": { "name": "qemu-name" } }
2673 .name = "query-name",
2675 .mhandler.cmd_new = qmp_marshal_input_query_name,
2684 Return a json-object with the following information:
2686 - "UUID": Universally Unique Identifier (json-string)
2690 -> { "execute": "query-uuid" }
2691 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
2696 .name = "query-uuid",
2698 .mhandler.cmd_new = qmp_marshal_input_query_uuid,
2702 query-command-line-options
2703 --------------------------
2705 Show command line option schema.
2707 Return a json-array of command line option schema for all options (or for
2708 the given option), returning an error if the given option doesn't exist.
2710 Each array entry contains the following:
2712 - "option": option name (json-string)
2713 - "parameters": a json-array describes all parameters of the option:
2714 - "name": parameter name (json-string)
2715 - "type": parameter type (one of 'string', 'boolean', 'number',
2717 - "help": human readable description of the parameter
2718 (json-string, optional)
2722 -> { "execute": "query-command-line-options", "arguments": { "option": "option-rom" } }
2731 "name": "bootindex",
2735 "option": "option-rom"
2743 .name = "query-command-line-options",
2744 .args_type = "option:s?",
2745 .mhandler.cmd_new = qmp_marshal_input_query_command_line_options,
2754 Return a json-object. If migration is active there will be another json-object
2755 with RAM migration status and if block migration is active another one with
2756 block migration status.
2758 The main json-object contains the following:
2760 - "status": migration status (json-string)
2761 - Possible values: "active", "completed", "failed", "cancelled"
2762 - "total-time": total amount of ms since migration started. If
2763 migration has ended, it returns the total migration
2765 - "setup-time" amount of setup time in milliseconds _before_ the
2766 iterations begin but _after_ the QMP command is issued.
2767 This is designed to provide an accounting of any activities
2768 (such as RDMA pinning) which may be expensive, but do not
2769 actually occur during the iterative migration rounds
2770 themselves. (json-int)
2771 - "downtime": only present when migration has finished correctly
2772 total amount in ms for downtime that happened (json-int)
2773 - "expected-downtime": only present while migration is active
2774 total amount in ms for downtime that was calculated on
2775 the last bitmap round (json-int)
2776 - "ram": only present if "status" is "active", it is a json-object with the
2777 following RAM information:
2778 - "transferred": amount transferred in bytes (json-int)
2779 - "remaining": amount remaining to transfer in bytes (json-int)
2780 - "total": total amount of memory in bytes (json-int)
2781 - "duplicate": number of pages filled entirely with the same
2783 These are sent over the wire much more efficiently.
2784 - "skipped": number of skipped zero pages (json-int)
2785 - "normal" : number of whole pages transferred. I.e. they
2786 were not sent as duplicate or xbzrle pages (json-int)
2787 - "normal-bytes" : number of bytes transferred in whole
2788 pages. This is just normal pages times size of one page,
2789 but this way upper levels don't need to care about page
2791 - "disk": only present if "status" is "active" and it is a block migration,
2792 it is a json-object with the following disk information:
2793 - "transferred": amount transferred in bytes (json-int)
2794 - "remaining": amount remaining to transfer in bytes json-int)
2795 - "total": total disk size in bytes (json-int)
2796 - "xbzrle-cache": only present if XBZRLE is active.
2797 It is a json-object with the following XBZRLE information:
2798 - "cache-size": XBZRLE cache size in bytes
2799 - "bytes": number of bytes transferred for XBZRLE compressed pages
2800 - "pages": number of XBZRLE compressed pages
2801 - "cache-miss": number of XBRZRLE page cache misses
2802 - "overflow": number of times XBZRLE overflows. This means
2803 that the XBZRLE encoding was bigger than just sent the
2804 whole page, and then we sent the whole page instead (as as
2809 1. Before the first migration
2811 -> { "execute": "query-migrate" }
2814 2. Migration is done and has succeeded
2816 -> { "execute": "query-migrate" }
2818 "status": "completed",
2828 "normal-bytes":123456
2833 3. Migration is done and has failed
2835 -> { "execute": "query-migrate" }
2836 <- { "return": { "status": "failed" } }
2838 4. Migration is being performed and is not a block migration:
2840 -> { "execute": "query-migrate" }
2850 "expected-downtime":12345,
2853 "normal-bytes":123456
2858 5. Migration is being performed and is a block migration:
2860 -> { "execute": "query-migrate" }
2866 "remaining":1053304,
2870 "expected-downtime":12345,
2873 "normal-bytes":123456
2877 "remaining":20880384,
2883 6. Migration is being performed and XBZRLE is active:
2885 -> { "execute": "query-migrate" }
2889 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
2892 "remaining":1053304,
2896 "expected-downtime":12345,
2899 "normal-bytes":3412992
2902 "cache-size":67108864,
2914 .name = "query-migrate",
2916 .mhandler.cmd_new = qmp_marshal_input_query_migrate,
2920 migrate-set-capabilities
2921 ------------------------
2923 Enable/Disable migration capabilities
2925 - "xbzrle": XBZRLE support
2931 -> { "execute": "migrate-set-capabilities" , "arguments":
2932 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
2937 .name = "migrate-set-capabilities",
2938 .args_type = "capabilities:O",
2939 .params = "capability:s,state:b",
2940 .mhandler.cmd_new = qmp_marshal_input_migrate_set_capabilities,
2943 query-migrate-capabilities
2944 --------------------------
2946 Query current migration capabilities
2948 - "capabilities": migration capabilities state
2949 - "xbzrle" : XBZRLE state (json-bool)
2955 -> { "execute": "query-migrate-capabilities" }
2956 <- { "return": [ { "state": false, "capability": "xbzrle" } ] }
2961 .name = "query-migrate-capabilities",
2963 .mhandler.cmd_new = qmp_marshal_input_query_migrate_capabilities,
2970 Show balloon information.
2972 Make an asynchronous request for balloon info. When the request completes a
2973 json-object will be returned containing the following data:
2975 - "actual": current balloon value in bytes (json-int)
2979 -> { "execute": "query-balloon" }
2982 "actual":1073741824,
2989 .name = "query-balloon",
2991 .mhandler.cmd_new = qmp_marshal_input_query_balloon,
2995 .name = "query-block-jobs",
2997 .mhandler.cmd_new = qmp_marshal_input_query_block_jobs,
3002 .args_type = "path:s",
3003 .mhandler.cmd_new = qmp_marshal_input_qom_list,
3008 .args_type = "path:s,property:s,value:q",
3009 .mhandler.cmd_new = qmp_qom_set,
3014 .args_type = "path:s,property:s",
3015 .mhandler.cmd_new = qmp_qom_get,
3019 .name = "nbd-server-start",
3020 .args_type = "addr:q",
3021 .mhandler.cmd_new = qmp_marshal_input_nbd_server_start,
3024 .name = "nbd-server-add",
3025 .args_type = "device:B,writable:b?",
3026 .mhandler.cmd_new = qmp_marshal_input_nbd_server_add,
3029 .name = "nbd-server-stop",
3031 .mhandler.cmd_new = qmp_marshal_input_nbd_server_stop,
3035 .name = "change-vnc-password",
3036 .args_type = "password:s",
3037 .mhandler.cmd_new = qmp_marshal_input_change_vnc_password,
3040 .name = "qom-list-types",
3041 .args_type = "implements:s?,abstract:b?",
3042 .mhandler.cmd_new = qmp_marshal_input_qom_list_types,
3046 .name = "device-list-properties",
3047 .args_type = "typename:s",
3048 .mhandler.cmd_new = qmp_marshal_input_device_list_properties,
3052 .name = "query-machines",
3054 .mhandler.cmd_new = qmp_marshal_input_query_machines,
3058 .name = "query-cpu-definitions",
3060 .mhandler.cmd_new = qmp_marshal_input_query_cpu_definitions,
3064 .name = "query-target",
3066 .mhandler.cmd_new = qmp_marshal_input_query_target,
3070 .name = "query-tpm",
3072 .mhandler.cmd_new = qmp_marshal_input_query_tpm,
3079 Return information about the TPM device.
3085 -> { "execute": "query-tpm" }
3088 { "model": "tpm-tis",
3090 { "type": "passthrough",
3092 { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
3104 .name = "query-tpm-models",
3106 .mhandler.cmd_new = qmp_marshal_input_query_tpm_models,
3113 Return a list of supported TPM models.
3119 -> { "execute": "query-tpm-models" }
3120 <- { "return": [ "tpm-tis" ] }
3125 .name = "query-tpm-types",
3127 .mhandler.cmd_new = qmp_marshal_input_query_tpm_types,
3134 Return a list of supported TPM types.
3140 -> { "execute": "query-tpm-types" }
3141 <- { "return": [ "passthrough" ] }
3146 .name = "chardev-add",
3147 .args_type = "id:s,backend:q",
3148 .mhandler.cmd_new = qmp_marshal_input_chardev_add,
3159 - "id": the chardev's ID, must be unique (json-string)
3160 - "backend": chardev backend type + parameters
3164 -> { "execute" : "chardev-add",
3165 "arguments" : { "id" : "foo",
3166 "backend" : { "type" : "null", "data" : {} } } }
3169 -> { "execute" : "chardev-add",
3170 "arguments" : { "id" : "bar",
3171 "backend" : { "type" : "file",
3172 "data" : { "out" : "/tmp/bar.log" } } } }
3175 -> { "execute" : "chardev-add",
3176 "arguments" : { "id" : "baz",
3177 "backend" : { "type" : "pty", "data" : {} } } }
3178 <- { "return": { "pty" : "/dev/pty/42" } }
3183 .name = "chardev-remove",
3184 .args_type = "id:s",
3185 .mhandler.cmd_new = qmp_marshal_input_chardev_remove,
3197 - "id": the chardev's ID, must exist and not be in use (json-string)
3201 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }
3206 .name = "query-rx-filter",
3207 .args_type = "name:s?",
3208 .mhandler.cmd_new = qmp_marshal_input_query_rx_filter,
3215 Show rx-filter information.
3217 Returns a json-array of rx-filter information for all NICs (or for the
3218 given NIC), returning an error if the given NIC doesn't exist, or
3219 given NIC doesn't support rx-filter querying, or given net client
3222 The query will clear the event notification flag of each NIC, then qemu
3223 will start to emit event to QMP monitor.
3225 Each array entry contains the following:
3227 - "name": net client name (json-string)
3228 - "promiscuous": promiscuous mode is enabled (json-bool)
3229 - "multicast": multicast receive state (one of 'normal', 'none', 'all')
3230 - "unicast": unicast receive state (one of 'normal', 'none', 'all')
3231 - "broadcast-allowed": allow to receive broadcast (json-bool)
3232 - "multicast-overflow": multicast table is overflowed (json-bool)
3233 - "unicast-overflow": unicast table is overflowed (json-bool)
3234 - "main-mac": main macaddr string (json-string)
3235 - "vlan-table": a json-array of active vlan id
3236 - "unicast-table": a json-array of unicast macaddr string
3237 - "multicast-table": a json-array of multicast macaddr string
3241 -> { "execute": "query-rx-filter", "arguments": { "name": "vnet0" } }
3244 "promiscuous": true,
3246 "main-mac": "52:54:00:12:34:56",
3247 "unicast": "normal",
3254 "multicast": "normal",
3255 "multicast-overflow": false,
3256 "unicast-overflow": false,
3257 "multicast-table": [
3258 "01:00:5e:00:00:01",
3259 "33:33:00:00:00:01",
3262 "broadcast-allowed": false
3270 .name = "blockdev-add",
3271 .args_type = "options:q",
3272 .mhandler.cmd_new = qmp_marshal_input_blockdev_add,
3283 - "options": block driver options
3287 -> { "execute": "blockdev-add",
3288 "arguments": { "options" : { "driver": "qcow2",
3289 "file": { "driver": "file",
3290 "filename": "test.qcow2" } } } }
3295 -> { "execute": "blockdev-add",
3307 "filename": "/tmp/test.qcow2"
3313 "filename": "/dev/fdset/4"