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 .params = "filename",
150 .help = "save screen into PPM image 'filename'",
151 .user_print = monitor_user_noop,
152 .mhandler.cmd_new = do_screen_dump,
159 Save screen into PPM image.
163 - "filename": file path (json-string)
167 -> { "execute": "screendump", "arguments": { "filename": "/tmp/image" } }
175 .mhandler.cmd_new = qmp_marshal_input_stop,
188 -> { "execute": "stop" }
196 .mhandler.cmd_new = qmp_marshal_input_cont,
209 -> { "execute": "cont" }
215 .name = "system_wakeup",
217 .mhandler.cmd_new = qmp_marshal_input_system_wakeup,
224 Wakeup guest from suspend.
230 -> { "execute": "system_wakeup" }
236 .name = "system_reset",
238 .mhandler.cmd_new = qmp_marshal_input_system_reset,
251 -> { "execute": "system_reset" }
257 .name = "system_powerdown",
259 .mhandler.cmd_new = qmp_marshal_input_system_powerdown,
266 Send system power down event.
272 -> { "execute": "system_powerdown" }
278 .name = "device_add",
279 .args_type = "device:O",
280 .params = "driver[,prop=value][,...]",
281 .help = "add device, like -device on the command line",
282 .user_print = monitor_user_noop,
283 .mhandler.cmd_new = do_device_add,
294 - "driver": the name of the new device's driver (json-string)
295 - "bus": the device's parent bus (device tree path, json-string, optional)
296 - "id": the device's ID, must be unique (json-string)
301 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
306 (1) For detailed information about this command, please refer to the
307 'docs/qdev-device-use.txt' file.
309 (2) It's possible to list device properties by running QEMU with the
310 "-device DEVICE,\?" command-line argument, where DEVICE is the device's name
315 .name = "device_del",
318 .help = "remove device",
319 .user_print = monitor_user_noop,
320 .mhandler.cmd_new = do_device_del,
331 - "id": the device's ID (json-string)
335 -> { "execute": "device_del", "arguments": { "id": "net1" } }
342 .args_type = "index:i",
343 .mhandler.cmd_new = qmp_marshal_input_cpu,
354 - "index": the CPU's index (json-int)
358 -> { "execute": "cpu", "arguments": { "index": 0 } }
361 Note: CPUs' indexes are obtained with the 'query-cpus' command.
367 .args_type = "val:l,size:i,filename:s,cpu:i?",
368 .mhandler.cmd_new = qmp_marshal_input_memsave,
375 Save to disk virtual memory dump starting at 'val' of size 'size'.
379 - "val": the starting address (json-int)
380 - "size": the memory size, in bytes (json-int)
381 - "filename": file path (json-string)
382 - "cpu": virtual CPU index (json-int, optional)
386 -> { "execute": "memsave",
387 "arguments": { "val": 10,
389 "filename": "/tmp/virtual-mem-dump" } }
396 .args_type = "val:l,size:i,filename:s",
397 .mhandler.cmd_new = qmp_marshal_input_pmemsave,
404 Save to disk physical memory dump starting at 'val' of size 'size'.
408 - "val": the starting address (json-int)
409 - "size": the memory size, in bytes (json-int)
410 - "filename": file path (json-string)
414 -> { "execute": "pmemsave",
415 "arguments": { "val": 10,
417 "filename": "/tmp/physical-mem-dump" } }
423 .name = "inject-nmi",
425 .mhandler.cmd_new = qmp_marshal_input_inject_nmi,
432 Inject an NMI on guest's CPUs.
438 -> { "execute": "inject-nmi" }
441 Note: inject-nmi is only supported for x86 guest currently, it will
442 returns "Unsupported" error for non-x86 guest.
448 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
449 .mhandler.cmd_new = qmp_marshal_input_migrate,
460 - "blk": block migration, full disk copy (json-bool, optional)
461 - "inc": incremental disk copy (json-bool, optional)
462 - "uri": Destination URI (json-string)
466 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
471 (1) The 'query-migrate' command should be used to check migration's progress
472 and final result (this information is provided by the 'status' member)
473 (2) All boolean arguments default to false
474 (3) The user Monitor's "detach" argument is invalid in QMP and should not
480 .name = "migrate_cancel",
482 .mhandler.cmd_new = qmp_marshal_input_migrate_cancel,
489 Cancel the current migration.
495 -> { "execute": "migrate_cancel" }
501 .name = "migrate_set_speed",
502 .args_type = "value:o",
503 .mhandler.cmd_new = qmp_marshal_input_migrate_set_speed,
510 Set maximum speed for migrations.
514 - "value": maximum speed, in bytes per second (json-int)
518 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
524 .name = "migrate_set_downtime",
525 .args_type = "value:T",
526 .mhandler.cmd_new = qmp_marshal_input_migrate_set_downtime,
533 Set maximum tolerated downtime (in seconds) for migrations.
537 - "value": maximum downtime (json-number)
541 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
547 .name = "client_migrate_info",
548 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
549 .params = "protocol hostname port tls-port cert-subject",
550 .help = "send migration info to spice/vnc client",
551 .user_print = monitor_user_noop,
552 .mhandler.cmd_async = client_migrate_info,
553 .flags = MONITOR_CMD_ASYNC,
560 Set the spice/vnc connection info for the migration target. The spice/vnc
561 server will ask the spice/vnc client to automatically reconnect using the
562 new parameters (if specified) once the vm migration finished successfully.
566 - "protocol": protocol: "spice" or "vnc" (json-string)
567 - "hostname": migration target hostname (json-string)
568 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
569 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
570 - "cert-subject": server certificate subject (json-string, optional)
574 -> { "execute": "client_migrate_info",
575 "arguments": { "protocol": "spice",
576 "hostname": "virt42.lab.kraxel.org",
583 .name = "netdev_add",
584 .args_type = "netdev:O",
585 .params = "[user|tap|socket],id=str[,prop=value][,...]",
586 .help = "add host network device",
587 .user_print = monitor_user_noop,
588 .mhandler.cmd_new = do_netdev_add,
595 Add host network device.
599 - "type": the device type, "tap", "user", ... (json-string)
600 - "id": the device's ID, must be unique (json-string)
605 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
608 Note: The supported device options are the same ones supported by the '-net'
609 command-line argument, which are listed in the '-help' output or QEMU's
615 .name = "netdev_del",
618 .help = "remove host network device",
619 .user_print = monitor_user_noop,
620 .mhandler.cmd_new = do_netdev_del,
627 Remove host network device.
631 - "id": the device's ID, must be unique (json-string)
635 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
642 .name = "block_resize",
643 .args_type = "device:B,size:o",
644 .mhandler.cmd_new = qmp_marshal_input_block_resize,
651 Resize a block image while a guest is running.
655 - "device": the device's ID, must be unique (json-string)
660 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
666 .name = "block_stream",
667 .args_type = "device:B,base:s?",
668 .mhandler.cmd_new = qmp_marshal_input_block_stream,
672 .name = "block_job_set_speed",
673 .args_type = "device:B,value:o",
674 .mhandler.cmd_new = qmp_marshal_input_block_job_set_speed,
678 .name = "block_job_cancel",
679 .args_type = "device:B",
680 .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
683 .name = "transaction",
684 .args_type = "actions:O",
685 .mhandler.cmd_new = qmp_marshal_input_transaction,
692 Atomically operate on one or more block devices. The only supported
693 operation for now is snapshotting. If there is any failure performing
694 any of the operations, all snapshots for the group are abandoned, and
695 the original disks pre-snapshot attempt are used.
697 A list of dictionaries is accepted, that contains the actions to be performed.
698 For snapshots this is the device, the file to use for the new snapshot,
699 and the format. The default format, if not specified, is qcow2.
701 Each new snapshot defaults to being created by QEMU (wiping any
702 contents if the file already exists), but it is also possible to reuse
703 an externally-created file. In the latter case, you should ensure that
704 the new image file has the same contents as the current one; QEMU cannot
705 perform any meaningful check. Typically this is achieved by using the
706 current image file as the backing file for the new image.
711 - "type": the operation to perform. The only supported
712 value is "blockdev-snapshot-sync". (json-string)
713 - "data": a dictionary. The contents depend on the value
714 of "type". When "type" is "blockdev-snapshot-sync":
715 - "device": device name to snapshot (json-string)
716 - "snapshot-file": name of new image file (json-string)
717 - "format": format of new image (json-string, optional)
718 - "mode": whether and how QEMU should create the snapshot file
719 (NewImageMode, optional, default "absolute-paths")
723 -> { "execute": "transaction",
724 "arguments": { "actions": [
725 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd0",
726 "snapshot-file": "/some/place/my-image",
727 "format": "qcow2" } },
728 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd1",
729 "snapshot-file": "/some/place/my-image2",
731 "format": "qcow2" } } ] } }
737 .name = "blockdev-snapshot-sync",
738 .args_type = "device:B,snapshot-file:s,format:s?",
739 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
743 blockdev-snapshot-sync
744 ----------------------
746 Synchronous snapshot of a block device. snapshot-file specifies the
747 target of the new image. If the file exists, or if it is a device, the
748 snapshot will be created in the existing file/device. If does not
749 exist, a new file will be created. format specifies the format of the
750 snapshot image, default is qcow2.
754 - "device": device name to snapshot (json-string)
755 - "snapshot-file": name of new image file (json-string)
756 - "mode": whether and how QEMU should create the snapshot file
757 (NewImageMode, optional, default "absolute-paths")
758 - "format": format of new image (json-string, optional)
762 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
764 "/some/place/my-image",
765 "format": "qcow2" } }
772 .args_type = "value:M",
773 .mhandler.cmd_new = qmp_marshal_input_balloon,
780 Request VM to change its memory allocation (in bytes).
784 - "value": New memory allocation (json-int)
788 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
795 .args_type = "name:s,up:b",
796 .mhandler.cmd_new = qmp_marshal_input_set_link,
803 Change the link status of a network adapter.
807 - "name": network device name (json-string)
808 - "up": status is up (json-bool)
812 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
819 .args_type = "fdname:s",
820 .params = "getfd name",
821 .help = "receive a file descriptor via SCM rights and assign it a name",
822 .user_print = monitor_user_noop,
823 .mhandler.cmd_new = do_getfd,
830 Receive a file descriptor via SCM rights and assign it a name.
834 - "fdname": file descriptor name (json-string)
838 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
845 .args_type = "fdname:s",
846 .params = "closefd name",
847 .help = "close a file descriptor previously passed via SCM rights",
848 .user_print = monitor_user_noop,
849 .mhandler.cmd_new = do_closefd,
856 Close a file descriptor previously passed via SCM rights.
860 - "fdname": file descriptor name (json-string)
864 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
870 .name = "block_passwd",
871 .args_type = "device:B,password:s",
872 .mhandler.cmd_new = qmp_marshal_input_block_passwd,
879 Set the password of encrypted block devices.
883 - "device": device name (json-string)
884 - "password": password (json-string)
888 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
889 "password": "12345" } }
895 .name = "block_set_io_throttle",
896 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l",
897 .mhandler.cmd_new = qmp_marshal_input_block_set_io_throttle,
901 block_set_io_throttle
904 Change I/O throttle limits for a block drive.
908 - "device": device name (json-string)
909 - "bps": total throughput limit in bytes per second(json-int)
910 - "bps_rd": read throughput limit in bytes per second(json-int)
911 - "bps_wr": read throughput limit in bytes per second(json-int)
912 - "iops": total I/O operations per second(json-int)
913 - "iops_rd": read I/O operations per second(json-int)
914 - "iops_wr": write I/O operations per second(json-int)
918 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
930 .name = "set_password",
931 .args_type = "protocol:s,password:s,connected:s?",
932 .mhandler.cmd_new = qmp_marshal_input_set_password,
939 Set the password for vnc/spice protocols.
943 - "protocol": protocol name (json-string)
944 - "password": password (json-string)
945 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
949 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
950 "password": "secret" } }
956 .name = "expire_password",
957 .args_type = "protocol:s,time:s",
958 .mhandler.cmd_new = qmp_marshal_input_expire_password,
965 Set the password expire time for vnc/spice protocols.
969 - "protocol": protocol name (json-string)
970 - "time": [ now | never | +secs | secs ] (json-string)
974 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
981 .name = "add_client",
982 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
983 .params = "protocol fdname skipauth tls",
984 .help = "add a graphics client",
985 .user_print = monitor_user_noop,
986 .mhandler.cmd_new = add_graphics_client,
993 Add a graphics client
997 - "protocol": protocol name (json-string)
998 - "fdname": file descriptor name (json-string)
999 - "skipauth": whether to skip authentication (json-bool, optional)
1000 - "tls": whether to perform TLS (json-bool, optional)
1004 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
1005 "fdname": "myclient" } }
1010 .name = "qmp_capabilities",
1013 .help = "enable QMP capabilities",
1014 .user_print = monitor_user_noop,
1015 .mhandler.cmd_new = do_qmp_capabilities,
1022 Enable QMP capabilities.
1028 -> { "execute": "qmp_capabilities" }
1031 Note: This command must be issued before issuing any other command.
1036 .name = "human-monitor-command",
1037 .args_type = "command-line:s,cpu-index:i?",
1038 .mhandler.cmd_new = qmp_marshal_input_human_monitor_command,
1042 human-monitor-command
1043 ---------------------
1045 Execute a Human Monitor command.
1049 - command-line: the command name and its arguments, just like the
1050 Human Monitor's shell (json-string)
1051 - cpu-index: select the CPU number to be used by commands which access CPU
1052 data, like 'info registers'. The Monitor selects CPU 0 if this
1053 argument is not provided (json-int, optional)
1057 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1058 <- { "return": "kvm support: enabled\r\n" }
1062 (1) The Human Monitor is NOT an stable interface, this means that command
1063 names, arguments and responses can change or be removed at ANY time.
1064 Applications that rely on long term stability guarantees should NOT
1069 o This command is stateless, this means that commands that depend
1070 on state information (such as getfd) might not work
1072 o Commands that prompt the user for data (eg. 'cont' when the block
1073 device is encrypted) don't currently work
1078 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1079 HXCOMM this! We will possibly move query commands definitions inside those
1080 HXCOMM sections, just like regular commands.
1090 Return a json-object with the following information:
1092 - "qemu": A json-object containing three integer values:
1093 - "major": QEMU's major version (json-int)
1094 - "minor": QEMU's minor version (json-int)
1095 - "micro": QEMU's micro version (json-int)
1096 - "package": package's version (json-string)
1100 -> { "execute": "query-version" }
1115 .name = "query-version",
1117 .mhandler.cmd_new = qmp_marshal_input_query_version,
1124 List QMP available commands.
1126 Each command is represented by a json-object, the returned value is a json-array
1129 Each json-object contain:
1131 - "name": command's name (json-string)
1135 -> { "execute": "query-commands" }
1139 "name":"query-balloon"
1142 "name":"system_powerdown"
1147 Note: This example has been shortened as the real response is too long.
1152 .name = "query-commands",
1154 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1161 Each device is represented by a json-object. The returned value is a json-array
1164 Each json-object contain the following:
1166 - "label": device's label (json-string)
1167 - "filename": device's file (json-string)
1171 -> { "execute": "query-chardev" }
1188 .name = "query-chardev",
1190 .mhandler.cmd_new = qmp_marshal_input_query_chardev,
1197 Show the block devices.
1199 Each block device information is stored in a json-object and the returned value
1200 is a json-array of all devices.
1202 Each json-object contain the following:
1204 - "device": device name (json-string)
1205 - "type": device type (json-string)
1206 - deprecated, retained for backward compatibility
1207 - Possible values: "unknown"
1208 - "removable": true if the device is removable, false otherwise (json-bool)
1209 - "locked": true if the device is locked, false otherwise (json-bool)
1210 - "tray-open": only present if removable, true if the device has a tray,
1211 and it is open (json-bool)
1212 - "inserted": only present if the device is inserted, it is a json-object
1213 containing the following:
1214 - "file": device file name (json-string)
1215 - "ro": true if read-only, false otherwise (json-bool)
1216 - "drv": driver format name (json-string)
1217 - Possible values: "blkdebug", "bochs", "cloop", "cow", "dmg",
1218 "file", "file", "ftp", "ftps", "host_cdrom",
1219 "host_device", "host_floppy", "http", "https",
1220 "nbd", "parallels", "qcow", "qcow2", "raw",
1221 "tftp", "vdi", "vmdk", "vpc", "vvfat"
1222 - "backing_file": backing file name (json-string, optional)
1223 - "encrypted": true if encrypted, false otherwise (json-bool)
1224 - "bps": limit total bytes per second (json-int)
1225 - "bps_rd": limit read bytes per second (json-int)
1226 - "bps_wr": limit write bytes per second (json-int)
1227 - "iops": limit total I/O operations per second (json-int)
1228 - "iops_rd": limit read operations per second (json-int)
1229 - "iops_wr": limit write operations per second (json-int)
1231 - "io-status": I/O operation status, only present if the device supports it
1232 and the VM is configured to stop on errors. It's always reset
1233 to "ok" when the "cont" command is issued (json_string, optional)
1234 - Possible values: "ok", "failed", "nospace"
1238 -> { "execute": "query-block" }
1243 "device":"ide0-hd0",
1250 "file":"disks/test.img",
1262 "device":"ide1-cd0",
1285 .name = "query-block",
1287 .mhandler.cmd_new = qmp_marshal_input_query_block,
1294 Show block device statistics.
1296 Each device statistic information is stored in a json-object and the returned
1297 value is a json-array of all devices.
1299 Each json-object contain the following:
1301 - "device": device name (json-string)
1302 - "stats": A json-object with the statistics information, it contains:
1303 - "rd_bytes": bytes read (json-int)
1304 - "wr_bytes": bytes written (json-int)
1305 - "rd_operations": read operations (json-int)
1306 - "wr_operations": write operations (json-int)
1307 - "flush_operations": cache flush operations (json-int)
1308 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
1309 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
1310 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
1311 - "wr_highest_offset": Highest offset of a sector written since the
1312 BlockDriverState has been opened (json-int)
1313 - "parent": Contains recursively the statistics of the underlying
1314 protocol (e.g. the host file for a qcow2 image). If there is
1315 no underlying protocol, this field is omitted
1316 (json-object, optional)
1320 -> { "execute": "query-blockstats" }
1324 "device":"ide0-hd0",
1327 "wr_highest_offset":3686448128,
1329 "wr_operations":751,
1330 "rd_bytes":122567168,
1331 "rd_operations":36772
1332 "wr_total_times_ns":313253456
1333 "rd_total_times_ns":3465673657
1334 "flush_total_times_ns":49653
1335 "flush_operations":61,
1339 "wr_highest_offset":2821110784,
1341 "wr_operations":692,
1342 "rd_bytes":122739200,
1343 "rd_operations":36604
1344 "flush_operations":51,
1345 "wr_total_times_ns":313253456
1346 "rd_total_times_ns":3465673657
1347 "flush_total_times_ns":49653
1351 "device":"ide1-cd0",
1353 "wr_highest_offset":0,
1358 "flush_operations":0,
1359 "wr_total_times_ns":0
1360 "rd_total_times_ns":0
1361 "flush_total_times_ns":0
1367 "wr_highest_offset":0,
1372 "flush_operations":0,
1373 "wr_total_times_ns":0
1374 "rd_total_times_ns":0
1375 "flush_total_times_ns":0
1381 "wr_highest_offset":0,
1386 "flush_operations":0,
1387 "wr_total_times_ns":0
1388 "rd_total_times_ns":0
1389 "flush_total_times_ns":0
1398 .name = "query-blockstats",
1400 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
1407 Show CPU information.
1409 Return a json-array. Each CPU is represented by a json-object, which contains:
1411 - "CPU": CPU index (json-int)
1412 - "current": true if this is the current CPU, false otherwise (json-bool)
1413 - "halted": true if the cpu is halted, false otherwise (json-bool)
1414 - Current program counter. The key's name depends on the architecture:
1415 "pc": i386/x86_64 (json-int)
1416 "nip": PPC (json-int)
1417 "pc" and "npc": sparc (json-int)
1418 "PC": mips (json-int)
1419 - "thread_id": ID of the underlying host thread (json-int)
1423 -> { "execute": "query-cpus" }
1446 .name = "query-cpus",
1448 .mhandler.cmd_new = qmp_marshal_input_query_cpus,
1455 PCI buses and devices information.
1457 The returned value is a json-array of all buses. Each bus is represented by
1458 a json-object, which has a key with a json-array of all PCI devices attached
1459 to it. Each device is represented by a json-object.
1461 The bus json-object contains the following:
1463 - "bus": bus number (json-int)
1464 - "devices": a json-array of json-objects, each json-object represents a
1467 The PCI device json-object contains the following:
1469 - "bus": identical to the parent's bus number (json-int)
1470 - "slot": slot number (json-int)
1471 - "function": function number (json-int)
1472 - "class_info": a json-object containing:
1473 - "desc": device class description (json-string, optional)
1474 - "class": device class number (json-int)
1475 - "id": a json-object containing:
1476 - "device": device ID (json-int)
1477 - "vendor": vendor ID (json-int)
1478 - "irq": device's IRQ if assigned (json-int, optional)
1479 - "qdev_id": qdev id string (json-string)
1480 - "pci_bridge": It's a json-object, only present if this device is a
1481 PCI bridge, contains:
1482 - "bus": bus number (json-int)
1483 - "secondary": secondary bus number (json-int)
1484 - "subordinate": subordinate bus number (json-int)
1485 - "io_range": I/O memory range information, a json-object with the
1487 - "base": base address, in bytes (json-int)
1488 - "limit": limit address, in bytes (json-int)
1489 - "memory_range": memory range information, a json-object with the
1491 - "base": base address, in bytes (json-int)
1492 - "limit": limit address, in bytes (json-int)
1493 - "prefetchable_range": Prefetchable memory range information, a
1494 json-object with the following members:
1495 - "base": base address, in bytes (json-int)
1496 - "limit": limit address, in bytes (json-int)
1497 - "devices": a json-array of PCI devices if there's any attached, each
1498 each element is represented by a json-object, which contains
1499 the same members of the 'PCI device json-object' described
1501 - "regions": a json-array of json-objects, each json-object represents a
1502 memory region of this device
1504 The memory range json-object contains the following:
1506 - "base": base memory address (json-int)
1507 - "limit": limit value (json-int)
1509 The region json-object can be an I/O region or a memory region, an I/O region
1510 json-object contains the following:
1512 - "type": "io" (json-string, fixed)
1513 - "bar": BAR number (json-int)
1514 - "address": memory address (json-int)
1515 - "size": memory size (json-int)
1517 A memory region json-object contains the following:
1519 - "type": "memory" (json-string, fixed)
1520 - "bar": BAR number (json-int)
1521 - "address": memory address (json-int)
1522 - "size": memory size (json-int)
1523 - "mem_type_64": true or false (json-bool)
1524 - "prefetch": true or false (json-bool)
1528 -> { "execute": "query-pci" }
1540 "desc":"Host bridge"
1574 "desc":"IDE controller"
1596 "desc":"VGA controller"
1606 "mem_type_64":false,
1609 "address":4026531840,
1614 "mem_type_64":false,
1617 "address":4060086272,
1622 "mem_type_64":false,
1637 "desc":"RAM controller"
1658 Note: This example has been shortened as the real response is too long.
1663 .name = "query-pci",
1665 .mhandler.cmd_new = qmp_marshal_input_query_pci,
1672 Show KVM information.
1674 Return a json-object with the following information:
1676 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
1677 - "present": true if QEMU has KVM support, false otherwise (json-bool)
1681 -> { "execute": "query-kvm" }
1682 <- { "return": { "enabled": true, "present": true } }
1687 .name = "query-kvm",
1689 .mhandler.cmd_new = qmp_marshal_input_query_kvm,
1696 Return a json-object with the following information:
1698 - "running": true if the VM is running, or false if it is paused (json-bool)
1699 - "singlestep": true if the VM is in single step mode,
1700 false otherwise (json-bool)
1701 - "status": one of the following values (json-string)
1702 "debug" - QEMU is running on a debugger
1703 "inmigrate" - guest is paused waiting for an incoming migration
1704 "internal-error" - An internal error that prevents further guest
1705 execution has occurred
1706 "io-error" - the last IOP has failed and the device is configured
1707 to pause on I/O errors
1708 "paused" - guest has been paused via the 'stop' command
1709 "postmigrate" - guest is paused following a successful 'migrate'
1710 "prelaunch" - QEMU was started with -S and guest has not started
1711 "finish-migrate" - guest is paused to finish the migration process
1712 "restore-vm" - guest is paused to restore VM state
1713 "running" - guest is actively running
1714 "save-vm" - guest is paused to save the VM state
1715 "shutdown" - guest is shut down (and -no-shutdown is in use)
1716 "watchdog" - the watchdog action is configured to pause and
1721 -> { "execute": "query-status" }
1722 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
1727 .name = "query-status",
1729 .mhandler.cmd_new = qmp_marshal_input_query_status,
1736 Show VM mice information.
1738 Each mouse is represented by a json-object, the returned value is a json-array
1741 The mouse json-object contains the following:
1743 - "name": mouse's name (json-string)
1744 - "index": mouse's index (json-int)
1745 - "current": true if this mouse is receiving events, false otherwise (json-bool)
1746 - "absolute": true if the mouse generates absolute input events (json-bool)
1750 -> { "execute": "query-mice" }
1754 "name":"QEMU Microsoft Mouse",
1760 "name":"QEMU PS/2 Mouse",
1771 .name = "query-mice",
1773 .mhandler.cmd_new = qmp_marshal_input_query_mice,
1780 Show VNC server information.
1782 Return a json-object with server information. Connected clients are returned
1783 as a json-array of json-objects.
1785 The main json-object contains the following:
1787 - "enabled": true or false (json-bool)
1788 - "host": server's IP address (json-string)
1789 - "family": address family (json-string)
1790 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1791 - "service": server's port number (json-string)
1792 - "auth": authentication method (json-string)
1793 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
1794 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
1795 "vencrypt+plain", "vencrypt+tls+none",
1796 "vencrypt+tls+plain", "vencrypt+tls+sasl",
1797 "vencrypt+tls+vnc", "vencrypt+x509+none",
1798 "vencrypt+x509+plain", "vencrypt+x509+sasl",
1799 "vencrypt+x509+vnc", "vnc"
1800 - "clients": a json-array of all connected clients
1802 Clients are described by a json-object, each one contain the following:
1804 - "host": client's IP address (json-string)
1805 - "family": address family (json-string)
1806 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1807 - "service": client's port number (json-string)
1808 - "x509_dname": TLS dname (json-string, optional)
1809 - "sasl_username": SASL username (json-string, optional)
1813 -> { "execute": "query-vnc" }
1834 .name = "query-vnc",
1836 .mhandler.cmd_new = qmp_marshal_input_query_vnc,
1843 Show SPICE server information.
1845 Return a json-object with server information. Connected clients are returned
1846 as a json-array of json-objects.
1848 The main json-object contains the following:
1850 - "enabled": true or false (json-bool)
1851 - "host": server's IP address (json-string)
1852 - "port": server's port number (json-int, optional)
1853 - "tls-port": server's port number (json-int, optional)
1854 - "auth": authentication method (json-string)
1855 - Possible values: "none", "spice"
1856 - "channels": a json-array of all active channels clients
1858 Channels are described by a json-object, each one contain the following:
1860 - "host": client's IP address (json-string)
1861 - "family": address family (json-string)
1862 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1863 - "port": client's port number (json-string)
1864 - "connection-id": spice connection id. All channels with the same id
1865 belong to the same spice session (json-int)
1866 - "channel-type": channel type. "1" is the main control channel, filter for
1867 this one if you want track spice sessions only (json-int)
1868 - "channel-id": channel id. Usually "0", might be different needed when
1869 multiple channels of the same type exist, such as multiple
1870 display channels in a multihead setup (json-int)
1871 - "tls": whevener the channel is encrypted (json-bool)
1875 -> { "execute": "query-spice" }
1888 "connection-id": 1804289383,
1889 "host": "127.0.0.1",
1897 "connection-id": 1804289383,
1898 "host": "127.0.0.1",
1902 [ ... more channels follow ... ]
1909 #if defined(CONFIG_SPICE)
1911 .name = "query-spice",
1913 .mhandler.cmd_new = qmp_marshal_input_query_spice,
1923 Return a json-object with the following information:
1925 - "name": VM's name (json-string, optional)
1929 -> { "execute": "query-name" }
1930 <- { "return": { "name": "qemu-name" } }
1935 .name = "query-name",
1937 .mhandler.cmd_new = qmp_marshal_input_query_name,
1946 Return a json-object with the following information:
1948 - "UUID": Universally Unique Identifier (json-string)
1952 -> { "execute": "query-uuid" }
1953 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
1958 .name = "query-uuid",
1960 .mhandler.cmd_new = qmp_marshal_input_query_uuid,
1969 Return a json-object. If migration is active there will be another json-object
1970 with RAM migration status and if block migration is active another one with
1971 block migration status.
1973 The main json-object contains the following:
1975 - "status": migration status (json-string)
1976 - Possible values: "active", "completed", "failed", "cancelled"
1977 - "ram": only present if "status" is "active", it is a json-object with the
1978 following RAM information (in bytes):
1979 - "transferred": amount transferred (json-int)
1980 - "remaining": amount remaining (json-int)
1981 - "total": total (json-int)
1982 - "disk": only present if "status" is "active" and it is a block migration,
1983 it is a json-object with the following disk information (in bytes):
1984 - "transferred": amount transferred (json-int)
1985 - "remaining": amount remaining (json-int)
1986 - "total": total (json-int)
1990 1. Before the first migration
1992 -> { "execute": "query-migrate" }
1995 2. Migration is done and has succeeded
1997 -> { "execute": "query-migrate" }
1998 <- { "return": { "status": "completed" } }
2000 3. Migration is done and has failed
2002 -> { "execute": "query-migrate" }
2003 <- { "return": { "status": "failed" } }
2005 4. Migration is being performed and is not a block migration:
2007 -> { "execute": "query-migrate" }
2019 5. Migration is being performed and is a block migration:
2021 -> { "execute": "query-migrate" }
2027 "remaining":1053304,
2032 "remaining":20880384,
2041 .name = "query-migrate",
2043 .mhandler.cmd_new = qmp_marshal_input_query_migrate,
2050 Show balloon information.
2052 Make an asynchronous request for balloon info. When the request completes a
2053 json-object will be returned containing the following data:
2055 - "actual": current balloon value in bytes (json-int)
2056 - "mem_swapped_in": Amount of memory swapped in bytes (json-int, optional)
2057 - "mem_swapped_out": Amount of memory swapped out in bytes (json-int, optional)
2058 - "major_page_faults": Number of major faults (json-int, optional)
2059 - "minor_page_faults": Number of minor faults (json-int, optional)
2060 - "free_mem": Total amount of free and unused memory in
2061 bytes (json-int, optional)
2062 - "total_mem": Total amount of available memory in bytes (json-int, optional)
2066 -> { "execute": "query-balloon" }
2069 "actual":1073741824,
2071 "mem_swapped_out":0,
2072 "major_page_faults":142,
2073 "minor_page_faults":239245,
2074 "free_mem":1014185984,
2075 "total_mem":1044668416
2082 .name = "query-balloon",
2084 .mhandler.cmd_new = qmp_marshal_input_query_balloon,
2088 .name = "query-block-jobs",
2090 .mhandler.cmd_new = qmp_marshal_input_query_block_jobs,
2095 .args_type = "path:s",
2096 .mhandler.cmd_new = qmp_marshal_input_qom_list,
2101 .args_type = "path:s,property:s,opts:O",
2102 .mhandler.cmd_new = qmp_qom_set,
2107 .args_type = "path:s,property:s",
2108 .mhandler.cmd_new = qmp_qom_get,
2112 .name = "change-vnc-password",
2113 .args_type = "password:s",
2114 .mhandler.cmd_new = qmp_marshal_input_change_vnc_password,
2117 .name = "qom-list-types",
2118 .args_type = "implements:s?,abstract:b?",
2119 .mhandler.cmd_new = qmp_marshal_input_qom_list_types,