ARM: PL061: Cleaning field of PL061 device state
[qemu/ar7.git] / qmp-commands.hx
blob9fb0d788bc1693c6174c2923ce82606a86fd3578
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?,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 max in bytes (json-int)
2029 - "bps_rd_max": read max in bytes (json-int)
2030 - "bps_wr_max": write max in bytes (json-int)
2031 - "iops_max": total I/O operations max (json-int)
2032 - "iops_rd_max": read I/O operations max (json-int)
2033 - "iops_wr_max": write I/O operations max (json-int)
2034 - "iops_size": I/O size in bytes when limiting (json-int)
2035 - "group": throttle group name (json-string)
2037 Example:
2039 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
2040 "bps": 1000000,
2041 "bps_rd": 0,
2042 "bps_wr": 0,
2043 "iops": 0,
2044 "iops_rd": 0,
2045 "iops_wr": 0,
2046 "bps_max": 8000000,
2047 "bps_rd_max": 0,
2048 "bps_wr_max": 0,
2049 "iops_max": 0,
2050 "iops_rd_max": 0,
2051 "iops_wr_max": 0,
2052 "iops_size": 0 } }
2053 <- { "return": {} }
2055 EQMP
2058 .name = "set_password",
2059 .args_type = "protocol:s,password:s,connected:s?",
2060 .mhandler.cmd_new = qmp_marshal_set_password,
2063 SQMP
2064 set_password
2065 ------------
2067 Set the password for vnc/spice protocols.
2069 Arguments:
2071 - "protocol": protocol name (json-string)
2072 - "password": password (json-string)
2073 - "connected": [ keep | disconnect | fail ] (json-string, optional)
2075 Example:
2077 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
2078 "password": "secret" } }
2079 <- { "return": {} }
2081 EQMP
2084 .name = "expire_password",
2085 .args_type = "protocol:s,time:s",
2086 .mhandler.cmd_new = qmp_marshal_expire_password,
2089 SQMP
2090 expire_password
2091 ---------------
2093 Set the password expire time for vnc/spice protocols.
2095 Arguments:
2097 - "protocol": protocol name (json-string)
2098 - "time": [ now | never | +secs | secs ] (json-string)
2100 Example:
2102 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
2103 "time": "+60" } }
2104 <- { "return": {} }
2106 EQMP
2109 .name = "add_client",
2110 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
2111 .mhandler.cmd_new = qmp_marshal_add_client,
2114 SQMP
2115 add_client
2116 ----------
2118 Add a graphics client
2120 Arguments:
2122 - "protocol": protocol name (json-string)
2123 - "fdname": file descriptor name (json-string)
2124 - "skipauth": whether to skip authentication (json-bool, optional)
2125 - "tls": whether to perform TLS (json-bool, optional)
2127 Example:
2129 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
2130 "fdname": "myclient" } }
2131 <- { "return": {} }
2133 EQMP
2135 .name = "qmp_capabilities",
2136 .args_type = "",
2137 .params = "",
2138 .help = "enable QMP capabilities",
2139 .mhandler.cmd_new = qmp_capabilities,
2142 SQMP
2143 qmp_capabilities
2144 ----------------
2146 Enable QMP capabilities.
2148 Arguments: None.
2150 Example:
2152 -> { "execute": "qmp_capabilities" }
2153 <- { "return": {} }
2155 Note: This command must be issued before issuing any other command.
2157 EQMP
2160 .name = "human-monitor-command",
2161 .args_type = "command-line:s,cpu-index:i?",
2162 .mhandler.cmd_new = qmp_marshal_human_monitor_command,
2165 SQMP
2166 human-monitor-command
2167 ---------------------
2169 Execute a Human Monitor command.
2171 Arguments:
2173 - command-line: the command name and its arguments, just like the
2174 Human Monitor's shell (json-string)
2175 - cpu-index: select the CPU number to be used by commands which access CPU
2176 data, like 'info registers'. The Monitor selects CPU 0 if this
2177 argument is not provided (json-int, optional)
2179 Example:
2181 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
2182 <- { "return": "kvm support: enabled\r\n" }
2184 Notes:
2186 (1) The Human Monitor is NOT an stable interface, this means that command
2187 names, arguments and responses can change or be removed at ANY time.
2188 Applications that rely on long term stability guarantees should NOT
2189 use this command
2191 (2) Limitations:
2193 o This command is stateless, this means that commands that depend
2194 on state information (such as getfd) might not work
2196 o Commands that prompt the user for data (eg. 'cont' when the block
2197 device is encrypted) don't currently work
2199 3. Query Commands
2200 =================
2202 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
2203 HXCOMM this! We will possibly move query commands definitions inside those
2204 HXCOMM sections, just like regular commands.
2206 EQMP
2208 SQMP
2209 query-version
2210 -------------
2212 Show QEMU version.
2214 Return a json-object with the following information:
2216 - "qemu": A json-object containing three integer values:
2217 - "major": QEMU's major version (json-int)
2218 - "minor": QEMU's minor version (json-int)
2219 - "micro": QEMU's micro version (json-int)
2220 - "package": package's version (json-string)
2222 Example:
2224 -> { "execute": "query-version" }
2225 <- {
2226 "return":{
2227 "qemu":{
2228 "major":0,
2229 "minor":11,
2230 "micro":5
2232 "package":""
2236 EQMP
2239 .name = "query-version",
2240 .args_type = "",
2241 .mhandler.cmd_new = qmp_marshal_query_version,
2244 SQMP
2245 query-commands
2246 --------------
2248 List QMP available commands.
2250 Each command is represented by a json-object, the returned value is a json-array
2251 of all commands.
2253 Each json-object contain:
2255 - "name": command's name (json-string)
2257 Example:
2259 -> { "execute": "query-commands" }
2260 <- {
2261 "return":[
2263 "name":"query-balloon"
2266 "name":"system_powerdown"
2271 Note: This example has been shortened as the real response is too long.
2273 EQMP
2276 .name = "query-commands",
2277 .args_type = "",
2278 .mhandler.cmd_new = qmp_marshal_query_commands,
2281 SQMP
2282 query-events
2283 --------------
2285 List QMP available events.
2287 Each event is represented by a json-object, the returned value is a json-array
2288 of all events.
2290 Each json-object contains:
2292 - "name": event's name (json-string)
2294 Example:
2296 -> { "execute": "query-events" }
2297 <- {
2298 "return":[
2300 "name":"SHUTDOWN"
2303 "name":"RESET"
2308 Note: This example has been shortened as the real response is too long.
2310 EQMP
2313 .name = "query-events",
2314 .args_type = "",
2315 .mhandler.cmd_new = qmp_marshal_query_events,
2318 SQMP
2319 query-qmp-schema
2320 ----------------
2322 Return the QMP wire schema. The returned value is a json-array of
2323 named schema entities. Entities are commands, events and various
2324 types. See docs/qapi-code-gen.txt for information on their structure
2325 and intended use.
2327 EQMP
2330 .name = "query-qmp-schema",
2331 .args_type = "",
2332 .mhandler.cmd_new = qmp_query_qmp_schema,
2335 SQMP
2336 query-chardev
2337 -------------
2339 Each device is represented by a json-object. The returned value is a json-array
2340 of all devices.
2342 Each json-object contain the following:
2344 - "label": device's label (json-string)
2345 - "filename": device's file (json-string)
2346 - "frontend-open": open/closed state of the frontend device attached to this
2347 backend (json-bool)
2349 Example:
2351 -> { "execute": "query-chardev" }
2352 <- {
2353 "return": [
2355 "label": "charchannel0",
2356 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.agent,server",
2357 "frontend-open": false
2360 "label": "charmonitor",
2361 "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.monitor,server",
2362 "frontend-open": true
2365 "label": "charserial0",
2366 "filename": "pty:/dev/pts/2",
2367 "frontend-open": true
2372 EQMP
2375 .name = "query-chardev",
2376 .args_type = "",
2377 .mhandler.cmd_new = qmp_marshal_query_chardev,
2380 SQMP
2381 query-chardev-backends
2382 -------------
2384 List available character device backends.
2386 Each backend is represented by a json-object, the returned value is a json-array
2387 of all backends.
2389 Each json-object contains:
2391 - "name": backend name (json-string)
2393 Example:
2395 -> { "execute": "query-chardev-backends" }
2396 <- {
2397 "return":[
2399 "name":"udp"
2402 "name":"tcp"
2405 "name":"unix"
2408 "name":"spiceport"
2413 EQMP
2416 .name = "query-chardev-backends",
2417 .args_type = "",
2418 .mhandler.cmd_new = qmp_marshal_query_chardev_backends,
2421 SQMP
2422 query-block
2423 -----------
2425 Show the block devices.
2427 Each block device information is stored in a json-object and the returned value
2428 is a json-array of all devices.
2430 Each json-object contain the following:
2432 - "device": device name (json-string)
2433 - "type": device type (json-string)
2434 - deprecated, retained for backward compatibility
2435 - Possible values: "unknown"
2436 - "removable": true if the device is removable, false otherwise (json-bool)
2437 - "locked": true if the device is locked, false otherwise (json-bool)
2438 - "tray_open": only present if removable, true if the device has a tray,
2439 and it is open (json-bool)
2440 - "inserted": only present if the device is inserted, it is a json-object
2441 containing the following:
2442 - "file": device file name (json-string)
2443 - "ro": true if read-only, false otherwise (json-bool)
2444 - "drv": driver format name (json-string)
2445 - Possible values: "blkdebug", "bochs", "cloop", "dmg",
2446 "file", "file", "ftp", "ftps", "host_cdrom",
2447 "host_device", "http", "https",
2448 "nbd", "parallels", "qcow", "qcow2", "raw",
2449 "tftp", "vdi", "vmdk", "vpc", "vvfat"
2450 - "backing_file": backing file name (json-string, optional)
2451 - "backing_file_depth": number of files in the backing file chain (json-int)
2452 - "encrypted": true if encrypted, false otherwise (json-bool)
2453 - "bps": limit total bytes per second (json-int)
2454 - "bps_rd": limit read bytes per second (json-int)
2455 - "bps_wr": limit write bytes per second (json-int)
2456 - "iops": limit total I/O operations per second (json-int)
2457 - "iops_rd": limit read operations per second (json-int)
2458 - "iops_wr": limit write operations per second (json-int)
2459 - "bps_max": total max in bytes (json-int)
2460 - "bps_rd_max": read max in bytes (json-int)
2461 - "bps_wr_max": write max in bytes (json-int)
2462 - "iops_max": total I/O operations max (json-int)
2463 - "iops_rd_max": read I/O operations max (json-int)
2464 - "iops_wr_max": write I/O operations max (json-int)
2465 - "iops_size": I/O size when limiting by iops (json-int)
2466 - "detect_zeroes": detect and optimize zero writing (json-string)
2467 - Possible values: "off", "on", "unmap"
2468 - "write_threshold": write offset threshold in bytes, a event will be
2469 emitted if crossed. Zero if disabled (json-int)
2470 - "image": the detail of the image, it is a json-object containing
2471 the following:
2472 - "filename": image file name (json-string)
2473 - "format": image format (json-string)
2474 - "virtual-size": image capacity in bytes (json-int)
2475 - "dirty-flag": true if image is not cleanly closed, not present
2476 means clean (json-bool, optional)
2477 - "actual-size": actual size on disk in bytes of the image, not
2478 present when image does not support thin
2479 provision (json-int, optional)
2480 - "cluster-size": size of a cluster in bytes, not present if image
2481 format does not support it (json-int, optional)
2482 - "encrypted": true if the image is encrypted, not present means
2483 false or the image format does not support
2484 encryption (json-bool, optional)
2485 - "backing_file": backing file name, not present means no backing
2486 file is used or the image format does not
2487 support backing file chain
2488 (json-string, optional)
2489 - "full-backing-filename": full path of the backing file, not
2490 present if it equals backing_file or no
2491 backing file is used
2492 (json-string, optional)
2493 - "backing-filename-format": the format of the backing file, not
2494 present means unknown or no backing
2495 file (json-string, optional)
2496 - "snapshots": the internal snapshot info, it is an optional list
2497 of json-object containing the following:
2498 - "id": unique snapshot id (json-string)
2499 - "name": snapshot name (json-string)
2500 - "vm-state-size": size of the VM state in bytes (json-int)
2501 - "date-sec": UTC date of the snapshot in seconds (json-int)
2502 - "date-nsec": fractional part in nanoseconds to be used with
2503 date-sec (json-int)
2504 - "vm-clock-sec": VM clock relative to boot in seconds
2505 (json-int)
2506 - "vm-clock-nsec": fractional part in nanoseconds to be used
2507 with vm-clock-sec (json-int)
2508 - "backing-image": the detail of the backing image, it is an
2509 optional json-object only present when a
2510 backing image present for this image
2512 - "io-status": I/O operation status, only present if the device supports it
2513 and the VM is configured to stop on errors. It's always reset
2514 to "ok" when the "cont" command is issued (json_string, optional)
2515 - Possible values: "ok", "failed", "nospace"
2517 Example:
2519 -> { "execute": "query-block" }
2520 <- {
2521 "return":[
2523 "io-status": "ok",
2524 "device":"ide0-hd0",
2525 "locked":false,
2526 "removable":false,
2527 "inserted":{
2528 "ro":false,
2529 "drv":"qcow2",
2530 "encrypted":false,
2531 "file":"disks/test.qcow2",
2532 "backing_file_depth":1,
2533 "bps":1000000,
2534 "bps_rd":0,
2535 "bps_wr":0,
2536 "iops":1000000,
2537 "iops_rd":0,
2538 "iops_wr":0,
2539 "bps_max": 8000000,
2540 "bps_rd_max": 0,
2541 "bps_wr_max": 0,
2542 "iops_max": 0,
2543 "iops_rd_max": 0,
2544 "iops_wr_max": 0,
2545 "iops_size": 0,
2546 "detect_zeroes": "on",
2547 "write_threshold": 0,
2548 "image":{
2549 "filename":"disks/test.qcow2",
2550 "format":"qcow2",
2551 "virtual-size":2048000,
2552 "backing_file":"base.qcow2",
2553 "full-backing-filename":"disks/base.qcow2",
2554 "backing-filename-format":"qcow2",
2555 "snapshots":[
2557 "id": "1",
2558 "name": "snapshot1",
2559 "vm-state-size": 0,
2560 "date-sec": 10000200,
2561 "date-nsec": 12,
2562 "vm-clock-sec": 206,
2563 "vm-clock-nsec": 30
2566 "backing-image":{
2567 "filename":"disks/base.qcow2",
2568 "format":"qcow2",
2569 "virtual-size":2048000
2573 "type":"unknown"
2576 "io-status": "ok",
2577 "device":"ide1-cd0",
2578 "locked":false,
2579 "removable":true,
2580 "type":"unknown"
2583 "device":"floppy0",
2584 "locked":false,
2585 "removable":true,
2586 "type":"unknown"
2589 "device":"sd0",
2590 "locked":false,
2591 "removable":true,
2592 "type":"unknown"
2597 EQMP
2600 .name = "query-block",
2601 .args_type = "",
2602 .mhandler.cmd_new = qmp_marshal_query_block,
2605 SQMP
2606 query-blockstats
2607 ----------------
2609 Show block device statistics.
2611 Each device statistic information is stored in a json-object and the returned
2612 value is a json-array of all devices.
2614 Each json-object contain the following:
2616 - "device": device name (json-string)
2617 - "stats": A json-object with the statistics information, it contains:
2618 - "rd_bytes": bytes read (json-int)
2619 - "wr_bytes": bytes written (json-int)
2620 - "rd_operations": read operations (json-int)
2621 - "wr_operations": write operations (json-int)
2622 - "flush_operations": cache flush operations (json-int)
2623 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
2624 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
2625 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
2626 - "wr_highest_offset": The offset after the greatest byte written to the
2627 BlockDriverState since it has been opened (json-int)
2628 - "rd_merged": number of read requests that have been merged into
2629 another request (json-int)
2630 - "wr_merged": number of write requests that have been merged into
2631 another request (json-int)
2632 - "idle_time_ns": time since the last I/O operation, in
2633 nanoseconds. If the field is absent it means
2634 that there haven't been any operations yet
2635 (json-int, optional)
2636 - "failed_rd_operations": number of failed read operations
2637 (json-int)
2638 - "failed_wr_operations": number of failed write operations
2639 (json-int)
2640 - "failed_flush_operations": number of failed flush operations
2641 (json-int)
2642 - "invalid_rd_operations": number of invalid read operations
2643 (json-int)
2644 - "invalid_wr_operations": number of invalid write operations
2645 (json-int)
2646 - "invalid_flush_operations": number of invalid flush operations
2647 (json-int)
2648 - "account_invalid": whether invalid operations are included in
2649 the last access statistics (json-bool)
2650 - "account_failed": whether failed operations are included in the
2651 latency and last access statistics
2652 (json-bool)
2653 - "timed_stats": A json-array containing statistics collected in
2654 specific intervals, with the following members:
2655 - "interval_length": interval used for calculating the
2656 statistics, in seconds (json-int)
2657 - "min_rd_latency_ns": minimum latency of read operations in
2658 the defined interval, in nanoseconds
2659 (json-int)
2660 - "min_wr_latency_ns": minimum latency of write operations in
2661 the defined interval, in nanoseconds
2662 (json-int)
2663 - "min_flush_latency_ns": minimum latency of flush operations
2664 in the defined interval, in
2665 nanoseconds (json-int)
2666 - "max_rd_latency_ns": maximum latency of read operations in
2667 the defined interval, in nanoseconds
2668 (json-int)
2669 - "max_wr_latency_ns": maximum latency of write operations in
2670 the defined interval, in nanoseconds
2671 (json-int)
2672 - "max_flush_latency_ns": maximum latency of flush operations
2673 in the defined interval, in
2674 nanoseconds (json-int)
2675 - "avg_rd_latency_ns": average latency of read operations in
2676 the defined interval, in nanoseconds
2677 (json-int)
2678 - "avg_wr_latency_ns": average latency of write operations in
2679 the defined interval, in nanoseconds
2680 (json-int)
2681 - "avg_flush_latency_ns": average latency of flush operations
2682 in the defined interval, in
2683 nanoseconds (json-int)
2684 - "avg_rd_queue_depth": average number of pending read
2685 operations in the defined interval
2686 (json-number)
2687 - "avg_wr_queue_depth": average number of pending write
2688 operations in the defined interval
2689 (json-number).
2690 - "parent": Contains recursively the statistics of the underlying
2691 protocol (e.g. the host file for a qcow2 image). If there is
2692 no underlying protocol, this field is omitted
2693 (json-object, optional)
2695 Example:
2697 -> { "execute": "query-blockstats" }
2698 <- {
2699 "return":[
2701 "device":"ide0-hd0",
2702 "parent":{
2703 "stats":{
2704 "wr_highest_offset":3686448128,
2705 "wr_bytes":9786368,
2706 "wr_operations":751,
2707 "rd_bytes":122567168,
2708 "rd_operations":36772
2709 "wr_total_times_ns":313253456
2710 "rd_total_times_ns":3465673657
2711 "flush_total_times_ns":49653
2712 "flush_operations":61,
2713 "rd_merged":0,
2714 "wr_merged":0,
2715 "idle_time_ns":2953431879,
2716 "account_invalid":true,
2717 "account_failed":false
2720 "stats":{
2721 "wr_highest_offset":2821110784,
2722 "wr_bytes":9786368,
2723 "wr_operations":692,
2724 "rd_bytes":122739200,
2725 "rd_operations":36604
2726 "flush_operations":51,
2727 "wr_total_times_ns":313253456
2728 "rd_total_times_ns":3465673657
2729 "flush_total_times_ns":49653,
2730 "rd_merged":0,
2731 "wr_merged":0,
2732 "idle_time_ns":2953431879,
2733 "account_invalid":true,
2734 "account_failed":false
2738 "device":"ide1-cd0",
2739 "stats":{
2740 "wr_highest_offset":0,
2741 "wr_bytes":0,
2742 "wr_operations":0,
2743 "rd_bytes":0,
2744 "rd_operations":0
2745 "flush_operations":0,
2746 "wr_total_times_ns":0
2747 "rd_total_times_ns":0
2748 "flush_total_times_ns":0,
2749 "rd_merged":0,
2750 "wr_merged":0,
2751 "account_invalid":false,
2752 "account_failed":false
2756 "device":"floppy0",
2757 "stats":{
2758 "wr_highest_offset":0,
2759 "wr_bytes":0,
2760 "wr_operations":0,
2761 "rd_bytes":0,
2762 "rd_operations":0
2763 "flush_operations":0,
2764 "wr_total_times_ns":0
2765 "rd_total_times_ns":0
2766 "flush_total_times_ns":0,
2767 "rd_merged":0,
2768 "wr_merged":0,
2769 "account_invalid":false,
2770 "account_failed":false
2774 "device":"sd0",
2775 "stats":{
2776 "wr_highest_offset":0,
2777 "wr_bytes":0,
2778 "wr_operations":0,
2779 "rd_bytes":0,
2780 "rd_operations":0
2781 "flush_operations":0,
2782 "wr_total_times_ns":0
2783 "rd_total_times_ns":0
2784 "flush_total_times_ns":0,
2785 "rd_merged":0,
2786 "wr_merged":0,
2787 "account_invalid":false,
2788 "account_failed":false
2794 EQMP
2797 .name = "query-blockstats",
2798 .args_type = "query-nodes:b?",
2799 .mhandler.cmd_new = qmp_marshal_query_blockstats,
2802 SQMP
2803 query-cpus
2804 ----------
2806 Show CPU information.
2808 Return a json-array. Each CPU is represented by a json-object, which contains:
2810 - "CPU": CPU index (json-int)
2811 - "current": true if this is the current CPU, false otherwise (json-bool)
2812 - "halted": true if the cpu is halted, false otherwise (json-bool)
2813 - "qom_path": path to the CPU object in the QOM tree (json-str)
2814 - "arch": architecture of the cpu, which determines what additional
2815 keys will be present (json-str)
2816 - Current program counter. The key's name depends on the architecture:
2817 "pc": i386/x86_64 (json-int)
2818 "nip": PPC (json-int)
2819 "pc" and "npc": sparc (json-int)
2820 "PC": mips (json-int)
2821 - "thread_id": ID of the underlying host thread (json-int)
2823 Example:
2825 -> { "execute": "query-cpus" }
2826 <- {
2827 "return":[
2829 "CPU":0,
2830 "current":true,
2831 "halted":false,
2832 "qom_path":"/machine/unattached/device[0]",
2833 "arch":"x86",
2834 "pc":3227107138,
2835 "thread_id":3134
2838 "CPU":1,
2839 "current":false,
2840 "halted":true,
2841 "qom_path":"/machine/unattached/device[2]",
2842 "arch":"x86",
2843 "pc":7108165,
2844 "thread_id":3135
2849 EQMP
2852 .name = "query-cpus",
2853 .args_type = "",
2854 .mhandler.cmd_new = qmp_marshal_query_cpus,
2857 SQMP
2858 query-iothreads
2859 ---------------
2861 Returns a list of information about each iothread.
2863 Note this list excludes the QEMU main loop thread, which is not declared
2864 using the -object iothread command-line option. It is always the main thread
2865 of the process.
2867 Return a json-array. Each iothread is represented by a json-object, which contains:
2869 - "id": name of iothread (json-str)
2870 - "thread-id": ID of the underlying host thread (json-int)
2872 Example:
2874 -> { "execute": "query-iothreads" }
2875 <- {
2876 "return":[
2878 "id":"iothread0",
2879 "thread-id":3134
2882 "id":"iothread1",
2883 "thread-id":3135
2888 EQMP
2891 .name = "query-iothreads",
2892 .args_type = "",
2893 .mhandler.cmd_new = qmp_marshal_query_iothreads,
2896 SQMP
2897 query-pci
2898 ---------
2900 PCI buses and devices information.
2902 The returned value is a json-array of all buses. Each bus is represented by
2903 a json-object, which has a key with a json-array of all PCI devices attached
2904 to it. Each device is represented by a json-object.
2906 The bus json-object contains the following:
2908 - "bus": bus number (json-int)
2909 - "devices": a json-array of json-objects, each json-object represents a
2910 PCI device
2912 The PCI device json-object contains the following:
2914 - "bus": identical to the parent's bus number (json-int)
2915 - "slot": slot number (json-int)
2916 - "function": function number (json-int)
2917 - "class_info": a json-object containing:
2918 - "desc": device class description (json-string, optional)
2919 - "class": device class number (json-int)
2920 - "id": a json-object containing:
2921 - "device": device ID (json-int)
2922 - "vendor": vendor ID (json-int)
2923 - "irq": device's IRQ if assigned (json-int, optional)
2924 - "qdev_id": qdev id string (json-string)
2925 - "pci_bridge": It's a json-object, only present if this device is a
2926 PCI bridge, contains:
2927 - "bus": bus number (json-int)
2928 - "secondary": secondary bus number (json-int)
2929 - "subordinate": subordinate bus number (json-int)
2930 - "io_range": I/O memory range information, a json-object with the
2931 following members:
2932 - "base": base address, in bytes (json-int)
2933 - "limit": limit address, in bytes (json-int)
2934 - "memory_range": memory range information, a json-object with the
2935 following members:
2936 - "base": base address, in bytes (json-int)
2937 - "limit": limit address, in bytes (json-int)
2938 - "prefetchable_range": Prefetchable memory range information, a
2939 json-object with the following members:
2940 - "base": base address, in bytes (json-int)
2941 - "limit": limit address, in bytes (json-int)
2942 - "devices": a json-array of PCI devices if there's any attached, each
2943 each element is represented by a json-object, which contains
2944 the same members of the 'PCI device json-object' described
2945 above (optional)
2946 - "regions": a json-array of json-objects, each json-object represents a
2947 memory region of this device
2949 The memory range json-object contains the following:
2951 - "base": base memory address (json-int)
2952 - "limit": limit value (json-int)
2954 The region json-object can be an I/O region or a memory region, an I/O region
2955 json-object contains the following:
2957 - "type": "io" (json-string, fixed)
2958 - "bar": BAR number (json-int)
2959 - "address": memory address (json-int)
2960 - "size": memory size (json-int)
2962 A memory region json-object contains the following:
2964 - "type": "memory" (json-string, fixed)
2965 - "bar": BAR number (json-int)
2966 - "address": memory address (json-int)
2967 - "size": memory size (json-int)
2968 - "mem_type_64": true or false (json-bool)
2969 - "prefetch": true or false (json-bool)
2971 Example:
2973 -> { "execute": "query-pci" }
2974 <- {
2975 "return":[
2977 "bus":0,
2978 "devices":[
2980 "bus":0,
2981 "qdev_id":"",
2982 "slot":0,
2983 "class_info":{
2984 "class":1536,
2985 "desc":"Host bridge"
2987 "id":{
2988 "device":32902,
2989 "vendor":4663
2991 "function":0,
2992 "regions":[
2997 "bus":0,
2998 "qdev_id":"",
2999 "slot":1,
3000 "class_info":{
3001 "class":1537,
3002 "desc":"ISA bridge"
3004 "id":{
3005 "device":32902,
3006 "vendor":28672
3008 "function":0,
3009 "regions":[
3014 "bus":0,
3015 "qdev_id":"",
3016 "slot":1,
3017 "class_info":{
3018 "class":257,
3019 "desc":"IDE controller"
3021 "id":{
3022 "device":32902,
3023 "vendor":28688
3025 "function":1,
3026 "regions":[
3028 "bar":4,
3029 "size":16,
3030 "address":49152,
3031 "type":"io"
3036 "bus":0,
3037 "qdev_id":"",
3038 "slot":2,
3039 "class_info":{
3040 "class":768,
3041 "desc":"VGA controller"
3043 "id":{
3044 "device":4115,
3045 "vendor":184
3047 "function":0,
3048 "regions":[
3050 "prefetch":true,
3051 "mem_type_64":false,
3052 "bar":0,
3053 "size":33554432,
3054 "address":4026531840,
3055 "type":"memory"
3058 "prefetch":false,
3059 "mem_type_64":false,
3060 "bar":1,
3061 "size":4096,
3062 "address":4060086272,
3063 "type":"memory"
3066 "prefetch":false,
3067 "mem_type_64":false,
3068 "bar":6,
3069 "size":65536,
3070 "address":-1,
3071 "type":"memory"
3076 "bus":0,
3077 "qdev_id":"",
3078 "irq":11,
3079 "slot":4,
3080 "class_info":{
3081 "class":1280,
3082 "desc":"RAM controller"
3084 "id":{
3085 "device":6900,
3086 "vendor":4098
3088 "function":0,
3089 "regions":[
3091 "bar":0,
3092 "size":32,
3093 "address":49280,
3094 "type":"io"
3103 Note: This example has been shortened as the real response is too long.
3105 EQMP
3108 .name = "query-pci",
3109 .args_type = "",
3110 .mhandler.cmd_new = qmp_marshal_query_pci,
3113 SQMP
3114 query-kvm
3115 ---------
3117 Show KVM information.
3119 Return a json-object with the following information:
3121 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
3122 - "present": true if QEMU has KVM support, false otherwise (json-bool)
3124 Example:
3126 -> { "execute": "query-kvm" }
3127 <- { "return": { "enabled": true, "present": true } }
3129 EQMP
3132 .name = "query-kvm",
3133 .args_type = "",
3134 .mhandler.cmd_new = qmp_marshal_query_kvm,
3137 SQMP
3138 query-status
3139 ------------
3141 Return a json-object with the following information:
3143 - "running": true if the VM is running, or false if it is paused (json-bool)
3144 - "singlestep": true if the VM is in single step mode,
3145 false otherwise (json-bool)
3146 - "status": one of the following values (json-string)
3147 "debug" - QEMU is running on a debugger
3148 "inmigrate" - guest is paused waiting for an incoming migration
3149 "internal-error" - An internal error that prevents further guest
3150 execution has occurred
3151 "io-error" - the last IOP has failed and the device is configured
3152 to pause on I/O errors
3153 "paused" - guest has been paused via the 'stop' command
3154 "postmigrate" - guest is paused following a successful 'migrate'
3155 "prelaunch" - QEMU was started with -S and guest has not started
3156 "finish-migrate" - guest is paused to finish the migration process
3157 "restore-vm" - guest is paused to restore VM state
3158 "running" - guest is actively running
3159 "save-vm" - guest is paused to save the VM state
3160 "shutdown" - guest is shut down (and -no-shutdown is in use)
3161 "watchdog" - the watchdog action is configured to pause and
3162 has been triggered
3164 Example:
3166 -> { "execute": "query-status" }
3167 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
3169 EQMP
3172 .name = "query-status",
3173 .args_type = "",
3174 .mhandler.cmd_new = qmp_marshal_query_status,
3177 SQMP
3178 query-mice
3179 ----------
3181 Show VM mice information.
3183 Each mouse is represented by a json-object, the returned value is a json-array
3184 of all mice.
3186 The mouse json-object contains the following:
3188 - "name": mouse's name (json-string)
3189 - "index": mouse's index (json-int)
3190 - "current": true if this mouse is receiving events, false otherwise (json-bool)
3191 - "absolute": true if the mouse generates absolute input events (json-bool)
3193 Example:
3195 -> { "execute": "query-mice" }
3196 <- {
3197 "return":[
3199 "name":"QEMU Microsoft Mouse",
3200 "index":0,
3201 "current":false,
3202 "absolute":false
3205 "name":"QEMU PS/2 Mouse",
3206 "index":1,
3207 "current":true,
3208 "absolute":true
3213 EQMP
3216 .name = "query-mice",
3217 .args_type = "",
3218 .mhandler.cmd_new = qmp_marshal_query_mice,
3221 SQMP
3222 query-vnc
3223 ---------
3225 Show VNC server information.
3227 Return a json-object with server information. Connected clients are returned
3228 as a json-array of json-objects.
3230 The main json-object contains the following:
3232 - "enabled": true or false (json-bool)
3233 - "host": server's IP address (json-string)
3234 - "family": address family (json-string)
3235 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3236 - "service": server's port number (json-string)
3237 - "auth": authentication method (json-string)
3238 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
3239 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
3240 "vencrypt+plain", "vencrypt+tls+none",
3241 "vencrypt+tls+plain", "vencrypt+tls+sasl",
3242 "vencrypt+tls+vnc", "vencrypt+x509+none",
3243 "vencrypt+x509+plain", "vencrypt+x509+sasl",
3244 "vencrypt+x509+vnc", "vnc"
3245 - "clients": a json-array of all connected clients
3247 Clients are described by a json-object, each one contain the following:
3249 - "host": client's IP address (json-string)
3250 - "family": address family (json-string)
3251 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3252 - "service": client's port number (json-string)
3253 - "x509_dname": TLS dname (json-string, optional)
3254 - "sasl_username": SASL username (json-string, optional)
3256 Example:
3258 -> { "execute": "query-vnc" }
3259 <- {
3260 "return":{
3261 "enabled":true,
3262 "host":"0.0.0.0",
3263 "service":"50402",
3264 "auth":"vnc",
3265 "family":"ipv4",
3266 "clients":[
3268 "host":"127.0.0.1",
3269 "service":"50401",
3270 "family":"ipv4"
3276 EQMP
3279 .name = "query-vnc",
3280 .args_type = "",
3281 .mhandler.cmd_new = qmp_marshal_query_vnc,
3284 .name = "query-vnc-servers",
3285 .args_type = "",
3286 .mhandler.cmd_new = qmp_marshal_query_vnc_servers,
3289 SQMP
3290 query-spice
3291 -----------
3293 Show SPICE server information.
3295 Return a json-object with server information. Connected clients are returned
3296 as a json-array of json-objects.
3298 The main json-object contains the following:
3300 - "enabled": true or false (json-bool)
3301 - "host": server's IP address (json-string)
3302 - "port": server's port number (json-int, optional)
3303 - "tls-port": server's port number (json-int, optional)
3304 - "auth": authentication method (json-string)
3305 - Possible values: "none", "spice"
3306 - "channels": a json-array of all active channels clients
3308 Channels are described by a json-object, each one contain the following:
3310 - "host": client's IP address (json-string)
3311 - "family": address family (json-string)
3312 - Possible values: "ipv4", "ipv6", "unix", "unknown"
3313 - "port": client's port number (json-string)
3314 - "connection-id": spice connection id. All channels with the same id
3315 belong to the same spice session (json-int)
3316 - "channel-type": channel type. "1" is the main control channel, filter for
3317 this one if you want track spice sessions only (json-int)
3318 - "channel-id": channel id. Usually "0", might be different needed when
3319 multiple channels of the same type exist, such as multiple
3320 display channels in a multihead setup (json-int)
3321 - "tls": whether the channel is encrypted (json-bool)
3323 Example:
3325 -> { "execute": "query-spice" }
3326 <- {
3327 "return": {
3328 "enabled": true,
3329 "auth": "spice",
3330 "port": 5920,
3331 "tls-port": 5921,
3332 "host": "0.0.0.0",
3333 "channels": [
3335 "port": "54924",
3336 "family": "ipv4",
3337 "channel-type": 1,
3338 "connection-id": 1804289383,
3339 "host": "127.0.0.1",
3340 "channel-id": 0,
3341 "tls": true
3344 "port": "36710",
3345 "family": "ipv4",
3346 "channel-type": 4,
3347 "connection-id": 1804289383,
3348 "host": "127.0.0.1",
3349 "channel-id": 0,
3350 "tls": false
3352 [ ... more channels follow ... ]
3357 EQMP
3359 #if defined(CONFIG_SPICE)
3361 .name = "query-spice",
3362 .args_type = "",
3363 .mhandler.cmd_new = qmp_marshal_query_spice,
3365 #endif
3367 SQMP
3368 query-name
3369 ----------
3371 Show VM name.
3373 Return a json-object with the following information:
3375 - "name": VM's name (json-string, optional)
3377 Example:
3379 -> { "execute": "query-name" }
3380 <- { "return": { "name": "qemu-name" } }
3382 EQMP
3385 .name = "query-name",
3386 .args_type = "",
3387 .mhandler.cmd_new = qmp_marshal_query_name,
3390 SQMP
3391 query-uuid
3392 ----------
3394 Show VM UUID.
3396 Return a json-object with the following information:
3398 - "UUID": Universally Unique Identifier (json-string)
3400 Example:
3402 -> { "execute": "query-uuid" }
3403 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
3405 EQMP
3408 .name = "query-uuid",
3409 .args_type = "",
3410 .mhandler.cmd_new = qmp_marshal_query_uuid,
3413 SQMP
3414 query-command-line-options
3415 --------------------------
3417 Show command line option schema.
3419 Return a json-array of command line option schema for all options (or for
3420 the given option), returning an error if the given option doesn't exist.
3422 Each array entry contains the following:
3424 - "option": option name (json-string)
3425 - "parameters": a json-array describes all parameters of the option:
3426 - "name": parameter name (json-string)
3427 - "type": parameter type (one of 'string', 'boolean', 'number',
3428 or 'size')
3429 - "help": human readable description of the parameter
3430 (json-string, optional)
3431 - "default": default value string for the parameter
3432 (json-string, optional)
3434 Example:
3436 -> { "execute": "query-command-line-options", "arguments": { "option": "option-rom" } }
3437 <- { "return": [
3439 "parameters": [
3441 "name": "romfile",
3442 "type": "string"
3445 "name": "bootindex",
3446 "type": "number"
3449 "option": "option-rom"
3454 EQMP
3457 .name = "query-command-line-options",
3458 .args_type = "option:s?",
3459 .mhandler.cmd_new = qmp_marshal_query_command_line_options,
3462 SQMP
3463 query-migrate
3464 -------------
3466 Migration status.
3468 Return a json-object. If migration is active there will be another json-object
3469 with RAM migration status and if block migration is active another one with
3470 block migration status.
3472 The main json-object contains the following:
3474 - "status": migration status (json-string)
3475 - Possible values: "setup", "active", "completed", "failed", "cancelled"
3476 - "total-time": total amount of ms since migration started. If
3477 migration has ended, it returns the total migration
3478 time (json-int)
3479 - "setup-time" amount of setup time in milliseconds _before_ the
3480 iterations begin but _after_ the QMP command is issued.
3481 This is designed to provide an accounting of any activities
3482 (such as RDMA pinning) which may be expensive, but do not
3483 actually occur during the iterative migration rounds
3484 themselves. (json-int)
3485 - "downtime": only present when migration has finished correctly
3486 total amount in ms for downtime that happened (json-int)
3487 - "expected-downtime": only present while migration is active
3488 total amount in ms for downtime that was calculated on
3489 the last bitmap round (json-int)
3490 - "ram": only present if "status" is "active", it is a json-object with the
3491 following RAM information:
3492 - "transferred": amount transferred in bytes (json-int)
3493 - "remaining": amount remaining to transfer in bytes (json-int)
3494 - "total": total amount of memory in bytes (json-int)
3495 - "duplicate": number of pages filled entirely with the same
3496 byte (json-int)
3497 These are sent over the wire much more efficiently.
3498 - "skipped": number of skipped zero pages (json-int)
3499 - "normal" : number of whole pages transferred. I.e. they
3500 were not sent as duplicate or xbzrle pages (json-int)
3501 - "normal-bytes" : number of bytes transferred in whole
3502 pages. This is just normal pages times size of one page,
3503 but this way upper levels don't need to care about page
3504 size (json-int)
3505 - "dirty-sync-count": times that dirty ram was synchronized (json-int)
3506 - "disk": only present if "status" is "active" and it is a block migration,
3507 it is a json-object with the following disk information:
3508 - "transferred": amount transferred in bytes (json-int)
3509 - "remaining": amount remaining to transfer in bytes json-int)
3510 - "total": total disk size in bytes (json-int)
3511 - "xbzrle-cache": only present if XBZRLE is active.
3512 It is a json-object with the following XBZRLE information:
3513 - "cache-size": XBZRLE cache size in bytes
3514 - "bytes": number of bytes transferred for XBZRLE compressed pages
3515 - "pages": number of XBZRLE compressed pages
3516 - "cache-miss": number of XBRZRLE page cache misses
3517 - "cache-miss-rate": rate of XBRZRLE page cache misses
3518 - "overflow": number of times XBZRLE overflows. This means
3519 that the XBZRLE encoding was bigger than just sent the
3520 whole page, and then we sent the whole page instead (as as
3521 normal page).
3523 Examples:
3525 1. Before the first migration
3527 -> { "execute": "query-migrate" }
3528 <- { "return": {} }
3530 2. Migration is done and has succeeded
3532 -> { "execute": "query-migrate" }
3533 <- { "return": {
3534 "status": "completed",
3535 "ram":{
3536 "transferred":123,
3537 "remaining":123,
3538 "total":246,
3539 "total-time":12345,
3540 "setup-time":12345,
3541 "downtime":12345,
3542 "duplicate":123,
3543 "normal":123,
3544 "normal-bytes":123456,
3545 "dirty-sync-count":15
3550 3. Migration is done and has failed
3552 -> { "execute": "query-migrate" }
3553 <- { "return": { "status": "failed" } }
3555 4. Migration is being performed and is not a block migration:
3557 -> { "execute": "query-migrate" }
3558 <- {
3559 "return":{
3560 "status":"active",
3561 "ram":{
3562 "transferred":123,
3563 "remaining":123,
3564 "total":246,
3565 "total-time":12345,
3566 "setup-time":12345,
3567 "expected-downtime":12345,
3568 "duplicate":123,
3569 "normal":123,
3570 "normal-bytes":123456,
3571 "dirty-sync-count":15
3576 5. Migration is being performed and is a block migration:
3578 -> { "execute": "query-migrate" }
3579 <- {
3580 "return":{
3581 "status":"active",
3582 "ram":{
3583 "total":1057024,
3584 "remaining":1053304,
3585 "transferred":3720,
3586 "total-time":12345,
3587 "setup-time":12345,
3588 "expected-downtime":12345,
3589 "duplicate":123,
3590 "normal":123,
3591 "normal-bytes":123456,
3592 "dirty-sync-count":15
3594 "disk":{
3595 "total":20971520,
3596 "remaining":20880384,
3597 "transferred":91136
3602 6. Migration is being performed and XBZRLE is active:
3604 -> { "execute": "query-migrate" }
3605 <- {
3606 "return":{
3607 "status":"active",
3608 "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
3609 "ram":{
3610 "total":1057024,
3611 "remaining":1053304,
3612 "transferred":3720,
3613 "total-time":12345,
3614 "setup-time":12345,
3615 "expected-downtime":12345,
3616 "duplicate":10,
3617 "normal":3333,
3618 "normal-bytes":3412992,
3619 "dirty-sync-count":15
3621 "xbzrle-cache":{
3622 "cache-size":67108864,
3623 "bytes":20971520,
3624 "pages":2444343,
3625 "cache-miss":2244,
3626 "cache-miss-rate":0.123,
3627 "overflow":34434
3632 EQMP
3635 .name = "query-migrate",
3636 .args_type = "",
3637 .mhandler.cmd_new = qmp_marshal_query_migrate,
3640 SQMP
3641 migrate-set-capabilities
3642 ------------------------
3644 Enable/Disable migration capabilities
3646 - "xbzrle": XBZRLE support
3647 - "rdma-pin-all": pin all pages when using RDMA during migration
3648 - "auto-converge": throttle down guest to help convergence of migration
3649 - "zero-blocks": compress zero blocks during block migration
3650 - "compress": use multiple compression threads to accelerate live migration
3651 - "events": generate events for each migration state change
3652 - "x-postcopy-ram": postcopy mode for live migration
3654 Arguments:
3656 Example:
3658 -> { "execute": "migrate-set-capabilities" , "arguments":
3659 { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
3661 EQMP
3664 .name = "migrate-set-capabilities",
3665 .args_type = "capabilities:q",
3666 .params = "capability:s,state:b",
3667 .mhandler.cmd_new = qmp_marshal_migrate_set_capabilities,
3669 SQMP
3670 query-migrate-capabilities
3671 --------------------------
3673 Query current migration capabilities
3675 - "capabilities": migration capabilities state
3676 - "xbzrle" : XBZRLE state (json-bool)
3677 - "rdma-pin-all" : RDMA Pin Page state (json-bool)
3678 - "auto-converge" : Auto Converge state (json-bool)
3679 - "zero-blocks" : Zero Blocks state (json-bool)
3680 - "compress": Multiple compression threads state (json-bool)
3681 - "events": Migration state change event state (json-bool)
3682 - "x-postcopy-ram": postcopy ram state (json-bool)
3684 Arguments:
3686 Example:
3688 -> { "execute": "query-migrate-capabilities" }
3689 <- {"return": [
3690 {"state": false, "capability": "xbzrle"},
3691 {"state": false, "capability": "rdma-pin-all"},
3692 {"state": false, "capability": "auto-converge"},
3693 {"state": false, "capability": "zero-blocks"},
3694 {"state": false, "capability": "compress"},
3695 {"state": true, "capability": "events"},
3696 {"state": false, "capability": "x-postcopy-ram"}
3699 EQMP
3702 .name = "query-migrate-capabilities",
3703 .args_type = "",
3704 .mhandler.cmd_new = qmp_marshal_query_migrate_capabilities,
3707 SQMP
3708 migrate-set-parameters
3709 ----------------------
3711 Set migration parameters
3713 - "compress-level": set compression level during migration (json-int)
3714 - "compress-threads": set compression thread count for migration (json-int)
3715 - "decompress-threads": set decompression thread count for migration (json-int)
3716 - "x-cpu-throttle-initial": set initial percentage of time guest cpus are
3717 throttled for auto-converge (json-int)
3718 - "x-cpu-throttle-increment": set throttle increasing percentage for
3719 auto-converge (json-int)
3721 Arguments:
3723 Example:
3725 -> { "execute": "migrate-set-parameters" , "arguments":
3726 { "compress-level": 1 } }
3728 EQMP
3731 .name = "migrate-set-parameters",
3732 .args_type =
3733 "compress-level:i?,compress-threads:i?,decompress-threads:i?,x-cpu-throttle-initial:i?,x-cpu-throttle-increment:i?",
3734 .mhandler.cmd_new = qmp_marshal_migrate_set_parameters,
3736 SQMP
3737 query-migrate-parameters
3738 ------------------------
3740 Query current migration parameters
3742 - "parameters": migration parameters value
3743 - "compress-level" : compression level value (json-int)
3744 - "compress-threads" : compression thread count value (json-int)
3745 - "decompress-threads" : decompression thread count value (json-int)
3746 - "x-cpu-throttle-initial" : initial percentage of time guest cpus are
3747 throttled (json-int)
3748 - "x-cpu-throttle-increment" : throttle increasing percentage for
3749 auto-converge (json-int)
3751 Arguments:
3753 Example:
3755 -> { "execute": "query-migrate-parameters" }
3756 <- {
3757 "return": {
3758 "decompress-threads": 2,
3759 "x-cpu-throttle-increment": 10,
3760 "compress-threads": 8,
3761 "compress-level": 1,
3762 "x-cpu-throttle-initial": 20
3766 EQMP
3769 .name = "query-migrate-parameters",
3770 .args_type = "",
3771 .mhandler.cmd_new = qmp_marshal_query_migrate_parameters,
3774 SQMP
3775 query-balloon
3776 -------------
3778 Show balloon information.
3780 Make an asynchronous request for balloon info. When the request completes a
3781 json-object will be returned containing the following data:
3783 - "actual": current balloon value in bytes (json-int)
3785 Example:
3787 -> { "execute": "query-balloon" }
3788 <- {
3789 "return":{
3790 "actual":1073741824,
3794 EQMP
3797 .name = "query-balloon",
3798 .args_type = "",
3799 .mhandler.cmd_new = qmp_marshal_query_balloon,
3803 .name = "query-block-jobs",
3804 .args_type = "",
3805 .mhandler.cmd_new = qmp_marshal_query_block_jobs,
3809 .name = "qom-list",
3810 .args_type = "path:s",
3811 .mhandler.cmd_new = qmp_marshal_qom_list,
3815 .name = "qom-set",
3816 .args_type = "path:s,property:s,value:q",
3817 .mhandler.cmd_new = qmp_marshal_qom_set,
3821 .name = "qom-get",
3822 .args_type = "path:s,property:s",
3823 .mhandler.cmd_new = qmp_marshal_qom_get,
3827 .name = "nbd-server-start",
3828 .args_type = "addr:q,tls-creds:s?",
3829 .mhandler.cmd_new = qmp_marshal_nbd_server_start,
3832 .name = "nbd-server-add",
3833 .args_type = "device:B,writable:b?",
3834 .mhandler.cmd_new = qmp_marshal_nbd_server_add,
3837 .name = "nbd-server-stop",
3838 .args_type = "",
3839 .mhandler.cmd_new = qmp_marshal_nbd_server_stop,
3843 .name = "change-vnc-password",
3844 .args_type = "password:s",
3845 .mhandler.cmd_new = qmp_marshal_change_vnc_password,
3848 .name = "qom-list-types",
3849 .args_type = "implements:s?,abstract:b?",
3850 .mhandler.cmd_new = qmp_marshal_qom_list_types,
3854 .name = "device-list-properties",
3855 .args_type = "typename:s",
3856 .mhandler.cmd_new = qmp_marshal_device_list_properties,
3860 .name = "query-machines",
3861 .args_type = "",
3862 .mhandler.cmd_new = qmp_marshal_query_machines,
3866 .name = "query-cpu-definitions",
3867 .args_type = "",
3868 .mhandler.cmd_new = qmp_marshal_query_cpu_definitions,
3872 .name = "query-target",
3873 .args_type = "",
3874 .mhandler.cmd_new = qmp_marshal_query_target,
3878 .name = "query-tpm",
3879 .args_type = "",
3880 .mhandler.cmd_new = qmp_marshal_query_tpm,
3883 SQMP
3884 query-tpm
3885 ---------
3887 Return information about the TPM device.
3889 Arguments: None
3891 Example:
3893 -> { "execute": "query-tpm" }
3894 <- { "return":
3896 { "model": "tpm-tis",
3897 "options":
3898 { "type": "passthrough",
3899 "data":
3900 { "cancel-path": "/sys/class/misc/tpm0/device/cancel",
3901 "path": "/dev/tpm0"
3904 "id": "tpm0"
3909 EQMP
3912 .name = "query-tpm-models",
3913 .args_type = "",
3914 .mhandler.cmd_new = qmp_marshal_query_tpm_models,
3917 SQMP
3918 query-tpm-models
3919 ----------------
3921 Return a list of supported TPM models.
3923 Arguments: None
3925 Example:
3927 -> { "execute": "query-tpm-models" }
3928 <- { "return": [ "tpm-tis" ] }
3930 EQMP
3933 .name = "query-tpm-types",
3934 .args_type = "",
3935 .mhandler.cmd_new = qmp_marshal_query_tpm_types,
3938 SQMP
3939 query-tpm-types
3940 ---------------
3942 Return a list of supported TPM types.
3944 Arguments: None
3946 Example:
3948 -> { "execute": "query-tpm-types" }
3949 <- { "return": [ "passthrough" ] }
3951 EQMP
3954 .name = "chardev-add",
3955 .args_type = "id:s,backend:q",
3956 .mhandler.cmd_new = qmp_marshal_chardev_add,
3959 SQMP
3960 chardev-add
3961 ----------------
3963 Add a chardev.
3965 Arguments:
3967 - "id": the chardev's ID, must be unique (json-string)
3968 - "backend": chardev backend type + parameters
3970 Examples:
3972 -> { "execute" : "chardev-add",
3973 "arguments" : { "id" : "foo",
3974 "backend" : { "type" : "null", "data" : {} } } }
3975 <- { "return": {} }
3977 -> { "execute" : "chardev-add",
3978 "arguments" : { "id" : "bar",
3979 "backend" : { "type" : "file",
3980 "data" : { "out" : "/tmp/bar.log" } } } }
3981 <- { "return": {} }
3983 -> { "execute" : "chardev-add",
3984 "arguments" : { "id" : "baz",
3985 "backend" : { "type" : "pty", "data" : {} } } }
3986 <- { "return": { "pty" : "/dev/pty/42" } }
3988 EQMP
3991 .name = "chardev-remove",
3992 .args_type = "id:s",
3993 .mhandler.cmd_new = qmp_marshal_chardev_remove,
3997 SQMP
3998 chardev-remove
3999 --------------
4001 Remove a chardev.
4003 Arguments:
4005 - "id": the chardev's ID, must exist and not be in use (json-string)
4007 Example:
4009 -> { "execute": "chardev-remove", "arguments": { "id" : "foo" } }
4010 <- { "return": {} }
4012 EQMP
4014 .name = "query-rx-filter",
4015 .args_type = "name:s?",
4016 .mhandler.cmd_new = qmp_marshal_query_rx_filter,
4019 SQMP
4020 query-rx-filter
4021 ---------------
4023 Show rx-filter information.
4025 Returns a json-array of rx-filter information for all NICs (or for the
4026 given NIC), returning an error if the given NIC doesn't exist, or
4027 given NIC doesn't support rx-filter querying, or given net client
4028 isn't a NIC.
4030 The query will clear the event notification flag of each NIC, then qemu
4031 will start to emit event to QMP monitor.
4033 Each array entry contains the following:
4035 - "name": net client name (json-string)
4036 - "promiscuous": promiscuous mode is enabled (json-bool)
4037 - "multicast": multicast receive state (one of 'normal', 'none', 'all')
4038 - "unicast": unicast receive state (one of 'normal', 'none', 'all')
4039 - "vlan": vlan receive state (one of 'normal', 'none', 'all') (Since 2.0)
4040 - "broadcast-allowed": allow to receive broadcast (json-bool)
4041 - "multicast-overflow": multicast table is overflowed (json-bool)
4042 - "unicast-overflow": unicast table is overflowed (json-bool)
4043 - "main-mac": main macaddr string (json-string)
4044 - "vlan-table": a json-array of active vlan id
4045 - "unicast-table": a json-array of unicast macaddr string
4046 - "multicast-table": a json-array of multicast macaddr string
4048 Example:
4050 -> { "execute": "query-rx-filter", "arguments": { "name": "vnet0" } }
4051 <- { "return": [
4053 "promiscuous": true,
4054 "name": "vnet0",
4055 "main-mac": "52:54:00:12:34:56",
4056 "unicast": "normal",
4057 "vlan": "normal",
4058 "vlan-table": [
4062 "unicast-table": [
4064 "multicast": "normal",
4065 "multicast-overflow": false,
4066 "unicast-overflow": false,
4067 "multicast-table": [
4068 "01:00:5e:00:00:01",
4069 "33:33:00:00:00:01",
4070 "33:33:ff:12:34:56"
4072 "broadcast-allowed": false
4077 EQMP
4080 .name = "blockdev-add",
4081 .args_type = "options:q",
4082 .mhandler.cmd_new = qmp_marshal_blockdev_add,
4085 SQMP
4086 blockdev-add
4087 ------------
4089 Add a block device.
4091 This command is still a work in progress. It doesn't support all
4092 block drivers among other things. Stay away from it unless you want
4093 to help with its development.
4095 Arguments:
4097 - "options": block driver options
4099 Example (1):
4101 -> { "execute": "blockdev-add",
4102 "arguments": { "options" : { "driver": "qcow2",
4103 "file": { "driver": "file",
4104 "filename": "test.qcow2" } } } }
4105 <- { "return": {} }
4107 Example (2):
4109 -> { "execute": "blockdev-add",
4110 "arguments": {
4111 "options": {
4112 "driver": "qcow2",
4113 "id": "my_disk",
4114 "discard": "unmap",
4115 "cache": {
4116 "direct": true,
4117 "writeback": true
4119 "file": {
4120 "driver": "file",
4121 "filename": "/tmp/test.qcow2"
4123 "backing": {
4124 "driver": "raw",
4125 "file": {
4126 "driver": "file",
4127 "filename": "/dev/fdset/4"
4134 <- { "return": {} }
4136 EQMP
4139 .name = "x-blockdev-del",
4140 .args_type = "id:s?,node-name:s?",
4141 .mhandler.cmd_new = qmp_marshal_x_blockdev_del,
4144 SQMP
4145 x-blockdev-del
4146 ------------
4147 Since 2.5
4149 Deletes a block device thas has been added using blockdev-add.
4150 The selected device can be either a block backend or a graph node.
4152 In the former case the backend will be destroyed, along with its
4153 inserted medium if there's any. The command will fail if the backend
4154 or its medium are in use.
4156 In the latter case the node will be destroyed. The command will fail
4157 if the node is attached to a block backend or is otherwise being
4158 used.
4160 One of "id" or "node-name" must be specified, but not both.
4162 This command is still a work in progress and is considered
4163 experimental. Stay away from it unless you want to help with its
4164 development.
4166 Arguments:
4168 - "id": Name of the block backend device to delete (json-string, optional)
4169 - "node-name": Name of the graph node to delete (json-string, optional)
4171 Example:
4173 -> { "execute": "blockdev-add",
4174 "arguments": {
4175 "options": {
4176 "driver": "qcow2",
4177 "id": "drive0",
4178 "file": {
4179 "driver": "file",
4180 "filename": "test.qcow2"
4186 <- { "return": {} }
4188 -> { "execute": "x-blockdev-del",
4189 "arguments": { "id": "drive0" }
4191 <- { "return": {} }
4193 EQMP
4196 .name = "blockdev-open-tray",
4197 .args_type = "device:s,force:b?",
4198 .mhandler.cmd_new = qmp_marshal_blockdev_open_tray,
4201 SQMP
4202 blockdev-open-tray
4203 ------------------
4205 Opens a block device's tray. If there is a block driver state tree inserted as a
4206 medium, it will become inaccessible to the guest (but it will remain associated
4207 to the block device, so closing the tray will make it accessible again).
4209 If the tray was already open before, this will be a no-op.
4211 Once the tray opens, a DEVICE_TRAY_MOVED event is emitted. There are cases in
4212 which no such event will be generated, these include:
4213 - if the guest has locked the tray, @force is false and the guest does not
4214 respond to the eject request
4215 - if the BlockBackend denoted by @device does not have a guest device attached
4216 to it
4217 - if the guest device does not have an actual tray and is empty, for instance
4218 for floppy disk drives
4220 Arguments:
4222 - "device": block device name (json-string)
4223 - "force": if false (the default), an eject request will be sent to the guest if
4224 it has locked the tray (and the tray will not be opened immediately);
4225 if true, the tray will be opened regardless of whether it is locked
4226 (json-bool, optional)
4228 Example:
4230 -> { "execute": "blockdev-open-tray",
4231 "arguments": { "device": "ide1-cd0" } }
4233 <- { "timestamp": { "seconds": 1418751016,
4234 "microseconds": 716996 },
4235 "event": "DEVICE_TRAY_MOVED",
4236 "data": { "device": "ide1-cd0",
4237 "tray-open": true } }
4239 <- { "return": {} }
4241 EQMP
4244 .name = "blockdev-close-tray",
4245 .args_type = "device:s",
4246 .mhandler.cmd_new = qmp_marshal_blockdev_close_tray,
4249 SQMP
4250 blockdev-close-tray
4251 -------------------
4253 Closes a block device's tray. If there is a block driver state tree associated
4254 with the block device (which is currently ejected), that tree will be loaded as
4255 the medium.
4257 If the tray was already closed before, this will be a no-op.
4259 Arguments:
4261 - "device": block device name (json-string)
4263 Example:
4265 -> { "execute": "blockdev-close-tray",
4266 "arguments": { "device": "ide1-cd0" } }
4268 <- { "timestamp": { "seconds": 1418751345,
4269 "microseconds": 272147 },
4270 "event": "DEVICE_TRAY_MOVED",
4271 "data": { "device": "ide1-cd0",
4272 "tray-open": false } }
4274 <- { "return": {} }
4276 EQMP
4279 .name = "x-blockdev-remove-medium",
4280 .args_type = "device:s",
4281 .mhandler.cmd_new = qmp_marshal_x_blockdev_remove_medium,
4284 SQMP
4285 x-blockdev-remove-medium
4286 ------------------------
4288 Removes a medium (a block driver state tree) from a block device. That block
4289 device's tray must currently be open (unless there is no attached guest device).
4291 If the tray is open and there is no medium inserted, this will be a no-op.
4293 This command is still a work in progress and is considered experimental.
4294 Stay away from it unless you want to help with its development.
4296 Arguments:
4298 - "device": block device name (json-string)
4300 Example:
4302 -> { "execute": "x-blockdev-remove-medium",
4303 "arguments": { "device": "ide1-cd0" } }
4305 <- { "error": { "class": "GenericError",
4306 "desc": "Tray of device 'ide1-cd0' is not open" } }
4308 -> { "execute": "blockdev-open-tray",
4309 "arguments": { "device": "ide1-cd0" } }
4311 <- { "timestamp": { "seconds": 1418751627,
4312 "microseconds": 549958 },
4313 "event": "DEVICE_TRAY_MOVED",
4314 "data": { "device": "ide1-cd0",
4315 "tray-open": true } }
4317 <- { "return": {} }
4319 -> { "execute": "x-blockdev-remove-medium",
4320 "arguments": { "device": "ide1-cd0" } }
4322 <- { "return": {} }
4324 EQMP
4327 .name = "x-blockdev-insert-medium",
4328 .args_type = "device:s,node-name:s",
4329 .mhandler.cmd_new = qmp_marshal_x_blockdev_insert_medium,
4332 SQMP
4333 x-blockdev-insert-medium
4334 ------------------------
4336 Inserts a medium (a block driver state tree) into a block device. That block
4337 device's tray must currently be open (unless there is no attached guest device)
4338 and there must be no medium inserted already.
4340 This command is still a work in progress and is considered experimental.
4341 Stay away from it unless you want to help with its development.
4343 Arguments:
4345 - "device": block device name (json-string)
4346 - "node-name": root node of the BDS tree to insert into the block device
4348 Example:
4350 -> { "execute": "blockdev-add",
4351 "arguments": { "options": { "node-name": "node0",
4352 "driver": "raw",
4353 "file": { "driver": "file",
4354 "filename": "fedora.iso" } } } }
4356 <- { "return": {} }
4358 -> { "execute": "x-blockdev-insert-medium",
4359 "arguments": { "device": "ide1-cd0",
4360 "node-name": "node0" } }
4362 <- { "return": {} }
4364 EQMP
4367 .name = "query-named-block-nodes",
4368 .args_type = "",
4369 .mhandler.cmd_new = qmp_marshal_query_named_block_nodes,
4372 SQMP
4373 @query-named-block-nodes
4374 ------------------------
4376 Return a list of BlockDeviceInfo for all the named block driver nodes
4378 Example:
4380 -> { "execute": "query-named-block-nodes" }
4381 <- { "return": [ { "ro":false,
4382 "drv":"qcow2",
4383 "encrypted":false,
4384 "file":"disks/test.qcow2",
4385 "node-name": "my-node",
4386 "backing_file_depth":1,
4387 "bps":1000000,
4388 "bps_rd":0,
4389 "bps_wr":0,
4390 "iops":1000000,
4391 "iops_rd":0,
4392 "iops_wr":0,
4393 "bps_max": 8000000,
4394 "bps_rd_max": 0,
4395 "bps_wr_max": 0,
4396 "iops_max": 0,
4397 "iops_rd_max": 0,
4398 "iops_wr_max": 0,
4399 "iops_size": 0,
4400 "write_threshold": 0,
4401 "image":{
4402 "filename":"disks/test.qcow2",
4403 "format":"qcow2",
4404 "virtual-size":2048000,
4405 "backing_file":"base.qcow2",
4406 "full-backing-filename":"disks/base.qcow2",
4407 "backing-filename-format":"qcow2",
4408 "snapshots":[
4410 "id": "1",
4411 "name": "snapshot1",
4412 "vm-state-size": 0,
4413 "date-sec": 10000200,
4414 "date-nsec": 12,
4415 "vm-clock-sec": 206,
4416 "vm-clock-nsec": 30
4419 "backing-image":{
4420 "filename":"disks/base.qcow2",
4421 "format":"qcow2",
4422 "virtual-size":2048000
4424 } } ] }
4426 EQMP
4429 .name = "blockdev-change-medium",
4430 .args_type = "device:B,filename:F,format:s?,read-only-mode:s?",
4431 .mhandler.cmd_new = qmp_marshal_blockdev_change_medium,
4434 SQMP
4435 blockdev-change-medium
4436 ----------------------
4438 Changes the medium inserted into a block device by ejecting the current medium
4439 and loading a new image file which is inserted as the new medium.
4441 Arguments:
4443 - "device": device name (json-string)
4444 - "filename": filename of the new image (json-string)
4445 - "format": format of the new image (json-string, optional)
4446 - "read-only-mode": new read-only mode (json-string, optional)
4447 - Possible values: "retain" (default), "read-only", "read-write"
4449 Examples:
4451 1. Change a removable medium
4453 -> { "execute": "blockdev-change-medium",
4454 "arguments": { "device": "ide1-cd0",
4455 "filename": "/srv/images/Fedora-12-x86_64-DVD.iso",
4456 "format": "raw" } }
4457 <- { "return": {} }
4459 2. Load a read-only medium into a writable drive
4461 -> { "execute": "blockdev-change-medium",
4462 "arguments": { "device": "isa-fd0",
4463 "filename": "/srv/images/ro.img",
4464 "format": "raw",
4465 "read-only-mode": "retain" } }
4467 <- { "error":
4468 { "class": "GenericError",
4469 "desc": "Could not open '/srv/images/ro.img': Permission denied" } }
4471 -> { "execute": "blockdev-change-medium",
4472 "arguments": { "device": "isa-fd0",
4473 "filename": "/srv/images/ro.img",
4474 "format": "raw",
4475 "read-only-mode": "read-only" } }
4477 <- { "return": {} }
4479 EQMP
4482 .name = "query-memdev",
4483 .args_type = "",
4484 .mhandler.cmd_new = qmp_marshal_query_memdev,
4487 SQMP
4488 query-memdev
4489 ------------
4491 Show memory devices information.
4494 Example (1):
4496 -> { "execute": "query-memdev" }
4497 <- { "return": [
4499 "size": 536870912,
4500 "merge": false,
4501 "dump": true,
4502 "prealloc": false,
4503 "host-nodes": [0, 1],
4504 "policy": "bind"
4507 "size": 536870912,
4508 "merge": false,
4509 "dump": true,
4510 "prealloc": true,
4511 "host-nodes": [2, 3],
4512 "policy": "preferred"
4517 EQMP
4520 .name = "query-memory-devices",
4521 .args_type = "",
4522 .mhandler.cmd_new = qmp_marshal_query_memory_devices,
4525 SQMP
4526 @query-memory-devices
4527 --------------------
4529 Return a list of memory devices.
4531 Example:
4532 -> { "execute": "query-memory-devices" }
4533 <- { "return": [ { "data":
4534 { "addr": 5368709120,
4535 "hotpluggable": true,
4536 "hotplugged": true,
4537 "id": "d1",
4538 "memdev": "/objects/memX",
4539 "node": 0,
4540 "size": 1073741824,
4541 "slot": 0},
4542 "type": "dimm"
4543 } ] }
4544 EQMP
4547 .name = "query-acpi-ospm-status",
4548 .args_type = "",
4549 .mhandler.cmd_new = qmp_marshal_query_acpi_ospm_status,
4552 SQMP
4553 @query-acpi-ospm-status
4554 --------------------
4556 Return list of ACPIOSTInfo for devices that support status reporting
4557 via ACPI _OST method.
4559 Example:
4560 -> { "execute": "query-acpi-ospm-status" }
4561 <- { "return": [ { "device": "d1", "slot": "0", "slot-type": "DIMM", "source": 1, "status": 0},
4562 { "slot": "1", "slot-type": "DIMM", "source": 0, "status": 0},
4563 { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
4564 { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
4566 EQMP
4568 #if defined TARGET_I386
4570 .name = "rtc-reset-reinjection",
4571 .args_type = "",
4572 .mhandler.cmd_new = qmp_marshal_rtc_reset_reinjection,
4574 #endif
4576 SQMP
4577 rtc-reset-reinjection
4578 ---------------------
4580 Reset the RTC interrupt reinjection backlog.
4582 Arguments: None.
4584 Example:
4586 -> { "execute": "rtc-reset-reinjection" }
4587 <- { "return": {} }
4588 EQMP
4591 .name = "trace-event-get-state",
4592 .args_type = "name:s",
4593 .mhandler.cmd_new = qmp_marshal_trace_event_get_state,
4596 SQMP
4597 trace-event-get-state
4598 ---------------------
4600 Query the state of events.
4602 Example:
4604 -> { "execute": "trace-event-get-state", "arguments": { "name": "qemu_memalign" } }
4605 <- { "return": [ { "name": "qemu_memalign", "state": "disabled" } ] }
4606 EQMP
4609 .name = "trace-event-set-state",
4610 .args_type = "name:s,enable:b,ignore-unavailable:b?",
4611 .mhandler.cmd_new = qmp_marshal_trace_event_set_state,
4614 SQMP
4615 trace-event-set-state
4616 ---------------------
4618 Set the state of events.
4620 Example:
4622 -> { "execute": "trace-event-set-state", "arguments": { "name": "qemu_memalign", "enable": "true" } }
4623 <- { "return": {} }
4624 EQMP
4627 .name = "x-input-send-event",
4628 .args_type = "console:i?,events:q",
4629 .mhandler.cmd_new = qmp_marshal_x_input_send_event,
4632 SQMP
4633 @x-input-send-event
4634 -----------------
4636 Send input event to guest.
4638 Arguments:
4640 - "console": console index. (json-int, optional)
4641 - "events": list of input events.
4643 The consoles are visible in the qom tree, under
4644 /backend/console[$index]. They have a device link and head property, so
4645 it is possible to map which console belongs to which device and display.
4647 Note: this command is experimental, and not a stable API.
4649 Example (1):
4651 Press left mouse button.
4653 -> { "execute": "x-input-send-event",
4654 "arguments": { "console": 0,
4655 "events": [ { "type": "btn",
4656 "data" : { "down": true, "button": "Left" } } ] } }
4657 <- { "return": {} }
4659 -> { "execute": "x-input-send-event",
4660 "arguments": { "console": 0,
4661 "events": [ { "type": "btn",
4662 "data" : { "down": false, "button": "Left" } } ] } }
4663 <- { "return": {} }
4665 Example (2):
4667 Press ctrl-alt-del.
4669 -> { "execute": "x-input-send-event",
4670 "arguments": { "console": 0, "events": [
4671 { "type": "key", "data" : { "down": true,
4672 "key": {"type": "qcode", "data": "ctrl" } } },
4673 { "type": "key", "data" : { "down": true,
4674 "key": {"type": "qcode", "data": "alt" } } },
4675 { "type": "key", "data" : { "down": true,
4676 "key": {"type": "qcode", "data": "delete" } } } ] } }
4677 <- { "return": {} }
4679 Example (3):
4681 Move mouse pointer to absolute coordinates (20000, 400).
4683 -> { "execute": "x-input-send-event" ,
4684 "arguments": { "console": 0, "events": [
4685 { "type": "abs", "data" : { "axis": "X", "value" : 20000 } },
4686 { "type": "abs", "data" : { "axis": "Y", "value" : 400 } } ] } }
4687 <- { "return": {} }
4689 EQMP
4692 .name = "block-set-write-threshold",
4693 .args_type = "node-name:s,write-threshold:l",
4694 .mhandler.cmd_new = qmp_marshal_block_set_write_threshold,
4697 SQMP
4698 block-set-write-threshold
4699 ------------
4701 Change the write threshold for a block drive. The threshold is an offset,
4702 thus must be non-negative. Default is no write threshold.
4703 Setting the threshold to zero disables it.
4705 Arguments:
4707 - "node-name": the node name in the block driver state graph (json-string)
4708 - "write-threshold": the write threshold in bytes (json-int)
4710 Example:
4712 -> { "execute": "block-set-write-threshold",
4713 "arguments": { "node-name": "mydev",
4714 "write-threshold": 17179869184 } }
4715 <- { "return": {} }
4717 EQMP
4720 .name = "query-rocker",
4721 .args_type = "name:s",
4722 .mhandler.cmd_new = qmp_marshal_query_rocker,
4725 SQMP
4726 Show rocker switch
4727 ------------------
4729 Arguments:
4731 - "name": switch name
4733 Example:
4735 -> { "execute": "query-rocker", "arguments": { "name": "sw1" } }
4736 <- { "return": {"name": "sw1", "ports": 2, "id": 1327446905938}}
4738 EQMP
4741 .name = "query-rocker-ports",
4742 .args_type = "name:s",
4743 .mhandler.cmd_new = qmp_marshal_query_rocker_ports,
4746 SQMP
4747 Show rocker switch ports
4748 ------------------------
4750 Arguments:
4752 - "name": switch name
4754 Example:
4756 -> { "execute": "query-rocker-ports", "arguments": { "name": "sw1" } }
4757 <- { "return": [ {"duplex": "full", "enabled": true, "name": "sw1.1",
4758 "autoneg": "off", "link-up": true, "speed": 10000},
4759 {"duplex": "full", "enabled": true, "name": "sw1.2",
4760 "autoneg": "off", "link-up": true, "speed": 10000}
4763 EQMP
4766 .name = "query-rocker-of-dpa-flows",
4767 .args_type = "name:s,tbl-id:i?",
4768 .mhandler.cmd_new = qmp_marshal_query_rocker_of_dpa_flows,
4771 SQMP
4772 Show rocker switch OF-DPA flow tables
4773 -------------------------------------
4775 Arguments:
4777 - "name": switch name
4778 - "tbl-id": (optional) flow table ID
4780 Example:
4782 -> { "execute": "query-rocker-of-dpa-flows", "arguments": { "name": "sw1" } }
4783 <- { "return": [ {"key": {"in-pport": 0, "priority": 1, "tbl-id": 0},
4784 "hits": 138,
4785 "cookie": 0,
4786 "action": {"goto-tbl": 10},
4787 "mask": {"in-pport": 4294901760}
4789 {...more...},
4792 EQMP
4795 .name = "query-rocker-of-dpa-groups",
4796 .args_type = "name:s,type:i?",
4797 .mhandler.cmd_new = qmp_marshal_query_rocker_of_dpa_groups,
4800 SQMP
4801 Show rocker OF-DPA group tables
4802 -------------------------------
4804 Arguments:
4806 - "name": switch name
4807 - "type": (optional) group type
4809 Example:
4811 -> { "execute": "query-rocker-of-dpa-groups", "arguments": { "name": "sw1" } }
4812 <- { "return": [ {"type": 0, "out-pport": 2, "pport": 2, "vlan-id": 3841,
4813 "pop-vlan": 1, "id": 251723778},
4814 {"type": 0, "out-pport": 0, "pport": 0, "vlan-id": 3841,
4815 "pop-vlan": 1, "id": 251723776},
4816 {"type": 0, "out-pport": 1, "pport": 1, "vlan-id": 3840,
4817 "pop-vlan": 1, "id": 251658241},
4818 {"type": 0, "out-pport": 0, "pport": 0, "vlan-id": 3840,
4819 "pop-vlan": 1, "id": 251658240}