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 enum values)
351 - hold-time: time to delay key up events, milliseconds. Defaults to 100
356 -> { "execute": "send-key",
357 "arguments": { 'keys': [ 'ctrl', 'alt', 'delete' ] } }
364 .args_type = "index:i",
365 .mhandler.cmd_new = qmp_marshal_input_cpu,
376 - "index": the CPU's index (json-int)
380 -> { "execute": "cpu", "arguments": { "index": 0 } }
383 Note: CPUs' indexes are obtained with the 'query-cpus' command.
389 .args_type = "val:l,size:i,filename:s,cpu:i?",
390 .mhandler.cmd_new = qmp_marshal_input_memsave,
397 Save to disk virtual memory dump starting at 'val' of size 'size'.
401 - "val": the starting address (json-int)
402 - "size": the memory size, in bytes (json-int)
403 - "filename": file path (json-string)
404 - "cpu": virtual CPU index (json-int, optional)
408 -> { "execute": "memsave",
409 "arguments": { "val": 10,
411 "filename": "/tmp/virtual-mem-dump" } }
418 .args_type = "val:l,size:i,filename:s",
419 .mhandler.cmd_new = qmp_marshal_input_pmemsave,
426 Save to disk physical memory dump starting at 'val' of size 'size'.
430 - "val": the starting address (json-int)
431 - "size": the memory size, in bytes (json-int)
432 - "filename": file path (json-string)
436 -> { "execute": "pmemsave",
437 "arguments": { "val": 10,
439 "filename": "/tmp/physical-mem-dump" } }
445 .name = "inject-nmi",
447 .mhandler.cmd_new = qmp_marshal_input_inject_nmi,
454 Inject an NMI on guest's CPUs.
460 -> { "execute": "inject-nmi" }
463 Note: inject-nmi fails when the guest doesn't support injecting.
464 Currently, only x86 guests do.
469 .name = "memchar-write",
470 .args_type = "device:s,size:i,data:s,format:s?",
471 .mhandler.cmd_new = qmp_marshal_input_memchar_write,
478 Provide writing interface for CirMemCharDriver. Write data to memory
483 - "device": the name of the char device, must be unique (json-string)
484 - "size": the memory size, in bytes, should be power of 2 (json-int)
485 - "data": the source data write to memory (json-string)
486 - "format": the data format write to memory, default is
487 utf8. (json-string, optional)
488 - Possible values: "utf8", "base64"
492 -> { "execute": "memchar-write",
493 "arguments": { "device": foo,
502 .name = "memchar-read",
503 .args_type = "device:s,size:i,format:s?",
504 .mhandler.cmd_new = qmp_marshal_input_memchar_read,
511 Provide read interface for CirMemCharDriver. Read from the char
512 device memory and return the data with size.
516 - "device": the name of the char device, must be unique (json-string)
517 - "size": the memory size wanted to read in bytes (refer to unencoded
518 size of the raw data), would adjust to the init size of the
519 memchar if the requested size is larger than it. (json-int)
520 - "format": the data format write to memchardev, default is
521 utf8. (json-string, optional)
522 - Possible values: "utf8", "base64"
526 -> { "execute": "memchar-read",
527 "arguments": { "device": foo,
530 <- { "return": { "data": "data string...", "count": 1000 } }
535 .name = "xen-save-devices-state",
536 .args_type = "filename:F",
537 .mhandler.cmd_new = qmp_marshal_input_xen_save_devices_state,
541 xen-save-devices-state
544 Save the state of all devices to file. The RAM and the block devices
545 of the VM are not saved by this command.
549 - "filename": the file to save the state of the devices to as binary
550 data. See xen-save-devices-state.txt for a description of the binary
555 -> { "execute": "xen-save-devices-state",
556 "arguments": { "filename": "/tmp/save" } }
562 .name = "xen-set-global-dirty-log",
563 .args_type = "enable:b",
564 .mhandler.cmd_new = qmp_marshal_input_xen_set_global_dirty_log,
568 xen-set-global-dirty-log
571 Enable or disable the global dirty log mode.
575 - "enable": Enable it or disable it.
579 -> { "execute": "xen-set-global-dirty-log",
580 "arguments": { "enable": true } }
587 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
588 .mhandler.cmd_new = qmp_marshal_input_migrate,
599 - "blk": block migration, full disk copy (json-bool, optional)
600 - "inc": incremental disk copy (json-bool, optional)
601 - "uri": Destination URI (json-string)
605 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
610 (1) The 'query-migrate' command should be used to check migration's progress
611 and final result (this information is provided by the 'status' member)
612 (2) All boolean arguments default to false
613 (3) The user Monitor's "detach" argument is invalid in QMP and should not
619 .name = "migrate_cancel",
621 .mhandler.cmd_new = qmp_marshal_input_migrate_cancel,
628 Cancel the current migration.
634 -> { "execute": "migrate_cancel" }
639 .name = "migrate-set-cache-size",
640 .args_type = "value:o",
641 .mhandler.cmd_new = qmp_marshal_input_migrate_set_cache_size,
645 migrate-set-cache-size
646 ---------------------
648 Set cache size to be used by XBZRLE migration, the cache size will be rounded
649 down to the nearest power of 2
653 - "value": cache size in bytes (json-int)
657 -> { "execute": "migrate-set-cache-size", "arguments": { "value": 536870912 } }
662 .name = "query-migrate-cache-size",
664 .mhandler.cmd_new = qmp_marshal_input_query_migrate_cache_size,
668 query-migrate-cache-size
669 ---------------------
671 Show cache size to be used by XBZRLE migration
673 returns a json-object with the following information:
678 -> { "execute": "query-migrate-cache-size" }
679 <- { "return": 67108864 }
684 .name = "migrate_set_speed",
685 .args_type = "value:o",
686 .mhandler.cmd_new = qmp_marshal_input_migrate_set_speed,
693 Set maximum speed for migrations.
697 - "value": maximum speed, in bytes per second (json-int)
701 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
707 .name = "migrate_set_downtime",
708 .args_type = "value:T",
709 .mhandler.cmd_new = qmp_marshal_input_migrate_set_downtime,
716 Set maximum tolerated downtime (in seconds) for migrations.
720 - "value": maximum downtime (json-number)
724 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
730 .name = "client_migrate_info",
731 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
732 .params = "protocol hostname port tls-port cert-subject",
733 .help = "send migration info to spice/vnc client",
734 .user_print = monitor_user_noop,
735 .mhandler.cmd_async = client_migrate_info,
736 .flags = MONITOR_CMD_ASYNC,
743 Set the spice/vnc connection info for the migration target. The spice/vnc
744 server will ask the spice/vnc client to automatically reconnect using the
745 new parameters (if specified) once the vm migration finished successfully.
749 - "protocol": protocol: "spice" or "vnc" (json-string)
750 - "hostname": migration target hostname (json-string)
751 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
752 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
753 - "cert-subject": server certificate subject (json-string, optional)
757 -> { "execute": "client_migrate_info",
758 "arguments": { "protocol": "spice",
759 "hostname": "virt42.lab.kraxel.org",
766 .name = "dump-guest-memory",
767 .args_type = "paging:b,protocol:s,begin:i?,end:i?",
768 .params = "-p protocol [begin] [length]",
769 .help = "dump guest memory to file",
770 .user_print = monitor_user_noop,
771 .mhandler.cmd_new = qmp_marshal_input_dump_guest_memory,
778 Dump guest memory to file. The file can be processed with crash or gdb.
782 - "paging": do paging to get guest's memory mapping (json-bool)
783 - "protocol": destination file(started with "file:") or destination file
784 descriptor (started with "fd:") (json-string)
785 - "begin": the starting physical address. It's optional, and should be specified
786 with length together (json-int)
787 - "length": the memory size, in bytes. It's optional, and should be specified
788 with begin together (json-int)
792 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
797 (1) All boolean arguments default to false
802 .name = "netdev_add",
803 .args_type = "netdev:O",
804 .mhandler.cmd_new = qmp_netdev_add,
811 Add host network device.
815 - "type": the device type, "tap", "user", ... (json-string)
816 - "id": the device's ID, must be unique (json-string)
821 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
824 Note: The supported device options are the same ones supported by the '-net'
825 command-line argument, which are listed in the '-help' output or QEMU's
831 .name = "netdev_del",
833 .mhandler.cmd_new = qmp_marshal_input_netdev_del,
840 Remove host network device.
844 - "id": the device's ID, must be unique (json-string)
848 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
855 .name = "block_resize",
856 .args_type = "device:B,size:o",
857 .mhandler.cmd_new = qmp_marshal_input_block_resize,
864 Resize a block image while a guest is running.
868 - "device": the device's ID, must be unique (json-string)
873 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
879 .name = "block-stream",
880 .args_type = "device:B,base:s?,speed:o?,on-error:s?",
881 .mhandler.cmd_new = qmp_marshal_input_block_stream,
885 .name = "block-commit",
886 .args_type = "device:B,base:s?,top:s,speed:o?",
887 .mhandler.cmd_new = qmp_marshal_input_block_commit,
891 .name = "block-job-set-speed",
892 .args_type = "device:B,speed:o",
893 .mhandler.cmd_new = qmp_marshal_input_block_job_set_speed,
897 .name = "block-job-cancel",
898 .args_type = "device:B,force:b?",
899 .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
902 .name = "block-job-pause",
903 .args_type = "device:B",
904 .mhandler.cmd_new = qmp_marshal_input_block_job_pause,
907 .name = "block-job-resume",
908 .args_type = "device:B",
909 .mhandler.cmd_new = qmp_marshal_input_block_job_resume,
912 .name = "block-job-complete",
913 .args_type = "device:B",
914 .mhandler.cmd_new = qmp_marshal_input_block_job_complete,
917 .name = "transaction",
918 .args_type = "actions:q",
919 .mhandler.cmd_new = qmp_marshal_input_transaction,
926 Atomically operate on one or more block devices. The only supported
927 operation for now is snapshotting. If there is any failure performing
928 any of the operations, all snapshots for the group are abandoned, and
929 the original disks pre-snapshot attempt are used.
931 A list of dictionaries is accepted, that contains the actions to be performed.
932 For snapshots this is the device, the file to use for the new snapshot,
933 and the format. The default format, if not specified, is qcow2.
935 Each new snapshot defaults to being created by QEMU (wiping any
936 contents if the file already exists), but it is also possible to reuse
937 an externally-created file. In the latter case, you should ensure that
938 the new image file has the same contents as the current one; QEMU cannot
939 perform any meaningful check. Typically this is achieved by using the
940 current image file as the backing file for the new image.
945 - "type": the operation to perform. The only supported
946 value is "blockdev-snapshot-sync". (json-string)
947 - "data": a dictionary. The contents depend on the value
948 of "type". When "type" is "blockdev-snapshot-sync":
949 - "device": device name to snapshot (json-string)
950 - "snapshot-file": name of new image file (json-string)
951 - "format": format of new image (json-string, optional)
952 - "mode": whether and how QEMU should create the snapshot file
953 (NewImageMode, optional, default "absolute-paths")
957 -> { "execute": "transaction",
958 "arguments": { "actions": [
959 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd0",
960 "snapshot-file": "/some/place/my-image",
961 "format": "qcow2" } },
962 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd1",
963 "snapshot-file": "/some/place/my-image2",
965 "format": "qcow2" } } ] } }
971 .name = "blockdev-snapshot-sync",
972 .args_type = "device:B,snapshot-file:s,format:s?,mode:s?",
973 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
977 blockdev-snapshot-sync
978 ----------------------
980 Synchronous snapshot of a block device. snapshot-file specifies the
981 target of the new image. If the file exists, or if it is a device, the
982 snapshot will be created in the existing file/device. If does not
983 exist, a new file will be created. format specifies the format of the
984 snapshot image, default is qcow2.
988 - "device": device name to snapshot (json-string)
989 - "snapshot-file": name of new image file (json-string)
990 - "mode": whether and how QEMU should create the snapshot file
991 (NewImageMode, optional, default "absolute-paths")
992 - "format": format of new image (json-string, optional)
996 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
998 "/some/place/my-image",
999 "format": "qcow2" } }
1005 .name = "drive-mirror",
1006 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1007 "on-source-error:s?,on-target-error:s?",
1008 .mhandler.cmd_new = qmp_marshal_input_drive_mirror,
1015 Start mirroring a block device's writes to a new destination. target
1016 specifies the target of the new image. If the file exists, or if it is
1017 a device, it will be used as the new destination for writes. If it does not
1018 exist, a new file will be created. format specifies the format of the
1019 mirror image, default is to probe if mode='existing', else the format
1024 - "device": device name to operate on (json-string)
1025 - "target": name of new image file (json-string)
1026 - "format": format of new image (json-string, optional)
1027 - "mode": how an image file should be created into the target
1028 file/device (NewImageMode, optional, default 'absolute-paths')
1029 - "speed": maximum speed of the streaming job, in bytes per second
1031 - "sync": what parts of the disk image should be copied to the destination;
1032 possibilities include "full" for all the disk, "top" for only the sectors
1033 allocated in the topmost image, or "none" to only replicate new I/O
1035 - "on-source-error": the action to take on an error on the source
1036 (BlockdevOnError, default 'report')
1037 - "on-target-error": the action to take on an error on the target
1038 (BlockdevOnError, default 'report')
1044 -> { "execute": "drive-mirror", "arguments": { "device": "ide-hd0",
1045 "target": "/some/place/my-image",
1047 "format": "qcow2" } }
1054 .args_type = "value:M",
1055 .mhandler.cmd_new = qmp_marshal_input_balloon,
1062 Request VM to change its memory allocation (in bytes).
1066 - "value": New memory allocation (json-int)
1070 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1077 .args_type = "name:s,up:b",
1078 .mhandler.cmd_new = qmp_marshal_input_set_link,
1085 Change the link status of a network adapter.
1089 - "name": network device name (json-string)
1090 - "up": status is up (json-bool)
1094 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
1101 .args_type = "fdname:s",
1102 .params = "getfd name",
1103 .help = "receive a file descriptor via SCM rights and assign it a name",
1104 .mhandler.cmd_new = qmp_marshal_input_getfd,
1111 Receive a file descriptor via SCM rights and assign it a name.
1115 - "fdname": file descriptor name (json-string)
1119 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1124 (1) If the name specified by the "fdname" argument already exists,
1125 the file descriptor assigned to it will be closed and replaced
1126 by the received file descriptor.
1127 (2) The 'closefd' command can be used to explicitly close the file
1128 descriptor when it is no longer needed.
1134 .args_type = "fdname:s",
1135 .params = "closefd name",
1136 .help = "close a file descriptor previously passed via SCM rights",
1137 .mhandler.cmd_new = qmp_marshal_input_closefd,
1144 Close a file descriptor previously passed via SCM rights.
1148 - "fdname": file descriptor name (json-string)
1152 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1159 .args_type = "fdset-id:i?,opaque:s?",
1160 .params = "add-fd fdset-id opaque",
1161 .help = "Add a file descriptor, that was passed via SCM rights, to an fd set",
1162 .mhandler.cmd_new = qmp_marshal_input_add_fd,
1169 Add a file descriptor, that was passed via SCM rights, to an fd set.
1173 - "fdset-id": The ID of the fd set to add the file descriptor to.
1174 (json-int, optional)
1175 - "opaque": A free-form string that can be used to describe the fd.
1176 (json-string, optional)
1178 Return a json-object with the following information:
1180 - "fdset-id": The ID of the fd set that the fd was added to. (json-int)
1181 - "fd": The file descriptor that was received via SCM rights and added to the
1186 -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1187 <- { "return": { "fdset-id": 1, "fd": 3 } }
1191 (1) The list of fd sets is shared by all monitor connections.
1192 (2) If "fdset-id" is not specified, a new fd set will be created.
1197 .name = "remove-fd",
1198 .args_type = "fdset-id:i,fd:i?",
1199 .params = "remove-fd fdset-id fd",
1200 .help = "Remove a file descriptor from an fd set",
1201 .mhandler.cmd_new = qmp_marshal_input_remove_fd,
1208 Remove a file descriptor from an fd set.
1212 - "fdset-id": The ID of the fd set that the file descriptor belongs to.
1214 - "fd": The file descriptor that is to be removed. (json-int, optional)
1218 -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1223 (1) The list of fd sets is shared by all monitor connections.
1224 (2) If "fd" is not specified, all file descriptors in "fdset-id" will be
1230 .name = "query-fdsets",
1232 .help = "Return information describing all fd sets",
1233 .mhandler.cmd_new = qmp_marshal_input_query_fdsets,
1240 Return information describing all fd sets.
1246 -> { "execute": "query-fdsets" }
1252 "opaque": "rdonly:/path/to/file"
1256 "opaque": "rdwr:/path/to/file"
1275 Note: The list of fd sets is shared by all monitor connections.
1280 .name = "block_passwd",
1281 .args_type = "device:B,password:s",
1282 .mhandler.cmd_new = qmp_marshal_input_block_passwd,
1289 Set the password of encrypted block devices.
1293 - "device": device name (json-string)
1294 - "password": password (json-string)
1298 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
1299 "password": "12345" } }
1305 .name = "block_set_io_throttle",
1306 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l",
1307 .mhandler.cmd_new = qmp_marshal_input_block_set_io_throttle,
1311 block_set_io_throttle
1314 Change I/O throttle limits for a block drive.
1318 - "device": device name (json-string)
1319 - "bps": total throughput limit in bytes per second(json-int)
1320 - "bps_rd": read throughput limit in bytes per second(json-int)
1321 - "bps_wr": read throughput limit in bytes per second(json-int)
1322 - "iops": total I/O operations per second(json-int)
1323 - "iops_rd": read I/O operations per second(json-int)
1324 - "iops_wr": write I/O operations per second(json-int)
1328 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
1340 .name = "set_password",
1341 .args_type = "protocol:s,password:s,connected:s?",
1342 .mhandler.cmd_new = qmp_marshal_input_set_password,
1349 Set the password for vnc/spice protocols.
1353 - "protocol": protocol name (json-string)
1354 - "password": password (json-string)
1355 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
1359 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
1360 "password": "secret" } }
1366 .name = "expire_password",
1367 .args_type = "protocol:s,time:s",
1368 .mhandler.cmd_new = qmp_marshal_input_expire_password,
1375 Set the password expire time for vnc/spice protocols.
1379 - "protocol": protocol name (json-string)
1380 - "time": [ now | never | +secs | secs ] (json-string)
1384 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
1391 .name = "add_client",
1392 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
1393 .mhandler.cmd_new = qmp_marshal_input_add_client,
1400 Add a graphics client
1404 - "protocol": protocol name (json-string)
1405 - "fdname": file descriptor name (json-string)
1406 - "skipauth": whether to skip authentication (json-bool, optional)
1407 - "tls": whether to perform TLS (json-bool, optional)
1411 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
1412 "fdname": "myclient" } }
1417 .name = "qmp_capabilities",
1420 .help = "enable QMP capabilities",
1421 .user_print = monitor_user_noop,
1422 .mhandler.cmd_new = do_qmp_capabilities,
1429 Enable QMP capabilities.
1435 -> { "execute": "qmp_capabilities" }
1438 Note: This command must be issued before issuing any other command.
1443 .name = "human-monitor-command",
1444 .args_type = "command-line:s,cpu-index:i?",
1445 .mhandler.cmd_new = qmp_marshal_input_human_monitor_command,
1449 human-monitor-command
1450 ---------------------
1452 Execute a Human Monitor command.
1456 - command-line: the command name and its arguments, just like the
1457 Human Monitor's shell (json-string)
1458 - cpu-index: select the CPU number to be used by commands which access CPU
1459 data, like 'info registers'. The Monitor selects CPU 0 if this
1460 argument is not provided (json-int, optional)
1464 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1465 <- { "return": "kvm support: enabled\r\n" }
1469 (1) The Human Monitor is NOT an stable interface, this means that command
1470 names, arguments and responses can change or be removed at ANY time.
1471 Applications that rely on long term stability guarantees should NOT
1476 o This command is stateless, this means that commands that depend
1477 on state information (such as getfd) might not work
1479 o Commands that prompt the user for data (eg. 'cont' when the block
1480 device is encrypted) don't currently work
1485 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1486 HXCOMM this! We will possibly move query commands definitions inside those
1487 HXCOMM sections, just like regular commands.
1497 Return a json-object with the following information:
1499 - "qemu": A json-object containing three integer values:
1500 - "major": QEMU's major version (json-int)
1501 - "minor": QEMU's minor version (json-int)
1502 - "micro": QEMU's micro version (json-int)
1503 - "package": package's version (json-string)
1507 -> { "execute": "query-version" }
1522 .name = "query-version",
1524 .mhandler.cmd_new = qmp_marshal_input_query_version,
1531 List QMP available commands.
1533 Each command is represented by a json-object, the returned value is a json-array
1536 Each json-object contain:
1538 - "name": command's name (json-string)
1542 -> { "execute": "query-commands" }
1546 "name":"query-balloon"
1549 "name":"system_powerdown"
1554 Note: This example has been shortened as the real response is too long.
1559 .name = "query-commands",
1561 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1568 List QMP available events.
1570 Each event is represented by a json-object, the returned value is a json-array
1573 Each json-object contains:
1575 - "name": event's name (json-string)
1579 -> { "execute": "query-events" }
1591 Note: This example has been shortened as the real response is too long.
1596 .name = "query-events",
1598 .mhandler.cmd_new = qmp_marshal_input_query_events,
1605 Each device is represented by a json-object. The returned value is a json-array
1608 Each json-object contain the following:
1610 - "label": device's label (json-string)
1611 - "filename": device's file (json-string)
1615 -> { "execute": "query-chardev" }
1632 .name = "query-chardev",
1634 .mhandler.cmd_new = qmp_marshal_input_query_chardev,
1641 Show the block devices.
1643 Each block device information is stored in a json-object and the returned value
1644 is a json-array of all devices.
1646 Each json-object contain the following:
1648 - "device": device name (json-string)
1649 - "type": device type (json-string)
1650 - deprecated, retained for backward compatibility
1651 - Possible values: "unknown"
1652 - "removable": true if the device is removable, false otherwise (json-bool)
1653 - "locked": true if the device is locked, false otherwise (json-bool)
1654 - "tray-open": only present if removable, true if the device has a tray,
1655 and it is open (json-bool)
1656 - "inserted": only present if the device is inserted, it is a json-object
1657 containing the following:
1658 - "file": device file name (json-string)
1659 - "ro": true if read-only, false otherwise (json-bool)
1660 - "drv": driver format name (json-string)
1661 - Possible values: "blkdebug", "bochs", "cloop", "cow", "dmg",
1662 "file", "file", "ftp", "ftps", "host_cdrom",
1663 "host_device", "host_floppy", "http", "https",
1664 "nbd", "parallels", "qcow", "qcow2", "raw",
1665 "tftp", "vdi", "vmdk", "vpc", "vvfat"
1666 - "backing_file": backing file name (json-string, optional)
1667 - "backing_file_depth": number of files in the backing file chain (json-int)
1668 - "encrypted": true if encrypted, false otherwise (json-bool)
1669 - "bps": limit total bytes per second (json-int)
1670 - "bps_rd": limit read bytes per second (json-int)
1671 - "bps_wr": limit write bytes per second (json-int)
1672 - "iops": limit total I/O operations per second (json-int)
1673 - "iops_rd": limit read operations per second (json-int)
1674 - "iops_wr": limit write operations per second (json-int)
1676 - "io-status": I/O operation status, only present if the device supports it
1677 and the VM is configured to stop on errors. It's always reset
1678 to "ok" when the "cont" command is issued (json_string, optional)
1679 - Possible values: "ok", "failed", "nospace"
1683 -> { "execute": "query-block" }
1688 "device":"ide0-hd0",
1695 "file":"disks/test.img",
1696 "backing_file_depth":0,
1708 "device":"ide1-cd0",
1731 .name = "query-block",
1733 .mhandler.cmd_new = qmp_marshal_input_query_block,
1740 Show block device statistics.
1742 Each device statistic information is stored in a json-object and the returned
1743 value is a json-array of all devices.
1745 Each json-object contain the following:
1747 - "device": device name (json-string)
1748 - "stats": A json-object with the statistics information, it contains:
1749 - "rd_bytes": bytes read (json-int)
1750 - "wr_bytes": bytes written (json-int)
1751 - "rd_operations": read operations (json-int)
1752 - "wr_operations": write operations (json-int)
1753 - "flush_operations": cache flush operations (json-int)
1754 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
1755 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
1756 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
1757 - "wr_highest_offset": Highest offset of a sector written since the
1758 BlockDriverState has been opened (json-int)
1759 - "parent": Contains recursively the statistics of the underlying
1760 protocol (e.g. the host file for a qcow2 image). If there is
1761 no underlying protocol, this field is omitted
1762 (json-object, optional)
1766 -> { "execute": "query-blockstats" }
1770 "device":"ide0-hd0",
1773 "wr_highest_offset":3686448128,
1775 "wr_operations":751,
1776 "rd_bytes":122567168,
1777 "rd_operations":36772
1778 "wr_total_times_ns":313253456
1779 "rd_total_times_ns":3465673657
1780 "flush_total_times_ns":49653
1781 "flush_operations":61,
1785 "wr_highest_offset":2821110784,
1787 "wr_operations":692,
1788 "rd_bytes":122739200,
1789 "rd_operations":36604
1790 "flush_operations":51,
1791 "wr_total_times_ns":313253456
1792 "rd_total_times_ns":3465673657
1793 "flush_total_times_ns":49653
1797 "device":"ide1-cd0",
1799 "wr_highest_offset":0,
1804 "flush_operations":0,
1805 "wr_total_times_ns":0
1806 "rd_total_times_ns":0
1807 "flush_total_times_ns":0
1813 "wr_highest_offset":0,
1818 "flush_operations":0,
1819 "wr_total_times_ns":0
1820 "rd_total_times_ns":0
1821 "flush_total_times_ns":0
1827 "wr_highest_offset":0,
1832 "flush_operations":0,
1833 "wr_total_times_ns":0
1834 "rd_total_times_ns":0
1835 "flush_total_times_ns":0
1844 .name = "query-blockstats",
1846 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
1853 Show CPU information.
1855 Return a json-array. Each CPU is represented by a json-object, which contains:
1857 - "CPU": CPU index (json-int)
1858 - "current": true if this is the current CPU, false otherwise (json-bool)
1859 - "halted": true if the cpu is halted, false otherwise (json-bool)
1860 - Current program counter. The key's name depends on the architecture:
1861 "pc": i386/x86_64 (json-int)
1862 "nip": PPC (json-int)
1863 "pc" and "npc": sparc (json-int)
1864 "PC": mips (json-int)
1865 - "thread_id": ID of the underlying host thread (json-int)
1869 -> { "execute": "query-cpus" }
1892 .name = "query-cpus",
1894 .mhandler.cmd_new = qmp_marshal_input_query_cpus,
1901 PCI buses and devices information.
1903 The returned value is a json-array of all buses. Each bus is represented by
1904 a json-object, which has a key with a json-array of all PCI devices attached
1905 to it. Each device is represented by a json-object.
1907 The bus json-object contains the following:
1909 - "bus": bus number (json-int)
1910 - "devices": a json-array of json-objects, each json-object represents a
1913 The PCI device json-object contains the following:
1915 - "bus": identical to the parent's bus number (json-int)
1916 - "slot": slot number (json-int)
1917 - "function": function number (json-int)
1918 - "class_info": a json-object containing:
1919 - "desc": device class description (json-string, optional)
1920 - "class": device class number (json-int)
1921 - "id": a json-object containing:
1922 - "device": device ID (json-int)
1923 - "vendor": vendor ID (json-int)
1924 - "irq": device's IRQ if assigned (json-int, optional)
1925 - "qdev_id": qdev id string (json-string)
1926 - "pci_bridge": It's a json-object, only present if this device is a
1927 PCI bridge, contains:
1928 - "bus": bus number (json-int)
1929 - "secondary": secondary bus number (json-int)
1930 - "subordinate": subordinate bus number (json-int)
1931 - "io_range": I/O memory range information, a json-object with the
1933 - "base": base address, in bytes (json-int)
1934 - "limit": limit address, in bytes (json-int)
1935 - "memory_range": memory range information, a json-object with the
1937 - "base": base address, in bytes (json-int)
1938 - "limit": limit address, in bytes (json-int)
1939 - "prefetchable_range": Prefetchable memory range information, a
1940 json-object with the following members:
1941 - "base": base address, in bytes (json-int)
1942 - "limit": limit address, in bytes (json-int)
1943 - "devices": a json-array of PCI devices if there's any attached, each
1944 each element is represented by a json-object, which contains
1945 the same members of the 'PCI device json-object' described
1947 - "regions": a json-array of json-objects, each json-object represents a
1948 memory region of this device
1950 The memory range json-object contains the following:
1952 - "base": base memory address (json-int)
1953 - "limit": limit value (json-int)
1955 The region json-object can be an I/O region or a memory region, an I/O region
1956 json-object contains the following:
1958 - "type": "io" (json-string, fixed)
1959 - "bar": BAR number (json-int)
1960 - "address": memory address (json-int)
1961 - "size": memory size (json-int)
1963 A memory region json-object contains the following:
1965 - "type": "memory" (json-string, fixed)
1966 - "bar": BAR number (json-int)
1967 - "address": memory address (json-int)
1968 - "size": memory size (json-int)
1969 - "mem_type_64": true or false (json-bool)
1970 - "prefetch": true or false (json-bool)
1974 -> { "execute": "query-pci" }
1986 "desc":"Host bridge"
2020 "desc":"IDE controller"
2042 "desc":"VGA controller"
2052 "mem_type_64":false,
2055 "address":4026531840,
2060 "mem_type_64":false,
2063 "address":4060086272,
2068 "mem_type_64":false,
2083 "desc":"RAM controller"
2104 Note: This example has been shortened as the real response is too long.
2109 .name = "query-pci",
2111 .mhandler.cmd_new = qmp_marshal_input_query_pci,
2118 Show KVM information.
2120 Return a json-object with the following information:
2122 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
2123 - "present": true if QEMU has KVM support, false otherwise (json-bool)
2127 -> { "execute": "query-kvm" }
2128 <- { "return": { "enabled": true, "present": true } }
2133 .name = "query-kvm",
2135 .mhandler.cmd_new = qmp_marshal_input_query_kvm,
2142 Return a json-object with the following information:
2144 - "running": true if the VM is running, or false if it is paused (json-bool)
2145 - "singlestep": true if the VM is in single step mode,
2146 false otherwise (json-bool)
2147 - "status": one of the following values (json-string)
2148 "debug" - QEMU is running on a debugger
2149 "inmigrate" - guest is paused waiting for an incoming migration
2150 "internal-error" - An internal error that prevents further guest
2151 execution has occurred
2152 "io-error" - the last IOP has failed and the device is configured
2153 to pause on I/O errors
2154 "paused" - guest has been paused via the 'stop' command
2155 "postmigrate" - guest is paused following a successful 'migrate'
2156 "prelaunch" - QEMU was started with -S and guest has not started
2157 "finish-migrate" - guest is paused to finish the migration process
2158 "restore-vm" - guest is paused to restore VM state
2159 "running" - guest is actively running
2160 "save-vm" - guest is paused to save the VM state
2161 "shutdown" - guest is shut down (and -no-shutdown is in use)
2162 "watchdog" - the watchdog action is configured to pause and
2167 -> { "execute": "query-status" }
2168 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
2173 .name = "query-status",
2175 .mhandler.cmd_new = qmp_marshal_input_query_status,
2182 Show VM mice information.
2184 Each mouse is represented by a json-object, the returned value is a json-array
2187 The mouse json-object contains the following:
2189 - "name": mouse's name (json-string)
2190 - "index": mouse's index (json-int)
2191 - "current": true if this mouse is receiving events, false otherwise (json-bool)
2192 - "absolute": true if the mouse generates absolute input events (json-bool)
2196 -> { "execute": "query-mice" }
2200 "name":"QEMU Microsoft Mouse",
2206 "name":"QEMU PS/2 Mouse",
2217 .name = "query-mice",
2219 .mhandler.cmd_new = qmp_marshal_input_query_mice,
2226 Show VNC server information.
2228 Return a json-object with server information. Connected clients are returned
2229 as a json-array of json-objects.
2231 The main json-object contains the following:
2233 - "enabled": true or false (json-bool)
2234 - "host": server's IP address (json-string)
2235 - "family": address family (json-string)
2236 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2237 - "service": server's port number (json-string)
2238 - "auth": authentication method (json-string)
2239 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
2240 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
2241 "vencrypt+plain", "vencrypt+tls+none",
2242 "vencrypt+tls+plain", "vencrypt+tls+sasl",
2243 "vencrypt+tls+vnc", "vencrypt+x509+none",
2244 "vencrypt+x509+plain", "vencrypt+x509+sasl",
2245 "vencrypt+x509+vnc", "vnc"
2246 - "clients": a json-array of all connected clients
2248 Clients are described by a json-object, each one contain the following:
2250 - "host": client's IP address (json-string)
2251 - "family": address family (json-string)
2252 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2253 - "service": client's port number (json-string)
2254 - "x509_dname": TLS dname (json-string, optional)
2255 - "sasl_username": SASL username (json-string, optional)
2259 -> { "execute": "query-vnc" }
2280 .name = "query-vnc",
2282 .mhandler.cmd_new = qmp_marshal_input_query_vnc,
2289 Show SPICE server information.
2291 Return a json-object with server information. Connected clients are returned
2292 as a json-array of json-objects.
2294 The main json-object contains the following:
2296 - "enabled": true or false (json-bool)
2297 - "host": server's IP address (json-string)
2298 - "port": server's port number (json-int, optional)
2299 - "tls-port": server's port number (json-int, optional)
2300 - "auth": authentication method (json-string)
2301 - Possible values: "none", "spice"
2302 - "channels": a json-array of all active channels clients
2304 Channels are described by a json-object, each one contain the following:
2306 - "host": client's IP address (json-string)
2307 - "family": address family (json-string)
2308 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2309 - "port": client's port number (json-string)
2310 - "connection-id": spice connection id. All channels with the same id
2311 belong to the same spice session (json-int)
2312 - "channel-type": channel type. "1" is the main control channel, filter for
2313 this one if you want track spice sessions only (json-int)
2314 - "channel-id": channel id. Usually "0", might be different needed when
2315 multiple channels of the same type exist, such as multiple
2316 display channels in a multihead setup (json-int)
2317 - "tls": whevener the channel is encrypted (json-bool)
2321 -> { "execute": "query-spice" }
2334 "connection-id": 1804289383,
2335 "host": "127.0.0.1",
2343 "connection-id": 1804289383,
2344 "host": "127.0.0.1",
2348 [ ... more channels follow ... ]
2355 #if defined(CONFIG_SPICE)
2357 .name = "query-spice",
2359 .mhandler.cmd_new = qmp_marshal_input_query_spice,
2369 Return a json-object with the following information:
2371 - "name": VM's name (json-string, optional)
2375 -> { "execute": "query-name" }
2376 <- { "return": { "name": "qemu-name" } }
2381 .name = "query-name",
2383 .mhandler.cmd_new = qmp_marshal_input_query_name,
2392 Return a json-object with the following information:
2394 - "UUID": Universally Unique Identifier (json-string)
2398 -> { "execute": "query-uuid" }
2399 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
2404 .name = "query-uuid",
2406 .mhandler.cmd_new = qmp_marshal_input_query_uuid,
2415 Return a json-object. If migration is active there will be another json-object
2416 with RAM migration status and if block migration is active another one with
2417 block migration status.
2419 The main json-object contains the following:
2421 - "status": migration status (json-string)
2422 - Possible values: "active", "completed", "failed", "cancelled"
2423 - "total-time": total amount of ms since migration started. If
2424 migration has ended, it returns the total migration
2426 - "downtime": only present when migration has finished correctly
2427 total amount in ms for downtime that happened (json-int)
2428 - "expected-downtime": only present while migration is active
2429 total amount in ms for downtime that was calculated on
2430 the last bitmap round (json-int)
2431 - "ram": only present if "status" is "active", it is a json-object with the
2432 following RAM information (in bytes):
2433 - "transferred": amount transferred (json-int)
2434 - "remaining": amount remaining (json-int)
2435 - "total": total (json-int)
2436 - "duplicate": number of duplicated pages (json-int)
2437 - "normal" : number of normal pages transferred (json-int)
2438 - "normal-bytes" : number of normal bytes transferred (json-int)
2439 - "disk": only present if "status" is "active" and it is a block migration,
2440 it is a json-object with the following disk information (in bytes):
2441 - "transferred": amount transferred (json-int)
2442 - "remaining": amount remaining (json-int)
2443 - "total": total (json-int)
2444 - "xbzrle-cache": only present if XBZRLE is active.
2445 It is a json-object with the following XBZRLE information:
2446 - "cache-size": XBZRLE cache size
2447 - "bytes": total XBZRLE bytes transferred
2448 - "pages": number of XBZRLE compressed pages
2449 - "cache-miss": number of cache misses
2450 - "overflow": number of XBZRLE overflows
2453 1. Before the first migration
2455 -> { "execute": "query-migrate" }
2458 2. Migration is done and has succeeded
2460 -> { "execute": "query-migrate" }
2462 "status": "completed",
2471 "normal-bytes":123456
2476 3. Migration is done and has failed
2478 -> { "execute": "query-migrate" }
2479 <- { "return": { "status": "failed" } }
2481 4. Migration is being performed and is not a block migration:
2483 -> { "execute": "query-migrate" }
2492 "expected-downtime":12345,
2495 "normal-bytes":123456
2500 5. Migration is being performed and is a block migration:
2502 -> { "execute": "query-migrate" }
2508 "remaining":1053304,
2511 "expected-downtime":12345,
2514 "normal-bytes":123456
2518 "remaining":20880384,
2524 6. Migration is being performed and XBZRLE is active:
2526 -> { "execute": "query-migrate" }
2530 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
2533 "remaining":1053304,
2536 "expected-downtime":12345,
2539 "normal-bytes":3412992
2542 "cache-size":67108864,
2554 .name = "query-migrate",
2556 .mhandler.cmd_new = qmp_marshal_input_query_migrate,
2560 migrate-set-capabilities
2563 Enable/Disable migration capabilities
2565 - "xbzrle": xbzrle support
2571 -> { "execute": "migrate-set-capabilities" , "arguments":
2572 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
2577 .name = "migrate-set-capabilities",
2578 .args_type = "capabilities:O",
2579 .params = "capability:s,state:b",
2580 .mhandler.cmd_new = qmp_marshal_input_migrate_set_capabilities,
2583 query-migrate-capabilities
2586 Query current migration capabilities
2588 - "capabilities": migration capabilities state
2589 - "xbzrle" : XBZRLE state (json-bool)
2595 -> { "execute": "query-migrate-capabilities" }
2597 "capabilities" : [ { "capability" : "xbzrle", "state" : false } ]
2603 .name = "query-migrate-capabilities",
2605 .mhandler.cmd_new = qmp_marshal_input_query_migrate_capabilities,
2612 Show balloon information.
2614 Make an asynchronous request for balloon info. When the request completes a
2615 json-object will be returned containing the following data:
2617 - "actual": current balloon value in bytes (json-int)
2621 -> { "execute": "query-balloon" }
2624 "actual":1073741824,
2631 .name = "query-balloon",
2633 .mhandler.cmd_new = qmp_marshal_input_query_balloon,
2637 .name = "query-block-jobs",
2639 .mhandler.cmd_new = qmp_marshal_input_query_block_jobs,
2644 .args_type = "path:s",
2645 .mhandler.cmd_new = qmp_marshal_input_qom_list,
2650 .args_type = "path:s,property:s,value:q",
2651 .mhandler.cmd_new = qmp_qom_set,
2656 .args_type = "path:s,property:s",
2657 .mhandler.cmd_new = qmp_qom_get,
2661 .name = "nbd-server-start",
2662 .args_type = "addr:q",
2663 .mhandler.cmd_new = qmp_marshal_input_nbd_server_start,
2666 .name = "nbd-server-add",
2667 .args_type = "device:B,writable:b?",
2668 .mhandler.cmd_new = qmp_marshal_input_nbd_server_add,
2671 .name = "nbd-server-stop",
2673 .mhandler.cmd_new = qmp_marshal_input_nbd_server_stop,
2677 .name = "change-vnc-password",
2678 .args_type = "password:s",
2679 .mhandler.cmd_new = qmp_marshal_input_change_vnc_password,
2682 .name = "qom-list-types",
2683 .args_type = "implements:s?,abstract:b?",
2684 .mhandler.cmd_new = qmp_marshal_input_qom_list_types,
2688 .name = "device-list-properties",
2689 .args_type = "typename:s",
2690 .mhandler.cmd_new = qmp_marshal_input_device_list_properties,
2694 .name = "query-machines",
2696 .mhandler.cmd_new = qmp_marshal_input_query_machines,
2700 .name = "query-cpu-definitions",
2702 .mhandler.cmd_new = qmp_marshal_input_query_cpu_definitions,
2706 .name = "query-target",
2708 .mhandler.cmd_new = qmp_marshal_input_query_target,
2712 .name = "chardev-add",
2713 .args_type = "id:s,backend:q",
2714 .mhandler.cmd_new = qmp_marshal_input_chardev_add,
2725 - "id": the chardev's ID, must be unique (json-string)
2726 - "backend": chardev backend type + parameters
2730 -> { "execute" : "chardev-add",
2731 "arguments" : { "id" : "foo",
2732 "backend" : { "type" : "null", "data" : {} } } }
2735 -> { "execute" : "chardev-add",
2736 "arguments" : { "id" : "bar",
2737 "backend" : { "type" : "file",
2738 "data" : { "out" : "/tmp/bar.log" } } } }
2741 -> { "execute" : "chardev-add",
2742 "arguments" : { "id" : "baz",
2743 "backend" : { "type" : "pty", "data" : {} } } }
2744 <- { "return": { "pty" : "/dev/pty/42" } }
2749 .name = "chardev-remove",
2750 .args_type = "id:s",
2751 .mhandler.cmd_new = qmp_marshal_input_chardev_remove,
2763 - "id": the chardev's ID, must exist and not be in use (json-string)
2767 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }