ui: Make qemu_default_pixman_format() return 0 on unsupported formats
[qemu/kevin.git] / qmp-commands.hx
blob8957201f73ae14148652085f7c8b1e7bd1124699
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 the default CPU (x86/s390) or all CPUs (ppc64).
482 Arguments: None.
484 Example:
486 -> { "execute": "inject-nmi" }
487 <- { "return": {} }
489 Note: inject-nmi fails when the guest doesn't support injecting.
491 EQMP
494 .name = "ringbuf-write",
495 .args_type = "device:s,data:s,format:s?",
496 .mhandler.cmd_new = qmp_marshal_input_ringbuf_write,
499 SQMP
500 ringbuf-write
501 -------------
503 Write to a ring buffer character device.
505 Arguments:
507 - "device": ring buffer character device name (json-string)
508 - "data": data to write (json-string)
509 - "format": data format (json-string, optional)
510 - Possible values: "utf8" (default), "base64"
511 Bug: invalid base64 is currently not rejected.
512 Whitespace *is* invalid.
514 Example:
516 -> { "execute": "ringbuf-write",
517 "arguments": { "device": "foo",
518 "data": "abcdefgh",
519 "format": "utf8" } }
520 <- { "return": {} }
522 EQMP
525 .name = "ringbuf-read",
526 .args_type = "device:s,size:i,format:s?",
527 .mhandler.cmd_new = qmp_marshal_input_ringbuf_read,
530 SQMP
531 ringbuf-read
532 -------------
534 Read from a ring buffer character device.
536 Arguments:
538 - "device": ring buffer character device name (json-string)
539 - "size": how many bytes to read at most (json-int)
540 - Number of data bytes, not number of characters in encoded data
541 - "format": data format (json-string, optional)
542 - Possible values: "utf8" (default), "base64"
543 - Naturally, format "utf8" works only when the ring buffer
544 contains valid UTF-8 text. Invalid UTF-8 sequences get
545 replaced. Bug: replacement doesn't work. Bug: can screw
546 up on encountering NUL characters, after the ring buffer
547 lost data, and when reading stops because the size limit
548 is reached.
550 Example:
552 -> { "execute": "ringbuf-read",
553 "arguments": { "device": "foo",
554 "size": 1000,
555 "format": "utf8" } }
556 <- {"return": "abcdefgh"}
558 EQMP
561 .name = "xen-save-devices-state",
562 .args_type = "filename:F",
563 .mhandler.cmd_new = qmp_marshal_input_xen_save_devices_state,
566 SQMP
567 xen-save-devices-state
568 -------
570 Save the state of all devices to file. The RAM and the block devices
571 of the VM are not saved by this command.
573 Arguments:
575 - "filename": the file to save the state of the devices to as binary
576 data. See xen-save-devices-state.txt for a description of the binary
577 format.
579 Example:
581 -> { "execute": "xen-save-devices-state",
582 "arguments": { "filename": "/tmp/save" } }
583 <- { "return": {} }
585 EQMP
588 .name = "xen-set-global-dirty-log",
589 .args_type = "enable:b",
590 .mhandler.cmd_new = qmp_marshal_input_xen_set_global_dirty_log,
593 SQMP
594 xen-set-global-dirty-log
595 -------
597 Enable or disable the global dirty log mode.
599 Arguments:
601 - "enable": Enable it or disable it.
603 Example:
605 -> { "execute": "xen-set-global-dirty-log",
606 "arguments": { "enable": true } }
607 <- { "return": {} }
609 EQMP
612 .name = "migrate",
613 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
614 .mhandler.cmd_new = qmp_marshal_input_migrate,
617 SQMP
618 migrate
619 -------
621 Migrate to URI.
623 Arguments:
625 - "blk": block migration, full disk copy (json-bool, optional)
626 - "inc": incremental disk copy (json-bool, optional)
627 - "uri": Destination URI (json-string)
629 Example:
631 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
632 <- { "return": {} }
634 Notes:
636 (1) The 'query-migrate' command should be used to check migration's progress
637 and final result (this information is provided by the 'status' member)
638 (2) All boolean arguments default to false
639 (3) The user Monitor's "detach" argument is invalid in QMP and should not
640 be used
642 EQMP
645 .name = "migrate_cancel",
646 .args_type = "",
647 .mhandler.cmd_new = qmp_marshal_input_migrate_cancel,
650 SQMP
651 migrate_cancel
652 --------------
654 Cancel the current migration.
656 Arguments: None.
658 Example:
660 -> { "execute": "migrate_cancel" }
661 <- { "return": {} }
663 EQMP
665 .name = "migrate-set-cache-size",
666 .args_type = "value:o",
667 .mhandler.cmd_new = qmp_marshal_input_migrate_set_cache_size,
670 SQMP
671 migrate-set-cache-size
672 ----------------------
674 Set cache size to be used by XBZRLE migration, the cache size will be rounded
675 down to the nearest power of 2
677 Arguments:
679 - "value": cache size in bytes (json-int)
681 Example:
683 -> { "execute": "migrate-set-cache-size", "arguments": { "value": 536870912 } }
684 <- { "return": {} }
686 EQMP
688 .name = "query-migrate-cache-size",
689 .args_type = "",
690 .mhandler.cmd_new = qmp_marshal_input_query_migrate_cache_size,
693 SQMP
694 query-migrate-cache-size
695 ------------------------
697 Show cache size to be used by XBZRLE migration
699 returns a json-object with the following information:
700 - "size" : json-int
702 Example:
704 -> { "execute": "query-migrate-cache-size" }
705 <- { "return": 67108864 }
707 EQMP
710 .name = "migrate_set_speed",
711 .args_type = "value:o",
712 .mhandler.cmd_new = qmp_marshal_input_migrate_set_speed,
715 SQMP
716 migrate_set_speed
717 -----------------
719 Set maximum speed for migrations.
721 Arguments:
723 - "value": maximum speed, in bytes per second (json-int)
725 Example:
727 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
728 <- { "return": {} }
730 EQMP
733 .name = "migrate_set_downtime",
734 .args_type = "value:T",
735 .mhandler.cmd_new = qmp_marshal_input_migrate_set_downtime,
738 SQMP
739 migrate_set_downtime
740 --------------------
742 Set maximum tolerated downtime (in seconds) for migrations.
744 Arguments:
746 - "value": maximum downtime (json-number)
748 Example:
750 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
751 <- { "return": {} }
753 EQMP
756 .name = "client_migrate_info",
757 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
758 .params = "protocol hostname port tls-port cert-subject",
759 .help = "send migration info to spice/vnc client",
760 .user_print = monitor_user_noop,
761 .mhandler.cmd_async = client_migrate_info,
762 .flags = MONITOR_CMD_ASYNC,
765 SQMP
766 client_migrate_info
767 ------------------
769 Set the spice/vnc connection info for the migration target. The spice/vnc
770 server will ask the spice/vnc client to automatically reconnect using the
771 new parameters (if specified) once the vm migration finished successfully.
773 Arguments:
775 - "protocol": protocol: "spice" or "vnc" (json-string)
776 - "hostname": migration target hostname (json-string)
777 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
778 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
779 - "cert-subject": server certificate subject (json-string, optional)
781 Example:
783 -> { "execute": "client_migrate_info",
784 "arguments": { "protocol": "spice",
785 "hostname": "virt42.lab.kraxel.org",
786 "port": 1234 } }
787 <- { "return": {} }
789 EQMP
792 .name = "dump-guest-memory",
793 .args_type = "paging:b,protocol:s,begin:i?,end:i?,format:s?",
794 .params = "-p protocol [begin] [length] [format]",
795 .help = "dump guest memory to file",
796 .user_print = monitor_user_noop,
797 .mhandler.cmd_new = qmp_marshal_input_dump_guest_memory,
800 SQMP
801 dump
804 Dump guest memory to file. The file can be processed with crash or gdb.
806 Arguments:
808 - "paging": do paging to get guest's memory mapping (json-bool)
809 - "protocol": destination file(started with "file:") or destination file
810 descriptor (started with "fd:") (json-string)
811 - "begin": the starting physical address. It's optional, and should be specified
812 with length together (json-int)
813 - "length": the memory size, in bytes. It's optional, and should be specified
814 with begin together (json-int)
815 - "format": the format of guest memory dump. It's optional, and can be
816 elf|kdump-zlib|kdump-lzo|kdump-snappy, but non-elf formats will
817 conflict with paging and filter, ie. begin and length (json-string)
819 Example:
821 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
822 <- { "return": {} }
824 Notes:
826 (1) All boolean arguments default to false
828 EQMP
831 .name = "query-dump-guest-memory-capability",
832 .args_type = "",
833 .mhandler.cmd_new = qmp_marshal_input_query_dump_guest_memory_capability,
836 SQMP
837 query-dump-guest-memory-capability
838 ----------
840 Show available formats for 'dump-guest-memory'
842 Example:
844 -> { "execute": "query-dump-guest-memory-capability" }
845 <- { "return": { "formats":
846 ["elf", "kdump-zlib", "kdump-lzo", "kdump-snappy"] }
848 EQMP
851 .name = "netdev_add",
852 .args_type = "netdev:O",
853 .mhandler.cmd_new = qmp_netdev_add,
856 SQMP
857 netdev_add
858 ----------
860 Add host network device.
862 Arguments:
864 - "type": the device type, "tap", "user", ... (json-string)
865 - "id": the device's ID, must be unique (json-string)
866 - device options
868 Example:
870 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
871 <- { "return": {} }
873 Note: The supported device options are the same ones supported by the '-netdev'
874 command-line argument, which are listed in the '-help' output or QEMU's
875 manual
877 EQMP
880 .name = "netdev_del",
881 .args_type = "id:s",
882 .mhandler.cmd_new = qmp_marshal_input_netdev_del,
885 SQMP
886 netdev_del
887 ----------
889 Remove host network device.
891 Arguments:
893 - "id": the device's ID, must be unique (json-string)
895 Example:
897 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
898 <- { "return": {} }
901 EQMP
904 .name = "object-add",
905 .args_type = "qom-type:s,id:s,props:q?",
906 .mhandler.cmd_new = qmp_object_add,
909 SQMP
910 object-add
911 ----------
913 Create QOM object.
915 Arguments:
917 - "qom-type": the object's QOM type, i.e. the class name (json-string)
918 - "id": the object's ID, must be unique (json-string)
919 - "props": a dictionary of object property values (optional, json-dict)
921 Example:
923 -> { "execute": "object-add", "arguments": { "qom-type": "rng-random", "id": "rng1",
924 "props": { "filename": "/dev/hwrng" } } }
925 <- { "return": {} }
927 EQMP
930 .name = "object-del",
931 .args_type = "id:s",
932 .mhandler.cmd_new = qmp_marshal_input_object_del,
935 SQMP
936 object-del
937 ----------
939 Remove QOM object.
941 Arguments:
943 - "id": the object's ID (json-string)
945 Example:
947 -> { "execute": "object-del", "arguments": { "id": "rng1" } }
948 <- { "return": {} }
951 EQMP
955 .name = "block_resize",
956 .args_type = "device:s?,node-name:s?,size:o",
957 .mhandler.cmd_new = qmp_marshal_input_block_resize,
960 SQMP
961 block_resize
962 ------------
964 Resize a block image while a guest is running.
966 Arguments:
968 - "device": the device's ID, must be unique (json-string)
969 - "node-name": the node name in the block driver state graph (json-string)
970 - "size": new size
972 Example:
974 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
975 <- { "return": {} }
977 EQMP
980 .name = "block-stream",
981 .args_type = "device:B,base:s?,speed:o?,backing-file:s?,on-error:s?",
982 .mhandler.cmd_new = qmp_marshal_input_block_stream,
986 .name = "block-commit",
987 .args_type = "device:B,base:s?,top:s?,backing-file:s?,speed:o?",
988 .mhandler.cmd_new = qmp_marshal_input_block_commit,
991 SQMP
992 block-commit
993 ------------
995 Live commit of data from overlay image nodes into backing nodes - i.e., writes
996 data between 'top' and 'base' into 'base'.
998 Arguments:
1000 - "device": The device's ID, must be unique (json-string)
1001 - "base": The file name of the backing image to write data into.
1002 If not specified, this is the deepest backing image
1003 (json-string, optional)
1004 - "top": The file name of the backing image within the image chain,
1005 which contains the topmost data to be committed down. If
1006 not specified, this is the active layer. (json-string, optional)
1008 - backing-file: The backing file string to write into the overlay
1009 image of 'top'. If 'top' is the active layer,
1010 specifying a backing file string is an error. This
1011 filename is not validated.
1013 If a pathname string is such that it cannot be
1014 resolved by QEMU, that means that subsequent QMP or
1015 HMP commands must use node-names for the image in
1016 question, as filename lookup methods will fail.
1018 If not specified, QEMU will automatically determine
1019 the backing file string to use, or error out if
1020 there is no obvious choice. Care should be taken
1021 when specifying the string, to specify a valid
1022 filename or protocol.
1023 (json-string, optional) (Since 2.1)
1025 If top == base, that is an error.
1026 If top == active, the job will not be completed by itself,
1027 user needs to complete the job with the block-job-complete
1028 command after getting the ready event. (Since 2.0)
1030 If the base image is smaller than top, then the base image
1031 will be resized to be the same size as top. If top is
1032 smaller than the base image, the base will not be
1033 truncated. If you want the base image size to match the
1034 size of the smaller top, you can safely truncate it
1035 yourself once the commit operation successfully completes.
1036 (json-string)
1037 - "speed": the maximum speed, in bytes per second (json-int, optional)
1040 Example:
1042 -> { "execute": "block-commit", "arguments": { "device": "virtio0",
1043 "top": "/tmp/snap1.qcow2" } }
1044 <- { "return": {} }
1046 EQMP
1049 .name = "drive-backup",
1050 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1051 "on-source-error:s?,on-target-error:s?",
1052 .mhandler.cmd_new = qmp_marshal_input_drive_backup,
1055 SQMP
1056 drive-backup
1057 ------------
1059 Start a point-in-time copy of a block device to a new destination. The
1060 status of ongoing drive-backup operations can be checked with
1061 query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1062 The operation can be stopped before it has completed using the
1063 block-job-cancel command.
1065 Arguments:
1067 - "device": the name of the device which should be copied.
1068 (json-string)
1069 - "target": the target of the new image. If the file exists, or if it is a
1070 device, the existing file/device will be used as the new
1071 destination. If it does not exist, a new file will be created.
1072 (json-string)
1073 - "format": the format of the new destination, default is to probe if 'mode' is
1074 'existing', else the format of the source
1075 (json-string, optional)
1076 - "sync": what parts of the disk image should be copied to the destination;
1077 possibilities include "full" for all the disk, "top" for only the sectors
1078 allocated in the topmost image, or "none" to only replicate new I/O
1079 (MirrorSyncMode).
1080 - "mode": whether and how QEMU should create a new image
1081 (NewImageMode, optional, default 'absolute-paths')
1082 - "speed": the maximum speed, in bytes per second (json-int, optional)
1083 - "on-source-error": the action to take on an error on the source, default
1084 'report'. 'stop' and 'enospc' can only be used
1085 if the block device supports io-status.
1086 (BlockdevOnError, optional)
1087 - "on-target-error": the action to take on an error on the target, default
1088 'report' (no limitations, since this applies to
1089 a different block device than device).
1090 (BlockdevOnError, optional)
1092 Example:
1093 -> { "execute": "drive-backup", "arguments": { "device": "drive0",
1094 "sync": "full",
1095 "target": "backup.img" } }
1096 <- { "return": {} }
1098 EQMP
1101 .name = "blockdev-backup",
1102 .args_type = "sync:s,device:B,target:B,speed:i?,"
1103 "on-source-error:s?,on-target-error:s?",
1104 .mhandler.cmd_new = qmp_marshal_input_blockdev_backup,
1107 SQMP
1108 blockdev-backup
1109 ---------------
1111 The device version of drive-backup: this command takes an existing named device
1112 as backup target.
1114 Arguments:
1116 - "device": the name of the device which should be copied.
1117 (json-string)
1118 - "target": the name of the backup target device. (json-string)
1119 - "sync": what parts of the disk image should be copied to the destination;
1120 possibilities include "full" for all the disk, "top" for only the
1121 sectors allocated in the topmost image, or "none" to only replicate
1122 new I/O (MirrorSyncMode).
1123 - "speed": the maximum speed, in bytes per second (json-int, optional)
1124 - "on-source-error": the action to take on an error on the source, default
1125 'report'. 'stop' and 'enospc' can only be used
1126 if the block device supports io-status.
1127 (BlockdevOnError, optional)
1128 - "on-target-error": the action to take on an error on the target, default
1129 'report' (no limitations, since this applies to
1130 a different block device than device).
1131 (BlockdevOnError, optional)
1133 Example:
1134 -> { "execute": "blockdev-backup", "arguments": { "device": "src-id",
1135 "sync": "full",
1136 "target": "tgt-id" } }
1137 <- { "return": {} }
1139 EQMP
1142 .name = "block-job-set-speed",
1143 .args_type = "device:B,speed:o",
1144 .mhandler.cmd_new = qmp_marshal_input_block_job_set_speed,
1148 .name = "block-job-cancel",
1149 .args_type = "device:B,force:b?",
1150 .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
1153 .name = "block-job-pause",
1154 .args_type = "device:B",
1155 .mhandler.cmd_new = qmp_marshal_input_block_job_pause,
1158 .name = "block-job-resume",
1159 .args_type = "device:B",
1160 .mhandler.cmd_new = qmp_marshal_input_block_job_resume,
1163 .name = "block-job-complete",
1164 .args_type = "device:B",
1165 .mhandler.cmd_new = qmp_marshal_input_block_job_complete,
1168 .name = "transaction",
1169 .args_type = "actions:q",
1170 .mhandler.cmd_new = qmp_marshal_input_transaction,
1173 SQMP
1174 transaction
1175 -----------
1177 Atomically operate on one or more block devices. The only supported operations
1178 for now are drive-backup, internal and external snapshotting. A list of
1179 dictionaries is accepted, that contains the actions to be performed.
1180 If there is any failure performing any of the operations, all operations
1181 for the group are abandoned.
1183 For external snapshots, the dictionary contains the device, the file to use for
1184 the new snapshot, and the format. The default format, if not specified, is
1185 qcow2.
1187 Each new snapshot defaults to being created by QEMU (wiping any
1188 contents if the file already exists), but it is also possible to reuse
1189 an externally-created file. In the latter case, you should ensure that
1190 the new image file has the same contents as the current one; QEMU cannot
1191 perform any meaningful check. Typically this is achieved by using the
1192 current image file as the backing file for the new image.
1194 On failure, the original disks pre-snapshot attempt will be used.
1196 For internal snapshots, the dictionary contains the device and the snapshot's
1197 name. If an internal snapshot matching name already exists, the request will
1198 be rejected. Only some image formats support it, for example, qcow2, rbd,
1199 and sheepdog.
1201 On failure, qemu will try delete the newly created internal snapshot in the
1202 transaction. When an I/O error occurs during deletion, the user needs to fix
1203 it later with qemu-img or other command.
1205 Arguments:
1207 actions array:
1208 - "type": the operation to perform. The only supported
1209 value is "blockdev-snapshot-sync". (json-string)
1210 - "data": a dictionary. The contents depend on the value
1211 of "type". When "type" is "blockdev-snapshot-sync":
1212 - "device": device name to snapshot (json-string)
1213 - "node-name": graph node name to snapshot (json-string)
1214 - "snapshot-file": name of new image file (json-string)
1215 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1216 - "format": format of new image (json-string, optional)
1217 - "mode": whether and how QEMU should create the snapshot file
1218 (NewImageMode, optional, default "absolute-paths")
1219 When "type" is "blockdev-snapshot-internal-sync":
1220 - "device": device name to snapshot (json-string)
1221 - "name": name of the new snapshot (json-string)
1223 Example:
1225 -> { "execute": "transaction",
1226 "arguments": { "actions": [
1227 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd0",
1228 "snapshot-file": "/some/place/my-image",
1229 "format": "qcow2" } },
1230 { "type": "blockdev-snapshot-sync", "data" : { "node-name": "myfile",
1231 "snapshot-file": "/some/place/my-image2",
1232 "snapshot-node-name": "node3432",
1233 "mode": "existing",
1234 "format": "qcow2" } },
1235 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd1",
1236 "snapshot-file": "/some/place/my-image2",
1237 "mode": "existing",
1238 "format": "qcow2" } },
1239 { "type": "blockdev-snapshot-internal-sync", "data" : {
1240 "device": "ide-hd2",
1241 "name": "snapshot0" } } ] } }
1242 <- { "return": {} }
1244 EQMP
1247 .name = "blockdev-snapshot-sync",
1248 .args_type = "device:s?,node-name:s?,snapshot-file:s,snapshot-node-name:s?,format:s?,mode:s?",
1249 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
1252 SQMP
1253 blockdev-snapshot-sync
1254 ----------------------
1256 Synchronous snapshot of a block device. snapshot-file specifies the
1257 target of the new image. If the file exists, or if it is a device, the
1258 snapshot will be created in the existing file/device. If does not
1259 exist, a new file will be created. format specifies the format of the
1260 snapshot image, default is qcow2.
1262 Arguments:
1264 - "device": device name to snapshot (json-string)
1265 - "node-name": graph node name to snapshot (json-string)
1266 - "snapshot-file": name of new image file (json-string)
1267 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1268 - "mode": whether and how QEMU should create the snapshot file
1269 (NewImageMode, optional, default "absolute-paths")
1270 - "format": format of new image (json-string, optional)
1272 Example:
1274 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
1275 "snapshot-file":
1276 "/some/place/my-image",
1277 "format": "qcow2" } }
1278 <- { "return": {} }
1280 EQMP
1283 .name = "blockdev-snapshot-internal-sync",
1284 .args_type = "device:B,name:s",
1285 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_internal_sync,
1288 SQMP
1289 blockdev-snapshot-internal-sync
1290 -------------------------------
1292 Synchronously take an internal snapshot of a block device when the format of
1293 image used supports it. If the name is an empty string, or a snapshot with
1294 name already exists, the operation will fail.
1296 Arguments:
1298 - "device": device name to snapshot (json-string)
1299 - "name": name of the new snapshot (json-string)
1301 Example:
1303 -> { "execute": "blockdev-snapshot-internal-sync",
1304 "arguments": { "device": "ide-hd0",
1305 "name": "snapshot0" }
1307 <- { "return": {} }
1309 EQMP
1312 .name = "blockdev-snapshot-delete-internal-sync",
1313 .args_type = "device:B,id:s?,name:s?",
1314 .mhandler.cmd_new =
1315 qmp_marshal_input_blockdev_snapshot_delete_internal_sync,
1318 SQMP
1319 blockdev-snapshot-delete-internal-sync
1320 --------------------------------------
1322 Synchronously delete an internal snapshot of a block device when the format of
1323 image used supports it. The snapshot is identified by name or id or both. One
1324 of name or id is required. If the snapshot is not found, the operation will
1325 fail.
1327 Arguments:
1329 - "device": device name (json-string)
1330 - "id": ID of the snapshot (json-string, optional)
1331 - "name": name of the snapshot (json-string, optional)
1333 Example:
1335 -> { "execute": "blockdev-snapshot-delete-internal-sync",
1336 "arguments": { "device": "ide-hd0",
1337 "name": "snapshot0" }
1339 <- { "return": {
1340 "id": "1",
1341 "name": "snapshot0",
1342 "vm-state-size": 0,
1343 "date-sec": 1000012,
1344 "date-nsec": 10,
1345 "vm-clock-sec": 100,
1346 "vm-clock-nsec": 20
1350 EQMP
1353 .name = "drive-mirror",
1354 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1355 "node-name:s?,replaces:s?,"
1356 "on-source-error:s?,on-target-error:s?,"
1357 "granularity:i?,buf-size:i?",
1358 .mhandler.cmd_new = qmp_marshal_input_drive_mirror,
1361 SQMP
1362 drive-mirror
1363 ------------
1365 Start mirroring a block device's writes to a new destination. target
1366 specifies the target of the new image. If the file exists, or if it is
1367 a device, it will be used as the new destination for writes. If it does not
1368 exist, a new file will be created. format specifies the format of the
1369 mirror image, default is to probe if mode='existing', else the format
1370 of the source.
1372 Arguments:
1374 - "device": device name to operate on (json-string)
1375 - "target": name of new image file (json-string)
1376 - "format": format of new image (json-string, optional)
1377 - "node-name": the name of the new block driver state in the node graph
1378 (json-string, optional)
1379 - "replaces": the block driver node name to replace when finished
1380 (json-string, optional)
1381 - "mode": how an image file should be created into the target
1382 file/device (NewImageMode, optional, default 'absolute-paths')
1383 - "speed": maximum speed of the streaming job, in bytes per second
1384 (json-int)
1385 - "granularity": granularity of the dirty bitmap, in bytes (json-int, optional)
1386 - "buf_size": maximum amount of data in flight from source to target, in bytes
1387 (json-int, default 10M)
1388 - "sync": what parts of the disk image should be copied to the destination;
1389 possibilities include "full" for all the disk, "top" for only the sectors
1390 allocated in the topmost image, or "none" to only replicate new I/O
1391 (MirrorSyncMode).
1392 - "on-source-error": the action to take on an error on the source
1393 (BlockdevOnError, default 'report')
1394 - "on-target-error": the action to take on an error on the target
1395 (BlockdevOnError, default 'report')
1397 The default value of the granularity is the image cluster size clamped
1398 between 4096 and 65536, if the image format defines one. If the format
1399 does not define a cluster size, the default value of the granularity
1400 is 65536.
1403 Example:
1405 -> { "execute": "drive-mirror", "arguments": { "device": "ide-hd0",
1406 "target": "/some/place/my-image",
1407 "sync": "full",
1408 "format": "qcow2" } }
1409 <- { "return": {} }
1411 EQMP
1414 .name = "change-backing-file",
1415 .args_type = "device:s,image-node-name:s,backing-file:s",
1416 .mhandler.cmd_new = qmp_marshal_input_change_backing_file,
1419 SQMP
1420 change-backing-file
1421 -------------------
1422 Since: 2.1
1424 Change the backing file in the image file metadata. This does not cause
1425 QEMU to reopen the image file to reparse the backing filename (it may,
1426 however, perform a reopen to change permissions from r/o -> r/w -> r/o,
1427 if needed). The new backing file string is written into the image file
1428 metadata, and the QEMU internal strings are updated.
1430 Arguments:
1432 - "image-node-name": The name of the block driver state node of the
1433 image to modify. The "device" is argument is used to
1434 verify "image-node-name" is in the chain described by
1435 "device".
1436 (json-string, optional)
1438 - "device": The name of the device.
1439 (json-string)
1441 - "backing-file": The string to write as the backing file. This string is
1442 not validated, so care should be taken when specifying
1443 the string or the image chain may not be able to be
1444 reopened again.
1445 (json-string)
1447 Returns: Nothing on success
1448 If "device" does not exist or cannot be determined, DeviceNotFound
1450 EQMP
1453 .name = "balloon",
1454 .args_type = "value:M",
1455 .mhandler.cmd_new = qmp_marshal_input_balloon,
1458 SQMP
1459 balloon
1460 -------
1462 Request VM to change its memory allocation (in bytes).
1464 Arguments:
1466 - "value": New memory allocation (json-int)
1468 Example:
1470 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1471 <- { "return": {} }
1473 EQMP
1476 .name = "set_link",
1477 .args_type = "name:s,up:b",
1478 .mhandler.cmd_new = qmp_marshal_input_set_link,
1481 SQMP
1482 set_link
1483 --------
1485 Change the link status of a network adapter.
1487 Arguments:
1489 - "name": network device name (json-string)
1490 - "up": status is up (json-bool)
1492 Example:
1494 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
1495 <- { "return": {} }
1497 EQMP
1500 .name = "getfd",
1501 .args_type = "fdname:s",
1502 .params = "getfd name",
1503 .help = "receive a file descriptor via SCM rights and assign it a name",
1504 .mhandler.cmd_new = qmp_marshal_input_getfd,
1507 SQMP
1508 getfd
1509 -----
1511 Receive a file descriptor via SCM rights and assign it a name.
1513 Arguments:
1515 - "fdname": file descriptor name (json-string)
1517 Example:
1519 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1520 <- { "return": {} }
1522 Notes:
1524 (1) If the name specified by the "fdname" argument already exists,
1525 the file descriptor assigned to it will be closed and replaced
1526 by the received file descriptor.
1527 (2) The 'closefd' command can be used to explicitly close the file
1528 descriptor when it is no longer needed.
1530 EQMP
1533 .name = "closefd",
1534 .args_type = "fdname:s",
1535 .params = "closefd name",
1536 .help = "close a file descriptor previously passed via SCM rights",
1537 .mhandler.cmd_new = qmp_marshal_input_closefd,
1540 SQMP
1541 closefd
1542 -------
1544 Close a file descriptor previously passed via SCM rights.
1546 Arguments:
1548 - "fdname": file descriptor name (json-string)
1550 Example:
1552 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1553 <- { "return": {} }
1555 EQMP
1558 .name = "add-fd",
1559 .args_type = "fdset-id:i?,opaque:s?",
1560 .params = "add-fd fdset-id opaque",
1561 .help = "Add a file descriptor, that was passed via SCM rights, to an fd set",
1562 .mhandler.cmd_new = qmp_marshal_input_add_fd,
1565 SQMP
1566 add-fd
1567 -------
1569 Add a file descriptor, that was passed via SCM rights, to an fd set.
1571 Arguments:
1573 - "fdset-id": The ID of the fd set to add the file descriptor to.
1574 (json-int, optional)
1575 - "opaque": A free-form string that can be used to describe the fd.
1576 (json-string, optional)
1578 Return a json-object with the following information:
1580 - "fdset-id": The ID of the fd set that the fd was added to. (json-int)
1581 - "fd": The file descriptor that was received via SCM rights and added to the
1582 fd set. (json-int)
1584 Example:
1586 -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1587 <- { "return": { "fdset-id": 1, "fd": 3 } }
1589 Notes:
1591 (1) The list of fd sets is shared by all monitor connections.
1592 (2) If "fdset-id" is not specified, a new fd set will be created.
1594 EQMP
1597 .name = "remove-fd",
1598 .args_type = "fdset-id:i,fd:i?",
1599 .params = "remove-fd fdset-id fd",
1600 .help = "Remove a file descriptor from an fd set",
1601 .mhandler.cmd_new = qmp_marshal_input_remove_fd,
1604 SQMP
1605 remove-fd
1606 ---------
1608 Remove a file descriptor from an fd set.
1610 Arguments:
1612 - "fdset-id": The ID of the fd set that the file descriptor belongs to.
1613 (json-int)
1614 - "fd": The file descriptor that is to be removed. (json-int, optional)
1616 Example:
1618 -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1619 <- { "return": {} }
1621 Notes:
1623 (1) The list of fd sets is shared by all monitor connections.
1624 (2) If "fd" is not specified, all file descriptors in "fdset-id" will be
1625 removed.
1627 EQMP
1630 .name = "query-fdsets",
1631 .args_type = "",
1632 .help = "Return information describing all fd sets",
1633 .mhandler.cmd_new = qmp_marshal_input_query_fdsets,
1636 SQMP
1637 query-fdsets
1638 -------------
1640 Return information describing all fd sets.
1642 Arguments: None
1644 Example:
1646 -> { "execute": "query-fdsets" }
1647 <- { "return": [
1649 "fds": [
1651 "fd": 30,
1652 "opaque": "rdonly:/path/to/file"
1655 "fd": 24,
1656 "opaque": "rdwr:/path/to/file"
1659 "fdset-id": 1
1662 "fds": [
1664 "fd": 28
1667 "fd": 29
1670 "fdset-id": 0
1675 Note: The list of fd sets is shared by all monitor connections.
1677 EQMP
1680 .name = "block_passwd",
1681 .args_type = "device:s?,node-name:s?,password:s",
1682 .mhandler.cmd_new = qmp_marshal_input_block_passwd,
1685 SQMP
1686 block_passwd
1687 ------------
1689 Set the password of encrypted block devices.
1691 Arguments:
1693 - "device": device name (json-string)
1694 - "node-name": name in the block driver state graph (json-string)
1695 - "password": password (json-string)
1697 Example:
1699 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
1700 "password": "12345" } }
1701 <- { "return": {} }
1703 EQMP
1706 .name = "block_set_io_throttle",
1707 .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?",
1708 .mhandler.cmd_new = qmp_marshal_input_block_set_io_throttle,
1711 SQMP
1712 block_set_io_throttle
1713 ------------
1715 Change I/O throttle limits for a block drive.
1717 Arguments:
1719 - "device": device name (json-string)
1720 - "bps": total throughput limit in bytes per second (json-int)
1721 - "bps_rd": read throughput limit in bytes per second (json-int)
1722 - "bps_wr": write throughput limit in bytes per second (json-int)
1723 - "iops": total I/O operations per second (json-int)
1724 - "iops_rd": read I/O operations per second (json-int)
1725 - "iops_wr": write I/O operations per second (json-int)
1726 - "bps_max": total max in bytes (json-int)
1727 - "bps_rd_max": read max in bytes (json-int)
1728 - "bps_wr_max": write max in bytes (json-int)
1729 - "iops_max": total I/O operations max (json-int)
1730 - "iops_rd_max": read I/O operations max (json-int)
1731 - "iops_wr_max": write I/O operations max (json-int)
1732 - "iops_size": I/O size in bytes when limiting (json-int)
1734 Example:
1736 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
1737 "bps": 1000000,
1738 "bps_rd": 0,
1739 "bps_wr": 0,
1740 "iops": 0,
1741 "iops_rd": 0,
1742 "iops_wr": 0,
1743 "bps_max": 8000000,
1744 "bps_rd_max": 0,
1745 "bps_wr_max": 0,
1746 "iops_max": 0,
1747 "iops_rd_max": 0,
1748 "iops_wr_max": 0,
1749 "iops_size": 0 } }
1750 <- { "return": {} }
1752 EQMP
1755 .name = "set_password",
1756 .args_type = "protocol:s,password:s,connected:s?",
1757 .mhandler.cmd_new = qmp_marshal_input_set_password,
1760 SQMP
1761 set_password
1762 ------------
1764 Set the password for vnc/spice protocols.
1766 Arguments:
1768 - "protocol": protocol name (json-string)
1769 - "password": password (json-string)
1770 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
1772 Example:
1774 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
1775 "password": "secret" } }
1776 <- { "return": {} }
1778 EQMP
1781 .name = "expire_password",
1782 .args_type = "protocol:s,time:s",
1783 .mhandler.cmd_new = qmp_marshal_input_expire_password,
1786 SQMP
1787 expire_password
1788 ---------------
1790 Set the password expire time for vnc/spice protocols.
1792 Arguments:
1794 - "protocol": protocol name (json-string)
1795 - "time": [ now | never | +secs | secs ] (json-string)
1797 Example:
1799 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
1800 "time": "+60" } }
1801 <- { "return": {} }
1803 EQMP
1806 .name = "add_client",
1807 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
1808 .mhandler.cmd_new = qmp_marshal_input_add_client,
1811 SQMP
1812 add_client
1813 ----------
1815 Add a graphics client
1817 Arguments:
1819 - "protocol": protocol name (json-string)
1820 - "fdname": file descriptor name (json-string)
1821 - "skipauth": whether to skip authentication (json-bool, optional)
1822 - "tls": whether to perform TLS (json-bool, optional)
1824 Example:
1826 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
1827 "fdname": "myclient" } }
1828 <- { "return": {} }
1830 EQMP
1832 .name = "qmp_capabilities",
1833 .args_type = "",
1834 .params = "",
1835 .help = "enable QMP capabilities",
1836 .user_print = monitor_user_noop,
1837 .mhandler.cmd_new = do_qmp_capabilities,
1840 SQMP
1841 qmp_capabilities
1842 ----------------
1844 Enable QMP capabilities.
1846 Arguments: None.
1848 Example:
1850 -> { "execute": "qmp_capabilities" }
1851 <- { "return": {} }
1853 Note: This command must be issued before issuing any other command.
1855 EQMP
1858 .name = "human-monitor-command",
1859 .args_type = "command-line:s,cpu-index:i?",
1860 .mhandler.cmd_new = qmp_marshal_input_human_monitor_command,
1863 SQMP
1864 human-monitor-command
1865 ---------------------
1867 Execute a Human Monitor command.
1869 Arguments:
1871 - command-line: the command name and its arguments, just like the
1872 Human Monitor's shell (json-string)
1873 - cpu-index: select the CPU number to be used by commands which access CPU
1874 data, like 'info registers'. The Monitor selects CPU 0 if this
1875 argument is not provided (json-int, optional)
1877 Example:
1879 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1880 <- { "return": "kvm support: enabled\r\n" }
1882 Notes:
1884 (1) The Human Monitor is NOT an stable interface, this means that command
1885 names, arguments and responses can change or be removed at ANY time.
1886 Applications that rely on long term stability guarantees should NOT
1887 use this command
1889 (2) Limitations:
1891 o This command is stateless, this means that commands that depend
1892 on state information (such as getfd) might not work
1894 o Commands that prompt the user for data (eg. 'cont' when the block
1895 device is encrypted) don't currently work
1897 3. Query Commands
1898 =================
1900 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1901 HXCOMM this! We will possibly move query commands definitions inside those
1902 HXCOMM sections, just like regular commands.
1904 EQMP
1906 SQMP
1907 query-version
1908 -------------
1910 Show QEMU version.
1912 Return a json-object with the following information:
1914 - "qemu": A json-object containing three integer values:
1915 - "major": QEMU's major version (json-int)
1916 - "minor": QEMU's minor version (json-int)
1917 - "micro": QEMU's micro version (json-int)
1918 - "package": package's version (json-string)
1920 Example:
1922 -> { "execute": "query-version" }
1923 <- {
1924 "return":{
1925 "qemu":{
1926 "major":0,
1927 "minor":11,
1928 "micro":5
1930 "package":""
1934 EQMP
1937 .name = "query-version",
1938 .args_type = "",
1939 .mhandler.cmd_new = qmp_marshal_input_query_version,
1942 SQMP
1943 query-commands
1944 --------------
1946 List QMP available commands.
1948 Each command is represented by a json-object, the returned value is a json-array
1949 of all commands.
1951 Each json-object contain:
1953 - "name": command's name (json-string)
1955 Example:
1957 -> { "execute": "query-commands" }
1958 <- {
1959 "return":[
1961 "name":"query-balloon"
1964 "name":"system_powerdown"
1969 Note: This example has been shortened as the real response is too long.
1971 EQMP
1974 .name = "query-commands",
1975 .args_type = "",
1976 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1979 SQMP
1980 query-events
1981 --------------
1983 List QMP available events.
1985 Each event is represented by a json-object, the returned value is a json-array
1986 of all events.
1988 Each json-object contains:
1990 - "name": event's name (json-string)
1992 Example:
1994 -> { "execute": "query-events" }
1995 <- {
1996 "return":[
1998 "name":"SHUTDOWN"
2001 "name":"RESET"
2006 Note: This example has been shortened as the real response is too long.
2008 EQMP
2011 .name = "query-events",
2012 .args_type = "",
2013 .mhandler.cmd_new = qmp_marshal_input_query_events,
2016 SQMP
2017 query-chardev
2018 -------------
2020 Each device is represented by a json-object. The returned value is a json-array
2021 of all devices.
2023 Each json-object contain the following:
2025 - "label": device's label (json-string)
2026 - "filename": device's file (json-string)
2027 - "frontend-open": open/closed state of the frontend device attached to this
2028 backend (json-bool)
2030 Example:
2032 -> { "execute": "query-chardev" }
2033 <- {
2034 "return": [
2036 "label": "charchannel0",
2037 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.agent,server",
2038 "frontend-open": false
2041 "label": "charmonitor",
2042 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.monitor,server",
2043 "frontend-open": true
2046 "label": "charserial0",
2047 "filename": "pty:/dev/pts/2",
2048 "frontend-open": true
2053 EQMP
2056 .name = "query-chardev",
2057 .args_type = "",
2058 .mhandler.cmd_new = qmp_marshal_input_query_chardev,
2061 SQMP
2062 query-chardev-backends
2063 -------------
2065 List available character device backends.
2067 Each backend is represented by a json-object, the returned value is a json-array
2068 of all backends.
2070 Each json-object contains:
2072 - "name": backend name (json-string)
2074 Example:
2076 -> { "execute": "query-chardev-backends" }
2077 <- {
2078 "return":[
2080 "name":"udp"
2083 "name":"tcp"
2086 "name":"unix"
2089 "name":"spiceport"
2094 EQMP
2097 .name = "query-chardev-backends",
2098 .args_type = "",
2099 .mhandler.cmd_new = qmp_marshal_input_query_chardev_backends,
2102 SQMP
2103 query-block
2104 -----------
2106 Show the block devices.
2108 Each block device information is stored in a json-object and the returned value
2109 is a json-array of all devices.
2111 Each json-object contain the following:
2113 - "device": device name (json-string)
2114 - "type": device type (json-string)
2115 - deprecated, retained for backward compatibility
2116 - Possible values: "unknown"
2117 - "removable": true if the device is removable, false otherwise (json-bool)
2118 - "locked": true if the device is locked, false otherwise (json-bool)
2119 - "tray_open": only present if removable, true if the device has a tray,
2120 and it is open (json-bool)
2121 - "inserted": only present if the device is inserted, it is a json-object
2122 containing the following:
2123 - "file": device file name (json-string)
2124 - "ro": true if read-only, false otherwise (json-bool)
2125 - "drv": driver format name (json-string)
2126 - Possible values: "blkdebug", "bochs", "cloop", "dmg",
2127 "file", "file", "ftp", "ftps", "host_cdrom",
2128 "host_device", "host_floppy", "http", "https",
2129 "nbd", "parallels", "qcow", "qcow2", "raw",
2130 "tftp", "vdi", "vmdk", "vpc", "vvfat"
2131 - "backing_file": backing file name (json-string, optional)
2132 - "backing_file_depth": number of files in the backing file chain (json-int)
2133 - "encrypted": true if encrypted, false otherwise (json-bool)
2134 - "bps": limit total bytes per second (json-int)
2135 - "bps_rd": limit read bytes per second (json-int)
2136 - "bps_wr": limit write bytes per second (json-int)
2137 - "iops": limit total I/O operations per second (json-int)
2138 - "iops_rd": limit read operations per second (json-int)
2139 - "iops_wr": limit write operations per second (json-int)
2140 - "bps_max": total max in bytes (json-int)
2141 - "bps_rd_max": read max in bytes (json-int)
2142 - "bps_wr_max": write max in bytes (json-int)
2143 - "iops_max": total I/O operations max (json-int)
2144 - "iops_rd_max": read I/O operations max (json-int)
2145 - "iops_wr_max": write I/O operations max (json-int)
2146 - "iops_size": I/O size when limiting by iops (json-int)
2147 - "detect_zeroes": detect and optimize zero writing (json-string)
2148 - Possible values: "off", "on", "unmap"
2149 - "image": the detail of the image, it is a json-object containing
2150 the following:
2151 - "filename": image file name (json-string)
2152 - "format": image format (json-string)
2153 - "virtual-size": image capacity in bytes (json-int)
2154 - "dirty-flag": true if image is not cleanly closed, not present
2155 means clean (json-bool, optional)
2156 - "actual-size": actual size on disk in bytes of the image, not
2157 present when image does not support thin
2158 provision (json-int, optional)
2159 - "cluster-size": size of a cluster in bytes, not present if image
2160 format does not support it (json-int, optional)
2161 - "encrypted": true if the image is encrypted, not present means
2162 false or the image format does not support
2163 encryption (json-bool, optional)
2164 - "backing_file": backing file name, not present means no backing
2165 file is used or the image format does not
2166 support backing file chain
2167 (json-string, optional)
2168 - "full-backing-filename": full path of the backing file, not
2169 present if it equals backing_file or no
2170 backing file is used
2171 (json-string, optional)
2172 - "backing-filename-format": the format of the backing file, not
2173 present means unknown or no backing
2174 file (json-string, optional)
2175 - "snapshots": the internal snapshot info, it is an optional list
2176 of json-object containing the following:
2177 - "id": unique snapshot id (json-string)
2178 - "name": snapshot name (json-string)
2179 - "vm-state-size": size of the VM state in bytes (json-int)
2180 - "date-sec": UTC date of the snapshot in seconds (json-int)
2181 - "date-nsec": fractional part in nanoseconds to be used with
2182 date-sec (json-int)
2183 - "vm-clock-sec": VM clock relative to boot in seconds
2184 (json-int)
2185 - "vm-clock-nsec": fractional part in nanoseconds to be used
2186 with vm-clock-sec (json-int)
2187 - "backing-image": the detail of the backing image, it is an
2188 optional json-object only present when a
2189 backing image present for this image
2191 - "io-status": I/O operation status, only present if the device supports it
2192 and the VM is configured to stop on errors. It's always reset
2193 to "ok" when the "cont" command is issued (json_string, optional)
2194 - Possible values: "ok", "failed", "nospace"
2196 Example:
2198 -> { "execute": "query-block" }
2199 <- {
2200 "return":[
2202 "io-status": "ok",
2203 "device":"ide0-hd0",
2204 "locked":false,
2205 "removable":false,
2206 "inserted":{
2207 "ro":false,
2208 "drv":"qcow2",
2209 "encrypted":false,
2210 "file":"disks/test.qcow2",
2211 "backing_file_depth":1,
2212 "bps":1000000,
2213 "bps_rd":0,
2214 "bps_wr":0,
2215 "iops":1000000,
2216 "iops_rd":0,
2217 "iops_wr":0,
2218 "bps_max": 8000000,
2219 "bps_rd_max": 0,
2220 "bps_wr_max": 0,
2221 "iops_max": 0,
2222 "iops_rd_max": 0,
2223 "iops_wr_max": 0,
2224 "iops_size": 0,
2225 "detect_zeroes": "on",
2226 "image":{
2227 "filename":"disks/test.qcow2",
2228 "format":"qcow2",
2229 "virtual-size":2048000,
2230 "backing_file":"base.qcow2",
2231 "full-backing-filename":"disks/base.qcow2",
2232 "backing-filename-format:"qcow2",
2233 "snapshots":[
2235 "id": "1",
2236 "name": "snapshot1",
2237 "vm-state-size": 0,
2238 "date-sec": 10000200,
2239 "date-nsec": 12,
2240 "vm-clock-sec": 206,
2241 "vm-clock-nsec": 30
2244 "backing-image":{
2245 "filename":"disks/base.qcow2",
2246 "format":"qcow2",
2247 "virtual-size":2048000
2251 "type":"unknown"
2254 "io-status": "ok",
2255 "device":"ide1-cd0",
2256 "locked":false,
2257 "removable":true,
2258 "type":"unknown"
2261 "device":"floppy0",
2262 "locked":false,
2263 "removable":true,
2264 "type":"unknown"
2267 "device":"sd0",
2268 "locked":false,
2269 "removable":true,
2270 "type":"unknown"
2275 EQMP
2278 .name = "query-block",
2279 .args_type = "",
2280 .mhandler.cmd_new = qmp_marshal_input_query_block,
2283 SQMP
2284 query-blockstats
2285 ----------------
2287 Show block device statistics.
2289 Each device statistic information is stored in a json-object and the returned
2290 value is a json-array of all devices.
2292 Each json-object contain the following:
2294 - "device": device name (json-string)
2295 - "stats": A json-object with the statistics information, it contains:
2296 - "rd_bytes": bytes read (json-int)
2297 - "wr_bytes": bytes written (json-int)
2298 - "rd_operations": read operations (json-int)
2299 - "wr_operations": write operations (json-int)
2300 - "flush_operations": cache flush operations (json-int)
2301 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
2302 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
2303 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
2304 - "wr_highest_offset": Highest offset of a sector written since the
2305 BlockDriverState has been opened (json-int)
2306 - "parent": Contains recursively the statistics of the underlying
2307 protocol (e.g. the host file for a qcow2 image). If there is
2308 no underlying protocol, this field is omitted
2309 (json-object, optional)
2311 Example:
2313 -> { "execute": "query-blockstats" }
2314 <- {
2315 "return":[
2317 "device":"ide0-hd0",
2318 "parent":{
2319 "stats":{
2320 "wr_highest_offset":3686448128,
2321 "wr_bytes":9786368,
2322 "wr_operations":751,
2323 "rd_bytes":122567168,
2324 "rd_operations":36772
2325 "wr_total_times_ns":313253456
2326 "rd_total_times_ns":3465673657
2327 "flush_total_times_ns":49653
2328 "flush_operations":61,
2331 "stats":{
2332 "wr_highest_offset":2821110784,
2333 "wr_bytes":9786368,
2334 "wr_operations":692,
2335 "rd_bytes":122739200,
2336 "rd_operations":36604
2337 "flush_operations":51,
2338 "wr_total_times_ns":313253456
2339 "rd_total_times_ns":3465673657
2340 "flush_total_times_ns":49653
2344 "device":"ide1-cd0",
2345 "stats":{
2346 "wr_highest_offset":0,
2347 "wr_bytes":0,
2348 "wr_operations":0,
2349 "rd_bytes":0,
2350 "rd_operations":0
2351 "flush_operations":0,
2352 "wr_total_times_ns":0
2353 "rd_total_times_ns":0
2354 "flush_total_times_ns":0
2358 "device":"floppy0",
2359 "stats":{
2360 "wr_highest_offset":0,
2361 "wr_bytes":0,
2362 "wr_operations":0,
2363 "rd_bytes":0,
2364 "rd_operations":0
2365 "flush_operations":0,
2366 "wr_total_times_ns":0
2367 "rd_total_times_ns":0
2368 "flush_total_times_ns":0
2372 "device":"sd0",
2373 "stats":{
2374 "wr_highest_offset":0,
2375 "wr_bytes":0,
2376 "wr_operations":0,
2377 "rd_bytes":0,
2378 "rd_operations":0
2379 "flush_operations":0,
2380 "wr_total_times_ns":0
2381 "rd_total_times_ns":0
2382 "flush_total_times_ns":0
2388 EQMP
2391 .name = "query-blockstats",
2392 .args_type = "query-nodes:b?",
2393 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
2396 SQMP
2397 query-cpus
2398 ----------
2400 Show CPU information.
2402 Return a json-array. Each CPU is represented by a json-object, which contains:
2404 - "CPU": CPU index (json-int)
2405 - "current": true if this is the current CPU, false otherwise (json-bool)
2406 - "halted": true if the cpu is halted, false otherwise (json-bool)
2407 - Current program counter. The key's name depends on the architecture:
2408 "pc": i386/x86_64 (json-int)
2409 "nip": PPC (json-int)
2410 "pc" and "npc": sparc (json-int)
2411 "PC": mips (json-int)
2412 - "thread_id": ID of the underlying host thread (json-int)
2414 Example:
2416 -> { "execute": "query-cpus" }
2417 <- {
2418 "return":[
2420 "CPU":0,
2421 "current":true,
2422 "halted":false,
2423 "pc":3227107138
2424 "thread_id":3134
2427 "CPU":1,
2428 "current":false,
2429 "halted":true,
2430 "pc":7108165
2431 "thread_id":3135
2436 EQMP
2439 .name = "query-cpus",
2440 .args_type = "",
2441 .mhandler.cmd_new = qmp_marshal_input_query_cpus,
2444 SQMP
2445 query-iothreads
2446 ---------------
2448 Returns a list of information about each iothread.
2450 Note this list excludes the QEMU main loop thread, which is not declared
2451 using the -object iothread command-line option. It is always the main thread
2452 of the process.
2454 Return a json-array. Each iothread is represented by a json-object, which contains:
2456 - "id": name of iothread (json-str)
2457 - "thread-id": ID of the underlying host thread (json-int)
2459 Example:
2461 -> { "execute": "query-iothreads" }
2462 <- {
2463 "return":[
2465 "id":"iothread0",
2466 "thread-id":3134
2469 "id":"iothread1",
2470 "thread-id":3135
2475 EQMP
2478 .name = "query-iothreads",
2479 .args_type = "",
2480 .mhandler.cmd_new = qmp_marshal_input_query_iothreads,
2483 SQMP
2484 query-pci
2485 ---------
2487 PCI buses and devices information.
2489 The returned value is a json-array of all buses. Each bus is represented by
2490 a json-object, which has a key with a json-array of all PCI devices attached
2491 to it. Each device is represented by a json-object.
2493 The bus json-object contains the following:
2495 - "bus": bus number (json-int)
2496 - "devices": a json-array of json-objects, each json-object represents a
2497 PCI device
2499 The PCI device json-object contains the following:
2501 - "bus": identical to the parent's bus number (json-int)
2502 - "slot": slot number (json-int)
2503 - "function": function number (json-int)
2504 - "class_info": a json-object containing:
2505 - "desc": device class description (json-string, optional)
2506 - "class": device class number (json-int)
2507 - "id": a json-object containing:
2508 - "device": device ID (json-int)
2509 - "vendor": vendor ID (json-int)
2510 - "irq": device's IRQ if assigned (json-int, optional)
2511 - "qdev_id": qdev id string (json-string)
2512 - "pci_bridge": It's a json-object, only present if this device is a
2513 PCI bridge, contains:
2514 - "bus": bus number (json-int)
2515 - "secondary": secondary bus number (json-int)
2516 - "subordinate": subordinate bus number (json-int)
2517 - "io_range": I/O memory range information, a json-object with the
2518 following members:
2519 - "base": base address, in bytes (json-int)
2520 - "limit": limit address, in bytes (json-int)
2521 - "memory_range": memory range information, a json-object with the
2522 following members:
2523 - "base": base address, in bytes (json-int)
2524 - "limit": limit address, in bytes (json-int)
2525 - "prefetchable_range": Prefetchable memory range information, a
2526 json-object with the following members:
2527 - "base": base address, in bytes (json-int)
2528 - "limit": limit address, in bytes (json-int)
2529 - "devices": a json-array of PCI devices if there's any attached, each
2530 each element is represented by a json-object, which contains
2531 the same members of the 'PCI device json-object' described
2532 above (optional)
2533 - "regions": a json-array of json-objects, each json-object represents a
2534 memory region of this device
2536 The memory range json-object contains the following:
2538 - "base": base memory address (json-int)
2539 - "limit": limit value (json-int)
2541 The region json-object can be an I/O region or a memory region, an I/O region
2542 json-object contains the following:
2544 - "type": "io" (json-string, fixed)
2545 - "bar": BAR number (json-int)
2546 - "address": memory address (json-int)
2547 - "size": memory size (json-int)
2549 A memory region json-object contains the following:
2551 - "type": "memory" (json-string, fixed)
2552 - "bar": BAR number (json-int)
2553 - "address": memory address (json-int)
2554 - "size": memory size (json-int)
2555 - "mem_type_64": true or false (json-bool)
2556 - "prefetch": true or false (json-bool)
2558 Example:
2560 -> { "execute": "query-pci" }
2561 <- {
2562 "return":[
2564 "bus":0,
2565 "devices":[
2567 "bus":0,
2568 "qdev_id":"",
2569 "slot":0,
2570 "class_info":{
2571 "class":1536,
2572 "desc":"Host bridge"
2574 "id":{
2575 "device":32902,
2576 "vendor":4663
2578 "function":0,
2579 "regions":[
2584 "bus":0,
2585 "qdev_id":"",
2586 "slot":1,
2587 "class_info":{
2588 "class":1537,
2589 "desc":"ISA bridge"
2591 "id":{
2592 "device":32902,
2593 "vendor":28672
2595 "function":0,
2596 "regions":[
2601 "bus":0,
2602 "qdev_id":"",
2603 "slot":1,
2604 "class_info":{
2605 "class":257,
2606 "desc":"IDE controller"
2608 "id":{
2609 "device":32902,
2610 "vendor":28688
2612 "function":1,
2613 "regions":[
2615 "bar":4,
2616 "size":16,
2617 "address":49152,
2618 "type":"io"
2623 "bus":0,
2624 "qdev_id":"",
2625 "slot":2,
2626 "class_info":{
2627 "class":768,
2628 "desc":"VGA controller"
2630 "id":{
2631 "device":4115,
2632 "vendor":184
2634 "function":0,
2635 "regions":[
2637 "prefetch":true,
2638 "mem_type_64":false,
2639 "bar":0,
2640 "size":33554432,
2641 "address":4026531840,
2642 "type":"memory"
2645 "prefetch":false,
2646 "mem_type_64":false,
2647 "bar":1,
2648 "size":4096,
2649 "address":4060086272,
2650 "type":"memory"
2653 "prefetch":false,
2654 "mem_type_64":false,
2655 "bar":6,
2656 "size":65536,
2657 "address":-1,
2658 "type":"memory"
2663 "bus":0,
2664 "qdev_id":"",
2665 "irq":11,
2666 "slot":4,
2667 "class_info":{
2668 "class":1280,
2669 "desc":"RAM controller"
2671 "id":{
2672 "device":6900,
2673 "vendor":4098
2675 "function":0,
2676 "regions":[
2678 "bar":0,
2679 "size":32,
2680 "address":49280,
2681 "type":"io"
2690 Note: This example has been shortened as the real response is too long.
2692 EQMP
2695 .name = "query-pci",
2696 .args_type = "",
2697 .mhandler.cmd_new = qmp_marshal_input_query_pci,
2700 SQMP
2701 query-kvm
2702 ---------
2704 Show KVM information.
2706 Return a json-object with the following information:
2708 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
2709 - "present": true if QEMU has KVM support, false otherwise (json-bool)
2711 Example:
2713 -> { "execute": "query-kvm" }
2714 <- { "return": { "enabled": true, "present": true } }
2716 EQMP
2719 .name = "query-kvm",
2720 .args_type = "",
2721 .mhandler.cmd_new = qmp_marshal_input_query_kvm,
2724 SQMP
2725 query-status
2726 ------------
2728 Return a json-object with the following information:
2730 - "running": true if the VM is running, or false if it is paused (json-bool)
2731 - "singlestep": true if the VM is in single step mode,
2732 false otherwise (json-bool)
2733 - "status": one of the following values (json-string)
2734 "debug" - QEMU is running on a debugger
2735 "inmigrate" - guest is paused waiting for an incoming migration
2736 "internal-error" - An internal error that prevents further guest
2737 execution has occurred
2738 "io-error" - the last IOP has failed and the device is configured
2739 to pause on I/O errors
2740 "paused" - guest has been paused via the 'stop' command
2741 "postmigrate" - guest is paused following a successful 'migrate'
2742 "prelaunch" - QEMU was started with -S and guest has not started
2743 "finish-migrate" - guest is paused to finish the migration process
2744 "restore-vm" - guest is paused to restore VM state
2745 "running" - guest is actively running
2746 "save-vm" - guest is paused to save the VM state
2747 "shutdown" - guest is shut down (and -no-shutdown is in use)
2748 "watchdog" - the watchdog action is configured to pause and
2749 has been triggered
2751 Example:
2753 -> { "execute": "query-status" }
2754 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
2756 EQMP
2759 .name = "query-status",
2760 .args_type = "",
2761 .mhandler.cmd_new = qmp_marshal_input_query_status,
2764 SQMP
2765 query-mice
2766 ----------
2768 Show VM mice information.
2770 Each mouse is represented by a json-object, the returned value is a json-array
2771 of all mice.
2773 The mouse json-object contains the following:
2775 - "name": mouse's name (json-string)
2776 - "index": mouse's index (json-int)
2777 - "current": true if this mouse is receiving events, false otherwise (json-bool)
2778 - "absolute": true if the mouse generates absolute input events (json-bool)
2780 Example:
2782 -> { "execute": "query-mice" }
2783 <- {
2784 "return":[
2786 "name":"QEMU Microsoft Mouse",
2787 "index":0,
2788 "current":false,
2789 "absolute":false
2792 "name":"QEMU PS/2 Mouse",
2793 "index":1,
2794 "current":true,
2795 "absolute":true
2800 EQMP
2803 .name = "query-mice",
2804 .args_type = "",
2805 .mhandler.cmd_new = qmp_marshal_input_query_mice,
2808 SQMP
2809 query-vnc
2810 ---------
2812 Show VNC server information.
2814 Return a json-object with server information. Connected clients are returned
2815 as a json-array of json-objects.
2817 The main json-object contains the following:
2819 - "enabled": true or false (json-bool)
2820 - "host": server's IP address (json-string)
2821 - "family": address family (json-string)
2822 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2823 - "service": server's port number (json-string)
2824 - "auth": authentication method (json-string)
2825 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
2826 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
2827 "vencrypt+plain", "vencrypt+tls+none",
2828 "vencrypt+tls+plain", "vencrypt+tls+sasl",
2829 "vencrypt+tls+vnc", "vencrypt+x509+none",
2830 "vencrypt+x509+plain", "vencrypt+x509+sasl",
2831 "vencrypt+x509+vnc", "vnc"
2832 - "clients": a json-array of all connected clients
2834 Clients are described by a json-object, each one contain the following:
2836 - "host": client's IP address (json-string)
2837 - "family": address family (json-string)
2838 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2839 - "service": client's port number (json-string)
2840 - "x509_dname": TLS dname (json-string, optional)
2841 - "sasl_username": SASL username (json-string, optional)
2843 Example:
2845 -> { "execute": "query-vnc" }
2846 <- {
2847 "return":{
2848 "enabled":true,
2849 "host":"0.0.0.0",
2850 "service":"50402",
2851 "auth":"vnc",
2852 "family":"ipv4",
2853 "clients":[
2855 "host":"127.0.0.1",
2856 "service":"50401",
2857 "family":"ipv4"
2863 EQMP
2866 .name = "query-vnc",
2867 .args_type = "",
2868 .mhandler.cmd_new = qmp_marshal_input_query_vnc,
2871 SQMP
2872 query-spice
2873 -----------
2875 Show SPICE server information.
2877 Return a json-object with server information. Connected clients are returned
2878 as a json-array of json-objects.
2880 The main json-object contains the following:
2882 - "enabled": true or false (json-bool)
2883 - "host": server's IP address (json-string)
2884 - "port": server's port number (json-int, optional)
2885 - "tls-port": server's port number (json-int, optional)
2886 - "auth": authentication method (json-string)
2887 - Possible values: "none", "spice"
2888 - "channels": a json-array of all active channels clients
2890 Channels are described by a json-object, each one contain the following:
2892 - "host": client's IP address (json-string)
2893 - "family": address family (json-string)
2894 - Possible values: "ipv4", "ipv6", "unix", "unknown"
2895 - "port": client's port number (json-string)
2896 - "connection-id": spice connection id. All channels with the same id
2897 belong to the same spice session (json-int)
2898 - "channel-type": channel type. "1" is the main control channel, filter for
2899 this one if you want track spice sessions only (json-int)
2900 - "channel-id": channel id. Usually "0", might be different needed when
2901 multiple channels of the same type exist, such as multiple
2902 display channels in a multihead setup (json-int)
2903 - "tls": whevener the channel is encrypted (json-bool)
2905 Example:
2907 -> { "execute": "query-spice" }
2908 <- {
2909 "return": {
2910 "enabled": true,
2911 "auth": "spice",
2912 "port": 5920,
2913 "tls-port": 5921,
2914 "host": "0.0.0.0",
2915 "channels": [
2917 "port": "54924",
2918 "family": "ipv4",
2919 "channel-type": 1,
2920 "connection-id": 1804289383,
2921 "host": "127.0.0.1",
2922 "channel-id": 0,
2923 "tls": true
2926 "port": "36710",
2927 "family": "ipv4",
2928 "channel-type": 4,
2929 "connection-id": 1804289383,
2930 "host": "127.0.0.1",
2931 "channel-id": 0,
2932 "tls": false
2934 [ ... more channels follow ... ]
2939 EQMP
2941 #if defined(CONFIG_SPICE)
2943 .name = "query-spice",
2944 .args_type = "",
2945 .mhandler.cmd_new = qmp_marshal_input_query_spice,
2947 #endif
2949 SQMP
2950 query-name
2951 ----------
2953 Show VM name.
2955 Return a json-object with the following information:
2957 - "name": VM's name (json-string, optional)
2959 Example:
2961 -> { "execute": "query-name" }
2962 <- { "return": { "name": "qemu-name" } }
2964 EQMP
2967 .name = "query-name",
2968 .args_type = "",
2969 .mhandler.cmd_new = qmp_marshal_input_query_name,
2972 SQMP
2973 query-uuid
2974 ----------
2976 Show VM UUID.
2978 Return a json-object with the following information:
2980 - "UUID": Universally Unique Identifier (json-string)
2982 Example:
2984 -> { "execute": "query-uuid" }
2985 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
2987 EQMP
2990 .name = "query-uuid",
2991 .args_type = "",
2992 .mhandler.cmd_new = qmp_marshal_input_query_uuid,
2995 SQMP
2996 query-command-line-options
2997 --------------------------
2999 Show command line option schema.
3001 Return a json-array of command line option schema for all options (or for
3002 the given option), returning an error if the given option doesn't exist.
3004 Each array entry contains the following:
3006 - "option": option name (json-string)
3007 - "parameters": a json-array describes all parameters of the option:
3008 - "name": parameter name (json-string)
3009 - "type": parameter type (one of 'string', 'boolean', 'number',
3010 or 'size')
3011 - "help": human readable description of the parameter
3012 (json-string, optional)
3013 - "default": default value string for the parameter
3014 (json-string, optional)
3016 Example:
3018 -> { "execute": "query-command-line-options", "arguments": { "option": "option-rom" } }
3019 <- { "return": [
3021 "parameters": [
3023 "name": "romfile",
3024 "type": "string"
3027 "name": "bootindex",
3028 "type": "number"
3031 "option": "option-rom"
3036 EQMP
3039 .name = "query-command-line-options",
3040 .args_type = "option:s?",
3041 .mhandler.cmd_new = qmp_marshal_input_query_command_line_options,
3044 SQMP
3045 query-migrate
3046 -------------
3048 Migration status.
3050 Return a json-object. If migration is active there will be another json-object
3051 with RAM migration status and if block migration is active another one with
3052 block migration status.
3054 The main json-object contains the following:
3056 - "status": migration status (json-string)
3057 - Possible values: "setup", "active", "completed", "failed", "cancelled"
3058 - "total-time": total amount of ms since migration started. If
3059 migration has ended, it returns the total migration
3060 time (json-int)
3061 - "setup-time" amount of setup time in milliseconds _before_ the
3062 iterations begin but _after_ the QMP command is issued.
3063 This is designed to provide an accounting of any activities
3064 (such as RDMA pinning) which may be expensive, but do not
3065 actually occur during the iterative migration rounds
3066 themselves. (json-int)
3067 - "downtime": only present when migration has finished correctly
3068 total amount in ms for downtime that happened (json-int)
3069 - "expected-downtime": only present while migration is active
3070 total amount in ms for downtime that was calculated on
3071 the last bitmap round (json-int)
3072 - "ram": only present if "status" is "active", it is a json-object with the
3073 following RAM information:
3074 - "transferred": amount transferred in bytes (json-int)
3075 - "remaining": amount remaining to transfer in bytes (json-int)
3076 - "total": total amount of memory in bytes (json-int)
3077 - "duplicate": number of pages filled entirely with the same
3078 byte (json-int)
3079 These are sent over the wire much more efficiently.
3080 - "skipped": number of skipped zero pages (json-int)
3081 - "normal" : number of whole pages transferred. I.e. they
3082 were not sent as duplicate or xbzrle pages (json-int)
3083 - "normal-bytes" : number of bytes transferred in whole
3084 pages. This is just normal pages times size of one page,
3085 but this way upper levels don't need to care about page
3086 size (json-int)
3087 - "dirty-sync-count": times that dirty ram was synchronized (json-int)
3088 - "disk": only present if "status" is "active" and it is a block migration,
3089 it is a json-object with the following disk information:
3090 - "transferred": amount transferred in bytes (json-int)
3091 - "remaining": amount remaining to transfer in bytes json-int)
3092 - "total": total disk size in bytes (json-int)
3093 - "xbzrle-cache": only present if XBZRLE is active.
3094 It is a json-object with the following XBZRLE information:
3095 - "cache-size": XBZRLE cache size in bytes
3096 - "bytes": number of bytes transferred for XBZRLE compressed pages
3097 - "pages": number of XBZRLE compressed pages
3098 - "cache-miss": number of XBRZRLE page cache misses
3099 - "cache-miss-rate": rate of XBRZRLE page cache misses
3100 - "overflow": number of times XBZRLE overflows. This means
3101 that the XBZRLE encoding was bigger than just sent the
3102 whole page, and then we sent the whole page instead (as as
3103 normal page).
3105 Examples:
3107 1. Before the first migration
3109 -> { "execute": "query-migrate" }
3110 <- { "return": {} }
3112 2. Migration is done and has succeeded
3114 -> { "execute": "query-migrate" }
3115 <- { "return": {
3116 "status": "completed",
3117 "ram":{
3118 "transferred":123,
3119 "remaining":123,
3120 "total":246,
3121 "total-time":12345,
3122 "setup-time":12345,
3123 "downtime":12345,
3124 "duplicate":123,
3125 "normal":123,
3126 "normal-bytes":123456,
3127 "dirty-sync-count":15
3132 3. Migration is done and has failed
3134 -> { "execute": "query-migrate" }
3135 <- { "return": { "status": "failed" } }
3137 4. Migration is being performed and is not a block migration:
3139 -> { "execute": "query-migrate" }
3140 <- {
3141 "return":{
3142 "status":"active",
3143 "ram":{
3144 "transferred":123,
3145 "remaining":123,
3146 "total":246,
3147 "total-time":12345,
3148 "setup-time":12345,
3149 "expected-downtime":12345,
3150 "duplicate":123,
3151 "normal":123,
3152 "normal-bytes":123456,
3153 "dirty-sync-count":15
3158 5. Migration is being performed and is a block migration:
3160 -> { "execute": "query-migrate" }
3161 <- {
3162 "return":{
3163 "status":"active",
3164 "ram":{
3165 "total":1057024,
3166 "remaining":1053304,
3167 "transferred":3720,
3168 "total-time":12345,
3169 "setup-time":12345,
3170 "expected-downtime":12345,
3171 "duplicate":123,
3172 "normal":123,
3173 "normal-bytes":123456,
3174 "dirty-sync-count":15
3176 "disk":{
3177 "total":20971520,
3178 "remaining":20880384,
3179 "transferred":91136
3184 6. Migration is being performed and XBZRLE is active:
3186 -> { "execute": "query-migrate" }
3187 <- {
3188 "return":{
3189 "status":"active",
3190 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
3191 "ram":{
3192 "total":1057024,
3193 "remaining":1053304,
3194 "transferred":3720,
3195 "total-time":12345,
3196 "setup-time":12345,
3197 "expected-downtime":12345,
3198 "duplicate":10,
3199 "normal":3333,
3200 "normal-bytes":3412992,
3201 "dirty-sync-count":15
3203 "xbzrle-cache":{
3204 "cache-size":67108864,
3205 "bytes":20971520,
3206 "pages":2444343,
3207 "cache-miss":2244,
3208 "cache-miss-rate":0.123,
3209 "overflow":34434
3214 EQMP
3217 .name = "query-migrate",
3218 .args_type = "",
3219 .mhandler.cmd_new = qmp_marshal_input_query_migrate,
3222 SQMP
3223 migrate-set-capabilities
3224 ------------------------
3226 Enable/Disable migration capabilities
3228 - "xbzrle": XBZRLE support
3229 - "rdma-pin-all": pin all pages when using RDMA during migration
3230 - "auto-converge": throttle down guest to help convergence of migration
3231 - "zero-blocks": compress zero blocks during block migration
3233 Arguments:
3235 Example:
3237 -> { "execute": "migrate-set-capabilities" , "arguments":
3238 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
3240 EQMP
3243 .name = "migrate-set-capabilities",
3244 .args_type = "capabilities:O",
3245 .params = "capability:s,state:b",
3246 .mhandler.cmd_new = qmp_marshal_input_migrate_set_capabilities,
3248 SQMP
3249 query-migrate-capabilities
3250 --------------------------
3252 Query current migration capabilities
3254 - "capabilities": migration capabilities state
3255 - "xbzrle" : XBZRLE state (json-bool)
3256 - "rdma-pin-all" : RDMA Pin Page state (json-bool)
3257 - "auto-converge" : Auto Converge state (json-bool)
3258 - "zero-blocks" : Zero Blocks state (json-bool)
3260 Arguments:
3262 Example:
3264 -> { "execute": "query-migrate-capabilities" }
3265 <- { "return": [ { "state": false, "capability": "xbzrle" } ] }
3267 EQMP
3270 .name = "query-migrate-capabilities",
3271 .args_type = "",
3272 .mhandler.cmd_new = qmp_marshal_input_query_migrate_capabilities,
3275 SQMP
3276 query-balloon
3277 -------------
3279 Show balloon information.
3281 Make an asynchronous request for balloon info. When the request completes a
3282 json-object will be returned containing the following data:
3284 - "actual": current balloon value in bytes (json-int)
3286 Example:
3288 -> { "execute": "query-balloon" }
3289 <- {
3290 "return":{
3291 "actual":1073741824,
3295 EQMP
3298 .name = "query-balloon",
3299 .args_type = "",
3300 .mhandler.cmd_new = qmp_marshal_input_query_balloon,
3304 .name = "query-block-jobs",
3305 .args_type = "",
3306 .mhandler.cmd_new = qmp_marshal_input_query_block_jobs,
3310 .name = "qom-list",
3311 .args_type = "path:s",
3312 .mhandler.cmd_new = qmp_marshal_input_qom_list,
3316 .name = "qom-set",
3317 .args_type = "path:s,property:s,value:q",
3318 .mhandler.cmd_new = qmp_qom_set,
3322 .name = "qom-get",
3323 .args_type = "path:s,property:s",
3324 .mhandler.cmd_new = qmp_qom_get,
3328 .name = "nbd-server-start",
3329 .args_type = "addr:q",
3330 .mhandler.cmd_new = qmp_marshal_input_nbd_server_start,
3333 .name = "nbd-server-add",
3334 .args_type = "device:B,writable:b?",
3335 .mhandler.cmd_new = qmp_marshal_input_nbd_server_add,
3338 .name = "nbd-server-stop",
3339 .args_type = "",
3340 .mhandler.cmd_new = qmp_marshal_input_nbd_server_stop,
3344 .name = "change-vnc-password",
3345 .args_type = "password:s",
3346 .mhandler.cmd_new = qmp_marshal_input_change_vnc_password,
3349 .name = "qom-list-types",
3350 .args_type = "implements:s?,abstract:b?",
3351 .mhandler.cmd_new = qmp_marshal_input_qom_list_types,
3355 .name = "device-list-properties",
3356 .args_type = "typename:s",
3357 .mhandler.cmd_new = qmp_marshal_input_device_list_properties,
3361 .name = "query-machines",
3362 .args_type = "",
3363 .mhandler.cmd_new = qmp_marshal_input_query_machines,
3367 .name = "query-cpu-definitions",
3368 .args_type = "",
3369 .mhandler.cmd_new = qmp_marshal_input_query_cpu_definitions,
3373 .name = "query-target",
3374 .args_type = "",
3375 .mhandler.cmd_new = qmp_marshal_input_query_target,
3379 .name = "query-tpm",
3380 .args_type = "",
3381 .mhandler.cmd_new = qmp_marshal_input_query_tpm,
3384 SQMP
3385 query-tpm
3386 ---------
3388 Return information about the TPM device.
3390 Arguments: None
3392 Example:
3394 -> { "execute": "query-tpm" }
3395 <- { "return":
3397 { "model": "tpm-tis",
3398 "options":
3399 { "type": "passthrough",
3400 "data":
3401 { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
3402 "path": "/dev/tpm0"
3405 "id": "tpm0"
3410 EQMP
3413 .name = "query-tpm-models",
3414 .args_type = "",
3415 .mhandler.cmd_new = qmp_marshal_input_query_tpm_models,
3418 SQMP
3419 query-tpm-models
3420 ----------------
3422 Return a list of supported TPM models.
3424 Arguments: None
3426 Example:
3428 -> { "execute": "query-tpm-models" }
3429 <- { "return": [ "tpm-tis" ] }
3431 EQMP
3434 .name = "query-tpm-types",
3435 .args_type = "",
3436 .mhandler.cmd_new = qmp_marshal_input_query_tpm_types,
3439 SQMP
3440 query-tpm-types
3441 ---------------
3443 Return a list of supported TPM types.
3445 Arguments: None
3447 Example:
3449 -> { "execute": "query-tpm-types" }
3450 <- { "return": [ "passthrough" ] }
3452 EQMP
3455 .name = "chardev-add",
3456 .args_type = "id:s,backend:q",
3457 .mhandler.cmd_new = qmp_marshal_input_chardev_add,
3460 SQMP
3461 chardev-add
3462 ----------------
3464 Add a chardev.
3466 Arguments:
3468 - "id": the chardev's ID, must be unique (json-string)
3469 - "backend": chardev backend type + parameters
3471 Examples:
3473 -> { "execute" : "chardev-add",
3474 "arguments" : { "id" : "foo",
3475 "backend" : { "type" : "null", "data" : {} } } }
3476 <- { "return": {} }
3478 -> { "execute" : "chardev-add",
3479 "arguments" : { "id" : "bar",
3480 "backend" : { "type" : "file",
3481 "data" : { "out" : "/tmp/bar.log" } } } }
3482 <- { "return": {} }
3484 -> { "execute" : "chardev-add",
3485 "arguments" : { "id" : "baz",
3486 "backend" : { "type" : "pty", "data" : {} } } }
3487 <- { "return": { "pty" : "/dev/pty/42" } }
3489 EQMP
3492 .name = "chardev-remove",
3493 .args_type = "id:s",
3494 .mhandler.cmd_new = qmp_marshal_input_chardev_remove,
3498 SQMP
3499 chardev-remove
3500 --------------
3502 Remove a chardev.
3504 Arguments:
3506 - "id": the chardev's ID, must exist and not be in use (json-string)
3508 Example:
3510 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }
3511 <- { "return": {} }
3513 EQMP
3515 .name = "query-rx-filter",
3516 .args_type = "name:s?",
3517 .mhandler.cmd_new = qmp_marshal_input_query_rx_filter,
3520 SQMP
3521 query-rx-filter
3522 ---------------
3524 Show rx-filter information.
3526 Returns a json-array of rx-filter information for all NICs (or for the
3527 given NIC), returning an error if the given NIC doesn't exist, or
3528 given NIC doesn't support rx-filter querying, or given net client
3529 isn't a NIC.
3531 The query will clear the event notification flag of each NIC, then qemu
3532 will start to emit event to QMP monitor.
3534 Each array entry contains the following:
3536 - "name": net client name (json-string)
3537 - "promiscuous": promiscuous mode is enabled (json-bool)
3538 - "multicast": multicast receive state (one of 'normal', 'none', 'all')
3539 - "unicast": unicast receive state (one of 'normal', 'none', 'all')
3540 - "vlan": vlan receive state (one of 'normal', 'none', 'all') (Since 2.0)
3541 - "broadcast-allowed": allow to receive broadcast (json-bool)
3542 - "multicast-overflow": multicast table is overflowed (json-bool)
3543 - "unicast-overflow": unicast table is overflowed (json-bool)
3544 - "main-mac": main macaddr string (json-string)
3545 - "vlan-table": a json-array of active vlan id
3546 - "unicast-table": a json-array of unicast macaddr string
3547 - "multicast-table": a json-array of multicast macaddr string
3549 Example:
3551 -> { "execute": "query-rx-filter", "arguments": { "name": "vnet0" } }
3552 <- { "return": [
3554 "promiscuous": true,
3555 "name": "vnet0",
3556 "main-mac": "52:54:00:12:34:56",
3557 "unicast": "normal",
3558 "vlan": "normal",
3559 "vlan-table": [
3563 "unicast-table": [
3565 "multicast": "normal",
3566 "multicast-overflow": false,
3567 "unicast-overflow": false,
3568 "multicast-table": [
3569 "01:00:5e:00:00:01",
3570 "33:33:00:00:00:01",
3571 "33:33:ff:12:34:56"
3573 "broadcast-allowed": false
3578 EQMP
3581 .name = "blockdev-add",
3582 .args_type = "options:q",
3583 .mhandler.cmd_new = qmp_marshal_input_blockdev_add,
3586 SQMP
3587 blockdev-add
3588 ------------
3590 Add a block device.
3592 Arguments:
3594 - "options": block driver options
3596 Example (1):
3598 -> { "execute": "blockdev-add",
3599 "arguments": { "options" : { "driver": "qcow2",
3600 "file": { "driver": "file",
3601 "filename": "test.qcow2" } } } }
3602 <- { "return": {} }
3604 Example (2):
3606 -> { "execute": "blockdev-add",
3607 "arguments": {
3608 "options": {
3609 "driver": "qcow2",
3610 "id": "my_disk",
3611 "discard": "unmap",
3612 "cache": {
3613 "direct": true,
3614 "writeback": true
3616 "file": {
3617 "driver": "file",
3618 "filename": "/tmp/test.qcow2"
3620 "backing": {
3621 "driver": "raw",
3622 "file": {
3623 "driver": "file",
3624 "filename": "/dev/fdset/4"
3631 <- { "return": {} }
3633 EQMP
3636 .name = "query-named-block-nodes",
3637 .args_type = "",
3638 .mhandler.cmd_new = qmp_marshal_input_query_named_block_nodes,
3641 SQMP
3642 @query-named-block-nodes
3643 ------------------------
3645 Return a list of BlockDeviceInfo for all the named block driver nodes
3647 Example:
3649 -> { "execute": "query-named-block-nodes" }
3650 <- { "return": [ { "ro":false,
3651 "drv":"qcow2",
3652 "encrypted":false,
3653 "file":"disks/test.qcow2",
3654 "node-name": "my-node",
3655 "backing_file_depth":1,
3656 "bps":1000000,
3657 "bps_rd":0,
3658 "bps_wr":0,
3659 "iops":1000000,
3660 "iops_rd":0,
3661 "iops_wr":0,
3662 "bps_max": 8000000,
3663 "bps_rd_max": 0,
3664 "bps_wr_max": 0,
3665 "iops_max": 0,
3666 "iops_rd_max": 0,
3667 "iops_wr_max": 0,
3668 "iops_size": 0,
3669 "image":{
3670 "filename":"disks/test.qcow2",
3671 "format":"qcow2",
3672 "virtual-size":2048000,
3673 "backing_file":"base.qcow2",
3674 "full-backing-filename":"disks/base.qcow2",
3675 "backing-filename-format:"qcow2",
3676 "snapshots":[
3678 "id": "1",
3679 "name": "snapshot1",
3680 "vm-state-size": 0,
3681 "date-sec": 10000200,
3682 "date-nsec": 12,
3683 "vm-clock-sec": 206,
3684 "vm-clock-nsec": 30
3687 "backing-image":{
3688 "filename":"disks/base.qcow2",
3689 "format":"qcow2",
3690 "virtual-size":2048000
3692 } } ] }
3694 EQMP
3697 .name = "query-memdev",
3698 .args_type = "",
3699 .mhandler.cmd_new = qmp_marshal_input_query_memdev,
3702 SQMP
3703 query-memdev
3704 ------------
3706 Show memory devices information.
3709 Example (1):
3711 -> { "execute": "query-memdev" }
3712 <- { "return": [
3714 "size": 536870912,
3715 "merge": false,
3716 "dump": true,
3717 "prealloc": false,
3718 "host-nodes": [0, 1],
3719 "policy": "bind"
3722 "size": 536870912,
3723 "merge": false,
3724 "dump": true,
3725 "prealloc": true,
3726 "host-nodes": [2, 3],
3727 "policy": "preferred"
3732 EQMP
3735 .name = "query-memory-devices",
3736 .args_type = "",
3737 .mhandler.cmd_new = qmp_marshal_input_query_memory_devices,
3740 SQMP
3741 @query-memory-devices
3742 --------------------
3744 Return a list of memory devices.
3746 Example:
3747 -> { "execute": "query-memory-devices" }
3748 <- { "return": [ { "data":
3749 { "addr": 5368709120,
3750 "hotpluggable": true,
3751 "hotplugged": true,
3752 "id": "d1",
3753 "memdev": "/objects/memX",
3754 "node": 0,
3755 "size": 1073741824,
3756 "slot": 0},
3757 "type": "dimm"
3758 } ] }
3759 EQMP
3762 .name = "query-acpi-ospm-status",
3763 .args_type = "",
3764 .mhandler.cmd_new = qmp_marshal_input_query_acpi_ospm_status,
3767 SQMP
3768 @query-acpi-ospm-status
3769 --------------------
3771 Return list of ACPIOSTInfo for devices that support status reporting
3772 via ACPI _OST method.
3774 Example:
3775 -> { "execute": "query-acpi-ospm-status" }
3776 <- { "return": [ { "device": "d1", "slot": "0", "slot-type": "DIMM", "source": 1, "status": 0},
3777 { "slot": "1", "slot-type": "DIMM", "source": 0, "status": 0},
3778 { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
3779 { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
3781 EQMP
3783 #if defined TARGET_I386
3785 .name = "rtc-reset-reinjection",
3786 .args_type = "",
3787 .mhandler.cmd_new = qmp_marshal_input_rtc_reset_reinjection,
3789 #endif
3791 SQMP
3792 rtc-reset-reinjection
3793 ---------------------
3795 Reset the RTC interrupt reinjection backlog.
3797 Arguments: None.
3799 Example:
3801 -> { "execute": "rtc-reset-reinjection" }
3802 <- { "return": {} }
3803 EQMP
3806 .name = "trace-event-get-state",
3807 .args_type = "name:s",
3808 .mhandler.cmd_new = qmp_marshal_input_trace_event_get_state,
3811 SQMP
3812 trace-event-get-state
3813 ---------------------
3815 Query the state of events.
3817 Example:
3819 -> { "execute": "trace-event-get-state", "arguments": { "name": "qemu_memalign" } }
3820 <- { "return": [ { "name": "qemu_memalign", "state": "disabled" } ] }
3821 EQMP
3824 .name = "trace-event-set-state",
3825 .args_type = "name:s,enable:b,ignore-unavailable:b?",
3826 .mhandler.cmd_new = qmp_marshal_input_trace_event_set_state,
3829 SQMP
3830 trace-event-set-state
3831 ---------------------
3833 Set the state of events.
3835 Example:
3837 -> { "execute": "trace-event-set-state", "arguments": { "name": "qemu_memalign", "enable": "true" } }
3838 <- { "return": {} }
3839 EQMP
3842 .name = "x-input-send-event",
3843 .args_type = "console:i?,events:q",
3844 .mhandler.cmd_new = qmp_marshal_input_x_input_send_event,
3847 SQMP
3848 @x-input-send-event
3849 -----------------
3851 Send input event to guest.
3853 Arguments:
3855 - "console": console index. (json-int, optional)
3856 - "events": list of input events.
3858 The consoles are visible in the qom tree, under
3859 /backend/console[$index]. They have a device link and head property, so
3860 it is possible to map which console belongs to which device and display.
3862 Note: this command is experimental, and not a stable API.
3864 Example (1):
3866 Press left mouse button.
3868 -> { "execute": "x-input-send-event",
3869 "arguments": { "console": 0,
3870 "events": [ { "type": "btn",
3871 "data" : { "down": true, "button": "Left" } } ] } }
3872 <- { "return": {} }
3874 -> { "execute": "x-input-send-event",
3875 "arguments": { "console": 0,
3876 "events": [ { "type": "btn",
3877 "data" : { "down": false, "button": "Left" } } ] } }
3878 <- { "return": {} }
3880 Example (2):
3882 Press ctrl-alt-del.
3884 -> { "execute": "x-input-send-event",
3885 "arguments": { "console": 0, "events": [
3886 { "type": "key", "data" : { "down": true,
3887 "key": {"type": "qcode", "data": "ctrl" } } },
3888 { "type": "key", "data" : { "down": true,
3889 "key": {"type": "qcode", "data": "alt" } } },
3890 { "type": "key", "data" : { "down": true,
3891 "key": {"type": "qcode", "data": "delete" } } } ] } }
3892 <- { "return": {} }
3894 Example (3):
3896 Move mouse pointer to absolute coordinates (20000, 400).
3898 -> { "execute": "x-input-send-event" ,
3899 "arguments": { "console": 0, "events": [
3900 { "type": "abs", "data" : { "axis": "X", "value" : 20000 } },
3901 { "type": "abs", "data" : { "axis": "Y", "value" : 400 } } ] } }
3902 <- { "return": {} }
3904 EQMP