x86: switch to AREG0 free mode
[qemu/blueswirl.git] / qmp-commands.hx
blob2e1a38e6952122fbf5071e516cc650df5f7ef5c1
1 HXCOMM QMP dispatch table and documentation
2 HXCOMM Text between SQMP and EQMP is copied to the QMP documention file and
3 HXCOMM does not show up in the other formats.
5 SQMP
6 QMP Supported Commands
7 ----------------------
9 This document describes all commands currently supported by QMP.
11 Most of the time their usage is exactly the same as in the user Monitor, this
12 means that any other document which also describe commands (the manpage,
13 QEMU's manual, etc) can and should be consulted.
15 QMP has two types of commands: regular and query commands. Regular commands
16 usually change the Virtual Machine's state someway, while query commands just
17 return information. The sections below are divided accordingly.
19 It's important to observe that all communication examples are formatted in
20 a reader-friendly way, so that they're easier to understand. However, in real
21 protocol usage, they're emitted as a single line.
23 Also, the following notation is used to denote data flow:
25 -> data issued by the Client
26 <- Server data response
28 Please, refer to the QMP specification (QMP/qmp-spec.txt) for detailed
29 information on the Server command and response formats.
31 NOTE: This document is temporary and will be replaced soon.
33 1. Stability Considerations
34 ===========================
36 The current QMP command set (described in this file) may be useful for a
37 number of use cases, however it's limited and several commands have bad
38 defined semantics, specially with regard to command completion.
40 These problems are going to be solved incrementally in the next QEMU releases
41 and we're going to establish a deprecation policy for badly defined commands.
43 If you're planning to adopt QMP, please observe the following:
45 1. The deprecation policy will take effect and be documented soon, please
46 check the documentation of each used command as soon as a new release of
47 QEMU is available
49 2. DO NOT rely on anything which is not explicit documented
51 3. Errors, in special, are not documented. Applications should NOT check
52 for specific errors classes or data (it's strongly recommended to only
53 check for the "error" key)
55 2. Regular Commands
56 ===================
58 Server's responses in the examples below are always a success response, please
59 refer to the QMP specification for more details on error responses.
61 EQMP
64 .name = "quit",
65 .args_type = "",
66 .mhandler.cmd_new = qmp_marshal_input_quit,
69 SQMP
70 quit
71 ----
73 Quit the emulator.
75 Arguments: None.
77 Example:
79 -> { "execute": "quit" }
80 <- { "return": {} }
82 EQMP
85 .name = "eject",
86 .args_type = "force:-f,device:B",
87 .mhandler.cmd_new = qmp_marshal_input_eject,
90 SQMP
91 eject
92 -----
94 Eject a removable medium.
96 Arguments:
98 - force: force ejection (json-bool, optional)
99 - device: device name (json-string)
101 Example:
103 -> { "execute": "eject", "arguments": { "device": "ide1-cd0" } }
104 <- { "return": {} }
106 Note: The "force" argument defaults to false.
108 EQMP
111 .name = "change",
112 .args_type = "device:B,target:F,arg:s?",
113 .mhandler.cmd_new = qmp_marshal_input_change,
116 SQMP
117 change
118 ------
120 Change a removable medium or VNC configuration.
122 Arguments:
124 - "device": device name (json-string)
125 - "target": filename or item (json-string)
126 - "arg": additional argument (json-string, optional)
128 Examples:
130 1. Change a removable medium
132 -> { "execute": "change",
133 "arguments": { "device": "ide1-cd0",
134 "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } }
135 <- { "return": {} }
137 2. Change VNC password
139 -> { "execute": "change",
140 "arguments": { "device": "vnc", "target": "password",
141 "arg": "foobar1" } }
142 <- { "return": {} }
144 EQMP
147 .name = "screendump",
148 .args_type = "filename:F",
149 .params = "filename",
150 .help = "save screen into PPM image 'filename'",
151 .user_print = monitor_user_noop,
152 .mhandler.cmd_new = do_screen_dump,
155 SQMP
156 screendump
157 ----------
159 Save screen into PPM image.
161 Arguments:
163 - "filename": file path (json-string)
165 Example:
167 -> { "execute": "screendump", "arguments": { "filename": "/tmp/image" } }
168 <- { "return": {} }
170 EQMP
173 .name = "stop",
174 .args_type = "",
175 .mhandler.cmd_new = qmp_marshal_input_stop,
178 SQMP
179 stop
180 ----
182 Stop the emulator.
184 Arguments: None.
186 Example:
188 -> { "execute": "stop" }
189 <- { "return": {} }
191 EQMP
194 .name = "cont",
195 .args_type = "",
196 .mhandler.cmd_new = qmp_marshal_input_cont,
199 SQMP
200 cont
201 ----
203 Resume emulation.
205 Arguments: None.
207 Example:
209 -> { "execute": "cont" }
210 <- { "return": {} }
212 EQMP
215 .name = "system_wakeup",
216 .args_type = "",
217 .mhandler.cmd_new = qmp_marshal_input_system_wakeup,
220 SQMP
221 system_wakeup
222 -------------
224 Wakeup guest from suspend.
226 Arguments: None.
228 Example:
230 -> { "execute": "system_wakeup" }
231 <- { "return": {} }
233 EQMP
236 .name = "system_reset",
237 .args_type = "",
238 .mhandler.cmd_new = qmp_marshal_input_system_reset,
241 SQMP
242 system_reset
243 ------------
245 Reset the system.
247 Arguments: None.
249 Example:
251 -> { "execute": "system_reset" }
252 <- { "return": {} }
254 EQMP
257 .name = "system_powerdown",
258 .args_type = "",
259 .mhandler.cmd_new = qmp_marshal_input_system_powerdown,
262 SQMP
263 system_powerdown
264 ----------------
266 Send system power down event.
268 Arguments: None.
270 Example:
272 -> { "execute": "system_powerdown" }
273 <- { "return": {} }
275 EQMP
278 .name = "device_add",
279 .args_type = "device:O",
280 .params = "driver[,prop=value][,...]",
281 .help = "add device, like -device on the command line",
282 .user_print = monitor_user_noop,
283 .mhandler.cmd_new = do_device_add,
286 SQMP
287 device_add
288 ----------
290 Add a device.
292 Arguments:
294 - "driver": the name of the new device's driver (json-string)
295 - "bus": the device's parent bus (device tree path, json-string, optional)
296 - "id": the device's ID, must be unique (json-string)
297 - device properties
299 Example:
301 -> { "execute": "device_add", "arguments": { "driver": "e1000", "id": "net1" } }
302 <- { "return": {} }
304 Notes:
306 (1) For detailed information about this command, please refer to the
307 'docs/qdev-device-use.txt' file.
309 (2) It's possible to list device properties by running QEMU with the
310 "-device DEVICE,\?" command-line argument, where DEVICE is the device's name
312 EQMP
315 .name = "device_del",
316 .args_type = "id:s",
317 .mhandler.cmd_new = qmp_marshal_input_device_del,
320 SQMP
321 device_del
322 ----------
324 Remove a device.
326 Arguments:
328 - "id": the device's ID (json-string)
330 Example:
332 -> { "execute": "device_del", "arguments": { "id": "net1" } }
333 <- { "return": {} }
335 EQMP
338 .name = "cpu",
339 .args_type = "index:i",
340 .mhandler.cmd_new = qmp_marshal_input_cpu,
343 SQMP
347 Set the default CPU.
349 Arguments:
351 - "index": the CPU's index (json-int)
353 Example:
355 -> { "execute": "cpu", "arguments": { "index": 0 } }
356 <- { "return": {} }
358 Note: CPUs' indexes are obtained with the 'query-cpus' command.
360 EQMP
363 .name = "memsave",
364 .args_type = "val:l,size:i,filename:s,cpu:i?",
365 .mhandler.cmd_new = qmp_marshal_input_memsave,
368 SQMP
369 memsave
370 -------
372 Save to disk virtual memory dump starting at 'val' of size 'size'.
374 Arguments:
376 - "val": the starting address (json-int)
377 - "size": the memory size, in bytes (json-int)
378 - "filename": file path (json-string)
379 - "cpu": virtual CPU index (json-int, optional)
381 Example:
383 -> { "execute": "memsave",
384 "arguments": { "val": 10,
385 "size": 100,
386 "filename": "/tmp/virtual-mem-dump" } }
387 <- { "return": {} }
389 EQMP
392 .name = "pmemsave",
393 .args_type = "val:l,size:i,filename:s",
394 .mhandler.cmd_new = qmp_marshal_input_pmemsave,
397 SQMP
398 pmemsave
399 --------
401 Save to disk physical memory dump starting at 'val' of size 'size'.
403 Arguments:
405 - "val": the starting address (json-int)
406 - "size": the memory size, in bytes (json-int)
407 - "filename": file path (json-string)
409 Example:
411 -> { "execute": "pmemsave",
412 "arguments": { "val": 10,
413 "size": 100,
414 "filename": "/tmp/physical-mem-dump" } }
415 <- { "return": {} }
417 EQMP
420 .name = "inject-nmi",
421 .args_type = "",
422 .mhandler.cmd_new = qmp_marshal_input_inject_nmi,
425 SQMP
426 inject-nmi
427 ----------
429 Inject an NMI on guest's CPUs.
431 Arguments: None.
433 Example:
435 -> { "execute": "inject-nmi" }
436 <- { "return": {} }
438 Note: inject-nmi is only supported for x86 guest currently, it will
439 returns "Unsupported" error for non-x86 guest.
441 EQMP
444 .name = "xen-save-devices-state",
445 .args_type = "filename:F",
446 .mhandler.cmd_new = qmp_marshal_input_xen_save_devices_state,
449 SQMP
450 xen-save-devices-state
451 -------
453 Save the state of all devices to file. The RAM and the block devices
454 of the VM are not saved by this command.
456 Arguments:
458 - "filename": the file to save the state of the devices to as binary
459 data. See xen-save-devices-state.txt for a description of the binary
460 format.
462 Example:
464 -> { "execute": "xen-save-devices-state",
465 "arguments": { "filename": "/tmp/save" } }
466 <- { "return": {} }
468 EQMP
471 .name = "migrate",
472 .args_type = "detach:-d,blk:-b,inc:-i,uri:s",
473 .mhandler.cmd_new = qmp_marshal_input_migrate,
476 SQMP
477 migrate
478 -------
480 Migrate to URI.
482 Arguments:
484 - "blk": block migration, full disk copy (json-bool, optional)
485 - "inc": incremental disk copy (json-bool, optional)
486 - "uri": Destination URI (json-string)
488 Example:
490 -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
491 <- { "return": {} }
493 Notes:
495 (1) The 'query-migrate' command should be used to check migration's progress
496 and final result (this information is provided by the 'status' member)
497 (2) All boolean arguments default to false
498 (3) The user Monitor's "detach" argument is invalid in QMP and should not
499 be used
501 EQMP
504 .name = "migrate_cancel",
505 .args_type = "",
506 .mhandler.cmd_new = qmp_marshal_input_migrate_cancel,
509 SQMP
510 migrate_cancel
511 --------------
513 Cancel the current migration.
515 Arguments: None.
517 Example:
519 -> { "execute": "migrate_cancel" }
520 <- { "return": {} }
522 EQMP
525 .name = "migrate_set_speed",
526 .args_type = "value:o",
527 .mhandler.cmd_new = qmp_marshal_input_migrate_set_speed,
530 SQMP
531 migrate_set_speed
532 -----------------
534 Set maximum speed for migrations.
536 Arguments:
538 - "value": maximum speed, in bytes per second (json-int)
540 Example:
542 -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
543 <- { "return": {} }
545 EQMP
548 .name = "migrate_set_downtime",
549 .args_type = "value:T",
550 .mhandler.cmd_new = qmp_marshal_input_migrate_set_downtime,
553 SQMP
554 migrate_set_downtime
555 --------------------
557 Set maximum tolerated downtime (in seconds) for migrations.
559 Arguments:
561 - "value": maximum downtime (json-number)
563 Example:
565 -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
566 <- { "return": {} }
568 EQMP
571 .name = "client_migrate_info",
572 .args_type = "protocol:s,hostname:s,port:i?,tls-port:i?,cert-subject:s?",
573 .params = "protocol hostname port tls-port cert-subject",
574 .help = "send migration info to spice/vnc client",
575 .user_print = monitor_user_noop,
576 .mhandler.cmd_async = client_migrate_info,
577 .flags = MONITOR_CMD_ASYNC,
580 SQMP
581 client_migrate_info
582 ------------------
584 Set the spice/vnc connection info for the migration target. The spice/vnc
585 server will ask the spice/vnc client to automatically reconnect using the
586 new parameters (if specified) once the vm migration finished successfully.
588 Arguments:
590 - "protocol": protocol: "spice" or "vnc" (json-string)
591 - "hostname": migration target hostname (json-string)
592 - "port": spice/vnc tcp port for plaintext channels (json-int, optional)
593 - "tls-port": spice tcp port for tls-secured channels (json-int, optional)
594 - "cert-subject": server certificate subject (json-string, optional)
596 Example:
598 -> { "execute": "client_migrate_info",
599 "arguments": { "protocol": "spice",
600 "hostname": "virt42.lab.kraxel.org",
601 "port": 1234 } }
602 <- { "return": {} }
604 EQMP
607 .name = "dump-guest-memory",
608 .args_type = "paging:b,protocol:s,begin:i?,end:i?",
609 .params = "-p protocol [begin] [length]",
610 .help = "dump guest memory to file",
611 .user_print = monitor_user_noop,
612 .mhandler.cmd_new = qmp_marshal_input_dump_guest_memory,
615 SQMP
616 dump
619 Dump guest memory to file. The file can be processed with crash or gdb.
621 Arguments:
623 - "paging": do paging to get guest's memory mapping (json-bool)
624 - "protocol": destination file(started with "file:") or destination file
625 descriptor (started with "fd:") (json-string)
626 - "begin": the starting physical address. It's optional, and should be specified
627 with length together (json-int)
628 - "length": the memory size, in bytes. It's optional, and should be specified
629 with begin together (json-int)
631 Example:
633 -> { "execute": "dump-guest-memory", "arguments": { "protocol": "fd:dump" } }
634 <- { "return": {} }
636 Notes:
638 (1) All boolean arguments default to false
640 EQMP
643 .name = "netdev_add",
644 .args_type = "netdev:O",
645 .mhandler.cmd_new = qmp_netdev_add,
648 SQMP
649 netdev_add
650 ----------
652 Add host network device.
654 Arguments:
656 - "type": the device type, "tap", "user", ... (json-string)
657 - "id": the device's ID, must be unique (json-string)
658 - device options
660 Example:
662 -> { "execute": "netdev_add", "arguments": { "type": "user", "id": "netdev1" } }
663 <- { "return": {} }
665 Note: The supported device options are the same ones supported by the '-net'
666 command-line argument, which are listed in the '-help' output or QEMU's
667 manual
669 EQMP
672 .name = "netdev_del",
673 .args_type = "id:s",
674 .mhandler.cmd_new = qmp_marshal_input_netdev_del,
677 SQMP
678 netdev_del
679 ----------
681 Remove host network device.
683 Arguments:
685 - "id": the device's ID, must be unique (json-string)
687 Example:
689 -> { "execute": "netdev_del", "arguments": { "id": "netdev1" } }
690 <- { "return": {} }
693 EQMP
696 .name = "block_resize",
697 .args_type = "device:B,size:o",
698 .mhandler.cmd_new = qmp_marshal_input_block_resize,
701 SQMP
702 block_resize
703 ------------
705 Resize a block image while a guest is running.
707 Arguments:
709 - "device": the device's ID, must be unique (json-string)
710 - "size": new size
712 Example:
714 -> { "execute": "block_resize", "arguments": { "device": "scratch", "size": 1073741824 } }
715 <- { "return": {} }
717 EQMP
720 .name = "block-stream",
721 .args_type = "device:B,base:s?,speed:o?",
722 .mhandler.cmd_new = qmp_marshal_input_block_stream,
726 .name = "block-job-set-speed",
727 .args_type = "device:B,speed:o",
728 .mhandler.cmd_new = qmp_marshal_input_block_job_set_speed,
732 .name = "block-job-cancel",
733 .args_type = "device:B",
734 .mhandler.cmd_new = qmp_marshal_input_block_job_cancel,
737 .name = "transaction",
738 .args_type = "actions:q",
739 .mhandler.cmd_new = qmp_marshal_input_transaction,
742 SQMP
743 transaction
744 -----------
746 Atomically operate on one or more block devices. The only supported
747 operation for now is snapshotting. If there is any failure performing
748 any of the operations, all snapshots for the group are abandoned, and
749 the original disks pre-snapshot attempt are used.
751 A list of dictionaries is accepted, that contains the actions to be performed.
752 For snapshots this is the device, the file to use for the new snapshot,
753 and the format. The default format, if not specified, is qcow2.
755 Each new snapshot defaults to being created by QEMU (wiping any
756 contents if the file already exists), but it is also possible to reuse
757 an externally-created file. In the latter case, you should ensure that
758 the new image file has the same contents as the current one; QEMU cannot
759 perform any meaningful check. Typically this is achieved by using the
760 current image file as the backing file for the new image.
762 Arguments:
764 actions array:
765 - "type": the operation to perform. The only supported
766 value is "blockdev-snapshot-sync". (json-string)
767 - "data": a dictionary. The contents depend on the value
768 of "type". When "type" is "blockdev-snapshot-sync":
769 - "device": device name to snapshot (json-string)
770 - "snapshot-file": name of new image file (json-string)
771 - "format": format of new image (json-string, optional)
772 - "mode": whether and how QEMU should create the snapshot file
773 (NewImageMode, optional, default "absolute-paths")
775 Example:
777 -> { "execute": "transaction",
778 "arguments": { "actions": [
779 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd0",
780 "snapshot-file": "/some/place/my-image",
781 "format": "qcow2" } },
782 { 'type': 'blockdev-snapshot-sync', 'data' : { "device": "ide-hd1",
783 "snapshot-file": "/some/place/my-image2",
784 "mode": "existing",
785 "format": "qcow2" } } ] } }
786 <- { "return": {} }
788 EQMP
791 .name = "blockdev-snapshot-sync",
792 .args_type = "device:B,snapshot-file:s,format:s?,mode:s?",
793 .mhandler.cmd_new = qmp_marshal_input_blockdev_snapshot_sync,
796 SQMP
797 blockdev-snapshot-sync
798 ----------------------
800 Synchronous snapshot of a block device. snapshot-file specifies the
801 target of the new image. If the file exists, or if it is a device, the
802 snapshot will be created in the existing file/device. If does not
803 exist, a new file will be created. format specifies the format of the
804 snapshot image, default is qcow2.
806 Arguments:
808 - "device": device name to snapshot (json-string)
809 - "snapshot-file": name of new image file (json-string)
810 - "mode": whether and how QEMU should create the snapshot file
811 (NewImageMode, optional, default "absolute-paths")
812 - "format": format of new image (json-string, optional)
814 Example:
816 -> { "execute": "blockdev-snapshot-sync", "arguments": { "device": "ide-hd0",
817 "snapshot-file":
818 "/some/place/my-image",
819 "format": "qcow2" } }
820 <- { "return": {} }
822 EQMP
825 .name = "balloon",
826 .args_type = "value:M",
827 .mhandler.cmd_new = qmp_marshal_input_balloon,
830 SQMP
831 balloon
832 -------
834 Request VM to change its memory allocation (in bytes).
836 Arguments:
838 - "value": New memory allocation (json-int)
840 Example:
842 -> { "execute": "balloon", "arguments": { "value": 536870912 } }
843 <- { "return": {} }
845 EQMP
848 .name = "set_link",
849 .args_type = "name:s,up:b",
850 .mhandler.cmd_new = qmp_marshal_input_set_link,
853 SQMP
854 set_link
855 --------
857 Change the link status of a network adapter.
859 Arguments:
861 - "name": network device name (json-string)
862 - "up": status is up (json-bool)
864 Example:
866 -> { "execute": "set_link", "arguments": { "name": "e1000.0", "up": false } }
867 <- { "return": {} }
869 EQMP
872 .name = "getfd",
873 .args_type = "fdname:s",
874 .params = "getfd name",
875 .help = "receive a file descriptor via SCM rights and assign it a name",
876 .user_print = monitor_user_noop,
877 .mhandler.cmd_new = do_getfd,
880 SQMP
881 getfd
882 -----
884 Receive a file descriptor via SCM rights and assign it a name.
886 Arguments:
888 - "fdname": file descriptor name (json-string)
890 Example:
892 -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
893 <- { "return": {} }
895 EQMP
898 .name = "closefd",
899 .args_type = "fdname:s",
900 .params = "closefd name",
901 .help = "close a file descriptor previously passed via SCM rights",
902 .user_print = monitor_user_noop,
903 .mhandler.cmd_new = do_closefd,
906 SQMP
907 closefd
908 -------
910 Close a file descriptor previously passed via SCM rights.
912 Arguments:
914 - "fdname": file descriptor name (json-string)
916 Example:
918 -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
919 <- { "return": {} }
921 EQMP
924 .name = "block_passwd",
925 .args_type = "device:B,password:s",
926 .mhandler.cmd_new = qmp_marshal_input_block_passwd,
929 SQMP
930 block_passwd
931 ------------
933 Set the password of encrypted block devices.
935 Arguments:
937 - "device": device name (json-string)
938 - "password": password (json-string)
940 Example:
942 -> { "execute": "block_passwd", "arguments": { "device": "ide0-hd0",
943 "password": "12345" } }
944 <- { "return": {} }
946 EQMP
949 .name = "block_set_io_throttle",
950 .args_type = "device:B,bps:l,bps_rd:l,bps_wr:l,iops:l,iops_rd:l,iops_wr:l",
951 .mhandler.cmd_new = qmp_marshal_input_block_set_io_throttle,
954 SQMP
955 block_set_io_throttle
956 ------------
958 Change I/O throttle limits for a block drive.
960 Arguments:
962 - "device": device name (json-string)
963 - "bps": total throughput limit in bytes per second(json-int)
964 - "bps_rd": read throughput limit in bytes per second(json-int)
965 - "bps_wr": read throughput limit in bytes per second(json-int)
966 - "iops": total I/O operations per second(json-int)
967 - "iops_rd": read I/O operations per second(json-int)
968 - "iops_wr": write I/O operations per second(json-int)
970 Example:
972 -> { "execute": "block_set_io_throttle", "arguments": { "device": "virtio0",
973 "bps": "1000000",
974 "bps_rd": "0",
975 "bps_wr": "0",
976 "iops": "0",
977 "iops_rd": "0",
978 "iops_wr": "0" } }
979 <- { "return": {} }
981 EQMP
984 .name = "set_password",
985 .args_type = "protocol:s,password:s,connected:s?",
986 .mhandler.cmd_new = qmp_marshal_input_set_password,
989 SQMP
990 set_password
991 ------------
993 Set the password for vnc/spice protocols.
995 Arguments:
997 - "protocol": protocol name (json-string)
998 - "password": password (json-string)
999 - "connected": [ keep | disconnect | fail ] (josn-string, optional)
1001 Example:
1003 -> { "execute": "set_password", "arguments": { "protocol": "vnc",
1004 "password": "secret" } }
1005 <- { "return": {} }
1007 EQMP
1010 .name = "expire_password",
1011 .args_type = "protocol:s,time:s",
1012 .mhandler.cmd_new = qmp_marshal_input_expire_password,
1015 SQMP
1016 expire_password
1017 ---------------
1019 Set the password expire time for vnc/spice protocols.
1021 Arguments:
1023 - "protocol": protocol name (json-string)
1024 - "time": [ now | never | +secs | secs ] (json-string)
1026 Example:
1028 -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
1029 "time": "+60" } }
1030 <- { "return": {} }
1032 EQMP
1035 .name = "add_client",
1036 .args_type = "protocol:s,fdname:s,skipauth:b?,tls:b?",
1037 .params = "protocol fdname skipauth tls",
1038 .help = "add a graphics client",
1039 .user_print = monitor_user_noop,
1040 .mhandler.cmd_new = add_graphics_client,
1043 SQMP
1044 add_client
1045 ----------
1047 Add a graphics client
1049 Arguments:
1051 - "protocol": protocol name (json-string)
1052 - "fdname": file descriptor name (json-string)
1053 - "skipauth": whether to skip authentication (json-bool, optional)
1054 - "tls": whether to perform TLS (json-bool, optional)
1056 Example:
1058 -> { "execute": "add_client", "arguments": { "protocol": "vnc",
1059 "fdname": "myclient" } }
1060 <- { "return": {} }
1062 EQMP
1064 .name = "qmp_capabilities",
1065 .args_type = "",
1066 .params = "",
1067 .help = "enable QMP capabilities",
1068 .user_print = monitor_user_noop,
1069 .mhandler.cmd_new = do_qmp_capabilities,
1072 SQMP
1073 qmp_capabilities
1074 ----------------
1076 Enable QMP capabilities.
1078 Arguments: None.
1080 Example:
1082 -> { "execute": "qmp_capabilities" }
1083 <- { "return": {} }
1085 Note: This command must be issued before issuing any other command.
1087 EQMP
1090 .name = "human-monitor-command",
1091 .args_type = "command-line:s,cpu-index:i?",
1092 .mhandler.cmd_new = qmp_marshal_input_human_monitor_command,
1095 SQMP
1096 human-monitor-command
1097 ---------------------
1099 Execute a Human Monitor command.
1101 Arguments:
1103 - command-line: the command name and its arguments, just like the
1104 Human Monitor's shell (json-string)
1105 - cpu-index: select the CPU number to be used by commands which access CPU
1106 data, like 'info registers'. The Monitor selects CPU 0 if this
1107 argument is not provided (json-int, optional)
1109 Example:
1111 -> { "execute": "human-monitor-command", "arguments": { "command-line": "info kvm" } }
1112 <- { "return": "kvm support: enabled\r\n" }
1114 Notes:
1116 (1) The Human Monitor is NOT an stable interface, this means that command
1117 names, arguments and responses can change or be removed at ANY time.
1118 Applications that rely on long term stability guarantees should NOT
1119 use this command
1121 (2) Limitations:
1123 o This command is stateless, this means that commands that depend
1124 on state information (such as getfd) might not work
1126 o Commands that prompt the user for data (eg. 'cont' when the block
1127 device is encrypted) don't currently work
1129 3. Query Commands
1130 =================
1132 HXCOMM Each query command below is inside a SQMP/EQMP section, do NOT change
1133 HXCOMM this! We will possibly move query commands definitions inside those
1134 HXCOMM sections, just like regular commands.
1136 EQMP
1138 SQMP
1139 query-version
1140 -------------
1142 Show QEMU version.
1144 Return a json-object with the following information:
1146 - "qemu": A json-object containing three integer values:
1147 - "major": QEMU's major version (json-int)
1148 - "minor": QEMU's minor version (json-int)
1149 - "micro": QEMU's micro version (json-int)
1150 - "package": package's version (json-string)
1152 Example:
1154 -> { "execute": "query-version" }
1155 <- {
1156 "return":{
1157 "qemu":{
1158 "major":0,
1159 "minor":11,
1160 "micro":5
1162 "package":""
1166 EQMP
1169 .name = "query-version",
1170 .args_type = "",
1171 .mhandler.cmd_new = qmp_marshal_input_query_version,
1174 SQMP
1175 query-commands
1176 --------------
1178 List QMP available commands.
1180 Each command is represented by a json-object, the returned value is a json-array
1181 of all commands.
1183 Each json-object contain:
1185 - "name": command's name (json-string)
1187 Example:
1189 -> { "execute": "query-commands" }
1190 <- {
1191 "return":[
1193 "name":"query-balloon"
1196 "name":"system_powerdown"
1201 Note: This example has been shortened as the real response is too long.
1203 EQMP
1206 .name = "query-commands",
1207 .args_type = "",
1208 .mhandler.cmd_new = qmp_marshal_input_query_commands,
1211 SQMP
1212 query-events
1213 --------------
1215 List QMP available events.
1217 Each event is represented by a json-object, the returned value is a json-array
1218 of all events.
1220 Each json-object contains:
1222 - "name": event's name (json-string)
1224 Example:
1226 -> { "execute": "query-events" }
1227 <- {
1228 "return":[
1230 "name":"SHUTDOWN"
1233 "name":"RESET"
1238 Note: This example has been shortened as the real response is too long.
1240 EQMP
1243 .name = "query-events",
1244 .args_type = "",
1245 .mhandler.cmd_new = qmp_marshal_input_query_events,
1248 SQMP
1249 query-chardev
1250 -------------
1252 Each device is represented by a json-object. The returned value is a json-array
1253 of all devices.
1255 Each json-object contain the following:
1257 - "label": device's label (json-string)
1258 - "filename": device's file (json-string)
1260 Example:
1262 -> { "execute": "query-chardev" }
1263 <- {
1264 "return":[
1266 "label":"monitor",
1267 "filename":"stdio"
1270 "label":"serial0",
1271 "filename":"vc"
1276 EQMP
1279 .name = "query-chardev",
1280 .args_type = "",
1281 .mhandler.cmd_new = qmp_marshal_input_query_chardev,
1284 SQMP
1285 query-block
1286 -----------
1288 Show the block devices.
1290 Each block device information is stored in a json-object and the returned value
1291 is a json-array of all devices.
1293 Each json-object contain the following:
1295 - "device": device name (json-string)
1296 - "type": device type (json-string)
1297 - deprecated, retained for backward compatibility
1298 - Possible values: "unknown"
1299 - "removable": true if the device is removable, false otherwise (json-bool)
1300 - "locked": true if the device is locked, false otherwise (json-bool)
1301 - "tray-open": only present if removable, true if the device has a tray,
1302 and it is open (json-bool)
1303 - "inserted": only present if the device is inserted, it is a json-object
1304 containing the following:
1305 - "file": device file name (json-string)
1306 - "ro": true if read-only, false otherwise (json-bool)
1307 - "drv": driver format name (json-string)
1308 - Possible values: "blkdebug", "bochs", "cloop", "cow", "dmg",
1309 "file", "file", "ftp", "ftps", "host_cdrom",
1310 "host_device", "host_floppy", "http", "https",
1311 "nbd", "parallels", "qcow", "qcow2", "raw",
1312 "tftp", "vdi", "vmdk", "vpc", "vvfat"
1313 - "backing_file": backing file name (json-string, optional)
1314 - "encrypted": true if encrypted, false otherwise (json-bool)
1315 - "bps": limit total bytes per second (json-int)
1316 - "bps_rd": limit read bytes per second (json-int)
1317 - "bps_wr": limit write bytes per second (json-int)
1318 - "iops": limit total I/O operations per second (json-int)
1319 - "iops_rd": limit read operations per second (json-int)
1320 - "iops_wr": limit write operations per second (json-int)
1322 - "io-status": I/O operation status, only present if the device supports it
1323 and the VM is configured to stop on errors. It's always reset
1324 to "ok" when the "cont" command is issued (json_string, optional)
1325 - Possible values: "ok", "failed", "nospace"
1327 Example:
1329 -> { "execute": "query-block" }
1330 <- {
1331 "return":[
1333 "io-status": "ok",
1334 "device":"ide0-hd0",
1335 "locked":false,
1336 "removable":false,
1337 "inserted":{
1338 "ro":false,
1339 "drv":"qcow2",
1340 "encrypted":false,
1341 "file":"disks/test.img",
1342 "bps":1000000,
1343 "bps_rd":0,
1344 "bps_wr":0,
1345 "iops":1000000,
1346 "iops_rd":0,
1347 "iops_wr":0,
1349 "type":"unknown"
1352 "io-status": "ok",
1353 "device":"ide1-cd0",
1354 "locked":false,
1355 "removable":true,
1356 "type":"unknown"
1359 "device":"floppy0",
1360 "locked":false,
1361 "removable":true,
1362 "type":"unknown"
1365 "device":"sd0",
1366 "locked":false,
1367 "removable":true,
1368 "type":"unknown"
1373 EQMP
1376 .name = "query-block",
1377 .args_type = "",
1378 .mhandler.cmd_new = qmp_marshal_input_query_block,
1381 SQMP
1382 query-blockstats
1383 ----------------
1385 Show block device statistics.
1387 Each device statistic information is stored in a json-object and the returned
1388 value is a json-array of all devices.
1390 Each json-object contain the following:
1392 - "device": device name (json-string)
1393 - "stats": A json-object with the statistics information, it contains:
1394 - "rd_bytes": bytes read (json-int)
1395 - "wr_bytes": bytes written (json-int)
1396 - "rd_operations": read operations (json-int)
1397 - "wr_operations": write operations (json-int)
1398 - "flush_operations": cache flush operations (json-int)
1399 - "wr_total_time_ns": total time spend on writes in nano-seconds (json-int)
1400 - "rd_total_time_ns": total time spend on reads in nano-seconds (json-int)
1401 - "flush_total_time_ns": total time spend on cache flushes in nano-seconds (json-int)
1402 - "wr_highest_offset": Highest offset of a sector written since the
1403 BlockDriverState has been opened (json-int)
1404 - "parent": Contains recursively the statistics of the underlying
1405 protocol (e.g. the host file for a qcow2 image). If there is
1406 no underlying protocol, this field is omitted
1407 (json-object, optional)
1409 Example:
1411 -> { "execute": "query-blockstats" }
1412 <- {
1413 "return":[
1415 "device":"ide0-hd0",
1416 "parent":{
1417 "stats":{
1418 "wr_highest_offset":3686448128,
1419 "wr_bytes":9786368,
1420 "wr_operations":751,
1421 "rd_bytes":122567168,
1422 "rd_operations":36772
1423 "wr_total_times_ns":313253456
1424 "rd_total_times_ns":3465673657
1425 "flush_total_times_ns":49653
1426 "flush_operations":61,
1429 "stats":{
1430 "wr_highest_offset":2821110784,
1431 "wr_bytes":9786368,
1432 "wr_operations":692,
1433 "rd_bytes":122739200,
1434 "rd_operations":36604
1435 "flush_operations":51,
1436 "wr_total_times_ns":313253456
1437 "rd_total_times_ns":3465673657
1438 "flush_total_times_ns":49653
1442 "device":"ide1-cd0",
1443 "stats":{
1444 "wr_highest_offset":0,
1445 "wr_bytes":0,
1446 "wr_operations":0,
1447 "rd_bytes":0,
1448 "rd_operations":0
1449 "flush_operations":0,
1450 "wr_total_times_ns":0
1451 "rd_total_times_ns":0
1452 "flush_total_times_ns":0
1456 "device":"floppy0",
1457 "stats":{
1458 "wr_highest_offset":0,
1459 "wr_bytes":0,
1460 "wr_operations":0,
1461 "rd_bytes":0,
1462 "rd_operations":0
1463 "flush_operations":0,
1464 "wr_total_times_ns":0
1465 "rd_total_times_ns":0
1466 "flush_total_times_ns":0
1470 "device":"sd0",
1471 "stats":{
1472 "wr_highest_offset":0,
1473 "wr_bytes":0,
1474 "wr_operations":0,
1475 "rd_bytes":0,
1476 "rd_operations":0
1477 "flush_operations":0,
1478 "wr_total_times_ns":0
1479 "rd_total_times_ns":0
1480 "flush_total_times_ns":0
1486 EQMP
1489 .name = "query-blockstats",
1490 .args_type = "",
1491 .mhandler.cmd_new = qmp_marshal_input_query_blockstats,
1494 SQMP
1495 query-cpus
1496 ----------
1498 Show CPU information.
1500 Return a json-array. Each CPU is represented by a json-object, which contains:
1502 - "CPU": CPU index (json-int)
1503 - "current": true if this is the current CPU, false otherwise (json-bool)
1504 - "halted": true if the cpu is halted, false otherwise (json-bool)
1505 - Current program counter. The key's name depends on the architecture:
1506 "pc": i386/x86_64 (json-int)
1507 "nip": PPC (json-int)
1508 "pc" and "npc": sparc (json-int)
1509 "PC": mips (json-int)
1510 - "thread_id": ID of the underlying host thread (json-int)
1512 Example:
1514 -> { "execute": "query-cpus" }
1515 <- {
1516 "return":[
1518 "CPU":0,
1519 "current":true,
1520 "halted":false,
1521 "pc":3227107138
1522 "thread_id":3134
1525 "CPU":1,
1526 "current":false,
1527 "halted":true,
1528 "pc":7108165
1529 "thread_id":3135
1534 EQMP
1537 .name = "query-cpus",
1538 .args_type = "",
1539 .mhandler.cmd_new = qmp_marshal_input_query_cpus,
1542 SQMP
1543 query-pci
1544 ---------
1546 PCI buses and devices information.
1548 The returned value is a json-array of all buses. Each bus is represented by
1549 a json-object, which has a key with a json-array of all PCI devices attached
1550 to it. Each device is represented by a json-object.
1552 The bus json-object contains the following:
1554 - "bus": bus number (json-int)
1555 - "devices": a json-array of json-objects, each json-object represents a
1556 PCI device
1558 The PCI device json-object contains the following:
1560 - "bus": identical to the parent's bus number (json-int)
1561 - "slot": slot number (json-int)
1562 - "function": function number (json-int)
1563 - "class_info": a json-object containing:
1564 - "desc": device class description (json-string, optional)
1565 - "class": device class number (json-int)
1566 - "id": a json-object containing:
1567 - "device": device ID (json-int)
1568 - "vendor": vendor ID (json-int)
1569 - "irq": device's IRQ if assigned (json-int, optional)
1570 - "qdev_id": qdev id string (json-string)
1571 - "pci_bridge": It's a json-object, only present if this device is a
1572 PCI bridge, contains:
1573 - "bus": bus number (json-int)
1574 - "secondary": secondary bus number (json-int)
1575 - "subordinate": subordinate bus number (json-int)
1576 - "io_range": I/O memory range information, a json-object with the
1577 following members:
1578 - "base": base address, in bytes (json-int)
1579 - "limit": limit address, in bytes (json-int)
1580 - "memory_range": memory range information, a json-object with the
1581 following members:
1582 - "base": base address, in bytes (json-int)
1583 - "limit": limit address, in bytes (json-int)
1584 - "prefetchable_range": Prefetchable memory range information, a
1585 json-object with the following members:
1586 - "base": base address, in bytes (json-int)
1587 - "limit": limit address, in bytes (json-int)
1588 - "devices": a json-array of PCI devices if there's any attached, each
1589 each element is represented by a json-object, which contains
1590 the same members of the 'PCI device json-object' described
1591 above (optional)
1592 - "regions": a json-array of json-objects, each json-object represents a
1593 memory region of this device
1595 The memory range json-object contains the following:
1597 - "base": base memory address (json-int)
1598 - "limit": limit value (json-int)
1600 The region json-object can be an I/O region or a memory region, an I/O region
1601 json-object contains the following:
1603 - "type": "io" (json-string, fixed)
1604 - "bar": BAR number (json-int)
1605 - "address": memory address (json-int)
1606 - "size": memory size (json-int)
1608 A memory region json-object contains the following:
1610 - "type": "memory" (json-string, fixed)
1611 - "bar": BAR number (json-int)
1612 - "address": memory address (json-int)
1613 - "size": memory size (json-int)
1614 - "mem_type_64": true or false (json-bool)
1615 - "prefetch": true or false (json-bool)
1617 Example:
1619 -> { "execute": "query-pci" }
1620 <- {
1621 "return":[
1623 "bus":0,
1624 "devices":[
1626 "bus":0,
1627 "qdev_id":"",
1628 "slot":0,
1629 "class_info":{
1630 "class":1536,
1631 "desc":"Host bridge"
1633 "id":{
1634 "device":32902,
1635 "vendor":4663
1637 "function":0,
1638 "regions":[
1643 "bus":0,
1644 "qdev_id":"",
1645 "slot":1,
1646 "class_info":{
1647 "class":1537,
1648 "desc":"ISA bridge"
1650 "id":{
1651 "device":32902,
1652 "vendor":28672
1654 "function":0,
1655 "regions":[
1660 "bus":0,
1661 "qdev_id":"",
1662 "slot":1,
1663 "class_info":{
1664 "class":257,
1665 "desc":"IDE controller"
1667 "id":{
1668 "device":32902,
1669 "vendor":28688
1671 "function":1,
1672 "regions":[
1674 "bar":4,
1675 "size":16,
1676 "address":49152,
1677 "type":"io"
1682 "bus":0,
1683 "qdev_id":"",
1684 "slot":2,
1685 "class_info":{
1686 "class":768,
1687 "desc":"VGA controller"
1689 "id":{
1690 "device":4115,
1691 "vendor":184
1693 "function":0,
1694 "regions":[
1696 "prefetch":true,
1697 "mem_type_64":false,
1698 "bar":0,
1699 "size":33554432,
1700 "address":4026531840,
1701 "type":"memory"
1704 "prefetch":false,
1705 "mem_type_64":false,
1706 "bar":1,
1707 "size":4096,
1708 "address":4060086272,
1709 "type":"memory"
1712 "prefetch":false,
1713 "mem_type_64":false,
1714 "bar":6,
1715 "size":65536,
1716 "address":-1,
1717 "type":"memory"
1722 "bus":0,
1723 "qdev_id":"",
1724 "irq":11,
1725 "slot":4,
1726 "class_info":{
1727 "class":1280,
1728 "desc":"RAM controller"
1730 "id":{
1731 "device":6900,
1732 "vendor":4098
1734 "function":0,
1735 "regions":[
1737 "bar":0,
1738 "size":32,
1739 "address":49280,
1740 "type":"io"
1749 Note: This example has been shortened as the real response is too long.
1751 EQMP
1754 .name = "query-pci",
1755 .args_type = "",
1756 .mhandler.cmd_new = qmp_marshal_input_query_pci,
1759 SQMP
1760 query-kvm
1761 ---------
1763 Show KVM information.
1765 Return a json-object with the following information:
1767 - "enabled": true if KVM support is enabled, false otherwise (json-bool)
1768 - "present": true if QEMU has KVM support, false otherwise (json-bool)
1770 Example:
1772 -> { "execute": "query-kvm" }
1773 <- { "return": { "enabled": true, "present": true } }
1775 EQMP
1778 .name = "query-kvm",
1779 .args_type = "",
1780 .mhandler.cmd_new = qmp_marshal_input_query_kvm,
1783 SQMP
1784 query-status
1785 ------------
1787 Return a json-object with the following information:
1789 - "running": true if the VM is running, or false if it is paused (json-bool)
1790 - "singlestep": true if the VM is in single step mode,
1791 false otherwise (json-bool)
1792 - "status": one of the following values (json-string)
1793 "debug" - QEMU is running on a debugger
1794 "inmigrate" - guest is paused waiting for an incoming migration
1795 "internal-error" - An internal error that prevents further guest
1796 execution has occurred
1797 "io-error" - the last IOP has failed and the device is configured
1798 to pause on I/O errors
1799 "paused" - guest has been paused via the 'stop' command
1800 "postmigrate" - guest is paused following a successful 'migrate'
1801 "prelaunch" - QEMU was started with -S and guest has not started
1802 "finish-migrate" - guest is paused to finish the migration process
1803 "restore-vm" - guest is paused to restore VM state
1804 "running" - guest is actively running
1805 "save-vm" - guest is paused to save the VM state
1806 "shutdown" - guest is shut down (and -no-shutdown is in use)
1807 "watchdog" - the watchdog action is configured to pause and
1808 has been triggered
1810 Example:
1812 -> { "execute": "query-status" }
1813 <- { "return": { "running": true, "singlestep": false, "status": "running" } }
1815 EQMP
1818 .name = "query-status",
1819 .args_type = "",
1820 .mhandler.cmd_new = qmp_marshal_input_query_status,
1823 SQMP
1824 query-mice
1825 ----------
1827 Show VM mice information.
1829 Each mouse is represented by a json-object, the returned value is a json-array
1830 of all mice.
1832 The mouse json-object contains the following:
1834 - "name": mouse's name (json-string)
1835 - "index": mouse's index (json-int)
1836 - "current": true if this mouse is receiving events, false otherwise (json-bool)
1837 - "absolute": true if the mouse generates absolute input events (json-bool)
1839 Example:
1841 -> { "execute": "query-mice" }
1842 <- {
1843 "return":[
1845 "name":"QEMU Microsoft Mouse",
1846 "index":0,
1847 "current":false,
1848 "absolute":false
1851 "name":"QEMU PS/2 Mouse",
1852 "index":1,
1853 "current":true,
1854 "absolute":true
1859 EQMP
1862 .name = "query-mice",
1863 .args_type = "",
1864 .mhandler.cmd_new = qmp_marshal_input_query_mice,
1867 SQMP
1868 query-vnc
1869 ---------
1871 Show VNC server information.
1873 Return a json-object with server information. Connected clients are returned
1874 as a json-array of json-objects.
1876 The main json-object contains the following:
1878 - "enabled": true or false (json-bool)
1879 - "host": server's IP address (json-string)
1880 - "family": address family (json-string)
1881 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1882 - "service": server's port number (json-string)
1883 - "auth": authentication method (json-string)
1884 - Possible values: "invalid", "none", "ra2", "ra2ne", "sasl", "tight",
1885 "tls", "ultra", "unknown", "vencrypt", "vencrypt",
1886 "vencrypt+plain", "vencrypt+tls+none",
1887 "vencrypt+tls+plain", "vencrypt+tls+sasl",
1888 "vencrypt+tls+vnc", "vencrypt+x509+none",
1889 "vencrypt+x509+plain", "vencrypt+x509+sasl",
1890 "vencrypt+x509+vnc", "vnc"
1891 - "clients": a json-array of all connected clients
1893 Clients are described by a json-object, each one contain the following:
1895 - "host": client's IP address (json-string)
1896 - "family": address family (json-string)
1897 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1898 - "service": client's port number (json-string)
1899 - "x509_dname": TLS dname (json-string, optional)
1900 - "sasl_username": SASL username (json-string, optional)
1902 Example:
1904 -> { "execute": "query-vnc" }
1905 <- {
1906 "return":{
1907 "enabled":true,
1908 "host":"0.0.0.0",
1909 "service":"50402",
1910 "auth":"vnc",
1911 "family":"ipv4",
1912 "clients":[
1914 "host":"127.0.0.1",
1915 "service":"50401",
1916 "family":"ipv4"
1922 EQMP
1925 .name = "query-vnc",
1926 .args_type = "",
1927 .mhandler.cmd_new = qmp_marshal_input_query_vnc,
1930 SQMP
1931 query-spice
1932 -----------
1934 Show SPICE server information.
1936 Return a json-object with server information. Connected clients are returned
1937 as a json-array of json-objects.
1939 The main json-object contains the following:
1941 - "enabled": true or false (json-bool)
1942 - "host": server's IP address (json-string)
1943 - "port": server's port number (json-int, optional)
1944 - "tls-port": server's port number (json-int, optional)
1945 - "auth": authentication method (json-string)
1946 - Possible values: "none", "spice"
1947 - "channels": a json-array of all active channels clients
1949 Channels are described by a json-object, each one contain the following:
1951 - "host": client's IP address (json-string)
1952 - "family": address family (json-string)
1953 - Possible values: "ipv4", "ipv6", "unix", "unknown"
1954 - "port": client's port number (json-string)
1955 - "connection-id": spice connection id. All channels with the same id
1956 belong to the same spice session (json-int)
1957 - "channel-type": channel type. "1" is the main control channel, filter for
1958 this one if you want track spice sessions only (json-int)
1959 - "channel-id": channel id. Usually "0", might be different needed when
1960 multiple channels of the same type exist, such as multiple
1961 display channels in a multihead setup (json-int)
1962 - "tls": whevener the channel is encrypted (json-bool)
1964 Example:
1966 -> { "execute": "query-spice" }
1967 <- {
1968 "return": {
1969 "enabled": true,
1970 "auth": "spice",
1971 "port": 5920,
1972 "tls-port": 5921,
1973 "host": "0.0.0.0",
1974 "channels": [
1976 "port": "54924",
1977 "family": "ipv4",
1978 "channel-type": 1,
1979 "connection-id": 1804289383,
1980 "host": "127.0.0.1",
1981 "channel-id": 0,
1982 "tls": true
1985 "port": "36710",
1986 "family": "ipv4",
1987 "channel-type": 4,
1988 "connection-id": 1804289383,
1989 "host": "127.0.0.1",
1990 "channel-id": 0,
1991 "tls": false
1993 [ ... more channels follow ... ]
1998 EQMP
2000 #if defined(CONFIG_SPICE)
2002 .name = "query-spice",
2003 .args_type = "",
2004 .mhandler.cmd_new = qmp_marshal_input_query_spice,
2006 #endif
2008 SQMP
2009 query-name
2010 ----------
2012 Show VM name.
2014 Return a json-object with the following information:
2016 - "name": VM's name (json-string, optional)
2018 Example:
2020 -> { "execute": "query-name" }
2021 <- { "return": { "name": "qemu-name" } }
2023 EQMP
2026 .name = "query-name",
2027 .args_type = "",
2028 .mhandler.cmd_new = qmp_marshal_input_query_name,
2031 SQMP
2032 query-uuid
2033 ----------
2035 Show VM UUID.
2037 Return a json-object with the following information:
2039 - "UUID": Universally Unique Identifier (json-string)
2041 Example:
2043 -> { "execute": "query-uuid" }
2044 <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
2046 EQMP
2049 .name = "query-uuid",
2050 .args_type = "",
2051 .mhandler.cmd_new = qmp_marshal_input_query_uuid,
2054 SQMP
2055 query-migrate
2056 -------------
2058 Migration status.
2060 Return a json-object. If migration is active there will be another json-object
2061 with RAM migration status and if block migration is active another one with
2062 block migration status.
2064 The main json-object contains the following:
2066 - "status": migration status (json-string)
2067 - Possible values: "active", "completed", "failed", "cancelled"
2068 - "ram": only present if "status" is "active", it is a json-object with the
2069 following RAM information (in bytes):
2070 - "transferred": amount transferred (json-int)
2071 - "remaining": amount remaining (json-int)
2072 - "total": total (json-int)
2073 - "disk": only present if "status" is "active" and it is a block migration,
2074 it is a json-object with the following disk information (in bytes):
2075 - "transferred": amount transferred (json-int)
2076 - "remaining": amount remaining (json-int)
2077 - "total": total (json-int)
2079 Examples:
2081 1. Before the first migration
2083 -> { "execute": "query-migrate" }
2084 <- { "return": {} }
2086 2. Migration is done and has succeeded
2088 -> { "execute": "query-migrate" }
2089 <- { "return": { "status": "completed" } }
2091 3. Migration is done and has failed
2093 -> { "execute": "query-migrate" }
2094 <- { "return": { "status": "failed" } }
2096 4. Migration is being performed and is not a block migration:
2098 -> { "execute": "query-migrate" }
2099 <- {
2100 "return":{
2101 "status":"active",
2102 "ram":{
2103 "transferred":123,
2104 "remaining":123,
2105 "total":246
2110 5. Migration is being performed and is a block migration:
2112 -> { "execute": "query-migrate" }
2113 <- {
2114 "return":{
2115 "status":"active",
2116 "ram":{
2117 "total":1057024,
2118 "remaining":1053304,
2119 "transferred":3720
2121 "disk":{
2122 "total":20971520,
2123 "remaining":20880384,
2124 "transferred":91136
2129 EQMP
2132 .name = "query-migrate",
2133 .args_type = "",
2134 .mhandler.cmd_new = qmp_marshal_input_query_migrate,
2137 SQMP
2138 query-balloon
2139 -------------
2141 Show balloon information.
2143 Make an asynchronous request for balloon info. When the request completes a
2144 json-object will be returned containing the following data:
2146 - "actual": current balloon value in bytes (json-int)
2147 - "mem_swapped_in": Amount of memory swapped in bytes (json-int, optional)
2148 - "mem_swapped_out": Amount of memory swapped out in bytes (json-int, optional)
2149 - "major_page_faults": Number of major faults (json-int, optional)
2150 - "minor_page_faults": Number of minor faults (json-int, optional)
2151 - "free_mem": Total amount of free and unused memory in
2152 bytes (json-int, optional)
2153 - "total_mem": Total amount of available memory in bytes (json-int, optional)
2155 Example:
2157 -> { "execute": "query-balloon" }
2158 <- {
2159 "return":{
2160 "actual":1073741824,
2161 "mem_swapped_in":0,
2162 "mem_swapped_out":0,
2163 "major_page_faults":142,
2164 "minor_page_faults":239245,
2165 "free_mem":1014185984,
2166 "total_mem":1044668416
2170 EQMP
2173 .name = "query-balloon",
2174 .args_type = "",
2175 .mhandler.cmd_new = qmp_marshal_input_query_balloon,
2179 .name = "query-block-jobs",
2180 .args_type = "",
2181 .mhandler.cmd_new = qmp_marshal_input_query_block_jobs,
2185 .name = "qom-list",
2186 .args_type = "path:s",
2187 .mhandler.cmd_new = qmp_marshal_input_qom_list,
2191 .name = "qom-set",
2192 .args_type = "path:s,property:s,value:q",
2193 .mhandler.cmd_new = qmp_qom_set,
2197 .name = "qom-get",
2198 .args_type = "path:s,property:s",
2199 .mhandler.cmd_new = qmp_qom_get,
2203 .name = "change-vnc-password",
2204 .args_type = "password:s",
2205 .mhandler.cmd_new = qmp_marshal_input_change_vnc_password,
2208 .name = "qom-list-types",
2209 .args_type = "implements:s?,abstract:b?",
2210 .mhandler.cmd_new = qmp_marshal_input_qom_list_types,