bios-linker-loader: document+validate input
[qemu.git] / qmp-commands.hx
blob085dc7d5cd3cfad1ed7c03e06cf14e8cafd7476b
1 HXCOMM QMP dispatch table and documentation
2 HXCOMM Text between SQMP and EQMP is copied to the QMP documentation 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_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_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_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_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_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_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_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_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_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 .mhandler.cmd_new = qmp_device_add,
282 SQMP
283 device_add
284 ----------
286 Add a device.
288 Arguments:
290 - "driver": the name of the new device's driver (json-string)
291 - "bus": the device's parent bus (device tree path, json-string, optional)
292 - "id": the device's ID, must be unique (json-string)
293 - device properties
295 Example:
297 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
298 <- { "return": {} }
300 Notes:
302 (1) For detailed information about this command, please refer to the
303 'docs/qdev-device-use.txt' file.
305 (2) It's possible to list device properties by running QEMU with the
306 "-device DEVICE,\?" command-line argument, where DEVICE is the device's name
308 EQMP
311 .name = "device_del",
312 .args_type = "id:s",
313 .mhandler.cmd_new = qmp_marshal_device_del,
316 SQMP
317 device_del
318 ----------
320 Remove a device.
322 Arguments:
324 - "id": the device's ID or QOM path (json-string)
326 Example:
328 -> { "execute": "device_del", "arguments": { "id": "net1" } }
329 <- { "return": {} }
331 Example:
333 -> { "execute": "device_del", "arguments": { "id": "/machine/peripheral-anon/device[0]" } }
334 <- { "return": {} }
336 EQMP
339 .name = "send-key",
340 .args_type = "keys:q,hold-time:i?",
341 .mhandler.cmd_new = qmp_marshal_send_key,
344 SQMP
345 send-key
346 ----------
348 Send keys to VM.
350 Arguments:
352 keys array:
353 - "key": key sequence (a json-array of key union values,
354 union can be number or qcode enum)
356 - hold-time: time to delay key up events, milliseconds. Defaults to 100
357 (json-int, optional)
359 Example:
361 -> { "execute": "send-key",
362 "arguments": { "keys": [ { "type": "qcode", "data": "ctrl" },
363 { "type": "qcode", "data": "alt" },
364 { "type": "qcode", "data": "delete" } ] } }
365 <- { "return": {} }
367 EQMP
370 .name = "cpu",
371 .args_type = "index:i",
372 .mhandler.cmd_new = qmp_marshal_cpu,
375 SQMP
379 Set the default CPU.
381 Arguments:
383 - "index": the CPU's index (json-int)
385 Example:
387 -> { "execute": "cpu", "arguments": { "index": 0 } }
388 <- { "return": {} }
390 Note: CPUs' indexes are obtained with the 'query-cpus' command.
392 EQMP
395 .name = "cpu-add",
396 .args_type = "id:i",
397 .mhandler.cmd_new = qmp_marshal_cpu_add,
400 SQMP
401 cpu-add
402 -------
404 Adds virtual cpu
406 Arguments:
408 - "id": cpu id (json-int)
410 Example:
412 -> { "execute": "cpu-add", "arguments": { "id": 2 } }
413 <- { "return": {} }
415 EQMP
418 .name = "memsave",
419 .args_type = "val:l,size:i,filename:s,cpu:i?",
420 .mhandler.cmd_new = qmp_marshal_memsave,
423 SQMP
424 memsave
425 -------
427 Save to disk virtual memory dump starting at 'val' of size 'size'.
429 Arguments:
431 - "val": the starting address (json-int)
432 - "size": the memory size, in bytes (json-int)
433 - "filename": file path (json-string)
434 - "cpu": virtual CPU index (json-int, optional)
436 Example:
438 -> { "execute": "memsave",
439 "arguments": { "val": 10,
440 "size": 100,
441 "filename": "/tmp/virtual-mem-dump" } }
442 <- { "return": {} }
444 EQMP
447 .name = "pmemsave",
448 .args_type = "val:l,size:i,filename:s",
449 .mhandler.cmd_new = qmp_marshal_pmemsave,
452 SQMP
453 pmemsave
454 --------
456 Save to disk physical memory dump starting at 'val' of size 'size'.
458 Arguments:
460 - "val": the starting address (json-int)
461 - "size": the memory size, in bytes (json-int)
462 - "filename": file path (json-string)
464 Example:
466 -> { "execute": "pmemsave",
467 "arguments": { "val": 10,
468 "size": 100,
469 "filename": "/tmp/physical-mem-dump" } }
470 <- { "return": {} }
472 EQMP
475 .name = "inject-nmi",
476 .args_type = "",
477 .mhandler.cmd_new = qmp_marshal_inject_nmi,
480 SQMP
481 inject-nmi
482 ----------
484 Inject an NMI on the default CPU (x86/s390) or all CPUs (ppc64).
486 Arguments: None.
488 Example:
490 -> { "execute": "inject-nmi" }
491 <- { "return": {} }
493 Note: inject-nmi fails when the guest doesn't support injecting.
495 EQMP
498 .name = "ringbuf-write",
499 .args_type = "device:s,data:s,format:s?",
500 .mhandler.cmd_new = qmp_marshal_ringbuf_write,
503 SQMP
504 ringbuf-write
505 -------------
507 Write to a ring buffer character device.
509 Arguments:
511 - "device": ring buffer character device name (json-string)
512 - "data": data to write (json-string)
513 - "format": data format (json-string, optional)
514 - Possible values: "utf8" (default), "base64"
516 Example:
518 -> { "execute": "ringbuf-write",
519 "arguments": { "device": "foo",
520 "data": "abcdefgh",
521 "format": "utf8" } }
522 <- { "return": {} }
524 EQMP
527 .name = "ringbuf-read",
528 .args_type = "device:s,size:i,format:s?",
529 .mhandler.cmd_new = qmp_marshal_ringbuf_read,
532 SQMP
533 ringbuf-read
534 -------------
536 Read from a ring buffer character device.
538 Arguments:
540 - "device": ring buffer character device name (json-string)
541 - "size": how many bytes to read at most (json-int)
542 - Number of data bytes, not number of characters in encoded data
543 - "format": data format (json-string, optional)
544 - Possible values: "utf8" (default), "base64"
545 - Naturally, format "utf8" works only when the ring buffer
546 contains valid UTF-8 text. Invalid UTF-8 sequences get
547 replaced. Bug: replacement doesn't work. Bug: can screw
548 up on encountering NUL characters, after the ring buffer
549 lost data, and when reading stops because the size limit
550 is reached.
552 Example:
554 -> { "execute": "ringbuf-read",
555 "arguments": { "device": "foo",
556 "size": 1000,
557 "format": "utf8" } }
558 <- {"return": "abcdefgh"}
560 EQMP
563 .name = "xen-save-devices-state",
564 .args_type = "filename:F",
565 .mhandler.cmd_new = qmp_marshal_xen_save_devices_state,
568 SQMP
569 xen-save-devices-state
570 -------
572 Save the state of all devices to file. The RAM and the block devices
573 of the VM are not saved by this command.
575 Arguments:
577 - "filename": the file to save the state of the devices to as binary
578 data. See xen-save-devices-state.txt for a description of the binary
579 format.
581 Example:
583 -> { "execute": "xen-save-devices-state",
584 "arguments": { "filename": "/tmp/save" } }
585 <- { "return": {} }
587 EQMP
590 .name = "xen-set-global-dirty-log",
591 .args_type = "enable:b",
592 .mhandler.cmd_new = qmp_marshal_xen_set_global_dirty_log,
595 SQMP
596 xen-set-global-dirty-log
597 -------
599 Enable or disable the global dirty log mode.
601 Arguments:
603 - "enable": Enable it or disable it.
605 Example:
607 -> { "execute": "xen-set-global-dirty-log",
608 "arguments": { "enable": true } }
609 <- { "return": {} }
611 EQMP
614 .name = "migrate",
615 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
616 .mhandler.cmd_new = qmp_marshal_migrate,
619 SQMP
620 migrate
621 -------
623 Migrate to URI.
625 Arguments:
627 - "blk": block migration, full disk copy (json-bool, optional)
628 - "inc": incremental disk copy (json-bool, optional)
629 - "uri": Destination URI (json-string)
631 Example:
633 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
634 <- { "return": {} }
636 Notes:
638 (1) The 'query-migrate' command should be used to check migration's progress
639 and final result (this information is provided by the 'status' member)
640 (2) All boolean arguments default to false
641 (3) The user Monitor's "detach" argument is invalid in QMP and should not
642 be used
644 EQMP
647 .name = "migrate_cancel",
648 .args_type = "",
649 .mhandler.cmd_new = qmp_marshal_migrate_cancel,
652 SQMP
653 migrate_cancel
654 --------------
656 Cancel the current migration.
658 Arguments: None.
660 Example:
662 -> { "execute": "migrate_cancel" }
663 <- { "return": {} }
665 EQMP
668 .name = "migrate-incoming",
669 .args_type = "uri:s",
670 .mhandler.cmd_new = qmp_marshal_migrate_incoming,
673 SQMP
674 migrate-incoming
675 ----------------
677 Continue an incoming migration
679 Arguments:
681 - "uri": Source/listening URI (json-string)
683 Example:
685 -> { "execute": "migrate-incoming", "arguments": { "uri": "tcp::4446" } }
686 <- { "return": {} }
688 Notes:
690 (1) QEMU must be started with -incoming defer to allow migrate-incoming to
691 be used
692 (2) The uri format is the same as for -incoming
694 EQMP
696 .name = "migrate-set-cache-size",
697 .args_type = "value:o",
698 .mhandler.cmd_new = qmp_marshal_migrate_set_cache_size,
701 SQMP
702 migrate-set-cache-size
703 ----------------------
705 Set cache size to be used by XBZRLE migration, the cache size will be rounded
706 down to the nearest power of 2
708 Arguments:
710 - "value": cache size in bytes (json-int)
712 Example:
714 -> { "execute": "migrate-set-cache-size", "arguments": { "value": 536870912 } }
715 <- { "return": {} }
717 EQMP
719 .name = "migrate-start-postcopy",
720 .args_type = "",
721 .mhandler.cmd_new = qmp_marshal_migrate_start_postcopy,
724 SQMP
725 migrate-start-postcopy
726 ----------------------
728 Switch an in-progress migration to postcopy mode. Ignored after the end of
729 migration (or once already in postcopy).
731 Example:
732 -> { "execute": "migrate-start-postcopy" }
733 <- { "return": {} }
735 EQMP
738 .name = "query-migrate-cache-size",
739 .args_type = "",
740 .mhandler.cmd_new = qmp_marshal_query_migrate_cache_size,
743 SQMP
744 query-migrate-cache-size
745 ------------------------
747 Show cache size to be used by XBZRLE migration
749 returns a json-object with the following information:
750 - "size" : json-int
752 Example:
754 -> { "execute": "query-migrate-cache-size" }
755 <- { "return": 67108864 }
757 EQMP
760 .name = "migrate_set_speed",
761 .args_type = "value:o",
762 .mhandler.cmd_new = qmp_marshal_migrate_set_speed,
765 SQMP
766 migrate_set_speed
767 -----------------
769 Set maximum speed for migrations.
771 Arguments:
773 - "value": maximum speed, in bytes per second (json-int)
775 Example:
777 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
778 <- { "return": {} }
780 EQMP
783 .name = "migrate_set_downtime",
784 .args_type = "value:T",
785 .mhandler.cmd_new = qmp_marshal_migrate_set_downtime,
788 SQMP
789 migrate_set_downtime
790 --------------------
792 Set maximum tolerated downtime (in seconds) for migrations.
794 Arguments:
796 - "value": maximum downtime (json-number)
798 Example:
800 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
801 <- { "return": {} }
803 EQMP
806 .name = "client_migrate_info",
807 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
808 .params = "protocol hostname port tls-port cert-subject",
809 .help = "set migration information for remote display",
810 .mhandler.cmd_new = qmp_marshal_client_migrate_info,
813 SQMP
814 client_migrate_info
815 -------------------
817 Set migration information for remote display. This makes the server
818 ask the client to automatically reconnect using the new parameters
819 once migration finished successfully. Only implemented for SPICE.
821 Arguments:
823 - "protocol": must be "spice" (json-string)
824 - "hostname": migration target hostname (json-string)
825 - "port": spice tcp port for plaintext channels (json-int, optional)
826 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
827 - "cert-subject": server certificate subject (json-string, optional)
829 Example:
831 -> { "execute": "client_migrate_info",
832 "arguments": { "protocol": "spice",
833 "hostname": "virt42.lab.kraxel.org",
834 "port": 1234 } }
835 <- { "return": {} }
837 EQMP
840 .name = "dump-guest-memory",
841 .args_type = "paging:b,protocol:s,begin:i?,end:i?,format:s?",
842 .params = "-p protocol [begin] [length] [format]",
843 .help = "dump guest memory to file",
844 .mhandler.cmd_new = qmp_marshal_dump_guest_memory,
847 SQMP
848 dump
851 Dump guest memory to file. The file can be processed with crash or gdb.
853 Arguments:
855 - "paging": do paging to get guest's memory mapping (json-bool)
856 - "protocol": destination file(started with "file:") or destination file
857 descriptor (started with "fd:") (json-string)
858 - "begin": the starting physical address. It's optional, and should be specified
859 with length together (json-int)
860 - "length": the memory size, in bytes. It's optional, and should be specified
861 with begin together (json-int)
862 - "format": the format of guest memory dump. It's optional, and can be
863 elf|kdump-zlib|kdump-lzo|kdump-snappy, but non-elf formats will
864 conflict with paging and filter, ie. begin and length (json-string)
866 Example:
868 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
869 <- { "return": {} }
871 Notes:
873 (1) All boolean arguments default to false
875 EQMP
878 .name = "query-dump-guest-memory-capability",
879 .args_type = "",
880 .mhandler.cmd_new = qmp_marshal_query_dump_guest_memory_capability,
883 SQMP
884 query-dump-guest-memory-capability
885 ----------
887 Show available formats for 'dump-guest-memory'
889 Example:
891 -> { "execute": "query-dump-guest-memory-capability" }
892 <- { "return": { "formats":
893 ["elf", "kdump-zlib", "kdump-lzo", "kdump-snappy"] }
895 EQMP
897 #if defined TARGET_S390X
899 .name = "dump-skeys",
900 .args_type = "filename:F",
901 .mhandler.cmd_new = qmp_marshal_dump_skeys,
903 #endif
905 SQMP
906 dump-skeys
907 ----------
909 Save guest storage keys to file.
911 Arguments:
913 - "filename": file path (json-string)
915 Example:
917 -> { "execute": "dump-skeys", "arguments": { "filename": "/tmp/skeys" } }
918 <- { "return": {} }
920 EQMP
923 .name = "netdev_add",
924 .args_type = "netdev:O",
925 .mhandler.cmd_new = qmp_netdev_add,
928 SQMP
929 netdev_add
930 ----------
932 Add host network device.
934 Arguments:
936 - "type": the device type, "tap", "user", ... (json-string)
937 - "id": the device's ID, must be unique (json-string)
938 - device options
940 Example:
942 -> { "execute": "netdev_add",
943 "arguments": { "type": "user", "id": "netdev1",
944 "dnssearch": "example.org" } }
945 <- { "return": {} }
947 Note: The supported device options are the same ones supported by the '-netdev'
948 command-line argument, which are listed in the '-help' output or QEMU's
949 manual
951 EQMP
954 .name = "netdev_del",
955 .args_type = "id:s",
956 .mhandler.cmd_new = qmp_marshal_netdev_del,
959 SQMP
960 netdev_del
961 ----------
963 Remove host network device.
965 Arguments:
967 - "id": the device's ID, must be unique (json-string)
969 Example:
971 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
972 <- { "return": {} }
975 EQMP
978 .name = "object-add",
979 .args_type = "qom-type:s,id:s,props:q?",
980 .mhandler.cmd_new = qmp_marshal_object_add,
983 SQMP
984 object-add
985 ----------
987 Create QOM object.
989 Arguments:
991 - "qom-type": the object's QOM type, i.e. the class name (json-string)
992 - "id": the object's ID, must be unique (json-string)
993 - "props": a dictionary of object property values (optional, json-dict)
995 Example:
997 -> { "execute": "object-add", "arguments": { "qom-type": "rng-random", "id": "rng1",
998 "props": { "filename": "/dev/hwrng" } } }
999 <- { "return": {} }
1001 EQMP
1004 .name = "object-del",
1005 .args_type = "id:s",
1006 .mhandler.cmd_new = qmp_marshal_object_del,
1009 SQMP
1010 object-del
1011 ----------
1013 Remove QOM object.
1015 Arguments:
1017 - "id": the object's ID (json-string)
1019 Example:
1021 -> { "execute": "object-del", "arguments": { "id": "rng1" } }
1022 <- { "return": {} }
1025 EQMP
1029 .name = "block_resize",
1030 .args_type = "device:s?,node-name:s?,size:o",
1031 .mhandler.cmd_new = qmp_marshal_block_resize,
1034 SQMP
1035 block_resize
1036 ------------
1038 Resize a block image while a guest is running.
1040 Arguments:
1042 - "device": the device's ID, must be unique (json-string)
1043 - "node-name": the node name in the block driver state graph (json-string)
1044 - "size": new size
1046 Example:
1048 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
1049 <- { "return": {} }
1051 EQMP
1054 .name = "block-stream",
1055 .args_type = "device:B,base:s?,speed:o?,backing-file:s?,on-error:s?",
1056 .mhandler.cmd_new = qmp_marshal_block_stream,
1059 SQMP
1060 block-stream
1061 ------------
1063 Copy data from a backing file into a block device.
1065 Arguments:
1067 - "device": The device's ID, must be unique (json-string)
1068 - "base": The file name of the backing image above which copying starts
1069 (json-string, optional)
1070 - "backing-file": The backing file string to write into the active layer. This
1071 filename is not validated.
1073 If a pathname string is such that it cannot be resolved by
1074 QEMU, that means that subsequent QMP or HMP commands must use
1075 node-names for the image in question, as filename lookup
1076 methods will fail.
1078 If not specified, QEMU will automatically determine the
1079 backing file string to use, or error out if there is no
1080 obvious choice. Care should be taken when specifying the
1081 string, to specify a valid filename or protocol.
1082 (json-string, optional) (Since 2.1)
1083 - "speed": the maximum speed, in bytes per second (json-int, optional)
1084 - "on-error": the action to take on an error (default 'report'). 'stop' and
1085 'enospc' can only be used if the block device supports io-status.
1086 (json-string, optional) (Since 2.1)
1088 Example:
1090 -> { "execute": "block-stream", "arguments": { "device": "virtio0",
1091 "base": "/tmp/master.qcow2" } }
1092 <- { "return": {} }
1094 EQMP
1097 .name = "block-commit",
1098 .args_type = "device:B,base:s?,top:s?,backing-file:s?,speed:o?",
1099 .mhandler.cmd_new = qmp_marshal_block_commit,
1102 SQMP
1103 block-commit
1104 ------------
1106 Live commit of data from overlay image nodes into backing nodes - i.e., writes
1107 data between 'top' and 'base' into 'base'.
1109 Arguments:
1111 - "device": The device's ID, must be unique (json-string)
1112 - "base": The file name of the backing image to write data into.
1113 If not specified, this is the deepest backing image
1114 (json-string, optional)
1115 - "top": The file name of the backing image within the image chain,
1116 which contains the topmost data to be committed down. If
1117 not specified, this is the active layer. (json-string, optional)
1119 - backing-file: The backing file string to write into the overlay
1120 image of 'top'. If 'top' is the active layer,
1121 specifying a backing file string is an error. This
1122 filename is not validated.
1124 If a pathname string is such that it cannot be
1125 resolved by QEMU, that means that subsequent QMP or
1126 HMP commands must use node-names for the image in
1127 question, as filename lookup methods will fail.
1129 If not specified, QEMU will automatically determine
1130 the backing file string to use, or error out if
1131 there is no obvious choice. Care should be taken
1132 when specifying the string, to specify a valid
1133 filename or protocol.
1134 (json-string, optional) (Since 2.1)
1136 If top == base, that is an error.
1137 If top == active, the job will not be completed by itself,
1138 user needs to complete the job with the block-job-complete
1139 command after getting the ready event. (Since 2.0)
1141 If the base image is smaller than top, then the base image
1142 will be resized to be the same size as top. If top is
1143 smaller than the base image, the base will not be
1144 truncated. If you want the base image size to match the
1145 size of the smaller top, you can safely truncate it
1146 yourself once the commit operation successfully completes.
1147 (json-string)
1148 - "speed": the maximum speed, in bytes per second (json-int, optional)
1151 Example:
1153 -> { "execute": "block-commit", "arguments": { "device": "virtio0",
1154 "top": "/tmp/snap1.qcow2" } }
1155 <- { "return": {} }
1157 EQMP
1160 .name = "drive-backup",
1161 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1162 "bitmap:s?,on-source-error:s?,on-target-error:s?",
1163 .mhandler.cmd_new = qmp_marshal_drive_backup,
1166 SQMP
1167 drive-backup
1168 ------------
1170 Start a point-in-time copy of a block device to a new destination. The
1171 status of ongoing drive-backup operations can be checked with
1172 query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1173 The operation can be stopped before it has completed using the
1174 block-job-cancel command.
1176 Arguments:
1178 - "device": the name of the device which should be copied.
1179 (json-string)
1180 - "target": the target of the new image. If the file exists, or if it is a
1181 device, the existing file/device will be used as the new
1182 destination. If it does not exist, a new file will be created.
1183 (json-string)
1184 - "format": the format of the new destination, default is to probe if 'mode' is
1185 'existing', else the format of the source
1186 (json-string, optional)
1187 - "sync": what parts of the disk image should be copied to the destination;
1188 possibilities include "full" for all the disk, "top" for only the sectors
1189 allocated in the topmost image, "incremental" for only the dirty sectors in
1190 the bitmap, or "none" to only replicate new I/O (MirrorSyncMode).
1191 - "bitmap": dirty bitmap name for sync==incremental. Must be present if sync
1192 is "incremental", must NOT be present otherwise.
1193 - "mode": whether and how QEMU should create a new image
1194 (NewImageMode, optional, default 'absolute-paths')
1195 - "speed": the maximum speed, in bytes per second (json-int, optional)
1196 - "on-source-error": the action to take on an error on the source, default
1197 'report'. 'stop' and 'enospc' can only be used
1198 if the block device supports io-status.
1199 (BlockdevOnError, optional)
1200 - "on-target-error": the action to take on an error on the target, default
1201 'report' (no limitations, since this applies to
1202 a different block device than device).
1203 (BlockdevOnError, optional)
1205 Example:
1206 -> { "execute": "drive-backup", "arguments": { "device": "drive0",
1207 "sync": "full",
1208 "target": "backup.img" } }
1209 <- { "return": {} }
1211 EQMP
1214 .name = "blockdev-backup",
1215 .args_type = "sync:s,device:B,target:B,speed:i?,"
1216 "on-source-error:s?,on-target-error:s?",
1217 .mhandler.cmd_new = qmp_marshal_blockdev_backup,
1220 SQMP
1221 blockdev-backup
1222 ---------------
1224 The device version of drive-backup: this command takes an existing named device
1225 as backup target.
1227 Arguments:
1229 - "device": the name of the device which should be copied.
1230 (json-string)
1231 - "target": the name of the backup target device. (json-string)
1232 - "sync": what parts of the disk image should be copied to the destination;
1233 possibilities include "full" for all the disk, "top" for only the
1234 sectors allocated in the topmost image, or "none" to only replicate
1235 new I/O (MirrorSyncMode).
1236 - "speed": the maximum speed, in bytes per second (json-int, optional)
1237 - "on-source-error": the action to take on an error on the source, default
1238 'report'. 'stop' and 'enospc' can only be used
1239 if the block device supports io-status.
1240 (BlockdevOnError, optional)
1241 - "on-target-error": the action to take on an error on the target, default
1242 'report' (no limitations, since this applies to
1243 a different block device than device).
1244 (BlockdevOnError, optional)
1246 Example:
1247 -> { "execute": "blockdev-backup", "arguments": { "device": "src-id",
1248 "sync": "full",
1249 "target": "tgt-id" } }
1250 <- { "return": {} }
1252 EQMP
1255 .name = "block-job-set-speed",
1256 .args_type = "device:B,speed:o",
1257 .mhandler.cmd_new = qmp_marshal_block_job_set_speed,
1261 .name = "block-job-cancel",
1262 .args_type = "device:B,force:b?",
1263 .mhandler.cmd_new = qmp_marshal_block_job_cancel,
1266 .name = "block-job-pause",
1267 .args_type = "device:B",
1268 .mhandler.cmd_new = qmp_marshal_block_job_pause,
1271 .name = "block-job-resume",
1272 .args_type = "device:B",
1273 .mhandler.cmd_new = qmp_marshal_block_job_resume,
1276 .name = "block-job-complete",
1277 .args_type = "device:B",
1278 .mhandler.cmd_new = qmp_marshal_block_job_complete,
1281 .name = "transaction",
1282 .args_type = "actions:q,properties:q?",
1283 .mhandler.cmd_new = qmp_marshal_transaction,
1286 SQMP
1287 transaction
1288 -----------
1290 Atomically operate on one or more block devices. Operations that are
1291 currently supported:
1293 - drive-backup
1294 - blockdev-backup
1295 - blockdev-snapshot-sync
1296 - blockdev-snapshot-internal-sync
1297 - abort
1298 - block-dirty-bitmap-add
1299 - block-dirty-bitmap-clear
1301 Refer to the qemu/qapi-schema.json file for minimum required QEMU
1302 versions for these operations. A list of dictionaries is accepted,
1303 that contains the actions to be performed. If there is any failure
1304 performing any of the operations, all operations for the group are
1305 abandoned.
1307 For external snapshots, the dictionary contains the device, the file to use for
1308 the new snapshot, and the format. The default format, if not specified, is
1309 qcow2.
1311 Each new snapshot defaults to being created by QEMU (wiping any
1312 contents if the file already exists), but it is also possible to reuse
1313 an externally-created file. In the latter case, you should ensure that
1314 the new image file has the same contents as the current one; QEMU cannot
1315 perform any meaningful check. Typically this is achieved by using the
1316 current image file as the backing file for the new image.
1318 On failure, the original disks pre-snapshot attempt will be used.
1320 For internal snapshots, the dictionary contains the device and the snapshot's
1321 name. If an internal snapshot matching name already exists, the request will
1322 be rejected. Only some image formats support it, for example, qcow2, rbd,
1323 and sheepdog.
1325 On failure, qemu will try delete the newly created internal snapshot in the
1326 transaction. When an I/O error occurs during deletion, the user needs to fix
1327 it later with qemu-img or other command.
1329 Arguments:
1331 actions array:
1332 - "type": the operation to perform (json-string). Possible
1333 values: "drive-backup", "blockdev-backup",
1334 "blockdev-snapshot-sync",
1335 "blockdev-snapshot-internal-sync",
1336 "abort", "block-dirty-bitmap-add",
1337 "block-dirty-bitmap-clear"
1338 - "data": a dictionary. The contents depend on the value
1339 of "type". When "type" is "blockdev-snapshot-sync":
1340 - "device": device name to snapshot (json-string)
1341 - "node-name": graph node name to snapshot (json-string)
1342 - "snapshot-file": name of new image file (json-string)
1343 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1344 - "format": format of new image (json-string, optional)
1345 - "mode": whether and how QEMU should create the snapshot file
1346 (NewImageMode, optional, default "absolute-paths")
1347 When "type" is "blockdev-snapshot-internal-sync":
1348 - "device": device name to snapshot (json-string)
1349 - "name": name of the new snapshot (json-string)
1351 Example:
1353 -> { "execute": "transaction",
1354 "arguments": { "actions": [
1355 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd0",
1356 "snapshot-file": "/some/place/my-image",
1357 "format": "qcow2" } },
1358 { "type": "blockdev-snapshot-sync", "data" : { "node-name": "myfile",
1359 "snapshot-file": "/some/place/my-image2",
1360 "snapshot-node-name": "node3432",
1361 "mode": "existing",
1362 "format": "qcow2" } },
1363 { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd1",
1364 "snapshot-file": "/some/place/my-image2",
1365 "mode": "existing",
1366 "format": "qcow2" } },
1367 { "type": "blockdev-snapshot-internal-sync", "data" : {
1368 "device": "ide-hd2",
1369 "name": "snapshot0" } } ] } }
1370 <- { "return": {} }
1372 EQMP
1375 .name = "block-dirty-bitmap-add",
1376 .args_type = "node:B,name:s,granularity:i?",
1377 .mhandler.cmd_new = qmp_marshal_block_dirty_bitmap_add,
1380 SQMP
1382 block-dirty-bitmap-add
1383 ----------------------
1384 Since 2.4
1386 Create a dirty bitmap with a name on the device, and start tracking the writes.
1388 Arguments:
1390 - "node": device/node on which to create dirty bitmap (json-string)
1391 - "name": name of the new dirty bitmap (json-string)
1392 - "granularity": granularity to track writes with (int, optional)
1394 Example:
1396 -> { "execute": "block-dirty-bitmap-add", "arguments": { "node": "drive0",
1397 "name": "bitmap0" } }
1398 <- { "return": {} }
1400 EQMP
1403 .name = "block-dirty-bitmap-remove",
1404 .args_type = "node:B,name:s",
1405 .mhandler.cmd_new = qmp_marshal_block_dirty_bitmap_remove,
1408 SQMP
1410 block-dirty-bitmap-remove
1411 -------------------------
1412 Since 2.4
1414 Stop write tracking and remove the dirty bitmap that was created with
1415 block-dirty-bitmap-add.
1417 Arguments:
1419 - "node": device/node on which to remove dirty bitmap (json-string)
1420 - "name": name of the dirty bitmap to remove (json-string)
1422 Example:
1424 -> { "execute": "block-dirty-bitmap-remove", "arguments": { "node": "drive0",
1425 "name": "bitmap0" } }
1426 <- { "return": {} }
1428 EQMP
1431 .name = "block-dirty-bitmap-clear",
1432 .args_type = "node:B,name:s",
1433 .mhandler.cmd_new = qmp_marshal_block_dirty_bitmap_clear,
1436 SQMP
1438 block-dirty-bitmap-clear
1439 ------------------------
1440 Since 2.4
1442 Reset the dirty bitmap associated with a node so that an incremental backup
1443 from this point in time forward will only backup clusters modified after this
1444 clear operation.
1446 Arguments:
1448 - "node": device/node on which to remove dirty bitmap (json-string)
1449 - "name": name of the dirty bitmap to remove (json-string)
1451 Example:
1453 -> { "execute": "block-dirty-bitmap-clear", "arguments": { "node": "drive0",
1454 "name": "bitmap0" } }
1455 <- { "return": {} }
1457 EQMP
1460 .name = "blockdev-snapshot-sync",
1461 .args_type = "device:s?,node-name:s?,snapshot-file:s,snapshot-node-name:s?,format:s?,mode:s?",
1462 .mhandler.cmd_new = qmp_marshal_blockdev_snapshot_sync,
1465 SQMP
1466 blockdev-snapshot-sync
1467 ----------------------
1469 Synchronous snapshot of a block device. snapshot-file specifies the
1470 target of the new image. If the file exists, or if it is a device, the
1471 snapshot will be created in the existing file/device. If does not
1472 exist, a new file will be created. format specifies the format of the
1473 snapshot image, default is qcow2.
1475 Arguments:
1477 - "device": device name to snapshot (json-string)
1478 - "node-name": graph node name to snapshot (json-string)
1479 - "snapshot-file": name of new image file (json-string)
1480 - "snapshot-node-name": graph node name of the new snapshot (json-string)
1481 - "mode": whether and how QEMU should create the snapshot file
1482 (NewImageMode, optional, default "absolute-paths")
1483 - "format": format of new image (json-string, optional)
1485 Example:
1487 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
1488 "snapshot-file":
1489 "/some/place/my-image",
1490 "format": "qcow2" } }
1491 <- { "return": {} }
1493 EQMP
1496 .name = "blockdev-snapshot",
1497 .args_type = "node:s,overlay:s",
1498 .mhandler.cmd_new = qmp_marshal_blockdev_snapshot,
1501 SQMP
1502 blockdev-snapshot
1503 -----------------
1504 Since 2.5
1506 Create a snapshot, by installing 'node' as the backing image of
1507 'overlay'. Additionally, if 'node' is associated with a block
1508 device, the block device changes to using 'overlay' as its new active
1509 image.
1511 Arguments:
1513 - "node": device that will have a snapshot created (json-string)
1514 - "overlay": device that will have 'node' as its backing image (json-string)
1516 Example:
1518 -> { "execute": "blockdev-add",
1519 "arguments": { "options": { "driver": "qcow2",
1520 "node-name": "node1534",
1521 "file": { "driver": "file",
1522 "filename": "hd1.qcow2" },
1523 "backing": "" } } }
1525 <- { "return": {} }
1527 -> { "execute": "blockdev-snapshot", "arguments": { "node": "ide-hd0",
1528 "overlay": "node1534" } }
1529 <- { "return": {} }
1531 EQMP
1534 .name = "blockdev-snapshot-internal-sync",
1535 .args_type = "device:B,name:s",
1536 .mhandler.cmd_new = qmp_marshal_blockdev_snapshot_internal_sync,
1539 SQMP
1540 blockdev-snapshot-internal-sync
1541 -------------------------------
1543 Synchronously take an internal snapshot of a block device when the format of
1544 image used supports it. If the name is an empty string, or a snapshot with
1545 name already exists, the operation will fail.
1547 Arguments:
1549 - "device": device name to snapshot (json-string)
1550 - "name": name of the new snapshot (json-string)
1552 Example:
1554 -> { "execute": "blockdev-snapshot-internal-sync",
1555 "arguments": { "device": "ide-hd0",
1556 "name": "snapshot0" }
1558 <- { "return": {} }
1560 EQMP
1563 .name = "blockdev-snapshot-delete-internal-sync",
1564 .args_type = "device:B,id:s?,name:s?",
1565 .mhandler.cmd_new =
1566 qmp_marshal_blockdev_snapshot_delete_internal_sync,
1569 SQMP
1570 blockdev-snapshot-delete-internal-sync
1571 --------------------------------------
1573 Synchronously delete an internal snapshot of a block device when the format of
1574 image used supports it. The snapshot is identified by name or id or both. One
1575 of name or id is required. If the snapshot is not found, the operation will
1576 fail.
1578 Arguments:
1580 - "device": device name (json-string)
1581 - "id": ID of the snapshot (json-string, optional)
1582 - "name": name of the snapshot (json-string, optional)
1584 Example:
1586 -> { "execute": "blockdev-snapshot-delete-internal-sync",
1587 "arguments": { "device": "ide-hd0",
1588 "name": "snapshot0" }
1590 <- { "return": {
1591 "id": "1",
1592 "name": "snapshot0",
1593 "vm-state-size": 0,
1594 "date-sec": 1000012,
1595 "date-nsec": 10,
1596 "vm-clock-sec": 100,
1597 "vm-clock-nsec": 20
1601 EQMP
1604 .name = "drive-mirror",
1605 .args_type = "sync:s,device:B,target:s,speed:i?,mode:s?,format:s?,"
1606 "node-name:s?,replaces:s?,"
1607 "on-source-error:s?,on-target-error:s?,"
1608 "unmap:b?,"
1609 "granularity:i?,buf-size:i?",
1610 .mhandler.cmd_new = qmp_marshal_drive_mirror,
1613 SQMP
1614 drive-mirror
1615 ------------
1617 Start mirroring a block device's writes to a new destination. target
1618 specifies the target of the new image. If the file exists, or if it is
1619 a device, it will be used as the new destination for writes. If it does not
1620 exist, a new file will be created. format specifies the format of the
1621 mirror image, default is to probe if mode='existing', else the format
1622 of the source.
1624 Arguments:
1626 - "device": device name to operate on (json-string)
1627 - "target": name of new image file (json-string)
1628 - "format": format of new image (json-string, optional)
1629 - "node-name": the name of the new block driver state in the node graph
1630 (json-string, optional)
1631 - "replaces": the block driver node name to replace when finished
1632 (json-string, optional)
1633 - "mode": how an image file should be created into the target
1634 file/device (NewImageMode, optional, default 'absolute-paths')
1635 - "speed": maximum speed of the streaming job, in bytes per second
1636 (json-int)
1637 - "granularity": granularity of the dirty bitmap, in bytes (json-int, optional)
1638 - "buf-size": maximum amount of data in flight from source to target, in bytes
1639 (json-int, default 10M)
1640 - "sync": what parts of the disk image should be copied to the destination;
1641 possibilities include "full" for all the disk, "top" for only the sectors
1642 allocated in the topmost image, or "none" to only replicate new I/O
1643 (MirrorSyncMode).
1644 - "on-source-error": the action to take on an error on the source
1645 (BlockdevOnError, default 'report')
1646 - "on-target-error": the action to take on an error on the target
1647 (BlockdevOnError, default 'report')
1648 - "unmap": whether the target sectors should be discarded where source has only
1649 zeroes. (json-bool, optional, default true)
1651 The default value of the granularity is the image cluster size clamped
1652 between 4096 and 65536, if the image format defines one. If the format
1653 does not define a cluster size, the default value of the granularity
1654 is 65536.
1657 Example:
1659 -> { "execute": "drive-mirror", "arguments": { "device": "ide-hd0",
1660 "target": "/some/place/my-image",
1661 "sync": "full",
1662 "format": "qcow2" } }
1663 <- { "return": {} }
1665 EQMP
1668 .name = "blockdev-mirror",
1669 .args_type = "sync:s,device:B,target:B,replaces:s?,speed:i?,"
1670 "on-source-error:s?,on-target-error:s?,"
1671 "granularity:i?,buf-size:i?",
1672 .mhandler.cmd_new = qmp_marshal_blockdev_mirror,
1675 SQMP
1676 blockdev-mirror
1677 ------------
1679 Start mirroring a block device's writes to another block device. target
1680 specifies the target of mirror operation.
1682 Arguments:
1684 - "device": device name to operate on (json-string)
1685 - "target": device name to mirror to (json-string)
1686 - "replaces": the block driver node name to replace when finished
1687 (json-string, optional)
1688 - "speed": maximum speed of the streaming job, in bytes per second
1689 (json-int)
1690 - "granularity": granularity of the dirty bitmap, in bytes (json-int, optional)
1691 - "buf_size": maximum amount of data in flight from source to target, in bytes
1692 (json-int, default 10M)
1693 - "sync": what parts of the disk image should be copied to the destination;
1694 possibilities include "full" for all the disk, "top" for only the sectors
1695 allocated in the topmost image, or "none" to only replicate new I/O
1696 (MirrorSyncMode).
1697 - "on-source-error": the action to take on an error on the source
1698 (BlockdevOnError, default 'report')
1699 - "on-target-error": the action to take on an error on the target
1700 (BlockdevOnError, default 'report')
1702 The default value of the granularity is the image cluster size clamped
1703 between 4096 and 65536, if the image format defines one. If the format
1704 does not define a cluster size, the default value of the granularity
1705 is 65536.
1707 Example:
1709 -> { "execute": "blockdev-mirror", "arguments": { "device": "ide-hd0",
1710 "target": "target0",
1711 "sync": "full" } }
1712 <- { "return": {} }
1714 EQMP
1716 .name = "change-backing-file",
1717 .args_type = "device:s,image-node-name:s,backing-file:s",
1718 .mhandler.cmd_new = qmp_marshal_change_backing_file,
1721 SQMP
1722 change-backing-file
1723 -------------------
1724 Since: 2.1
1726 Change the backing file in the image file metadata. This does not cause
1727 QEMU to reopen the image file to reparse the backing filename (it may,
1728 however, perform a reopen to change permissions from r/o -> r/w -> r/o,
1729 if needed). The new backing file string is written into the image file
1730 metadata, and the QEMU internal strings are updated.
1732 Arguments:
1734 - "image-node-name": The name of the block driver state node of the
1735 image to modify. The "device" is argument is used to
1736 verify "image-node-name" is in the chain described by
1737 "device".
1738 (json-string, optional)
1740 - "device": The name of the device.
1741 (json-string)
1743 - "backing-file": The string to write as the backing file. This string is
1744 not validated, so care should be taken when specifying
1745 the string or the image chain may not be able to be
1746 reopened again.
1747 (json-string)
1749 Returns: Nothing on success
1750 If "device" does not exist or cannot be determined, DeviceNotFound
1752 EQMP
1755 .name = "balloon",
1756 .args_type = "value:M",
1757 .mhandler.cmd_new = qmp_marshal_balloon,
1760 SQMP
1761 balloon
1762 -------
1764 Request VM to change its memory allocation (in bytes).
1766 Arguments:
1768 - "value": New memory allocation (json-int)
1770 Example:
1772 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1773 <- { "return": {} }
1775 EQMP
1778 .name = "set_link",
1779 .args_type = "name:s,up:b",
1780 .mhandler.cmd_new = qmp_marshal_set_link,
1783 SQMP
1784 set_link
1785 --------
1787 Change the link status of a network adapter.
1789 Arguments:
1791 - "name": network device name (json-string)
1792 - "up": status is up (json-bool)
1794 Example:
1796 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
1797 <- { "return": {} }
1799 EQMP
1802 .name = "getfd",
1803 .args_type = "fdname:s",
1804 .params = "getfd name",
1805 .help = "receive a file descriptor via SCM rights and assign it a name",
1806 .mhandler.cmd_new = qmp_marshal_getfd,
1809 SQMP
1810 getfd
1811 -----
1813 Receive a file descriptor via SCM rights and assign it a name.
1815 Arguments:
1817 - "fdname": file descriptor name (json-string)
1819 Example:
1821 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1822 <- { "return": {} }
1824 Notes:
1826 (1) If the name specified by the "fdname" argument already exists,
1827 the file descriptor assigned to it will be closed and replaced
1828 by the received file descriptor.
1829 (2) The 'closefd' command can be used to explicitly close the file
1830 descriptor when it is no longer needed.
1832 EQMP
1835 .name = "closefd",
1836 .args_type = "fdname:s",
1837 .params = "closefd name",
1838 .help = "close a file descriptor previously passed via SCM rights",
1839 .mhandler.cmd_new = qmp_marshal_closefd,
1842 SQMP
1843 closefd
1844 -------
1846 Close a file descriptor previously passed via SCM rights.
1848 Arguments:
1850 - "fdname": file descriptor name (json-string)
1852 Example:
1854 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1855 <- { "return": {} }
1857 EQMP
1860 .name = "add-fd",
1861 .args_type = "fdset-id:i?,opaque:s?",
1862 .params = "add-fd fdset-id opaque",
1863 .help = "Add a file descriptor, that was passed via SCM rights, to an fd set",
1864 .mhandler.cmd_new = qmp_marshal_add_fd,
1867 SQMP
1868 add-fd
1869 -------
1871 Add a file descriptor, that was passed via SCM rights, to an fd set.
1873 Arguments:
1875 - "fdset-id": The ID of the fd set to add the file descriptor to.
1876 (json-int, optional)
1877 - "opaque": A free-form string that can be used to describe the fd.
1878 (json-string, optional)
1880 Return a json-object with the following information:
1882 - "fdset-id": The ID of the fd set that the fd was added to. (json-int)
1883 - "fd": The file descriptor that was received via SCM rights and added to the
1884 fd set. (json-int)
1886 Example:
1888 -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1889 <- { "return": { "fdset-id": 1, "fd": 3 } }
1891 Notes:
1893 (1) The list of fd sets is shared by all monitor connections.
1894 (2) If "fdset-id" is not specified, a new fd set will be created.
1896 EQMP
1899 .name = "remove-fd",
1900 .args_type = "fdset-id:i,fd:i?",
1901 .params = "remove-fd fdset-id fd",
1902 .help = "Remove a file descriptor from an fd set",
1903 .mhandler.cmd_new = qmp_marshal_remove_fd,
1906 SQMP
1907 remove-fd
1908 ---------
1910 Remove a file descriptor from an fd set.
1912 Arguments:
1914 - "fdset-id": The ID of the fd set that the file descriptor belongs to.
1915 (json-int)
1916 - "fd": The file descriptor that is to be removed. (json-int, optional)
1918 Example:
1920 -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1921 <- { "return": {} }
1923 Notes:
1925 (1) The list of fd sets is shared by all monitor connections.
1926 (2) If "fd" is not specified, all file descriptors in "fdset-id" will be
1927 removed.
1929 EQMP
1932 .name = "query-fdsets",
1933 .args_type = "",
1934 .help = "Return information describing all fd sets",
1935 .mhandler.cmd_new = qmp_marshal_query_fdsets,
1938 SQMP
1939 query-fdsets
1940 -------------
1942 Return information describing all fd sets.
1944 Arguments: None
1946 Example:
1948 -> { "execute": "query-fdsets" }
1949 <- { "return": [
1951 "fds": [
1953 "fd": 30,
1954 "opaque": "rdonly:/path/to/file"
1957 "fd": 24,
1958 "opaque": "rdwr:/path/to/file"
1961 "fdset-id": 1
1964 "fds": [
1966 "fd": 28
1969 "fd": 29
1972 "fdset-id": 0
1977 Note: The list of fd sets is shared by all monitor connections.
1979 EQMP
1982 .name = "block_passwd",
1983 .args_type = "device:s?,node-name:s?,password:s",
1984 .mhandler.cmd_new = qmp_marshal_block_passwd,
1987 SQMP
1988 block_passwd
1989 ------------
1991 Set the password of encrypted block devices.
1993 Arguments:
1995 - "device": device name (json-string)
1996 - "node-name": name in the block driver state graph (json-string)
1997 - "password": password (json-string)
1999 Example:
2001 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
2002 "password": "12345" } }
2003 <- { "return": {} }
2005 EQMP
2008 .name = "block_set_io_throttle",
2009 .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?,bps_max_length:l?,bps_rd_max_length:l?,bps_wr_max_length:l?,iops_max_length:l?,iops_rd_max_length:l?,iops_wr_max_length:l?,iops_size:l?,group:s?",
2010 .mhandler.cmd_new = qmp_marshal_block_set_io_throttle,
2013 SQMP
2014 block_set_io_throttle
2015 ------------
2017 Change I/O throttle limits for a block drive.
2019 Arguments:
2021 - "device": device name (json-string)
2022 - "bps": total throughput limit in bytes per second (json-int)
2023 - "bps_rd": read throughput limit in bytes per second (json-int)
2024 - "bps_wr": write throughput limit in bytes per second (json-int)
2025 - "iops": total I/O operations per second (json-int)
2026 - "iops_rd": read I/O operations per second (json-int)
2027 - "iops_wr": write I/O operations per second (json-int)
2028 - "bps_max": total throughput limit during bursts, in bytes (json-int, optional)
2029 - "bps_rd_max": read throughput limit during bursts, in bytes (json-int, optional)
2030 - "bps_wr_max": write throughput limit during bursts, in bytes (json-int, optional)
2031 - "iops_max": total I/O operations per second during bursts (json-int, optional)
2032 - "iops_rd_max": read I/O operations per second during bursts (json-int, optional)
2033 - "iops_wr_max": write I/O operations per second during bursts (json-int, optional)
2034 - "bps_max_length": maximum length of the @bps_max burst period, in seconds (json-int, optional)
2035 - "bps_rd_max_length": maximum length of the @bps_rd_max burst period, in seconds (json-int, optional)
2036 - "bps_wr_max_length": maximum length of the @bps_wr_max burst period, in seconds (json-int, optional)
2037 - "iops_max_length": maximum length of the @iops_max burst period, in seconds (json-int, optional)
2038 - "iops_rd_max_length": maximum length of the @iops_rd_max burst period, in seconds (json-int, optional)
2039 - "iops_wr_max_length": maximum length of the @iops_wr_max burst period, in seconds (json-int, optional)
2040 - "iops_size": I/O size in bytes when limiting (json-int, optional)
2041 - "group": throttle group name (json-string, optional)
2043 Example:
2045 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
2046 "bps": 1000000,
2047 "bps_rd": 0,
2048 "bps_wr": 0,
2049 "iops": 0,
2050 "iops_rd": 0,
2051 "iops_wr": 0,
2052 "bps_max": 8000000,
2053 "bps_rd_max": 0,
2054 "bps_wr_max": 0,
2055 "iops_max": 0,
2056 "iops_rd_max": 0,
2057 "iops_wr_max": 0,
2058 "bps_max_length": 60,
2059 "iops_size": 0 } }
2060 <- { "return": {} }
2062 EQMP
2065 .name = "set_password",
2066 .args_type = "protocol:s,password:s,connected:s?",
2067 .mhandler.cmd_new = qmp_marshal_set_password,
2070 SQMP
2071 set_password
2072 ------------
2074 Set the password for vnc/spice protocols.
2076 Arguments:
2078 - "protocol": protocol name (json-string)
2079 - "password": password (json-string)
2080 - "connected": [ keep | disconnect | fail ] (json-string, optional)
2082 Example:
2084 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
2085 "password": "secret" } }
2086 <- { "return": {} }
2088 EQMP
2091 .name = "expire_password",
2092 .args_type = "protocol:s,time:s",
2093 .mhandler.cmd_new = qmp_marshal_expire_password,
2096 SQMP
2097 expire_password
2098 ---------------
2100 Set the password expire time for vnc/spice protocols.
2102 Arguments:
2104 - "protocol": protocol name (json-string)
2105 - "time": [ now | never | +secs | secs ] (json-string)
2107 Example:
2109 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
2110 "time": "+60" } }
2111 <- { "return": {} }
2113 EQMP
2116 .name = "add_client",
2117 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
2118 .mhandler.cmd_new = qmp_marshal_add_client,
2121 SQMP
2122 add_client
2123 ----------
2125 Add a graphics client
2127 Arguments:
2129 - "protocol": protocol name (json-string)
2130 - "fdname": file descriptor name (json-string)
2131 - "skipauth": whether to skip authentication (json-bool, optional)
2132 - "tls": whether to perform TLS (json-bool, optional)
2134 Example:
2136 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
2137 "fdname": "myclient" } }
2138 <- { "return": {} }
2140 EQMP
2142 .name = "qmp_capabilities",
2143 .args_type = "",
2144 .params = "",
2145 .help = "enable QMP capabilities",
2146 .mhandler.cmd_new = qmp_capabilities,
2149 SQMP
2150 qmp_capabilities
2151 ----------------
2153 Enable QMP capabilities.
2155 Arguments: None.
2157 Example:
2159 -> { "execute": "qmp_capabilities" }
2160 <- { "return": {} }
2162 Note: This command must be issued before issuing any other command.
2164 EQMP
2167 .name = "human-monitor-command",
2168 .args_type = "command-line:s,cpu-index:i?",
2169 .mhandler.cmd_new = qmp_marshal_human_monitor_command,
2172 SQMP
2173 human-monitor-command
2174 ---------------------
2176 Execute a Human Monitor command.
2178 Arguments:
2180 - command-line: the command name and its arguments, just like the
2181 Human Monitor's shell (json-string)
2182 - cpu-index: select the CPU number to be used by commands which access CPU
2183 data, like 'info registers'. The Monitor selects CPU 0 if this
2184 argument is not provided (json-int, optional)
2186 Example:
2188 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
2189 <- { "return": "kvm support: enabled\r\n" }
2191 Notes:
2193 (1) The Human Monitor is NOT an stable interface, this means that command
2194 names, arguments and responses can change or be removed at ANY time.
2195 Applications that rely on long term stability guarantees should NOT
2196 use this command
2198 (2) Limitations:
2200 o This command is stateless, this means that commands that depend
2201 on state information (such as getfd) might not work
2203 o Commands that prompt the user for data (eg. 'cont' when the block
2204 device is encrypted) don't currently work
2206 3. Query Commands
2207 =================
2209 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
2210 HXCOMM this! We will possibly move query commands definitions inside those
2211 HXCOMM sections, just like regular commands.
2213 EQMP
2215 SQMP
2216 query-version
2217 -------------
2219 Show QEMU version.
2221 Return a json-object with the following information:
2223 - "qemu": A json-object containing three integer values:
2224 - "major": QEMU's major version (json-int)
2225 - "minor": QEMU's minor version (json-int)
2226 - "micro": QEMU's micro version (json-int)
2227 - "package": package's version (json-string)
2229 Example:
2231 -> { "execute": "query-version" }
2232 <- {
2233 "return":{
2234 "qemu":{
2235 "major":0,
2236 "minor":11,
2237 "micro":5
2239 "package":""
2243 EQMP
2246 .name = "query-version",
2247 .args_type = "",
2248 .mhandler.cmd_new = qmp_marshal_query_version,
2251 SQMP
2252 query-commands
2253 --------------
2255 List QMP available commands.
2257 Each command is represented by a json-object, the returned value is a json-array
2258 of all commands.
2260 Each json-object contain:
2262 - "name": command's name (json-string)
2264 Example:
2266 -> { "execute": "query-commands" }
2267 <- {
2268 "return":[
2270 "name":"query-balloon"
2273 "name":"system_powerdown"
2278 Note: This example has been shortened as the real response is too long.
2280 EQMP
2283 .name = "query-commands",
2284 .args_type = "",
2285 .mhandler.cmd_new = qmp_marshal_query_commands,
2288 SQMP
2289 query-events
2290 --------------
2292 List QMP available events.
2294 Each event is represented by a json-object, the returned value is a json-array
2295 of all events.
2297 Each json-object contains:
2299 - "name": event's name (json-string)
2301 Example:
2303 -> { "execute": "query-events" }
2304 <- {
2305 "return":[
2307 "name":"SHUTDOWN"
2310 "name":"RESET"
2315 Note: This example has been shortened as the real response is too long.
2317 EQMP
2320 .name = "query-events",
2321 .args_type = "",
2322 .mhandler.cmd_new = qmp_marshal_query_events,
2325 SQMP
2326 query-qmp-schema
2327 ----------------
2329 Return the QMP wire schema. The returned value is a json-array of
2330 named schema entities. Entities are commands, events and various
2331 types. See docs/qapi-code-gen.txt for information on their structure
2332 and intended use.
2334 EQMP
2337 .name = "query-qmp-schema",
2338 .args_type = "",
2339 .mhandler.cmd_new = qmp_query_qmp_schema,
2342 SQMP
2343 query-chardev
2344 -------------
2346 Each device is represented by a json-object. The returned value is a json-array
2347 of all devices.
2349 Each json-object contain the following:
2351 - "label": device's label (json-string)
2352 - "filename": device's file (json-string)
2353 - "frontend-open": open/closed state of the frontend device attached to this
2354 backend (json-bool)
2356 Example:
2358 -> { "execute": "query-chardev" }
2359 <- {
2360 "return": [
2362 "label": "charchannel0",
2363 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.agent,server",
2364 "frontend-open": false
2367 "label": "charmonitor",
2368 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.monitor,server",
2369 "frontend-open": true
2372 "label": "charserial0",
2373 "filename": "pty:/dev/pts/2",
2374 "frontend-open": true
2379 EQMP
2382 .name = "query-chardev",
2383 .args_type = "",
2384 .mhandler.cmd_new = qmp_marshal_query_chardev,
2387 SQMP
2388 query-chardev-backends
2389 -------------
2391 List available character device backends.
2393 Each backend is represented by a json-object, the returned value is a json-array
2394 of all backends.
2396 Each json-object contains:
2398 - "name": backend name (json-string)
2400 Example:
2402 -> { "execute": "query-chardev-backends" }
2403 <- {
2404 "return":[
2406 "name":"udp"
2409 "name":"tcp"
2412 "name":"unix"
2415 "name":"spiceport"
2420 EQMP
2423 .name = "query-chardev-backends",
2424 .args_type = "",
2425 .mhandler.cmd_new = qmp_marshal_query_chardev_backends,
2428 SQMP
2429 query-block
2430 -----------
2432 Show the block devices.
2434 Each block device information is stored in a json-object and the returned value
2435 is a json-array of all devices.
2437 Each json-object contain the following:
2439 - "device": device name (json-string)
2440 - "type": device type (json-string)
2441 - deprecated, retained for backward compatibility
2442 - Possible values: "unknown"
2443 - "removable": true if the device is removable, false otherwise (json-bool)
2444 - "locked": true if the device is locked, false otherwise (json-bool)
2445 - "tray_open": only present if removable, true if the device has a tray,
2446 and it is open (json-bool)
2447 - "inserted": only present if the device is inserted, it is a json-object
2448 containing the following:
2449 - "file": device file name (json-string)
2450 - "ro": true if read-only, false otherwise (json-bool)
2451 - "drv": driver format name (json-string)
2452 - Possible values: "blkdebug", "bochs", "cloop", "dmg",
2453 "file", "file", "ftp", "ftps", "host_cdrom",
2454 "host_device", "http", "https",
2455 "nbd", "parallels", "qcow", "qcow2", "raw",
2456 "tftp", "vdi", "vmdk", "vpc", "vvfat"
2457 - "backing_file": backing file name (json-string, optional)
2458 - "backing_file_depth": number of files in the backing file chain (json-int)
2459 - "encrypted": true if encrypted, false otherwise (json-bool)
2460 - "bps": limit total bytes per second (json-int)
2461 - "bps_rd": limit read bytes per second (json-int)
2462 - "bps_wr": limit write bytes per second (json-int)
2463 - "iops": limit total I/O operations per second (json-int)
2464 - "iops_rd": limit read operations per second (json-int)
2465 - "iops_wr": limit write operations per second (json-int)
2466 - "bps_max": total max in bytes (json-int)
2467 - "bps_rd_max": read max in bytes (json-int)
2468 - "bps_wr_max": write max in bytes (json-int)
2469 - "iops_max": total I/O operations max (json-int)
2470 - "iops_rd_max": read I/O operations max (json-int)
2471 - "iops_wr_max": write I/O operations max (json-int)
2472 - "iops_size": I/O size when limiting by iops (json-int)
2473 - "detect_zeroes": detect and optimize zero writing (json-string)
2474 - Possible values: "off", "on", "unmap"
2475 - "write_threshold": write offset threshold in bytes, a event will be
2476 emitted if crossed. Zero if disabled (json-int)
2477 - "image": the detail of the image, it is a json-object containing
2478 the following:
2479 - "filename": image file name (json-string)
2480 - "format": image format (json-string)
2481 - "virtual-size": image capacity in bytes (json-int)
2482 - "dirty-flag": true if image is not cleanly closed, not present
2483 means clean (json-bool, optional)
2484 - "actual-size": actual size on disk in bytes of the image, not
2485 present when image does not support thin
2486 provision (json-int, optional)
2487 - "cluster-size": size of a cluster in bytes, not present if image
2488 format does not support it (json-int, optional)
2489 - "encrypted": true if the image is encrypted, not present means
2490 false or the image format does not support
2491 encryption (json-bool, optional)
2492 - "backing_file": backing file name, not present means no backing
2493 file is used or the image format does not
2494 support backing file chain
2495 (json-string, optional)
2496 - "full-backing-filename": full path of the backing file, not
2497 present if it equals backing_file or no
2498 backing file is used
2499 (json-string, optional)
2500 - "backing-filename-format": the format of the backing file, not
2501 present means unknown or no backing
2502 file (json-string, optional)
2503 - "snapshots": the internal snapshot info, it is an optional list
2504 of json-object containing the following:
2505 - "id": unique snapshot id (json-string)
2506 - "name": snapshot name (json-string)
2507 - "vm-state-size": size of the VM state in bytes (json-int)
2508 - "date-sec": UTC date of the snapshot in seconds (json-int)
2509 - "date-nsec": fractional part in nanoseconds to be used with
2510 date-sec (json-int)
2511 - "vm-clock-sec": VM clock relative to boot in seconds
2512 (json-int)
2513 - "vm-clock-nsec": fractional part in nanoseconds to be used
2514 with vm-clock-sec (json-int)
2515 - "backing-image": the detail of the backing image, it is an
2516 optional json-object only present when a
2517 backing image present for this image
2519 - "io-status": I/O operation status, only present if the device supports it
2520 and the VM is configured to stop on errors. It's always reset
2521 to "ok" when the "cont" command is issued (json_string, optional)
2522 - Possible values: "ok", "failed", "nospace"
2524 Example:
2526 -> { "execute": "query-block" }
2527 <- {
2528 "return":[
2530 "io-status": "ok",
2531 "device":"ide0-hd0",
2532 "locked":false,
2533 "removable":false,
2534 "inserted":{
2535 "ro":false,
2536 "drv":"qcow2",
2537 "encrypted":false,
2538 "file":"disks/test.qcow2",
2539 "backing_file_depth":1,
2540 "bps":1000000,
2541 "bps_rd":0,
2542 "bps_wr":0,
2543 "iops":1000000,
2544 "iops_rd":0,
2545 "iops_wr":0,
2546 "bps_max": 8000000,
2547 "bps_rd_max": 0,
2548 "bps_wr_max": 0,
2549 "iops_max": 0,
2550 "iops_rd_max": 0,
2551 "iops_wr_max": 0,
2552 "iops_size": 0,
2553 "detect_zeroes": "on",
2554 "write_threshold": 0,
2555 "image":{
2556 "filename":"disks/test.qcow2",
2557 "format":"qcow2",
2558 "virtual-size":2048000,
2559 "backing_file":"base.qcow2",
2560 "full-backing-filename":"disks/base.qcow2",
2561 "backing-filename-format":"qcow2",
2562 "snapshots":[
2564 "id": "1",
2565 "name": "snapshot1",
2566 "vm-state-size": 0,
2567 "date-sec": 10000200,
2568 "date-nsec": 12,
2569 "vm-clock-sec": 206,
2570 "vm-clock-nsec": 30
2573 "backing-image":{
2574 "filename":"disks/base.qcow2",
2575 "format":"qcow2",
2576 "virtual-size":2048000
2580 "type":"unknown"
2583 "io-status": "ok",
2584 "device":"ide1-cd0",
2585 "locked":false,
2586 "removable":true,
2587 "type":"unknown"
2590 "device":"floppy0",
2591 "locked":false,
2592 "removable":true,
2593 "type":"unknown"
2596 "device":"sd0",
2597 "locked":false,
2598 "removable":true,
2599 "type":"unknown"
2604 EQMP
2607 .name = "query-block",
2608 .args_type = "",
2609 .mhandler.cmd_new = qmp_marshal_query_block,
2612 SQMP
2613 query-blockstats
2614 ----------------
2616 Show block device statistics.
2618 Each device statistic information is stored in a json-object and the returned
2619 value is a json-array of all devices.
2621 Each json-object contain the following:
2623 - "device": device name (json-string)
2624 - "stats": A json-object with the statistics information, it contains:
2625 - "rd_bytes": bytes read (json-int)
2626 - "wr_bytes": bytes written (json-int)
2627 - "rd_operations": read operations (json-int)
2628 - "wr_operations": write operations (json-int)
2629 - "flush_operations": cache flush operations (json-int)
2630 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
2631 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
2632 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
2633 - "wr_highest_offset": The offset after the greatest byte written to the
2634 BlockDriverState since it has been opened (json-int)
2635 - "rd_merged": number of read requests that have been merged into
2636 another request (json-int)
2637 - "wr_merged": number of write requests that have been merged into
2638 another request (json-int)
2639 - "idle_time_ns": time since the last I/O operation, in
2640 nanoseconds. If the field is absent it means
2641 that there haven't been any operations yet
2642 (json-int, optional)
2643 - "failed_rd_operations": number of failed read operations
2644 (json-int)
2645 - "failed_wr_operations": number of failed write operations
2646 (json-int)
2647 - "failed_flush_operations": number of failed flush operations
2648 (json-int)
2649 - "invalid_rd_operations": number of invalid read operations
2650 (json-int)
2651 - "invalid_wr_operations": number of invalid write operations
2652 (json-int)
2653 - "invalid_flush_operations": number of invalid flush operations
2654 (json-int)
2655 - "account_invalid": whether invalid operations are included in
2656 the last access statistics (json-bool)
2657 - "account_failed": whether failed operations are included in the
2658 latency and last access statistics
2659 (json-bool)
2660 - "timed_stats": A json-array containing statistics collected in
2661 specific intervals, with the following members:
2662 - "interval_length": interval used for calculating the
2663 statistics, in seconds (json-int)
2664 - "min_rd_latency_ns": minimum latency of read operations in
2665 the defined interval, in nanoseconds
2666 (json-int)
2667 - "min_wr_latency_ns": minimum latency of write operations in
2668 the defined interval, in nanoseconds
2669 (json-int)
2670 - "min_flush_latency_ns": minimum latency of flush operations
2671 in the defined interval, in
2672 nanoseconds (json-int)
2673 - "max_rd_latency_ns": maximum latency of read operations in
2674 the defined interval, in nanoseconds
2675 (json-int)
2676 - "max_wr_latency_ns": maximum latency of write operations in
2677 the defined interval, in nanoseconds
2678 (json-int)
2679 - "max_flush_latency_ns": maximum latency of flush operations
2680 in the defined interval, in
2681 nanoseconds (json-int)
2682 - "avg_rd_latency_ns": average latency of read operations in
2683 the defined interval, in nanoseconds
2684 (json-int)
2685 - "avg_wr_latency_ns": average latency of write operations in
2686 the defined interval, in nanoseconds
2687 (json-int)
2688 - "avg_flush_latency_ns": average latency of flush operations
2689 in the defined interval, in
2690 nanoseconds (json-int)
2691 - "avg_rd_queue_depth": average number of pending read
2692 operations in the defined interval
2693 (json-number)
2694 - "avg_wr_queue_depth": average number of pending write
2695 operations in the defined interval
2696 (json-number).
2697 - "parent": Contains recursively the statistics of the underlying
2698 protocol (e.g. the host file for a qcow2 image). If there is
2699 no underlying protocol, this field is omitted
2700 (json-object, optional)
2702 Example:
2704 -> { "execute": "query-blockstats" }
2705 <- {
2706 "return":[
2708 "device":"ide0-hd0",
2709 "parent":{
2710 "stats":{
2711 "wr_highest_offset":3686448128,
2712 "wr_bytes":9786368,
2713 "wr_operations":751,
2714 "rd_bytes":122567168,
2715 "rd_operations":36772
2716 "wr_total_times_ns":313253456
2717 "rd_total_times_ns":3465673657
2718 "flush_total_times_ns":49653
2719 "flush_operations":61,
2720 "rd_merged":0,
2721 "wr_merged":0,
2722 "idle_time_ns":2953431879,
2723 "account_invalid":true,
2724 "account_failed":false
2727 "stats":{
2728 "wr_highest_offset":2821110784,
2729 "wr_bytes":9786368,
2730 "wr_operations":692,
2731 "rd_bytes":122739200,
2732 "rd_operations":36604
2733 "flush_operations":51,
2734 "wr_total_times_ns":313253456
2735 "rd_total_times_ns":3465673657
2736 "flush_total_times_ns":49653,
2737 "rd_merged":0,
2738 "wr_merged":0,
2739 "idle_time_ns":2953431879,
2740 "account_invalid":true,
2741 "account_failed":false
2745 "device":"ide1-cd0",
2746 "stats":{
2747 "wr_highest_offset":0,
2748 "wr_bytes":0,
2749 "wr_operations":0,
2750 "rd_bytes":0,
2751 "rd_operations":0
2752 "flush_operations":0,
2753 "wr_total_times_ns":0
2754 "rd_total_times_ns":0
2755 "flush_total_times_ns":0,
2756 "rd_merged":0,
2757 "wr_merged":0,
2758 "account_invalid":false,
2759 "account_failed":false
2763 "device":"floppy0",
2764 "stats":{
2765 "wr_highest_offset":0,
2766 "wr_bytes":0,
2767 "wr_operations":0,
2768 "rd_bytes":0,
2769 "rd_operations":0
2770 "flush_operations":0,
2771 "wr_total_times_ns":0
2772 "rd_total_times_ns":0
2773 "flush_total_times_ns":0,
2774 "rd_merged":0,
2775 "wr_merged":0,
2776 "account_invalid":false,
2777 "account_failed":false
2781 "device":"sd0",
2782 "stats":{
2783 "wr_highest_offset":0,
2784 "wr_bytes":0,
2785 "wr_operations":0,
2786 "rd_bytes":0,
2787 "rd_operations":0
2788 "flush_operations":0,
2789 "wr_total_times_ns":0
2790 "rd_total_times_ns":0
2791 "flush_total_times_ns":0,
2792 "rd_merged":0,
2793 "wr_merged":0,
2794 "account_invalid":false,
2795 "account_failed":false
2801 EQMP
2804 .name = "query-blockstats",
2805 .args_type = "query-nodes:b?",
2806 .mhandler.cmd_new = qmp_marshal_query_blockstats,
2809 SQMP
2810 query-cpus
2811 ----------
2813 Show CPU information.
2815 Return a json-array. Each CPU is represented by a json-object, which contains:
2817 - "CPU": CPU index (json-int)
2818 - "current": true if this is the current CPU, false otherwise (json-bool)
2819 - "halted": true if the cpu is halted, false otherwise (json-bool)
2820 - "qom_path": path to the CPU object in the QOM tree (json-str)
2821 - "arch": architecture of the cpu, which determines what additional
2822 keys will be present (json-str)
2823 - Current program counter. The key's name depends on the architecture:
2824 "pc": i386/x86_64 (json-int)
2825 "nip": PPC (json-int)
2826 "pc" and "npc": sparc (json-int)
2827 "PC": mips (json-int)
2828 - "thread_id": ID of the underlying host thread (json-int)
2830 Example:
2832 -> { "execute": "query-cpus" }
2833 <- {
2834 "return":[
2836 "CPU":0,
2837 "current":true,
2838 "halted":false,
2839 "qom_path":"/machine/unattached/device[0]",
2840 "arch":"x86",
2841 "pc":3227107138,
2842 "thread_id":3134
2845 "CPU":1,
2846 "current":false,
2847 "halted":true,
2848 "qom_path":"/machine/unattached/device[2]",
2849 "arch":"x86",
2850 "pc":7108165,
2851 "thread_id":3135
2856 EQMP
2859 .name = "query-cpus",
2860 .args_type = "",
2861 .mhandler.cmd_new = qmp_marshal_query_cpus,
2864 SQMP
2865 query-iothreads
2866 ---------------
2868 Returns a list of information about each iothread.
2870 Note this list excludes the QEMU main loop thread, which is not declared
2871 using the -object iothread command-line option. It is always the main thread
2872 of the process.
2874 Return a json-array. Each iothread is represented by a json-object, which contains:
2876 - "id": name of iothread (json-str)
2877 - "thread-id": ID of the underlying host thread (json-int)
2879 Example:
2881 -> { "execute": "query-iothreads" }
2882 <- {
2883 "return":[
2885 "id":"iothread0",
2886 "thread-id":3134
2889 "id":"iothread1",
2890 "thread-id":3135
2895 EQMP
2898 .name = "query-iothreads",
2899 .args_type = "",
2900 .mhandler.cmd_new = qmp_marshal_query_iothreads,
2903 SQMP
2904 query-pci
2905 ---------
2907 PCI buses and devices information.
2909 The returned value is a json-array of all buses. Each bus is represented by
2910 a json-object, which has a key with a json-array of all PCI devices attached
2911 to it. Each device is represented by a json-object.
2913 The bus json-object contains the following:
2915 - "bus": bus number (json-int)
2916 - "devices": a json-array of json-objects, each json-object represents a
2917 PCI device
2919 The PCI device json-object contains the following:
2921 - "bus": identical to the parent's bus number (json-int)
2922 - "slot": slot number (json-int)
2923 - "function": function number (json-int)
2924 - "class_info": a json-object containing:
2925 - "desc": device class description (json-string, optional)
2926 - "class": device class number (json-int)
2927 - "id": a json-object containing:
2928 - "device": device ID (json-int)
2929 - "vendor": vendor ID (json-int)
2930 - "irq": device's IRQ if assigned (json-int, optional)
2931 - "qdev_id": qdev id string (json-string)
2932 - "pci_bridge": It's a json-object, only present if this device is a
2933 PCI bridge, contains:
2934 - "bus": bus number (json-int)
2935 - "secondary": secondary bus number (json-int)
2936 - "subordinate": subordinate bus number (json-int)
2937 - "io_range": I/O memory range information, a json-object with the
2938 following members:
2939 - "base": base address, in bytes (json-int)
2940 - "limit": limit address, in bytes (json-int)
2941 - "memory_range": memory range information, a json-object with the
2942 following members:
2943 - "base": base address, in bytes (json-int)
2944 - "limit": limit address, in bytes (json-int)
2945 - "prefetchable_range": Prefetchable memory range information, a
2946 json-object with the following members:
2947 - "base": base address, in bytes (json-int)
2948 - "limit": limit address, in bytes (json-int)
2949 - "devices": a json-array of PCI devices if there's any attached, each
2950 each element is represented by a json-object, which contains
2951 the same members of the 'PCI device json-object' described
2952 above (optional)
2953 - "regions": a json-array of json-objects, each json-object represents a
2954 memory region of this device
2956 The memory range json-object contains the following:
2958 - "base": base memory address (json-int)
2959 - "limit": limit value (json-int)
2961 The region json-object can be an I/O region or a memory region, an I/O region
2962 json-object contains the following:
2964 - "type": "io" (json-string, fixed)
2965 - "bar": BAR number (json-int)
2966 - "address": memory address (json-int)
2967 - "size": memory size (json-int)
2969 A memory region json-object contains the following:
2971 - "type": "memory" (json-string, fixed)
2972 - "bar": BAR number (json-int)
2973 - "address": memory address (json-int)
2974 - "size": memory size (json-int)
2975 - "mem_type_64": true or false (json-bool)
2976 - "prefetch": true or false (json-bool)
2978 Example:
2980 -> { "execute": "query-pci" }
2981 <- {
2982 "return":[
2984 "bus":0,
2985 "devices":[
2987 "bus":0,
2988 "qdev_id":"",
2989 "slot":0,
2990 "class_info":{
2991 "class":1536,
2992 "desc":"Host bridge"
2994 "id":{
2995 "device":32902,
2996 "vendor":4663
2998 "function":0,
2999 "regions":[
3004 "bus":0,
3005 "qdev_id":"",
3006 "slot":1,
3007 "class_info":{
3008 "class":1537,
3009 "desc":"ISA bridge"
3011 "id":{
3012 "device":32902,
3013 "vendor":28672
3015 "function":0,
3016 "regions":[
3021 "bus":0,
3022 "qdev_id":"",
3023 "slot":1,
3024 "class_info":{
3025 "class":257,
3026 "desc":"IDE controller"
3028 "id":{
3029 "device":32902,
3030 "vendor":28688
3032 "function":1,
3033 "regions":[
3035 "bar":4,
3036 "size":16,
3037 "address":49152,
3038 "type":"io"
3043 "bus":0,
3044 "qdev_id":"",
3045 "slot":2,
3046 "class_info":{
3047 "class":768,
3048 "desc":"VGA controller"
3050 "id":{
3051 "device":4115,
3052 "vendor":184
3054 "function":0,
3055 "regions":[
3057 "prefetch":true,
3058 "mem_type_64":false,
3059 "bar":0,
3060 "size":33554432,
3061 "address":4026531840,
3062 "type":"memory"
3065 "prefetch":false,
3066 "mem_type_64":false,
3067 "bar":1,
3068 "size":4096,
3069 "address":4060086272,
3070 "type":"memory"
3073 "prefetch":false,
3074 "mem_type_64":false,
3075 "bar":6,
3076 "size":65536,
3077 "address":-1,
3078 "type":"memory"
3083 "bus":0,
3084 "qdev_id":"",
3085 "irq":11,
3086 "slot":4,
3087 "class_info":{
3088 "class":1280,
3089 "desc":"RAM controller"
3091 "id":{
3092 "device":6900,
3093 "vendor":4098
3095 "function":0,
3096 "regions":[
3098 "bar":0,
3099 "size":32,
3100 "address":49280,
3101 "type":"io"
3110 Note: This example has been shortened as the real response is too long.
3112 EQMP
3115 .name = "query-pci",
3116 .args_type = "",
3117 .mhandler.cmd_new = qmp_marshal_query_pci,
3120 SQMP
3121 query-kvm
3122 ---------
3124 Show KVM information.
3126 Return a json-object with the following information:
3128 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
3129 - "present": true if QEMU has KVM support, false otherwise (json-bool)
3131 Example:
3133 -> { "execute": "query-kvm" }
3134 <- { "return": { "enabled": true, "present": true } }
3136 EQMP
3139 .name = "query-kvm",
3140 .args_type = "",
3141 .mhandler.cmd_new = qmp_marshal_query_kvm,
3144 SQMP
3145 query-status
3146 ------------
3148 Return a json-object with the following information:
3150 - "running": true if the VM is running, or false if it is paused (json-bool)
3151 - "singlestep": true if the VM is in single step mode,
3152 false otherwise (json-bool)
3153 - "status": one of the following values (json-string)
3154 "debug" - QEMU is running on a debugger
3155 "inmigrate" - guest is paused waiting for an incoming migration
3156 "internal-error" - An internal error that prevents further guest
3157 execution has occurred
3158 "io-error" - the last IOP has failed and the device is configured
3159 to pause on I/O errors
3160 "paused" - guest has been paused via the 'stop' command
3161 "postmigrate" - guest is paused following a successful 'migrate'
3162 "prelaunch" - QEMU was started with -S and guest has not started
3163 "finish-migrate" - guest is paused to finish the migration process
3164 "restore-vm" - guest is paused to restore VM state
3165 "running" - guest is actively running
3166 "save-vm" - guest is paused to save the VM state
3167 "shutdown" - guest is shut down (and -no-shutdown is in use)
3168 "watchdog" - the watchdog action is configured to pause and
3169 has been triggered
3171 Example:
3173 -> { "execute": "query-status" }
3174 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
3176 EQMP
3179 .name = "query-status",
3180 .args_type = "",
3181 .mhandler.cmd_new = qmp_marshal_query_status,
3184 SQMP
3185 query-mice
3186 ----------
3188 Show VM mice information.
3190 Each mouse is represented by a json-object, the returned value is a json-array
3191 of all mice.
3193 The mouse json-object contains the following:
3195 - "name": mouse's name (json-string)
3196 - "index": mouse's index (json-int)
3197 - "current": true if this mouse is receiving events, false otherwise (json-bool)
3198 - "absolute": true if the mouse generates absolute input events (json-bool)
3200 Example:
3202 -> { "execute": "query-mice" }
3203 <- {
3204 "return":[
3206 "name":"QEMU Microsoft Mouse",
3207 "index":0,
3208 "current":false,
3209 "absolute":false
3212 "name":"QEMU PS/2 Mouse",
3213 "index":1,
3214 "current":true,
3215 "absolute":true
3220 EQMP
3223 .name = "query-mice",
3224 .args_type = "",
3225 .mhandler.cmd_new = qmp_marshal_query_mice,
3228 SQMP
3229 query-vnc
3230 ---------
3232 Show VNC server information.
3234 Return a json-object with server information. Connected clients are returned
3235 as a json-array of json-objects.
3237 The main json-object contains the following:
3239 - "enabled": true or false (json-bool)
3240 - "host": server's IP address (json-string)
3241 - "family": address family (json-string)
3242 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3243 - "service": server's port number (json-string)
3244 - "auth": authentication method (json-string)
3245 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
3246 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
3247 "vencrypt+plain", "vencrypt+tls+none",
3248 "vencrypt+tls+plain", "vencrypt+tls+sasl",
3249 "vencrypt+tls+vnc", "vencrypt+x509+none",
3250 "vencrypt+x509+plain", "vencrypt+x509+sasl",
3251 "vencrypt+x509+vnc", "vnc"
3252 - "clients": a json-array of all connected clients
3254 Clients are described by a json-object, each one contain the following:
3256 - "host": client's IP address (json-string)
3257 - "family": address family (json-string)
3258 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3259 - "service": client's port number (json-string)
3260 - "x509_dname": TLS dname (json-string, optional)
3261 - "sasl_username": SASL username (json-string, optional)
3263 Example:
3265 -> { "execute": "query-vnc" }
3266 <- {
3267 "return":{
3268 "enabled":true,
3269 "host":"0.0.0.0",
3270 "service":"50402",
3271 "auth":"vnc",
3272 "family":"ipv4",
3273 "clients":[
3275 "host":"127.0.0.1",
3276 "service":"50401",
3277 "family":"ipv4"
3283 EQMP
3286 .name = "query-vnc",
3287 .args_type = "",
3288 .mhandler.cmd_new = qmp_marshal_query_vnc,
3291 .name = "query-vnc-servers",
3292 .args_type = "",
3293 .mhandler.cmd_new = qmp_marshal_query_vnc_servers,
3296 SQMP
3297 query-spice
3298 -----------
3300 Show SPICE server information.
3302 Return a json-object with server information. Connected clients are returned
3303 as a json-array of json-objects.
3305 The main json-object contains the following:
3307 - "enabled": true or false (json-bool)
3308 - "host": server's IP address (json-string)
3309 - "port": server's port number (json-int, optional)
3310 - "tls-port": server's port number (json-int, optional)
3311 - "auth": authentication method (json-string)
3312 - Possible values: "none", "spice"
3313 - "channels": a json-array of all active channels clients
3315 Channels are described by a json-object, each one contain the following:
3317 - "host": client's IP address (json-string)
3318 - "family": address family (json-string)
3319 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3320 - "port": client's port number (json-string)
3321 - "connection-id": spice connection id. All channels with the same id
3322 belong to the same spice session (json-int)
3323 - "channel-type": channel type. "1" is the main control channel, filter for
3324 this one if you want track spice sessions only (json-int)
3325 - "channel-id": channel id. Usually "0", might be different needed when
3326 multiple channels of the same type exist, such as multiple
3327 display channels in a multihead setup (json-int)
3328 - "tls": whether the channel is encrypted (json-bool)
3330 Example:
3332 -> { "execute": "query-spice" }
3333 <- {
3334 "return": {
3335 "enabled": true,
3336 "auth": "spice",
3337 "port": 5920,
3338 "tls-port": 5921,
3339 "host": "0.0.0.0",
3340 "channels": [
3342 "port": "54924",
3343 "family": "ipv4",
3344 "channel-type": 1,
3345 "connection-id": 1804289383,
3346 "host": "127.0.0.1",
3347 "channel-id": 0,
3348 "tls": true
3351 "port": "36710",
3352 "family": "ipv4",
3353 "channel-type": 4,
3354 "connection-id": 1804289383,
3355 "host": "127.0.0.1",
3356 "channel-id": 0,
3357 "tls": false
3359 [ ... more channels follow ... ]
3364 EQMP
3366 #if defined(CONFIG_SPICE)
3368 .name = "query-spice",
3369 .args_type = "",
3370 .mhandler.cmd_new = qmp_marshal_query_spice,
3372 #endif
3374 SQMP
3375 query-name
3376 ----------
3378 Show VM name.
3380 Return a json-object with the following information:
3382 - "name": VM's name (json-string, optional)
3384 Example:
3386 -> { "execute": "query-name" }
3387 <- { "return": { "name": "qemu-name" } }
3389 EQMP
3392 .name = "query-name",
3393 .args_type = "",
3394 .mhandler.cmd_new = qmp_marshal_query_name,
3397 SQMP
3398 query-uuid
3399 ----------
3401 Show VM UUID.
3403 Return a json-object with the following information:
3405 - "UUID": Universally Unique Identifier (json-string)
3407 Example:
3409 -> { "execute": "query-uuid" }
3410 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
3412 EQMP
3415 .name = "query-uuid",
3416 .args_type = "",
3417 .mhandler.cmd_new = qmp_marshal_query_uuid,
3420 SQMP
3421 query-command-line-options
3422 --------------------------
3424 Show command line option schema.
3426 Return a json-array of command line option schema for all options (or for
3427 the given option), returning an error if the given option doesn't exist.
3429 Each array entry contains the following:
3431 - "option": option name (json-string)
3432 - "parameters": a json-array describes all parameters of the option:
3433 - "name": parameter name (json-string)
3434 - "type": parameter type (one of 'string', 'boolean', 'number',
3435 or 'size')
3436 - "help": human readable description of the parameter
3437 (json-string, optional)
3438 - "default": default value string for the parameter
3439 (json-string, optional)
3441 Example:
3443 -> { "execute": "query-command-line-options", "arguments": { "option": "option-rom" } }
3444 <- { "return": [
3446 "parameters": [
3448 "name": "romfile",
3449 "type": "string"
3452 "name": "bootindex",
3453 "type": "number"
3456 "option": "option-rom"
3461 EQMP
3464 .name = "query-command-line-options",
3465 .args_type = "option:s?",
3466 .mhandler.cmd_new = qmp_marshal_query_command_line_options,
3469 SQMP
3470 query-migrate
3471 -------------
3473 Migration status.
3475 Return a json-object. If migration is active there will be another json-object
3476 with RAM migration status and if block migration is active another one with
3477 block migration status.
3479 The main json-object contains the following:
3481 - "status": migration status (json-string)
3482 - Possible values: "setup", "active", "completed", "failed", "cancelled"
3483 - "total-time": total amount of ms since migration started. If
3484 migration has ended, it returns the total migration
3485 time (json-int)
3486 - "setup-time" amount of setup time in milliseconds _before_ the
3487 iterations begin but _after_ the QMP command is issued.
3488 This is designed to provide an accounting of any activities
3489 (such as RDMA pinning) which may be expensive, but do not
3490 actually occur during the iterative migration rounds
3491 themselves. (json-int)
3492 - "downtime": only present when migration has finished correctly
3493 total amount in ms for downtime that happened (json-int)
3494 - "expected-downtime": only present while migration is active
3495 total amount in ms for downtime that was calculated on
3496 the last bitmap round (json-int)
3497 - "ram": only present if "status" is "active", it is a json-object with the
3498 following RAM information:
3499 - "transferred": amount transferred in bytes (json-int)
3500 - "remaining": amount remaining to transfer in bytes (json-int)
3501 - "total": total amount of memory in bytes (json-int)
3502 - "duplicate": number of pages filled entirely with the same
3503 byte (json-int)
3504 These are sent over the wire much more efficiently.
3505 - "skipped": number of skipped zero pages (json-int)
3506 - "normal" : number of whole pages transferred. I.e. they
3507 were not sent as duplicate or xbzrle pages (json-int)
3508 - "normal-bytes" : number of bytes transferred in whole
3509 pages. This is just normal pages times size of one page,
3510 but this way upper levels don't need to care about page
3511 size (json-int)
3512 - "dirty-sync-count": times that dirty ram was synchronized (json-int)
3513 - "disk": only present if "status" is "active" and it is a block migration,
3514 it is a json-object with the following disk information:
3515 - "transferred": amount transferred in bytes (json-int)
3516 - "remaining": amount remaining to transfer in bytes json-int)
3517 - "total": total disk size in bytes (json-int)
3518 - "xbzrle-cache": only present if XBZRLE is active.
3519 It is a json-object with the following XBZRLE information:
3520 - "cache-size": XBZRLE cache size in bytes
3521 - "bytes": number of bytes transferred for XBZRLE compressed pages
3522 - "pages": number of XBZRLE compressed pages
3523 - "cache-miss": number of XBRZRLE page cache misses
3524 - "cache-miss-rate": rate of XBRZRLE page cache misses
3525 - "overflow": number of times XBZRLE overflows. This means
3526 that the XBZRLE encoding was bigger than just sent the
3527 whole page, and then we sent the whole page instead (as as
3528 normal page).
3530 Examples:
3532 1. Before the first migration
3534 -> { "execute": "query-migrate" }
3535 <- { "return": {} }
3537 2. Migration is done and has succeeded
3539 -> { "execute": "query-migrate" }
3540 <- { "return": {
3541 "status": "completed",
3542 "ram":{
3543 "transferred":123,
3544 "remaining":123,
3545 "total":246,
3546 "total-time":12345,
3547 "setup-time":12345,
3548 "downtime":12345,
3549 "duplicate":123,
3550 "normal":123,
3551 "normal-bytes":123456,
3552 "dirty-sync-count":15
3557 3. Migration is done and has failed
3559 -> { "execute": "query-migrate" }
3560 <- { "return": { "status": "failed" } }
3562 4. Migration is being performed and is not a block migration:
3564 -> { "execute": "query-migrate" }
3565 <- {
3566 "return":{
3567 "status":"active",
3568 "ram":{
3569 "transferred":123,
3570 "remaining":123,
3571 "total":246,
3572 "total-time":12345,
3573 "setup-time":12345,
3574 "expected-downtime":12345,
3575 "duplicate":123,
3576 "normal":123,
3577 "normal-bytes":123456,
3578 "dirty-sync-count":15
3583 5. Migration is being performed and is a block migration:
3585 -> { "execute": "query-migrate" }
3586 <- {
3587 "return":{
3588 "status":"active",
3589 "ram":{
3590 "total":1057024,
3591 "remaining":1053304,
3592 "transferred":3720,
3593 "total-time":12345,
3594 "setup-time":12345,
3595 "expected-downtime":12345,
3596 "duplicate":123,
3597 "normal":123,
3598 "normal-bytes":123456,
3599 "dirty-sync-count":15
3601 "disk":{
3602 "total":20971520,
3603 "remaining":20880384,
3604 "transferred":91136
3609 6. Migration is being performed and XBZRLE is active:
3611 -> { "execute": "query-migrate" }
3612 <- {
3613 "return":{
3614 "status":"active",
3615 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
3616 "ram":{
3617 "total":1057024,
3618 "remaining":1053304,
3619 "transferred":3720,
3620 "total-time":12345,
3621 "setup-time":12345,
3622 "expected-downtime":12345,
3623 "duplicate":10,
3624 "normal":3333,
3625 "normal-bytes":3412992,
3626 "dirty-sync-count":15
3628 "xbzrle-cache":{
3629 "cache-size":67108864,
3630 "bytes":20971520,
3631 "pages":2444343,
3632 "cache-miss":2244,
3633 "cache-miss-rate":0.123,
3634 "overflow":34434
3639 EQMP
3642 .name = "query-migrate",
3643 .args_type = "",
3644 .mhandler.cmd_new = qmp_marshal_query_migrate,
3647 SQMP
3648 migrate-set-capabilities
3649 ------------------------
3651 Enable/Disable migration capabilities
3653 - "xbzrle": XBZRLE support
3654 - "rdma-pin-all": pin all pages when using RDMA during migration
3655 - "auto-converge": throttle down guest to help convergence of migration
3656 - "zero-blocks": compress zero blocks during block migration
3657 - "compress": use multiple compression threads to accelerate live migration
3658 - "events": generate events for each migration state change
3659 - "x-postcopy-ram": postcopy mode for live migration
3661 Arguments:
3663 Example:
3665 -> { "execute": "migrate-set-capabilities" , "arguments":
3666 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
3668 EQMP
3671 .name = "migrate-set-capabilities",
3672 .args_type = "capabilities:q",
3673 .params = "capability:s,state:b",
3674 .mhandler.cmd_new = qmp_marshal_migrate_set_capabilities,
3676 SQMP
3677 query-migrate-capabilities
3678 --------------------------
3680 Query current migration capabilities
3682 - "capabilities": migration capabilities state
3683 - "xbzrle" : XBZRLE state (json-bool)
3684 - "rdma-pin-all" : RDMA Pin Page state (json-bool)
3685 - "auto-converge" : Auto Converge state (json-bool)
3686 - "zero-blocks" : Zero Blocks state (json-bool)
3687 - "compress": Multiple compression threads state (json-bool)
3688 - "events": Migration state change event state (json-bool)
3689 - "x-postcopy-ram": postcopy ram state (json-bool)
3691 Arguments:
3693 Example:
3695 -> { "execute": "query-migrate-capabilities" }
3696 <- {"return": [
3697 {"state": false, "capability": "xbzrle"},
3698 {"state": false, "capability": "rdma-pin-all"},
3699 {"state": false, "capability": "auto-converge"},
3700 {"state": false, "capability": "zero-blocks"},
3701 {"state": false, "capability": "compress"},
3702 {"state": true, "capability": "events"},
3703 {"state": false, "capability": "x-postcopy-ram"}
3706 EQMP
3709 .name = "query-migrate-capabilities",
3710 .args_type = "",
3711 .mhandler.cmd_new = qmp_marshal_query_migrate_capabilities,
3714 SQMP
3715 migrate-set-parameters
3716 ----------------------
3718 Set migration parameters
3720 - "compress-level": set compression level during migration (json-int)
3721 - "compress-threads": set compression thread count for migration (json-int)
3722 - "decompress-threads": set decompression thread count for migration (json-int)
3723 - "x-cpu-throttle-initial": set initial percentage of time guest cpus are
3724 throttled for auto-converge (json-int)
3725 - "x-cpu-throttle-increment": set throttle increasing percentage for
3726 auto-converge (json-int)
3728 Arguments:
3730 Example:
3732 -> { "execute": "migrate-set-parameters" , "arguments":
3733 { "compress-level": 1 } }
3735 EQMP
3738 .name = "migrate-set-parameters",
3739 .args_type =
3740 "compress-level:i?,compress-threads:i?,decompress-threads:i?,x-cpu-throttle-initial:i?,x-cpu-throttle-increment:i?",
3741 .mhandler.cmd_new = qmp_marshal_migrate_set_parameters,
3743 SQMP
3744 query-migrate-parameters
3745 ------------------------
3747 Query current migration parameters
3749 - "parameters": migration parameters value
3750 - "compress-level" : compression level value (json-int)
3751 - "compress-threads" : compression thread count value (json-int)
3752 - "decompress-threads" : decompression thread count value (json-int)
3753 - "x-cpu-throttle-initial" : initial percentage of time guest cpus are
3754 throttled (json-int)
3755 - "x-cpu-throttle-increment" : throttle increasing percentage for
3756 auto-converge (json-int)
3758 Arguments:
3760 Example:
3762 -> { "execute": "query-migrate-parameters" }
3763 <- {
3764 "return": {
3765 "decompress-threads": 2,
3766 "x-cpu-throttle-increment": 10,
3767 "compress-threads": 8,
3768 "compress-level": 1,
3769 "x-cpu-throttle-initial": 20
3773 EQMP
3776 .name = "query-migrate-parameters",
3777 .args_type = "",
3778 .mhandler.cmd_new = qmp_marshal_query_migrate_parameters,
3781 SQMP
3782 query-balloon
3783 -------------
3785 Show balloon information.
3787 Make an asynchronous request for balloon info. When the request completes a
3788 json-object will be returned containing the following data:
3790 - "actual": current balloon value in bytes (json-int)
3792 Example:
3794 -> { "execute": "query-balloon" }
3795 <- {
3796 "return":{
3797 "actual":1073741824,
3801 EQMP
3804 .name = "query-balloon",
3805 .args_type = "",
3806 .mhandler.cmd_new = qmp_marshal_query_balloon,
3810 .name = "query-block-jobs",
3811 .args_type = "",
3812 .mhandler.cmd_new = qmp_marshal_query_block_jobs,
3816 .name = "qom-list",
3817 .args_type = "path:s",
3818 .mhandler.cmd_new = qmp_marshal_qom_list,
3822 .name = "qom-set",
3823 .args_type = "path:s,property:s,value:q",
3824 .mhandler.cmd_new = qmp_marshal_qom_set,
3828 .name = "qom-get",
3829 .args_type = "path:s,property:s",
3830 .mhandler.cmd_new = qmp_marshal_qom_get,
3834 .name = "nbd-server-start",
3835 .args_type = "addr:q,tls-creds:s?",
3836 .mhandler.cmd_new = qmp_marshal_nbd_server_start,
3839 .name = "nbd-server-add",
3840 .args_type = "device:B,writable:b?",
3841 .mhandler.cmd_new = qmp_marshal_nbd_server_add,
3844 .name = "nbd-server-stop",
3845 .args_type = "",
3846 .mhandler.cmd_new = qmp_marshal_nbd_server_stop,
3850 .name = "change-vnc-password",
3851 .args_type = "password:s",
3852 .mhandler.cmd_new = qmp_marshal_change_vnc_password,
3855 .name = "qom-list-types",
3856 .args_type = "implements:s?,abstract:b?",
3857 .mhandler.cmd_new = qmp_marshal_qom_list_types,
3861 .name = "device-list-properties",
3862 .args_type = "typename:s",
3863 .mhandler.cmd_new = qmp_marshal_device_list_properties,
3867 .name = "query-machines",
3868 .args_type = "",
3869 .mhandler.cmd_new = qmp_marshal_query_machines,
3873 .name = "query-cpu-definitions",
3874 .args_type = "",
3875 .mhandler.cmd_new = qmp_marshal_query_cpu_definitions,
3879 .name = "query-target",
3880 .args_type = "",
3881 .mhandler.cmd_new = qmp_marshal_query_target,
3885 .name = "query-tpm",
3886 .args_type = "",
3887 .mhandler.cmd_new = qmp_marshal_query_tpm,
3890 SQMP
3891 query-tpm
3892 ---------
3894 Return information about the TPM device.
3896 Arguments: None
3898 Example:
3900 -> { "execute": "query-tpm" }
3901 <- { "return":
3903 { "model": "tpm-tis",
3904 "options":
3905 { "type": "passthrough",
3906 "data":
3907 { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
3908 "path": "/dev/tpm0"
3911 "id": "tpm0"
3916 EQMP
3919 .name = "query-tpm-models",
3920 .args_type = "",
3921 .mhandler.cmd_new = qmp_marshal_query_tpm_models,
3924 SQMP
3925 query-tpm-models
3926 ----------------
3928 Return a list of supported TPM models.
3930 Arguments: None
3932 Example:
3934 -> { "execute": "query-tpm-models" }
3935 <- { "return": [ "tpm-tis" ] }
3937 EQMP
3940 .name = "query-tpm-types",
3941 .args_type = "",
3942 .mhandler.cmd_new = qmp_marshal_query_tpm_types,
3945 SQMP
3946 query-tpm-types
3947 ---------------
3949 Return a list of supported TPM types.
3951 Arguments: None
3953 Example:
3955 -> { "execute": "query-tpm-types" }
3956 <- { "return": [ "passthrough" ] }
3958 EQMP
3961 .name = "chardev-add",
3962 .args_type = "id:s,backend:q",
3963 .mhandler.cmd_new = qmp_marshal_chardev_add,
3966 SQMP
3967 chardev-add
3968 ----------------
3970 Add a chardev.
3972 Arguments:
3974 - "id": the chardev's ID, must be unique (json-string)
3975 - "backend": chardev backend type + parameters
3977 Examples:
3979 -> { "execute" : "chardev-add",
3980 "arguments" : { "id" : "foo",
3981 "backend" : { "type" : "null", "data" : {} } } }
3982 <- { "return": {} }
3984 -> { "execute" : "chardev-add",
3985 "arguments" : { "id" : "bar",
3986 "backend" : { "type" : "file",
3987 "data" : { "out" : "/tmp/bar.log" } } } }
3988 <- { "return": {} }
3990 -> { "execute" : "chardev-add",
3991 "arguments" : { "id" : "baz",
3992 "backend" : { "type" : "pty", "data" : {} } } }
3993 <- { "return": { "pty" : "/dev/pty/42" } }
3995 EQMP
3998 .name = "chardev-remove",
3999 .args_type = "id:s",
4000 .mhandler.cmd_new = qmp_marshal_chardev_remove,
4004 SQMP
4005 chardev-remove
4006 --------------
4008 Remove a chardev.
4010 Arguments:
4012 - "id": the chardev's ID, must exist and not be in use (json-string)
4014 Example:
4016 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }
4017 <- { "return": {} }
4019 EQMP
4021 .name = "query-rx-filter",
4022 .args_type = "name:s?",
4023 .mhandler.cmd_new = qmp_marshal_query_rx_filter,
4026 SQMP
4027 query-rx-filter
4028 ---------------
4030 Show rx-filter information.
4032 Returns a json-array of rx-filter information for all NICs (or for the
4033 given NIC), returning an error if the given NIC doesn't exist, or
4034 given NIC doesn't support rx-filter querying, or given net client
4035 isn't a NIC.
4037 The query will clear the event notification flag of each NIC, then qemu
4038 will start to emit event to QMP monitor.
4040 Each array entry contains the following:
4042 - "name": net client name (json-string)
4043 - "promiscuous": promiscuous mode is enabled (json-bool)
4044 - "multicast": multicast receive state (one of 'normal', 'none', 'all')
4045 - "unicast": unicast receive state (one of 'normal', 'none', 'all')
4046 - "vlan": vlan receive state (one of 'normal', 'none', 'all') (Since 2.0)
4047 - "broadcast-allowed": allow to receive broadcast (json-bool)
4048 - "multicast-overflow": multicast table is overflowed (json-bool)
4049 - "unicast-overflow": unicast table is overflowed (json-bool)
4050 - "main-mac": main macaddr string (json-string)
4051 - "vlan-table": a json-array of active vlan id
4052 - "unicast-table": a json-array of unicast macaddr string
4053 - "multicast-table": a json-array of multicast macaddr string
4055 Example:
4057 -> { "execute": "query-rx-filter", "arguments": { "name": "vnet0" } }
4058 <- { "return": [
4060 "promiscuous": true,
4061 "name": "vnet0",
4062 "main-mac": "52:54:00:12:34:56",
4063 "unicast": "normal",
4064 "vlan": "normal",
4065 "vlan-table": [
4069 "unicast-table": [
4071 "multicast": "normal",
4072 "multicast-overflow": false,
4073 "unicast-overflow": false,
4074 "multicast-table": [
4075 "01:00:5e:00:00:01",
4076 "33:33:00:00:00:01",
4077 "33:33:ff:12:34:56"
4079 "broadcast-allowed": false
4084 EQMP
4087 .name = "blockdev-add",
4088 .args_type = "options:q",
4089 .mhandler.cmd_new = qmp_marshal_blockdev_add,
4092 SQMP
4093 blockdev-add
4094 ------------
4096 Add a block device.
4098 This command is still a work in progress. It doesn't support all
4099 block drivers among other things. Stay away from it unless you want
4100 to help with its development.
4102 Arguments:
4104 - "options": block driver options
4106 Example (1):
4108 -> { "execute": "blockdev-add",
4109 "arguments": { "options" : { "driver": "qcow2",
4110 "file": { "driver": "file",
4111 "filename": "test.qcow2" } } } }
4112 <- { "return": {} }
4114 Example (2):
4116 -> { "execute": "blockdev-add",
4117 "arguments": {
4118 "options": {
4119 "driver": "qcow2",
4120 "id": "my_disk",
4121 "discard": "unmap",
4122 "cache": {
4123 "direct": true,
4124 "writeback": true
4126 "file": {
4127 "driver": "file",
4128 "filename": "/tmp/test.qcow2"
4130 "backing": {
4131 "driver": "raw",
4132 "file": {
4133 "driver": "file",
4134 "filename": "/dev/fdset/4"
4141 <- { "return": {} }
4143 EQMP
4146 .name = "x-blockdev-del",
4147 .args_type = "id:s?,node-name:s?",
4148 .mhandler.cmd_new = qmp_marshal_x_blockdev_del,
4151 SQMP
4152 x-blockdev-del
4153 ------------
4154 Since 2.5
4156 Deletes a block device thas has been added using blockdev-add.
4157 The selected device can be either a block backend or a graph node.
4159 In the former case the backend will be destroyed, along with its
4160 inserted medium if there's any. The command will fail if the backend
4161 or its medium are in use.
4163 In the latter case the node will be destroyed. The command will fail
4164 if the node is attached to a block backend or is otherwise being
4165 used.
4167 One of "id" or "node-name" must be specified, but not both.
4169 This command is still a work in progress and is considered
4170 experimental. Stay away from it unless you want to help with its
4171 development.
4173 Arguments:
4175 - "id": Name of the block backend device to delete (json-string, optional)
4176 - "node-name": Name of the graph node to delete (json-string, optional)
4178 Example:
4180 -> { "execute": "blockdev-add",
4181 "arguments": {
4182 "options": {
4183 "driver": "qcow2",
4184 "id": "drive0",
4185 "file": {
4186 "driver": "file",
4187 "filename": "test.qcow2"
4193 <- { "return": {} }
4195 -> { "execute": "x-blockdev-del",
4196 "arguments": { "id": "drive0" }
4198 <- { "return": {} }
4200 EQMP
4203 .name = "blockdev-open-tray",
4204 .args_type = "device:s,force:b?",
4205 .mhandler.cmd_new = qmp_marshal_blockdev_open_tray,
4208 SQMP
4209 blockdev-open-tray
4210 ------------------
4212 Opens a block device's tray. If there is a block driver state tree inserted as a
4213 medium, it will become inaccessible to the guest (but it will remain associated
4214 to the block device, so closing the tray will make it accessible again).
4216 If the tray was already open before, this will be a no-op.
4218 Once the tray opens, a DEVICE_TRAY_MOVED event is emitted. There are cases in
4219 which no such event will be generated, these include:
4220 - if the guest has locked the tray, @force is false and the guest does not
4221 respond to the eject request
4222 - if the BlockBackend denoted by @device does not have a guest device attached
4223 to it
4224 - if the guest device does not have an actual tray and is empty, for instance
4225 for floppy disk drives
4227 Arguments:
4229 - "device": block device name (json-string)
4230 - "force": if false (the default), an eject request will be sent to the guest if
4231 it has locked the tray (and the tray will not be opened immediately);
4232 if true, the tray will be opened regardless of whether it is locked
4233 (json-bool, optional)
4235 Example:
4237 -> { "execute": "blockdev-open-tray",
4238 "arguments": { "device": "ide1-cd0" } }
4240 <- { "timestamp": { "seconds": 1418751016,
4241 "microseconds": 716996 },
4242 "event": "DEVICE_TRAY_MOVED",
4243 "data": { "device": "ide1-cd0",
4244 "tray-open": true } }
4246 <- { "return": {} }
4248 EQMP
4251 .name = "blockdev-close-tray",
4252 .args_type = "device:s",
4253 .mhandler.cmd_new = qmp_marshal_blockdev_close_tray,
4256 SQMP
4257 blockdev-close-tray
4258 -------------------
4260 Closes a block device's tray. If there is a block driver state tree associated
4261 with the block device (which is currently ejected), that tree will be loaded as
4262 the medium.
4264 If the tray was already closed before, this will be a no-op.
4266 Arguments:
4268 - "device": block device name (json-string)
4270 Example:
4272 -> { "execute": "blockdev-close-tray",
4273 "arguments": { "device": "ide1-cd0" } }
4275 <- { "timestamp": { "seconds": 1418751345,
4276 "microseconds": 272147 },
4277 "event": "DEVICE_TRAY_MOVED",
4278 "data": { "device": "ide1-cd0",
4279 "tray-open": false } }
4281 <- { "return": {} }
4283 EQMP
4286 .name = "x-blockdev-remove-medium",
4287 .args_type = "device:s",
4288 .mhandler.cmd_new = qmp_marshal_x_blockdev_remove_medium,
4291 SQMP
4292 x-blockdev-remove-medium
4293 ------------------------
4295 Removes a medium (a block driver state tree) from a block device. That block
4296 device's tray must currently be open (unless there is no attached guest device).
4298 If the tray is open and there is no medium inserted, this will be a no-op.
4300 This command is still a work in progress and is considered experimental.
4301 Stay away from it unless you want to help with its development.
4303 Arguments:
4305 - "device": block device name (json-string)
4307 Example:
4309 -> { "execute": "x-blockdev-remove-medium",
4310 "arguments": { "device": "ide1-cd0" } }
4312 <- { "error": { "class": "GenericError",
4313 "desc": "Tray of device 'ide1-cd0' is not open" } }
4315 -> { "execute": "blockdev-open-tray",
4316 "arguments": { "device": "ide1-cd0" } }
4318 <- { "timestamp": { "seconds": 1418751627,
4319 "microseconds": 549958 },
4320 "event": "DEVICE_TRAY_MOVED",
4321 "data": { "device": "ide1-cd0",
4322 "tray-open": true } }
4324 <- { "return": {} }
4326 -> { "execute": "x-blockdev-remove-medium",
4327 "arguments": { "device": "ide1-cd0" } }
4329 <- { "return": {} }
4331 EQMP
4334 .name = "x-blockdev-insert-medium",
4335 .args_type = "device:s,node-name:s",
4336 .mhandler.cmd_new = qmp_marshal_x_blockdev_insert_medium,
4339 SQMP
4340 x-blockdev-insert-medium
4341 ------------------------
4343 Inserts a medium (a block driver state tree) into a block device. That block
4344 device's tray must currently be open (unless there is no attached guest device)
4345 and there must be no medium inserted already.
4347 This command is still a work in progress and is considered experimental.
4348 Stay away from it unless you want to help with its development.
4350 Arguments:
4352 - "device": block device name (json-string)
4353 - "node-name": root node of the BDS tree to insert into the block device
4355 Example:
4357 -> { "execute": "blockdev-add",
4358 "arguments": { "options": { "node-name": "node0",
4359 "driver": "raw",
4360 "file": { "driver": "file",
4361 "filename": "fedora.iso" } } } }
4363 <- { "return": {} }
4365 -> { "execute": "x-blockdev-insert-medium",
4366 "arguments": { "device": "ide1-cd0",
4367 "node-name": "node0" } }
4369 <- { "return": {} }
4371 EQMP
4374 .name = "query-named-block-nodes",
4375 .args_type = "",
4376 .mhandler.cmd_new = qmp_marshal_query_named_block_nodes,
4379 SQMP
4380 @query-named-block-nodes
4381 ------------------------
4383 Return a list of BlockDeviceInfo for all the named block driver nodes
4385 Example:
4387 -> { "execute": "query-named-block-nodes" }
4388 <- { "return": [ { "ro":false,
4389 "drv":"qcow2",
4390 "encrypted":false,
4391 "file":"disks/test.qcow2",
4392 "node-name": "my-node",
4393 "backing_file_depth":1,
4394 "bps":1000000,
4395 "bps_rd":0,
4396 "bps_wr":0,
4397 "iops":1000000,
4398 "iops_rd":0,
4399 "iops_wr":0,
4400 "bps_max": 8000000,
4401 "bps_rd_max": 0,
4402 "bps_wr_max": 0,
4403 "iops_max": 0,
4404 "iops_rd_max": 0,
4405 "iops_wr_max": 0,
4406 "iops_size": 0,
4407 "write_threshold": 0,
4408 "image":{
4409 "filename":"disks/test.qcow2",
4410 "format":"qcow2",
4411 "virtual-size":2048000,
4412 "backing_file":"base.qcow2",
4413 "full-backing-filename":"disks/base.qcow2",
4414 "backing-filename-format":"qcow2",
4415 "snapshots":[
4417 "id": "1",
4418 "name": "snapshot1",
4419 "vm-state-size": 0,
4420 "date-sec": 10000200,
4421 "date-nsec": 12,
4422 "vm-clock-sec": 206,
4423 "vm-clock-nsec": 30
4426 "backing-image":{
4427 "filename":"disks/base.qcow2",
4428 "format":"qcow2",
4429 "virtual-size":2048000
4431 } } ] }
4433 EQMP
4436 .name = "blockdev-change-medium",
4437 .args_type = "device:B,filename:F,format:s?,read-only-mode:s?",
4438 .mhandler.cmd_new = qmp_marshal_blockdev_change_medium,
4441 SQMP
4442 blockdev-change-medium
4443 ----------------------
4445 Changes the medium inserted into a block device by ejecting the current medium
4446 and loading a new image file which is inserted as the new medium.
4448 Arguments:
4450 - "device": device name (json-string)
4451 - "filename": filename of the new image (json-string)
4452 - "format": format of the new image (json-string, optional)
4453 - "read-only-mode": new read-only mode (json-string, optional)
4454 - Possible values: "retain" (default), "read-only", "read-write"
4456 Examples:
4458 1. Change a removable medium
4460 -> { "execute": "blockdev-change-medium",
4461 "arguments": { "device": "ide1-cd0",
4462 "filename": "/srv/images/Fedora-12-x86_64-DVD.iso",
4463 "format": "raw" } }
4464 <- { "return": {} }
4466 2. Load a read-only medium into a writable drive
4468 -> { "execute": "blockdev-change-medium",
4469 "arguments": { "device": "isa-fd0",
4470 "filename": "/srv/images/ro.img",
4471 "format": "raw",
4472 "read-only-mode": "retain" } }
4474 <- { "error":
4475 { "class": "GenericError",
4476 "desc": "Could not open '/srv/images/ro.img': Permission denied" } }
4478 -> { "execute": "blockdev-change-medium",
4479 "arguments": { "device": "isa-fd0",
4480 "filename": "/srv/images/ro.img",
4481 "format": "raw",
4482 "read-only-mode": "read-only" } }
4484 <- { "return": {} }
4486 EQMP
4489 .name = "query-memdev",
4490 .args_type = "",
4491 .mhandler.cmd_new = qmp_marshal_query_memdev,
4494 SQMP
4495 query-memdev
4496 ------------
4498 Show memory devices information.
4501 Example (1):
4503 -> { "execute": "query-memdev" }
4504 <- { "return": [
4506 "size": 536870912,
4507 "merge": false,
4508 "dump": true,
4509 "prealloc": false,
4510 "host-nodes": [0, 1],
4511 "policy": "bind"
4514 "size": 536870912,
4515 "merge": false,
4516 "dump": true,
4517 "prealloc": true,
4518 "host-nodes": [2, 3],
4519 "policy": "preferred"
4524 EQMP
4527 .name = "query-memory-devices",
4528 .args_type = "",
4529 .mhandler.cmd_new = qmp_marshal_query_memory_devices,
4532 SQMP
4533 @query-memory-devices
4534 --------------------
4536 Return a list of memory devices.
4538 Example:
4539 -> { "execute": "query-memory-devices" }
4540 <- { "return": [ { "data":
4541 { "addr": 5368709120,
4542 "hotpluggable": true,
4543 "hotplugged": true,
4544 "id": "d1",
4545 "memdev": "/objects/memX",
4546 "node": 0,
4547 "size": 1073741824,
4548 "slot": 0},
4549 "type": "dimm"
4550 } ] }
4551 EQMP
4554 .name = "query-acpi-ospm-status",
4555 .args_type = "",
4556 .mhandler.cmd_new = qmp_marshal_query_acpi_ospm_status,
4559 SQMP
4560 @query-acpi-ospm-status
4561 --------------------
4563 Return list of ACPIOSTInfo for devices that support status reporting
4564 via ACPI _OST method.
4566 Example:
4567 -> { "execute": "query-acpi-ospm-status" }
4568 <- { "return": [ { "device": "d1", "slot": "0", "slot-type": "DIMM", "source": 1, "status": 0},
4569 { "slot": "1", "slot-type": "DIMM", "source": 0, "status": 0},
4570 { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
4571 { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
4573 EQMP
4575 #if defined TARGET_I386
4577 .name = "rtc-reset-reinjection",
4578 .args_type = "",
4579 .mhandler.cmd_new = qmp_marshal_rtc_reset_reinjection,
4581 #endif
4583 SQMP
4584 rtc-reset-reinjection
4585 ---------------------
4587 Reset the RTC interrupt reinjection backlog.
4589 Arguments: None.
4591 Example:
4593 -> { "execute": "rtc-reset-reinjection" }
4594 <- { "return": {} }
4595 EQMP
4598 .name = "trace-event-get-state",
4599 .args_type = "name:s",
4600 .mhandler.cmd_new = qmp_marshal_trace_event_get_state,
4603 SQMP
4604 trace-event-get-state
4605 ---------------------
4607 Query the state of events.
4609 Example:
4611 -> { "execute": "trace-event-get-state", "arguments": { "name": "qemu_memalign" } }
4612 <- { "return": [ { "name": "qemu_memalign", "state": "disabled" } ] }
4613 EQMP
4616 .name = "trace-event-set-state",
4617 .args_type = "name:s,enable:b,ignore-unavailable:b?",
4618 .mhandler.cmd_new = qmp_marshal_trace_event_set_state,
4621 SQMP
4622 trace-event-set-state
4623 ---------------------
4625 Set the state of events.
4627 Example:
4629 -> { "execute": "trace-event-set-state", "arguments": { "name": "qemu_memalign", "enable": "true" } }
4630 <- { "return": {} }
4631 EQMP
4634 .name = "x-input-send-event",
4635 .args_type = "console:i?,events:q",
4636 .mhandler.cmd_new = qmp_marshal_x_input_send_event,
4639 SQMP
4640 @x-input-send-event
4641 -----------------
4643 Send input event to guest.
4645 Arguments:
4647 - "console": console index. (json-int, optional)
4648 - "events": list of input events.
4650 The consoles are visible in the qom tree, under
4651 /backend/console[$index]. They have a device link and head property, so
4652 it is possible to map which console belongs to which device and display.
4654 Note: this command is experimental, and not a stable API.
4656 Example (1):
4658 Press left mouse button.
4660 -> { "execute": "x-input-send-event",
4661 "arguments": { "console": 0,
4662 "events": [ { "type": "btn",
4663 "data" : { "down": true, "button": "Left" } } ] } }
4664 <- { "return": {} }
4666 -> { "execute": "x-input-send-event",
4667 "arguments": { "console": 0,
4668 "events": [ { "type": "btn",
4669 "data" : { "down": false, "button": "Left" } } ] } }
4670 <- { "return": {} }
4672 Example (2):
4674 Press ctrl-alt-del.
4676 -> { "execute": "x-input-send-event",
4677 "arguments": { "console": 0, "events": [
4678 { "type": "key", "data" : { "down": true,
4679 "key": {"type": "qcode", "data": "ctrl" } } },
4680 { "type": "key", "data" : { "down": true,
4681 "key": {"type": "qcode", "data": "alt" } } },
4682 { "type": "key", "data" : { "down": true,
4683 "key": {"type": "qcode", "data": "delete" } } } ] } }
4684 <- { "return": {} }
4686 Example (3):
4688 Move mouse pointer to absolute coordinates (20000, 400).
4690 -> { "execute": "x-input-send-event" ,
4691 "arguments": { "console": 0, "events": [
4692 { "type": "abs", "data" : { "axis": "X", "value" : 20000 } },
4693 { "type": "abs", "data" : { "axis": "Y", "value" : 400 } } ] } }
4694 <- { "return": {} }
4696 EQMP
4699 .name = "block-set-write-threshold",
4700 .args_type = "node-name:s,write-threshold:l",
4701 .mhandler.cmd_new = qmp_marshal_block_set_write_threshold,
4704 SQMP
4705 block-set-write-threshold
4706 ------------
4708 Change the write threshold for a block drive. The threshold is an offset,
4709 thus must be non-negative. Default is no write threshold.
4710 Setting the threshold to zero disables it.
4712 Arguments:
4714 - "node-name": the node name in the block driver state graph (json-string)
4715 - "write-threshold": the write threshold in bytes (json-int)
4717 Example:
4719 -> { "execute": "block-set-write-threshold",
4720 "arguments": { "node-name": "mydev",
4721 "write-threshold": 17179869184 } }
4722 <- { "return": {} }
4724 EQMP
4727 .name = "query-rocker",
4728 .args_type = "name:s",
4729 .mhandler.cmd_new = qmp_marshal_query_rocker,
4732 SQMP
4733 Show rocker switch
4734 ------------------
4736 Arguments:
4738 - "name": switch name
4740 Example:
4742 -> { "execute": "query-rocker", "arguments": { "name": "sw1" } }
4743 <- { "return": {"name": "sw1", "ports": 2, "id": 1327446905938}}
4745 EQMP
4748 .name = "query-rocker-ports",
4749 .args_type = "name:s",
4750 .mhandler.cmd_new = qmp_marshal_query_rocker_ports,
4753 SQMP
4754 Show rocker switch ports
4755 ------------------------
4757 Arguments:
4759 - "name": switch name
4761 Example:
4763 -> { "execute": "query-rocker-ports", "arguments": { "name": "sw1" } }
4764 <- { "return": [ {"duplex": "full", "enabled": true, "name": "sw1.1",
4765 "autoneg": "off", "link-up": true, "speed": 10000},
4766 {"duplex": "full", "enabled": true, "name": "sw1.2",
4767 "autoneg": "off", "link-up": true, "speed": 10000}
4770 EQMP
4773 .name = "query-rocker-of-dpa-flows",
4774 .args_type = "name:s,tbl-id:i?",
4775 .mhandler.cmd_new = qmp_marshal_query_rocker_of_dpa_flows,
4778 SQMP
4779 Show rocker switch OF-DPA flow tables
4780 -------------------------------------
4782 Arguments:
4784 - "name": switch name
4785 - "tbl-id": (optional) flow table ID
4787 Example:
4789 -> { "execute": "query-rocker-of-dpa-flows", "arguments": { "name": "sw1" } }
4790 <- { "return": [ {"key": {"in-pport": 0, "priority": 1, "tbl-id": 0},
4791 "hits": 138,
4792 "cookie": 0,
4793 "action": {"goto-tbl": 10},
4794 "mask": {"in-pport": 4294901760}
4796 {...more...},
4799 EQMP
4802 .name = "query-rocker-of-dpa-groups",
4803 .args_type = "name:s,type:i?",
4804 .mhandler.cmd_new = qmp_marshal_query_rocker_of_dpa_groups,
4807 SQMP
4808 Show rocker OF-DPA group tables
4809 -------------------------------
4811 Arguments:
4813 - "name": switch name
4814 - "type": (optional) group type
4816 Example:
4818 -> { "execute": "query-rocker-of-dpa-groups", "arguments": { "name": "sw1" } }
4819 <- { "return": [ {"type": 0, "out-pport": 2, "pport": 2, "vlan-id": 3841,
4820 "pop-vlan": 1, "id": 251723778},
4821 {"type": 0, "out-pport": 0, "pport": 0, "vlan-id": 3841,
4822 "pop-vlan": 1, "id": 251723776},
4823 {"type": 0, "out-pport": 1, "pport": 1, "vlan-id": 3840,
4824 "pop-vlan": 1, "id": 251658241},
4825 {"type": 0, "out-pport": 0, "pport": 0, "vlan-id": 3840,
4826 "pop-vlan": 1, "id": 251658240}