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 .params = "[-d] [-b] [-i] uri",
450 .help = "migrate to URI (using -d to not wait for completion)"
451 "\n\t\t\t -b for migration without shared storage with"
452 " full copy of disk\n\t\t\t -i for migration without "
453 "shared storage with incremental copy of disk "
454 "(base image shared between src and destination)",
455 .user_print = monitor_user_noop,
456 .mhandler.cmd_new = do_migrate,
467 - "blk": block migration, full disk copy (json-bool, optional)
468 - "inc": incremental disk copy (json-bool, optional)
469 - "uri": Destination URI (json-string)
473 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
478 (1) The 'query
-migrate
' command should be used to check migration's progress
479 and final
result (this information is provided by the
'status' member
)
480 (2) All boolean arguments
default to
false
481 (3) The user Monitor
's "detach" argument is invalid in QMP and should not
487 .name = "migrate_cancel",
489 .mhandler.cmd_new = qmp_marshal_input_migrate_cancel,
496 Cancel the current migration.
502 -> { "execute": "migrate_cancel" }
508 .name = "migrate_set_speed",
509 .args_type = "value:o",
510 .mhandler.cmd_new = qmp_marshal_input_migrate_set_speed,
517 Set maximum speed for migrations.
521 - "value": maximum speed, in bytes per second (json-int)
525 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
531 .name = "migrate_set_downtime",
532 .args_type = "value:T",
533 .mhandler.cmd_new = qmp_marshal_input_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 .mhandler
.cmd_new
= qmp_marshal_input_block_resize
,
658 Resize a block image
while a guest is running
.
662 - "device": the device
's ID, must be unique (json-string)
667 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
673 .name = "block_stream",
674 .args_type = "device:B,base:s?",
675 .mhandler.cmd_new = qmp_marshal_input_block_stream,
679 .name = "block_job_set_speed",
680 .args_type = "device:B,value:o",
681 .mhandler.cmd_new = qmp_marshal_input_block_job_set_speed,
685 .name = "block_job_cancel",
686 .args_type = "device:B",
687 .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
690 .name = "transaction",
691 .args_type = "actions:O",
692 .mhandler.cmd_new = qmp_marshal_input_transaction,
699 Atomically operate on one or more block devices. The only supported
700 operation for now is snapshotting. If there is any failure performing
701 any of the operations, all snapshots for the group are abandoned, and
702 the original disks pre-snapshot attempt are used.
704 A list of dictionaries is accepted, that contains the actions to be performed.
705 For snapshots this is the device, the file to use for the new snapshot,
706 and the format. The default format, if not specified, is qcow2.
708 Each new snapshot defaults to being created by QEMU (wiping any
709 contents if the file already exists), but it is also possible to reuse
710 an externally-created file. In the latter case, you should ensure that
711 the new image file has the same contents as the current one; QEMU cannot
712 perform any meaningful check. Typically this is achieved by using the
713 current image file as the backing file for the new image.
718 - "type": the operation to perform. The only supported
719 value is "blockdev-snapshot-sync". (json-string)
720 - "data": a dictionary. The contents depend on the value
721 of "type". When "type" is "blockdev-snapshot-sync":
722 - "device": device name to snapshot (json-string)
723 - "snapshot-file": name of new image file (json-string)
724 - "format": format of new image (json-string, optional)
725 - "mode": whether and how QEMU should create the snapshot file
726 (NewImageMode, optional, default "absolute-paths")
730 -> { "execute": "transaction",
731 "arguments": { "actions": [
732 { 'type
': 'blockdev
-snapshot
-sync
', 'data
' : { "device": "ide-hd0",
733 "snapshot-file": "/some/place/my-image",
734 "format": "qcow2" } },
735 { 'type
': 'blockdev
-snapshot
-sync
', 'data
' : { "device": "ide-hd1",
736 "snapshot-file": "/some/place/my-image2",
738 "format": "qcow2" } } ] } }
744 .name = "blockdev-snapshot-sync",
745 .args_type = "device:B,snapshot-file:s,format:s?",
746 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
750 blockdev-snapshot-sync
751 ----------------------
753 Synchronous snapshot of a block device. snapshot-file specifies the
754 target of the new image. If the file exists, or if it is a device, the
755 snapshot will be created in the existing file/device. If does not
756 exist, a new file will be created. format specifies the format of the
757 snapshot image, default is qcow2.
761 - "device": device name to snapshot (json-string)
762 - "snapshot-file": name of new image file (json-string)
763 - "mode": whether and how QEMU should create the snapshot file
764 (NewImageMode, optional, default "absolute-paths")
765 - "format": format of new image (json-string, optional)
769 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
771 "/some/place/my-image",
772 "format": "qcow2" } }
779 .args_type = "value:M",
780 .mhandler.cmd_new = qmp_marshal_input_balloon,
787 Request VM to change its memory allocation (in bytes).
791 - "value": New memory allocation (json-int)
795 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
802 .args_type = "name:s,up:b",
803 .mhandler.cmd_new = qmp_marshal_input_set_link,
810 Change the link status of a network adapter.
814 - "name": network device name (json-string)
815 - "up": status is up (json-bool)
819 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
826 .args_type = "fdname:s",
827 .params = "getfd name",
828 .help = "receive a file descriptor via SCM rights and assign it a name",
829 .user_print = monitor_user_noop,
830 .mhandler.cmd_new = do_getfd,
837 Receive a file descriptor via SCM rights and assign it a name.
841 - "fdname": file descriptor name (json-string)
845 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
852 .args_type = "fdname:s",
853 .params = "closefd name",
854 .help = "close a file descriptor previously passed via SCM rights",
855 .user_print = monitor_user_noop,
856 .mhandler.cmd_new = do_closefd,
863 Close a file descriptor previously passed via SCM rights.
867 - "fdname": file descriptor name (json-string)
871 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
877 .name = "block_passwd",
878 .args_type = "device:B,password:s",
879 .mhandler.cmd_new = qmp_marshal_input_block_passwd,
886 Set the password of encrypted block devices.
890 - "device": device name (json-string)
891 - "password": password (json-string)
895 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
896 "password": "12345" } }
902 .name = "block_set_io_throttle",
903 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l",
904 .mhandler.cmd_new = qmp_marshal_input_block_set_io_throttle,
908 block_set_io_throttle
911 Change I/O throttle limits for a block drive.
915 - "device": device name (json-string)
916 - "bps": total throughput limit in bytes per second(json-int)
917 - "bps_rd": read throughput limit in bytes per second(json-int)
918 - "bps_wr": read throughput limit in bytes per second(json-int)
919 - "iops": total I/O operations per second(json-int)
920 - "iops_rd": read I/O operations per second(json-int)
921 - "iops_wr": write I/O operations per second(json-int)
925 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
937 .name = "set_password",
938 .args_type = "protocol:s,password:s,connected:s?",
939 .mhandler.cmd_new = qmp_marshal_input_set_password,
946 Set the password for vnc/spice protocols.
950 - "protocol": protocol name (json-string)
951 - "password": password (json-string)
952 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
956 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
957 "password": "secret" } }
963 .name = "expire_password",
964 .args_type = "protocol:s,time:s",
965 .mhandler.cmd_new = qmp_marshal_input_expire_password,
972 Set the password expire time for vnc/spice protocols.
976 - "protocol": protocol name (json-string)
977 - "time": [ now | never | +secs | secs ] (json-string)
981 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
988 .name = "add_client",
989 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
990 .params = "protocol fdname skipauth tls",
991 .help = "add a graphics client",
992 .user_print = monitor_user_noop,
993 .mhandler.cmd_new = add_graphics_client,
1000 Add a graphics client
1004 - "protocol": protocol name (json-string)
1005 - "fdname": file descriptor name (json-string)
1006 - "skipauth": whether to skip authentication (json-bool, optional)
1007 - "tls": whether to perform TLS (json-bool, optional)
1011 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
1012 "fdname": "myclient" } }
1017 .name = "qmp_capabilities",
1020 .help = "enable QMP capabilities",
1021 .user_print = monitor_user_noop,
1022 .mhandler.cmd_new = do_qmp_capabilities,
1029 Enable QMP capabilities.
1035 -> { "execute": "qmp_capabilities" }
1038 Note: This command must be issued before issuing any other command.
1043 .name = "human-monitor-command",
1044 .args_type = "command-line:s,cpu-index:i?",
1045 .mhandler.cmd_new = qmp_marshal_input_human_monitor_command,
1049 human-monitor-command
1050 ---------------------
1052 Execute a Human Monitor command.
1056 - command-line: the command name and its arguments, just like the
1057 Human Monitor's
shell (json
-string
)
1058 - cpu
-index
: select the CPU number to be used by commands which access CPU
1059 data
, like
'info registers'. The Monitor selects CPU
0 if this
1060 argument is not
provided (json
-int
, optional
)
1064 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1065 <- { "return": "kvm support: enabled\r\n" }
1069 (1) The Human Monitor is NOT an stable
interface, this means that command
1070 names
, arguments and responses can change or be removed at ANY time
.
1071 Applications that rely on long term stability guarantees should NOT
1076 o This command is stateless
, this means that commands that depend
1077 on state
information (such as getfd
) might not work
1079 o Commands that prompt the user
for data (eg
. 'cont' when the block
1080 device is encrypted
) don
't currently work
1085 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1086 HXCOMM this! We will possibly move query commands definitions inside those
1087 HXCOMM sections, just like regular commands.
1097 Return a json-object with the following information:
1099 - "qemu": A json-object containing three integer values:
1100 - "major": QEMU's major
version (json
-int
)
1101 - "minor": QEMU
's minor version (json-int)
1102 - "micro": QEMU's micro
version (json
-int
)
1103 - "package": package's version (json-string)
1107 -> { "execute": "query-version" }
1122 .name = "query-version",
1124 .mhandler.cmd_new = qmp_marshal_input_query_version,
1131 List QMP available commands.
1133 Each command is represented by a json-object, the returned value is a json-array
1136 Each json-object contain:
1138 - "name": command's
name (json
-string
)
1142 -> { "execute": "query-commands" }
1146 "name":"query-balloon"
1149 "name":"system_powerdown"
1154 Note
: This example has been shortened as the real response is too long
.
1159 .name
= "query-commands",
1161 .mhandler
.cmd_new
= qmp_marshal_input_query_commands
,
1168 Each device is represented by a json
-object
. The returned value is a json
-array
1171 Each json
-object contain the following
:
1173 - "label": device
's label (json-string)
1174 - "filename": device's
file (json
-string
)
1178 -> { "execute": "query-chardev" }
1195 .name
= "query-chardev",
1197 .mhandler
.cmd_new
= qmp_marshal_input_query_chardev
,
1204 Show the block devices
.
1206 Each block device information is stored
in a json
-object and the returned value
1207 is a json
-array of all devices
.
1209 Each json
-object contain the following
:
1211 - "device": device
name (json
-string
)
1212 - "type": device
type (json
-string
)
1213 - deprecated
, retained
for backward compatibility
1214 - Possible values
: "unknown"
1215 - "removable": true if the device is removable
, false otherwise (json
-bool
)
1216 - "locked": true if the device is locked
, false otherwise (json
-bool
)
1217 - "tray-open": only present
if removable
, true if the device has a tray
,
1218 and it is
open (json
-bool
)
1219 - "inserted": only present
if the device is inserted
, it is a json
-object
1220 containing the following
:
1221 - "file": device file
name (json
-string
)
1222 - "ro": true if read
-only
, false otherwise (json
-bool
)
1223 - "drv": driver format
name (json
-string
)
1224 - Possible values
: "blkdebug", "bochs", "cloop", "cow", "dmg",
1225 "file", "file", "ftp", "ftps", "host_cdrom",
1226 "host_device", "host_floppy", "http", "https",
1227 "nbd", "parallels", "qcow", "qcow2", "raw",
1228 "tftp", "vdi", "vmdk", "vpc", "vvfat"
1229 - "backing_file": backing file
name (json
-string
, optional
)
1230 - "encrypted": true if encrypted
, false otherwise (json
-bool
)
1231 - "bps": limit total bytes per
second (json
-int
)
1232 - "bps_rd": limit read bytes per
second (json
-int
)
1233 - "bps_wr": limit write bytes per
second (json
-int
)
1234 - "iops": limit total I
/O operations per
second (json
-int
)
1235 - "iops_rd": limit read operations per
second (json
-int
)
1236 - "iops_wr": limit write operations per
second (json
-int
)
1238 - "io-status": I
/O operation status
, only present
if the device supports it
1239 and the VM is configured to stop on errors
. It
's always reset
1240 to "ok" when the "cont" command is issued (json_string, optional)
1241 - Possible values: "ok", "failed", "nospace"
1245 -> { "execute": "query-block" }
1250 "device":"ide0-hd0",
1257 "file":"disks/test.img",
1269 "device":"ide1-cd0",
1292 .name = "query-block",
1294 .mhandler.cmd_new = qmp_marshal_input_query_block,
1301 Show block device statistics.
1303 Each device statistic information is stored in a json-object and the returned
1304 value is a json-array of all devices.
1306 Each json-object contain the following:
1308 - "device": device name (json-string)
1309 - "stats": A json-object with the statistics information, it contains:
1310 - "rd_bytes": bytes read (json-int)
1311 - "wr_bytes": bytes written (json-int)
1312 - "rd_operations": read operations (json-int)
1313 - "wr_operations": write operations (json-int)
1314 - "flush_operations": cache flush operations (json-int)
1315 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
1316 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
1317 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
1318 - "wr_highest_offset": Highest offset of a sector written since the
1319 BlockDriverState has been opened (json-int)
1320 - "parent": Contains recursively the statistics of the underlying
1321 protocol (e.g. the host file for a qcow2 image). If there is
1322 no underlying protocol, this field is omitted
1323 (json-object, optional)
1327 -> { "execute": "query-blockstats" }
1331 "device":"ide0-hd0",
1334 "wr_highest_offset":3686448128,
1336 "wr_operations":751,
1337 "rd_bytes":122567168,
1338 "rd_operations":36772
1339 "wr_total_times_ns":313253456
1340 "rd_total_times_ns":3465673657
1341 "flush_total_times_ns":49653
1342 "flush_operations":61,
1346 "wr_highest_offset":2821110784,
1348 "wr_operations":692,
1349 "rd_bytes":122739200,
1350 "rd_operations":36604
1351 "flush_operations":51,
1352 "wr_total_times_ns":313253456
1353 "rd_total_times_ns":3465673657
1354 "flush_total_times_ns":49653
1358 "device":"ide1-cd0",
1360 "wr_highest_offset":0,
1365 "flush_operations":0,
1366 "wr_total_times_ns":0
1367 "rd_total_times_ns":0
1368 "flush_total_times_ns":0
1374 "wr_highest_offset":0,
1379 "flush_operations":0,
1380 "wr_total_times_ns":0
1381 "rd_total_times_ns":0
1382 "flush_total_times_ns":0
1388 "wr_highest_offset":0,
1393 "flush_operations":0,
1394 "wr_total_times_ns":0
1395 "rd_total_times_ns":0
1396 "flush_total_times_ns":0
1405 .name = "query-blockstats",
1407 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
1414 Show CPU information.
1416 Return a json-array. Each CPU is represented by a json-object, which contains:
1418 - "CPU": CPU index (json-int)
1419 - "current": true if this is the current CPU, false otherwise (json-bool)
1420 - "halted": true if the cpu is halted, false otherwise (json-bool)
1421 - Current program counter. The key's name depends on the architecture
:
1422 "pc": i386
/x86_64 (json
-int
)
1423 "nip": PPC (json
-int
)
1424 "pc" and
"npc": sparc (json
-int
)
1425 "PC": mips (json
-int
)
1426 - "thread_id": ID of the underlying host
thread (json
-int
)
1430 -> { "execute": "query-cpus" }
1453 .name
= "query-cpus",
1455 .mhandler
.cmd_new
= qmp_marshal_input_query_cpus
,
1462 PCI buses and devices information
.
1464 The returned value is a json
-array of all buses
. Each bus is represented by
1465 a json
-object
, which has a key with a json
-array of all PCI devices attached
1466 to it
. Each device is represented by a json
-object
.
1468 The bus json
-object contains the following
:
1470 - "bus": bus
number (json
-int
)
1471 - "devices": a json
-array of json
-objects
, each json
-object represents a
1474 The PCI device json
-object contains the following
:
1476 - "bus": identical to the parent
's bus number (json-int)
1477 - "slot": slot number (json-int)
1478 - "function": function number (json-int)
1479 - "class_info": a json-object containing:
1480 - "desc": device class description (json-string, optional)
1481 - "class": device class number (json-int)
1482 - "id": a json-object containing:
1483 - "device": device ID (json-int)
1484 - "vendor": vendor ID (json-int)
1485 - "irq": device's IRQ
if assigned (json
-int
, optional
)
1486 - "qdev_id": qdev id
string (json
-string
)
1487 - "pci_bridge": It
's a json-object, only present if this device is a
1488 PCI bridge, contains:
1489 - "bus": bus number (json-int)
1490 - "secondary": secondary bus number (json-int)
1491 - "subordinate": subordinate bus number (json-int)
1492 - "io_range": I/O memory range information, a json-object with the
1494 - "base": base address, in bytes (json-int)
1495 - "limit": limit address, in bytes (json-int)
1496 - "memory_range": memory range information, a json-object with the
1498 - "base": base address, in bytes (json-int)
1499 - "limit": limit address, in bytes (json-int)
1500 - "prefetchable_range": Prefetchable memory range information, a
1501 json-object with the following members:
1502 - "base": base address, in bytes (json-int)
1503 - "limit": limit address, in bytes (json-int)
1504 - "devices": a json-array of PCI devices if there's any attached
, each
1505 each element is represented by a json
-object
, which contains
1506 the same members of the
'PCI device json-object' described
1508 - "regions": a json
-array of json
-objects
, each json
-object represents a
1509 memory region of
this device
1511 The memory range json
-object contains the following
:
1513 - "base": base memory
address (json
-int
)
1514 - "limit": limit
value (json
-int
)
1516 The region json
-object can be an I
/O region or a memory region
, an I
/O region
1517 json
-object contains the following
:
1519 - "type": "io" (json
-string
, fixed
)
1520 - "bar": BAR
number (json
-int
)
1521 - "address": memory
address (json
-int
)
1522 - "size": memory
size (json
-int
)
1524 A memory region json
-object contains the following
:
1526 - "type": "memory" (json
-string
, fixed
)
1527 - "bar": BAR
number (json
-int
)
1528 - "address": memory
address (json
-int
)
1529 - "size": memory
size (json
-int
)
1530 - "mem_type_64": true or
false (json
-bool
)
1531 - "prefetch": true or
false (json
-bool
)
1535 -> { "execute": "query-pci" }
1547 "desc":"Host bridge"
1581 "desc":"IDE controller"
1603 "desc":"VGA controller"
1613 "mem_type_64":false,
1616 "address":4026531840,
1621 "mem_type_64":false,
1624 "address":4060086272,
1629 "mem_type_64":false,
1644 "desc":"RAM controller"
1665 Note
: This example has been shortened as the real response is too long
.
1670 .name
= "query-pci",
1672 .mhandler
.cmd_new
= qmp_marshal_input_query_pci
,
1679 Show KVM information
.
1681 Return a json
-object with the following information
:
1683 - "enabled": true if KVM support is enabled
, false otherwise (json
-bool
)
1684 - "present": true if QEMU has KVM support
, false otherwise (json
-bool
)
1688 -> { "execute": "query-kvm" }
1689 <- { "return": { "enabled": true, "present": true } }
1694 .name
= "query-kvm",
1696 .mhandler
.cmd_new
= qmp_marshal_input_query_kvm
,
1703 Return a json
-object with the following information
:
1705 - "running": true if the VM is running
, or
false if it is
paused (json
-bool
)
1706 - "singlestep": true if the VM is
in single step mode
,
1707 false otherwise (json
-bool
)
1708 - "status": one of the following
values (json
-string
)
1709 "debug" - QEMU is running on a debugger
1710 "inmigrate" - guest is paused waiting
for an incoming migration
1711 "internal-error" - An internal error that prevents further guest
1712 execution has occurred
1713 "io-error" - the last IOP has failed and the device is configured
1714 to pause on I
/O errors
1715 "paused" - guest has been paused via the
'stop' command
1716 "postmigrate" - guest is paused following a successful
'migrate'
1717 "prelaunch" - QEMU was started with
-S and guest has not started
1718 "finish-migrate" - guest is paused to finish the migration process
1719 "restore-vm" - guest is paused to restore VM state
1720 "running" - guest is actively running
1721 "save-vm" - guest is paused to save the VM state
1722 "shutdown" - guest is shut
down (and
-no
-shutdown is
in use
)
1723 "watchdog" - the watchdog action is configured to pause and
1728 -> { "execute": "query-status" }
1729 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
1734 .name
= "query-status",
1736 .mhandler
.cmd_new
= qmp_marshal_input_query_status
,
1743 Show VM mice information
.
1745 Each mouse is represented by a json
-object
, the returned value is a json
-array
1748 The mouse json
-object contains the following
:
1750 - "name": mouse
's name (json-string)
1751 - "index": mouse's
index (json
-int
)
1752 - "current": true if this mouse is receiving events
, false otherwise (json
-bool
)
1753 - "absolute": true if the mouse generates absolute input
events (json
-bool
)
1757 -> { "execute": "query-mice" }
1761 "name":"QEMU Microsoft Mouse",
1767 "name":"QEMU PS/2 Mouse",
1778 .name
= "query-mice",
1780 .mhandler
.cmd_new
= qmp_marshal_input_query_mice
,
1787 Show VNC server information
.
1789 Return a json
-object with server information
. Connected clients are returned
1790 as a json
-array of json
-objects
.
1792 The main json
-object contains the following
:
1794 - "enabled": true or
false (json
-bool
)
1795 - "host": server
's IP address (json-string)
1796 - "family": address family (json-string)
1797 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1798 - "service": server's port
number (json
-string
)
1799 - "auth": authentication
method (json
-string
)
1800 - Possible values
: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
1801 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
1802 "vencrypt+plain", "vencrypt+tls+none",
1803 "vencrypt+tls+plain", "vencrypt+tls+sasl",
1804 "vencrypt+tls+vnc", "vencrypt+x509+none",
1805 "vencrypt+x509+plain", "vencrypt+x509+sasl",
1806 "vencrypt+x509+vnc", "vnc"
1807 - "clients": a json
-array of all connected clients
1809 Clients are described by a json
-object
, each one contain the following
:
1811 - "host": client
's IP address (json-string)
1812 - "family": address family (json-string)
1813 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1814 - "service": client's port
number (json
-string
)
1815 - "x509_dname": TLS
dname (json
-string
, optional
)
1816 - "sasl_username": SASL
username (json
-string
, optional
)
1820 -> { "execute": "query-vnc" }
1841 .name
= "query-vnc",
1843 .mhandler
.cmd_new
= qmp_marshal_input_query_vnc
,
1850 Show SPICE server information
.
1852 Return a json
-object with server information
. Connected clients are returned
1853 as a json
-array of json
-objects
.
1855 The main json
-object contains the following
:
1857 - "enabled": true or
false (json
-bool
)
1858 - "host": server
's IP address (json-string)
1859 - "port": server's port
number (json
-int
, optional
)
1860 - "tls-port": server
's port number (json-int, optional)
1861 - "auth": authentication method (json-string)
1862 - Possible values: "none", "spice"
1863 - "channels": a json-array of all active channels clients
1865 Channels are described by a json-object, each one contain the following:
1867 - "host": client's IP
address (json
-string
)
1868 - "family": address
family (json
-string
)
1869 - Possible values
: "ipv4", "ipv6", "unix", "unknown"
1870 - "port": client
's port number (json-string)
1871 - "connection-id": spice connection id. All channels with the same id
1872 belong to the same spice session (json-int)
1873 - "channel-type": channel type. "1" is the main control channel, filter for
1874 this one if you want track spice sessions only (json-int)
1875 - "channel-id": channel id. Usually "0", might be different needed when
1876 multiple channels of the same type exist, such as multiple
1877 display channels in a multihead setup (json-int)
1878 - "tls": whevener the channel is encrypted (json-bool)
1882 -> { "execute": "query-spice" }
1895 "connection-id": 1804289383,
1896 "host": "127.0.0.1",
1904 "connection-id": 1804289383,
1905 "host": "127.0.0.1",
1909 [ ... more channels follow ... ]
1916 #if defined(CONFIG_SPICE)
1918 .name = "query-spice",
1920 .mhandler.cmd_new = qmp_marshal_input_query_spice,
1930 Return a json-object with the following information:
1932 - "name": VM's
name (json
-string
, optional
)
1936 -> { "execute": "query-name" }
1937 <- { "return": { "name": "qemu-name" } }
1942 .name
= "query-name",
1944 .mhandler
.cmd_new
= qmp_marshal_input_query_name
,
1953 Return a json
-object with the following information
:
1955 - "UUID": Universally Unique
Identifier (json
-string
)
1959 -> { "execute": "query-uuid" }
1960 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
1965 .name
= "query-uuid",
1967 .mhandler
.cmd_new
= qmp_marshal_input_query_uuid
,
1976 Return a json
-object
. If migration is active there will be another json
-object
1977 with RAM migration status and
if block migration is active another one with
1978 block migration status
.
1980 The main json
-object contains the following
:
1982 - "status": migration
status (json
-string
)
1983 - Possible values
: "active", "completed", "failed", "cancelled"
1984 - "ram": only present
if "status" is
"active", it is a json
-object with the
1985 following RAM
information (in bytes
):
1986 - "transferred": amount
transferred (json
-int
)
1987 - "remaining": amount
remaining (json
-int
)
1988 - "total": total (json
-int
)
1989 - "disk": only present
if "status" is
"active" and it is a block migration
,
1990 it is a json
-object with the following disk
information (in bytes
):
1991 - "transferred": amount
transferred (json
-int
)
1992 - "remaining": amount
remaining (json
-int
)
1993 - "total": total (json
-int
)
1997 1. Before the first migration
1999 -> { "execute": "query-migrate" }
2002 2. Migration is done and has succeeded
2004 -> { "execute": "query-migrate" }
2005 <- { "return": { "status": "completed" } }
2007 3. Migration is done and has failed
2009 -> { "execute": "query-migrate" }
2010 <- { "return": { "status": "failed" } }
2012 4. Migration is being performed and is not a block migration
:
2014 -> { "execute": "query-migrate" }
2026 5. Migration is being performed and is a block migration
:
2028 -> { "execute": "query-migrate" }
2034 "remaining":1053304,
2039 "remaining":20880384,
2048 .name
= "query-migrate",
2050 .mhandler
.cmd_new
= qmp_marshal_input_query_migrate
,
2057 Show balloon information
.
2059 Make an asynchronous request
for balloon info
. When the request completes a
2060 json
-object will be returned containing the following data
:
2062 - "actual": current balloon value
in bytes (json
-int
)
2063 - "mem_swapped_in": Amount of memory swapped
in bytes (json
-int
, optional
)
2064 - "mem_swapped_out": Amount of memory swapped out
in bytes (json
-int
, optional
)
2065 - "major_page_faults": Number of major
faults (json
-int
, optional
)
2066 - "minor_page_faults": Number of minor
faults (json
-int
, optional
)
2067 - "free_mem": Total amount of free and unused memory
in
2068 bytes (json
-int
, optional
)
2069 - "total_mem": Total amount of available memory
in bytes (json
-int
, optional
)
2073 -> { "execute": "query-balloon" }
2076 "actual":1073741824,
2078 "mem_swapped_out":0,
2079 "major_page_faults":142,
2080 "minor_page_faults":239245,
2081 "free_mem":1014185984,
2082 "total_mem":1044668416
2089 .name
= "query-balloon",
2091 .mhandler
.cmd_new
= qmp_marshal_input_query_balloon
,
2095 .name
= "query-block-jobs",
2097 .mhandler
.cmd_new
= qmp_marshal_input_query_block_jobs
,
2102 .args_type
= "path:s",
2103 .mhandler
.cmd_new
= qmp_marshal_input_qom_list
,
2108 .args_type
= "path:s,property:s,opts:O",
2109 .mhandler
.cmd_new
= qmp_qom_set
,
2114 .args_type
= "path:s,property:s",
2115 .mhandler
.cmd_new
= qmp_qom_get
,
2119 .name
= "change-vnc-password",
2120 .args_type
= "password:s",
2121 .mhandler
.cmd_new
= qmp_marshal_input_change_vnc_password
,
2124 .name
= "qom-list-types",
2125 .args_type
= "implements:s?,abstract:b?",
2126 .mhandler
.cmd_new
= qmp_marshal_input_qom_list_types
,