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_reset",
217 .mhandler
.cmd_new
= qmp_marshal_input_system_reset
,
230 -> { "execute": "system_reset" }
236 .name
= "system_powerdown",
238 .mhandler
.cmd_new
= qmp_marshal_input_system_powerdown
,
245 Send system power down event
.
251 -> { "execute": "system_powerdown" }
257 .name
= "device_add",
258 .args_type
= "device:O",
259 .params
= "driver[,prop=value][,...]",
260 .help
= "add device, like -device on the command line",
261 .user_print
= monitor_user_noop
,
262 .mhandler
.cmd_new
= do_device_add
,
273 - "driver": the name of the
new device
's driver (json-string)
274 - "bus": the device's parent
bus (device tree path
, json
-string
, optional
)
275 - "id": the device
's ID, must be unique (json-string)
280 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
285 (1) For detailed information about this command, please refer to the
286 'docs
/qdev
-device
-use
.txt
' file.
288 (2) It's possible to list device properties by running QEMU with the
289 "-device DEVICE,\?" command
-line argument
, where DEVICE is the device
's name
294 .name = "device_del",
297 .help = "remove device",
298 .user_print = monitor_user_noop,
299 .mhandler.cmd_new = do_device_del,
310 - "id": the device's
ID (json
-string
)
314 -> { "execute": "device_del", "arguments": { "id": "net1" } }
321 .args_type
= "index:i",
322 .mhandler
.cmd_new
= qmp_marshal_input_cpu
,
333 - "index": the CPU
's index (json-int)
337 -> { "execute": "cpu", "arguments": { "index": 0 } }
340 Note: CPUs' indexes are obtained with the
'query-cpus' command
.
346 .args_type
= "val:l,size:i,filename:s,cpu:i?",
347 .mhandler
.cmd_new
= qmp_marshal_input_memsave
,
354 Save to disk virtual memory dump starting at
'val' of size
'size'.
358 - "val": the starting
address (json
-int
)
359 - "size": the memory size
, in bytes (json
-int
)
360 - "filename": file
path (json
-string
)
361 - "cpu": virtual CPU
index (json
-int
, optional
)
365 -> { "execute": "memsave",
366 "arguments": { "val": 10,
368 "filename": "/tmp/virtual-mem-dump" } }
375 .args_type
= "val:l,size:i,filename:s",
376 .mhandler
.cmd_new
= qmp_marshal_input_pmemsave
,
383 Save to disk physical memory dump starting at
'val' of size
'size'.
387 - "val": the starting
address (json
-int
)
388 - "size": the memory size
, in bytes (json
-int
)
389 - "filename": file
path (json
-string
)
393 -> { "execute": "pmemsave",
394 "arguments": { "val": 10,
396 "filename": "/tmp/physical-mem-dump" } }
402 .name
= "inject-nmi",
404 .mhandler
.cmd_new
= qmp_marshal_input_inject_nmi
,
411 Inject an NMI on guest
's CPUs.
417 -> { "execute": "inject-nmi" }
420 Note: inject-nmi is only supported for x86 guest currently, it will
421 returns "Unsupported" error for non-x86 guest.
427 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
428 .params = "[-d] [-b] [-i] uri",
429 .help = "migrate to URI (using -d to not wait for completion)"
430 "\n\t\t\t -b for migration without shared storage with"
431 " full copy of disk\n\t\t\t -i for migration without "
432 "shared storage with incremental copy of disk "
433 "(base image shared between src and destination)",
434 .user_print = monitor_user_noop,
435 .mhandler.cmd_new = do_migrate,
446 - "blk": block migration, full disk copy (json-bool, optional)
447 - "inc": incremental disk copy (json-bool, optional)
448 - "uri": Destination URI (json-string)
452 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
457 (1) The 'query
-migrate
' command should be used to check migration's progress
458 and final
result (this information is provided by the
'status' member
)
459 (2) All boolean arguments
default to
false
460 (3) The user Monitor
's "detach" argument is invalid in QMP and should not
466 .name = "migrate_cancel",
468 .mhandler.cmd_new = qmp_marshal_input_migrate_cancel,
475 Cancel the current migration.
481 -> { "execute": "migrate_cancel" }
487 .name = "migrate_set_speed",
488 .args_type = "value:o",
489 .mhandler.cmd_new = qmp_marshal_input_migrate_set_speed,
496 Set maximum speed for migrations.
500 - "value": maximum speed, in bytes per second (json-int)
504 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
510 .name = "migrate_set_downtime",
511 .args_type = "value:T",
512 .mhandler.cmd_new = qmp_marshal_input_migrate_set_downtime,
519 Set maximum tolerated downtime (in seconds) for migrations.
523 - "value": maximum downtime (json-number)
527 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
533 .name = "client_migrate_info",
534 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
535 .params = "protocol hostname port tls-port cert-subject",
536 .help = "send migration info to spice/vnc client",
537 .user_print = monitor_user_noop,
538 .mhandler.cmd_async = client_migrate_info,
539 .flags = MONITOR_CMD_ASYNC,
546 Set the spice/vnc connection info for the migration target. The spice/vnc
547 server will ask the spice/vnc client to automatically reconnect using the
548 new parameters (if specified) once the vm migration finished successfully.
552 - "protocol": protocol: "spice" or "vnc" (json-string)
553 - "hostname": migration target hostname (json-string)
554 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
555 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
556 - "cert-subject": server certificate subject (json-string, optional)
560 -> { "execute": "client_migrate_info",
561 "arguments": { "protocol": "spice",
562 "hostname": "virt42.lab.kraxel.org",
569 .name = "netdev_add",
570 .args_type = "netdev:O",
571 .params = "[user|tap|socket],id=str[,prop=value][,...]",
572 .help = "add host network device",
573 .user_print = monitor_user_noop,
574 .mhandler.cmd_new = do_netdev_add,
581 Add host network device.
585 - "type": the device type, "tap", "user", ... (json-string)
586 - "id": the device's ID
, must be
unique (json
-string
)
591 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
594 Note
: The supported device options are the same ones supported by the
'-net'
595 command
-line argument
, which are listed
in the
'-help' output or QEMU
's
601 .name = "netdev_del",
604 .help = "remove host network device",
605 .user_print = monitor_user_noop,
606 .mhandler.cmd_new = do_netdev_del,
613 Remove host network device.
617 - "id": the device's ID
, must be
unique (json
-string
)
621 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
628 .name
= "block_resize",
629 .args_type
= "device:B,size:o",
630 .mhandler
.cmd_new
= qmp_marshal_input_block_resize
,
637 Resize a block image
while a guest is running
.
641 - "device": the device
's ID, must be unique (json-string)
646 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
652 .name = "block_stream",
653 .args_type = "device:B,base:s?",
654 .mhandler.cmd_new = qmp_marshal_input_block_stream,
658 .name = "block_job_set_speed",
659 .args_type = "device:B,value:o",
660 .mhandler.cmd_new = qmp_marshal_input_block_job_set_speed,
664 .name = "block_job_cancel",
665 .args_type = "device:B",
666 .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
670 .name = "blockdev-snapshot-sync",
671 .args_type = "device:B,snapshot-file:s,format:s?",
672 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
676 blockdev-snapshot-sync
677 ----------------------
679 Synchronous snapshot of a block device. snapshot-file specifies the
680 target of the new image. If the file exists, or if it is a device, the
681 snapshot will be created in the existing file/device. If does not
682 exist, a new file will be created. format specifies the format of the
683 snapshot image, default is qcow2.
687 - "device": device name to snapshot (json-string)
688 - "snapshot-file": name of new image file (json-string)
689 - "format": format of new image (json-string, optional)
693 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
695 "/some/place/my-image",
696 "format": "qcow2" } }
703 .args_type = "value:M",
704 .mhandler.cmd_new = qmp_marshal_input_balloon,
711 Request VM to change its memory allocation (in bytes).
715 - "value": New memory allocation (json-int)
719 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
726 .args_type = "name:s,up:b",
727 .mhandler.cmd_new = qmp_marshal_input_set_link,
734 Change the link status of a network adapter.
738 - "name": network device name (json-string)
739 - "up": status is up (json-bool)
743 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
750 .args_type = "fdname:s",
751 .params = "getfd name",
752 .help = "receive a file descriptor via SCM rights and assign it a name",
753 .user_print = monitor_user_noop,
754 .mhandler.cmd_new = do_getfd,
761 Receive a file descriptor via SCM rights and assign it a name.
765 - "fdname": file descriptor name (json-string)
769 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
776 .args_type = "fdname:s",
777 .params = "closefd name",
778 .help = "close a file descriptor previously passed via SCM rights",
779 .user_print = monitor_user_noop,
780 .mhandler.cmd_new = do_closefd,
787 Close a file descriptor previously passed via SCM rights.
791 - "fdname": file descriptor name (json-string)
795 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
801 .name = "block_passwd",
802 .args_type = "device:B,password:s",
803 .mhandler.cmd_new = qmp_marshal_input_block_passwd,
810 Set the password of encrypted block devices.
814 - "device": device name (json-string)
815 - "password": password (json-string)
819 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
820 "password": "12345" } }
826 .name = "block_set_io_throttle",
827 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l",
828 .mhandler.cmd_new = qmp_marshal_input_block_set_io_throttle,
832 block_set_io_throttle
835 Change I/O throttle limits for a block drive.
839 - "device": device name (json-string)
840 - "bps": total throughput limit in bytes per second(json-int)
841 - "bps_rd": read throughput limit in bytes per second(json-int)
842 - "bps_wr": read throughput limit in bytes per second(json-int)
843 - "iops": total I/O operations per second(json-int)
844 - "iops_rd": read I/O operations per second(json-int)
845 - "iops_wr": write I/O operations per second(json-int)
849 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
861 .name = "set_password",
862 .args_type = "protocol:s,password:s,connected:s?",
863 .mhandler.cmd_new = qmp_marshal_input_set_password,
870 Set the password for vnc/spice protocols.
874 - "protocol": protocol name (json-string)
875 - "password": password (json-string)
876 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
880 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
881 "password": "secret" } }
887 .name = "expire_password",
888 .args_type = "protocol:s,time:s",
889 .mhandler.cmd_new = qmp_marshal_input_expire_password,
896 Set the password expire time for vnc/spice protocols.
900 - "protocol": protocol name (json-string)
901 - "time": [ now | never | +secs | secs ] (json-string)
905 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
912 .name = "add_client",
913 .args_type = "protocol:s,fdname:s,skipauth:b?",
914 .params = "protocol fdname skipauth",
915 .help = "add a graphics client",
916 .user_print = monitor_user_noop,
917 .mhandler.cmd_new = add_graphics_client,
924 Add a graphics client
928 - "protocol": protocol name (json-string)
929 - "fdname": file descriptor name (json-string)
933 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
934 "fdname": "myclient" } }
939 .name = "qmp_capabilities",
942 .help = "enable QMP capabilities",
943 .user_print = monitor_user_noop,
944 .mhandler.cmd_new = do_qmp_capabilities,
951 Enable QMP capabilities.
957 -> { "execute": "qmp_capabilities" }
960 Note: This command must be issued before issuing any other command.
965 .name = "human-monitor-command",
966 .args_type = "command-line:s,cpu-index:i?",
967 .mhandler.cmd_new = qmp_marshal_input_human_monitor_command,
971 human-monitor-command
972 ---------------------
974 Execute a Human Monitor command.
978 - command-line: the command name and its arguments, just like the
979 Human Monitor's
shell (json
-string
)
980 - cpu
-index
: select the CPU number to be used by commands which access CPU
981 data
, like
'info registers'. The Monitor selects CPU
0 if this
982 argument is not
provided (json
-int
, optional
)
986 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
987 <- { "return": "kvm support: enabled\r\n" }
991 (1) The Human Monitor is NOT an stable
interface, this means that command
992 names
, arguments and responses can change or be removed at ANY time
.
993 Applications that rely on long term stability guarantees should NOT
998 o This command is stateless
, this means that commands that depend
999 on state
information (such as getfd
) might not work
1001 o Commands that prompt the user
for data (eg
. 'cont' when the block
1002 device is encrypted
) don
't currently work
1007 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1008 HXCOMM this! We will possibly move query commands definitions inside those
1009 HXCOMM sections, just like regular commands.
1019 Return a json-object with the following information:
1021 - "qemu": A json-object containing three integer values:
1022 - "major": QEMU's major
version (json
-int
)
1023 - "minor": QEMU
's minor version (json-int)
1024 - "micro": QEMU's micro
version (json
-int
)
1025 - "package": package's version (json-string)
1029 -> { "execute": "query-version" }
1044 .name = "query-version",
1046 .mhandler.cmd_new = qmp_marshal_input_query_version,
1053 List QMP available commands.
1055 Each command is represented by a json-object, the returned value is a json-array
1058 Each json-object contain:
1060 - "name": command's
name (json
-string
)
1064 -> { "execute": "query-commands" }
1068 "name":"query-balloon"
1071 "name":"system_powerdown"
1076 Note
: This example has been shortened as the real response is too long
.
1081 .name
= "query-commands",
1083 .mhandler
.cmd_new
= qmp_marshal_input_query_commands
,
1090 Each device is represented by a json
-object
. The returned value is a json
-array
1093 Each json
-object contain the following
:
1095 - "label": device
's label (json-string)
1096 - "filename": device's
file (json
-string
)
1100 -> { "execute": "query-chardev" }
1117 .name
= "query-chardev",
1119 .mhandler
.cmd_new
= qmp_marshal_input_query_chardev
,
1126 Show the block devices
.
1128 Each block device information is stored
in a json
-object and the returned value
1129 is a json
-array of all devices
.
1131 Each json
-object contain the following
:
1133 - "device": device
name (json
-string
)
1134 - "type": device
type (json
-string
)
1135 - deprecated
, retained
for backward compatibility
1136 - Possible values
: "unknown"
1137 - "removable": true if the device is removable
, false otherwise (json
-bool
)
1138 - "locked": true if the device is locked
, false otherwise (json
-bool
)
1139 - "tray-open": only present
if removable
, true if the device has a tray
,
1140 and it is
open (json
-bool
)
1141 - "inserted": only present
if the device is inserted
, it is a json
-object
1142 containing the following
:
1143 - "file": device file
name (json
-string
)
1144 - "ro": true if read
-only
, false otherwise (json
-bool
)
1145 - "drv": driver format
name (json
-string
)
1146 - Possible values
: "blkdebug", "bochs", "cloop", "cow", "dmg",
1147 "file", "file", "ftp", "ftps", "host_cdrom",
1148 "host_device", "host_floppy", "http", "https",
1149 "nbd", "parallels", "qcow", "qcow2", "raw",
1150 "tftp", "vdi", "vmdk", "vpc", "vvfat"
1151 - "backing_file": backing file
name (json
-string
, optional
)
1152 - "encrypted": true if encrypted
, false otherwise (json
-bool
)
1153 - "bps": limit total bytes per
second (json
-int
)
1154 - "bps_rd": limit read bytes per
second (json
-int
)
1155 - "bps_wr": limit write bytes per
second (json
-int
)
1156 - "iops": limit total I
/O operations per
second (json
-int
)
1157 - "iops_rd": limit read operations per
second (json
-int
)
1158 - "iops_wr": limit write operations per
second (json
-int
)
1160 - "io-status": I
/O operation status
, only present
if the device supports it
1161 and the VM is configured to stop on errors
. It
's always reset
1162 to "ok" when the "cont" command is issued (json_string, optional)
1163 - Possible values: "ok", "failed", "nospace"
1167 -> { "execute": "query-block" }
1172 "device":"ide0-hd0",
1179 "file":"disks/test.img",
1191 "device":"ide1-cd0",
1214 .name = "query-block",
1216 .mhandler.cmd_new = qmp_marshal_input_query_block,
1223 Show block device statistics.
1225 Each device statistic information is stored in a json-object and the returned
1226 value is a json-array of all devices.
1228 Each json-object contain the following:
1230 - "device": device name (json-string)
1231 - "stats": A json-object with the statistics information, it contains:
1232 - "rd_bytes": bytes read (json-int)
1233 - "wr_bytes": bytes written (json-int)
1234 - "rd_operations": read operations (json-int)
1235 - "wr_operations": write operations (json-int)
1236 - "flush_operations": cache flush operations (json-int)
1237 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
1238 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
1239 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
1240 - "wr_highest_offset": Highest offset of a sector written since the
1241 BlockDriverState has been opened (json-int)
1242 - "parent": Contains recursively the statistics of the underlying
1243 protocol (e.g. the host file for a qcow2 image). If there is
1244 no underlying protocol, this field is omitted
1245 (json-object, optional)
1249 -> { "execute": "query-blockstats" }
1253 "device":"ide0-hd0",
1256 "wr_highest_offset":3686448128,
1258 "wr_operations":751,
1259 "rd_bytes":122567168,
1260 "rd_operations":36772
1261 "wr_total_times_ns":313253456
1262 "rd_total_times_ns":3465673657
1263 "flush_total_times_ns":49653
1264 "flush_operations":61,
1268 "wr_highest_offset":2821110784,
1270 "wr_operations":692,
1271 "rd_bytes":122739200,
1272 "rd_operations":36604
1273 "flush_operations":51,
1274 "wr_total_times_ns":313253456
1275 "rd_total_times_ns":3465673657
1276 "flush_total_times_ns":49653
1280 "device":"ide1-cd0",
1282 "wr_highest_offset":0,
1287 "flush_operations":0,
1288 "wr_total_times_ns":0
1289 "rd_total_times_ns":0
1290 "flush_total_times_ns":0
1296 "wr_highest_offset":0,
1301 "flush_operations":0,
1302 "wr_total_times_ns":0
1303 "rd_total_times_ns":0
1304 "flush_total_times_ns":0
1310 "wr_highest_offset":0,
1315 "flush_operations":0,
1316 "wr_total_times_ns":0
1317 "rd_total_times_ns":0
1318 "flush_total_times_ns":0
1327 .name = "query-blockstats",
1329 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
1336 Show CPU information.
1338 Return a json-array. Each CPU is represented by a json-object, which contains:
1340 - "CPU": CPU index (json-int)
1341 - "current": true if this is the current CPU, false otherwise (json-bool)
1342 - "halted": true if the cpu is halted, false otherwise (json-bool)
1343 - Current program counter. The key's name depends on the architecture
:
1344 "pc": i386
/x86_64 (json
-int
)
1345 "nip": PPC (json
-int
)
1346 "pc" and
"npc": sparc (json
-int
)
1347 "PC": mips (json
-int
)
1348 - "thread_id": ID of the underlying host
thread (json
-int
)
1352 -> { "execute": "query-cpus" }
1375 .name
= "query-cpus",
1377 .mhandler
.cmd_new
= qmp_marshal_input_query_cpus
,
1384 PCI buses and devices information
.
1386 The returned value is a json
-array of all buses
. Each bus is represented by
1387 a json
-object
, which has a key with a json
-array of all PCI devices attached
1388 to it
. Each device is represented by a json
-object
.
1390 The bus json
-object contains the following
:
1392 - "bus": bus
number (json
-int
)
1393 - "devices": a json
-array of json
-objects
, each json
-object represents a
1396 The PCI device json
-object contains the following
:
1398 - "bus": identical to the parent
's bus number (json-int)
1399 - "slot": slot number (json-int)
1400 - "function": function number (json-int)
1401 - "class_info": a json-object containing:
1402 - "desc": device class description (json-string, optional)
1403 - "class": device class number (json-int)
1404 - "id": a json-object containing:
1405 - "device": device ID (json-int)
1406 - "vendor": vendor ID (json-int)
1407 - "irq": device's IRQ
if assigned (json
-int
, optional
)
1408 - "qdev_id": qdev id
string (json
-string
)
1409 - "pci_bridge": It
's a json-object, only present if this device is a
1410 PCI bridge, contains:
1411 - "bus": bus number (json-int)
1412 - "secondary": secondary bus number (json-int)
1413 - "subordinate": subordinate bus number (json-int)
1414 - "io_range": I/O memory range information, a json-object with the
1416 - "base": base address, in bytes (json-int)
1417 - "limit": limit address, in bytes (json-int)
1418 - "memory_range": memory range information, a json-object with the
1420 - "base": base address, in bytes (json-int)
1421 - "limit": limit address, in bytes (json-int)
1422 - "prefetchable_range": Prefetchable memory range information, a
1423 json-object with the following members:
1424 - "base": base address, in bytes (json-int)
1425 - "limit": limit address, in bytes (json-int)
1426 - "devices": a json-array of PCI devices if there's any attached
, each
1427 each element is represented by a json
-object
, which contains
1428 the same members of the
'PCI device json-object' described
1430 - "regions": a json
-array of json
-objects
, each json
-object represents a
1431 memory region of
this device
1433 The memory range json
-object contains the following
:
1435 - "base": base memory
address (json
-int
)
1436 - "limit": limit
value (json
-int
)
1438 The region json
-object can be an I
/O region or a memory region
, an I
/O region
1439 json
-object contains the following
:
1441 - "type": "io" (json
-string
, fixed
)
1442 - "bar": BAR
number (json
-int
)
1443 - "address": memory
address (json
-int
)
1444 - "size": memory
size (json
-int
)
1446 A memory region json
-object contains the following
:
1448 - "type": "memory" (json
-string
, fixed
)
1449 - "bar": BAR
number (json
-int
)
1450 - "address": memory
address (json
-int
)
1451 - "size": memory
size (json
-int
)
1452 - "mem_type_64": true or
false (json
-bool
)
1453 - "prefetch": true or
false (json
-bool
)
1457 -> { "execute": "query-pci" }
1469 "desc":"Host bridge"
1503 "desc":"IDE controller"
1525 "desc":"VGA controller"
1535 "mem_type_64":false,
1538 "address":4026531840,
1543 "mem_type_64":false,
1546 "address":4060086272,
1551 "mem_type_64":false,
1566 "desc":"RAM controller"
1587 Note
: This example has been shortened as the real response is too long
.
1592 .name
= "query-pci",
1594 .mhandler
.cmd_new
= qmp_marshal_input_query_pci
,
1601 Show KVM information
.
1603 Return a json
-object with the following information
:
1605 - "enabled": true if KVM support is enabled
, false otherwise (json
-bool
)
1606 - "present": true if QEMU has KVM support
, false otherwise (json
-bool
)
1610 -> { "execute": "query-kvm" }
1611 <- { "return": { "enabled": true, "present": true } }
1616 .name
= "query-kvm",
1618 .mhandler
.cmd_new
= qmp_marshal_input_query_kvm
,
1625 Return a json
-object with the following information
:
1627 - "running": true if the VM is running
, or
false if it is
paused (json
-bool
)
1628 - "singlestep": true if the VM is
in single step mode
,
1629 false otherwise (json
-bool
)
1630 - "status": one of the following
values (json
-string
)
1631 "debug" - QEMU is running on a debugger
1632 "inmigrate" - guest is paused waiting
for an incoming migration
1633 "internal-error" - An internal error that prevents further guest
1634 execution has occurred
1635 "io-error" - the last IOP has failed and the device is configured
1636 to pause on I
/O errors
1637 "paused" - guest has been paused via the
'stop' command
1638 "postmigrate" - guest is paused following a successful
'migrate'
1639 "prelaunch" - QEMU was started with
-S and guest has not started
1640 "finish-migrate" - guest is paused to finish the migration process
1641 "restore-vm" - guest is paused to restore VM state
1642 "running" - guest is actively running
1643 "save-vm" - guest is paused to save the VM state
1644 "shutdown" - guest is shut
down (and
-no
-shutdown is
in use
)
1645 "watchdog" - the watchdog action is configured to pause and
1650 -> { "execute": "query-status" }
1651 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
1656 .name
= "query-status",
1658 .mhandler
.cmd_new
= qmp_marshal_input_query_status
,
1665 Show VM mice information
.
1667 Each mouse is represented by a json
-object
, the returned value is a json
-array
1670 The mouse json
-object contains the following
:
1672 - "name": mouse
's name (json-string)
1673 - "index": mouse's
index (json
-int
)
1674 - "current": true if this mouse is receiving events
, false otherwise (json
-bool
)
1675 - "absolute": true if the mouse generates absolute input
events (json
-bool
)
1679 -> { "execute": "query-mice" }
1683 "name":"QEMU Microsoft Mouse",
1689 "name":"QEMU PS/2 Mouse",
1700 .name
= "query-mice",
1702 .mhandler
.cmd_new
= qmp_marshal_input_query_mice
,
1709 Show VNC server information
.
1711 Return a json
-object with server information
. Connected clients are returned
1712 as a json
-array of json
-objects
.
1714 The main json
-object contains the following
:
1716 - "enabled": true or
false (json
-bool
)
1717 - "host": server
's IP address (json-string)
1718 - "family": address family (json-string)
1719 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1720 - "service": server's port
number (json
-string
)
1721 - "auth": authentication
method (json
-string
)
1722 - Possible values
: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
1723 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
1724 "vencrypt+plain", "vencrypt+tls+none",
1725 "vencrypt+tls+plain", "vencrypt+tls+sasl",
1726 "vencrypt+tls+vnc", "vencrypt+x509+none",
1727 "vencrypt+x509+plain", "vencrypt+x509+sasl",
1728 "vencrypt+x509+vnc", "vnc"
1729 - "clients": a json
-array of all connected clients
1731 Clients are described by a json
-object
, each one contain the following
:
1733 - "host": client
's IP address (json-string)
1734 - "family": address family (json-string)
1735 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1736 - "service": client's port
number (json
-string
)
1737 - "x509_dname": TLS
dname (json
-string
, optional
)
1738 - "sasl_username": SASL
username (json
-string
, optional
)
1742 -> { "execute": "query-vnc" }
1763 .name
= "query-vnc",
1765 .mhandler
.cmd_new
= qmp_marshal_input_query_vnc
,
1772 Show SPICE server information
.
1774 Return a json
-object with server information
. Connected clients are returned
1775 as a json
-array of json
-objects
.
1777 The main json
-object contains the following
:
1779 - "enabled": true or
false (json
-bool
)
1780 - "host": server
's IP address (json-string)
1781 - "port": server's port
number (json
-int
, optional
)
1782 - "tls-port": server
's port number (json-int, optional)
1783 - "auth": authentication method (json-string)
1784 - Possible values: "none", "spice"
1785 - "channels": a json-array of all active channels clients
1787 Channels are described by a json-object, each one contain the following:
1789 - "host": client's IP
address (json
-string
)
1790 - "family": address
family (json
-string
)
1791 - Possible values
: "ipv4", "ipv6", "unix", "unknown"
1792 - "port": client
's port number (json-string)
1793 - "connection-id": spice connection id. All channels with the same id
1794 belong to the same spice session (json-int)
1795 - "channel-type": channel type. "1" is the main control channel, filter for
1796 this one if you want track spice sessions only (json-int)
1797 - "channel-id": channel id. Usually "0", might be different needed when
1798 multiple channels of the same type exist, such as multiple
1799 display channels in a multihead setup (json-int)
1800 - "tls": whevener the channel is encrypted (json-bool)
1804 -> { "execute": "query-spice" }
1817 "connection-id": 1804289383,
1818 "host": "127.0.0.1",
1826 "connection-id": 1804289383,
1827 "host": "127.0.0.1",
1831 [ ... more channels follow ... ]
1838 #if defined(CONFIG_SPICE)
1840 .name = "query-spice",
1842 .mhandler.cmd_new = qmp_marshal_input_query_spice,
1852 Return a json-object with the following information:
1854 - "name": VM's
name (json
-string
, optional
)
1858 -> { "execute": "query-name" }
1859 <- { "return": { "name": "qemu-name" } }
1864 .name
= "query-name",
1866 .mhandler
.cmd_new
= qmp_marshal_input_query_name
,
1875 Return a json
-object with the following information
:
1877 - "UUID": Universally Unique
Identifier (json
-string
)
1881 -> { "execute": "query-uuid" }
1882 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
1887 .name
= "query-uuid",
1889 .mhandler
.cmd_new
= qmp_marshal_input_query_uuid
,
1898 Return a json
-object
. If migration is active there will be another json
-object
1899 with RAM migration status and
if block migration is active another one with
1900 block migration status
.
1902 The main json
-object contains the following
:
1904 - "status": migration
status (json
-string
)
1905 - Possible values
: "active", "completed", "failed", "cancelled"
1906 - "ram": only present
if "status" is
"active", it is a json
-object with the
1907 following RAM
information (in bytes
):
1908 - "transferred": amount
transferred (json
-int
)
1909 - "remaining": amount
remaining (json
-int
)
1910 - "total": total (json
-int
)
1911 - "disk": only present
if "status" is
"active" and it is a block migration
,
1912 it is a json
-object with the following disk
information (in bytes
):
1913 - "transferred": amount
transferred (json
-int
)
1914 - "remaining": amount
remaining (json
-int
)
1915 - "total": total (json
-int
)
1919 1. Before the first migration
1921 -> { "execute": "query-migrate" }
1924 2. Migration is done and has succeeded
1926 -> { "execute": "query-migrate" }
1927 <- { "return": { "status": "completed" } }
1929 3. Migration is done and has failed
1931 -> { "execute": "query-migrate" }
1932 <- { "return": { "status": "failed" } }
1934 4. Migration is being performed and is not a block migration
:
1936 -> { "execute": "query-migrate" }
1948 5. Migration is being performed and is a block migration
:
1950 -> { "execute": "query-migrate" }
1956 "remaining":1053304,
1961 "remaining":20880384,
1970 .name
= "query-migrate",
1972 .mhandler
.cmd_new
= qmp_marshal_input_query_migrate
,
1979 Show balloon information
.
1981 Make an asynchronous request
for balloon info
. When the request completes a
1982 json
-object will be returned containing the following data
:
1984 - "actual": current balloon value
in bytes (json
-int
)
1985 - "mem_swapped_in": Amount of memory swapped
in bytes (json
-int
, optional
)
1986 - "mem_swapped_out": Amount of memory swapped out
in bytes (json
-int
, optional
)
1987 - "major_page_faults": Number of major
faults (json
-int
, optional
)
1988 - "minor_page_faults": Number of minor
faults (json
-int
, optional
)
1989 - "free_mem": Total amount of free and unused memory
in
1990 bytes (json
-int
, optional
)
1991 - "total_mem": Total amount of available memory
in bytes (json
-int
, optional
)
1995 -> { "execute": "query-balloon" }
1998 "actual":1073741824,
2000 "mem_swapped_out":0,
2001 "major_page_faults":142,
2002 "minor_page_faults":239245,
2003 "free_mem":1014185984,
2004 "total_mem":1044668416
2011 .name
= "query-balloon",
2013 .mhandler
.cmd_new
= qmp_marshal_input_query_balloon
,
2017 .name
= "query-block-jobs",
2019 .mhandler
.cmd_new
= qmp_marshal_input_query_block_jobs
,
2024 .args_type
= "path:s",
2025 .mhandler
.cmd_new
= qmp_marshal_input_qom_list
,
2030 .args_type
= "path:s,property:s,opts:O",
2031 .mhandler
.cmd_new
= qmp_qom_set
,
2036 .args_type
= "path:s,property:s",
2037 .mhandler
.cmd_new
= qmp_qom_get
,
2041 .name
= "change-vnc-password",
2042 .args_type
= "password:s",
2043 .mhandler
.cmd_new
= qmp_marshal_input_change_vnc_password
,
2046 .name
= "qom-list-types",
2047 .args_type
= "implements:s?,abstract:b?",
2048 .mhandler
.cmd_new
= qmp_marshal_input_qom_list_types
,