]> git.proxmox.com Git - mirror_qemu.git/blob - qapi/misc.json
qapi: Fix indent level on doc comments in json files
[mirror_qemu.git] / qapi / misc.json
1 # -*- Mode: Python -*-
2 #
3
4 ##
5 # = Miscellanea
6 ##
7
8 { 'include': 'common.json' }
9
10 ##
11 # @qmp_capabilities:
12 #
13 # Enable QMP capabilities.
14 #
15 # Arguments:
16 #
17 # @enable: An optional list of QMPCapability values to enable. The
18 # client must not enable any capability that is not
19 # mentioned in the QMP greeting message. If the field is not
20 # provided, it means no QMP capabilities will be enabled.
21 # (since 2.12)
22 #
23 # Example:
24 #
25 # -> { "execute": "qmp_capabilities",
26 # "arguments": { "enable": [ "oob" ] } }
27 # <- { "return": {} }
28 #
29 # Notes: This command is valid exactly when first connecting: it must be
30 # issued before any other command will be accepted, and will fail once the
31 # monitor is accepting other commands. (see qemu docs/interop/qmp-spec.txt)
32 #
33 # The QMP client needs to explicitly enable QMP capabilities, otherwise
34 # all the QMP capabilities will be turned off by default.
35 #
36 # Since: 0.13
37 #
38 ##
39 { 'command': 'qmp_capabilities',
40 'data': { '*enable': [ 'QMPCapability' ] },
41 'allow-preconfig': true }
42
43 ##
44 # @QMPCapability:
45 #
46 # Enumeration of capabilities to be advertised during initial client
47 # connection, used for agreeing on particular QMP extension behaviors.
48 #
49 # @oob: QMP ability to support out-of-band requests.
50 # (Please refer to qmp-spec.txt for more information on OOB)
51 #
52 # Since: 2.12
53 #
54 ##
55 { 'enum': 'QMPCapability',
56 'data': [ 'oob' ] }
57
58 ##
59 # @VersionTriple:
60 #
61 # A three-part version number.
62 #
63 # @major: The major version number.
64 #
65 # @minor: The minor version number.
66 #
67 # @micro: The micro version number.
68 #
69 # Since: 2.4
70 ##
71 { 'struct': 'VersionTriple',
72 'data': {'major': 'int', 'minor': 'int', 'micro': 'int'} }
73
74
75 ##
76 # @VersionInfo:
77 #
78 # A description of QEMU's version.
79 #
80 # @qemu: The version of QEMU. By current convention, a micro
81 # version of 50 signifies a development branch. A micro version
82 # greater than or equal to 90 signifies a release candidate for
83 # the next minor version. A micro version of less than 50
84 # signifies a stable release.
85 #
86 # @package: QEMU will always set this field to an empty string. Downstream
87 # versions of QEMU should set this to a non-empty string. The
88 # exact format depends on the downstream however it highly
89 # recommended that a unique name is used.
90 #
91 # Since: 0.14.0
92 ##
93 { 'struct': 'VersionInfo',
94 'data': {'qemu': 'VersionTriple', 'package': 'str'} }
95
96 ##
97 # @query-version:
98 #
99 # Returns the current version of QEMU.
100 #
101 # Returns: A @VersionInfo object describing the current version of QEMU.
102 #
103 # Since: 0.14.0
104 #
105 # Example:
106 #
107 # -> { "execute": "query-version" }
108 # <- {
109 # "return":{
110 # "qemu":{
111 # "major":0,
112 # "minor":11,
113 # "micro":5
114 # },
115 # "package":""
116 # }
117 # }
118 #
119 ##
120 { 'command': 'query-version', 'returns': 'VersionInfo',
121 'allow-preconfig': true }
122
123 ##
124 # @CommandInfo:
125 #
126 # Information about a QMP command
127 #
128 # @name: The command name
129 #
130 # Since: 0.14.0
131 ##
132 { 'struct': 'CommandInfo', 'data': {'name': 'str'} }
133
134 ##
135 # @query-commands:
136 #
137 # Return a list of supported QMP commands by this server
138 #
139 # Returns: A list of @CommandInfo for all supported commands
140 #
141 # Since: 0.14.0
142 #
143 # Example:
144 #
145 # -> { "execute": "query-commands" }
146 # <- {
147 # "return":[
148 # {
149 # "name":"query-balloon"
150 # },
151 # {
152 # "name":"system_powerdown"
153 # }
154 # ]
155 # }
156 #
157 # Note: This example has been shortened as the real response is too long.
158 #
159 ##
160 { 'command': 'query-commands', 'returns': ['CommandInfo'],
161 'allow-preconfig': true }
162
163 ##
164 # @LostTickPolicy:
165 #
166 # Policy for handling lost ticks in timer devices. Ticks end up getting
167 # lost when, for example, the guest is paused.
168 #
169 # @discard: throw away the missed ticks and continue with future injection
170 # normally. The guest OS will see the timer jump ahead by a
171 # potentially quite significant amount all at once, as if the
172 # intervening chunk of time had simply not existed; needless to
173 # say, such a sudden jump can easily confuse a guest OS which is
174 # not specifically prepared to deal with it. Assuming the guest
175 # OS can deal correctly with the time jump, the time in the guest
176 # and in the host should now match.
177 #
178 # @delay: continue to deliver ticks at the normal rate. The guest OS will
179 # not notice anything is amiss, as from its point of view time will
180 # have continued to flow normally. The time in the guest should now
181 # be behind the time in the host by exactly the amount of time during
182 # which ticks have been missed.
183 #
184 # @slew: deliver ticks at a higher rate to catch up with the missed ticks.
185 # The guest OS will not notice anything is amiss, as from its point
186 # of view time will have continued to flow normally. Once the timer
187 # has managed to catch up with all the missing ticks, the time in
188 # the guest and in the host should match.
189 #
190 # Since: 2.0
191 ##
192 { 'enum': 'LostTickPolicy',
193 'data': ['discard', 'delay', 'slew' ] }
194
195 ##
196 # @add_client:
197 #
198 # Allow client connections for VNC, Spice and socket based
199 # character devices to be passed in to QEMU via SCM_RIGHTS.
200 #
201 # @protocol: protocol name. Valid names are "vnc", "spice" or the
202 # name of a character device (eg. from -chardev id=XXXX)
203 #
204 # @fdname: file descriptor name previously passed via 'getfd' command
205 #
206 # @skipauth: whether to skip authentication. Only applies
207 # to "vnc" and "spice" protocols
208 #
209 # @tls: whether to perform TLS. Only applies to the "spice"
210 # protocol
211 #
212 # Returns: nothing on success.
213 #
214 # Since: 0.14.0
215 #
216 # Example:
217 #
218 # -> { "execute": "add_client", "arguments": { "protocol": "vnc",
219 # "fdname": "myclient" } }
220 # <- { "return": {} }
221 #
222 ##
223 { 'command': 'add_client',
224 'data': { 'protocol': 'str', 'fdname': 'str', '*skipauth': 'bool',
225 '*tls': 'bool' } }
226
227 ##
228 # @NameInfo:
229 #
230 # Guest name information.
231 #
232 # @name: The name of the guest
233 #
234 # Since: 0.14.0
235 ##
236 { 'struct': 'NameInfo', 'data': {'*name': 'str'} }
237
238 ##
239 # @query-name:
240 #
241 # Return the name information of a guest.
242 #
243 # Returns: @NameInfo of the guest
244 #
245 # Since: 0.14.0
246 #
247 # Example:
248 #
249 # -> { "execute": "query-name" }
250 # <- { "return": { "name": "qemu-name" } }
251 #
252 ##
253 { 'command': 'query-name', 'returns': 'NameInfo', 'allow-preconfig': true }
254
255 ##
256 # @KvmInfo:
257 #
258 # Information about support for KVM acceleration
259 #
260 # @enabled: true if KVM acceleration is active
261 #
262 # @present: true if KVM acceleration is built into this executable
263 #
264 # Since: 0.14.0
265 ##
266 { 'struct': 'KvmInfo', 'data': {'enabled': 'bool', 'present': 'bool'} }
267
268 ##
269 # @query-kvm:
270 #
271 # Returns information about KVM acceleration
272 #
273 # Returns: @KvmInfo
274 #
275 # Since: 0.14.0
276 #
277 # Example:
278 #
279 # -> { "execute": "query-kvm" }
280 # <- { "return": { "enabled": true, "present": true } }
281 #
282 ##
283 { 'command': 'query-kvm', 'returns': 'KvmInfo' }
284
285 ##
286 # @UuidInfo:
287 #
288 # Guest UUID information (Universally Unique Identifier).
289 #
290 # @UUID: the UUID of the guest
291 #
292 # Since: 0.14.0
293 #
294 # Notes: If no UUID was specified for the guest, a null UUID is returned.
295 ##
296 { 'struct': 'UuidInfo', 'data': {'UUID': 'str'} }
297
298 ##
299 # @query-uuid:
300 #
301 # Query the guest UUID information.
302 #
303 # Returns: The @UuidInfo for the guest
304 #
305 # Since: 0.14.0
306 #
307 # Example:
308 #
309 # -> { "execute": "query-uuid" }
310 # <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
311 #
312 ##
313 { 'command': 'query-uuid', 'returns': 'UuidInfo', 'allow-preconfig': true }
314
315 ##
316 # @EventInfo:
317 #
318 # Information about a QMP event
319 #
320 # @name: The event name
321 #
322 # Since: 1.2.0
323 ##
324 { 'struct': 'EventInfo', 'data': {'name': 'str'} }
325
326 ##
327 # @query-events:
328 #
329 # Return information on QMP events.
330 #
331 # Returns: A list of @EventInfo.
332 #
333 # Since: 1.2.0
334 #
335 # Note: This command is deprecated, because its output doesn't reflect
336 # compile-time configuration. Use query-qmp-schema instead.
337 #
338 # Example:
339 #
340 # -> { "execute": "query-events" }
341 # <- {
342 # "return": [
343 # {
344 # "name":"SHUTDOWN"
345 # },
346 # {
347 # "name":"RESET"
348 # }
349 # ]
350 # }
351 #
352 # Note: This example has been shortened as the real response is too long.
353 #
354 ##
355 { 'command': 'query-events', 'returns': ['EventInfo'] }
356
357 ##
358 # @IOThreadInfo:
359 #
360 # Information about an iothread
361 #
362 # @id: the identifier of the iothread
363 #
364 # @thread-id: ID of the underlying host thread
365 #
366 # @poll-max-ns: maximum polling time in ns, 0 means polling is disabled
367 # (since 2.9)
368 #
369 # @poll-grow: how many ns will be added to polling time, 0 means that it's not
370 # configured (since 2.9)
371 #
372 # @poll-shrink: how many ns will be removed from polling time, 0 means that
373 # it's not configured (since 2.9)
374 #
375 # Since: 2.0
376 ##
377 { 'struct': 'IOThreadInfo',
378 'data': {'id': 'str',
379 'thread-id': 'int',
380 'poll-max-ns': 'int',
381 'poll-grow': 'int',
382 'poll-shrink': 'int' } }
383
384 ##
385 # @query-iothreads:
386 #
387 # Returns a list of information about each iothread.
388 #
389 # Note: this list excludes the QEMU main loop thread, which is not declared
390 # using the -object iothread command-line option. It is always the main thread
391 # of the process.
392 #
393 # Returns: a list of @IOThreadInfo for each iothread
394 #
395 # Since: 2.0
396 #
397 # Example:
398 #
399 # -> { "execute": "query-iothreads" }
400 # <- { "return": [
401 # {
402 # "id":"iothread0",
403 # "thread-id":3134
404 # },
405 # {
406 # "id":"iothread1",
407 # "thread-id":3135
408 # }
409 # ]
410 # }
411 #
412 ##
413 { 'command': 'query-iothreads', 'returns': ['IOThreadInfo'],
414 'allow-preconfig': true }
415
416 ##
417 # @BalloonInfo:
418 #
419 # Information about the guest balloon device.
420 #
421 # @actual: the number of bytes the balloon currently contains
422 #
423 # Since: 0.14.0
424 #
425 ##
426 { 'struct': 'BalloonInfo', 'data': {'actual': 'int' } }
427
428 ##
429 # @query-balloon:
430 #
431 # Return information about the balloon device.
432 #
433 # Returns: @BalloonInfo on success
434 #
435 # If the balloon driver is enabled but not functional because the KVM
436 # kernel module cannot support it, KvmMissingCap
437 #
438 # If no balloon device is present, DeviceNotActive
439 #
440 # Since: 0.14.0
441 #
442 # Example:
443 #
444 # -> { "execute": "query-balloon" }
445 # <- { "return": {
446 # "actual": 1073741824,
447 # }
448 # }
449 #
450 ##
451 { 'command': 'query-balloon', 'returns': 'BalloonInfo' }
452
453 ##
454 # @BALLOON_CHANGE:
455 #
456 # Emitted when the guest changes the actual BALLOON level. This value is
457 # equivalent to the @actual field return by the 'query-balloon' command
458 #
459 # @actual: actual level of the guest memory balloon in bytes
460 #
461 # Note: this event is rate-limited.
462 #
463 # Since: 1.2
464 #
465 # Example:
466 #
467 # <- { "event": "BALLOON_CHANGE",
468 # "data": { "actual": 944766976 },
469 # "timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
470 #
471 ##
472 { 'event': 'BALLOON_CHANGE',
473 'data': { 'actual': 'int' } }
474
475 ##
476 # @PciMemoryRange:
477 #
478 # A PCI device memory region
479 #
480 # @base: the starting address (guest physical)
481 #
482 # @limit: the ending address (guest physical)
483 #
484 # Since: 0.14.0
485 ##
486 { 'struct': 'PciMemoryRange', 'data': {'base': 'int', 'limit': 'int'} }
487
488 ##
489 # @PciMemoryRegion:
490 #
491 # Information about a PCI device I/O region.
492 #
493 # @bar: the index of the Base Address Register for this region
494 #
495 # @type: 'io' if the region is a PIO region
496 # 'memory' if the region is a MMIO region
497 #
498 # @size: memory size
499 #
500 # @prefetch: if @type is 'memory', true if the memory is prefetchable
501 #
502 # @mem_type_64: if @type is 'memory', true if the BAR is 64-bit
503 #
504 # Since: 0.14.0
505 ##
506 { 'struct': 'PciMemoryRegion',
507 'data': {'bar': 'int', 'type': 'str', 'address': 'int', 'size': 'int',
508 '*prefetch': 'bool', '*mem_type_64': 'bool' } }
509
510 ##
511 # @PciBusInfo:
512 #
513 # Information about a bus of a PCI Bridge device
514 #
515 # @number: primary bus interface number. This should be the number of the
516 # bus the device resides on.
517 #
518 # @secondary: secondary bus interface number. This is the number of the
519 # main bus for the bridge
520 #
521 # @subordinate: This is the highest number bus that resides below the
522 # bridge.
523 #
524 # @io_range: The PIO range for all devices on this bridge
525 #
526 # @memory_range: The MMIO range for all devices on this bridge
527 #
528 # @prefetchable_range: The range of prefetchable MMIO for all devices on
529 # this bridge
530 #
531 # Since: 2.4
532 ##
533 { 'struct': 'PciBusInfo',
534 'data': {'number': 'int', 'secondary': 'int', 'subordinate': 'int',
535 'io_range': 'PciMemoryRange',
536 'memory_range': 'PciMemoryRange',
537 'prefetchable_range': 'PciMemoryRange' } }
538
539 ##
540 # @PciBridgeInfo:
541 #
542 # Information about a PCI Bridge device
543 #
544 # @bus: information about the bus the device resides on
545 #
546 # @devices: a list of @PciDeviceInfo for each device on this bridge
547 #
548 # Since: 0.14.0
549 ##
550 { 'struct': 'PciBridgeInfo',
551 'data': {'bus': 'PciBusInfo', '*devices': ['PciDeviceInfo']} }
552
553 ##
554 # @PciDeviceClass:
555 #
556 # Information about the Class of a PCI device
557 #
558 # @desc: a string description of the device's class
559 #
560 # @class: the class code of the device
561 #
562 # Since: 2.4
563 ##
564 { 'struct': 'PciDeviceClass',
565 'data': {'*desc': 'str', 'class': 'int'} }
566
567 ##
568 # @PciDeviceId:
569 #
570 # Information about the Id of a PCI device
571 #
572 # @device: the PCI device id
573 #
574 # @vendor: the PCI vendor id
575 #
576 # @subsystem: the PCI subsystem id (since 3.1)
577 #
578 # @subsystem-vendor: the PCI subsystem vendor id (since 3.1)
579 #
580 # Since: 2.4
581 ##
582 { 'struct': 'PciDeviceId',
583 'data': {'device': 'int', 'vendor': 'int', '*subsystem': 'int',
584 '*subsystem-vendor': 'int'} }
585
586 ##
587 # @PciDeviceInfo:
588 #
589 # Information about a PCI device
590 #
591 # @bus: the bus number of the device
592 #
593 # @slot: the slot the device is located in
594 #
595 # @function: the function of the slot used by the device
596 #
597 # @class_info: the class of the device
598 #
599 # @id: the PCI device id
600 #
601 # @irq: if an IRQ is assigned to the device, the IRQ number
602 #
603 # @qdev_id: the device name of the PCI device
604 #
605 # @pci_bridge: if the device is a PCI bridge, the bridge information
606 #
607 # @regions: a list of the PCI I/O regions associated with the device
608 #
609 # Notes: the contents of @class_info.desc are not stable and should only be
610 # treated as informational.
611 #
612 # Since: 0.14.0
613 ##
614 { 'struct': 'PciDeviceInfo',
615 'data': {'bus': 'int', 'slot': 'int', 'function': 'int',
616 'class_info': 'PciDeviceClass', 'id': 'PciDeviceId',
617 '*irq': 'int', 'qdev_id': 'str', '*pci_bridge': 'PciBridgeInfo',
618 'regions': ['PciMemoryRegion']} }
619
620 ##
621 # @PciInfo:
622 #
623 # Information about a PCI bus
624 #
625 # @bus: the bus index
626 #
627 # @devices: a list of devices on this bus
628 #
629 # Since: 0.14.0
630 ##
631 { 'struct': 'PciInfo', 'data': {'bus': 'int', 'devices': ['PciDeviceInfo']} }
632
633 ##
634 # @query-pci:
635 #
636 # Return information about the PCI bus topology of the guest.
637 #
638 # Returns: a list of @PciInfo for each PCI bus. Each bus is
639 # represented by a json-object, which has a key with a json-array of
640 # all PCI devices attached to it. Each device is represented by a
641 # json-object.
642 #
643 # Since: 0.14.0
644 #
645 # Example:
646 #
647 # -> { "execute": "query-pci" }
648 # <- { "return": [
649 # {
650 # "bus": 0,
651 # "devices": [
652 # {
653 # "bus": 0,
654 # "qdev_id": "",
655 # "slot": 0,
656 # "class_info": {
657 # "class": 1536,
658 # "desc": "Host bridge"
659 # },
660 # "id": {
661 # "device": 32902,
662 # "vendor": 4663
663 # },
664 # "function": 0,
665 # "regions": [
666 # ]
667 # },
668 # {
669 # "bus": 0,
670 # "qdev_id": "",
671 # "slot": 1,
672 # "class_info": {
673 # "class": 1537,
674 # "desc": "ISA bridge"
675 # },
676 # "id": {
677 # "device": 32902,
678 # "vendor": 28672
679 # },
680 # "function": 0,
681 # "regions": [
682 # ]
683 # },
684 # {
685 # "bus": 0,
686 # "qdev_id": "",
687 # "slot": 1,
688 # "class_info": {
689 # "class": 257,
690 # "desc": "IDE controller"
691 # },
692 # "id": {
693 # "device": 32902,
694 # "vendor": 28688
695 # },
696 # "function": 1,
697 # "regions": [
698 # {
699 # "bar": 4,
700 # "size": 16,
701 # "address": 49152,
702 # "type": "io"
703 # }
704 # ]
705 # },
706 # {
707 # "bus": 0,
708 # "qdev_id": "",
709 # "slot": 2,
710 # "class_info": {
711 # "class": 768,
712 # "desc": "VGA controller"
713 # },
714 # "id": {
715 # "device": 4115,
716 # "vendor": 184
717 # },
718 # "function": 0,
719 # "regions": [
720 # {
721 # "prefetch": true,
722 # "mem_type_64": false,
723 # "bar": 0,
724 # "size": 33554432,
725 # "address": 4026531840,
726 # "type": "memory"
727 # },
728 # {
729 # "prefetch": false,
730 # "mem_type_64": false,
731 # "bar": 1,
732 # "size": 4096,
733 # "address": 4060086272,
734 # "type": "memory"
735 # },
736 # {
737 # "prefetch": false,
738 # "mem_type_64": false,
739 # "bar": 6,
740 # "size": 65536,
741 # "address": -1,
742 # "type": "memory"
743 # }
744 # ]
745 # },
746 # {
747 # "bus": 0,
748 # "qdev_id": "",
749 # "irq": 11,
750 # "slot": 4,
751 # "class_info": {
752 # "class": 1280,
753 # "desc": "RAM controller"
754 # },
755 # "id": {
756 # "device": 6900,
757 # "vendor": 4098
758 # },
759 # "function": 0,
760 # "regions": [
761 # {
762 # "bar": 0,
763 # "size": 32,
764 # "address": 49280,
765 # "type": "io"
766 # }
767 # ]
768 # }
769 # ]
770 # }
771 # ]
772 # }
773 #
774 # Note: This example has been shortened as the real response is too long.
775 #
776 ##
777 { 'command': 'query-pci', 'returns': ['PciInfo'] }
778
779 ##
780 # @quit:
781 #
782 # This command will cause the QEMU process to exit gracefully. While every
783 # attempt is made to send the QMP response before terminating, this is not
784 # guaranteed. When using this interface, a premature EOF would not be
785 # unexpected.
786 #
787 # Since: 0.14.0
788 #
789 # Example:
790 #
791 # -> { "execute": "quit" }
792 # <- { "return": {} }
793 ##
794 { 'command': 'quit' }
795
796 ##
797 # @stop:
798 #
799 # Stop all guest VCPU execution.
800 #
801 # Since: 0.14.0
802 #
803 # Notes: This function will succeed even if the guest is already in the stopped
804 # state. In "inmigrate" state, it will ensure that the guest
805 # remains paused once migration finishes, as if the -S option was
806 # passed on the command line.
807 #
808 # Example:
809 #
810 # -> { "execute": "stop" }
811 # <- { "return": {} }
812 #
813 ##
814 { 'command': 'stop' }
815
816 ##
817 # @system_reset:
818 #
819 # Performs a hard reset of a guest.
820 #
821 # Since: 0.14.0
822 #
823 # Example:
824 #
825 # -> { "execute": "system_reset" }
826 # <- { "return": {} }
827 #
828 ##
829 { 'command': 'system_reset' }
830
831 ##
832 # @system_powerdown:
833 #
834 # Requests that a guest perform a powerdown operation.
835 #
836 # Since: 0.14.0
837 #
838 # Notes: A guest may or may not respond to this command. This command
839 # returning does not indicate that a guest has accepted the request or
840 # that it has shut down. Many guests will respond to this command by
841 # prompting the user in some way.
842 # Example:
843 #
844 # -> { "execute": "system_powerdown" }
845 # <- { "return": {} }
846 #
847 ##
848 { 'command': 'system_powerdown' }
849
850 ##
851 # @memsave:
852 #
853 # Save a portion of guest memory to a file.
854 #
855 # @val: the virtual address of the guest to start from
856 #
857 # @size: the size of memory region to save
858 #
859 # @filename: the file to save the memory to as binary data
860 #
861 # @cpu-index: the index of the virtual CPU to use for translating the
862 # virtual address (defaults to CPU 0)
863 #
864 # Returns: Nothing on success
865 #
866 # Since: 0.14.0
867 #
868 # Notes: Errors were not reliably returned until 1.1
869 #
870 # Example:
871 #
872 # -> { "execute": "memsave",
873 # "arguments": { "val": 10,
874 # "size": 100,
875 # "filename": "/tmp/virtual-mem-dump" } }
876 # <- { "return": {} }
877 #
878 ##
879 { 'command': 'memsave',
880 'data': {'val': 'int', 'size': 'int', 'filename': 'str', '*cpu-index': 'int'} }
881
882 ##
883 # @pmemsave:
884 #
885 # Save a portion of guest physical memory to a file.
886 #
887 # @val: the physical address of the guest to start from
888 #
889 # @size: the size of memory region to save
890 #
891 # @filename: the file to save the memory to as binary data
892 #
893 # Returns: Nothing on success
894 #
895 # Since: 0.14.0
896 #
897 # Notes: Errors were not reliably returned until 1.1
898 #
899 # Example:
900 #
901 # -> { "execute": "pmemsave",
902 # "arguments": { "val": 10,
903 # "size": 100,
904 # "filename": "/tmp/physical-mem-dump" } }
905 # <- { "return": {} }
906 #
907 ##
908 { 'command': 'pmemsave',
909 'data': {'val': 'int', 'size': 'int', 'filename': 'str'} }
910
911 ##
912 # @cont:
913 #
914 # Resume guest VCPU execution.
915 #
916 # Since: 0.14.0
917 #
918 # Returns: If successful, nothing
919 #
920 # Notes: This command will succeed if the guest is currently running. It
921 # will also succeed if the guest is in the "inmigrate" state; in
922 # this case, the effect of the command is to make sure the guest
923 # starts once migration finishes, removing the effect of the -S
924 # command line option if it was passed.
925 #
926 # Example:
927 #
928 # -> { "execute": "cont" }
929 # <- { "return": {} }
930 #
931 ##
932 { 'command': 'cont' }
933
934 ##
935 # @x-exit-preconfig:
936 #
937 # Exit from "preconfig" state
938 #
939 # This command makes QEMU exit the preconfig state and proceed with
940 # VM initialization using configuration data provided on the command line
941 # and via the QMP monitor during the preconfig state. The command is only
942 # available during the preconfig state (i.e. when the --preconfig command
943 # line option was in use).
944 #
945 # Since 3.0
946 #
947 # Returns: nothing
948 #
949 # Example:
950 #
951 # -> { "execute": "x-exit-preconfig" }
952 # <- { "return": {} }
953 #
954 ##
955 { 'command': 'x-exit-preconfig', 'allow-preconfig': true }
956
957 ##
958 # @system_wakeup:
959 #
960 # Wake up guest from suspend. If the guest has wake-up from suspend
961 # support enabled (wakeup-suspend-support flag from
962 # query-current-machine), wake-up guest from suspend if the guest is
963 # in SUSPENDED state. Return an error otherwise.
964 #
965 # Since: 1.1
966 #
967 # Returns: nothing.
968 #
969 # Note: prior to 4.0, this command does nothing in case the guest
970 # isn't suspended.
971 #
972 # Example:
973 #
974 # -> { "execute": "system_wakeup" }
975 # <- { "return": {} }
976 #
977 ##
978 { 'command': 'system_wakeup' }
979
980 ##
981 # @inject-nmi:
982 #
983 # Injects a Non-Maskable Interrupt into the default CPU (x86/s390) or all CPUs (ppc64).
984 # The command fails when the guest doesn't support injecting.
985 #
986 # Returns: If successful, nothing
987 #
988 # Since: 0.14.0
989 #
990 # Note: prior to 2.1, this command was only supported for x86 and s390 VMs
991 #
992 # Example:
993 #
994 # -> { "execute": "inject-nmi" }
995 # <- { "return": {} }
996 #
997 ##
998 { 'command': 'inject-nmi' }
999
1000 ##
1001 # @balloon:
1002 #
1003 # Request the balloon driver to change its balloon size.
1004 #
1005 # @value: the target size of the balloon in bytes
1006 #
1007 # Returns: Nothing on success
1008 # If the balloon driver is enabled but not functional because the KVM
1009 # kernel module cannot support it, KvmMissingCap
1010 # If no balloon device is present, DeviceNotActive
1011 #
1012 # Notes: This command just issues a request to the guest. When it returns,
1013 # the balloon size may not have changed. A guest can change the balloon
1014 # size independent of this command.
1015 #
1016 # Since: 0.14.0
1017 #
1018 # Example:
1019 #
1020 # -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1021 # <- { "return": {} }
1022 #
1023 ##
1024 { 'command': 'balloon', 'data': {'value': 'int'} }
1025
1026 ##
1027 # @human-monitor-command:
1028 #
1029 # Execute a command on the human monitor and return the output.
1030 #
1031 # @command-line: the command to execute in the human monitor
1032 #
1033 # @cpu-index: The CPU to use for commands that require an implicit CPU
1034 #
1035 # Features:
1036 # @savevm-monitor-nodes: If present, HMP command savevm only snapshots
1037 # monitor-owned nodes if they have no parents.
1038 # This allows the use of 'savevm' with
1039 # -blockdev. (since 4.2)
1040 #
1041 # Returns: the output of the command as a string
1042 #
1043 # Since: 0.14.0
1044 #
1045 # Notes: This command only exists as a stop-gap. Its use is highly
1046 # discouraged. The semantics of this command are not
1047 # guaranteed: this means that command names, arguments and
1048 # responses can change or be removed at ANY time. Applications
1049 # that rely on long term stability guarantees should NOT
1050 # use this command.
1051 #
1052 # Known limitations:
1053 #
1054 # * This command is stateless, this means that commands that depend
1055 # on state information (such as getfd) might not work
1056 #
1057 # * Commands that prompt the user for data don't currently work
1058 #
1059 # Example:
1060 #
1061 # -> { "execute": "human-monitor-command",
1062 # "arguments": { "command-line": "info kvm" } }
1063 # <- { "return": "kvm support: enabled\r\n" }
1064 #
1065 ##
1066 { 'command': 'human-monitor-command',
1067 'data': {'command-line': 'str', '*cpu-index': 'int'},
1068 'returns': 'str',
1069 'features': [ 'savevm-monitor-nodes' ] }
1070
1071 ##
1072 # @change:
1073 #
1074 # This command is multiple commands multiplexed together.
1075 #
1076 # @device: This is normally the name of a block device but it may also be 'vnc'.
1077 # when it's 'vnc', then sub command depends on @target
1078 #
1079 # @target: If @device is a block device, then this is the new filename.
1080 # If @device is 'vnc', then if the value 'password' selects the vnc
1081 # change password command. Otherwise, this specifies a new server URI
1082 # address to listen to for VNC connections.
1083 #
1084 # @arg: If @device is a block device, then this is an optional format to open
1085 # the device with.
1086 # If @device is 'vnc' and @target is 'password', this is the new VNC
1087 # password to set. See change-vnc-password for additional notes.
1088 #
1089 # Returns: Nothing on success.
1090 # If @device is not a valid block device, DeviceNotFound
1091 #
1092 # Notes: This interface is deprecated, and it is strongly recommended that you
1093 # avoid using it. For changing block devices, use
1094 # blockdev-change-medium; for changing VNC parameters, use
1095 # change-vnc-password.
1096 #
1097 # Since: 0.14.0
1098 #
1099 # Example:
1100 #
1101 # 1. Change a removable medium
1102 #
1103 # -> { "execute": "change",
1104 # "arguments": { "device": "ide1-cd0",
1105 # "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } }
1106 # <- { "return": {} }
1107 #
1108 # 2. Change VNC password
1109 #
1110 # -> { "execute": "change",
1111 # "arguments": { "device": "vnc", "target": "password",
1112 # "arg": "foobar1" } }
1113 # <- { "return": {} }
1114 #
1115 ##
1116 { 'command': 'change',
1117 'data': {'device': 'str', 'target': 'str', '*arg': 'str'} }
1118
1119 ##
1120 # @xen-set-global-dirty-log:
1121 #
1122 # Enable or disable the global dirty log mode.
1123 #
1124 # @enable: true to enable, false to disable.
1125 #
1126 # Returns: nothing
1127 #
1128 # Since: 1.3
1129 #
1130 # Example:
1131 #
1132 # -> { "execute": "xen-set-global-dirty-log",
1133 # "arguments": { "enable": true } }
1134 # <- { "return": {} }
1135 #
1136 ##
1137 { 'command': 'xen-set-global-dirty-log', 'data': { 'enable': 'bool' } }
1138
1139 ##
1140 # @getfd:
1141 #
1142 # Receive a file descriptor via SCM rights and assign it a name
1143 #
1144 # @fdname: file descriptor name
1145 #
1146 # Returns: Nothing on success
1147 #
1148 # Since: 0.14.0
1149 #
1150 # Notes: If @fdname already exists, the file descriptor assigned to
1151 # it will be closed and replaced by the received file
1152 # descriptor.
1153 #
1154 # The 'closefd' command can be used to explicitly close the
1155 # file descriptor when it is no longer needed.
1156 #
1157 # Example:
1158 #
1159 # -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1160 # <- { "return": {} }
1161 #
1162 ##
1163 { 'command': 'getfd', 'data': {'fdname': 'str'} }
1164
1165 ##
1166 # @closefd:
1167 #
1168 # Close a file descriptor previously passed via SCM rights
1169 #
1170 # @fdname: file descriptor name
1171 #
1172 # Returns: Nothing on success
1173 #
1174 # Since: 0.14.0
1175 #
1176 # Example:
1177 #
1178 # -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1179 # <- { "return": {} }
1180 #
1181 ##
1182 { 'command': 'closefd', 'data': {'fdname': 'str'} }
1183
1184 ##
1185 # @MemoryInfo:
1186 #
1187 # Actual memory information in bytes.
1188 #
1189 # @base-memory: size of "base" memory specified with command line
1190 # option -m.
1191 #
1192 # @plugged-memory: size of memory that can be hot-unplugged. This field
1193 # is omitted if target doesn't support memory hotplug
1194 # (i.e. CONFIG_MEM_DEVICE not defined at build time).
1195 #
1196 # Since: 2.11.0
1197 ##
1198 { 'struct': 'MemoryInfo',
1199 'data' : { 'base-memory': 'size', '*plugged-memory': 'size' } }
1200
1201 ##
1202 # @query-memory-size-summary:
1203 #
1204 # Return the amount of initially allocated and present hotpluggable (if
1205 # enabled) memory in bytes.
1206 #
1207 # Example:
1208 #
1209 # -> { "execute": "query-memory-size-summary" }
1210 # <- { "return": { "base-memory": 4294967296, "plugged-memory": 0 } }
1211 #
1212 # Since: 2.11.0
1213 ##
1214 { 'command': 'query-memory-size-summary', 'returns': 'MemoryInfo' }
1215
1216
1217 ##
1218 # @AddfdInfo:
1219 #
1220 # Information about a file descriptor that was added to an fd set.
1221 #
1222 # @fdset-id: The ID of the fd set that @fd was added to.
1223 #
1224 # @fd: The file descriptor that was received via SCM rights and
1225 # added to the fd set.
1226 #
1227 # Since: 1.2.0
1228 ##
1229 { 'struct': 'AddfdInfo', 'data': {'fdset-id': 'int', 'fd': 'int'} }
1230
1231 ##
1232 # @add-fd:
1233 #
1234 # Add a file descriptor, that was passed via SCM rights, to an fd set.
1235 #
1236 # @fdset-id: The ID of the fd set to add the file descriptor to.
1237 #
1238 # @opaque: A free-form string that can be used to describe the fd.
1239 #
1240 # Returns: @AddfdInfo on success
1241 #
1242 # If file descriptor was not received, FdNotSupplied
1243 #
1244 # If @fdset-id is a negative value, InvalidParameterValue
1245 #
1246 # Notes: The list of fd sets is shared by all monitor connections.
1247 #
1248 # If @fdset-id is not specified, a new fd set will be created.
1249 #
1250 # Since: 1.2.0
1251 #
1252 # Example:
1253 #
1254 # -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1255 # <- { "return": { "fdset-id": 1, "fd": 3 } }
1256 #
1257 ##
1258 { 'command': 'add-fd',
1259 'data': { '*fdset-id': 'int',
1260 '*opaque': 'str' },
1261 'returns': 'AddfdInfo' }
1262
1263 ##
1264 # @remove-fd:
1265 #
1266 # Remove a file descriptor from an fd set.
1267 #
1268 # @fdset-id: The ID of the fd set that the file descriptor belongs to.
1269 #
1270 # @fd: The file descriptor that is to be removed.
1271 #
1272 # Returns: Nothing on success
1273 # If @fdset-id or @fd is not found, FdNotFound
1274 #
1275 # Since: 1.2.0
1276 #
1277 # Notes: The list of fd sets is shared by all monitor connections.
1278 #
1279 # If @fd is not specified, all file descriptors in @fdset-id
1280 # will be removed.
1281 #
1282 # Example:
1283 #
1284 # -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1285 # <- { "return": {} }
1286 #
1287 ##
1288 { 'command': 'remove-fd', 'data': {'fdset-id': 'int', '*fd': 'int'} }
1289
1290 ##
1291 # @FdsetFdInfo:
1292 #
1293 # Information about a file descriptor that belongs to an fd set.
1294 #
1295 # @fd: The file descriptor value.
1296 #
1297 # @opaque: A free-form string that can be used to describe the fd.
1298 #
1299 # Since: 1.2.0
1300 ##
1301 { 'struct': 'FdsetFdInfo',
1302 'data': {'fd': 'int', '*opaque': 'str'} }
1303
1304 ##
1305 # @FdsetInfo:
1306 #
1307 # Information about an fd set.
1308 #
1309 # @fdset-id: The ID of the fd set.
1310 #
1311 # @fds: A list of file descriptors that belong to this fd set.
1312 #
1313 # Since: 1.2.0
1314 ##
1315 { 'struct': 'FdsetInfo',
1316 'data': {'fdset-id': 'int', 'fds': ['FdsetFdInfo']} }
1317
1318 ##
1319 # @query-fdsets:
1320 #
1321 # Return information describing all fd sets.
1322 #
1323 # Returns: A list of @FdsetInfo
1324 #
1325 # Since: 1.2.0
1326 #
1327 # Note: The list of fd sets is shared by all monitor connections.
1328 #
1329 # Example:
1330 #
1331 # -> { "execute": "query-fdsets" }
1332 # <- { "return": [
1333 # {
1334 # "fds": [
1335 # {
1336 # "fd": 30,
1337 # "opaque": "rdonly:/path/to/file"
1338 # },
1339 # {
1340 # "fd": 24,
1341 # "opaque": "rdwr:/path/to/file"
1342 # }
1343 # ],
1344 # "fdset-id": 1
1345 # },
1346 # {
1347 # "fds": [
1348 # {
1349 # "fd": 28
1350 # },
1351 # {
1352 # "fd": 29
1353 # }
1354 # ],
1355 # "fdset-id": 0
1356 # }
1357 # ]
1358 # }
1359 #
1360 ##
1361 { 'command': 'query-fdsets', 'returns': ['FdsetInfo'] }
1362
1363 ##
1364 # @AcpiTableOptions:
1365 #
1366 # Specify an ACPI table on the command line to load.
1367 #
1368 # At most one of @file and @data can be specified. The list of files specified
1369 # by any one of them is loaded and concatenated in order. If both are omitted,
1370 # @data is implied.
1371 #
1372 # Other fields / optargs can be used to override fields of the generic ACPI
1373 # table header; refer to the ACPI specification 5.0, section 5.2.6 System
1374 # Description Table Header. If a header field is not overridden, then the
1375 # corresponding value from the concatenated blob is used (in case of @file), or
1376 # it is filled in with a hard-coded value (in case of @data).
1377 #
1378 # String fields are copied into the matching ACPI member from lowest address
1379 # upwards, and silently truncated / NUL-padded to length.
1380 #
1381 # @sig: table signature / identifier (4 bytes)
1382 #
1383 # @rev: table revision number (dependent on signature, 1 byte)
1384 #
1385 # @oem_id: OEM identifier (6 bytes)
1386 #
1387 # @oem_table_id: OEM table identifier (8 bytes)
1388 #
1389 # @oem_rev: OEM-supplied revision number (4 bytes)
1390 #
1391 # @asl_compiler_id: identifier of the utility that created the table
1392 # (4 bytes)
1393 #
1394 # @asl_compiler_rev: revision number of the utility that created the
1395 # table (4 bytes)
1396 #
1397 # @file: colon (:) separated list of pathnames to load and
1398 # concatenate as table data. The resultant binary blob is expected to
1399 # have an ACPI table header. At least one file is required. This field
1400 # excludes @data.
1401 #
1402 # @data: colon (:) separated list of pathnames to load and
1403 # concatenate as table data. The resultant binary blob must not have an
1404 # ACPI table header. At least one file is required. This field excludes
1405 # @file.
1406 #
1407 # Since: 1.5
1408 ##
1409 { 'struct': 'AcpiTableOptions',
1410 'data': {
1411 '*sig': 'str',
1412 '*rev': 'uint8',
1413 '*oem_id': 'str',
1414 '*oem_table_id': 'str',
1415 '*oem_rev': 'uint32',
1416 '*asl_compiler_id': 'str',
1417 '*asl_compiler_rev': 'uint32',
1418 '*file': 'str',
1419 '*data': 'str' }}
1420
1421 ##
1422 # @CommandLineParameterType:
1423 #
1424 # Possible types for an option parameter.
1425 #
1426 # @string: accepts a character string
1427 #
1428 # @boolean: accepts "on" or "off"
1429 #
1430 # @number: accepts a number
1431 #
1432 # @size: accepts a number followed by an optional suffix (K)ilo,
1433 # (M)ega, (G)iga, (T)era
1434 #
1435 # Since: 1.5
1436 ##
1437 { 'enum': 'CommandLineParameterType',
1438 'data': ['string', 'boolean', 'number', 'size'] }
1439
1440 ##
1441 # @CommandLineParameterInfo:
1442 #
1443 # Details about a single parameter of a command line option.
1444 #
1445 # @name: parameter name
1446 #
1447 # @type: parameter @CommandLineParameterType
1448 #
1449 # @help: human readable text string, not suitable for parsing.
1450 #
1451 # @default: default value string (since 2.1)
1452 #
1453 # Since: 1.5
1454 ##
1455 { 'struct': 'CommandLineParameterInfo',
1456 'data': { 'name': 'str',
1457 'type': 'CommandLineParameterType',
1458 '*help': 'str',
1459 '*default': 'str' } }
1460
1461 ##
1462 # @CommandLineOptionInfo:
1463 #
1464 # Details about a command line option, including its list of parameter details
1465 #
1466 # @option: option name
1467 #
1468 # @parameters: an array of @CommandLineParameterInfo
1469 #
1470 # Since: 1.5
1471 ##
1472 { 'struct': 'CommandLineOptionInfo',
1473 'data': { 'option': 'str', 'parameters': ['CommandLineParameterInfo'] } }
1474
1475 ##
1476 # @query-command-line-options:
1477 #
1478 # Query command line option schema.
1479 #
1480 # @option: option name
1481 #
1482 # Returns: list of @CommandLineOptionInfo for all options (or for the given
1483 # @option). Returns an error if the given @option doesn't exist.
1484 #
1485 # Since: 1.5
1486 #
1487 # Example:
1488 #
1489 # -> { "execute": "query-command-line-options",
1490 # "arguments": { "option": "option-rom" } }
1491 # <- { "return": [
1492 # {
1493 # "parameters": [
1494 # {
1495 # "name": "romfile",
1496 # "type": "string"
1497 # },
1498 # {
1499 # "name": "bootindex",
1500 # "type": "number"
1501 # }
1502 # ],
1503 # "option": "option-rom"
1504 # }
1505 # ]
1506 # }
1507 #
1508 ##
1509 {'command': 'query-command-line-options',
1510 'data': { '*option': 'str' },
1511 'returns': ['CommandLineOptionInfo'],
1512 'allow-preconfig': true }
1513
1514 ##
1515 # @PCDIMMDeviceInfo:
1516 #
1517 # PCDIMMDevice state information
1518 #
1519 # @id: device's ID
1520 #
1521 # @addr: physical address, where device is mapped
1522 #
1523 # @size: size of memory that the device provides
1524 #
1525 # @slot: slot number at which device is plugged in
1526 #
1527 # @node: NUMA node number where device is plugged in
1528 #
1529 # @memdev: memory backend linked with device
1530 #
1531 # @hotplugged: true if device was hotplugged
1532 #
1533 # @hotpluggable: true if device if could be added/removed while machine is running
1534 #
1535 # Since: 2.1
1536 ##
1537 { 'struct': 'PCDIMMDeviceInfo',
1538 'data': { '*id': 'str',
1539 'addr': 'int',
1540 'size': 'int',
1541 'slot': 'int',
1542 'node': 'int',
1543 'memdev': 'str',
1544 'hotplugged': 'bool',
1545 'hotpluggable': 'bool'
1546 }
1547 }
1548
1549 ##
1550 # @VirtioPMEMDeviceInfo:
1551 #
1552 # VirtioPMEM state information
1553 #
1554 # @id: device's ID
1555 #
1556 # @memaddr: physical address in memory, where device is mapped
1557 #
1558 # @size: size of memory that the device provides
1559 #
1560 # @memdev: memory backend linked with device
1561 #
1562 # Since: 4.1
1563 ##
1564 { 'struct': 'VirtioPMEMDeviceInfo',
1565 'data': { '*id': 'str',
1566 'memaddr': 'size',
1567 'size': 'size',
1568 'memdev': 'str'
1569 }
1570 }
1571
1572 ##
1573 # @MemoryDeviceInfo:
1574 #
1575 # Union containing information about a memory device
1576 #
1577 # nvdimm is included since 2.12. virtio-pmem is included since 4.1.
1578 #
1579 # Since: 2.1
1580 ##
1581 { 'union': 'MemoryDeviceInfo',
1582 'data': { 'dimm': 'PCDIMMDeviceInfo',
1583 'nvdimm': 'PCDIMMDeviceInfo',
1584 'virtio-pmem': 'VirtioPMEMDeviceInfo'
1585 }
1586 }
1587
1588 ##
1589 # @query-memory-devices:
1590 #
1591 # Lists available memory devices and their state
1592 #
1593 # Since: 2.1
1594 #
1595 # Example:
1596 #
1597 # -> { "execute": "query-memory-devices" }
1598 # <- { "return": [ { "data":
1599 # { "addr": 5368709120,
1600 # "hotpluggable": true,
1601 # "hotplugged": true,
1602 # "id": "d1",
1603 # "memdev": "/objects/memX",
1604 # "node": 0,
1605 # "size": 1073741824,
1606 # "slot": 0},
1607 # "type": "dimm"
1608 # } ] }
1609 #
1610 ##
1611 { 'command': 'query-memory-devices', 'returns': ['MemoryDeviceInfo'] }
1612
1613 ##
1614 # @MEM_UNPLUG_ERROR:
1615 #
1616 # Emitted when memory hot unplug error occurs.
1617 #
1618 # @device: device name
1619 #
1620 # @msg: Informative message
1621 #
1622 # Since: 2.4
1623 #
1624 # Example:
1625 #
1626 # <- { "event": "MEM_UNPLUG_ERROR"
1627 # "data": { "device": "dimm1",
1628 # "msg": "acpi: device unplug for unsupported device"
1629 # },
1630 # "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
1631 #
1632 ##
1633 { 'event': 'MEM_UNPLUG_ERROR',
1634 'data': { 'device': 'str', 'msg': 'str' } }
1635
1636 ##
1637 # @ACPISlotType:
1638 #
1639 # @DIMM: memory slot
1640 # @CPU: logical CPU slot (since 2.7)
1641 ##
1642 { 'enum': 'ACPISlotType', 'data': [ 'DIMM', 'CPU' ] }
1643
1644 ##
1645 # @ACPIOSTInfo:
1646 #
1647 # OSPM Status Indication for a device
1648 # For description of possible values of @source and @status fields
1649 # see "_OST (OSPM Status Indication)" chapter of ACPI5.0 spec.
1650 #
1651 # @device: device ID associated with slot
1652 #
1653 # @slot: slot ID, unique per slot of a given @slot-type
1654 #
1655 # @slot-type: type of the slot
1656 #
1657 # @source: an integer containing the source event
1658 #
1659 # @status: an integer containing the status code
1660 #
1661 # Since: 2.1
1662 ##
1663 { 'struct': 'ACPIOSTInfo',
1664 'data' : { '*device': 'str',
1665 'slot': 'str',
1666 'slot-type': 'ACPISlotType',
1667 'source': 'int',
1668 'status': 'int' } }
1669
1670 ##
1671 # @query-acpi-ospm-status:
1672 #
1673 # Return a list of ACPIOSTInfo for devices that support status
1674 # reporting via ACPI _OST method.
1675 #
1676 # Since: 2.1
1677 #
1678 # Example:
1679 #
1680 # -> { "execute": "query-acpi-ospm-status" }
1681 # <- { "return": [ { "device": "d1", "slot": "0", "slot-type": "DIMM", "source": 1, "status": 0},
1682 # { "slot": "1", "slot-type": "DIMM", "source": 0, "status": 0},
1683 # { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
1684 # { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
1685 # ]}
1686 #
1687 ##
1688 { 'command': 'query-acpi-ospm-status', 'returns': ['ACPIOSTInfo'] }
1689
1690 ##
1691 # @ACPI_DEVICE_OST:
1692 #
1693 # Emitted when guest executes ACPI _OST method.
1694 #
1695 # @info: OSPM Status Indication
1696 #
1697 # Since: 2.1
1698 #
1699 # Example:
1700 #
1701 # <- { "event": "ACPI_DEVICE_OST",
1702 # "data": { "device": "d1", "slot": "0",
1703 # "slot-type": "DIMM", "source": 1, "status": 0 } }
1704 #
1705 ##
1706 { 'event': 'ACPI_DEVICE_OST',
1707 'data': { 'info': 'ACPIOSTInfo' } }
1708
1709 ##
1710 # @ReplayMode:
1711 #
1712 # Mode of the replay subsystem.
1713 #
1714 # @none: normal execution mode. Replay or record are not enabled.
1715 #
1716 # @record: record mode. All non-deterministic data is written into the
1717 # replay log.
1718 #
1719 # @play: replay mode. Non-deterministic data required for system execution
1720 # is read from the log.
1721 #
1722 # Since: 2.5
1723 ##
1724 { 'enum': 'ReplayMode',
1725 'data': [ 'none', 'record', 'play' ] }
1726
1727 ##
1728 # @xen-load-devices-state:
1729 #
1730 # Load the state of all devices from file. The RAM and the block devices
1731 # of the VM are not loaded by this command.
1732 #
1733 # @filename: the file to load the state of the devices from as binary
1734 # data. See xen-save-devices-state.txt for a description of the binary
1735 # format.
1736 #
1737 # Since: 2.7
1738 #
1739 # Example:
1740 #
1741 # -> { "execute": "xen-load-devices-state",
1742 # "arguments": { "filename": "/tmp/resume" } }
1743 # <- { "return": {} }
1744 #
1745 ##
1746 { 'command': 'xen-load-devices-state', 'data': {'filename': 'str'} }
1747
1748 ##
1749 # @GuidInfo:
1750 #
1751 # GUID information.
1752 #
1753 # @guid: the globally unique identifier
1754 #
1755 # Since: 2.9
1756 ##
1757 { 'struct': 'GuidInfo', 'data': {'guid': 'str'} }
1758
1759 ##
1760 # @query-vm-generation-id:
1761 #
1762 # Show Virtual Machine Generation ID
1763 #
1764 # Since: 2.9
1765 ##
1766 { 'command': 'query-vm-generation-id', 'returns': 'GuidInfo' }
1767