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" }
202 .mhandler.cmd_new = qmp_marshal_input_cont,
215 -> { "execute": "cont" }
221 .name = "system_reset",
223 .mhandler.cmd_new = qmp_marshal_input_system_reset,
236 -> { "execute": "system_reset" }
242 .name = "system_powerdown",
244 .mhandler.cmd_new = qmp_marshal_input_system_powerdown,
251 Send system power down event.
257 -> { "execute": "system_powerdown" }
263 .name = "device_add",
264 .args_type = "device:O",
265 .params = "driver[,prop=value][,...]",
266 .help = "add device, like -device on the command line",
267 .user_print = monitor_user_noop,
268 .mhandler.cmd_new = do_device_add,
279 - "driver": the name of the new device's driver (json-string)
280 - "bus": the device's parent bus (device tree path, json-string, optional)
281 - "id": the device's ID, must be unique (json-string)
286 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
291 (1) For detailed information about this command, please refer to the
292 'docs/qdev-device-use.txt' file.
294 (2) It's possible to list device properties by running QEMU with the
295 "-device DEVICE,\?" command-line argument, where DEVICE is the device's name
300 .name = "device_del",
303 .help = "remove device",
304 .user_print = monitor_user_noop,
305 .mhandler.cmd_new = do_device_del,
316 - "id": the device's ID (json-string)
320 -> { "execute": "device_del", "arguments": { "id": "net1" } }
327 .args_type = "index:i",
328 .mhandler.cmd_new = qmp_marshal_input_cpu,
339 - "index": the CPU's index (json-int)
343 -> { "execute": "cpu", "arguments": { "index": 0 } }
346 Note: CPUs' indexes are obtained with the 'query-cpus' command.
352 .args_type = "val:l,size:i,filename:s,cpu:i?",
353 .mhandler.cmd_new = qmp_marshal_input_memsave,
360 Save to disk virtual memory dump starting at 'val' of size 'size'.
364 - "val": the starting address (json-int)
365 - "size": the memory size, in bytes (json-int)
366 - "filename": file path (json-string)
367 - "cpu": virtual CPU index (json-int, optional)
371 -> { "execute": "memsave",
372 "arguments": { "val": 10,
374 "filename": "/tmp/virtual-mem-dump" } }
381 .args_type = "val:l,size:i,filename:s",
382 .mhandler.cmd_new = qmp_marshal_input_pmemsave,
389 Save to disk physical memory dump starting at 'val' of size 'size'.
393 - "val": the starting address (json-int)
394 - "size": the memory size, in bytes (json-int)
395 - "filename": file path (json-string)
399 -> { "execute": "pmemsave",
400 "arguments": { "val": 10,
402 "filename": "/tmp/physical-mem-dump" } }
408 .name = "inject-nmi",
410 .mhandler.cmd_new = qmp_marshal_input_inject_nmi,
417 Inject an NMI on guest's CPUs.
423 -> { "execute": "inject-nmi" }
426 Note: inject-nmi is only supported for x86 guest currently, it will
427 returns "Unsupported" error for non-x86 guest.
433 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
434 .params = "[-d] [-b] [-i] uri",
435 .help = "migrate to URI (using -d to not wait for completion)"
436 "\n\t\t\t -b for migration without shared storage with"
437 " full copy of disk\n\t\t\t -i for migration without "
438 "shared storage with incremental copy of disk "
439 "(base image shared between src and destination)",
440 .user_print = monitor_user_noop,
441 .mhandler.cmd_new = do_migrate,
452 - "blk": block migration, full disk copy (json-bool, optional)
453 - "inc": incremental disk copy (json-bool, optional)
454 - "uri": Destination URI (json-string)
458 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
463 (1) The 'query-migrate' command should be used to check migration's progress
464 and final result (this information is provided by the 'status' member)
465 (2) All boolean arguments default to false
466 (3) The user Monitor's "detach" argument is invalid in QMP and should not
472 .name = "migrate_cancel",
475 .help = "cancel the current VM migration",
476 .user_print = monitor_user_noop,
477 .mhandler.cmd_new = do_migrate_cancel,
484 Cancel the current migration.
490 -> { "execute": "migrate_cancel" }
496 .name = "migrate_set_speed",
497 .args_type = "value:o",
499 .help = "set maximum speed (in bytes) for migrations",
500 .user_print = monitor_user_noop,
501 .mhandler.cmd_new = do_migrate_set_speed,
508 Set maximum speed for migrations.
512 - "value": maximum speed, in bytes per second (json-int)
516 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
522 .name = "migrate_set_downtime",
523 .args_type = "value:T",
525 .help = "set maximum tolerated downtime (in seconds) for migrations",
526 .user_print = monitor_user_noop,
527 .mhandler.cmd_new = do_migrate_set_downtime,
534 Set maximum tolerated downtime (in seconds) for migrations.
538 - "value": maximum downtime (json-number)
542 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
548 .name = "client_migrate_info",
549 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
550 .params = "protocol hostname port tls-port cert-subject",
551 .help = "send migration info to spice/vnc client",
552 .user_print = monitor_user_noop,
553 .mhandler.cmd_async = client_migrate_info,
554 .flags = MONITOR_CMD_ASYNC,
561 Set the spice/vnc connection info for the migration target. The spice/vnc
562 server will ask the spice/vnc client to automatically reconnect using the
563 new parameters (if specified) once the vm migration finished successfully.
567 - "protocol": protocol: "spice" or "vnc" (json-string)
568 - "hostname": migration target hostname (json-string)
569 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
570 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
571 - "cert-subject": server certificate subject (json-string, optional)
575 -> { "execute": "client_migrate_info",
576 "arguments": { "protocol": "spice",
577 "hostname": "virt42.lab.kraxel.org",
584 .name = "netdev_add",
585 .args_type = "netdev:O",
586 .params = "[user|tap|socket],id=str[,prop=value][,...]",
587 .help = "add host network device",
588 .user_print = monitor_user_noop,
589 .mhandler.cmd_new = do_netdev_add,
596 Add host network device.
600 - "type": the device type, "tap", "user", ... (json-string)
601 - "id": the device's ID, must be unique (json-string)
606 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
609 Note: The supported device options are the same ones supported by the '-net'
610 command-line argument, which are listed in the '-help' output or QEMU's
616 .name = "netdev_del",
619 .help = "remove host network device",
620 .user_print = monitor_user_noop,
621 .mhandler.cmd_new = do_netdev_del,
628 Remove host network device.
632 - "id": the device's ID, must be unique (json-string)
636 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
643 .name = "block_resize",
644 .args_type = "device:B,size:o",
645 .params = "device size",
646 .help = "resize a block image",
647 .user_print = monitor_user_noop,
648 .mhandler.cmd_new = do_block_resize,
655 Resize a block image while a guest is running.
659 - "device": the device's ID, must be unique (json-string)
664 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
670 .name = "blockdev-snapshot-sync",
671 .args_type = "device:B,snapshot-file:s?,format:s?",
672 .params = "device [new-image-file] [format]",
673 .user_print = monitor_user_noop,
674 .mhandler.cmd_new = do_snapshot_blkdev,
678 blockdev-snapshot-sync
679 ----------------------
681 Synchronous snapshot of a block device. snapshot-file specifies the
682 target of the new image. If the file exists, or if it is a device, the
683 snapshot will be created in the existing file/device. If does not
684 exist, a new file will be created. format specifies the format of the
685 snapshot image, default is qcow2.
689 - "device": device name to snapshot (json-string)
690 - "snapshot-file": name of new image file (json-string)
691 - "format": format of new image (json-string, optional)
695 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
697 "/some/place/my-image",
698 "format": "qcow2" } }
705 .args_type = "value:M",
707 .help = "request VM to change its memory allocation (in MB)",
708 .user_print = monitor_user_noop,
709 .mhandler.cmd_async = do_balloon,
710 .flags = MONITOR_CMD_ASYNC,
717 Request VM to change its memory allocation (in bytes).
721 - "value": New memory allocation (json-int)
725 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
732 .args_type = "name:s,up:b",
733 .params = "name on|off",
734 .help = "change the link status of a network adapter",
735 .user_print = monitor_user_noop,
736 .mhandler.cmd_new = do_set_link,
743 Change the link status of a network adapter.
747 - "name": network device name (json-string)
748 - "up": status is up (json-bool)
752 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
759 .args_type = "fdname:s",
760 .params = "getfd name",
761 .help = "receive a file descriptor via SCM rights and assign it a name",
762 .user_print = monitor_user_noop,
763 .mhandler.cmd_new = do_getfd,
770 Receive a file descriptor via SCM rights and assign it a name.
774 - "fdname": file descriptor name (json-string)
778 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
785 .args_type = "fdname:s",
786 .params = "closefd name",
787 .help = "close a file descriptor previously passed via SCM rights",
788 .user_print = monitor_user_noop,
789 .mhandler.cmd_new = do_closefd,
796 Close a file descriptor previously passed via SCM rights.
800 - "fdname": file descriptor name (json-string)
804 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
810 .name = "block_passwd",
811 .args_type = "device:B,password:s",
812 .params = "block_passwd device password",
813 .help = "set the password of encrypted block devices",
814 .user_print = monitor_user_noop,
815 .mhandler.cmd_new = do_block_set_passwd,
822 Set the password of encrypted block devices.
826 - "device": device name (json-string)
827 - "password": password (json-string)
831 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
832 "password": "12345" } }
838 .name = "block_set_io_throttle",
839 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l",
840 .params = "device bps bps_rd bps_wr iops iops_rd iops_wr",
841 .help = "change I/O throttle limits for a block drive",
842 .user_print = monitor_user_noop,
843 .mhandler.cmd_new = do_block_set_io_throttle,
847 block_set_io_throttle
850 Change I/O throttle limits for a block drive.
854 - "device": device name (json-string)
855 - "bps": total throughput limit in bytes per second(json-int)
856 - "bps_rd": read throughput limit in bytes per second(json-int)
857 - "bps_wr": read throughput limit in bytes per second(json-int)
858 - "iops": total I/O operations per second(json-int)
859 - "iops_rd": read I/O operations per second(json-int)
860 - "iops_wr": write I/O operations per second(json-int)
864 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
876 .name = "set_password",
877 .args_type = "protocol:s,password:s,connected:s?",
878 .params = "protocol password action-if-connected",
879 .help = "set spice/vnc password",
880 .user_print = monitor_user_noop,
881 .mhandler.cmd_new = set_password,
888 Set the password for vnc/spice protocols.
892 - "protocol": protocol name (json-string)
893 - "password": password (json-string)
894 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
898 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
899 "password": "secret" } }
905 .name = "expire_password",
906 .args_type = "protocol:s,time:s",
907 .params = "protocol time",
908 .help = "set spice/vnc password expire-time",
909 .user_print = monitor_user_noop,
910 .mhandler.cmd_new = expire_password,
917 Set the password expire time for vnc/spice protocols.
921 - "protocol": protocol name (json-string)
922 - "time": [ now | never | +secs | secs ] (json-string)
926 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
933 .name = "add_client",
934 .args_type = "protocol:s,fdname:s,skipauth:b?",
935 .params = "protocol fdname skipauth",
936 .help = "add a graphics client",
937 .user_print = monitor_user_noop,
938 .mhandler.cmd_new = add_graphics_client,
945 Add a graphics client
949 - "protocol": protocol name (json-string)
950 - "fdname": file descriptor name (json-string)
954 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
955 "fdname": "myclient" } }
960 .name = "qmp_capabilities",
963 .help = "enable QMP capabilities",
964 .user_print = monitor_user_noop,
965 .mhandler.cmd_new = do_qmp_capabilities,
972 Enable QMP capabilities.
978 -> { "execute": "qmp_capabilities" }
981 Note: This command must be issued before issuing any other command.
986 .name = "human-monitor-command",
987 .args_type = "command-line:s,cpu-index:i?",
990 .user_print = monitor_user_noop,
991 .mhandler.cmd_new = do_hmp_passthrough,
995 human-monitor-command
996 ---------------------
998 Execute a Human Monitor command.
1002 - command-line: the command name and its arguments, just like the
1003 Human Monitor's shell (json-string)
1004 - cpu-index: select the CPU number to be used by commands which access CPU
1005 data, like 'info registers'. The Monitor selects CPU 0 if this
1006 argument is not provided (json-int, optional)
1010 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1011 <- { "return": "kvm support: enabled\r\n" }
1015 (1) The Human Monitor is NOT an stable interface, this means that command
1016 names, arguments and responses can change or be removed at ANY time.
1017 Applications that rely on long term stability guarantees should NOT
1022 o This command is stateless, this means that commands that depend
1023 on state information (such as getfd) might not work
1025 o Commands that prompt the user for data (eg. 'cont' when the block
1026 device is encrypted) don't currently work
1031 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1032 HXCOMM this! We will possibly move query commands definitions inside those
1033 HXCOMM sections, just like regular commands.
1043 Return a json-object with the following information:
1045 - "qemu": A json-object containing three integer values:
1046 - "major": QEMU's major version (json-int)
1047 - "minor": QEMU's minor version (json-int)
1048 - "micro": QEMU's micro version (json-int)
1049 - "package": package's version (json-string)
1053 -> { "execute": "query-version" }
1068 .name = "query-version",
1070 .mhandler.cmd_new = qmp_marshal_input_query_version,
1077 List QMP available commands.
1079 Each command is represented by a json-object, the returned value is a json-array
1082 Each json-object contain:
1084 - "name": command's name (json-string)
1088 -> { "execute": "query-commands" }
1092 "name":"query-balloon"
1095 "name":"system_powerdown"
1100 Note: This example has been shortened as the real response is too long.
1105 .name = "query-commands",
1107 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1114 Each device is represented by a json-object. The returned value is a json-array
1117 Each json-object contain the following:
1119 - "label": device's label (json-string)
1120 - "filename": device's file (json-string)
1124 -> { "execute": "query-chardev" }
1141 .name = "query-chardev",
1143 .mhandler.cmd_new = qmp_marshal_input_query_chardev,
1150 Show the block devices.
1152 Each block device information is stored in a json-object and the returned value
1153 is a json-array of all devices.
1155 Each json-object contain the following:
1157 - "device": device name (json-string)
1158 - "type": device type (json-string)
1159 - deprecated, retained for backward compatibility
1160 - Possible values: "unknown"
1161 - "removable": true if the device is removable, false otherwise (json-bool)
1162 - "locked": true if the device is locked, false otherwise (json-bool)
1163 - "tray-open": only present if removable, true if the device has a tray,
1164 and it is open (json-bool)
1165 - "inserted": only present if the device is inserted, it is a json-object
1166 containing the following:
1167 - "file": device file name (json-string)
1168 - "ro": true if read-only, false otherwise (json-bool)
1169 - "drv": driver format name (json-string)
1170 - Possible values: "blkdebug", "bochs", "cloop", "cow", "dmg",
1171 "file", "file", "ftp", "ftps", "host_cdrom",
1172 "host_device", "host_floppy", "http", "https",
1173 "nbd", "parallels", "qcow", "qcow2", "raw",
1174 "tftp", "vdi", "vmdk", "vpc", "vvfat"
1175 - "backing_file": backing file name (json-string, optional)
1176 - "encrypted": true if encrypted, false otherwise (json-bool)
1177 - "bps": limit total bytes per second (json-int)
1178 - "bps_rd": limit read bytes per second (json-int)
1179 - "bps_wr": limit write bytes per second (json-int)
1180 - "iops": limit total I/O operations per second (json-int)
1181 - "iops_rd": limit read operations per second (json-int)
1182 - "iops_wr": limit write operations per second (json-int)
1184 - "io-status": I/O operation status, only present if the device supports it
1185 and the VM is configured to stop on errors. It's always reset
1186 to "ok" when the "cont" command is issued (json_string, optional)
1187 - Possible values: "ok", "failed", "nospace"
1191 -> { "execute": "query-block" }
1196 "device":"ide0-hd0",
1203 "file":"disks/test.img",
1215 "device":"ide1-cd0",
1238 .name = "query-block",
1240 .mhandler.cmd_new = qmp_marshal_input_query_block,
1247 Show block device statistics.
1249 Each device statistic information is stored in a json-object and the returned
1250 value is a json-array of all devices.
1252 Each json-object contain the following:
1254 - "device": device name (json-string)
1255 - "stats": A json-object with the statistics information, it contains:
1256 - "rd_bytes": bytes read (json-int)
1257 - "wr_bytes": bytes written (json-int)
1258 - "rd_operations": read operations (json-int)
1259 - "wr_operations": write operations (json-int)
1260 - "flush_operations": cache flush operations (json-int)
1261 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
1262 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
1263 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
1264 - "wr_highest_offset": Highest offset of a sector written since the
1265 BlockDriverState has been opened (json-int)
1266 - "parent": Contains recursively the statistics of the underlying
1267 protocol (e.g. the host file for a qcow2 image). If there is
1268 no underlying protocol, this field is omitted
1269 (json-object, optional)
1273 -> { "execute": "query-blockstats" }
1277 "device":"ide0-hd0",
1280 "wr_highest_offset":3686448128,
1282 "wr_operations":751,
1283 "rd_bytes":122567168,
1284 "rd_operations":36772
1285 "wr_total_times_ns":313253456
1286 "rd_total_times_ns":3465673657
1287 "flush_total_times_ns":49653
1288 "flush_operations":61,
1292 "wr_highest_offset":2821110784,
1294 "wr_operations":692,
1295 "rd_bytes":122739200,
1296 "rd_operations":36604
1297 "flush_operations":51,
1298 "wr_total_times_ns":313253456
1299 "rd_total_times_ns":3465673657
1300 "flush_total_times_ns":49653
1304 "device":"ide1-cd0",
1306 "wr_highest_offset":0,
1311 "flush_operations":0,
1312 "wr_total_times_ns":0
1313 "rd_total_times_ns":0
1314 "flush_total_times_ns":0
1320 "wr_highest_offset":0,
1325 "flush_operations":0,
1326 "wr_total_times_ns":0
1327 "rd_total_times_ns":0
1328 "flush_total_times_ns":0
1334 "wr_highest_offset":0,
1339 "flush_operations":0,
1340 "wr_total_times_ns":0
1341 "rd_total_times_ns":0
1342 "flush_total_times_ns":0
1351 .name = "query-blockstats",
1353 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
1360 Show CPU information.
1362 Return a json-array. Each CPU is represented by a json-object, which contains:
1364 - "CPU": CPU index (json-int)
1365 - "current": true if this is the current CPU, false otherwise (json-bool)
1366 - "halted": true if the cpu is halted, false otherwise (json-bool)
1367 - Current program counter. The key's name depends on the architecture:
1368 "pc": i386/x86_64 (json-int)
1369 "nip": PPC (json-int)
1370 "pc" and "npc": sparc (json-int)
1371 "PC": mips (json-int)
1372 - "thread_id": ID of the underlying host thread (json-int)
1376 -> { "execute": "query-cpus" }
1399 .name = "query-cpus",
1401 .mhandler.cmd_new = qmp_marshal_input_query_cpus,
1408 PCI buses and devices information.
1410 The returned value is a json-array of all buses. Each bus is represented by
1411 a json-object, which has a key with a json-array of all PCI devices attached
1412 to it. Each device is represented by a json-object.
1414 The bus json-object contains the following:
1416 - "bus": bus number (json-int)
1417 - "devices": a json-array of json-objects, each json-object represents a
1420 The PCI device json-object contains the following:
1422 - "bus": identical to the parent's bus number (json-int)
1423 - "slot": slot number (json-int)
1424 - "function": function number (json-int)
1425 - "class_info": a json-object containing:
1426 - "desc": device class description (json-string, optional)
1427 - "class": device class number (json-int)
1428 - "id": a json-object containing:
1429 - "device": device ID (json-int)
1430 - "vendor": vendor ID (json-int)
1431 - "irq": device's IRQ if assigned (json-int, optional)
1432 - "qdev_id": qdev id string (json-string)
1433 - "pci_bridge": It's a json-object, only present if this device is a
1434 PCI bridge, contains:
1435 - "bus": bus number (json-int)
1436 - "secondary": secondary bus number (json-int)
1437 - "subordinate": subordinate bus number (json-int)
1438 - "io_range": I/O memory range information, a json-object with the
1440 - "base": base address, in bytes (json-int)
1441 - "limit": limit address, in bytes (json-int)
1442 - "memory_range": memory range information, a json-object with the
1444 - "base": base address, in bytes (json-int)
1445 - "limit": limit address, in bytes (json-int)
1446 - "prefetchable_range": Prefetchable memory range information, a
1447 json-object with the following members:
1448 - "base": base address, in bytes (json-int)
1449 - "limit": limit address, in bytes (json-int)
1450 - "devices": a json-array of PCI devices if there's any attached, each
1451 each element is represented by a json-object, which contains
1452 the same members of the 'PCI device json-object' described
1454 - "regions": a json-array of json-objects, each json-object represents a
1455 memory region of this device
1457 The memory range json-object contains the following:
1459 - "base": base memory address (json-int)
1460 - "limit": limit value (json-int)
1462 The region json-object can be an I/O region or a memory region, an I/O region
1463 json-object contains the following:
1465 - "type": "io" (json-string, fixed)
1466 - "bar": BAR number (json-int)
1467 - "address": memory address (json-int)
1468 - "size": memory size (json-int)
1470 A memory region json-object contains the following:
1472 - "type": "memory" (json-string, fixed)
1473 - "bar": BAR number (json-int)
1474 - "address": memory address (json-int)
1475 - "size": memory size (json-int)
1476 - "mem_type_64": true or false (json-bool)
1477 - "prefetch": true or false (json-bool)
1481 -> { "execute": "query-pci" }
1493 "desc":"Host bridge"
1527 "desc":"IDE controller"
1549 "desc":"VGA controller"
1559 "mem_type_64":false,
1562 "address":4026531840,
1567 "mem_type_64":false,
1570 "address":4060086272,
1575 "mem_type_64":false,
1590 "desc":"RAM controller"
1611 Note: This example has been shortened as the real response is too long.
1616 .name = "query-pci",
1618 .mhandler.cmd_new = qmp_marshal_input_query_pci,
1625 Show KVM information.
1627 Return a json-object with the following information:
1629 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
1630 - "present": true if QEMU has KVM support, false otherwise (json-bool)
1634 -> { "execute": "query-kvm" }
1635 <- { "return": { "enabled": true, "present": true } }
1640 .name = "query-kvm",
1642 .mhandler.cmd_new = qmp_marshal_input_query_kvm,
1649 Return a json-object with the following information:
1651 - "running": true if the VM is running, or false if it is paused (json-bool)
1652 - "singlestep": true if the VM is in single step mode,
1653 false otherwise (json-bool)
1654 - "status": one of the following values (json-string)
1655 "debug" - QEMU is running on a debugger
1656 "inmigrate" - guest is paused waiting for an incoming migration
1657 "internal-error" - An internal error that prevents further guest
1658 execution has occurred
1659 "io-error" - the last IOP has failed and the device is configured
1660 to pause on I/O errors
1661 "paused" - guest has been paused via the 'stop' command
1662 "postmigrate" - guest is paused following a successful 'migrate'
1663 "prelaunch" - QEMU was started with -S and guest has not started
1664 "finish-migrate" - guest is paused to finish the migration process
1665 "restore-vm" - guest is paused to restore VM state
1666 "running" - guest is actively running
1667 "save-vm" - guest is paused to save the VM state
1668 "shutdown" - guest is shut down (and -no-shutdown is in use)
1669 "watchdog" - the watchdog action is configured to pause and
1674 -> { "execute": "query-status" }
1675 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
1680 .name = "query-status",
1682 .mhandler.cmd_new = qmp_marshal_input_query_status,
1689 Show VM mice information.
1691 Each mouse is represented by a json-object, the returned value is a json-array
1694 The mouse json-object contains the following:
1696 - "name": mouse's name (json-string)
1697 - "index": mouse's index (json-int)
1698 - "current": true if this mouse is receiving events, false otherwise (json-bool)
1699 - "absolute": true if the mouse generates absolute input events (json-bool)
1703 -> { "execute": "query-mice" }
1707 "name":"QEMU Microsoft Mouse",
1713 "name":"QEMU PS/2 Mouse",
1724 .name = "query-mice",
1726 .mhandler.cmd_new = qmp_marshal_input_query_mice,
1733 Show VNC server information.
1735 Return a json-object with server information. Connected clients are returned
1736 as a json-array of json-objects.
1738 The main json-object contains the following:
1740 - "enabled": true or false (json-bool)
1741 - "host": server's IP address (json-string)
1742 - "family": address family (json-string)
1743 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1744 - "service": server's port number (json-string)
1745 - "auth": authentication method (json-string)
1746 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
1747 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
1748 "vencrypt+plain", "vencrypt+tls+none",
1749 "vencrypt+tls+plain", "vencrypt+tls+sasl",
1750 "vencrypt+tls+vnc", "vencrypt+x509+none",
1751 "vencrypt+x509+plain", "vencrypt+x509+sasl",
1752 "vencrypt+x509+vnc", "vnc"
1753 - "clients": a json-array of all connected clients
1755 Clients are described by a json-object, each one contain the following:
1757 - "host": client's IP address (json-string)
1758 - "family": address family (json-string)
1759 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1760 - "service": client's port number (json-string)
1761 - "x509_dname": TLS dname (json-string, optional)
1762 - "sasl_username": SASL username (json-string, optional)
1766 -> { "execute": "query-vnc" }
1787 .name = "query-vnc",
1789 .mhandler.cmd_new = qmp_marshal_input_query_vnc,
1796 Show SPICE server information.
1798 Return a json-object with server information. Connected clients are returned
1799 as a json-array of json-objects.
1801 The main json-object contains the following:
1803 - "enabled": true or false (json-bool)
1804 - "host": server's IP address (json-string)
1805 - "port": server's port number (json-int, optional)
1806 - "tls-port": server's port number (json-int, optional)
1807 - "auth": authentication method (json-string)
1808 - Possible values: "none", "spice"
1809 - "channels": a json-array of all active channels clients
1811 Channels are described by a json-object, each one contain the following:
1813 - "host": client's IP address (json-string)
1814 - "family": address family (json-string)
1815 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1816 - "port": client's port number (json-string)
1817 - "connection-id": spice connection id. All channels with the same id
1818 belong to the same spice session (json-int)
1819 - "channel-type": channel type. "1" is the main control channel, filter for
1820 this one if you want track spice sessions only (json-int)
1821 - "channel-id": channel id. Usually "0", might be different needed when
1822 multiple channels of the same type exist, such as multiple
1823 display channels in a multihead setup (json-int)
1824 - "tls": whevener the channel is encrypted (json-bool)
1828 -> { "execute": "query-spice" }
1841 "connection-id": 1804289383,
1842 "host": "127.0.0.1",
1850 "connection-id": 1804289383,
1851 "host": "127.0.0.1",
1855 [ ... more channels follow ... ]
1862 #if defined(CONFIG_SPICE)
1864 .name = "query-spice",
1866 .mhandler.cmd_new = qmp_marshal_input_query_spice,
1876 Return a json-object with the following information:
1878 - "name": VM's name (json-string, optional)
1882 -> { "execute": "query-name" }
1883 <- { "return": { "name": "qemu-name" } }
1888 .name = "query-name",
1890 .mhandler.cmd_new = qmp_marshal_input_query_name,
1899 Return a json-object with the following information:
1901 - "UUID": Universally Unique Identifier (json-string)
1905 -> { "execute": "query-uuid" }
1906 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
1911 .name = "query-uuid",
1913 .mhandler.cmd_new = qmp_marshal_input_query_uuid,
1922 Return a json-object. If migration is active there will be another json-object
1923 with RAM migration status and if block migration is active another one with
1924 block migration status.
1926 The main json-object contains the following:
1928 - "status": migration status (json-string)
1929 - Possible values: "active", "completed", "failed", "cancelled"
1930 - "ram": only present if "status" is "active", it is a json-object with the
1931 following RAM information (in bytes):
1932 - "transferred": amount transferred (json-int)
1933 - "remaining": amount remaining (json-int)
1934 - "total": total (json-int)
1935 - "disk": only present if "status" is "active" and it is a block migration,
1936 it is a json-object with the following disk information (in bytes):
1937 - "transferred": amount transferred (json-int)
1938 - "remaining": amount remaining (json-int)
1939 - "total": total (json-int)
1943 1. Before the first migration
1945 -> { "execute": "query-migrate" }
1948 2. Migration is done and has succeeded
1950 -> { "execute": "query-migrate" }
1951 <- { "return": { "status": "completed" } }
1953 3. Migration is done and has failed
1955 -> { "execute": "query-migrate" }
1956 <- { "return": { "status": "failed" } }
1958 4. Migration is being performed and is not a block migration:
1960 -> { "execute": "query-migrate" }
1972 5. Migration is being performed and is a block migration:
1974 -> { "execute": "query-migrate" }
1980 "remaining":1053304,
1985 "remaining":20880384,
1994 .name = "query-migrate",
1996 .mhandler.cmd_new = qmp_marshal_input_query_migrate,
2003 Show balloon information.
2005 Make an asynchronous request for balloon info. When the request completes a
2006 json-object will be returned containing the following data:
2008 - "actual": current balloon value in bytes (json-int)
2009 - "mem_swapped_in": Amount of memory swapped in bytes (json-int, optional)
2010 - "mem_swapped_out": Amount of memory swapped out in bytes (json-int, optional)
2011 - "major_page_faults": Number of major faults (json-int, optional)
2012 - "minor_page_faults": Number of minor faults (json-int, optional)
2013 - "free_mem": Total amount of free and unused memory in
2014 bytes (json-int, optional)
2015 - "total_mem": Total amount of available memory in bytes (json-int, optional)
2019 -> { "execute": "query-balloon" }
2022 "actual":1073741824,
2024 "mem_swapped_out":0,
2025 "major_page_faults":142,
2026 "minor_page_faults":239245,
2027 "free_mem":1014185984,
2028 "total_mem":1044668416
2035 .name = "query-balloon",
2037 .mhandler.cmd_new = qmp_marshal_input_query_balloon,