target-ppc: dump DAR and DSISR
[qemu/ar7.git] / qmp-commands.hx
blobd982cd62b90d916ea2958b46cd11ae46a1f7d284
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.
5 SQMP
6 QMP Supported Commands
7 ----------------------
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
47 QEMU is available
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)
55 2. Regular Commands
56 ===================
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.
61 EQMP
64 .name = "quit",
65 .args_type = "",
66 .mhandler.cmd_new = qmp_marshal_input_quit,
69 SQMP
70 quit
71 ----
73 Quit the emulator.
75 Arguments: None.
77 Example:
79 -> { "execute": "quit" }
80 <- { "return": {} }
82 EQMP
85 .name = "eject",
86 .args_type = "force:-f,device:B",
87 .mhandler.cmd_new = qmp_marshal_input_eject,
90 SQMP
91 eject
92 -----
94 Eject a removable medium.
96 Arguments:
98 - force: force ejection (json-bool, optional)
99 - device: device name (json-string)
101 Example:
103 -> { "execute": "eject", "arguments": { "device": "ide1-cd0" } }
104 <- { "return": {} }
106 Note: The "force" argument defaults to false.
108 EQMP
111 .name = "change",
112 .args_type = "device:B,target:F,arg:s?",
113 .mhandler.cmd_new = qmp_marshal_input_change,
116 SQMP
117 change
118 ------
120 Change a removable medium or VNC configuration.
122 Arguments:
124 - "device": device name (json-string)
125 - "target": filename or item (json-string)
126 - "arg": additional argument (json-string, optional)
128 Examples:
130 1. Change a removable medium
132 -> { "execute": "change",
133 "arguments": { "device": "ide1-cd0",
134 "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } }
135 <- { "return": {} }
137 2. Change VNC password
139 -> { "execute": "change",
140 "arguments": { "device": "vnc", "target": "password",
141 "arg": "foobar1" } }
142 <- { "return": {} }
144 EQMP
147 .name = "screendump",
148 .args_type = "filename:F",
149 .mhandler.cmd_new = qmp_marshal_input_screendump,
152 SQMP
153 screendump
154 ----------
156 Save screen into PPM image.
158 Arguments:
160 - "filename": file path (json-string)
162 Example:
164 -> { "execute": "screendump", "arguments": { "filename": "/tmp/image" } }
165 <- { "return": {} }
167 EQMP
170 .name = "stop",
171 .args_type = "",
172 .mhandler.cmd_new = qmp_marshal_input_stop,
175 SQMP
176 stop
177 ----
179 Stop the emulator.
181 Arguments: None.
183 Example:
185 -> { "execute": "stop" }
186 <- { "return": {} }
188 EQMP
191 .name = "cont",
192 .args_type = "",
193 .mhandler.cmd_new = qmp_marshal_input_cont,
196 SQMP
197 cont
198 ----
200 Resume emulation.
202 Arguments: None.
204 Example:
206 -> { "execute": "cont" }
207 <- { "return": {} }
209 EQMP
212 .name = "system_wakeup",
213 .args_type = "",
214 .mhandler.cmd_new = qmp_marshal_input_system_wakeup,
217 SQMP
218 system_wakeup
219 -------------
221 Wakeup guest from suspend.
223 Arguments: None.
225 Example:
227 -> { "execute": "system_wakeup" }
228 <- { "return": {} }
230 EQMP
233 .name = "system_reset",
234 .args_type = "",
235 .mhandler.cmd_new = qmp_marshal_input_system_reset,
238 SQMP
239 system_reset
240 ------------
242 Reset the system.
244 Arguments: None.
246 Example:
248 -> { "execute": "system_reset" }
249 <- { "return": {} }
251 EQMP
254 .name = "system_powerdown",
255 .args_type = "",
256 .mhandler.cmd_new = qmp_marshal_input_system_powerdown,
259 SQMP
260 system_powerdown
261 ----------------
263 Send system power down event.
265 Arguments: None.
267 Example:
269 -> { "execute": "system_powerdown" }
270 <- { "return": {} }
272 EQMP
275 .name = "device_add",
276 .args_type = "device:O",
277 .params = "driver[,prop=value][,...]",
278 .help = "add device, like -device on the command line",
279 .user_print = monitor_user_noop,
280 .mhandler.cmd_new = do_device_add,
283 SQMP
284 device_add
285 ----------
287 Add a device.
289 Arguments:
291 - "driver": the name of the new device's driver (json-string)
292 - "bus": the device's parent bus (device tree path, json-string, optional)
293 - "id": the device's ID, must be unique (json-string)
294 - device properties
296 Example:
298 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
299 <- { "return": {} }
301 Notes:
303 (1) For detailed information about this command, please refer to the
304 'docs/qdev-device-use.txt' file.
306 (2) It's possible to list device properties by running QEMU with the
307 "-device DEVICE,\?" command-line argument, where DEVICE is the device's name
309 EQMP
312 .name = "device_del",
313 .args_type = "id:s",
314 .mhandler.cmd_new = qmp_marshal_input_device_del,
317 SQMP
318 device_del
319 ----------
321 Remove a device.
323 Arguments:
325 - "id": the device's ID (json-string)
327 Example:
329 -> { "execute": "device_del", "arguments": { "id": "net1" } }
330 <- { "return": {} }
332 EQMP
335 .name = "send-key",
336 .args_type = "keys:O,hold-time:i?",
337 .mhandler.cmd_new = qmp_marshal_input_send_key,
340 SQMP
341 send-key
342 ----------
344 Send keys to VM.
346 Arguments:
348 keys array:
349 - "key": key sequence (a json-array of key union values,
350 union can be number or qcode enum)
352 - hold-time: time to delay key up events, milliseconds. Defaults to 100
353 (json-int, optional)
355 Example:
357 -> { "execute": "send-key",
358 "arguments": { "keys": [ { "type": "qcode", "data": "ctrl" },
359 { "type": "qcode", "data": "alt" },
360 { "type": "qcode", "data": "delete" } ] } }
361 <- { "return": {} }
363 EQMP
366 .name = "cpu",
367 .args_type = "index:i",
368 .mhandler.cmd_new = qmp_marshal_input_cpu,
371 SQMP
375 Set the default CPU.
377 Arguments:
379 - "index": the CPU's index (json-int)
381 Example:
383 -> { "execute": "cpu", "arguments": { "index": 0 } }
384 <- { "return": {} }
386 Note: CPUs' indexes are obtained with the 'query-cpus' command.
388 EQMP
391 .name = "cpu-add",
392 .args_type = "id:i",
393 .mhandler.cmd_new = qmp_marshal_input_cpu_add,
396 SQMP
397 cpu-add
398 -------
400 Adds virtual cpu
402 Arguments:
404 - "id": cpu id (json-int)
406 Example:
408 -> { "execute": "cpu-add", "arguments": { "id": 2 } }
409 <- { "return": {} }
411 EQMP
414 .name = "memsave",
415 .args_type = "val:l,size:i,filename:s,cpu:i?",
416 .mhandler.cmd_new = qmp_marshal_input_memsave,
419 SQMP
420 memsave
421 -------
423 Save to disk virtual memory dump starting at 'val' of size 'size'.
425 Arguments:
427 - "val": the starting address (json-int)
428 - "size": the memory size, in bytes (json-int)
429 - "filename": file path (json-string)
430 - "cpu": virtual CPU index (json-int, optional)
432 Example:
434 -> { "execute": "memsave",
435 "arguments": { "val": 10,
436 "size": 100,
437 "filename": "/tmp/virtual-mem-dump" } }
438 <- { "return": {} }
440 EQMP
443 .name = "pmemsave",
444 .args_type = "val:l,size:i,filename:s",
445 .mhandler.cmd_new = qmp_marshal_input_pmemsave,
448 SQMP
449 pmemsave
450 --------
452 Save to disk physical memory dump starting at 'val' of size 'size'.
454 Arguments:
456 - "val": the starting address (json-int)
457 - "size": the memory size, in bytes (json-int)
458 - "filename": file path (json-string)
460 Example:
462 -> { "execute": "pmemsave",
463 "arguments": { "val": 10,
464 "size": 100,
465 "filename": "/tmp/physical-mem-dump" } }
466 <- { "return": {} }
468 EQMP
471 .name = "inject-nmi",
472 .args_type = "",
473 .mhandler.cmd_new = qmp_marshal_input_inject_nmi,
476 SQMP
477 inject-nmi
478 ----------
480 Inject an NMI on guest's CPUs.
482 Arguments: None.
484 Example:
486 -> { "execute": "inject-nmi" }
487 <- { "return": {} }
489 Note: inject-nmi fails when the guest doesn't support injecting.
490 Currently, only x86 (NMI) and s390x (RESTART) guests do.
492 EQMP
495 .name = "ringbuf-write",
496 .args_type = "device:s,data:s,format:s?",
497 .mhandler.cmd_new = qmp_marshal_input_ringbuf_write,
500 SQMP
501 ringbuf-write
502 -------------
504 Write to a ring buffer character device.
506 Arguments:
508 - "device": ring buffer character device name (json-string)
509 - "data": data to write (json-string)
510 - "format": data format (json-string, optional)
511 - Possible values: "utf8" (default), "base64"
512 Bug: invalid base64 is currently not rejected.
513 Whitespace *is* invalid.
515 Example:
517 -> { "execute": "ringbuf-write",
518 "arguments": { "device": "foo",
519 "data": "abcdefgh",
520 "format": "utf8" } }
521 <- { "return": {} }
523 EQMP
526 .name = "ringbuf-read",
527 .args_type = "device:s,size:i,format:s?",
528 .mhandler.cmd_new = qmp_marshal_input_ringbuf_read,
531 SQMP
532 ringbuf-read
533 -------------
535 Read from a ring buffer character device.
537 Arguments:
539 - "device": ring buffer character device name (json-string)
540 - "size": how many bytes to read at most (json-int)
541 - Number of data bytes, not number of characters in encoded data
542 - "format": data format (json-string, optional)
543 - Possible values: "utf8" (default), "base64"
544 - Naturally, format "utf8" works only when the ring buffer
545 contains valid UTF-8 text. Invalid UTF-8 sequences get
546 replaced. Bug: replacement doesn't work. Bug: can screw
547 up on encountering NUL characters, after the ring buffer
548 lost data, and when reading stops because the size limit
549 is reached.
551 Example:
553 -> { "execute": "ringbuf-read",
554 "arguments": { "device": "foo",
555 "size": 1000,
556 "format": "utf8" } }
557 <- {"return": "abcdefgh"}
559 EQMP
562 .name = "xen-save-devices-state",
563 .args_type = "filename:F",
564 .mhandler.cmd_new = qmp_marshal_input_xen_save_devices_state,
567 SQMP
568 xen-save-devices-state
569 -------
571 Save the state of all devices to file. The RAM and the block devices
572 of the VM are not saved by this command.
574 Arguments:
576 - "filename": the file to save the state of the devices to as binary
577 data. See xen-save-devices-state.txt for a description of the binary
578 format.
580 Example:
582 -> { "execute": "xen-save-devices-state",
583 "arguments": { "filename": "/tmp/save" } }
584 <- { "return": {} }
586 EQMP
589 .name = "xen-set-global-dirty-log",
590 .args_type = "enable:b",
591 .mhandler.cmd_new = qmp_marshal_input_xen_set_global_dirty_log,
594 SQMP
595 xen-set-global-dirty-log
596 -------
598 Enable or disable the global dirty log mode.
600 Arguments:
602 - "enable": Enable it or disable it.
604 Example:
606 -> { "execute": "xen-set-global-dirty-log",
607 "arguments": { "enable": true } }
608 <- { "return": {} }
610 EQMP
613 .name = "migrate",
614 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
615 .mhandler.cmd_new = qmp_marshal_input_migrate,
618 SQMP
619 migrate
620 -------
622 Migrate to URI.
624 Arguments:
626 - "blk": block migration, full disk copy (json-bool, optional)
627 - "inc": incremental disk copy (json-bool, optional)
628 - "uri": Destination URI (json-string)
630 Example:
632 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
633 <- { "return": {} }
635 Notes:
637 (1) The 'query-migrate' command should be used to check migration's progress
638 and final result (this information is provided by the 'status' member)
639 (2) All boolean arguments default to false
640 (3) The user Monitor's "detach" argument is invalid in QMP and should not
641 be used
643 EQMP
646 .name = "migrate_cancel",
647 .args_type = "",
648 .mhandler.cmd_new = qmp_marshal_input_migrate_cancel,
651 SQMP
652 migrate_cancel
653 --------------
655 Cancel the current migration.
657 Arguments: None.
659 Example:
661 -> { "execute": "migrate_cancel" }
662 <- { "return": {} }
664 EQMP
666 .name = "migrate-set-cache-size",
667 .args_type = "value:o",
668 .mhandler.cmd_new = qmp_marshal_input_migrate_set_cache_size,
671 SQMP
672 migrate-set-cache-size
673 ----------------------
675 Set cache size to be used by XBZRLE migration, the cache size will be rounded
676 down to the nearest power of 2
678 Arguments:
680 - "value": cache size in bytes (json-int)
682 Example:
684 -> { "execute": "migrate-set-cache-size", "arguments": { "value": 536870912 } }
685 <- { "return": {} }
687 EQMP
689 .name = "query-migrate-cache-size",
690 .args_type = "",
691 .mhandler.cmd_new = qmp_marshal_input_query_migrate_cache_size,
694 SQMP
695 query-migrate-cache-size
696 ------------------------
698 Show cache size to be used by XBZRLE migration
700 returns a json-object with the following information:
701 - "size" : json-int
703 Example:
705 -> { "execute": "query-migrate-cache-size" }
706 <- { "return": 67108864 }
708 EQMP
711 .name = "migrate_set_speed",
712 .args_type = "value:o",
713 .mhandler.cmd_new = qmp_marshal_input_migrate_set_speed,
716 SQMP
717 migrate_set_speed
718 -----------------
720 Set maximum speed for migrations.
722 Arguments:
724 - "value": maximum speed, in bytes per second (json-int)
726 Example:
728 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
729 <- { "return": {} }
731 EQMP
734 .name = "migrate_set_downtime",
735 .args_type = "value:T",
736 .mhandler.cmd_new = qmp_marshal_input_migrate_set_downtime,
739 SQMP
740 migrate_set_downtime
741 --------------------
743 Set maximum tolerated downtime (in seconds) for migrations.
745 Arguments:
747 - "value": maximum downtime (json-number)
749 Example:
751 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
752 <- { "return": {} }
754 EQMP
757 .name = "client_migrate_info",
758 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
759 .params = "protocol hostname port tls-port cert-subject",
760 .help = "send migration info to spice/vnc client",
761 .user_print = monitor_user_noop,
762 .mhandler.cmd_async = client_migrate_info,
763 .flags = MONITOR_CMD_ASYNC,
766 SQMP
767 client_migrate_info
768 ------------------
770 Set the spice/vnc connection info for the migration target. The spice/vnc
771 server will ask the spice/vnc client to automatically reconnect using the
772 new parameters (if specified) once the vm migration finished successfully.
774 Arguments:
776 - "protocol": protocol: "spice" or "vnc" (json-string)
777 - "hostname": migration target hostname (json-string)
778 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
779 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
780 - "cert-subject": server certificate subject (json-string, optional)
782 Example:
784 -> { "execute": "client_migrate_info",
785 "arguments": { "protocol": "spice",
786 "hostname": "virt42.lab.kraxel.org",
787 "port": 1234 } }
788 <- { "return": {} }
790 EQMP
793 .name = "dump-guest-memory",
794 .args_type = "paging:b,protocol:s,begin:i?,end:i?,format:s?",
795 .params = "-p protocol [begin] [length] [format]",
796 .help = "dump guest memory to file",
797 .user_print = monitor_user_noop,
798 .mhandler.cmd_new = qmp_marshal_input_dump_guest_memory,
801 SQMP
802 dump
805 Dump guest memory to file. The file can be processed with crash or gdb.
807 Arguments:
809 - "paging": do paging to get guest's memory mapping (json-bool)
810 - "protocol": destination file(started with "file:") or destination file
811 descriptor (started with "fd:") (json-string)
812 - "begin": the starting physical address. It's optional, and should be specified
813 with length together (json-int)
814 - "length": the memory size, in bytes. It's optional, and should be specified
815 with begin together (json-int)
816 - "format": the format of guest memory dump. It's optional, and can be
817 elf|kdump-zlib|kdump-lzo|kdump-snappy, but non-elf formats will
818 conflict with paging and filter, ie. begin and length (json-string)
820 Example:
822 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
823 <- { "return": {} }
825 Notes:
827 (1) All boolean arguments default to false
829 EQMP
832 .name = "query-dump-guest-memory-capability",
833 .args_type = "",
834 .mhandler.cmd_new = qmp_marshal_input_query_dump_guest_memory_capability,
837 SQMP
838 query-dump-guest-memory-capability
839 ----------
841 Show available formats for 'dump-guest-memory'
843 Example:
845 -> { "execute": "query-dump-guest-memory-capability" }
846 <- { "return": { "formats":
847 ["elf", "kdump-zlib", "kdump-lzo", "kdump-snappy"] }
849 EQMP
852 .name = "netdev_add",
853 .args_type = "netdev:O",
854 .mhandler.cmd_new = qmp_netdev_add,
857 SQMP
858 netdev_add
859 ----------
861 Add host network device.
863 Arguments:
865 - "type": the device type, "tap", "user", ... (json-string)
866 - "id": the device's ID, must be unique (json-string)
867 - device options
869 Example:
871 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
872 <- { "return": {} }
874 Note: The supported device options are the same ones supported by the '-netdev'
875 command-line argument, which are listed in the '-help' output or QEMU's
876 manual
878 EQMP
881 .name = "netdev_del",
882 .args_type = "id:s",
883 .mhandler.cmd_new = qmp_marshal_input_netdev_del,
886 SQMP
887 netdev_del
888 ----------
890 Remove host network device.
892 Arguments:
894 - "id": the device's ID, must be unique (json-string)
896 Example:
898 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
899 <- { "return": {} }
902 EQMP
905 .name = "object-add",
906 .args_type = "qom-type:s,id:s,props:q?",
907 .mhandler.cmd_new = qmp_object_add,
910 SQMP
911 object-add
912 ----------
914 Create QOM object.
916 Arguments:
918 - "qom-type": the object's QOM type, i.e. the class name (json-string)
919 - "id": the object's ID, must be unique (json-string)
920 - "props": a dictionary of object property values (optional, json-dict)
922 Example:
924 -> { "execute": "object-add", "arguments": { "qom-type": "rng-random", "id": "rng1",
925 "props": { "filename": "/dev/hwrng" } } }
926 <- { "return": {} }
928 EQMP
931 .name = "object-del",
932 .args_type = "id:s",
933 .mhandler.cmd_new = qmp_marshal_input_object_del,
936 SQMP
937 object-del
938 ----------
940 Remove QOM object.
942 Arguments:
944 - "id": the object's ID (json-string)
946 Example:
948 -> { "execute": "object-del", "arguments": { "id": "rng1" } }
949 <- { "return": {} }
952 EQMP
956 .name = "block_resize",
957 .args_type = "device:s?,node-name:s?,size:o",
958 .mhandler.cmd_new = qmp_marshal_input_block_resize,
961 SQMP
962 block_resize
963 ------------
965 Resize a block image while a guest is running.
967 Arguments:
969 - "device": the device's ID, must be unique (json-string)
970 - "node-name": the node name in the block driver state graph (json-string)
971 - "size": new size
973 Example:
975 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
976 <- { "return": {} }
978 EQMP
981 .name = "block-stream",
982 .args_type = "device:B,base:s?,speed:o?,on-error:s?",
983 .mhandler.cmd_new = qmp_marshal_input_block_stream,
987 .name = "block-commit",
988 .args_type = "device:B,base:s?,top:s,speed:o?",
989 .mhandler.cmd_new = qmp_marshal_input_block_commit,
992 SQMP
993 block-commit
994 ------------
996 Live commit of data from overlay image nodes into backing nodes - i.e., writes
997 data between 'top' and 'base' into 'base'.
999 Arguments:
1001 - "device": The device's ID, must be unique (json-string)
1002 - "base": The file name of the backing image to write data into.
1003 If not specified, this is the deepest backing image
1004 (json-string, optional)
1005 - "top": The file name of the backing image within the image chain,
1006 which contains the topmost data to be committed down.
1008 If top == base, that is an error.
1009 If top == active, the job will not be completed by itself,
1010 user needs to complete the job with the block-job-complete
1011 command after getting the ready event. (Since 2.0)
1013 If the base image is smaller than top, then the base image
1014 will be resized to be the same size as top. If top is
1015 smaller than the base image, the base will not be
1016 truncated. If you want the base image size to match the
1017 size of the smaller top, you can safely truncate it
1018 yourself once the commit operation successfully completes.
1019 (json-string)
1020 - "speed": the maximum speed, in bytes per second (json-int, optional)
1023 Example:
1025 -> { "execute": "block-commit", "arguments": { "device": "virtio0",
1026 "top": "/tmp/snap1.qcow2" } }
1027 <- { "return": {} }
1029 EQMP
1032 .name = "drive-backup",
1033 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1034 "on-source-error:s?,on-target-error:s?",
1035 .mhandler.cmd_new = qmp_marshal_input_drive_backup,
1038 SQMP
1039 drive-backup
1040 ------------
1042 Start a point-in-time copy of a block device to a new destination. The
1043 status of ongoing drive-backup operations can be checked with
1044 query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1045 The operation can be stopped before it has completed using the
1046 block-job-cancel command.
1048 Arguments:
1050 - "device": the name of the device which should be copied.
1051 (json-string)
1052 - "target": the target of the new image. If the file exists, or if it is a
1053 device, the existing file/device will be used as the new
1054 destination. If it does not exist, a new file will be created.
1055 (json-string)
1056 - "format": the format of the new destination, default is to probe if 'mode' is
1057 'existing', else the format of the source
1058 (json-string, optional)
1059 - "sync": what parts of the disk image should be copied to the destination;
1060 possibilities include "full" for all the disk, "top" for only the sectors
1061 allocated in the topmost image, or "none" to only replicate new I/O
1062 (MirrorSyncMode).
1063 - "mode": whether and how QEMU should create a new image
1064 (NewImageMode, optional, default 'absolute-paths')
1065 - "speed": the maximum speed, in bytes per second (json-int, optional)
1066 - "on-source-error": the action to take on an error on the source, default
1067 'report'. 'stop' and 'enospc' can only be used
1068 if the block device supports io-status.
1069 (BlockdevOnError, optional)
1070 - "on-target-error": the action to take on an error on the target, default
1071 'report' (no limitations, since this applies to
1072 a different block device than device).
1073 (BlockdevOnError, optional)
1075 Example:
1076 -> { "execute": "drive-backup", "arguments": { "device": "drive0",
1077 "sync": "full",
1078 "target": "backup.img" } }
1079 <- { "return": {} }
1080 EQMP
1083 .name = "block-job-set-speed",
1084 .args_type = "device:B,speed:o",
1085 .mhandler.cmd_new = qmp_marshal_input_block_job_set_speed,
1089 .name = "block-job-cancel",
1090 .args_type = "device:B,force:b?",
1091 .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
1094 .name = "block-job-pause",
1095 .args_type = "device:B",
1096 .mhandler.cmd_new = qmp_marshal_input_block_job_pause,
1099 .name = "block-job-resume",
1100 .args_type = "device:B",
1101 .mhandler.cmd_new = qmp_marshal_input_block_job_resume,
1104 .name = "block-job-complete",
1105 .args_type = "device:B",
1106 .mhandler.cmd_new = qmp_marshal_input_block_job_complete,
1109 .name = "transaction",
1110 .args_type = "actions:q",
1111 .mhandler.cmd_new = qmp_marshal_input_transaction,
1114 SQMP
1115 transaction
1116 -----------
1118 Atomically operate on one or more block devices. The only supported operations
1119 for now are drive-backup, internal and external snapshotting. A list of
1120 dictionaries is accepted, that contains the actions to be performed.
1121 If there is any failure performing any of the operations, all operations
1122 for the group are abandoned.
1124 For external snapshots, the dictionary contains the device, the file to use for
1125 the new snapshot, and the format. The default format, if not specified, is
1126 qcow2.
1128 Each new snapshot defaults to being created by QEMU (wiping any
1129 contents if the file already exists), but it is also possible to reuse
1130 an externally-created file. In the latter case, you should ensure that
1131 the new image file has the same contents as the current one; QEMU cannot
1132 perform any meaningful check. Typically this is achieved by using the
1133 current image file as the backing file for the new image.
1135 On failure, the original disks pre-snapshot attempt will be used.
1137 For internal snapshots, the dictionary contains the device and the snapshot's
1138 name. If an internal snapshot matching name already exists, the request will
1139 be rejected. Only some image formats support it, for example, qcow2, rbd,
1140 and sheepdog.
1142 On failure, qemu will try delete the newly created internal snapshot in the
1143 transaction. When an I/O error occurs during deletion, the user needs to fix
1144 it later with qemu-img or other command.
1146 Arguments:
1148 actions array:
1149 - "type": the operation to perform. The only supported
1150 value is "blockdev-snapshot-sync". (json-string)
1151 - "data": a dictionary. The contents depend on the value
1152 of "type". When "type" is "blockdev-snapshot-sync":
1153 - "device": device name to snapshot (json-string)
1154 - "node-name": graph node name to snapshot (json-string)
1155 - "snapshot-file": name of new image file (json-string)
1156 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1157 - "format": format of new image (json-string, optional)
1158 - "mode": whether and how QEMU should create the snapshot file
1159 (NewImageMode, optional, default "absolute-paths")
1160 When "type" is "blockdev-snapshot-internal-sync":
1161 - "device": device name to snapshot (json-string)
1162 - "name": name of the new snapshot (json-string)
1164 Example:
1166 -> { "execute": "transaction",
1167 "arguments": { "actions": [
1168 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd0",
1169 "snapshot-file": "/some/place/my-image",
1170 "format": "qcow2" } },
1171 { 'type': 'blockdev-snapshot-sync', 'data' : { "node-name": "myfile",
1172 "snapshot-file": "/some/place/my-image2",
1173 "snapshot-node-name": "node3432",
1174 "mode": "existing",
1175 "format": "qcow2" } },
1176 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd1",
1177 "snapshot-file": "/some/place/my-image2",
1178 "mode": "existing",
1179 "format": "qcow2" } },
1180 { 'type': 'blockdev-snapshot-internal-sync', 'data' : {
1181 "device": "ide-hd2",
1182 "name": "snapshot0" } } ] } }
1183 <- { "return": {} }
1185 EQMP
1188 .name = "blockdev-snapshot-sync",
1189 .args_type = "device:s?,node-name:s?,snapshot-file:s,snapshot-node-name:s?,format:s?,mode:s?",
1190 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
1193 SQMP
1194 blockdev-snapshot-sync
1195 ----------------------
1197 Synchronous snapshot of a block device. snapshot-file specifies the
1198 target of the new image. If the file exists, or if it is a device, the
1199 snapshot will be created in the existing file/device. If does not
1200 exist, a new file will be created. format specifies the format of the
1201 snapshot image, default is qcow2.
1203 Arguments:
1205 - "device": device name to snapshot (json-string)
1206 - "node-name": graph node name to snapshot (json-string)
1207 - "snapshot-file": name of new image file (json-string)
1208 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1209 - "mode": whether and how QEMU should create the snapshot file
1210 (NewImageMode, optional, default "absolute-paths")
1211 - "format": format of new image (json-string, optional)
1213 Example:
1215 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
1216 "snapshot-file":
1217 "/some/place/my-image",
1218 "format": "qcow2" } }
1219 <- { "return": {} }
1221 EQMP
1224 .name = "blockdev-snapshot-internal-sync",
1225 .args_type = "device:B,name:s",
1226 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_internal_sync,
1229 SQMP
1230 blockdev-snapshot-internal-sync
1231 -------------------------------
1233 Synchronously take an internal snapshot of a block device when the format of
1234 image used supports it. If the name is an empty string, or a snapshot with
1235 name already exists, the operation will fail.
1237 Arguments:
1239 - "device": device name to snapshot (json-string)
1240 - "name": name of the new snapshot (json-string)
1242 Example:
1244 -> { "execute": "blockdev-snapshot-internal-sync",
1245 "arguments": { "device": "ide-hd0",
1246 "name": "snapshot0" }
1248 <- { "return": {} }
1250 EQMP
1253 .name = "blockdev-snapshot-delete-internal-sync",
1254 .args_type = "device:B,id:s?,name:s?",
1255 .mhandler.cmd_new =
1256 qmp_marshal_input_blockdev_snapshot_delete_internal_sync,
1259 SQMP
1260 blockdev-snapshot-delete-internal-sync
1261 --------------------------------------
1263 Synchronously delete an internal snapshot of a block device when the format of
1264 image used supports it. The snapshot is identified by name or id or both. One
1265 of name or id is required. If the snapshot is not found, the operation will
1266 fail.
1268 Arguments:
1270 - "device": device name (json-string)
1271 - "id": ID of the snapshot (json-string, optional)
1272 - "name": name of the snapshot (json-string, optional)
1274 Example:
1276 -> { "execute": "blockdev-snapshot-delete-internal-sync",
1277 "arguments": { "device": "ide-hd0",
1278 "name": "snapshot0" }
1280 <- { "return": {
1281 "id": "1",
1282 "name": "snapshot0",
1283 "vm-state-size": 0,
1284 "date-sec": 1000012,
1285 "date-nsec": 10,
1286 "vm-clock-sec": 100,
1287 "vm-clock-nsec": 20
1291 EQMP
1294 .name = "drive-mirror",
1295 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1296 "on-source-error:s?,on-target-error:s?,"
1297 "granularity:i?,buf-size:i?",
1298 .mhandler.cmd_new = qmp_marshal_input_drive_mirror,
1301 SQMP
1302 drive-mirror
1303 ------------
1305 Start mirroring a block device's writes to a new destination. target
1306 specifies the target of the new image. If the file exists, or if it is
1307 a device, it will be used as the new destination for writes. If it does not
1308 exist, a new file will be created. format specifies the format of the
1309 mirror image, default is to probe if mode='existing', else the format
1310 of the source.
1312 Arguments:
1314 - "device": device name to operate on (json-string)
1315 - "target": name of new image file (json-string)
1316 - "format": format of new image (json-string, optional)
1317 - "mode": how an image file should be created into the target
1318 file/device (NewImageMode, optional, default 'absolute-paths')
1319 - "speed": maximum speed of the streaming job, in bytes per second
1320 (json-int)
1321 - "granularity": granularity of the dirty bitmap, in bytes (json-int, optional)
1322 - "buf_size": maximum amount of data in flight from source to target, in bytes
1323 (json-int, default 10M)
1324 - "sync": what parts of the disk image should be copied to the destination;
1325 possibilities include "full" for all the disk, "top" for only the sectors
1326 allocated in the topmost image, or "none" to only replicate new I/O
1327 (MirrorSyncMode).
1328 - "on-source-error": the action to take on an error on the source
1329 (BlockdevOnError, default 'report')
1330 - "on-target-error": the action to take on an error on the target
1331 (BlockdevOnError, default 'report')
1333 The default value of the granularity is the image cluster size clamped
1334 between 4096 and 65536, if the image format defines one. If the format
1335 does not define a cluster size, the default value of the granularity
1336 is 65536.
1339 Example:
1341 -> { "execute": "drive-mirror", "arguments": { "device": "ide-hd0",
1342 "target": "/some/place/my-image",
1343 "sync": "full",
1344 "format": "qcow2" } }
1345 <- { "return": {} }
1347 EQMP
1350 .name = "balloon",
1351 .args_type = "value:M",
1352 .mhandler.cmd_new = qmp_marshal_input_balloon,
1355 SQMP
1356 balloon
1357 -------
1359 Request VM to change its memory allocation (in bytes).
1361 Arguments:
1363 - "value": New memory allocation (json-int)
1365 Example:
1367 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1368 <- { "return": {} }
1370 EQMP
1373 .name = "set_link",
1374 .args_type = "name:s,up:b",
1375 .mhandler.cmd_new = qmp_marshal_input_set_link,
1378 SQMP
1379 set_link
1380 --------
1382 Change the link status of a network adapter.
1384 Arguments:
1386 - "name": network device name (json-string)
1387 - "up": status is up (json-bool)
1389 Example:
1391 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
1392 <- { "return": {} }
1394 EQMP
1397 .name = "getfd",
1398 .args_type = "fdname:s",
1399 .params = "getfd name",
1400 .help = "receive a file descriptor via SCM rights and assign it a name",
1401 .mhandler.cmd_new = qmp_marshal_input_getfd,
1404 SQMP
1405 getfd
1406 -----
1408 Receive a file descriptor via SCM rights and assign it a name.
1410 Arguments:
1412 - "fdname": file descriptor name (json-string)
1414 Example:
1416 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1417 <- { "return": {} }
1419 Notes:
1421 (1) If the name specified by the "fdname" argument already exists,
1422 the file descriptor assigned to it will be closed and replaced
1423 by the received file descriptor.
1424 (2) The 'closefd' command can be used to explicitly close the file
1425 descriptor when it is no longer needed.
1427 EQMP
1430 .name = "closefd",
1431 .args_type = "fdname:s",
1432 .params = "closefd name",
1433 .help = "close a file descriptor previously passed via SCM rights",
1434 .mhandler.cmd_new = qmp_marshal_input_closefd,
1437 SQMP
1438 closefd
1439 -------
1441 Close a file descriptor previously passed via SCM rights.
1443 Arguments:
1445 - "fdname": file descriptor name (json-string)
1447 Example:
1449 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1450 <- { "return": {} }
1452 EQMP
1455 .name = "add-fd",
1456 .args_type = "fdset-id:i?,opaque:s?",
1457 .params = "add-fd fdset-id opaque",
1458 .help = "Add a file descriptor, that was passed via SCM rights, to an fd set",
1459 .mhandler.cmd_new = qmp_marshal_input_add_fd,
1462 SQMP
1463 add-fd
1464 -------
1466 Add a file descriptor, that was passed via SCM rights, to an fd set.
1468 Arguments:
1470 - "fdset-id": The ID of the fd set to add the file descriptor to.
1471 (json-int, optional)
1472 - "opaque": A free-form string that can be used to describe the fd.
1473 (json-string, optional)
1475 Return a json-object with the following information:
1477 - "fdset-id": The ID of the fd set that the fd was added to. (json-int)
1478 - "fd": The file descriptor that was received via SCM rights and added to the
1479 fd set. (json-int)
1481 Example:
1483 -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1484 <- { "return": { "fdset-id": 1, "fd": 3 } }
1486 Notes:
1488 (1) The list of fd sets is shared by all monitor connections.
1489 (2) If "fdset-id" is not specified, a new fd set will be created.
1491 EQMP
1494 .name = "remove-fd",
1495 .args_type = "fdset-id:i,fd:i?",
1496 .params = "remove-fd fdset-id fd",
1497 .help = "Remove a file descriptor from an fd set",
1498 .mhandler.cmd_new = qmp_marshal_input_remove_fd,
1501 SQMP
1502 remove-fd
1503 ---------
1505 Remove a file descriptor from an fd set.
1507 Arguments:
1509 - "fdset-id": The ID of the fd set that the file descriptor belongs to.
1510 (json-int)
1511 - "fd": The file descriptor that is to be removed. (json-int, optional)
1513 Example:
1515 -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1516 <- { "return": {} }
1518 Notes:
1520 (1) The list of fd sets is shared by all monitor connections.
1521 (2) If "fd" is not specified, all file descriptors in "fdset-id" will be
1522 removed.
1524 EQMP
1527 .name = "query-fdsets",
1528 .args_type = "",
1529 .help = "Return information describing all fd sets",
1530 .mhandler.cmd_new = qmp_marshal_input_query_fdsets,
1533 SQMP
1534 query-fdsets
1535 -------------
1537 Return information describing all fd sets.
1539 Arguments: None
1541 Example:
1543 -> { "execute": "query-fdsets" }
1544 <- { "return": [
1546 "fds": [
1548 "fd": 30,
1549 "opaque": "rdonly:/path/to/file"
1552 "fd": 24,
1553 "opaque": "rdwr:/path/to/file"
1556 "fdset-id": 1
1559 "fds": [
1561 "fd": 28
1564 "fd": 29
1567 "fdset-id": 0
1572 Note: The list of fd sets is shared by all monitor connections.
1574 EQMP
1577 .name = "block_passwd",
1578 .args_type = "device:s?,node-name:s?,password:s",
1579 .mhandler.cmd_new = qmp_marshal_input_block_passwd,
1582 SQMP
1583 block_passwd
1584 ------------
1586 Set the password of encrypted block devices.
1588 Arguments:
1590 - "device": device name (json-string)
1591 - "node-name": name in the block driver state graph (json-string)
1592 - "password": password (json-string)
1594 Example:
1596 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
1597 "password": "12345" } }
1598 <- { "return": {} }
1600 EQMP
1603 .name = "block_set_io_throttle",
1604 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l,bps_max:l?,bps_rd_max:l?,bps_wr_max:l?,iops_max:l?,iops_rd_max:l?,iops_wr_max:l?,iops_size:l?",
1605 .mhandler.cmd_new = qmp_marshal_input_block_set_io_throttle,
1608 SQMP
1609 block_set_io_throttle
1610 ------------
1612 Change I/O throttle limits for a block drive.
1614 Arguments:
1616 - "device": device name (json-string)
1617 - "bps": total throughput limit in bytes per second (json-int)
1618 - "bps_rd": read throughput limit in bytes per second (json-int)
1619 - "bps_wr": write throughput limit in bytes per second (json-int)
1620 - "iops": total I/O operations per second (json-int)
1621 - "iops_rd": read I/O operations per second (json-int)
1622 - "iops_wr": write I/O operations per second (json-int)
1623 - "bps_max": total max in bytes (json-int)
1624 - "bps_rd_max": read max in bytes (json-int)
1625 - "bps_wr_max": write max in bytes (json-int)
1626 - "iops_max": total I/O operations max (json-int)
1627 - "iops_rd_max": read I/O operations max (json-int)
1628 - "iops_wr_max": write I/O operations max (json-int)
1629 - "iops_size": I/O size in bytes when limiting (json-int)
1631 Example:
1633 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
1634 "bps": 1000000,
1635 "bps_rd": 0,
1636 "bps_wr": 0,
1637 "iops": 0,
1638 "iops_rd": 0,
1639 "iops_wr": 0,
1640 "bps_max": 8000000,
1641 "bps_rd_max": 0,
1642 "bps_wr_max": 0,
1643 "iops_max": 0,
1644 "iops_rd_max": 0,
1645 "iops_wr_max": 0,
1646 "iops_size": 0 } }
1647 <- { "return": {} }
1649 EQMP
1652 .name = "set_password",
1653 .args_type = "protocol:s,password:s,connected:s?",
1654 .mhandler.cmd_new = qmp_marshal_input_set_password,
1657 SQMP
1658 set_password
1659 ------------
1661 Set the password for vnc/spice protocols.
1663 Arguments:
1665 - "protocol": protocol name (json-string)
1666 - "password": password (json-string)
1667 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
1669 Example:
1671 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
1672 "password": "secret" } }
1673 <- { "return": {} }
1675 EQMP
1678 .name = "expire_password",
1679 .args_type = "protocol:s,time:s",
1680 .mhandler.cmd_new = qmp_marshal_input_expire_password,
1683 SQMP
1684 expire_password
1685 ---------------
1687 Set the password expire time for vnc/spice protocols.
1689 Arguments:
1691 - "protocol": protocol name (json-string)
1692 - "time": [ now | never | +secs | secs ] (json-string)
1694 Example:
1696 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
1697 "time": "+60" } }
1698 <- { "return": {} }
1700 EQMP
1703 .name = "add_client",
1704 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
1705 .mhandler.cmd_new = qmp_marshal_input_add_client,
1708 SQMP
1709 add_client
1710 ----------
1712 Add a graphics client
1714 Arguments:
1716 - "protocol": protocol name (json-string)
1717 - "fdname": file descriptor name (json-string)
1718 - "skipauth": whether to skip authentication (json-bool, optional)
1719 - "tls": whether to perform TLS (json-bool, optional)
1721 Example:
1723 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
1724 "fdname": "myclient" } }
1725 <- { "return": {} }
1727 EQMP
1729 .name = "qmp_capabilities",
1730 .args_type = "",
1731 .params = "",
1732 .help = "enable QMP capabilities",
1733 .user_print = monitor_user_noop,
1734 .mhandler.cmd_new = do_qmp_capabilities,
1737 SQMP
1738 qmp_capabilities
1739 ----------------
1741 Enable QMP capabilities.
1743 Arguments: None.
1745 Example:
1747 -> { "execute": "qmp_capabilities" }
1748 <- { "return": {} }
1750 Note: This command must be issued before issuing any other command.
1752 EQMP
1755 .name = "human-monitor-command",
1756 .args_type = "command-line:s,cpu-index:i?",
1757 .mhandler.cmd_new = qmp_marshal_input_human_monitor_command,
1760 SQMP
1761 human-monitor-command
1762 ---------------------
1764 Execute a Human Monitor command.
1766 Arguments:
1768 - command-line: the command name and its arguments, just like the
1769 Human Monitor's shell (json-string)
1770 - cpu-index: select the CPU number to be used by commands which access CPU
1771 data, like 'info registers'. The Monitor selects CPU 0 if this
1772 argument is not provided (json-int, optional)
1774 Example:
1776 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1777 <- { "return": "kvm support: enabled\r\n" }
1779 Notes:
1781 (1) The Human Monitor is NOT an stable interface, this means that command
1782 names, arguments and responses can change or be removed at ANY time.
1783 Applications that rely on long term stability guarantees should NOT
1784 use this command
1786 (2) Limitations:
1788 o This command is stateless, this means that commands that depend
1789 on state information (such as getfd) might not work
1791 o Commands that prompt the user for data (eg. 'cont' when the block
1792 device is encrypted) don't currently work
1794 3. Query Commands
1795 =================
1797 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1798 HXCOMM this! We will possibly move query commands definitions inside those
1799 HXCOMM sections, just like regular commands.
1801 EQMP
1803 SQMP
1804 query-version
1805 -------------
1807 Show QEMU version.
1809 Return a json-object with the following information:
1811 - "qemu": A json-object containing three integer values:
1812 - "major": QEMU's major version (json-int)
1813 - "minor": QEMU's minor version (json-int)
1814 - "micro": QEMU's micro version (json-int)
1815 - "package": package's version (json-string)
1817 Example:
1819 -> { "execute": "query-version" }
1820 <- {
1821 "return":{
1822 "qemu":{
1823 "major":0,
1824 "minor":11,
1825 "micro":5
1827 "package":""
1831 EQMP
1834 .name = "query-version",
1835 .args_type = "",
1836 .mhandler.cmd_new = qmp_marshal_input_query_version,
1839 SQMP
1840 query-commands
1841 --------------
1843 List QMP available commands.
1845 Each command is represented by a json-object, the returned value is a json-array
1846 of all commands.
1848 Each json-object contain:
1850 - "name": command's name (json-string)
1852 Example:
1854 -> { "execute": "query-commands" }
1855 <- {
1856 "return":[
1858 "name":"query-balloon"
1861 "name":"system_powerdown"
1866 Note: This example has been shortened as the real response is too long.
1868 EQMP
1871 .name = "query-commands",
1872 .args_type = "",
1873 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1876 SQMP
1877 query-events
1878 --------------
1880 List QMP available events.
1882 Each event is represented by a json-object, the returned value is a json-array
1883 of all events.
1885 Each json-object contains:
1887 - "name": event's name (json-string)
1889 Example:
1891 -> { "execute": "query-events" }
1892 <- {
1893 "return":[
1895 "name":"SHUTDOWN"
1898 "name":"RESET"
1903 Note: This example has been shortened as the real response is too long.
1905 EQMP
1908 .name = "query-events",
1909 .args_type = "",
1910 .mhandler.cmd_new = qmp_marshal_input_query_events,
1913 SQMP
1914 query-chardev
1915 -------------
1917 Each device is represented by a json-object. The returned value is a json-array
1918 of all devices.
1920 Each json-object contain the following:
1922 - "label": device's label (json-string)
1923 - "filename": device's file (json-string)
1925 Example:
1927 -> { "execute": "query-chardev" }
1928 <- {
1929 "return":[
1931 "label":"monitor",
1932 "filename":"stdio"
1935 "label":"serial0",
1936 "filename":"vc"
1941 EQMP
1944 .name = "query-chardev",
1945 .args_type = "",
1946 .mhandler.cmd_new = qmp_marshal_input_query_chardev,
1949 SQMP
1950 query-chardev-backends
1951 -------------
1953 List available character device backends.
1955 Each backend is represented by a json-object, the returned value is a json-array
1956 of all backends.
1958 Each json-object contains:
1960 - "name": backend name (json-string)
1962 Example:
1964 -> { "execute": "query-chardev-backends" }
1965 <- {
1966 "return":[
1968 "name":"udp"
1971 "name":"tcp"
1974 "name":"unix"
1977 "name":"spiceport"
1982 EQMP
1985 .name = "query-chardev-backends",
1986 .args_type = "",
1987 .mhandler.cmd_new = qmp_marshal_input_query_chardev_backends,
1990 SQMP
1991 query-block
1992 -----------
1994 Show the block devices.
1996 Each block device information is stored in a json-object and the returned value
1997 is a json-array of all devices.
1999 Each json-object contain the following:
2001 - "device": device name (json-string)
2002 - "type": device type (json-string)
2003 - deprecated, retained for backward compatibility
2004 - Possible values: "unknown"
2005 - "removable": true if the device is removable, false otherwise (json-bool)
2006 - "locked": true if the device is locked, false otherwise (json-bool)
2007 - "tray_open": only present if removable, true if the device has a tray,
2008 and it is open (json-bool)
2009 - "inserted": only present if the device is inserted, it is a json-object
2010 containing the following:
2011 - "file": device file name (json-string)
2012 - "ro": true if read-only, false otherwise (json-bool)
2013 - "drv": driver format name (json-string)
2014 - Possible values: "blkdebug", "bochs", "cloop", "cow", "dmg",
2015 "file", "file", "ftp", "ftps", "host_cdrom",
2016 "host_device", "host_floppy", "http", "https",
2017 "nbd", "parallels", "qcow", "qcow2", "raw",
2018 "tftp", "vdi", "vmdk", "vpc", "vvfat"
2019 - "backing_file": backing file name (json-string, optional)
2020 - "backing_file_depth": number of files in the backing file chain (json-int)
2021 - "encrypted": true if encrypted, false otherwise (json-bool)
2022 - "bps": limit total bytes per second (json-int)
2023 - "bps_rd": limit read bytes per second (json-int)
2024 - "bps_wr": limit write bytes per second (json-int)
2025 - "iops": limit total I/O operations per second (json-int)
2026 - "iops_rd": limit read operations per second (json-int)
2027 - "iops_wr": limit write operations per second (json-int)
2028 - "bps_max": total max in bytes (json-int)
2029 - "bps_rd_max": read max in bytes (json-int)
2030 - "bps_wr_max": write max in bytes (json-int)
2031 - "iops_max": total I/O operations max (json-int)
2032 - "iops_rd_max": read I/O operations max (json-int)
2033 - "iops_wr_max": write I/O operations max (json-int)
2034 - "iops_size": I/O size when limiting by iops (json-int)
2035 - "image": the detail of the image, it is a json-object containing
2036 the following:
2037 - "filename": image file name (json-string)
2038 - "format": image format (json-string)
2039 - "virtual-size": image capacity in bytes (json-int)
2040 - "dirty-flag": true if image is not cleanly closed, not present
2041 means clean (json-bool, optional)
2042 - "actual-size": actual size on disk in bytes of the image, not
2043 present when image does not support thin
2044 provision (json-int, optional)
2045 - "cluster-size": size of a cluster in bytes, not present if image
2046 format does not support it (json-int, optional)
2047 - "encrypted": true if the image is encrypted, not present means
2048 false or the image format does not support
2049 encryption (json-bool, optional)
2050 - "backing_file": backing file name, not present means no backing
2051 file is used or the image format does not
2052 support backing file chain
2053 (json-string, optional)
2054 - "full-backing-filename": full path of the backing file, not
2055 present if it equals backing_file or no
2056 backing file is used
2057 (json-string, optional)
2058 - "backing-filename-format": the format of the backing file, not
2059 present means unknown or no backing
2060 file (json-string, optional)
2061 - "snapshots": the internal snapshot info, it is an optional list
2062 of json-object containing the following:
2063 - "id": unique snapshot id (json-string)
2064 - "name": snapshot name (json-string)
2065 - "vm-state-size": size of the VM state in bytes (json-int)
2066 - "date-sec": UTC date of the snapshot in seconds (json-int)
2067 - "date-nsec": fractional part in nanoseconds to be used with
2068 date-sec (json-int)
2069 - "vm-clock-sec": VM clock relative to boot in seconds
2070 (json-int)
2071 - "vm-clock-nsec": fractional part in nanoseconds to be used
2072 with vm-clock-sec (json-int)
2073 - "backing-image": the detail of the backing image, it is an
2074 optional json-object only present when a
2075 backing image present for this image
2077 - "io-status": I/O operation status, only present if the device supports it
2078 and the VM is configured to stop on errors. It's always reset
2079 to "ok" when the "cont" command is issued (json_string, optional)
2080 - Possible values: "ok", "failed", "nospace"
2082 Example:
2084 -> { "execute": "query-block" }
2085 <- {
2086 "return":[
2088 "io-status": "ok",
2089 "device":"ide0-hd0",
2090 "locked":false,
2091 "removable":false,
2092 "inserted":{
2093 "ro":false,
2094 "drv":"qcow2",
2095 "encrypted":false,
2096 "file":"disks/test.qcow2",
2097 "backing_file_depth":1,
2098 "bps":1000000,
2099 "bps_rd":0,
2100 "bps_wr":0,
2101 "iops":1000000,
2102 "iops_rd":0,
2103 "iops_wr":0,
2104 "bps_max": 8000000,
2105 "bps_rd_max": 0,
2106 "bps_wr_max": 0,
2107 "iops_max": 0,
2108 "iops_rd_max": 0,
2109 "iops_wr_max": 0,
2110 "iops_size": 0,
2111 "image":{
2112 "filename":"disks/test.qcow2",
2113 "format":"qcow2",
2114 "virtual-size":2048000,
2115 "backing_file":"base.qcow2",
2116 "full-backing-filename":"disks/base.qcow2",
2117 "backing-filename-format:"qcow2",
2118 "snapshots":[
2120 "id": "1",
2121 "name": "snapshot1",
2122 "vm-state-size": 0,
2123 "date-sec": 10000200,
2124 "date-nsec": 12,
2125 "vm-clock-sec": 206,
2126 "vm-clock-nsec": 30
2129 "backing-image":{
2130 "filename":"disks/base.qcow2",
2131 "format":"qcow2",
2132 "virtual-size":2048000
2136 "type":"unknown"
2139 "io-status": "ok",
2140 "device":"ide1-cd0",
2141 "locked":false,
2142 "removable":true,
2143 "type":"unknown"
2146 "device":"floppy0",
2147 "locked":false,
2148 "removable":true,
2149 "type":"unknown"
2152 "device":"sd0",
2153 "locked":false,
2154 "removable":true,
2155 "type":"unknown"
2160 EQMP
2163 .name = "query-block",
2164 .args_type = "",
2165 .mhandler.cmd_new = qmp_marshal_input_query_block,
2168 SQMP
2169 query-blockstats
2170 ----------------
2172 Show block device statistics.
2174 Each device statistic information is stored in a json-object and the returned
2175 value is a json-array of all devices.
2177 Each json-object contain the following:
2179 - "device": device name (json-string)
2180 - "stats": A json-object with the statistics information, it contains:
2181 - "rd_bytes": bytes read (json-int)
2182 - "wr_bytes": bytes written (json-int)
2183 - "rd_operations": read operations (json-int)
2184 - "wr_operations": write operations (json-int)
2185 - "flush_operations": cache flush operations (json-int)
2186 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
2187 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
2188 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
2189 - "wr_highest_offset": Highest offset of a sector written since the
2190 BlockDriverState has been opened (json-int)
2191 - "parent": Contains recursively the statistics of the underlying
2192 protocol (e.g. the host file for a qcow2 image). If there is
2193 no underlying protocol, this field is omitted
2194 (json-object, optional)
2196 Example:
2198 -> { "execute": "query-blockstats" }
2199 <- {
2200 "return":[
2202 "device":"ide0-hd0",
2203 "parent":{
2204 "stats":{
2205 "wr_highest_offset":3686448128,
2206 "wr_bytes":9786368,
2207 "wr_operations":751,
2208 "rd_bytes":122567168,
2209 "rd_operations":36772
2210 "wr_total_times_ns":313253456
2211 "rd_total_times_ns":3465673657
2212 "flush_total_times_ns":49653
2213 "flush_operations":61,
2216 "stats":{
2217 "wr_highest_offset":2821110784,
2218 "wr_bytes":9786368,
2219 "wr_operations":692,
2220 "rd_bytes":122739200,
2221 "rd_operations":36604
2222 "flush_operations":51,
2223 "wr_total_times_ns":313253456
2224 "rd_total_times_ns":3465673657
2225 "flush_total_times_ns":49653
2229 "device":"ide1-cd0",
2230 "stats":{
2231 "wr_highest_offset":0,
2232 "wr_bytes":0,
2233 "wr_operations":0,
2234 "rd_bytes":0,
2235 "rd_operations":0
2236 "flush_operations":0,
2237 "wr_total_times_ns":0
2238 "rd_total_times_ns":0
2239 "flush_total_times_ns":0
2243 "device":"floppy0",
2244 "stats":{
2245 "wr_highest_offset":0,
2246 "wr_bytes":0,
2247 "wr_operations":0,
2248 "rd_bytes":0,
2249 "rd_operations":0
2250 "flush_operations":0,
2251 "wr_total_times_ns":0
2252 "rd_total_times_ns":0
2253 "flush_total_times_ns":0
2257 "device":"sd0",
2258 "stats":{
2259 "wr_highest_offset":0,
2260 "wr_bytes":0,
2261 "wr_operations":0,
2262 "rd_bytes":0,
2263 "rd_operations":0
2264 "flush_operations":0,
2265 "wr_total_times_ns":0
2266 "rd_total_times_ns":0
2267 "flush_total_times_ns":0
2273 EQMP
2276 .name = "query-blockstats",
2277 .args_type = "",
2278 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
2281 SQMP
2282 query-cpus
2283 ----------
2285 Show CPU information.
2287 Return a json-array. Each CPU is represented by a json-object, which contains:
2289 - "CPU": CPU index (json-int)
2290 - "current": true if this is the current CPU, false otherwise (json-bool)
2291 - "halted": true if the cpu is halted, false otherwise (json-bool)
2292 - Current program counter. The key's name depends on the architecture:
2293 "pc": i386/x86_64 (json-int)
2294 "nip": PPC (json-int)
2295 "pc" and "npc": sparc (json-int)
2296 "PC": mips (json-int)
2297 - "thread_id": ID of the underlying host thread (json-int)
2299 Example:
2301 -> { "execute": "query-cpus" }
2302 <- {
2303 "return":[
2305 "CPU":0,
2306 "current":true,
2307 "halted":false,
2308 "pc":3227107138
2309 "thread_id":3134
2312 "CPU":1,
2313 "current":false,
2314 "halted":true,
2315 "pc":7108165
2316 "thread_id":3135
2321 EQMP
2324 .name = "query-cpus",
2325 .args_type = "",
2326 .mhandler.cmd_new = qmp_marshal_input_query_cpus,
2329 SQMP
2330 query-pci
2331 ---------
2333 PCI buses and devices information.
2335 The returned value is a json-array of all buses. Each bus is represented by
2336 a json-object, which has a key with a json-array of all PCI devices attached
2337 to it. Each device is represented by a json-object.
2339 The bus json-object contains the following:
2341 - "bus": bus number (json-int)
2342 - "devices": a json-array of json-objects, each json-object represents a
2343 PCI device
2345 The PCI device json-object contains the following:
2347 - "bus": identical to the parent's bus number (json-int)
2348 - "slot": slot number (json-int)
2349 - "function": function number (json-int)
2350 - "class_info": a json-object containing:
2351 - "desc": device class description (json-string, optional)
2352 - "class": device class number (json-int)
2353 - "id": a json-object containing:
2354 - "device": device ID (json-int)
2355 - "vendor": vendor ID (json-int)
2356 - "irq": device's IRQ if assigned (json-int, optional)
2357 - "qdev_id": qdev id string (json-string)
2358 - "pci_bridge": It's a json-object, only present if this device is a
2359 PCI bridge, contains:
2360 - "bus": bus number (json-int)
2361 - "secondary": secondary bus number (json-int)
2362 - "subordinate": subordinate bus number (json-int)
2363 - "io_range": I/O memory range information, a json-object with the
2364 following members:
2365 - "base": base address, in bytes (json-int)
2366 - "limit": limit address, in bytes (json-int)
2367 - "memory_range": memory range information, a json-object with the
2368 following members:
2369 - "base": base address, in bytes (json-int)
2370 - "limit": limit address, in bytes (json-int)
2371 - "prefetchable_range": Prefetchable memory range information, a
2372 json-object with the following members:
2373 - "base": base address, in bytes (json-int)
2374 - "limit": limit address, in bytes (json-int)
2375 - "devices": a json-array of PCI devices if there's any attached, each
2376 each element is represented by a json-object, which contains
2377 the same members of the 'PCI device json-object' described
2378 above (optional)
2379 - "regions": a json-array of json-objects, each json-object represents a
2380 memory region of this device
2382 The memory range json-object contains the following:
2384 - "base": base memory address (json-int)
2385 - "limit": limit value (json-int)
2387 The region json-object can be an I/O region or a memory region, an I/O region
2388 json-object contains the following:
2390 - "type": "io" (json-string, fixed)
2391 - "bar": BAR number (json-int)
2392 - "address": memory address (json-int)
2393 - "size": memory size (json-int)
2395 A memory region json-object contains the following:
2397 - "type": "memory" (json-string, fixed)
2398 - "bar": BAR number (json-int)
2399 - "address": memory address (json-int)
2400 - "size": memory size (json-int)
2401 - "mem_type_64": true or false (json-bool)
2402 - "prefetch": true or false (json-bool)
2404 Example:
2406 -> { "execute": "query-pci" }
2407 <- {
2408 "return":[
2410 "bus":0,
2411 "devices":[
2413 "bus":0,
2414 "qdev_id":"",
2415 "slot":0,
2416 "class_info":{
2417 "class":1536,
2418 "desc":"Host bridge"
2420 "id":{
2421 "device":32902,
2422 "vendor":4663
2424 "function":0,
2425 "regions":[
2430 "bus":0,
2431 "qdev_id":"",
2432 "slot":1,
2433 "class_info":{
2434 "class":1537,
2435 "desc":"ISA bridge"
2437 "id":{
2438 "device":32902,
2439 "vendor":28672
2441 "function":0,
2442 "regions":[
2447 "bus":0,
2448 "qdev_id":"",
2449 "slot":1,
2450 "class_info":{
2451 "class":257,
2452 "desc":"IDE controller"
2454 "id":{
2455 "device":32902,
2456 "vendor":28688
2458 "function":1,
2459 "regions":[
2461 "bar":4,
2462 "size":16,
2463 "address":49152,
2464 "type":"io"
2469 "bus":0,
2470 "qdev_id":"",
2471 "slot":2,
2472 "class_info":{
2473 "class":768,
2474 "desc":"VGA controller"
2476 "id":{
2477 "device":4115,
2478 "vendor":184
2480 "function":0,
2481 "regions":[
2483 "prefetch":true,
2484 "mem_type_64":false,
2485 "bar":0,
2486 "size":33554432,
2487 "address":4026531840,
2488 "type":"memory"
2491 "prefetch":false,
2492 "mem_type_64":false,
2493 "bar":1,
2494 "size":4096,
2495 "address":4060086272,
2496 "type":"memory"
2499 "prefetch":false,
2500 "mem_type_64":false,
2501 "bar":6,
2502 "size":65536,
2503 "address":-1,
2504 "type":"memory"
2509 "bus":0,
2510 "qdev_id":"",
2511 "irq":11,
2512 "slot":4,
2513 "class_info":{
2514 "class":1280,
2515 "desc":"RAM controller"
2517 "id":{
2518 "device":6900,
2519 "vendor":4098
2521 "function":0,
2522 "regions":[
2524 "bar":0,
2525 "size":32,
2526 "address":49280,
2527 "type":"io"
2536 Note: This example has been shortened as the real response is too long.
2538 EQMP
2541 .name = "query-pci",
2542 .args_type = "",
2543 .mhandler.cmd_new = qmp_marshal_input_query_pci,
2546 SQMP
2547 query-kvm
2548 ---------
2550 Show KVM information.
2552 Return a json-object with the following information:
2554 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
2555 - "present": true if QEMU has KVM support, false otherwise (json-bool)
2557 Example:
2559 -> { "execute": "query-kvm" }
2560 <- { "return": { "enabled": true, "present": true } }
2562 EQMP
2565 .name = "query-kvm",
2566 .args_type = "",
2567 .mhandler.cmd_new = qmp_marshal_input_query_kvm,
2570 SQMP
2571 query-status
2572 ------------
2574 Return a json-object with the following information:
2576 - "running": true if the VM is running, or false if it is paused (json-bool)
2577 - "singlestep": true if the VM is in single step mode,
2578 false otherwise (json-bool)
2579 - "status": one of the following values (json-string)
2580 "debug" - QEMU is running on a debugger
2581 "inmigrate" - guest is paused waiting for an incoming migration
2582 "internal-error" - An internal error that prevents further guest
2583 execution has occurred
2584 "io-error" - the last IOP has failed and the device is configured
2585 to pause on I/O errors
2586 "paused" - guest has been paused via the 'stop' command
2587 "postmigrate" - guest is paused following a successful 'migrate'
2588 "prelaunch" - QEMU was started with -S and guest has not started
2589 "finish-migrate" - guest is paused to finish the migration process
2590 "restore-vm" - guest is paused to restore VM state
2591 "running" - guest is actively running
2592 "save-vm" - guest is paused to save the VM state
2593 "shutdown" - guest is shut down (and -no-shutdown is in use)
2594 "watchdog" - the watchdog action is configured to pause and
2595 has been triggered
2597 Example:
2599 -> { "execute": "query-status" }
2600 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
2602 EQMP
2605 .name = "query-status",
2606 .args_type = "",
2607 .mhandler.cmd_new = qmp_marshal_input_query_status,
2610 SQMP
2611 query-mice
2612 ----------
2614 Show VM mice information.
2616 Each mouse is represented by a json-object, the returned value is a json-array
2617 of all mice.
2619 The mouse json-object contains the following:
2621 - "name": mouse's name (json-string)
2622 - "index": mouse's index (json-int)
2623 - "current": true if this mouse is receiving events, false otherwise (json-bool)
2624 - "absolute": true if the mouse generates absolute input events (json-bool)
2626 Example:
2628 -> { "execute": "query-mice" }
2629 <- {
2630 "return":[
2632 "name":"QEMU Microsoft Mouse",
2633 "index":0,
2634 "current":false,
2635 "absolute":false
2638 "name":"QEMU PS/2 Mouse",
2639 "index":1,
2640 "current":true,
2641 "absolute":true
2646 EQMP
2649 .name = "query-mice",
2650 .args_type = "",
2651 .mhandler.cmd_new = qmp_marshal_input_query_mice,
2654 SQMP
2655 query-vnc
2656 ---------
2658 Show VNC server information.
2660 Return a json-object with server information. Connected clients are returned
2661 as a json-array of json-objects.
2663 The main json-object contains the following:
2665 - "enabled": true or false (json-bool)
2666 - "host": server's IP address (json-string)
2667 - "family": address family (json-string)
2668 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2669 - "service": server's port number (json-string)
2670 - "auth": authentication method (json-string)
2671 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
2672 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
2673 "vencrypt+plain", "vencrypt+tls+none",
2674 "vencrypt+tls+plain", "vencrypt+tls+sasl",
2675 "vencrypt+tls+vnc", "vencrypt+x509+none",
2676 "vencrypt+x509+plain", "vencrypt+x509+sasl",
2677 "vencrypt+x509+vnc", "vnc"
2678 - "clients": a json-array of all connected clients
2680 Clients are described by a json-object, each one contain the following:
2682 - "host": client's IP address (json-string)
2683 - "family": address family (json-string)
2684 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2685 - "service": client's port number (json-string)
2686 - "x509_dname": TLS dname (json-string, optional)
2687 - "sasl_username": SASL username (json-string, optional)
2689 Example:
2691 -> { "execute": "query-vnc" }
2692 <- {
2693 "return":{
2694 "enabled":true,
2695 "host":"0.0.0.0",
2696 "service":"50402",
2697 "auth":"vnc",
2698 "family":"ipv4",
2699 "clients":[
2701 "host":"127.0.0.1",
2702 "service":"50401",
2703 "family":"ipv4"
2709 EQMP
2712 .name = "query-vnc",
2713 .args_type = "",
2714 .mhandler.cmd_new = qmp_marshal_input_query_vnc,
2717 SQMP
2718 query-spice
2719 -----------
2721 Show SPICE server information.
2723 Return a json-object with server information. Connected clients are returned
2724 as a json-array of json-objects.
2726 The main json-object contains the following:
2728 - "enabled": true or false (json-bool)
2729 - "host": server's IP address (json-string)
2730 - "port": server's port number (json-int, optional)
2731 - "tls-port": server's port number (json-int, optional)
2732 - "auth": authentication method (json-string)
2733 - Possible values: "none", "spice"
2734 - "channels": a json-array of all active channels clients
2736 Channels are described by a json-object, each one contain the following:
2738 - "host": client's IP address (json-string)
2739 - "family": address family (json-string)
2740 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2741 - "port": client's port number (json-string)
2742 - "connection-id": spice connection id. All channels with the same id
2743 belong to the same spice session (json-int)
2744 - "channel-type": channel type. "1" is the main control channel, filter for
2745 this one if you want track spice sessions only (json-int)
2746 - "channel-id": channel id. Usually "0", might be different needed when
2747 multiple channels of the same type exist, such as multiple
2748 display channels in a multihead setup (json-int)
2749 - "tls": whevener the channel is encrypted (json-bool)
2751 Example:
2753 -> { "execute": "query-spice" }
2754 <- {
2755 "return": {
2756 "enabled": true,
2757 "auth": "spice",
2758 "port": 5920,
2759 "tls-port": 5921,
2760 "host": "0.0.0.0",
2761 "channels": [
2763 "port": "54924",
2764 "family": "ipv4",
2765 "channel-type": 1,
2766 "connection-id": 1804289383,
2767 "host": "127.0.0.1",
2768 "channel-id": 0,
2769 "tls": true
2772 "port": "36710",
2773 "family": "ipv4",
2774 "channel-type": 4,
2775 "connection-id": 1804289383,
2776 "host": "127.0.0.1",
2777 "channel-id": 0,
2778 "tls": false
2780 [ ... more channels follow ... ]
2785 EQMP
2787 #if defined(CONFIG_SPICE)
2789 .name = "query-spice",
2790 .args_type = "",
2791 .mhandler.cmd_new = qmp_marshal_input_query_spice,
2793 #endif
2795 SQMP
2796 query-name
2797 ----------
2799 Show VM name.
2801 Return a json-object with the following information:
2803 - "name": VM's name (json-string, optional)
2805 Example:
2807 -> { "execute": "query-name" }
2808 <- { "return": { "name": "qemu-name" } }
2810 EQMP
2813 .name = "query-name",
2814 .args_type = "",
2815 .mhandler.cmd_new = qmp_marshal_input_query_name,
2818 SQMP
2819 query-uuid
2820 ----------
2822 Show VM UUID.
2824 Return a json-object with the following information:
2826 - "UUID": Universally Unique Identifier (json-string)
2828 Example:
2830 -> { "execute": "query-uuid" }
2831 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
2833 EQMP
2836 .name = "query-uuid",
2837 .args_type = "",
2838 .mhandler.cmd_new = qmp_marshal_input_query_uuid,
2841 SQMP
2842 query-command-line-options
2843 --------------------------
2845 Show command line option schema.
2847 Return a json-array of command line option schema for all options (or for
2848 the given option), returning an error if the given option doesn't exist.
2850 Each array entry contains the following:
2852 - "option": option name (json-string)
2853 - "parameters": a json-array describes all parameters of the option:
2854 - "name": parameter name (json-string)
2855 - "type": parameter type (one of 'string', 'boolean', 'number',
2856 or 'size')
2857 - "help": human readable description of the parameter
2858 (json-string, optional)
2860 Example:
2862 -> { "execute": "query-command-line-options", "arguments": { "option": "option-rom" } }
2863 <- { "return": [
2865 "parameters": [
2867 "name": "romfile",
2868 "type": "string"
2871 "name": "bootindex",
2872 "type": "number"
2875 "option": "option-rom"
2880 EQMP
2883 .name = "query-command-line-options",
2884 .args_type = "option:s?",
2885 .mhandler.cmd_new = qmp_marshal_input_query_command_line_options,
2888 SQMP
2889 query-migrate
2890 -------------
2892 Migration status.
2894 Return a json-object. If migration is active there will be another json-object
2895 with RAM migration status and if block migration is active another one with
2896 block migration status.
2898 The main json-object contains the following:
2900 - "status": migration status (json-string)
2901 - Possible values: "active", "completed", "failed", "cancelled"
2902 - "total-time": total amount of ms since migration started. If
2903 migration has ended, it returns the total migration
2904 time (json-int)
2905 - "setup-time" amount of setup time in milliseconds _before_ the
2906 iterations begin but _after_ the QMP command is issued.
2907 This is designed to provide an accounting of any activities
2908 (such as RDMA pinning) which may be expensive, but do not
2909 actually occur during the iterative migration rounds
2910 themselves. (json-int)
2911 - "downtime": only present when migration has finished correctly
2912 total amount in ms for downtime that happened (json-int)
2913 - "expected-downtime": only present while migration is active
2914 total amount in ms for downtime that was calculated on
2915 the last bitmap round (json-int)
2916 - "ram": only present if "status" is "active", it is a json-object with the
2917 following RAM information:
2918 - "transferred": amount transferred in bytes (json-int)
2919 - "remaining": amount remaining to transfer in bytes (json-int)
2920 - "total": total amount of memory in bytes (json-int)
2921 - "duplicate": number of pages filled entirely with the same
2922 byte (json-int)
2923 These are sent over the wire much more efficiently.
2924 - "skipped": number of skipped zero pages (json-int)
2925 - "normal" : number of whole pages transferred. I.e. they
2926 were not sent as duplicate or xbzrle pages (json-int)
2927 - "normal-bytes" : number of bytes transferred in whole
2928 pages. This is just normal pages times size of one page,
2929 but this way upper levels don't need to care about page
2930 size (json-int)
2931 - "disk": only present if "status" is "active" and it is a block migration,
2932 it is a json-object with the following disk information:
2933 - "transferred": amount transferred in bytes (json-int)
2934 - "remaining": amount remaining to transfer in bytes json-int)
2935 - "total": total disk size in bytes (json-int)
2936 - "xbzrle-cache": only present if XBZRLE is active.
2937 It is a json-object with the following XBZRLE information:
2938 - "cache-size": XBZRLE cache size in bytes
2939 - "bytes": number of bytes transferred for XBZRLE compressed pages
2940 - "pages": number of XBZRLE compressed pages
2941 - "cache-miss": number of XBRZRLE page cache misses
2942 - "overflow": number of times XBZRLE overflows. This means
2943 that the XBZRLE encoding was bigger than just sent the
2944 whole page, and then we sent the whole page instead (as as
2945 normal page).
2947 Examples:
2949 1. Before the first migration
2951 -> { "execute": "query-migrate" }
2952 <- { "return": {} }
2954 2. Migration is done and has succeeded
2956 -> { "execute": "query-migrate" }
2957 <- { "return": {
2958 "status": "completed",
2959 "ram":{
2960 "transferred":123,
2961 "remaining":123,
2962 "total":246,
2963 "total-time":12345,
2964 "setup-time":12345,
2965 "downtime":12345,
2966 "duplicate":123,
2967 "normal":123,
2968 "normal-bytes":123456
2973 3. Migration is done and has failed
2975 -> { "execute": "query-migrate" }
2976 <- { "return": { "status": "failed" } }
2978 4. Migration is being performed and is not a block migration:
2980 -> { "execute": "query-migrate" }
2981 <- {
2982 "return":{
2983 "status":"active",
2984 "ram":{
2985 "transferred":123,
2986 "remaining":123,
2987 "total":246,
2988 "total-time":12345,
2989 "setup-time":12345,
2990 "expected-downtime":12345,
2991 "duplicate":123,
2992 "normal":123,
2993 "normal-bytes":123456
2998 5. Migration is being performed and is a block migration:
3000 -> { "execute": "query-migrate" }
3001 <- {
3002 "return":{
3003 "status":"active",
3004 "ram":{
3005 "total":1057024,
3006 "remaining":1053304,
3007 "transferred":3720,
3008 "total-time":12345,
3009 "setup-time":12345,
3010 "expected-downtime":12345,
3011 "duplicate":123,
3012 "normal":123,
3013 "normal-bytes":123456
3015 "disk":{
3016 "total":20971520,
3017 "remaining":20880384,
3018 "transferred":91136
3023 6. Migration is being performed and XBZRLE is active:
3025 -> { "execute": "query-migrate" }
3026 <- {
3027 "return":{
3028 "status":"active",
3029 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
3030 "ram":{
3031 "total":1057024,
3032 "remaining":1053304,
3033 "transferred":3720,
3034 "total-time":12345,
3035 "setup-time":12345,
3036 "expected-downtime":12345,
3037 "duplicate":10,
3038 "normal":3333,
3039 "normal-bytes":3412992
3041 "xbzrle-cache":{
3042 "cache-size":67108864,
3043 "bytes":20971520,
3044 "pages":2444343,
3045 "cache-miss":2244,
3046 "overflow":34434
3051 EQMP
3054 .name = "query-migrate",
3055 .args_type = "",
3056 .mhandler.cmd_new = qmp_marshal_input_query_migrate,
3059 SQMP
3060 migrate-set-capabilities
3061 ------------------------
3063 Enable/Disable migration capabilities
3065 - "xbzrle": XBZRLE support
3067 Arguments:
3069 Example:
3071 -> { "execute": "migrate-set-capabilities" , "arguments":
3072 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
3074 EQMP
3077 .name = "migrate-set-capabilities",
3078 .args_type = "capabilities:O",
3079 .params = "capability:s,state:b",
3080 .mhandler.cmd_new = qmp_marshal_input_migrate_set_capabilities,
3082 SQMP
3083 query-migrate-capabilities
3084 --------------------------
3086 Query current migration capabilities
3088 - "capabilities": migration capabilities state
3089 - "xbzrle" : XBZRLE state (json-bool)
3091 Arguments:
3093 Example:
3095 -> { "execute": "query-migrate-capabilities" }
3096 <- { "return": [ { "state": false, "capability": "xbzrle" } ] }
3098 EQMP
3101 .name = "query-migrate-capabilities",
3102 .args_type = "",
3103 .mhandler.cmd_new = qmp_marshal_input_query_migrate_capabilities,
3106 SQMP
3107 query-balloon
3108 -------------
3110 Show balloon information.
3112 Make an asynchronous request for balloon info. When the request completes a
3113 json-object will be returned containing the following data:
3115 - "actual": current balloon value in bytes (json-int)
3117 Example:
3119 -> { "execute": "query-balloon" }
3120 <- {
3121 "return":{
3122 "actual":1073741824,
3126 EQMP
3129 .name = "query-balloon",
3130 .args_type = "",
3131 .mhandler.cmd_new = qmp_marshal_input_query_balloon,
3135 .name = "query-block-jobs",
3136 .args_type = "",
3137 .mhandler.cmd_new = qmp_marshal_input_query_block_jobs,
3141 .name = "qom-list",
3142 .args_type = "path:s",
3143 .mhandler.cmd_new = qmp_marshal_input_qom_list,
3147 .name = "qom-set",
3148 .args_type = "path:s,property:s,value:q",
3149 .mhandler.cmd_new = qmp_qom_set,
3153 .name = "qom-get",
3154 .args_type = "path:s,property:s",
3155 .mhandler.cmd_new = qmp_qom_get,
3159 .name = "nbd-server-start",
3160 .args_type = "addr:q",
3161 .mhandler.cmd_new = qmp_marshal_input_nbd_server_start,
3164 .name = "nbd-server-add",
3165 .args_type = "device:B,writable:b?",
3166 .mhandler.cmd_new = qmp_marshal_input_nbd_server_add,
3169 .name = "nbd-server-stop",
3170 .args_type = "",
3171 .mhandler.cmd_new = qmp_marshal_input_nbd_server_stop,
3175 .name = "change-vnc-password",
3176 .args_type = "password:s",
3177 .mhandler.cmd_new = qmp_marshal_input_change_vnc_password,
3180 .name = "qom-list-types",
3181 .args_type = "implements:s?,abstract:b?",
3182 .mhandler.cmd_new = qmp_marshal_input_qom_list_types,
3186 .name = "device-list-properties",
3187 .args_type = "typename:s",
3188 .mhandler.cmd_new = qmp_marshal_input_device_list_properties,
3192 .name = "query-machines",
3193 .args_type = "",
3194 .mhandler.cmd_new = qmp_marshal_input_query_machines,
3198 .name = "query-cpu-definitions",
3199 .args_type = "",
3200 .mhandler.cmd_new = qmp_marshal_input_query_cpu_definitions,
3204 .name = "query-target",
3205 .args_type = "",
3206 .mhandler.cmd_new = qmp_marshal_input_query_target,
3210 .name = "query-tpm",
3211 .args_type = "",
3212 .mhandler.cmd_new = qmp_marshal_input_query_tpm,
3215 SQMP
3216 query-tpm
3217 ---------
3219 Return information about the TPM device.
3221 Arguments: None
3223 Example:
3225 -> { "execute": "query-tpm" }
3226 <- { "return":
3228 { "model": "tpm-tis",
3229 "options":
3230 { "type": "passthrough",
3231 "data":
3232 { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
3233 "path": "/dev/tpm0"
3236 "id": "tpm0"
3241 EQMP
3244 .name = "query-tpm-models",
3245 .args_type = "",
3246 .mhandler.cmd_new = qmp_marshal_input_query_tpm_models,
3249 SQMP
3250 query-tpm-models
3251 ----------------
3253 Return a list of supported TPM models.
3255 Arguments: None
3257 Example:
3259 -> { "execute": "query-tpm-models" }
3260 <- { "return": [ "tpm-tis" ] }
3262 EQMP
3265 .name = "query-tpm-types",
3266 .args_type = "",
3267 .mhandler.cmd_new = qmp_marshal_input_query_tpm_types,
3270 SQMP
3271 query-tpm-types
3272 ---------------
3274 Return a list of supported TPM types.
3276 Arguments: None
3278 Example:
3280 -> { "execute": "query-tpm-types" }
3281 <- { "return": [ "passthrough" ] }
3283 EQMP
3286 .name = "chardev-add",
3287 .args_type = "id:s,backend:q",
3288 .mhandler.cmd_new = qmp_marshal_input_chardev_add,
3291 SQMP
3292 chardev-add
3293 ----------------
3295 Add a chardev.
3297 Arguments:
3299 - "id": the chardev's ID, must be unique (json-string)
3300 - "backend": chardev backend type + parameters
3302 Examples:
3304 -> { "execute" : "chardev-add",
3305 "arguments" : { "id" : "foo",
3306 "backend" : { "type" : "null", "data" : {} } } }
3307 <- { "return": {} }
3309 -> { "execute" : "chardev-add",
3310 "arguments" : { "id" : "bar",
3311 "backend" : { "type" : "file",
3312 "data" : { "out" : "/tmp/bar.log" } } } }
3313 <- { "return": {} }
3315 -> { "execute" : "chardev-add",
3316 "arguments" : { "id" : "baz",
3317 "backend" : { "type" : "pty", "data" : {} } } }
3318 <- { "return": { "pty" : "/dev/pty/42" } }
3320 EQMP
3323 .name = "chardev-remove",
3324 .args_type = "id:s",
3325 .mhandler.cmd_new = qmp_marshal_input_chardev_remove,
3329 SQMP
3330 chardev-remove
3331 --------------
3333 Remove a chardev.
3335 Arguments:
3337 - "id": the chardev's ID, must exist and not be in use (json-string)
3339 Example:
3341 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }
3342 <- { "return": {} }
3344 EQMP
3346 .name = "query-rx-filter",
3347 .args_type = "name:s?",
3348 .mhandler.cmd_new = qmp_marshal_input_query_rx_filter,
3351 SQMP
3352 query-rx-filter
3353 ---------------
3355 Show rx-filter information.
3357 Returns a json-array of rx-filter information for all NICs (or for the
3358 given NIC), returning an error if the given NIC doesn't exist, or
3359 given NIC doesn't support rx-filter querying, or given net client
3360 isn't a NIC.
3362 The query will clear the event notification flag of each NIC, then qemu
3363 will start to emit event to QMP monitor.
3365 Each array entry contains the following:
3367 - "name": net client name (json-string)
3368 - "promiscuous": promiscuous mode is enabled (json-bool)
3369 - "multicast": multicast receive state (one of 'normal', 'none', 'all')
3370 - "unicast": unicast receive state (one of 'normal', 'none', 'all')
3371 - "broadcast-allowed": allow to receive broadcast (json-bool)
3372 - "multicast-overflow": multicast table is overflowed (json-bool)
3373 - "unicast-overflow": unicast table is overflowed (json-bool)
3374 - "main-mac": main macaddr string (json-string)
3375 - "vlan-table": a json-array of active vlan id
3376 - "unicast-table": a json-array of unicast macaddr string
3377 - "multicast-table": a json-array of multicast macaddr string
3379 Example:
3381 -> { "execute": "query-rx-filter", "arguments": { "name": "vnet0" } }
3382 <- { "return": [
3384 "promiscuous": true,
3385 "name": "vnet0",
3386 "main-mac": "52:54:00:12:34:56",
3387 "unicast": "normal",
3388 "vlan-table": [
3392 "unicast-table": [
3394 "multicast": "normal",
3395 "multicast-overflow": false,
3396 "unicast-overflow": false,
3397 "multicast-table": [
3398 "01:00:5e:00:00:01",
3399 "33:33:00:00:00:01",
3400 "33:33:ff:12:34:56"
3402 "broadcast-allowed": false
3407 EQMP
3410 .name = "blockdev-add",
3411 .args_type = "options:q",
3412 .mhandler.cmd_new = qmp_marshal_input_blockdev_add,
3415 SQMP
3416 blockdev-add
3417 ------------
3419 Add a block device.
3421 Arguments:
3423 - "options": block driver options
3425 Example (1):
3427 -> { "execute": "blockdev-add",
3428 "arguments": { "options" : { "driver": "qcow2",
3429 "file": { "driver": "file",
3430 "filename": "test.qcow2" } } } }
3431 <- { "return": {} }
3433 Example (2):
3435 -> { "execute": "blockdev-add",
3436 "arguments": {
3437 "options": {
3438 "driver": "qcow2",
3439 "id": "my_disk",
3440 "discard": "unmap",
3441 "cache": {
3442 "direct": true,
3443 "writeback": true
3445 "file": {
3446 "driver": "file",
3447 "filename": "/tmp/test.qcow2"
3449 "backing": {
3450 "driver": "raw",
3451 "file": {
3452 "driver": "file",
3453 "filename": "/dev/fdset/4"
3460 <- { "return": {} }
3462 EQMP
3465 .name = "query-named-block-nodes",
3466 .args_type = "",
3467 .mhandler.cmd_new = qmp_marshal_input_query_named_block_nodes,
3470 SQMP
3471 @query-named-block-nodes
3472 ------------------------
3474 Return a list of BlockDeviceInfo for all the named block driver nodes
3476 Example:
3478 -> { "execute": "query-named-block-nodes" }
3479 <- { "return": [ { "ro":false,
3480 "drv":"qcow2",
3481 "encrypted":false,
3482 "file":"disks/test.qcow2",
3483 "node-name": "my-node",
3484 "backing_file_depth":1,
3485 "bps":1000000,
3486 "bps_rd":0,
3487 "bps_wr":0,
3488 "iops":1000000,
3489 "iops_rd":0,
3490 "iops_wr":0,
3491 "bps_max": 8000000,
3492 "bps_rd_max": 0,
3493 "bps_wr_max": 0,
3494 "iops_max": 0,
3495 "iops_rd_max": 0,
3496 "iops_wr_max": 0,
3497 "iops_size": 0,
3498 "image":{
3499 "filename":"disks/test.qcow2",
3500 "format":"qcow2",
3501 "virtual-size":2048000,
3502 "backing_file":"base.qcow2",
3503 "full-backing-filename":"disks/base.qcow2",
3504 "backing-filename-format:"qcow2",
3505 "snapshots":[
3507 "id": "1",
3508 "name": "snapshot1",
3509 "vm-state-size": 0,
3510 "date-sec": 10000200,
3511 "date-nsec": 12,
3512 "vm-clock-sec": 206,
3513 "vm-clock-nsec": 30
3516 "backing-image":{
3517 "filename":"disks/base.qcow2",
3518 "format":"qcow2",
3519 "virtual-size":2048000
3521 } } ] }
3523 EQMP