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 .params = "[-f] device",
88 .help = "eject a removable medium (use -f to force it)",
89 .user_print = monitor_user_noop,
90 .mhandler.cmd_new = do_eject,
97 Eject a removable medium.
101 - force: force ejection (json-bool, optional)
102 - device: device name (json-string)
106 -> { "execute": "eject", "arguments": { "device": "ide1-cd0" } }
109 Note: The "force" argument defaults to false.
115 .args_type = "device:B,target:F,arg:s?",
116 .params = "device filename [format]",
117 .help = "change a removable medium, optional format",
118 .user_print = monitor_user_noop,
119 .mhandler.cmd_new = do_change,
126 Change a removable medium or VNC configuration.
130 - "device": device name (json-string)
131 - "target": filename or item (json-string)
132 - "arg": additional argument (json-string, optional)
136 1. Change a removable medium
138 -> { "execute": "change",
139 "arguments": { "device": "ide1-cd0",
140 "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } }
143 2. Change VNC password
145 -> { "execute": "change",
146 "arguments": { "device": "vnc", "target": "password",
153 .name = "screendump",
154 .args_type = "filename:F",
155 .params = "filename",
156 .help = "save screen into PPM image 'filename'",
157 .user_print = monitor_user_noop,
158 .mhandler.cmd_new = do_screen_dump,
165 Save screen into PPM image.
169 - "filename": file path (json-string)
173 -> { "execute": "screendump", "arguments": { "filename": "/tmp/image" } }
181 .mhandler.cmd_new = qmp_marshal_input_stop,
194 -> { "execute": "stop" }
203 .help = "resume emulation",
204 .user_print = monitor_user_noop,
205 .mhandler.cmd_new = do_cont,
218 -> { "execute": "cont" }
224 .name = "system_reset",
226 .mhandler.cmd_new = qmp_marshal_input_system_reset,
239 -> { "execute": "system_reset" }
245 .name = "system_powerdown",
247 .mhandler.cmd_new = qmp_marshal_input_system_powerdown,
254 Send system power down event.
260 -> { "execute": "system_powerdown" }
266 .name = "device_add",
267 .args_type = "device:O",
268 .params = "driver[,prop=value][,...]",
269 .help = "add device, like -device on the command line",
270 .user_print = monitor_user_noop,
271 .mhandler.cmd_new = do_device_add,
282 - "driver": the name of the new device's driver (json-string)
283 - "bus": the device's parent bus (device tree path, json-string, optional)
284 - "id": the device's ID, must be unique (json-string)
289 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
294 (1) For detailed information about this command, please refer to the
295 'docs/qdev-device-use.txt' file.
297 (2) It's possible to list device properties by running QEMU with the
298 "-device DEVICE,\?" command-line argument, where DEVICE is the device's name
303 .name = "device_del",
306 .help = "remove device",
307 .user_print = monitor_user_noop,
308 .mhandler.cmd_new = do_device_del,
319 - "id": the device's ID (json-string)
323 -> { "execute": "device_del", "arguments": { "id": "net1" } }
330 .args_type = "index:i",
331 .mhandler.cmd_new = qmp_marshal_input_cpu,
342 - "index": the CPU's index (json-int)
346 -> { "execute": "cpu", "arguments": { "index": 0 } }
349 Note: CPUs' indexes are obtained with the 'query-cpus' command.
355 .args_type = "val:l,size:i,filename:s,cpu:i?",
356 .mhandler.cmd_new = qmp_marshal_input_memsave,
363 Save to disk virtual memory dump starting at 'val' of size 'size'.
367 - "val": the starting address (json-int)
368 - "size": the memory size, in bytes (json-int)
369 - "filename": file path (json-string)
370 - "cpu": virtual CPU index (json-int, optional)
374 -> { "execute": "memsave",
375 "arguments": { "val": 10,
377 "filename": "/tmp/virtual-mem-dump" } }
384 .args_type = "val:l,size:i,filename:s",
385 .mhandler.cmd_new = qmp_marshal_input_pmemsave,
392 Save to disk physical memory dump starting at 'val' of size 'size'.
396 - "val": the starting address (json-int)
397 - "size": the memory size, in bytes (json-int)
398 - "filename": file path (json-string)
402 -> { "execute": "pmemsave",
403 "arguments": { "val": 10,
405 "filename": "/tmp/physical-mem-dump" } }
411 .name = "inject-nmi",
415 .user_print = monitor_user_noop,
416 .mhandler.cmd_new = do_inject_nmi,
423 Inject an NMI on guest's CPUs.
429 -> { "execute": "inject-nmi" }
432 Note: inject-nmi is only supported for x86 guest currently, it will
433 returns "Unsupported" error for non-x86 guest.
439 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
440 .params = "[-d] [-b] [-i] uri",
441 .help = "migrate to URI (using -d to not wait for completion)"
442 "\n\t\t\t -b for migration without shared storage with"
443 " full copy of disk\n\t\t\t -i for migration without "
444 "shared storage with incremental copy of disk "
445 "(base image shared between src and destination)",
446 .user_print = monitor_user_noop,
447 .mhandler.cmd_new = do_migrate,
458 - "blk": block migration, full disk copy (json-bool, optional)
459 - "inc": incremental disk copy (json-bool, optional)
460 - "uri": Destination URI (json-string)
464 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
469 (1) The 'query-migrate' command should be used to check migration's progress
470 and final result (this information is provided by the 'status' member)
471 (2) All boolean arguments default to false
472 (3) The user Monitor's "detach" argument is invalid in QMP and should not
478 .name = "migrate_cancel",
481 .help = "cancel the current VM migration",
482 .user_print = monitor_user_noop,
483 .mhandler.cmd_new = do_migrate_cancel,
490 Cancel the current migration.
496 -> { "execute": "migrate_cancel" }
502 .name = "migrate_set_speed",
503 .args_type = "value:o",
505 .help = "set maximum speed (in bytes) for migrations",
506 .user_print = monitor_user_noop,
507 .mhandler.cmd_new = do_migrate_set_speed,
514 Set maximum speed for migrations.
518 - "value": maximum speed, in bytes per second (json-int)
522 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
528 .name = "migrate_set_downtime",
529 .args_type = "value:T",
531 .help = "set maximum tolerated downtime (in seconds) for migrations",
532 .user_print = monitor_user_noop,
533 .mhandler.cmd_new = do_migrate_set_downtime,
540 Set maximum tolerated downtime (in seconds) for migrations.
544 - "value": maximum downtime (json-number)
548 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
554 .name = "client_migrate_info",
555 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
556 .params = "protocol hostname port tls-port cert-subject",
557 .help = "send migration info to spice/vnc client",
558 .user_print = monitor_user_noop,
559 .mhandler.cmd_async = client_migrate_info,
560 .flags = MONITOR_CMD_ASYNC,
567 Set the spice/vnc connection info for the migration target. The spice/vnc
568 server will ask the spice/vnc client to automatically reconnect using the
569 new parameters (if specified) once the vm migration finished successfully.
573 - "protocol": protocol: "spice" or "vnc" (json-string)
574 - "hostname": migration target hostname (json-string)
575 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
576 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
577 - "cert-subject": server certificate subject (json-string, optional)
581 -> { "execute": "client_migrate_info",
582 "arguments": { "protocol": "spice",
583 "hostname": "virt42.lab.kraxel.org",
590 .name = "netdev_add",
591 .args_type = "netdev:O",
592 .params = "[user|tap|socket],id=str[,prop=value][,...]",
593 .help = "add host network device",
594 .user_print = monitor_user_noop,
595 .mhandler.cmd_new = do_netdev_add,
602 Add host network device.
606 - "type": the device type, "tap", "user", ... (json-string)
607 - "id": the device's ID, must be unique (json-string)
612 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
615 Note: The supported device options are the same ones supported by the '-net'
616 command-line argument, which are listed in the '-help' output or QEMU's
622 .name = "netdev_del",
625 .help = "remove host network device",
626 .user_print = monitor_user_noop,
627 .mhandler.cmd_new = do_netdev_del,
634 Remove host network device.
638 - "id": the device's ID, must be unique (json-string)
642 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
649 .name = "block_resize",
650 .args_type = "device:B,size:o",
651 .params = "device size",
652 .help = "resize a block image",
653 .user_print = monitor_user_noop,
654 .mhandler.cmd_new = do_block_resize,
661 Resize a block image while a guest is running.
665 - "device": the device's ID, must be unique (json-string)
670 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
676 .name = "blockdev-snapshot-sync",
677 .args_type = "device:B,snapshot-file:s?,format:s?",
678 .params = "device [new-image-file] [format]",
679 .user_print = monitor_user_noop,
680 .mhandler.cmd_new = do_snapshot_blkdev,
684 blockdev-snapshot-sync
685 ----------------------
687 Synchronous snapshot of a block device. snapshot-file specifies the
688 target of the new image. If the file exists, or if it is a device, the
689 snapshot will be created in the existing file/device. If does not
690 exist, a new file will be created. format specifies the format of the
691 snapshot image, default is qcow2.
695 - "device": device name to snapshot (json-string)
696 - "snapshot-file": name of new image file (json-string)
697 - "format": format of new image (json-string, optional)
701 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
703 "/some/place/my-image",
704 "format": "qcow2" } }
711 .args_type = "value:M",
713 .help = "request VM to change its memory allocation (in MB)",
714 .user_print = monitor_user_noop,
715 .mhandler.cmd_async = do_balloon,
716 .flags = MONITOR_CMD_ASYNC,
723 Request VM to change its memory allocation (in bytes).
727 - "value": New memory allocation (json-int)
731 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
738 .args_type = "name:s,up:b",
739 .params = "name on|off",
740 .help = "change the link status of a network adapter",
741 .user_print = monitor_user_noop,
742 .mhandler.cmd_new = do_set_link,
749 Change the link status of a network adapter.
753 - "name": network device name (json-string)
754 - "up": status is up (json-bool)
758 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
765 .args_type = "fdname:s",
766 .params = "getfd name",
767 .help = "receive a file descriptor via SCM rights and assign it a name",
768 .user_print = monitor_user_noop,
769 .mhandler.cmd_new = do_getfd,
776 Receive a file descriptor via SCM rights and assign it a name.
780 - "fdname": file descriptor name (json-string)
784 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
791 .args_type = "fdname:s",
792 .params = "closefd name",
793 .help = "close a file descriptor previously passed via SCM rights",
794 .user_print = monitor_user_noop,
795 .mhandler.cmd_new = do_closefd,
802 Close a file descriptor previously passed via SCM rights.
806 - "fdname": file descriptor name (json-string)
810 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
816 .name = "block_passwd",
817 .args_type = "device:B,password:s",
818 .params = "block_passwd device password",
819 .help = "set the password of encrypted block devices",
820 .user_print = monitor_user_noop,
821 .mhandler.cmd_new = do_block_set_passwd,
828 Set the password of encrypted block devices.
832 - "device": device name (json-string)
833 - "password": password (json-string)
837 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
838 "password": "12345" } }
844 .name = "block_set_io_throttle",
845 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l",
846 .params = "device bps bps_rd bps_wr iops iops_rd iops_wr",
847 .help = "change I/O throttle limits for a block drive",
848 .user_print = monitor_user_noop,
849 .mhandler.cmd_new = do_block_set_io_throttle,
853 block_set_io_throttle
856 Change I/O throttle limits for a block drive.
860 - "device": device name (json-string)
861 - "bps": total throughput limit in bytes per second(json-int)
862 - "bps_rd": read throughput limit in bytes per second(json-int)
863 - "bps_wr": read throughput limit in bytes per second(json-int)
864 - "iops": total I/O operations per second(json-int)
865 - "iops_rd": read I/O operations per second(json-int)
866 - "iops_wr": write I/O operations per second(json-int)
870 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
882 .name = "set_password",
883 .args_type = "protocol:s,password:s,connected:s?",
884 .params = "protocol password action-if-connected",
885 .help = "set spice/vnc password",
886 .user_print = monitor_user_noop,
887 .mhandler.cmd_new = set_password,
894 Set the password for vnc/spice protocols.
898 - "protocol": protocol name (json-string)
899 - "password": password (json-string)
900 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
904 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
905 "password": "secret" } }
911 .name = "expire_password",
912 .args_type = "protocol:s,time:s",
913 .params = "protocol time",
914 .help = "set spice/vnc password expire-time",
915 .user_print = monitor_user_noop,
916 .mhandler.cmd_new = expire_password,
923 Set the password expire time for vnc/spice protocols.
927 - "protocol": protocol name (json-string)
928 - "time": [ now | never | +secs | secs ] (json-string)
932 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
939 .name = "add_client",
940 .args_type = "protocol:s,fdname:s,skipauth:b?",
941 .params = "protocol fdname skipauth",
942 .help = "add a graphics client",
943 .user_print = monitor_user_noop,
944 .mhandler.cmd_new = add_graphics_client,
951 Add a graphics client
955 - "protocol": protocol name (json-string)
956 - "fdname": file descriptor name (json-string)
960 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
961 "fdname": "myclient" } }
966 .name = "qmp_capabilities",
969 .help = "enable QMP capabilities",
970 .user_print = monitor_user_noop,
971 .mhandler.cmd_new = do_qmp_capabilities,
978 Enable QMP capabilities.
984 -> { "execute": "qmp_capabilities" }
987 Note: This command must be issued before issuing any other command.
992 .name = "human-monitor-command",
993 .args_type = "command-line:s,cpu-index:i?",
996 .user_print = monitor_user_noop,
997 .mhandler.cmd_new = do_hmp_passthrough,
1001 human-monitor-command
1002 ---------------------
1004 Execute a Human Monitor command.
1008 - command-line: the command name and its arguments, just like the
1009 Human Monitor's shell (json-string)
1010 - cpu-index: select the CPU number to be used by commands which access CPU
1011 data, like 'info registers'. The Monitor selects CPU 0 if this
1012 argument is not provided (json-int, optional)
1016 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1017 <- { "return": "kvm support: enabled\r\n" }
1021 (1) The Human Monitor is NOT an stable interface, this means that command
1022 names, arguments and responses can change or be removed at ANY time.
1023 Applications that rely on long term stability guarantees should NOT
1028 o This command is stateless, this means that commands that depend
1029 on state information (such as getfd) might not work
1031 o Commands that prompt the user for data (eg. 'cont' when the block
1032 device is encrypted) don't currently work
1037 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1038 HXCOMM this! We will possibly move query commands definitions inside those
1039 HXCOMM sections, just like regular commands.
1049 Return a json-object with the following information:
1051 - "qemu": A json-object containing three integer values:
1052 - "major": QEMU's major version (json-int)
1053 - "minor": QEMU's minor version (json-int)
1054 - "micro": QEMU's micro version (json-int)
1055 - "package": package's version (json-string)
1059 -> { "execute": "query-version" }
1074 .name = "query-version",
1076 .mhandler.cmd_new = qmp_marshal_input_query_version,
1083 List QMP available commands.
1085 Each command is represented by a json-object, the returned value is a json-array
1088 Each json-object contain:
1090 - "name": command's name (json-string)
1094 -> { "execute": "query-commands" }
1098 "name":"query-balloon"
1101 "name":"system_powerdown"
1106 Note: This example has been shortened as the real response is too long.
1111 .name = "query-commands",
1113 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1120 Each device is represented by a json-object. The returned value is a json-array
1123 Each json-object contain the following:
1125 - "label": device's label (json-string)
1126 - "filename": device's file (json-string)
1130 -> { "execute": "query-chardev" }
1147 .name = "query-chardev",
1149 .mhandler.cmd_new = qmp_marshal_input_query_chardev,
1156 Show the block devices.
1158 Each block device information is stored in a json-object and the returned value
1159 is a json-array of all devices.
1161 Each json-object contain the following:
1163 - "device": device name (json-string)
1164 - "type": device type (json-string)
1165 - deprecated, retained for backward compatibility
1166 - Possible values: "unknown"
1167 - "removable": true if the device is removable, false otherwise (json-bool)
1168 - "locked": true if the device is locked, false otherwise (json-bool)
1169 - "tray-open": only present if removable, true if the device has a tray,
1170 and it is open (json-bool)
1171 - "inserted": only present if the device is inserted, it is a json-object
1172 containing the following:
1173 - "file": device file name (json-string)
1174 - "ro": true if read-only, false otherwise (json-bool)
1175 - "drv": driver format name (json-string)
1176 - Possible values: "blkdebug", "bochs", "cloop", "cow", "dmg",
1177 "file", "file", "ftp", "ftps", "host_cdrom",
1178 "host_device", "host_floppy", "http", "https",
1179 "nbd", "parallels", "qcow", "qcow2", "raw",
1180 "tftp", "vdi", "vmdk", "vpc", "vvfat"
1181 - "backing_file": backing file name (json-string, optional)
1182 - "encrypted": true if encrypted, false otherwise (json-bool)
1183 - "bps": limit total bytes per second (json-int)
1184 - "bps_rd": limit read bytes per second (json-int)
1185 - "bps_wr": limit write bytes per second (json-int)
1186 - "iops": limit total I/O operations per second (json-int)
1187 - "iops_rd": limit read operations per second (json-int)
1188 - "iops_wr": limit write operations per second (json-int)
1190 - "io-status": I/O operation status, only present if the device supports it
1191 and the VM is configured to stop on errors. It's always reset
1192 to "ok" when the "cont" command is issued (json_string, optional)
1193 - Possible values: "ok", "failed", "nospace"
1197 -> { "execute": "query-block" }
1202 "device":"ide0-hd0",
1209 "file":"disks/test.img",
1221 "device":"ide1-cd0",
1244 .name = "query-block",
1246 .mhandler.cmd_new = qmp_marshal_input_query_block,
1253 Show block device statistics.
1255 Each device statistic information is stored in a json-object and the returned
1256 value is a json-array of all devices.
1258 Each json-object contain the following:
1260 - "device": device name (json-string)
1261 - "stats": A json-object with the statistics information, it contains:
1262 - "rd_bytes": bytes read (json-int)
1263 - "wr_bytes": bytes written (json-int)
1264 - "rd_operations": read operations (json-int)
1265 - "wr_operations": write operations (json-int)
1266 - "flush_operations": cache flush operations (json-int)
1267 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
1268 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
1269 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
1270 - "wr_highest_offset": Highest offset of a sector written since the
1271 BlockDriverState has been opened (json-int)
1272 - "parent": Contains recursively the statistics of the underlying
1273 protocol (e.g. the host file for a qcow2 image). If there is
1274 no underlying protocol, this field is omitted
1275 (json-object, optional)
1279 -> { "execute": "query-blockstats" }
1283 "device":"ide0-hd0",
1286 "wr_highest_offset":3686448128,
1288 "wr_operations":751,
1289 "rd_bytes":122567168,
1290 "rd_operations":36772
1291 "wr_total_times_ns":313253456
1292 "rd_total_times_ns":3465673657
1293 "flush_total_times_ns":49653
1294 "flush_operations":61,
1298 "wr_highest_offset":2821110784,
1300 "wr_operations":692,
1301 "rd_bytes":122739200,
1302 "rd_operations":36604
1303 "flush_operations":51,
1304 "wr_total_times_ns":313253456
1305 "rd_total_times_ns":3465673657
1306 "flush_total_times_ns":49653
1310 "device":"ide1-cd0",
1312 "wr_highest_offset":0,
1317 "flush_operations":0,
1318 "wr_total_times_ns":0
1319 "rd_total_times_ns":0
1320 "flush_total_times_ns":0
1326 "wr_highest_offset":0,
1331 "flush_operations":0,
1332 "wr_total_times_ns":0
1333 "rd_total_times_ns":0
1334 "flush_total_times_ns":0
1340 "wr_highest_offset":0,
1345 "flush_operations":0,
1346 "wr_total_times_ns":0
1347 "rd_total_times_ns":0
1348 "flush_total_times_ns":0
1357 .name = "query-blockstats",
1359 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
1366 Show CPU information.
1368 Return a json-array. Each CPU is represented by a json-object, which contains:
1370 - "CPU": CPU index (json-int)
1371 - "current": true if this is the current CPU, false otherwise (json-bool)
1372 - "halted": true if the cpu is halted, false otherwise (json-bool)
1373 - Current program counter. The key's name depends on the architecture:
1374 "pc": i386/x86_64 (json-int)
1375 "nip": PPC (json-int)
1376 "pc" and "npc": sparc (json-int)
1377 "PC": mips (json-int)
1378 - "thread_id": ID of the underlying host thread (json-int)
1382 -> { "execute": "query-cpus" }
1405 .name = "query-cpus",
1407 .mhandler.cmd_new = qmp_marshal_input_query_cpus,
1414 PCI buses and devices information.
1416 The returned value is a json-array of all buses. Each bus is represented by
1417 a json-object, which has a key with a json-array of all PCI devices attached
1418 to it. Each device is represented by a json-object.
1420 The bus json-object contains the following:
1422 - "bus": bus number (json-int)
1423 - "devices": a json-array of json-objects, each json-object represents a
1426 The PCI device json-object contains the following:
1428 - "bus": identical to the parent's bus number (json-int)
1429 - "slot": slot number (json-int)
1430 - "function": function number (json-int)
1431 - "class_info": a json-object containing:
1432 - "desc": device class description (json-string, optional)
1433 - "class": device class number (json-int)
1434 - "id": a json-object containing:
1435 - "device": device ID (json-int)
1436 - "vendor": vendor ID (json-int)
1437 - "irq": device's IRQ if assigned (json-int, optional)
1438 - "qdev_id": qdev id string (json-string)
1439 - "pci_bridge": It's a json-object, only present if this device is a
1440 PCI bridge, contains:
1441 - "bus": bus number (json-int)
1442 - "secondary": secondary bus number (json-int)
1443 - "subordinate": subordinate bus number (json-int)
1444 - "io_range": I/O memory range information, a json-object with the
1446 - "base": base address, in bytes (json-int)
1447 - "limit": limit address, in bytes (json-int)
1448 - "memory_range": memory range information, a json-object with the
1450 - "base": base address, in bytes (json-int)
1451 - "limit": limit address, in bytes (json-int)
1452 - "prefetchable_range": Prefetchable memory range information, a
1453 json-object with the following members:
1454 - "base": base address, in bytes (json-int)
1455 - "limit": limit address, in bytes (json-int)
1456 - "devices": a json-array of PCI devices if there's any attached, each
1457 each element is represented by a json-object, which contains
1458 the same members of the 'PCI device json-object' described
1460 - "regions": a json-array of json-objects, each json-object represents a
1461 memory region of this device
1463 The memory range json-object contains the following:
1465 - "base": base memory address (json-int)
1466 - "limit": limit value (json-int)
1468 The region json-object can be an I/O region or a memory region, an I/O region
1469 json-object contains the following:
1471 - "type": "io" (json-string, fixed)
1472 - "bar": BAR number (json-int)
1473 - "address": memory address (json-int)
1474 - "size": memory size (json-int)
1476 A memory region json-object contains the following:
1478 - "type": "memory" (json-string, fixed)
1479 - "bar": BAR number (json-int)
1480 - "address": memory address (json-int)
1481 - "size": memory size (json-int)
1482 - "mem_type_64": true or false (json-bool)
1483 - "prefetch": true or false (json-bool)
1487 -> { "execute": "query-pci" }
1499 "desc":"Host bridge"
1533 "desc":"IDE controller"
1555 "desc":"VGA controller"
1565 "mem_type_64":false,
1568 "address":4026531840,
1573 "mem_type_64":false,
1576 "address":4060086272,
1581 "mem_type_64":false,
1596 "desc":"RAM controller"
1617 Note: This example has been shortened as the real response is too long.
1622 .name = "query-pci",
1624 .mhandler.cmd_new = qmp_marshal_input_query_pci,
1631 Show KVM information.
1633 Return a json-object with the following information:
1635 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
1636 - "present": true if QEMU has KVM support, false otherwise (json-bool)
1640 -> { "execute": "query-kvm" }
1641 <- { "return": { "enabled": true, "present": true } }
1646 .name = "query-kvm",
1648 .mhandler.cmd_new = qmp_marshal_input_query_kvm,
1655 Return a json-object with the following information:
1657 - "running": true if the VM is running, or false if it is paused (json-bool)
1658 - "singlestep": true if the VM is in single step mode,
1659 false otherwise (json-bool)
1660 - "status": one of the following values (json-string)
1661 "debug" - QEMU is running on a debugger
1662 "inmigrate" - guest is paused waiting for an incoming migration
1663 "internal-error" - An internal error that prevents further guest
1664 execution has occurred
1665 "io-error" - the last IOP has failed and the device is configured
1666 to pause on I/O errors
1667 "paused" - guest has been paused via the 'stop' command
1668 "postmigrate" - guest is paused following a successful 'migrate'
1669 "prelaunch" - QEMU was started with -S and guest has not started
1670 "finish-migrate" - guest is paused to finish the migration process
1671 "restore-vm" - guest is paused to restore VM state
1672 "running" - guest is actively running
1673 "save-vm" - guest is paused to save the VM state
1674 "shutdown" - guest is shut down (and -no-shutdown is in use)
1675 "watchdog" - the watchdog action is configured to pause and
1680 -> { "execute": "query-status" }
1681 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
1686 .name = "query-status",
1688 .mhandler.cmd_new = qmp_marshal_input_query_status,
1695 Show VM mice information.
1697 Each mouse is represented by a json-object, the returned value is a json-array
1700 The mouse json-object contains the following:
1702 - "name": mouse's name (json-string)
1703 - "index": mouse's index (json-int)
1704 - "current": true if this mouse is receiving events, false otherwise (json-bool)
1705 - "absolute": true if the mouse generates absolute input events (json-bool)
1709 -> { "execute": "query-mice" }
1713 "name":"QEMU Microsoft Mouse",
1719 "name":"QEMU PS/2 Mouse",
1730 .name = "query-mice",
1732 .mhandler.cmd_new = qmp_marshal_input_query_mice,
1739 Show VNC server information.
1741 Return a json-object with server information. Connected clients are returned
1742 as a json-array of json-objects.
1744 The main json-object contains the following:
1746 - "enabled": true or false (json-bool)
1747 - "host": server's IP address (json-string)
1748 - "family": address family (json-string)
1749 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1750 - "service": server's port number (json-string)
1751 - "auth": authentication method (json-string)
1752 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
1753 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
1754 "vencrypt+plain", "vencrypt+tls+none",
1755 "vencrypt+tls+plain", "vencrypt+tls+sasl",
1756 "vencrypt+tls+vnc", "vencrypt+x509+none",
1757 "vencrypt+x509+plain", "vencrypt+x509+sasl",
1758 "vencrypt+x509+vnc", "vnc"
1759 - "clients": a json-array of all connected clients
1761 Clients are described by a json-object, each one contain the following:
1763 - "host": client's IP address (json-string)
1764 - "family": address family (json-string)
1765 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1766 - "service": client's port number (json-string)
1767 - "x509_dname": TLS dname (json-string, optional)
1768 - "sasl_username": SASL username (json-string, optional)
1772 -> { "execute": "query-vnc" }
1793 .name = "query-vnc",
1795 .mhandler.cmd_new = qmp_marshal_input_query_vnc,
1802 Show SPICE server information.
1804 Return a json-object with server information. Connected clients are returned
1805 as a json-array of json-objects.
1807 The main json-object contains the following:
1809 - "enabled": true or false (json-bool)
1810 - "host": server's IP address (json-string)
1811 - "port": server's port number (json-int, optional)
1812 - "tls-port": server's port number (json-int, optional)
1813 - "auth": authentication method (json-string)
1814 - Possible values: "none", "spice"
1815 - "channels": a json-array of all active channels clients
1817 Channels are described by a json-object, each one contain the following:
1819 - "host": client's IP address (json-string)
1820 - "family": address family (json-string)
1821 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1822 - "port": client's port number (json-string)
1823 - "connection-id": spice connection id. All channels with the same id
1824 belong to the same spice session (json-int)
1825 - "channel-type": channel type. "1" is the main control channel, filter for
1826 this one if you want track spice sessions only (json-int)
1827 - "channel-id": channel id. Usually "0", might be different needed when
1828 multiple channels of the same type exist, such as multiple
1829 display channels in a multihead setup (json-int)
1830 - "tls": whevener the channel is encrypted (json-bool)
1834 -> { "execute": "query-spice" }
1847 "connection-id": 1804289383,
1848 "host": "127.0.0.1",
1856 "connection-id": 1804289383,
1857 "host": "127.0.0.1",
1861 [ ... more channels follow ... ]
1868 #if defined(CONFIG_SPICE)
1870 .name = "query-spice",
1872 .mhandler.cmd_new = qmp_marshal_input_query_spice,
1882 Return a json-object with the following information:
1884 - "name": VM's name (json-string, optional)
1888 -> { "execute": "query-name" }
1889 <- { "return": { "name": "qemu-name" } }
1894 .name = "query-name",
1896 .mhandler.cmd_new = qmp_marshal_input_query_name,
1905 Return a json-object with the following information:
1907 - "UUID": Universally Unique Identifier (json-string)
1911 -> { "execute": "query-uuid" }
1912 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
1917 .name = "query-uuid",
1919 .mhandler.cmd_new = qmp_marshal_input_query_uuid,
1928 Return a json-object. If migration is active there will be another json-object
1929 with RAM migration status and if block migration is active another one with
1930 block migration status.
1932 The main json-object contains the following:
1934 - "status": migration status (json-string)
1935 - Possible values: "active", "completed", "failed", "cancelled"
1936 - "ram": only present if "status" is "active", it is a json-object with the
1937 following RAM information (in bytes):
1938 - "transferred": amount transferred (json-int)
1939 - "remaining": amount remaining (json-int)
1940 - "total": total (json-int)
1941 - "disk": only present if "status" is "active" and it is a block migration,
1942 it is a json-object with the following disk information (in bytes):
1943 - "transferred": amount transferred (json-int)
1944 - "remaining": amount remaining (json-int)
1945 - "total": total (json-int)
1949 1. Before the first migration
1951 -> { "execute": "query-migrate" }
1954 2. Migration is done and has succeeded
1956 -> { "execute": "query-migrate" }
1957 <- { "return": { "status": "completed" } }
1959 3. Migration is done and has failed
1961 -> { "execute": "query-migrate" }
1962 <- { "return": { "status": "failed" } }
1964 4. Migration is being performed and is not a block migration:
1966 -> { "execute": "query-migrate" }
1978 5. Migration is being performed and is a block migration:
1980 -> { "execute": "query-migrate" }
1986 "remaining":1053304,
1991 "remaining":20880384,
2000 .name = "query-migrate",
2002 .mhandler.cmd_new = qmp_marshal_input_query_migrate,
2009 Show balloon information.
2011 Make an asynchronous request for balloon info. When the request completes a
2012 json-object will be returned containing the following data:
2014 - "actual": current balloon value in bytes (json-int)
2015 - "mem_swapped_in": Amount of memory swapped in bytes (json-int, optional)
2016 - "mem_swapped_out": Amount of memory swapped out in bytes (json-int, optional)
2017 - "major_page_faults": Number of major faults (json-int, optional)
2018 - "minor_page_faults": Number of minor faults (json-int, optional)
2019 - "free_mem": Total amount of free and unused memory in
2020 bytes (json-int, optional)
2021 - "total_mem": Total amount of available memory in bytes (json-int, optional)
2025 -> { "execute": "query-balloon" }
2028 "actual":1073741824,
2030 "mem_swapped_out":0,
2031 "major_page_faults":142,
2032 "minor_page_faults":239245,
2033 "free_mem":1014185984,
2034 "total_mem":1044668416
2041 .name = "query-balloon",
2043 .mhandler.cmd_new = qmp_marshal_input_query_balloon,