]> git.ipfire.org Git - thirdparty/qemu.git/blob - qapi/misc.json
qapi: Delete all the "foo: dropped in n.n" notes
[thirdparty/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 # - If the balloon driver is enabled but not functional because the KVM
435 # kernel module cannot support it, KvmMissingCap
436 # - If no balloon device is present, DeviceNotActive
437 #
438 # Since: 0.14.0
439 #
440 # Example:
441 #
442 # -> { "execute": "query-balloon" }
443 # <- { "return": {
444 # "actual": 1073741824,
445 # }
446 # }
447 #
448 ##
449 { 'command': 'query-balloon', 'returns': 'BalloonInfo' }
450
451 ##
452 # @BALLOON_CHANGE:
453 #
454 # Emitted when the guest changes the actual BALLOON level. This value is
455 # equivalent to the @actual field return by the 'query-balloon' command
456 #
457 # @actual: actual level of the guest memory balloon in bytes
458 #
459 # Note: this event is rate-limited.
460 #
461 # Since: 1.2
462 #
463 # Example:
464 #
465 # <- { "event": "BALLOON_CHANGE",
466 # "data": { "actual": 944766976 },
467 # "timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
468 #
469 ##
470 { 'event': 'BALLOON_CHANGE',
471 'data': { 'actual': 'int' } }
472
473 ##
474 # @PciMemoryRange:
475 #
476 # A PCI device memory region
477 #
478 # @base: the starting address (guest physical)
479 #
480 # @limit: the ending address (guest physical)
481 #
482 # Since: 0.14.0
483 ##
484 { 'struct': 'PciMemoryRange', 'data': {'base': 'int', 'limit': 'int'} }
485
486 ##
487 # @PciMemoryRegion:
488 #
489 # Information about a PCI device I/O region.
490 #
491 # @bar: the index of the Base Address Register for this region
492 #
493 # @type: - 'io' if the region is a PIO region
494 # - 'memory' if the region is a MMIO region
495 #
496 # @size: memory size
497 #
498 # @prefetch: if @type is 'memory', true if the memory is prefetchable
499 #
500 # @mem_type_64: if @type is 'memory', true if the BAR is 64-bit
501 #
502 # Since: 0.14.0
503 ##
504 { 'struct': 'PciMemoryRegion',
505 'data': {'bar': 'int', 'type': 'str', 'address': 'int', 'size': 'int',
506 '*prefetch': 'bool', '*mem_type_64': 'bool' } }
507
508 ##
509 # @PciBusInfo:
510 #
511 # Information about a bus of a PCI Bridge device
512 #
513 # @number: primary bus interface number. This should be the number of the
514 # bus the device resides on.
515 #
516 # @secondary: secondary bus interface number. This is the number of the
517 # main bus for the bridge
518 #
519 # @subordinate: This is the highest number bus that resides below the
520 # bridge.
521 #
522 # @io_range: The PIO range for all devices on this bridge
523 #
524 # @memory_range: The MMIO range for all devices on this bridge
525 #
526 # @prefetchable_range: The range of prefetchable MMIO for all devices on
527 # this bridge
528 #
529 # Since: 2.4
530 ##
531 { 'struct': 'PciBusInfo',
532 'data': {'number': 'int', 'secondary': 'int', 'subordinate': 'int',
533 'io_range': 'PciMemoryRange',
534 'memory_range': 'PciMemoryRange',
535 'prefetchable_range': 'PciMemoryRange' } }
536
537 ##
538 # @PciBridgeInfo:
539 #
540 # Information about a PCI Bridge device
541 #
542 # @bus: information about the bus the device resides on
543 #
544 # @devices: a list of @PciDeviceInfo for each device on this bridge
545 #
546 # Since: 0.14.0
547 ##
548 { 'struct': 'PciBridgeInfo',
549 'data': {'bus': 'PciBusInfo', '*devices': ['PciDeviceInfo']} }
550
551 ##
552 # @PciDeviceClass:
553 #
554 # Information about the Class of a PCI device
555 #
556 # @desc: a string description of the device's class
557 #
558 # @class: the class code of the device
559 #
560 # Since: 2.4
561 ##
562 { 'struct': 'PciDeviceClass',
563 'data': {'*desc': 'str', 'class': 'int'} }
564
565 ##
566 # @PciDeviceId:
567 #
568 # Information about the Id of a PCI device
569 #
570 # @device: the PCI device id
571 #
572 # @vendor: the PCI vendor id
573 #
574 # @subsystem: the PCI subsystem id (since 3.1)
575 #
576 # @subsystem-vendor: the PCI subsystem vendor id (since 3.1)
577 #
578 # Since: 2.4
579 ##
580 { 'struct': 'PciDeviceId',
581 'data': {'device': 'int', 'vendor': 'int', '*subsystem': 'int',
582 '*subsystem-vendor': 'int'} }
583
584 ##
585 # @PciDeviceInfo:
586 #
587 # Information about a PCI device
588 #
589 # @bus: the bus number of the device
590 #
591 # @slot: the slot the device is located in
592 #
593 # @function: the function of the slot used by the device
594 #
595 # @class_info: the class of the device
596 #
597 # @id: the PCI device id
598 #
599 # @irq: if an IRQ is assigned to the device, the IRQ number
600 #
601 # @qdev_id: the device name of the PCI device
602 #
603 # @pci_bridge: if the device is a PCI bridge, the bridge information
604 #
605 # @regions: a list of the PCI I/O regions associated with the device
606 #
607 # Notes: the contents of @class_info.desc are not stable and should only be
608 # treated as informational.
609 #
610 # Since: 0.14.0
611 ##
612 { 'struct': 'PciDeviceInfo',
613 'data': {'bus': 'int', 'slot': 'int', 'function': 'int',
614 'class_info': 'PciDeviceClass', 'id': 'PciDeviceId',
615 '*irq': 'int', 'qdev_id': 'str', '*pci_bridge': 'PciBridgeInfo',
616 'regions': ['PciMemoryRegion']} }
617
618 ##
619 # @PciInfo:
620 #
621 # Information about a PCI bus
622 #
623 # @bus: the bus index
624 #
625 # @devices: a list of devices on this bus
626 #
627 # Since: 0.14.0
628 ##
629 { 'struct': 'PciInfo', 'data': {'bus': 'int', 'devices': ['PciDeviceInfo']} }
630
631 ##
632 # @query-pci:
633 #
634 # Return information about the PCI bus topology of the guest.
635 #
636 # Returns: a list of @PciInfo for each PCI bus. Each bus is
637 # represented by a json-object, which has a key with a json-array of
638 # all PCI devices attached to it. Each device is represented by a
639 # json-object.
640 #
641 # Since: 0.14.0
642 #
643 # Example:
644 #
645 # -> { "execute": "query-pci" }
646 # <- { "return": [
647 # {
648 # "bus": 0,
649 # "devices": [
650 # {
651 # "bus": 0,
652 # "qdev_id": "",
653 # "slot": 0,
654 # "class_info": {
655 # "class": 1536,
656 # "desc": "Host bridge"
657 # },
658 # "id": {
659 # "device": 32902,
660 # "vendor": 4663
661 # },
662 # "function": 0,
663 # "regions": [
664 # ]
665 # },
666 # {
667 # "bus": 0,
668 # "qdev_id": "",
669 # "slot": 1,
670 # "class_info": {
671 # "class": 1537,
672 # "desc": "ISA bridge"
673 # },
674 # "id": {
675 # "device": 32902,
676 # "vendor": 28672
677 # },
678 # "function": 0,
679 # "regions": [
680 # ]
681 # },
682 # {
683 # "bus": 0,
684 # "qdev_id": "",
685 # "slot": 1,
686 # "class_info": {
687 # "class": 257,
688 # "desc": "IDE controller"
689 # },
690 # "id": {
691 # "device": 32902,
692 # "vendor": 28688
693 # },
694 # "function": 1,
695 # "regions": [
696 # {
697 # "bar": 4,
698 # "size": 16,
699 # "address": 49152,
700 # "type": "io"
701 # }
702 # ]
703 # },
704 # {
705 # "bus": 0,
706 # "qdev_id": "",
707 # "slot": 2,
708 # "class_info": {
709 # "class": 768,
710 # "desc": "VGA controller"
711 # },
712 # "id": {
713 # "device": 4115,
714 # "vendor": 184
715 # },
716 # "function": 0,
717 # "regions": [
718 # {
719 # "prefetch": true,
720 # "mem_type_64": false,
721 # "bar": 0,
722 # "size": 33554432,
723 # "address": 4026531840,
724 # "type": "memory"
725 # },
726 # {
727 # "prefetch": false,
728 # "mem_type_64": false,
729 # "bar": 1,
730 # "size": 4096,
731 # "address": 4060086272,
732 # "type": "memory"
733 # },
734 # {
735 # "prefetch": false,
736 # "mem_type_64": false,
737 # "bar": 6,
738 # "size": 65536,
739 # "address": -1,
740 # "type": "memory"
741 # }
742 # ]
743 # },
744 # {
745 # "bus": 0,
746 # "qdev_id": "",
747 # "irq": 11,
748 # "slot": 4,
749 # "class_info": {
750 # "class": 1280,
751 # "desc": "RAM controller"
752 # },
753 # "id": {
754 # "device": 6900,
755 # "vendor": 4098
756 # },
757 # "function": 0,
758 # "regions": [
759 # {
760 # "bar": 0,
761 # "size": 32,
762 # "address": 49280,
763 # "type": "io"
764 # }
765 # ]
766 # }
767 # ]
768 # }
769 # ]
770 # }
771 #
772 # Note: This example has been shortened as the real response is too long.
773 #
774 ##
775 { 'command': 'query-pci', 'returns': ['PciInfo'] }
776
777 ##
778 # @quit:
779 #
780 # This command will cause the QEMU process to exit gracefully. While every
781 # attempt is made to send the QMP response before terminating, this is not
782 # guaranteed. When using this interface, a premature EOF would not be
783 # unexpected.
784 #
785 # Since: 0.14.0
786 #
787 # Example:
788 #
789 # -> { "execute": "quit" }
790 # <- { "return": {} }
791 ##
792 { 'command': 'quit' }
793
794 ##
795 # @stop:
796 #
797 # Stop all guest VCPU execution.
798 #
799 # Since: 0.14.0
800 #
801 # Notes: This function will succeed even if the guest is already in the stopped
802 # state. In "inmigrate" state, it will ensure that the guest
803 # remains paused once migration finishes, as if the -S option was
804 # passed on the command line.
805 #
806 # Example:
807 #
808 # -> { "execute": "stop" }
809 # <- { "return": {} }
810 #
811 ##
812 { 'command': 'stop' }
813
814 ##
815 # @system_reset:
816 #
817 # Performs a hard reset of a guest.
818 #
819 # Since: 0.14.0
820 #
821 # Example:
822 #
823 # -> { "execute": "system_reset" }
824 # <- { "return": {} }
825 #
826 ##
827 { 'command': 'system_reset' }
828
829 ##
830 # @system_powerdown:
831 #
832 # Requests that a guest perform a powerdown operation.
833 #
834 # Since: 0.14.0
835 #
836 # Notes: A guest may or may not respond to this command. This command
837 # returning does not indicate that a guest has accepted the request or
838 # that it has shut down. Many guests will respond to this command by
839 # prompting the user in some way.
840 # Example:
841 #
842 # -> { "execute": "system_powerdown" }
843 # <- { "return": {} }
844 #
845 ##
846 { 'command': 'system_powerdown' }
847
848 ##
849 # @memsave:
850 #
851 # Save a portion of guest memory to a file.
852 #
853 # @val: the virtual address of the guest to start from
854 #
855 # @size: the size of memory region to save
856 #
857 # @filename: the file to save the memory to as binary data
858 #
859 # @cpu-index: the index of the virtual CPU to use for translating the
860 # virtual address (defaults to CPU 0)
861 #
862 # Returns: Nothing on success
863 #
864 # Since: 0.14.0
865 #
866 # Notes: Errors were not reliably returned until 1.1
867 #
868 # Example:
869 #
870 # -> { "execute": "memsave",
871 # "arguments": { "val": 10,
872 # "size": 100,
873 # "filename": "/tmp/virtual-mem-dump" } }
874 # <- { "return": {} }
875 #
876 ##
877 { 'command': 'memsave',
878 'data': {'val': 'int', 'size': 'int', 'filename': 'str', '*cpu-index': 'int'} }
879
880 ##
881 # @pmemsave:
882 #
883 # Save a portion of guest physical memory to a file.
884 #
885 # @val: the physical address of the guest to start from
886 #
887 # @size: the size of memory region to save
888 #
889 # @filename: the file to save the memory to as binary data
890 #
891 # Returns: Nothing on success
892 #
893 # Since: 0.14.0
894 #
895 # Notes: Errors were not reliably returned until 1.1
896 #
897 # Example:
898 #
899 # -> { "execute": "pmemsave",
900 # "arguments": { "val": 10,
901 # "size": 100,
902 # "filename": "/tmp/physical-mem-dump" } }
903 # <- { "return": {} }
904 #
905 ##
906 { 'command': 'pmemsave',
907 'data': {'val': 'int', 'size': 'int', 'filename': 'str'} }
908
909 ##
910 # @cont:
911 #
912 # Resume guest VCPU execution.
913 #
914 # Since: 0.14.0
915 #
916 # Returns: If successful, nothing
917 #
918 # Notes: This command will succeed if the guest is currently running. It
919 # will also succeed if the guest is in the "inmigrate" state; in
920 # this case, the effect of the command is to make sure the guest
921 # starts once migration finishes, removing the effect of the -S
922 # command line option if it was passed.
923 #
924 # Example:
925 #
926 # -> { "execute": "cont" }
927 # <- { "return": {} }
928 #
929 ##
930 { 'command': 'cont' }
931
932 ##
933 # @x-exit-preconfig:
934 #
935 # Exit from "preconfig" state
936 #
937 # This command makes QEMU exit the preconfig state and proceed with
938 # VM initialization using configuration data provided on the command line
939 # and via the QMP monitor during the preconfig state. The command is only
940 # available during the preconfig state (i.e. when the --preconfig command
941 # line option was in use).
942 #
943 # Since 3.0
944 #
945 # Returns: nothing
946 #
947 # Example:
948 #
949 # -> { "execute": "x-exit-preconfig" }
950 # <- { "return": {} }
951 #
952 ##
953 { 'command': 'x-exit-preconfig', 'allow-preconfig': true }
954
955 ##
956 # @system_wakeup:
957 #
958 # Wake up guest from suspend. If the guest has wake-up from suspend
959 # support enabled (wakeup-suspend-support flag from
960 # query-current-machine), wake-up guest from suspend if the guest is
961 # in SUSPENDED state. Return an error otherwise.
962 #
963 # Since: 1.1
964 #
965 # Returns: nothing.
966 #
967 # Note: prior to 4.0, this command does nothing in case the guest
968 # isn't suspended.
969 #
970 # Example:
971 #
972 # -> { "execute": "system_wakeup" }
973 # <- { "return": {} }
974 #
975 ##
976 { 'command': 'system_wakeup' }
977
978 ##
979 # @inject-nmi:
980 #
981 # Injects a Non-Maskable Interrupt into the default CPU (x86/s390) or all CPUs (ppc64).
982 # The command fails when the guest doesn't support injecting.
983 #
984 # Returns: If successful, nothing
985 #
986 # Since: 0.14.0
987 #
988 # Note: prior to 2.1, this command was only supported for x86 and s390 VMs
989 #
990 # Example:
991 #
992 # -> { "execute": "inject-nmi" }
993 # <- { "return": {} }
994 #
995 ##
996 { 'command': 'inject-nmi' }
997
998 ##
999 # @balloon:
1000 #
1001 # Request the balloon driver to change its balloon size.
1002 #
1003 # @value: the target size of the balloon in bytes
1004 #
1005 # Returns: - Nothing on success
1006 # - If the balloon driver is enabled but not functional because the KVM
1007 # kernel module cannot support it, KvmMissingCap
1008 # - If no balloon device is present, DeviceNotActive
1009 #
1010 # Notes: This command just issues a request to the guest. When it returns,
1011 # the balloon size may not have changed. A guest can change the balloon
1012 # size independent of this command.
1013 #
1014 # Since: 0.14.0
1015 #
1016 # Example:
1017 #
1018 # -> { "execute": "balloon", "arguments": { "value": 536870912 } }
1019 # <- { "return": {} }
1020 #
1021 ##
1022 { 'command': 'balloon', 'data': {'value': 'int'} }
1023
1024 ##
1025 # @human-monitor-command:
1026 #
1027 # Execute a command on the human monitor and return the output.
1028 #
1029 # @command-line: the command to execute in the human monitor
1030 #
1031 # @cpu-index: The CPU to use for commands that require an implicit CPU
1032 #
1033 # Features:
1034 # @savevm-monitor-nodes: If present, HMP command savevm only snapshots
1035 # monitor-owned nodes if they have no parents.
1036 # This allows the use of 'savevm' with
1037 # -blockdev. (since 4.2)
1038 #
1039 # Returns: the output of the command as a string
1040 #
1041 # Since: 0.14.0
1042 #
1043 # Notes: This command only exists as a stop-gap. Its use is highly
1044 # discouraged. The semantics of this command are not
1045 # guaranteed: this means that command names, arguments and
1046 # responses can change or be removed at ANY time. Applications
1047 # that rely on long term stability guarantees should NOT
1048 # use this command.
1049 #
1050 # Known limitations:
1051 #
1052 # * This command is stateless, this means that commands that depend
1053 # on state information (such as getfd) might not work
1054 #
1055 # * Commands that prompt the user for data don't currently work
1056 #
1057 # Example:
1058 #
1059 # -> { "execute": "human-monitor-command",
1060 # "arguments": { "command-line": "info kvm" } }
1061 # <- { "return": "kvm support: enabled\r\n" }
1062 #
1063 ##
1064 { 'command': 'human-monitor-command',
1065 'data': {'command-line': 'str', '*cpu-index': 'int'},
1066 'returns': 'str',
1067 'features': [ 'savevm-monitor-nodes' ] }
1068
1069 ##
1070 # @change:
1071 #
1072 # This command is multiple commands multiplexed together.
1073 #
1074 # @device: This is normally the name of a block device but it may also be 'vnc'.
1075 # when it's 'vnc', then sub command depends on @target
1076 #
1077 # @target: If @device is a block device, then this is the new filename.
1078 # If @device is 'vnc', then if the value 'password' selects the vnc
1079 # change password command. Otherwise, this specifies a new server URI
1080 # address to listen to for VNC connections.
1081 #
1082 # @arg: If @device is a block device, then this is an optional format to open
1083 # the device with.
1084 # If @device is 'vnc' and @target is 'password', this is the new VNC
1085 # password to set. See change-vnc-password for additional notes.
1086 #
1087 # Returns: - Nothing on success.
1088 # - If @device is not a valid block device, DeviceNotFound
1089 #
1090 # Notes: This interface is deprecated, and it is strongly recommended that you
1091 # avoid using it. For changing block devices, use
1092 # blockdev-change-medium; for changing VNC parameters, use
1093 # change-vnc-password.
1094 #
1095 # Since: 0.14.0
1096 #
1097 # Example:
1098 #
1099 # 1. Change a removable medium
1100 #
1101 # -> { "execute": "change",
1102 # "arguments": { "device": "ide1-cd0",
1103 # "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } }
1104 # <- { "return": {} }
1105 #
1106 # 2. Change VNC password
1107 #
1108 # -> { "execute": "change",
1109 # "arguments": { "device": "vnc", "target": "password",
1110 # "arg": "foobar1" } }
1111 # <- { "return": {} }
1112 #
1113 ##
1114 { 'command': 'change',
1115 'data': {'device': 'str', 'target': 'str', '*arg': 'str'} }
1116
1117 ##
1118 # @xen-set-global-dirty-log:
1119 #
1120 # Enable or disable the global dirty log mode.
1121 #
1122 # @enable: true to enable, false to disable.
1123 #
1124 # Returns: nothing
1125 #
1126 # Since: 1.3
1127 #
1128 # Example:
1129 #
1130 # -> { "execute": "xen-set-global-dirty-log",
1131 # "arguments": { "enable": true } }
1132 # <- { "return": {} }
1133 #
1134 ##
1135 { 'command': 'xen-set-global-dirty-log', 'data': { 'enable': 'bool' } }
1136
1137 ##
1138 # @getfd:
1139 #
1140 # Receive a file descriptor via SCM rights and assign it a name
1141 #
1142 # @fdname: file descriptor name
1143 #
1144 # Returns: Nothing on success
1145 #
1146 # Since: 0.14.0
1147 #
1148 # Notes: If @fdname already exists, the file descriptor assigned to
1149 # it will be closed and replaced by the received file
1150 # descriptor.
1151 #
1152 # The 'closefd' command can be used to explicitly close the
1153 # file descriptor when it is no longer needed.
1154 #
1155 # Example:
1156 #
1157 # -> { "execute": "getfd", "arguments": { "fdname": "fd1" } }
1158 # <- { "return": {} }
1159 #
1160 ##
1161 { 'command': 'getfd', 'data': {'fdname': 'str'} }
1162
1163 ##
1164 # @closefd:
1165 #
1166 # Close a file descriptor previously passed via SCM rights
1167 #
1168 # @fdname: file descriptor name
1169 #
1170 # Returns: Nothing on success
1171 #
1172 # Since: 0.14.0
1173 #
1174 # Example:
1175 #
1176 # -> { "execute": "closefd", "arguments": { "fdname": "fd1" } }
1177 # <- { "return": {} }
1178 #
1179 ##
1180 { 'command': 'closefd', 'data': {'fdname': 'str'} }
1181
1182 ##
1183 # @MemoryInfo:
1184 #
1185 # Actual memory information in bytes.
1186 #
1187 # @base-memory: size of "base" memory specified with command line
1188 # option -m.
1189 #
1190 # @plugged-memory: size of memory that can be hot-unplugged. This field
1191 # is omitted if target doesn't support memory hotplug
1192 # (i.e. CONFIG_MEM_DEVICE not defined at build time).
1193 #
1194 # Since: 2.11.0
1195 ##
1196 { 'struct': 'MemoryInfo',
1197 'data' : { 'base-memory': 'size', '*plugged-memory': 'size' } }
1198
1199 ##
1200 # @query-memory-size-summary:
1201 #
1202 # Return the amount of initially allocated and present hotpluggable (if
1203 # enabled) memory in bytes.
1204 #
1205 # Example:
1206 #
1207 # -> { "execute": "query-memory-size-summary" }
1208 # <- { "return": { "base-memory": 4294967296, "plugged-memory": 0 } }
1209 #
1210 # Since: 2.11.0
1211 ##
1212 { 'command': 'query-memory-size-summary', 'returns': 'MemoryInfo' }
1213
1214
1215 ##
1216 # @AddfdInfo:
1217 #
1218 # Information about a file descriptor that was added to an fd set.
1219 #
1220 # @fdset-id: The ID of the fd set that @fd was added to.
1221 #
1222 # @fd: The file descriptor that was received via SCM rights and
1223 # added to the fd set.
1224 #
1225 # Since: 1.2.0
1226 ##
1227 { 'struct': 'AddfdInfo', 'data': {'fdset-id': 'int', 'fd': 'int'} }
1228
1229 ##
1230 # @add-fd:
1231 #
1232 # Add a file descriptor, that was passed via SCM rights, to an fd set.
1233 #
1234 # @fdset-id: The ID of the fd set to add the file descriptor to.
1235 #
1236 # @opaque: A free-form string that can be used to describe the fd.
1237 #
1238 # Returns: - @AddfdInfo on success
1239 # - If file descriptor was not received, FdNotSupplied
1240 # - If @fdset-id is a negative value, InvalidParameterValue
1241 #
1242 # Notes: The list of fd sets is shared by all monitor connections.
1243 #
1244 # If @fdset-id is not specified, a new fd set will be created.
1245 #
1246 # Since: 1.2.0
1247 #
1248 # Example:
1249 #
1250 # -> { "execute": "add-fd", "arguments": { "fdset-id": 1 } }
1251 # <- { "return": { "fdset-id": 1, "fd": 3 } }
1252 #
1253 ##
1254 { 'command': 'add-fd',
1255 'data': { '*fdset-id': 'int',
1256 '*opaque': 'str' },
1257 'returns': 'AddfdInfo' }
1258
1259 ##
1260 # @remove-fd:
1261 #
1262 # Remove a file descriptor from an fd set.
1263 #
1264 # @fdset-id: The ID of the fd set that the file descriptor belongs to.
1265 #
1266 # @fd: The file descriptor that is to be removed.
1267 #
1268 # Returns: - Nothing on success
1269 # - If @fdset-id or @fd is not found, FdNotFound
1270 #
1271 # Since: 1.2.0
1272 #
1273 # Notes: The list of fd sets is shared by all monitor connections.
1274 #
1275 # If @fd is not specified, all file descriptors in @fdset-id
1276 # will be removed.
1277 #
1278 # Example:
1279 #
1280 # -> { "execute": "remove-fd", "arguments": { "fdset-id": 1, "fd": 3 } }
1281 # <- { "return": {} }
1282 #
1283 ##
1284 { 'command': 'remove-fd', 'data': {'fdset-id': 'int', '*fd': 'int'} }
1285
1286 ##
1287 # @FdsetFdInfo:
1288 #
1289 # Information about a file descriptor that belongs to an fd set.
1290 #
1291 # @fd: The file descriptor value.
1292 #
1293 # @opaque: A free-form string that can be used to describe the fd.
1294 #
1295 # Since: 1.2.0
1296 ##
1297 { 'struct': 'FdsetFdInfo',
1298 'data': {'fd': 'int', '*opaque': 'str'} }
1299
1300 ##
1301 # @FdsetInfo:
1302 #
1303 # Information about an fd set.
1304 #
1305 # @fdset-id: The ID of the fd set.
1306 #
1307 # @fds: A list of file descriptors that belong to this fd set.
1308 #
1309 # Since: 1.2.0
1310 ##
1311 { 'struct': 'FdsetInfo',
1312 'data': {'fdset-id': 'int', 'fds': ['FdsetFdInfo']} }
1313
1314 ##
1315 # @query-fdsets:
1316 #
1317 # Return information describing all fd sets.
1318 #
1319 # Returns: A list of @FdsetInfo
1320 #
1321 # Since: 1.2.0
1322 #
1323 # Note: The list of fd sets is shared by all monitor connections.
1324 #
1325 # Example:
1326 #
1327 # -> { "execute": "query-fdsets" }
1328 # <- { "return": [
1329 # {
1330 # "fds": [
1331 # {
1332 # "fd": 30,
1333 # "opaque": "rdonly:/path/to/file"
1334 # },
1335 # {
1336 # "fd": 24,
1337 # "opaque": "rdwr:/path/to/file"
1338 # }
1339 # ],
1340 # "fdset-id": 1
1341 # },
1342 # {
1343 # "fds": [
1344 # {
1345 # "fd": 28
1346 # },
1347 # {
1348 # "fd": 29
1349 # }
1350 # ],
1351 # "fdset-id": 0
1352 # }
1353 # ]
1354 # }
1355 #
1356 ##
1357 { 'command': 'query-fdsets', 'returns': ['FdsetInfo'] }
1358
1359 ##
1360 # @AcpiTableOptions:
1361 #
1362 # Specify an ACPI table on the command line to load.
1363 #
1364 # At most one of @file and @data can be specified. The list of files specified
1365 # by any one of them is loaded and concatenated in order. If both are omitted,
1366 # @data is implied.
1367 #
1368 # Other fields / optargs can be used to override fields of the generic ACPI
1369 # table header; refer to the ACPI specification 5.0, section 5.2.6 System
1370 # Description Table Header. If a header field is not overridden, then the
1371 # corresponding value from the concatenated blob is used (in case of @file), or
1372 # it is filled in with a hard-coded value (in case of @data).
1373 #
1374 # String fields are copied into the matching ACPI member from lowest address
1375 # upwards, and silently truncated / NUL-padded to length.
1376 #
1377 # @sig: table signature / identifier (4 bytes)
1378 #
1379 # @rev: table revision number (dependent on signature, 1 byte)
1380 #
1381 # @oem_id: OEM identifier (6 bytes)
1382 #
1383 # @oem_table_id: OEM table identifier (8 bytes)
1384 #
1385 # @oem_rev: OEM-supplied revision number (4 bytes)
1386 #
1387 # @asl_compiler_id: identifier of the utility that created the table
1388 # (4 bytes)
1389 #
1390 # @asl_compiler_rev: revision number of the utility that created the
1391 # table (4 bytes)
1392 #
1393 # @file: colon (:) separated list of pathnames to load and
1394 # concatenate as table data. The resultant binary blob is expected to
1395 # have an ACPI table header. At least one file is required. This field
1396 # excludes @data.
1397 #
1398 # @data: colon (:) separated list of pathnames to load and
1399 # concatenate as table data. The resultant binary blob must not have an
1400 # ACPI table header. At least one file is required. This field excludes
1401 # @file.
1402 #
1403 # Since: 1.5
1404 ##
1405 { 'struct': 'AcpiTableOptions',
1406 'data': {
1407 '*sig': 'str',
1408 '*rev': 'uint8',
1409 '*oem_id': 'str',
1410 '*oem_table_id': 'str',
1411 '*oem_rev': 'uint32',
1412 '*asl_compiler_id': 'str',
1413 '*asl_compiler_rev': 'uint32',
1414 '*file': 'str',
1415 '*data': 'str' }}
1416
1417 ##
1418 # @CommandLineParameterType:
1419 #
1420 # Possible types for an option parameter.
1421 #
1422 # @string: accepts a character string
1423 #
1424 # @boolean: accepts "on" or "off"
1425 #
1426 # @number: accepts a number
1427 #
1428 # @size: accepts a number followed by an optional suffix (K)ilo,
1429 # (M)ega, (G)iga, (T)era
1430 #
1431 # Since: 1.5
1432 ##
1433 { 'enum': 'CommandLineParameterType',
1434 'data': ['string', 'boolean', 'number', 'size'] }
1435
1436 ##
1437 # @CommandLineParameterInfo:
1438 #
1439 # Details about a single parameter of a command line option.
1440 #
1441 # @name: parameter name
1442 #
1443 # @type: parameter @CommandLineParameterType
1444 #
1445 # @help: human readable text string, not suitable for parsing.
1446 #
1447 # @default: default value string (since 2.1)
1448 #
1449 # Since: 1.5
1450 ##
1451 { 'struct': 'CommandLineParameterInfo',
1452 'data': { 'name': 'str',
1453 'type': 'CommandLineParameterType',
1454 '*help': 'str',
1455 '*default': 'str' } }
1456
1457 ##
1458 # @CommandLineOptionInfo:
1459 #
1460 # Details about a command line option, including its list of parameter details
1461 #
1462 # @option: option name
1463 #
1464 # @parameters: an array of @CommandLineParameterInfo
1465 #
1466 # Since: 1.5
1467 ##
1468 { 'struct': 'CommandLineOptionInfo',
1469 'data': { 'option': 'str', 'parameters': ['CommandLineParameterInfo'] } }
1470
1471 ##
1472 # @query-command-line-options:
1473 #
1474 # Query command line option schema.
1475 #
1476 # @option: option name
1477 #
1478 # Returns: list of @CommandLineOptionInfo for all options (or for the given
1479 # @option). Returns an error if the given @option doesn't exist.
1480 #
1481 # Since: 1.5
1482 #
1483 # Example:
1484 #
1485 # -> { "execute": "query-command-line-options",
1486 # "arguments": { "option": "option-rom" } }
1487 # <- { "return": [
1488 # {
1489 # "parameters": [
1490 # {
1491 # "name": "romfile",
1492 # "type": "string"
1493 # },
1494 # {
1495 # "name": "bootindex",
1496 # "type": "number"
1497 # }
1498 # ],
1499 # "option": "option-rom"
1500 # }
1501 # ]
1502 # }
1503 #
1504 ##
1505 {'command': 'query-command-line-options',
1506 'data': { '*option': 'str' },
1507 'returns': ['CommandLineOptionInfo'],
1508 'allow-preconfig': true }
1509
1510 ##
1511 # @PCDIMMDeviceInfo:
1512 #
1513 # PCDIMMDevice state information
1514 #
1515 # @id: device's ID
1516 #
1517 # @addr: physical address, where device is mapped
1518 #
1519 # @size: size of memory that the device provides
1520 #
1521 # @slot: slot number at which device is plugged in
1522 #
1523 # @node: NUMA node number where device is plugged in
1524 #
1525 # @memdev: memory backend linked with device
1526 #
1527 # @hotplugged: true if device was hotplugged
1528 #
1529 # @hotpluggable: true if device if could be added/removed while machine is running
1530 #
1531 # Since: 2.1
1532 ##
1533 { 'struct': 'PCDIMMDeviceInfo',
1534 'data': { '*id': 'str',
1535 'addr': 'int',
1536 'size': 'int',
1537 'slot': 'int',
1538 'node': 'int',
1539 'memdev': 'str',
1540 'hotplugged': 'bool',
1541 'hotpluggable': 'bool'
1542 }
1543 }
1544
1545 ##
1546 # @VirtioPMEMDeviceInfo:
1547 #
1548 # VirtioPMEM state information
1549 #
1550 # @id: device's ID
1551 #
1552 # @memaddr: physical address in memory, where device is mapped
1553 #
1554 # @size: size of memory that the device provides
1555 #
1556 # @memdev: memory backend linked with device
1557 #
1558 # Since: 4.1
1559 ##
1560 { 'struct': 'VirtioPMEMDeviceInfo',
1561 'data': { '*id': 'str',
1562 'memaddr': 'size',
1563 'size': 'size',
1564 'memdev': 'str'
1565 }
1566 }
1567
1568 ##
1569 # @MemoryDeviceInfo:
1570 #
1571 # Union containing information about a memory device
1572 #
1573 # nvdimm is included since 2.12. virtio-pmem is included since 4.1.
1574 #
1575 # Since: 2.1
1576 ##
1577 { 'union': 'MemoryDeviceInfo',
1578 'data': { 'dimm': 'PCDIMMDeviceInfo',
1579 'nvdimm': 'PCDIMMDeviceInfo',
1580 'virtio-pmem': 'VirtioPMEMDeviceInfo'
1581 }
1582 }
1583
1584 ##
1585 # @query-memory-devices:
1586 #
1587 # Lists available memory devices and their state
1588 #
1589 # Since: 2.1
1590 #
1591 # Example:
1592 #
1593 # -> { "execute": "query-memory-devices" }
1594 # <- { "return": [ { "data":
1595 # { "addr": 5368709120,
1596 # "hotpluggable": true,
1597 # "hotplugged": true,
1598 # "id": "d1",
1599 # "memdev": "/objects/memX",
1600 # "node": 0,
1601 # "size": 1073741824,
1602 # "slot": 0},
1603 # "type": "dimm"
1604 # } ] }
1605 #
1606 ##
1607 { 'command': 'query-memory-devices', 'returns': ['MemoryDeviceInfo'] }
1608
1609 ##
1610 # @MEM_UNPLUG_ERROR:
1611 #
1612 # Emitted when memory hot unplug error occurs.
1613 #
1614 # @device: device name
1615 #
1616 # @msg: Informative message
1617 #
1618 # Since: 2.4
1619 #
1620 # Example:
1621 #
1622 # <- { "event": "MEM_UNPLUG_ERROR"
1623 # "data": { "device": "dimm1",
1624 # "msg": "acpi: device unplug for unsupported device"
1625 # },
1626 # "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
1627 #
1628 ##
1629 { 'event': 'MEM_UNPLUG_ERROR',
1630 'data': { 'device': 'str', 'msg': 'str' } }
1631
1632 ##
1633 # @ACPISlotType:
1634 #
1635 # @DIMM: memory slot
1636 # @CPU: logical CPU slot (since 2.7)
1637 ##
1638 { 'enum': 'ACPISlotType', 'data': [ 'DIMM', 'CPU' ] }
1639
1640 ##
1641 # @ACPIOSTInfo:
1642 #
1643 # OSPM Status Indication for a device
1644 # For description of possible values of @source and @status fields
1645 # see "_OST (OSPM Status Indication)" chapter of ACPI5.0 spec.
1646 #
1647 # @device: device ID associated with slot
1648 #
1649 # @slot: slot ID, unique per slot of a given @slot-type
1650 #
1651 # @slot-type: type of the slot
1652 #
1653 # @source: an integer containing the source event
1654 #
1655 # @status: an integer containing the status code
1656 #
1657 # Since: 2.1
1658 ##
1659 { 'struct': 'ACPIOSTInfo',
1660 'data' : { '*device': 'str',
1661 'slot': 'str',
1662 'slot-type': 'ACPISlotType',
1663 'source': 'int',
1664 'status': 'int' } }
1665
1666 ##
1667 # @query-acpi-ospm-status:
1668 #
1669 # Return a list of ACPIOSTInfo for devices that support status
1670 # reporting via ACPI _OST method.
1671 #
1672 # Since: 2.1
1673 #
1674 # Example:
1675 #
1676 # -> { "execute": "query-acpi-ospm-status" }
1677 # <- { "return": [ { "device": "d1", "slot": "0", "slot-type": "DIMM", "source": 1, "status": 0},
1678 # { "slot": "1", "slot-type": "DIMM", "source": 0, "status": 0},
1679 # { "slot": "2", "slot-type": "DIMM", "source": 0, "status": 0},
1680 # { "slot": "3", "slot-type": "DIMM", "source": 0, "status": 0}
1681 # ]}
1682 #
1683 ##
1684 { 'command': 'query-acpi-ospm-status', 'returns': ['ACPIOSTInfo'] }
1685
1686 ##
1687 # @ACPI_DEVICE_OST:
1688 #
1689 # Emitted when guest executes ACPI _OST method.
1690 #
1691 # @info: OSPM Status Indication
1692 #
1693 # Since: 2.1
1694 #
1695 # Example:
1696 #
1697 # <- { "event": "ACPI_DEVICE_OST",
1698 # "data": { "device": "d1", "slot": "0",
1699 # "slot-type": "DIMM", "source": 1, "status": 0 } }
1700 #
1701 ##
1702 { 'event': 'ACPI_DEVICE_OST',
1703 'data': { 'info': 'ACPIOSTInfo' } }
1704
1705 ##
1706 # @ReplayMode:
1707 #
1708 # Mode of the replay subsystem.
1709 #
1710 # @none: normal execution mode. Replay or record are not enabled.
1711 #
1712 # @record: record mode. All non-deterministic data is written into the
1713 # replay log.
1714 #
1715 # @play: replay mode. Non-deterministic data required for system execution
1716 # is read from the log.
1717 #
1718 # Since: 2.5
1719 ##
1720 { 'enum': 'ReplayMode',
1721 'data': [ 'none', 'record', 'play' ] }
1722
1723 ##
1724 # @xen-load-devices-state:
1725 #
1726 # Load the state of all devices from file. The RAM and the block devices
1727 # of the VM are not loaded by this command.
1728 #
1729 # @filename: the file to load the state of the devices from as binary
1730 # data. See xen-save-devices-state.txt for a description of the binary
1731 # format.
1732 #
1733 # Since: 2.7
1734 #
1735 # Example:
1736 #
1737 # -> { "execute": "xen-load-devices-state",
1738 # "arguments": { "filename": "/tmp/resume" } }
1739 # <- { "return": {} }
1740 #
1741 ##
1742 { 'command': 'xen-load-devices-state', 'data': {'filename': 'str'} }
1743
1744 ##
1745 # @GuidInfo:
1746 #
1747 # GUID information.
1748 #
1749 # @guid: the globally unique identifier
1750 #
1751 # Since: 2.9
1752 ##
1753 { 'struct': 'GuidInfo', 'data': {'guid': 'str'} }
1754
1755 ##
1756 # @query-vm-generation-id:
1757 #
1758 # Show Virtual Machine Generation ID
1759 #
1760 # Since: 2.9
1761 ##
1762 { 'command': 'query-vm-generation-id', 'returns': 'GuidInfo' }
1763