]> git.proxmox.com Git - mirror_qemu.git/blob - qapi-schema.json
qmp-commands: move 'migrate-incoming' doc to schema
[mirror_qemu.git] / qapi-schema.json
1 # -*- Mode: Python -*-
2 #
3 # QAPI Schema
4
5 # QAPI common definitions
6 { 'include': 'qapi/common.json' }
7
8 # QAPI crypto definitions
9 { 'include': 'qapi/crypto.json' }
10
11 # QAPI block definitions
12 { 'include': 'qapi/block.json' }
13
14 # QAPI event definitions
15 { 'include': 'qapi/event.json' }
16
17 # Tracing commands
18 { 'include': 'qapi/trace.json' }
19
20 # QAPI introspection
21 { 'include': 'qapi/introspect.json' }
22
23 ##
24 # = QMP commands
25 ##
26
27 ##
28 # @qmp_capabilities:
29 #
30 # Enable QMP capabilities.
31 #
32 # Arguments: None.
33 #
34 # Example:
35 #
36 # -> { "execute": "qmp_capabilities" }
37 # <- { "return": {} }
38 #
39 # Notes: This command is valid exactly when first connecting: it must be
40 # issued before any other command will be accepted, and will fail once the
41 # monitor is accepting other commands. (see qemu docs/qmp-spec.txt)
42 #
43 # Since: 0.13
44 #
45 ##
46 { 'command': 'qmp_capabilities' }
47
48 ##
49 # @LostTickPolicy:
50 #
51 # Policy for handling lost ticks in timer devices.
52 #
53 # @discard: throw away the missed tick(s) and continue with future injection
54 # normally. Guest time may be delayed, unless the OS has explicit
55 # handling of lost ticks
56 #
57 # @delay: continue to deliver ticks at the normal rate. Guest time will be
58 # delayed due to the late tick
59 #
60 # @merge: merge the missed tick(s) into one tick and inject. Guest time
61 # may be delayed, depending on how the OS reacts to the merging
62 # of ticks
63 #
64 # @slew: deliver ticks at a higher rate to catch up with the missed tick. The
65 # guest time should not be delayed once catchup is complete.
66 #
67 # Since: 2.0
68 ##
69 { 'enum': 'LostTickPolicy',
70 'data': ['discard', 'delay', 'merge', 'slew' ] }
71
72 ##
73 # @add_client:
74 #
75 # Allow client connections for VNC, Spice and socket based
76 # character devices to be passed in to QEMU via SCM_RIGHTS.
77 #
78 # @protocol: protocol name. Valid names are "vnc", "spice" or the
79 # name of a character device (eg. from -chardev id=XXXX)
80 #
81 # @fdname: file descriptor name previously passed via 'getfd' command
82 #
83 # @skipauth: #optional whether to skip authentication. Only applies
84 # to "vnc" and "spice" protocols
85 #
86 # @tls: #optional whether to perform TLS. Only applies to the "spice"
87 # protocol
88 #
89 # Returns: nothing on success.
90 #
91 # Since: 0.14.0
92 #
93 # Example:
94 #
95 # -> { "execute": "add_client", "arguments": { "protocol": "vnc",
96 # "fdname": "myclient" } }
97 # <- { "return": {} }
98 #
99 ##
100 { 'command': 'add_client',
101 'data': { 'protocol': 'str', 'fdname': 'str', '*skipauth': 'bool',
102 '*tls': 'bool' } }
103
104 ##
105 # @NameInfo:
106 #
107 # Guest name information.
108 #
109 # @name: #optional The name of the guest
110 #
111 # Since: 0.14.0
112 ##
113 { 'struct': 'NameInfo', 'data': {'*name': 'str'} }
114
115 ##
116 # @query-name:
117 #
118 # Return the name information of a guest.
119 #
120 # Returns: @NameInfo of the guest
121 #
122 # Since: 0.14.0
123 #
124 # Example:
125 #
126 # -> { "execute": "query-name" }
127 # <- { "return": { "name": "qemu-name" } }
128 #
129 ##
130 { 'command': 'query-name', 'returns': 'NameInfo' }
131
132 ##
133 # @KvmInfo:
134 #
135 # Information about support for KVM acceleration
136 #
137 # @enabled: true if KVM acceleration is active
138 #
139 # @present: true if KVM acceleration is built into this executable
140 #
141 # Since: 0.14.0
142 ##
143 { 'struct': 'KvmInfo', 'data': {'enabled': 'bool', 'present': 'bool'} }
144
145 ##
146 # @query-kvm:
147 #
148 # Returns information about KVM acceleration
149 #
150 # Returns: @KvmInfo
151 #
152 # Since: 0.14.0
153 #
154 # Example:
155 #
156 # -> { "execute": "query-kvm" }
157 # <- { "return": { "enabled": true, "present": true } }
158 #
159 ##
160 { 'command': 'query-kvm', 'returns': 'KvmInfo' }
161
162 ##
163 # @RunState:
164 #
165 # An enumeration of VM run states.
166 #
167 # @debug: QEMU is running on a debugger
168 #
169 # @finish-migrate: guest is paused to finish the migration process
170 #
171 # @inmigrate: guest is paused waiting for an incoming migration. Note
172 # that this state does not tell whether the machine will start at the
173 # end of the migration. This depends on the command-line -S option and
174 # any invocation of 'stop' or 'cont' that has happened since QEMU was
175 # started.
176 #
177 # @internal-error: An internal error that prevents further guest execution
178 # has occurred
179 #
180 # @io-error: the last IOP has failed and the device is configured to pause
181 # on I/O errors
182 #
183 # @paused: guest has been paused via the 'stop' command
184 #
185 # @postmigrate: guest is paused following a successful 'migrate'
186 #
187 # @prelaunch: QEMU was started with -S and guest has not started
188 #
189 # @restore-vm: guest is paused to restore VM state
190 #
191 # @running: guest is actively running
192 #
193 # @save-vm: guest is paused to save the VM state
194 #
195 # @shutdown: guest is shut down (and -no-shutdown is in use)
196 #
197 # @suspended: guest is suspended (ACPI S3)
198 #
199 # @watchdog: the watchdog action is configured to pause and has been triggered
200 #
201 # @guest-panicked: guest has been panicked as a result of guest OS panic
202 #
203 # @colo: guest is paused to save/restore VM state under colo checkpoint,
204 # VM can not get into this state unless colo capability is enabled
205 # for migration. (since 2.8)
206 ##
207 { 'enum': 'RunState',
208 'data': [ 'debug', 'inmigrate', 'internal-error', 'io-error', 'paused',
209 'postmigrate', 'prelaunch', 'finish-migrate', 'restore-vm',
210 'running', 'save-vm', 'shutdown', 'suspended', 'watchdog',
211 'guest-panicked', 'colo' ] }
212
213 ##
214 # @StatusInfo:
215 #
216 # Information about VCPU run state
217 #
218 # @running: true if all VCPUs are runnable, false if not runnable
219 #
220 # @singlestep: true if VCPUs are in single-step mode
221 #
222 # @status: the virtual machine @RunState
223 #
224 # Since: 0.14.0
225 #
226 # Notes: @singlestep is enabled through the GDB stub
227 ##
228 { 'struct': 'StatusInfo',
229 'data': {'running': 'bool', 'singlestep': 'bool', 'status': 'RunState'} }
230
231 ##
232 # @query-status:
233 #
234 # Query the run status of all VCPUs
235 #
236 # Returns: @StatusInfo reflecting all VCPUs
237 #
238 # Since: 0.14.0
239 #
240 # Example:
241 #
242 # -> { "execute": "query-status" }
243 # <- { "return": { "running": true,
244 # "singlestep": false,
245 # "status": "running" } }
246 #
247 ##
248 { 'command': 'query-status', 'returns': 'StatusInfo' }
249
250 ##
251 # @UuidInfo:
252 #
253 # Guest UUID information (Universally Unique Identifier).
254 #
255 # @UUID: the UUID of the guest
256 #
257 # Since: 0.14.0
258 #
259 # Notes: If no UUID was specified for the guest, a null UUID is returned.
260 ##
261 { 'struct': 'UuidInfo', 'data': {'UUID': 'str'} }
262
263 ##
264 # @query-uuid:
265 #
266 # Query the guest UUID information.
267 #
268 # Returns: The @UuidInfo for the guest
269 #
270 # Since: 0.14.0
271 #
272 # Example:
273 #
274 # -> { "execute": "query-uuid" }
275 # <- { "return": { "UUID": "550e8400-e29b-41d4-a716-446655440000" } }
276 #
277 ##
278 { 'command': 'query-uuid', 'returns': 'UuidInfo' }
279
280 ##
281 # @ChardevInfo:
282 #
283 # Information about a character device.
284 #
285 # @label: the label of the character device
286 #
287 # @filename: the filename of the character device
288 #
289 # @frontend-open: shows whether the frontend device attached to this backend
290 # (eg. with the chardev=... option) is in open or closed state
291 # (since 2.1)
292 #
293 # Notes: @filename is encoded using the QEMU command line character device
294 # encoding. See the QEMU man page for details.
295 #
296 # Since: 0.14.0
297 ##
298 { 'struct': 'ChardevInfo', 'data': {'label': 'str',
299 'filename': 'str',
300 'frontend-open': 'bool'} }
301
302 ##
303 # @query-chardev:
304 #
305 # Returns information about current character devices.
306 #
307 # Returns: a list of @ChardevInfo
308 #
309 # Since: 0.14.0
310 #
311 # Example:
312 #
313 # -> { "execute": "query-chardev" }
314 # <- {
315 # "return": [
316 # {
317 # "label": "charchannel0",
318 # "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.agent,server",
319 # "frontend-open": false
320 # },
321 # {
322 # "label": "charmonitor",
323 # "filename": "unix:/var/lib/libvirt/qemu/seabios.rhel6.monitor,server",
324 # "frontend-open": true
325 # },
326 # {
327 # "label": "charserial0",
328 # "filename": "pty:/dev/pts/2",
329 # "frontend-open": true
330 # }
331 # ]
332 # }
333 #
334 ##
335 { 'command': 'query-chardev', 'returns': ['ChardevInfo'] }
336
337 ##
338 # @ChardevBackendInfo:
339 #
340 # Information about a character device backend
341 #
342 # @name: The backend name
343 #
344 # Since: 2.0
345 ##
346 { 'struct': 'ChardevBackendInfo', 'data': {'name': 'str'} }
347
348 ##
349 # @query-chardev-backends:
350 #
351 # Returns information about character device backends.
352 #
353 # Returns: a list of @ChardevBackendInfo
354 #
355 # Since: 2.0
356 #
357 # Example:
358 #
359 # -> { "execute": "query-chardev-backends" }
360 # <- {
361 # "return":[
362 # {
363 # "name":"udp"
364 # },
365 # {
366 # "name":"tcp"
367 # },
368 # {
369 # "name":"unix"
370 # },
371 # {
372 # "name":"spiceport"
373 # }
374 # ]
375 # }
376 #
377 ##
378 { 'command': 'query-chardev-backends', 'returns': ['ChardevBackendInfo'] }
379
380 ##
381 # @DataFormat:
382 #
383 # An enumeration of data format.
384 #
385 # @utf8: Data is a UTF-8 string (RFC 3629)
386 #
387 # @base64: Data is Base64 encoded binary (RFC 3548)
388 #
389 # Since: 1.4
390 ##
391 { 'enum': 'DataFormat',
392 'data': [ 'utf8', 'base64' ] }
393
394 ##
395 # @ringbuf-write:
396 #
397 # Write to a ring buffer character device.
398 #
399 # @device: the ring buffer character device name
400 #
401 # @data: data to write
402 #
403 # @format: #optional data encoding (default 'utf8').
404 # - base64: data must be base64 encoded text. Its binary
405 # decoding gets written.
406 # - utf8: data's UTF-8 encoding is written
407 # - data itself is always Unicode regardless of format, like
408 # any other string.
409 #
410 # Returns: Nothing on success
411 #
412 # Since: 1.4
413 #
414 # Example:
415 #
416 # -> { "execute": "ringbuf-write",
417 # "arguments": { "device": "foo",
418 # "data": "abcdefgh",
419 # "format": "utf8" } }
420 # <- { "return": {} }
421 #
422 ##
423 { 'command': 'ringbuf-write',
424 'data': {'device': 'str', 'data': 'str',
425 '*format': 'DataFormat'} }
426
427 ##
428 # @ringbuf-read:
429 #
430 # Read from a ring buffer character device.
431 #
432 # @device: the ring buffer character device name
433 #
434 # @size: how many bytes to read at most
435 #
436 # @format: #optional data encoding (default 'utf8').
437 # - base64: the data read is returned in base64 encoding.
438 # - utf8: the data read is interpreted as UTF-8.
439 # Bug: can screw up when the buffer contains invalid UTF-8
440 # sequences, NUL characters, after the ring buffer lost
441 # data, and when reading stops because the size limit is
442 # reached.
443 # - The return value is always Unicode regardless of format,
444 # like any other string.
445 #
446 # Returns: data read from the device
447 #
448 # Since: 1.4
449 #
450 # Example:
451 #
452 # -> { "execute": "ringbuf-read",
453 # "arguments": { "device": "foo",
454 # "size": 1000,
455 # "format": "utf8" } }
456 # <- { "return": "abcdefgh" }
457 #
458 ##
459 { 'command': 'ringbuf-read',
460 'data': {'device': 'str', 'size': 'int', '*format': 'DataFormat'},
461 'returns': 'str' }
462
463 ##
464 # @EventInfo:
465 #
466 # Information about a QMP event
467 #
468 # @name: The event name
469 #
470 # Since: 1.2.0
471 ##
472 { 'struct': 'EventInfo', 'data': {'name': 'str'} }
473
474 ##
475 # @query-events:
476 #
477 # Return a list of supported QMP events by this server
478 #
479 # Returns: A list of @EventInfo for all supported events
480 #
481 # Since: 1.2.0
482 #
483 # Example:
484 #
485 # -> { "execute": "query-events" }
486 # <- {
487 # "return": [
488 # {
489 # "name":"SHUTDOWN"
490 # },
491 # {
492 # "name":"RESET"
493 # }
494 # ]
495 # }
496 #
497 # Note: This example has been shortened as the real response is too long.
498 #
499 ##
500 { 'command': 'query-events', 'returns': ['EventInfo'] }
501
502 ##
503 # @MigrationStats:
504 #
505 # Detailed migration status.
506 #
507 # @transferred: amount of bytes already transferred to the target VM
508 #
509 # @remaining: amount of bytes remaining to be transferred to the target VM
510 #
511 # @total: total amount of bytes involved in the migration process
512 #
513 # @duplicate: number of duplicate (zero) pages (since 1.2)
514 #
515 # @skipped: number of skipped zero pages (since 1.5)
516 #
517 # @normal: number of normal pages (since 1.2)
518 #
519 # @normal-bytes: number of normal bytes sent (since 1.2)
520 #
521 # @dirty-pages-rate: number of pages dirtied by second by the
522 # guest (since 1.3)
523 #
524 # @mbps: throughput in megabits/sec. (since 1.6)
525 #
526 # @dirty-sync-count: number of times that dirty ram was synchronized (since 2.1)
527 #
528 # @postcopy-requests: The number of page requests received from the destination
529 # (since 2.7)
530 #
531 # Since: 0.14.0
532 ##
533 { 'struct': 'MigrationStats',
534 'data': {'transferred': 'int', 'remaining': 'int', 'total': 'int' ,
535 'duplicate': 'int', 'skipped': 'int', 'normal': 'int',
536 'normal-bytes': 'int', 'dirty-pages-rate' : 'int',
537 'mbps' : 'number', 'dirty-sync-count' : 'int',
538 'postcopy-requests' : 'int' } }
539
540 ##
541 # @XBZRLECacheStats:
542 #
543 # Detailed XBZRLE migration cache statistics
544 #
545 # @cache-size: XBZRLE cache size
546 #
547 # @bytes: amount of bytes already transferred to the target VM
548 #
549 # @pages: amount of pages transferred to the target VM
550 #
551 # @cache-miss: number of cache miss
552 #
553 # @cache-miss-rate: rate of cache miss (since 2.1)
554 #
555 # @overflow: number of overflows
556 #
557 # Since: 1.2
558 ##
559 { 'struct': 'XBZRLECacheStats',
560 'data': {'cache-size': 'int', 'bytes': 'int', 'pages': 'int',
561 'cache-miss': 'int', 'cache-miss-rate': 'number',
562 'overflow': 'int' } }
563
564 ##
565 # @MigrationStatus:
566 #
567 # An enumeration of migration status.
568 #
569 # @none: no migration has ever happened.
570 #
571 # @setup: migration process has been initiated.
572 #
573 # @cancelling: in the process of cancelling migration.
574 #
575 # @cancelled: cancelling migration is finished.
576 #
577 # @active: in the process of doing migration.
578 #
579 # @postcopy-active: like active, but now in postcopy mode. (since 2.5)
580 #
581 # @completed: migration is finished.
582 #
583 # @failed: some error occurred during migration process.
584 #
585 # @colo: VM is in the process of fault tolerance, VM can not get into this
586 # state unless colo capability is enabled for migration. (since 2.8)
587 #
588 # Since: 2.3
589 #
590 ##
591 { 'enum': 'MigrationStatus',
592 'data': [ 'none', 'setup', 'cancelling', 'cancelled',
593 'active', 'postcopy-active', 'completed', 'failed', 'colo' ] }
594
595 ##
596 # @MigrationInfo:
597 #
598 # Information about current migration process.
599 #
600 # @status: #optional @MigrationStatus describing the current migration status.
601 # If this field is not returned, no migration process
602 # has been initiated
603 #
604 # @ram: #optional @MigrationStats containing detailed migration
605 # status, only returned if status is 'active' or
606 # 'completed'(since 1.2)
607 #
608 # @disk: #optional @MigrationStats containing detailed disk migration
609 # status, only returned if status is 'active' and it is a block
610 # migration
611 #
612 # @xbzrle-cache: #optional @XBZRLECacheStats containing detailed XBZRLE
613 # migration statistics, only returned if XBZRLE feature is on and
614 # status is 'active' or 'completed' (since 1.2)
615 #
616 # @total-time: #optional total amount of milliseconds since migration started.
617 # If migration has ended, it returns the total migration
618 # time. (since 1.2)
619 #
620 # @downtime: #optional only present when migration finishes correctly
621 # total downtime in milliseconds for the guest.
622 # (since 1.3)
623 #
624 # @expected-downtime: #optional only present while migration is active
625 # expected downtime in milliseconds for the guest in last walk
626 # of the dirty bitmap. (since 1.3)
627 #
628 # @setup-time: #optional amount of setup time in milliseconds _before_ the
629 # iterations begin but _after_ the QMP command is issued. This is designed
630 # to provide an accounting of any activities (such as RDMA pinning) which
631 # may be expensive, but do not actually occur during the iterative
632 # migration rounds themselves. (since 1.6)
633 #
634 # @cpu-throttle-percentage: #optional percentage of time guest cpus are being
635 # throttled during auto-converge. This is only present when auto-converge
636 # has started throttling guest cpus. (Since 2.7)
637 #
638 # @error-desc: #optional the human readable error description string, when
639 # @status is 'failed'. Clients should not attempt to parse the
640 # error strings. (Since 2.7)
641 #
642 # Since: 0.14.0
643 ##
644 { 'struct': 'MigrationInfo',
645 'data': {'*status': 'MigrationStatus', '*ram': 'MigrationStats',
646 '*disk': 'MigrationStats',
647 '*xbzrle-cache': 'XBZRLECacheStats',
648 '*total-time': 'int',
649 '*expected-downtime': 'int',
650 '*downtime': 'int',
651 '*setup-time': 'int',
652 '*cpu-throttle-percentage': 'int',
653 '*error-desc': 'str'} }
654
655 ##
656 # @query-migrate:
657 #
658 # Returns information about current migration process. If migration
659 # is active there will be another json-object with RAM migration
660 # status and if block migration is active another one with block
661 # migration status.
662 #
663 # Returns: @MigrationInfo
664 #
665 # Since: 0.14.0
666 #
667 # Example:
668 #
669 # 1. Before the first migration
670 #
671 # -> { "execute": "query-migrate" }
672 # <- { "return": {} }
673 #
674 # 2. Migration is done and has succeeded
675 #
676 # -> { "execute": "query-migrate" }
677 # <- { "return": {
678 # "status": "completed",
679 # "ram":{
680 # "transferred":123,
681 # "remaining":123,
682 # "total":246,
683 # "total-time":12345,
684 # "setup-time":12345,
685 # "downtime":12345,
686 # "duplicate":123,
687 # "normal":123,
688 # "normal-bytes":123456,
689 # "dirty-sync-count":15
690 # }
691 # }
692 # }
693 #
694 # 3. Migration is done and has failed
695 #
696 # -> { "execute": "query-migrate" }
697 # <- { "return": { "status": "failed" } }
698 #
699 # 4. Migration is being performed and is not a block migration:
700 #
701 # -> { "execute": "query-migrate" }
702 # <- {
703 # "return":{
704 # "status":"active",
705 # "ram":{
706 # "transferred":123,
707 # "remaining":123,
708 # "total":246,
709 # "total-time":12345,
710 # "setup-time":12345,
711 # "expected-downtime":12345,
712 # "duplicate":123,
713 # "normal":123,
714 # "normal-bytes":123456,
715 # "dirty-sync-count":15
716 # }
717 # }
718 # }
719 #
720 # 5. Migration is being performed and is a block migration:
721 #
722 # -> { "execute": "query-migrate" }
723 # <- {
724 # "return":{
725 # "status":"active",
726 # "ram":{
727 # "total":1057024,
728 # "remaining":1053304,
729 # "transferred":3720,
730 # "total-time":12345,
731 # "setup-time":12345,
732 # "expected-downtime":12345,
733 # "duplicate":123,
734 # "normal":123,
735 # "normal-bytes":123456,
736 # "dirty-sync-count":15
737 # },
738 # "disk":{
739 # "total":20971520,
740 # "remaining":20880384,
741 # "transferred":91136
742 # }
743 # }
744 # }
745 #
746 # 6. Migration is being performed and XBZRLE is active:
747 #
748 # -> { "execute": "query-migrate" }
749 # <- {
750 # "return":{
751 # "status":"active",
752 # "capabilities" : [ { "capability": "xbzrle", "state" : true } ],
753 # "ram":{
754 # "total":1057024,
755 # "remaining":1053304,
756 # "transferred":3720,
757 # "total-time":12345,
758 # "setup-time":12345,
759 # "expected-downtime":12345,
760 # "duplicate":10,
761 # "normal":3333,
762 # "normal-bytes":3412992,
763 # "dirty-sync-count":15
764 # },
765 # "xbzrle-cache":{
766 # "cache-size":67108864,
767 # "bytes":20971520,
768 # "pages":2444343,
769 # "cache-miss":2244,
770 # "cache-miss-rate":0.123,
771 # "overflow":34434
772 # }
773 # }
774 # }
775 #
776 ##
777 { 'command': 'query-migrate', 'returns': 'MigrationInfo' }
778
779 ##
780 # @MigrationCapability:
781 #
782 # Migration capabilities enumeration
783 #
784 # @xbzrle: Migration supports xbzrle (Xor Based Zero Run Length Encoding).
785 # This feature allows us to minimize migration traffic for certain work
786 # loads, by sending compressed difference of the pages
787 #
788 # @rdma-pin-all: Controls whether or not the entire VM memory footprint is
789 # mlock()'d on demand or all at once. Refer to docs/rdma.txt for usage.
790 # Disabled by default. (since 2.0)
791 #
792 # @zero-blocks: During storage migration encode blocks of zeroes efficiently. This
793 # essentially saves 1MB of zeroes per block on the wire. Enabling requires
794 # source and target VM to support this feature. To enable it is sufficient
795 # to enable the capability on the source VM. The feature is disabled by
796 # default. (since 1.6)
797 #
798 # @compress: Use multiple compression threads to accelerate live migration.
799 # This feature can help to reduce the migration traffic, by sending
800 # compressed pages. Please note that if compress and xbzrle are both
801 # on, compress only takes effect in the ram bulk stage, after that,
802 # it will be disabled and only xbzrle takes effect, this can help to
803 # minimize migration traffic. The feature is disabled by default.
804 # (since 2.4 )
805 #
806 # @events: generate events for each migration state change
807 # (since 2.4 )
808 #
809 # @auto-converge: If enabled, QEMU will automatically throttle down the guest
810 # to speed up convergence of RAM migration. (since 1.6)
811 #
812 # @postcopy-ram: Start executing on the migration target before all of RAM has
813 # been migrated, pulling the remaining pages along as needed. NOTE: If
814 # the migration fails during postcopy the VM will fail. (since 2.6)
815 #
816 # @x-colo: If enabled, migration will never end, and the state of the VM on the
817 # primary side will be migrated continuously to the VM on secondary
818 # side, this process is called COarse-Grain LOck Stepping (COLO) for
819 # Non-stop Service. (since 2.8)
820 #
821 # Since: 1.2
822 ##
823 { 'enum': 'MigrationCapability',
824 'data': ['xbzrle', 'rdma-pin-all', 'auto-converge', 'zero-blocks',
825 'compress', 'events', 'postcopy-ram', 'x-colo'] }
826
827 ##
828 # @MigrationCapabilityStatus:
829 #
830 # Migration capability information
831 #
832 # @capability: capability enum
833 #
834 # @state: capability state bool
835 #
836 # Since: 1.2
837 ##
838 { 'struct': 'MigrationCapabilityStatus',
839 'data': { 'capability' : 'MigrationCapability', 'state' : 'bool' } }
840
841 ##
842 # @migrate-set-capabilities:
843 #
844 # Enable/Disable the following migration capabilities (like xbzrle)
845 #
846 # @capabilities: json array of capability modifications to make
847 #
848 # Since: 1.2
849 #
850 # Example:
851 #
852 # -> { "execute": "migrate-set-capabilities" , "arguments":
853 # { "capabilities": [ { "capability": "xbzrle", "state": true } ] } }
854 #
855 ##
856 { 'command': 'migrate-set-capabilities',
857 'data': { 'capabilities': ['MigrationCapabilityStatus'] } }
858
859 ##
860 # @query-migrate-capabilities:
861 #
862 # Returns information about the current migration capabilities status
863 #
864 # Returns: @MigrationCapabilitiesStatus
865 #
866 # Since: 1.2
867 #
868 # Example:
869 #
870 # -> { "execute": "query-migrate-capabilities" }
871 # <- { "return": [
872 # {"state": false, "capability": "xbzrle"},
873 # {"state": false, "capability": "rdma-pin-all"},
874 # {"state": false, "capability": "auto-converge"},
875 # {"state": false, "capability": "zero-blocks"},
876 # {"state": false, "capability": "compress"},
877 # {"state": true, "capability": "events"},
878 # {"state": false, "capability": "postcopy-ram"},
879 # {"state": false, "capability": "x-colo"}
880 # ]}
881 #
882 ##
883 { 'command': 'query-migrate-capabilities', 'returns': ['MigrationCapabilityStatus']}
884
885 ##
886 # @MigrationParameter:
887 #
888 # Migration parameters enumeration
889 #
890 # @compress-level: Set the compression level to be used in live migration,
891 # the compression level is an integer between 0 and 9, where 0 means
892 # no compression, 1 means the best compression speed, and 9 means best
893 # compression ratio which will consume more CPU.
894 #
895 # @compress-threads: Set compression thread count to be used in live migration,
896 # the compression thread count is an integer between 1 and 255.
897 #
898 # @decompress-threads: Set decompression thread count to be used in live
899 # migration, the decompression thread count is an integer between 1
900 # and 255. Usually, decompression is at least 4 times as fast as
901 # compression, so set the decompress-threads to the number about 1/4
902 # of compress-threads is adequate.
903 #
904 # @cpu-throttle-initial: Initial percentage of time guest cpus are throttled
905 # when migration auto-converge is activated. The
906 # default value is 20. (Since 2.7)
907 #
908 # @cpu-throttle-increment: throttle percentage increase each time
909 # auto-converge detects that migration is not making
910 # progress. The default value is 10. (Since 2.7)
911 #
912 # @tls-creds: ID of the 'tls-creds' object that provides credentials for
913 # establishing a TLS connection over the migration data channel.
914 # On the outgoing side of the migration, the credentials must
915 # be for a 'client' endpoint, while for the incoming side the
916 # credentials must be for a 'server' endpoint. Setting this
917 # will enable TLS for all migrations. The default is unset,
918 # resulting in unsecured migration at the QEMU level. (Since 2.7)
919 #
920 # @tls-hostname: hostname of the target host for the migration. This is
921 # required when using x509 based TLS credentials and the
922 # migration URI does not already include a hostname. For
923 # example if using fd: or exec: based migration, the
924 # hostname must be provided so that the server's x509
925 # certificate identity can be validated. (Since 2.7)
926 #
927 # @max-bandwidth: to set maximum speed for migration. maximum speed in
928 # bytes per second. (Since 2.8)
929 #
930 # @downtime-limit: set maximum tolerated downtime for migration. maximum
931 # downtime in milliseconds (Since 2.8)
932 #
933 # @x-checkpoint-delay: The delay time (in ms) between two COLO checkpoints in
934 # periodic mode. (Since 2.8)
935 #
936 # Since: 2.4
937 ##
938 { 'enum': 'MigrationParameter',
939 'data': ['compress-level', 'compress-threads', 'decompress-threads',
940 'cpu-throttle-initial', 'cpu-throttle-increment',
941 'tls-creds', 'tls-hostname', 'max-bandwidth',
942 'downtime-limit', 'x-checkpoint-delay' ] }
943
944 ##
945 # @migrate-set-parameters:
946 #
947 # Set various migration parameters. See MigrationParameters for details.
948 #
949 # Since: 2.4
950 #
951 # Example:
952 #
953 # -> { "execute": "migrate-set-parameters" ,
954 # "arguments": { "compress-level": 1 } }
955 #
956 ##
957 { 'command': 'migrate-set-parameters', 'boxed': true,
958 'data': 'MigrationParameters' }
959
960 ##
961 # @MigrationParameters:
962 #
963 # Optional members can be omitted on input ('migrate-set-parameters')
964 # but most members will always be present on output
965 # ('query-migrate-parameters'), with the exception of tls-creds and
966 # tls-hostname.
967 #
968 # @compress-level: #optional compression level
969 #
970 # @compress-threads: #optional compression thread count
971 #
972 # @decompress-threads: #optional decompression thread count
973 #
974 # @cpu-throttle-initial: #optional Initial percentage of time guest cpus are
975 # throttledwhen migration auto-converge is activated.
976 # The default value is 20. (Since 2.7)
977 #
978 # @cpu-throttle-increment: #optional throttle percentage increase each time
979 # auto-converge detects that migration is not making
980 # progress. The default value is 10. (Since 2.7)
981 #
982 # @tls-creds: #optional ID of the 'tls-creds' object that provides credentials
983 # for establishing a TLS connection over the migration data
984 # channel. On the outgoing side of the migration, the credentials
985 # must be for a 'client' endpoint, while for the incoming side the
986 # credentials must be for a 'server' endpoint. Setting this
987 # will enable TLS for all migrations. The default is unset,
988 # resulting in unsecured migration at the QEMU level. (Since 2.7)
989 #
990 # @tls-hostname: #optional hostname of the target host for the migration. This
991 # is required when using x509 based TLS credentials and the
992 # migration URI does not already include a hostname. For
993 # example if using fd: or exec: based migration, the
994 # hostname must be provided so that the server's x509
995 # certificate identity can be validated. (Since 2.7)
996 #
997 # @max-bandwidth: to set maximum speed for migration. maximum speed in
998 # bytes per second. (Since 2.8)
999 #
1000 # @downtime-limit: set maximum tolerated downtime for migration. maximum
1001 # downtime in milliseconds (Since 2.8)
1002 #
1003 # @x-checkpoint-delay: the delay time between two COLO checkpoints. (Since 2.8)
1004 #
1005 # Since: 2.4
1006 ##
1007 { 'struct': 'MigrationParameters',
1008 'data': { '*compress-level': 'int',
1009 '*compress-threads': 'int',
1010 '*decompress-threads': 'int',
1011 '*cpu-throttle-initial': 'int',
1012 '*cpu-throttle-increment': 'int',
1013 '*tls-creds': 'str',
1014 '*tls-hostname': 'str',
1015 '*max-bandwidth': 'int',
1016 '*downtime-limit': 'int',
1017 '*x-checkpoint-delay': 'int'} }
1018
1019 ##
1020 # @query-migrate-parameters:
1021 #
1022 # Returns information about the current migration parameters
1023 #
1024 # Returns: @MigrationParameters
1025 #
1026 # Since: 2.4
1027 #
1028 # Example:
1029 #
1030 # -> { "execute": "query-migrate-parameters" }
1031 # <- { "return": {
1032 # "decompress-threads": 2,
1033 # "cpu-throttle-increment": 10,
1034 # "compress-threads": 8,
1035 # "compress-level": 1,
1036 # "cpu-throttle-initial": 20,
1037 # "max-bandwidth": 33554432,
1038 # "downtime-limit": 300
1039 # }
1040 # }
1041 #
1042 ##
1043 { 'command': 'query-migrate-parameters',
1044 'returns': 'MigrationParameters' }
1045
1046 ##
1047 # @client_migrate_info:
1048 #
1049 # Set migration information for remote display. This makes the server
1050 # ask the client to automatically reconnect using the new parameters
1051 # once migration finished successfully. Only implemented for SPICE.
1052 #
1053 # @protocol: must be "spice"
1054 # @hostname: migration target hostname
1055 # @port: #optional spice tcp port for plaintext channels
1056 # @tls-port: #optional spice tcp port for tls-secured channels
1057 # @cert-subject: #optional server certificate subject
1058 #
1059 # Since: 0.14.0
1060 #
1061 # Example:
1062 #
1063 # -> { "execute": "client_migrate_info",
1064 # "arguments": { "protocol": "spice",
1065 # "hostname": "virt42.lab.kraxel.org",
1066 # "port": 1234 } }
1067 # <- { "return": {} }
1068 #
1069 ##
1070 { 'command': 'client_migrate_info',
1071 'data': { 'protocol': 'str', 'hostname': 'str', '*port': 'int',
1072 '*tls-port': 'int', '*cert-subject': 'str' } }
1073
1074 ##
1075 # @migrate-start-postcopy:
1076 #
1077 # Followup to a migration command to switch the migration to postcopy mode.
1078 # The postcopy-ram capability must be set before the original migration
1079 # command.
1080 #
1081 # Since: 2.5
1082 #
1083 # Example:
1084 #
1085 # -> { "execute": "migrate-start-postcopy" }
1086 # <- { "return": {} }
1087 #
1088 ##
1089 { 'command': 'migrate-start-postcopy' }
1090
1091 ##
1092 # @COLOMessage:
1093 #
1094 # The message transmission between Primary side and Secondary side.
1095 #
1096 # @checkpoint-ready: Secondary VM (SVM) is ready for checkpointing
1097 #
1098 # @checkpoint-request: Primary VM (PVM) tells SVM to prepare for checkpointing
1099 #
1100 # @checkpoint-reply: SVM gets PVM's checkpoint request
1101 #
1102 # @vmstate-send: VM's state will be sent by PVM.
1103 #
1104 # @vmstate-size: The total size of VMstate.
1105 #
1106 # @vmstate-received: VM's state has been received by SVM.
1107 #
1108 # @vmstate-loaded: VM's state has been loaded by SVM.
1109 #
1110 # Since: 2.8
1111 ##
1112 { 'enum': 'COLOMessage',
1113 'data': [ 'checkpoint-ready', 'checkpoint-request', 'checkpoint-reply',
1114 'vmstate-send', 'vmstate-size', 'vmstate-received',
1115 'vmstate-loaded' ] }
1116
1117 ##
1118 # @COLOMode:
1119 #
1120 # The colo mode
1121 #
1122 # @unknown: unknown mode
1123 #
1124 # @primary: master side
1125 #
1126 # @secondary: slave side
1127 #
1128 # Since: 2.8
1129 ##
1130 { 'enum': 'COLOMode',
1131 'data': [ 'unknown', 'primary', 'secondary'] }
1132
1133 ##
1134 # @FailoverStatus:
1135 #
1136 # An enumeration of COLO failover status
1137 #
1138 # @none: no failover has ever happened
1139 #
1140 # @require: got failover requirement but not handled
1141 #
1142 # @active: in the process of doing failover
1143 #
1144 # @completed: finish the process of failover
1145 #
1146 # Since: 2.8
1147 ##
1148 { 'enum': 'FailoverStatus',
1149 'data': [ 'none', 'require', 'active', 'completed'] }
1150
1151 ##
1152 # @x-colo-lost-heartbeat:
1153 #
1154 # Tell qemu that heartbeat is lost, request it to do takeover procedures.
1155 # If this command is sent to the PVM, the Primary side will exit COLO mode.
1156 # If sent to the Secondary, the Secondary side will run failover work,
1157 # then takes over server operation to become the service VM.
1158 #
1159 # Since: 2.8
1160 ##
1161 { 'command': 'x-colo-lost-heartbeat' }
1162
1163 ##
1164 # @MouseInfo:
1165 #
1166 # Information about a mouse device.
1167 #
1168 # @name: the name of the mouse device
1169 #
1170 # @index: the index of the mouse device
1171 #
1172 # @current: true if this device is currently receiving mouse events
1173 #
1174 # @absolute: true if this device supports absolute coordinates as input
1175 #
1176 # Since: 0.14.0
1177 ##
1178 { 'struct': 'MouseInfo',
1179 'data': {'name': 'str', 'index': 'int', 'current': 'bool',
1180 'absolute': 'bool'} }
1181
1182 ##
1183 # @query-mice:
1184 #
1185 # Returns information about each active mouse device
1186 #
1187 # Returns: a list of @MouseInfo for each device
1188 #
1189 # Since: 0.14.0
1190 #
1191 # Example:
1192 #
1193 # -> { "execute": "query-mice" }
1194 # <- { "return": [
1195 # {
1196 # "name":"QEMU Microsoft Mouse",
1197 # "index":0,
1198 # "current":false,
1199 # "absolute":false
1200 # },
1201 # {
1202 # "name":"QEMU PS/2 Mouse",
1203 # "index":1,
1204 # "current":true,
1205 # "absolute":true
1206 # }
1207 # ]
1208 # }
1209 #
1210 ##
1211 { 'command': 'query-mice', 'returns': ['MouseInfo'] }
1212
1213 ##
1214 # @CpuInfoArch:
1215 #
1216 # An enumeration of cpu types that enable additional information during
1217 # @query-cpus.
1218 #
1219 # Since: 2.6
1220 ##
1221 { 'enum': 'CpuInfoArch',
1222 'data': ['x86', 'sparc', 'ppc', 'mips', 'tricore', 'other' ] }
1223
1224 ##
1225 # @CpuInfo:
1226 #
1227 # Information about a virtual CPU
1228 #
1229 # @CPU: the index of the virtual CPU
1230 #
1231 # @current: this only exists for backwards compatibility and should be ignored
1232 #
1233 # @halted: true if the virtual CPU is in the halt state. Halt usually refers
1234 # to a processor specific low power mode.
1235 #
1236 # @qom_path: path to the CPU object in the QOM tree (since 2.4)
1237 #
1238 # @thread_id: ID of the underlying host thread
1239 #
1240 # @arch: architecture of the cpu, which determines which additional fields
1241 # will be listed (since 2.6)
1242 #
1243 # Since: 0.14.0
1244 #
1245 # Notes: @halted is a transient state that changes frequently. By the time the
1246 # data is sent to the client, the guest may no longer be halted.
1247 ##
1248 { 'union': 'CpuInfo',
1249 'base': {'CPU': 'int', 'current': 'bool', 'halted': 'bool',
1250 'qom_path': 'str', 'thread_id': 'int', 'arch': 'CpuInfoArch' },
1251 'discriminator': 'arch',
1252 'data': { 'x86': 'CpuInfoX86',
1253 'sparc': 'CpuInfoSPARC',
1254 'ppc': 'CpuInfoPPC',
1255 'mips': 'CpuInfoMIPS',
1256 'tricore': 'CpuInfoTricore',
1257 'other': 'CpuInfoOther' } }
1258
1259 ##
1260 # @CpuInfoX86:
1261 #
1262 # Additional information about a virtual i386 or x86_64 CPU
1263 #
1264 # @pc: the 64-bit instruction pointer
1265 #
1266 # Since: 2.6
1267 ##
1268 { 'struct': 'CpuInfoX86', 'data': { 'pc': 'int' } }
1269
1270 ##
1271 # @CpuInfoSPARC:
1272 #
1273 # Additional information about a virtual SPARC CPU
1274 #
1275 # @pc: the PC component of the instruction pointer
1276 #
1277 # @npc: the NPC component of the instruction pointer
1278 #
1279 # Since: 2.6
1280 ##
1281 { 'struct': 'CpuInfoSPARC', 'data': { 'pc': 'int', 'npc': 'int' } }
1282
1283 ##
1284 # @CpuInfoPPC:
1285 #
1286 # Additional information about a virtual PPC CPU
1287 #
1288 # @nip: the instruction pointer
1289 #
1290 # Since: 2.6
1291 ##
1292 { 'struct': 'CpuInfoPPC', 'data': { 'nip': 'int' } }
1293
1294 ##
1295 # @CpuInfoMIPS:
1296 #
1297 # Additional information about a virtual MIPS CPU
1298 #
1299 # @PC: the instruction pointer
1300 #
1301 # Since: 2.6
1302 ##
1303 { 'struct': 'CpuInfoMIPS', 'data': { 'PC': 'int' } }
1304
1305 ##
1306 # @CpuInfoTricore:
1307 #
1308 # Additional information about a virtual Tricore CPU
1309 #
1310 # @PC: the instruction pointer
1311 #
1312 # Since: 2.6
1313 ##
1314 { 'struct': 'CpuInfoTricore', 'data': { 'PC': 'int' } }
1315
1316 ##
1317 # @CpuInfoOther:
1318 #
1319 # No additional information is available about the virtual CPU
1320 #
1321 # Since: 2.6
1322 #
1323 ##
1324 { 'struct': 'CpuInfoOther', 'data': { } }
1325
1326 ##
1327 # @query-cpus:
1328 #
1329 # Returns a list of information about each virtual CPU.
1330 #
1331 # Returns: a list of @CpuInfo for each virtual CPU
1332 #
1333 # Since: 0.14.0
1334 #
1335 # Example:
1336 #
1337 # -> { "execute": "query-cpus" }
1338 # <- { "return": [
1339 # {
1340 # "CPU":0,
1341 # "current":true,
1342 # "halted":false,
1343 # "qom_path":"/machine/unattached/device[0]",
1344 # "arch":"x86",
1345 # "pc":3227107138,
1346 # "thread_id":3134
1347 # },
1348 # {
1349 # "CPU":1,
1350 # "current":false,
1351 # "halted":true,
1352 # "qom_path":"/machine/unattached/device[2]",
1353 # "arch":"x86",
1354 # "pc":7108165,
1355 # "thread_id":3135
1356 # }
1357 # ]
1358 # }
1359 #
1360 ##
1361 { 'command': 'query-cpus', 'returns': ['CpuInfo'] }
1362
1363 ##
1364 # @IOThreadInfo:
1365 #
1366 # Information about an iothread
1367 #
1368 # @id: the identifier of the iothread
1369 #
1370 # @thread-id: ID of the underlying host thread
1371 #
1372 # Since: 2.0
1373 ##
1374 { 'struct': 'IOThreadInfo',
1375 'data': {'id': 'str', 'thread-id': 'int'} }
1376
1377 ##
1378 # @query-iothreads:
1379 #
1380 # Returns a list of information about each iothread.
1381 #
1382 # Note: this list excludes the QEMU main loop thread, which is not declared
1383 # using the -object iothread command-line option. It is always the main thread
1384 # of the process.
1385 #
1386 # Returns: a list of @IOThreadInfo for each iothread
1387 #
1388 # Since: 2.0
1389 #
1390 # Example:
1391 #
1392 # -> { "execute": "query-iothreads" }
1393 # <- { "return": [
1394 # {
1395 # "id":"iothread0",
1396 # "thread-id":3134
1397 # },
1398 # {
1399 # "id":"iothread1",
1400 # "thread-id":3135
1401 # }
1402 # ]
1403 # }
1404 #
1405 ##
1406 { 'command': 'query-iothreads', 'returns': ['IOThreadInfo'] }
1407
1408 ##
1409 # @NetworkAddressFamily:
1410 #
1411 # The network address family
1412 #
1413 # @ipv4: IPV4 family
1414 #
1415 # @ipv6: IPV6 family
1416 #
1417 # @unix: unix socket
1418 #
1419 # @vsock: vsock family (since 2.8)
1420 #
1421 # @unknown: otherwise
1422 #
1423 # Since: 2.1
1424 ##
1425 { 'enum': 'NetworkAddressFamily',
1426 'data': [ 'ipv4', 'ipv6', 'unix', 'vsock', 'unknown' ] }
1427
1428 ##
1429 # @VncBasicInfo:
1430 #
1431 # The basic information for vnc network connection
1432 #
1433 # @host: IP address
1434 #
1435 # @service: The service name of the vnc port. This may depend on the host
1436 # system's service database so symbolic names should not be relied
1437 # on.
1438 #
1439 # @family: address family
1440 #
1441 # @websocket: true in case the socket is a websocket (since 2.3).
1442 #
1443 # Since: 2.1
1444 ##
1445 { 'struct': 'VncBasicInfo',
1446 'data': { 'host': 'str',
1447 'service': 'str',
1448 'family': 'NetworkAddressFamily',
1449 'websocket': 'bool' } }
1450
1451 ##
1452 # @VncServerInfo:
1453 #
1454 # The network connection information for server
1455 #
1456 # @auth: #optional, authentication method
1457 #
1458 # Since: 2.1
1459 ##
1460 { 'struct': 'VncServerInfo',
1461 'base': 'VncBasicInfo',
1462 'data': { '*auth': 'str' } }
1463
1464 ##
1465 # @VncClientInfo:
1466 #
1467 # Information about a connected VNC client.
1468 #
1469 # @x509_dname: #optional If x509 authentication is in use, the Distinguished
1470 # Name of the client.
1471 #
1472 # @sasl_username: #optional If SASL authentication is in use, the SASL username
1473 # used for authentication.
1474 #
1475 # Since: 0.14.0
1476 ##
1477 { 'struct': 'VncClientInfo',
1478 'base': 'VncBasicInfo',
1479 'data': { '*x509_dname': 'str', '*sasl_username': 'str' } }
1480
1481 ##
1482 # @VncInfo:
1483 #
1484 # Information about the VNC session.
1485 #
1486 # @enabled: true if the VNC server is enabled, false otherwise
1487 #
1488 # @host: #optional The hostname the VNC server is bound to. This depends on
1489 # the name resolution on the host and may be an IP address.
1490 #
1491 # @family: #optional 'ipv6' if the host is listening for IPv6 connections
1492 # 'ipv4' if the host is listening for IPv4 connections
1493 # 'unix' if the host is listening on a unix domain socket
1494 # 'unknown' otherwise
1495 #
1496 # @service: #optional The service name of the server's port. This may depends
1497 # on the host system's service database so symbolic names should not
1498 # be relied on.
1499 #
1500 # @auth: #optional the current authentication type used by the server
1501 # 'none' if no authentication is being used
1502 # 'vnc' if VNC authentication is being used
1503 # 'vencrypt+plain' if VEncrypt is used with plain text authentication
1504 # 'vencrypt+tls+none' if VEncrypt is used with TLS and no authentication
1505 # 'vencrypt+tls+vnc' if VEncrypt is used with TLS and VNC authentication
1506 # 'vencrypt+tls+plain' if VEncrypt is used with TLS and plain text auth
1507 # 'vencrypt+x509+none' if VEncrypt is used with x509 and no auth
1508 # 'vencrypt+x509+vnc' if VEncrypt is used with x509 and VNC auth
1509 # 'vencrypt+x509+plain' if VEncrypt is used with x509 and plain text auth
1510 # 'vencrypt+tls+sasl' if VEncrypt is used with TLS and SASL auth
1511 # 'vencrypt+x509+sasl' if VEncrypt is used with x509 and SASL auth
1512 #
1513 # @clients: a list of @VncClientInfo of all currently connected clients
1514 #
1515 # Since: 0.14.0
1516 ##
1517 { 'struct': 'VncInfo',
1518 'data': {'enabled': 'bool', '*host': 'str',
1519 '*family': 'NetworkAddressFamily',
1520 '*service': 'str', '*auth': 'str', '*clients': ['VncClientInfo']} }
1521
1522 ##
1523 # @VncPrimaryAuth:
1524 #
1525 # vnc primary authentication method.
1526 #
1527 # Since: 2.3
1528 ##
1529 { 'enum': 'VncPrimaryAuth',
1530 'data': [ 'none', 'vnc', 'ra2', 'ra2ne', 'tight', 'ultra',
1531 'tls', 'vencrypt', 'sasl' ] }
1532
1533 ##
1534 # @VncVencryptSubAuth:
1535 #
1536 # vnc sub authentication method with vencrypt.
1537 #
1538 # Since: 2.3
1539 ##
1540 { 'enum': 'VncVencryptSubAuth',
1541 'data': [ 'plain',
1542 'tls-none', 'x509-none',
1543 'tls-vnc', 'x509-vnc',
1544 'tls-plain', 'x509-plain',
1545 'tls-sasl', 'x509-sasl' ] }
1546
1547 ##
1548 # @VncInfo2:
1549 #
1550 # Information about a vnc server
1551 #
1552 # @id: vnc server name.
1553 #
1554 # @server: A list of @VncBasincInfo describing all listening sockets.
1555 # The list can be empty (in case the vnc server is disabled).
1556 # It also may have multiple entries: normal + websocket,
1557 # possibly also ipv4 + ipv6 in the future.
1558 #
1559 # @clients: A list of @VncClientInfo of all currently connected clients.
1560 # The list can be empty, for obvious reasons.
1561 #
1562 # @auth: The current authentication type used by the server
1563 #
1564 # @vencrypt: #optional The vencrypt sub authentication type used by the server,
1565 # only specified in case auth == vencrypt.
1566 #
1567 # @display: #optional The display device the vnc server is linked to.
1568 #
1569 # Since: 2.3
1570 ##
1571 { 'struct': 'VncInfo2',
1572 'data': { 'id' : 'str',
1573 'server' : ['VncBasicInfo'],
1574 'clients' : ['VncClientInfo'],
1575 'auth' : 'VncPrimaryAuth',
1576 '*vencrypt' : 'VncVencryptSubAuth',
1577 '*display' : 'str' } }
1578
1579 ##
1580 # @query-vnc:
1581 #
1582 # Returns information about the current VNC server
1583 #
1584 # Returns: @VncInfo
1585 #
1586 # Since: 0.14.0
1587 #
1588 # Example:
1589 #
1590 # -> { "execute": "query-vnc" }
1591 # <- { "return": {
1592 # "enabled":true,
1593 # "host":"0.0.0.0",
1594 # "service":"50402",
1595 # "auth":"vnc",
1596 # "family":"ipv4",
1597 # "clients":[
1598 # {
1599 # "host":"127.0.0.1",
1600 # "service":"50401",
1601 # "family":"ipv4"
1602 # }
1603 # ]
1604 # }
1605 # }
1606 #
1607 ##
1608 { 'command': 'query-vnc', 'returns': 'VncInfo' }
1609
1610 ##
1611 # @query-vnc-servers:
1612 #
1613 # Returns a list of vnc servers. The list can be empty.
1614 #
1615 # Returns: a list of @VncInfo2
1616 #
1617 # Since: 2.3
1618 ##
1619 { 'command': 'query-vnc-servers', 'returns': ['VncInfo2'] }
1620
1621 ##
1622 # @SpiceBasicInfo:
1623 #
1624 # The basic information for SPICE network connection
1625 #
1626 # @host: IP address
1627 #
1628 # @port: port number
1629 #
1630 # @family: address family
1631 #
1632 # Since: 2.1
1633 ##
1634 { 'struct': 'SpiceBasicInfo',
1635 'data': { 'host': 'str',
1636 'port': 'str',
1637 'family': 'NetworkAddressFamily' } }
1638
1639 ##
1640 # @SpiceServerInfo:
1641 #
1642 # Information about a SPICE server
1643 #
1644 # @auth: #optional, authentication method
1645 #
1646 # Since: 2.1
1647 ##
1648 { 'struct': 'SpiceServerInfo',
1649 'base': 'SpiceBasicInfo',
1650 'data': { '*auth': 'str' } }
1651
1652 ##
1653 # @SpiceChannel:
1654 #
1655 # Information about a SPICE client channel.
1656 #
1657 # @connection-id: SPICE connection id number. All channels with the same id
1658 # belong to the same SPICE session.
1659 #
1660 # @channel-type: SPICE channel type number. "1" is the main control
1661 # channel, filter for this one if you want to track spice
1662 # sessions only
1663 #
1664 # @channel-id: SPICE channel ID number. Usually "0", might be different when
1665 # multiple channels of the same type exist, such as multiple
1666 # display channels in a multihead setup
1667 #
1668 # @tls: true if the channel is encrypted, false otherwise.
1669 #
1670 # Since: 0.14.0
1671 ##
1672 { 'struct': 'SpiceChannel',
1673 'base': 'SpiceBasicInfo',
1674 'data': {'connection-id': 'int', 'channel-type': 'int', 'channel-id': 'int',
1675 'tls': 'bool'} }
1676
1677 ##
1678 # @SpiceQueryMouseMode:
1679 #
1680 # An enumeration of Spice mouse states.
1681 #
1682 # @client: Mouse cursor position is determined by the client.
1683 #
1684 # @server: Mouse cursor position is determined by the server.
1685 #
1686 # @unknown: No information is available about mouse mode used by
1687 # the spice server.
1688 #
1689 # Note: spice/enums.h has a SpiceMouseMode already, hence the name.
1690 #
1691 # Since: 1.1
1692 ##
1693 { 'enum': 'SpiceQueryMouseMode',
1694 'data': [ 'client', 'server', 'unknown' ] }
1695
1696 ##
1697 # @SpiceInfo:
1698 #
1699 # Information about the SPICE session.
1700 #
1701 # @enabled: true if the SPICE server is enabled, false otherwise
1702 #
1703 # @migrated: true if the last guest migration completed and spice
1704 # migration had completed as well. false otherwise. (since 1.4)
1705 #
1706 # @host: #optional The hostname the SPICE server is bound to. This depends on
1707 # the name resolution on the host and may be an IP address.
1708 #
1709 # @port: #optional The SPICE server's port number.
1710 #
1711 # @compiled-version: #optional SPICE server version.
1712 #
1713 # @tls-port: #optional The SPICE server's TLS port number.
1714 #
1715 # @auth: #optional the current authentication type used by the server
1716 # 'none' if no authentication is being used
1717 # 'spice' uses SASL or direct TLS authentication, depending on command
1718 # line options
1719 #
1720 # @mouse-mode: The mode in which the mouse cursor is displayed currently. Can
1721 # be determined by the client or the server, or unknown if spice
1722 # server doesn't provide this information. (since: 1.1)
1723 #
1724 # @channels: a list of @SpiceChannel for each active spice channel
1725 #
1726 # Since: 0.14.0
1727 ##
1728 { 'struct': 'SpiceInfo',
1729 'data': {'enabled': 'bool', 'migrated': 'bool', '*host': 'str', '*port': 'int',
1730 '*tls-port': 'int', '*auth': 'str', '*compiled-version': 'str',
1731 'mouse-mode': 'SpiceQueryMouseMode', '*channels': ['SpiceChannel']} }
1732
1733 ##
1734 # @query-spice:
1735 #
1736 # Returns information about the current SPICE server
1737 #
1738 # Returns: @SpiceInfo
1739 #
1740 # Since: 0.14.0
1741 #
1742 # Example:
1743 #
1744 # -> { "execute": "query-spice" }
1745 # <- { "return": {
1746 # "enabled": true,
1747 # "auth": "spice",
1748 # "port": 5920,
1749 # "tls-port": 5921,
1750 # "host": "0.0.0.0",
1751 # "channels": [
1752 # {
1753 # "port": "54924",
1754 # "family": "ipv4",
1755 # "channel-type": 1,
1756 # "connection-id": 1804289383,
1757 # "host": "127.0.0.1",
1758 # "channel-id": 0,
1759 # "tls": true
1760 # },
1761 # {
1762 # "port": "36710",
1763 # "family": "ipv4",
1764 # "channel-type": 4,
1765 # "connection-id": 1804289383,
1766 # "host": "127.0.0.1",
1767 # "channel-id": 0,
1768 # "tls": false
1769 # },
1770 # [ ... more channels follow ... ]
1771 # ]
1772 # }
1773 # }
1774 #
1775 ##
1776 { 'command': 'query-spice', 'returns': 'SpiceInfo' }
1777
1778 ##
1779 # @BalloonInfo:
1780 #
1781 # Information about the guest balloon device.
1782 #
1783 # @actual: the number of bytes the balloon currently contains
1784 #
1785 # Since: 0.14.0
1786 #
1787 ##
1788 { 'struct': 'BalloonInfo', 'data': {'actual': 'int' } }
1789
1790 ##
1791 # @query-balloon:
1792 #
1793 # Return information about the balloon device.
1794 #
1795 # Returns: @BalloonInfo on success
1796 #
1797 # If the balloon driver is enabled but not functional because the KVM
1798 # kernel module cannot support it, KvmMissingCap
1799 #
1800 # If no balloon device is present, DeviceNotActive
1801 #
1802 # Since: 0.14.0
1803 #
1804 # Example:
1805 #
1806 # -> { "execute": "query-balloon" }
1807 # <- { "return": {
1808 # "actual": 1073741824,
1809 # }
1810 # }
1811 #
1812 ##
1813 { 'command': 'query-balloon', 'returns': 'BalloonInfo' }
1814
1815 ##
1816 # @PciMemoryRange:
1817 #
1818 # A PCI device memory region
1819 #
1820 # @base: the starting address (guest physical)
1821 #
1822 # @limit: the ending address (guest physical)
1823 #
1824 # Since: 0.14.0
1825 ##
1826 { 'struct': 'PciMemoryRange', 'data': {'base': 'int', 'limit': 'int'} }
1827
1828 ##
1829 # @PciMemoryRegion:
1830 #
1831 # Information about a PCI device I/O region.
1832 #
1833 # @bar: the index of the Base Address Register for this region
1834 #
1835 # @type: 'io' if the region is a PIO region
1836 # 'memory' if the region is a MMIO region
1837 #
1838 # @size: memory size
1839 #
1840 # @prefetch: #optional if @type is 'memory', true if the memory is prefetchable
1841 #
1842 # @mem_type_64: #optional if @type is 'memory', true if the BAR is 64-bit
1843 #
1844 # Since: 0.14.0
1845 ##
1846 { 'struct': 'PciMemoryRegion',
1847 'data': {'bar': 'int', 'type': 'str', 'address': 'int', 'size': 'int',
1848 '*prefetch': 'bool', '*mem_type_64': 'bool' } }
1849
1850 ##
1851 # @PciBusInfo:
1852 #
1853 # Information about a bus of a PCI Bridge device
1854 #
1855 # @number: primary bus interface number. This should be the number of the
1856 # bus the device resides on.
1857 #
1858 # @secondary: secondary bus interface number. This is the number of the
1859 # main bus for the bridge
1860 #
1861 # @subordinate: This is the highest number bus that resides below the
1862 # bridge.
1863 #
1864 # @io_range: The PIO range for all devices on this bridge
1865 #
1866 # @memory_range: The MMIO range for all devices on this bridge
1867 #
1868 # @prefetchable_range: The range of prefetchable MMIO for all devices on
1869 # this bridge
1870 #
1871 # Since: 2.4
1872 ##
1873 { 'struct': 'PciBusInfo',
1874 'data': {'number': 'int', 'secondary': 'int', 'subordinate': 'int',
1875 'io_range': 'PciMemoryRange',
1876 'memory_range': 'PciMemoryRange',
1877 'prefetchable_range': 'PciMemoryRange' } }
1878
1879 ##
1880 # @PciBridgeInfo:
1881 #
1882 # Information about a PCI Bridge device
1883 #
1884 # @bus: information about the bus the device resides on
1885 #
1886 # @devices: a list of @PciDeviceInfo for each device on this bridge
1887 #
1888 # Since: 0.14.0
1889 ##
1890 { 'struct': 'PciBridgeInfo',
1891 'data': {'bus': 'PciBusInfo', '*devices': ['PciDeviceInfo']} }
1892
1893 ##
1894 # @PciDeviceClass:
1895 #
1896 # Information about the Class of a PCI device
1897 #
1898 # @desc: #optional a string description of the device's class
1899 #
1900 # @class: the class code of the device
1901 #
1902 # Since: 2.4
1903 ##
1904 { 'struct': 'PciDeviceClass',
1905 'data': {'*desc': 'str', 'class': 'int'} }
1906
1907 ##
1908 # @PciDeviceId:
1909 #
1910 # Information about the Id of a PCI device
1911 #
1912 # @device: the PCI device id
1913 #
1914 # @vendor: the PCI vendor id
1915 #
1916 # Since: 2.4
1917 ##
1918 { 'struct': 'PciDeviceId',
1919 'data': {'device': 'int', 'vendor': 'int'} }
1920
1921 ##
1922 # @PciDeviceInfo:
1923 #
1924 # Information about a PCI device
1925 #
1926 # @bus: the bus number of the device
1927 #
1928 # @slot: the slot the device is located in
1929 #
1930 # @function: the function of the slot used by the device
1931 #
1932 # @class_info: the class of the device
1933 #
1934 # @id: the PCI device id
1935 #
1936 # @irq: #optional if an IRQ is assigned to the device, the IRQ number
1937 #
1938 # @qdev_id: the device name of the PCI device
1939 #
1940 # @pci_bridge: if the device is a PCI bridge, the bridge information
1941 #
1942 # @regions: a list of the PCI I/O regions associated with the device
1943 #
1944 # Notes: the contents of @class_info.desc are not stable and should only be
1945 # treated as informational.
1946 #
1947 # Since: 0.14.0
1948 ##
1949 { 'struct': 'PciDeviceInfo',
1950 'data': {'bus': 'int', 'slot': 'int', 'function': 'int',
1951 'class_info': 'PciDeviceClass', 'id': 'PciDeviceId',
1952 '*irq': 'int', 'qdev_id': 'str', '*pci_bridge': 'PciBridgeInfo',
1953 'regions': ['PciMemoryRegion']} }
1954
1955 ##
1956 # @PciInfo:
1957 #
1958 # Information about a PCI bus
1959 #
1960 # @bus: the bus index
1961 #
1962 # @devices: a list of devices on this bus
1963 #
1964 # Since: 0.14.0
1965 ##
1966 { 'struct': 'PciInfo', 'data': {'bus': 'int', 'devices': ['PciDeviceInfo']} }
1967
1968 ##
1969 # @query-pci:
1970 #
1971 # Return information about the PCI bus topology of the guest.
1972 #
1973 # Returns: a list of @PciInfo for each PCI bus. Each bus is
1974 # represented by a json-object, which has a key with a json-array of
1975 # all PCI devices attached to it. Each device is represented by a
1976 # json-object.
1977 #
1978 # Since: 0.14.0
1979 #
1980 # Example:
1981 #
1982 # -> { "execute": "query-pci" }
1983 # <- { "return": [
1984 # {
1985 # "bus": 0,
1986 # "devices": [
1987 # {
1988 # "bus": 0,
1989 # "qdev_id": "",
1990 # "slot": 0,
1991 # "class_info": {
1992 # "class": 1536,
1993 # "desc": "Host bridge"
1994 # },
1995 # "id": {
1996 # "device": 32902,
1997 # "vendor": 4663
1998 # },
1999 # "function": 0,
2000 # "regions": [
2001 # ]
2002 # },
2003 # {
2004 # "bus": 0,
2005 # "qdev_id": "",
2006 # "slot": 1,
2007 # "class_info": {
2008 # "class": 1537,
2009 # "desc": "ISA bridge"
2010 # },
2011 # "id": {
2012 # "device": 32902,
2013 # "vendor": 28672
2014 # },
2015 # "function": 0,
2016 # "regions": [
2017 # ]
2018 # },
2019 # {
2020 # "bus": 0,
2021 # "qdev_id": "",
2022 # "slot": 1,
2023 # "class_info": {
2024 # "class": 257,
2025 # "desc": "IDE controller"
2026 # },
2027 # "id": {
2028 # "device": 32902,
2029 # "vendor": 28688
2030 # },
2031 # "function": 1,
2032 # "regions": [
2033 # {
2034 # "bar": 4,
2035 # "size": 16,
2036 # "address": 49152,
2037 # "type": "io"
2038 # }
2039 # ]
2040 # },
2041 # {
2042 # "bus": 0,
2043 # "qdev_id": "",
2044 # "slot": 2,
2045 # "class_info": {
2046 # "class": 768,
2047 # "desc": "VGA controller"
2048 # },
2049 # "id": {
2050 # "device": 4115,
2051 # "vendor": 184
2052 # },
2053 # "function": 0,
2054 # "regions": [
2055 # {
2056 # "prefetch": true,
2057 # "mem_type_64": false,
2058 # "bar": 0,
2059 # "size": 33554432,
2060 # "address": 4026531840,
2061 # "type": "memory"
2062 # },
2063 # {
2064 # "prefetch": false,
2065 # "mem_type_64": false,
2066 # "bar": 1,
2067 # "size": 4096,
2068 # "address": 4060086272,
2069 # "type": "memory"
2070 # },
2071 # {
2072 # "prefetch": false,
2073 # "mem_type_64": false,
2074 # "bar": 6,
2075 # "size": 65536,
2076 # "address": -1,
2077 # "type": "memory"
2078 # }
2079 # ]
2080 # },
2081 # {
2082 # "bus": 0,
2083 # "qdev_id": "",
2084 # "irq": 11,
2085 # "slot": 4,
2086 # "class_info": {
2087 # "class": 1280,
2088 # "desc": "RAM controller"
2089 # },
2090 # "id": {
2091 # "device": 6900,
2092 # "vendor": 4098
2093 # },
2094 # "function": 0,
2095 # "regions": [
2096 # {
2097 # "bar": 0,
2098 # "size": 32,
2099 # "address": 49280,
2100 # "type": "io"
2101 # }
2102 # ]
2103 # }
2104 # ]
2105 # }
2106 # ]
2107 # }
2108 #
2109 # Note: This example has been shortened as the real response is too long.
2110 #
2111 ##
2112 { 'command': 'query-pci', 'returns': ['PciInfo'] }
2113
2114 ##
2115 # @quit:
2116 #
2117 # This command will cause the QEMU process to exit gracefully. While every
2118 # attempt is made to send the QMP response before terminating, this is not
2119 # guaranteed. When using this interface, a premature EOF would not be
2120 # unexpected.
2121 #
2122 # Since: 0.14.0
2123 #
2124 # Example:
2125 #
2126 # -> { "execute": "quit" }
2127 # <- { "return": {} }
2128 ##
2129 { 'command': 'quit' }
2130
2131 ##
2132 # @stop:
2133 #
2134 # Stop all guest VCPU execution.
2135 #
2136 # Since: 0.14.0
2137 #
2138 # Notes: This function will succeed even if the guest is already in the stopped
2139 # state. In "inmigrate" state, it will ensure that the guest
2140 # remains paused once migration finishes, as if the -S option was
2141 # passed on the command line.
2142 #
2143 # Example:
2144 #
2145 # -> { "execute": "stop" }
2146 # <- { "return": {} }
2147 #
2148 ##
2149 { 'command': 'stop' }
2150
2151 ##
2152 # @system_reset:
2153 #
2154 # Performs a hard reset of a guest.
2155 #
2156 # Since: 0.14.0
2157 #
2158 # Example:
2159 #
2160 # -> { "execute": "system_reset" }
2161 # <- { "return": {} }
2162 #
2163 ##
2164 { 'command': 'system_reset' }
2165
2166 ##
2167 # @system_powerdown:
2168 #
2169 # Requests that a guest perform a powerdown operation.
2170 #
2171 # Since: 0.14.0
2172 #
2173 # Notes: A guest may or may not respond to this command. This command
2174 # returning does not indicate that a guest has accepted the request or
2175 # that it has shut down. Many guests will respond to this command by
2176 # prompting the user in some way.
2177 # Example:
2178 #
2179 # -> { "execute": "system_powerdown" }
2180 # <- { "return": {} }
2181 #
2182 ##
2183 { 'command': 'system_powerdown' }
2184
2185 ##
2186 # @cpu:
2187 #
2188 # This command is a nop that is only provided for the purposes of compatibility.
2189 #
2190 # Since: 0.14.0
2191 #
2192 # Notes: Do not use this command.
2193 ##
2194 { 'command': 'cpu', 'data': {'index': 'int'} }
2195
2196 ##
2197 # @cpu-add:
2198 #
2199 # Adds CPU with specified ID
2200 #
2201 # @id: ID of CPU to be created, valid values [0..max_cpus)
2202 #
2203 # Returns: Nothing on success
2204 #
2205 # Since: 1.5
2206 #
2207 # Example:
2208 #
2209 # -> { "execute": "cpu-add", "arguments": { "id": 2 } }
2210 # <- { "return": {} }
2211 #
2212 ##
2213 { 'command': 'cpu-add', 'data': {'id': 'int'} }
2214
2215 ##
2216 # @memsave:
2217 #
2218 # Save a portion of guest memory to a file.
2219 #
2220 # @val: the virtual address of the guest to start from
2221 #
2222 # @size: the size of memory region to save
2223 #
2224 # @filename: the file to save the memory to as binary data
2225 #
2226 # @cpu-index: #optional the index of the virtual CPU to use for translating the
2227 # virtual address (defaults to CPU 0)
2228 #
2229 # Returns: Nothing on success
2230 #
2231 # Since: 0.14.0
2232 #
2233 # Notes: Errors were not reliably returned until 1.1
2234 #
2235 # Example:
2236 #
2237 # -> { "execute": "memsave",
2238 # "arguments": { "val": 10,
2239 # "size": 100,
2240 # "filename": "/tmp/virtual-mem-dump" } }
2241 # <- { "return": {} }
2242 #
2243 ##
2244 { 'command': 'memsave',
2245 'data': {'val': 'int', 'size': 'int', 'filename': 'str', '*cpu-index': 'int'} }
2246
2247 ##
2248 # @pmemsave:
2249 #
2250 # Save a portion of guest physical memory to a file.
2251 #
2252 # @val: the physical address of the guest to start from
2253 #
2254 # @size: the size of memory region to save
2255 #
2256 # @filename: the file to save the memory to as binary data
2257 #
2258 # Returns: Nothing on success
2259 #
2260 # Since: 0.14.0
2261 #
2262 # Notes: Errors were not reliably returned until 1.1
2263 #
2264 # Example:
2265 #
2266 # -> { "execute": "pmemsave",
2267 # "arguments": { "val": 10,
2268 # "size": 100,
2269 # "filename": "/tmp/physical-mem-dump" } }
2270 # <- { "return": {} }
2271 #
2272 ##
2273 { 'command': 'pmemsave',
2274 'data': {'val': 'int', 'size': 'int', 'filename': 'str'} }
2275
2276 ##
2277 # @cont:
2278 #
2279 # Resume guest VCPU execution.
2280 #
2281 # Since: 0.14.0
2282 #
2283 # Returns: If successful, nothing
2284 # If QEMU was started with an encrypted block device and a key has
2285 # not yet been set, DeviceEncrypted.
2286 #
2287 # Notes: This command will succeed if the guest is currently running. It
2288 # will also succeed if the guest is in the "inmigrate" state; in
2289 # this case, the effect of the command is to make sure the guest
2290 # starts once migration finishes, removing the effect of the -S
2291 # command line option if it was passed.
2292 #
2293 # Example:
2294 #
2295 # -> { "execute": "cont" }
2296 # <- { "return": {} }
2297 #
2298 ##
2299 { 'command': 'cont' }
2300
2301 ##
2302 # @system_wakeup:
2303 #
2304 # Wakeup guest from suspend. Does nothing in case the guest isn't suspended.
2305 #
2306 # Since: 1.1
2307 #
2308 # Returns: nothing.
2309 #
2310 # Example:
2311 #
2312 # -> { "execute": "system_wakeup" }
2313 # <- { "return": {} }
2314 #
2315 ##
2316 { 'command': 'system_wakeup' }
2317
2318 ##
2319 # @inject-nmi:
2320 #
2321 # Injects a Non-Maskable Interrupt into the default CPU (x86/s390) or all CPUs (ppc64).
2322 # The command fails when the guest doesn't support injecting.
2323 #
2324 # Returns: If successful, nothing
2325 #
2326 # Since: 0.14.0
2327 #
2328 # Note: prior to 2.1, this command was only supported for x86 and s390 VMs
2329 #
2330 # Example:
2331 #
2332 # -> { "execute": "inject-nmi" }
2333 # <- { "return": {} }
2334 #
2335 ##
2336 { 'command': 'inject-nmi' }
2337
2338 ##
2339 # @set_link:
2340 #
2341 # Sets the link status of a virtual network adapter.
2342 #
2343 # @name: the device name of the virtual network adapter
2344 #
2345 # @up: true to set the link status to be up
2346 #
2347 # Returns: Nothing on success
2348 # If @name is not a valid network device, DeviceNotFound
2349 #
2350 # Since: 0.14.0
2351 #
2352 # Notes: Not all network adapters support setting link status. This command
2353 # will succeed even if the network adapter does not support link status
2354 # notification.
2355 #
2356 # Example:
2357 #
2358 # -> { "execute": "set_link",
2359 # "arguments": { "name": "e1000.0", "up": false } }
2360 # <- { "return": {} }
2361 #
2362 ##
2363 { 'command': 'set_link', 'data': {'name': 'str', 'up': 'bool'} }
2364
2365 ##
2366 # @balloon:
2367 #
2368 # Request the balloon driver to change its balloon size.
2369 #
2370 # @value: the target size of the balloon in bytes
2371 #
2372 # Returns: Nothing on success
2373 # If the balloon driver is enabled but not functional because the KVM
2374 # kernel module cannot support it, KvmMissingCap
2375 # If no balloon device is present, DeviceNotActive
2376 #
2377 # Notes: This command just issues a request to the guest. When it returns,
2378 # the balloon size may not have changed. A guest can change the balloon
2379 # size independent of this command.
2380 #
2381 # Since: 0.14.0
2382 #
2383 # Example:
2384 #
2385 # -> { "execute": "balloon", "arguments": { "value": 536870912 } }
2386 # <- { "return": {} }
2387 #
2388 ##
2389 { 'command': 'balloon', 'data': {'value': 'int'} }
2390
2391 ##
2392 # @Abort:
2393 #
2394 # This action can be used to test transaction failure.
2395 #
2396 # Since: 1.6
2397 ##
2398 { 'struct': 'Abort',
2399 'data': { } }
2400
2401 ##
2402 # @ActionCompletionMode:
2403 #
2404 # An enumeration of Transactional completion modes.
2405 #
2406 # @individual: Do not attempt to cancel any other Actions if any Actions fail
2407 # after the Transaction request succeeds. All Actions that
2408 # can complete successfully will do so without waiting on others.
2409 # This is the default.
2410 #
2411 # @grouped: If any Action fails after the Transaction succeeds, cancel all
2412 # Actions. Actions do not complete until all Actions are ready to
2413 # complete. May be rejected by Actions that do not support this
2414 # completion mode.
2415 #
2416 # Since: 2.5
2417 ##
2418 { 'enum': 'ActionCompletionMode',
2419 'data': [ 'individual', 'grouped' ] }
2420
2421 ##
2422 # @TransactionAction:
2423 #
2424 # A discriminated record of operations that can be performed with
2425 # @transaction. Action @type can be:
2426 #
2427 # - @abort: since 1.6
2428 # - @block-dirty-bitmap-add: since 2.5
2429 # - @block-dirty-bitmap-clear: since 2.5
2430 # - @blockdev-backup: since 2.3
2431 # - @blockdev-snapshot: since 2.5
2432 # - @blockdev-snapshot-internal-sync: since 1.7
2433 # - @blockdev-snapshot-sync: since 1.1
2434 # - @drive-backup: since 1.6
2435 #
2436 # Since: 1.1
2437 ##
2438 { 'union': 'TransactionAction',
2439 'data': {
2440 'abort': 'Abort',
2441 'block-dirty-bitmap-add': 'BlockDirtyBitmapAdd',
2442 'block-dirty-bitmap-clear': 'BlockDirtyBitmap',
2443 'blockdev-backup': 'BlockdevBackup',
2444 'blockdev-snapshot': 'BlockdevSnapshot',
2445 'blockdev-snapshot-internal-sync': 'BlockdevSnapshotInternal',
2446 'blockdev-snapshot-sync': 'BlockdevSnapshotSync',
2447 'drive-backup': 'DriveBackup'
2448 } }
2449
2450 ##
2451 # @TransactionProperties:
2452 #
2453 # Optional arguments to modify the behavior of a Transaction.
2454 #
2455 # @completion-mode: #optional Controls how jobs launched asynchronously by
2456 # Actions will complete or fail as a group.
2457 # See @ActionCompletionMode for details.
2458 #
2459 # Since: 2.5
2460 ##
2461 { 'struct': 'TransactionProperties',
2462 'data': {
2463 '*completion-mode': 'ActionCompletionMode'
2464 }
2465 }
2466
2467 ##
2468 # @transaction:
2469 #
2470 # Executes a number of transactionable QMP commands atomically. If any
2471 # operation fails, then the entire set of actions will be abandoned and the
2472 # appropriate error returned.
2473 #
2474 # For external snapshots, the dictionary contains the device, the file to use for
2475 # the new snapshot, and the format. The default format, if not specified, is
2476 # qcow2.
2477 #
2478 # Each new snapshot defaults to being created by QEMU (wiping any
2479 # contents if the file already exists), but it is also possible to reuse
2480 # an externally-created file. In the latter case, you should ensure that
2481 # the new image file has the same contents as the current one; QEMU cannot
2482 # perform any meaningful check. Typically this is achieved by using the
2483 # current image file as the backing file for the new image.
2484 #
2485 # On failure, the original disks pre-snapshot attempt will be used.
2486 #
2487 # For internal snapshots, the dictionary contains the device and the snapshot's
2488 # name. If an internal snapshot matching name already exists, the request will
2489 # be rejected. Only some image formats support it, for example, qcow2, rbd,
2490 # and sheepdog.
2491 #
2492 # On failure, qemu will try delete the newly created internal snapshot in the
2493 # transaction. When an I/O error occurs during deletion, the user needs to fix
2494 # it later with qemu-img or other command.
2495 #
2496 # @actions: List of @TransactionAction;
2497 # information needed for the respective operations.
2498 #
2499 # @properties: #optional structure of additional options to control the
2500 # execution of the transaction. See @TransactionProperties
2501 # for additional detail.
2502 #
2503 # Returns: nothing on success
2504 #
2505 # Errors depend on the operations of the transaction
2506 #
2507 # Note: The transaction aborts on the first failure. Therefore, there will be
2508 # information on only one failed operation returned in an error condition, and
2509 # subsequent actions will not have been attempted.
2510 #
2511 # Since: 1.1
2512 #
2513 # Example:
2514 #
2515 # -> { "execute": "transaction",
2516 # "arguments": { "actions": [
2517 # { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd0",
2518 # "snapshot-file": "/some/place/my-image",
2519 # "format": "qcow2" } },
2520 # { "type": "blockdev-snapshot-sync", "data" : { "node-name": "myfile",
2521 # "snapshot-file": "/some/place/my-image2",
2522 # "snapshot-node-name": "node3432",
2523 # "mode": "existing",
2524 # "format": "qcow2" } },
2525 # { "type": "blockdev-snapshot-sync", "data" : { "device": "ide-hd1",
2526 # "snapshot-file": "/some/place/my-image2",
2527 # "mode": "existing",
2528 # "format": "qcow2" } },
2529 # { "type": "blockdev-snapshot-internal-sync", "data" : {
2530 # "device": "ide-hd2",
2531 # "name": "snapshot0" } } ] } }
2532 # <- { "return": {} }
2533 #
2534 ##
2535 { 'command': 'transaction',
2536 'data': { 'actions': [ 'TransactionAction' ],
2537 '*properties': 'TransactionProperties'
2538 }
2539 }
2540
2541 ##
2542 # @human-monitor-command:
2543 #
2544 # Execute a command on the human monitor and return the output.
2545 #
2546 # @command-line: the command to execute in the human monitor
2547 #
2548 # @cpu-index: #optional The CPU to use for commands that require an implicit CPU
2549 #
2550 # Returns: the output of the command as a string
2551 #
2552 # Since: 0.14.0
2553 #
2554 # Notes: This command only exists as a stop-gap. Its use is highly
2555 # discouraged. The semantics of this command are not
2556 # guaranteed: this means that command names, arguments and
2557 # responses can change or be removed at ANY time. Applications
2558 # that rely on long term stability guarantees should NOT
2559 # use this command.
2560 #
2561 # Known limitations:
2562 #
2563 # * This command is stateless, this means that commands that depend
2564 # on state information (such as getfd) might not work
2565 #
2566 # * Commands that prompt the user for data (eg. 'cont' when the block
2567 # device is encrypted) don't currently work
2568 #
2569 # Example:
2570 #
2571 # -> { "execute": "human-monitor-command",
2572 # "arguments": { "command-line": "info kvm" } }
2573 # <- { "return": "kvm support: enabled\r\n" }
2574 #
2575 ##
2576 { 'command': 'human-monitor-command',
2577 'data': {'command-line': 'str', '*cpu-index': 'int'},
2578 'returns': 'str' }
2579
2580 ##
2581 # @migrate_cancel:
2582 #
2583 # Cancel the current executing migration process.
2584 #
2585 # Returns: nothing on success
2586 #
2587 # Notes: This command succeeds even if there is no migration process running.
2588 #
2589 # Since: 0.14.0
2590 #
2591 # Example:
2592 #
2593 # -> { "execute": "migrate_cancel" }
2594 # <- { "return": {} }
2595 #
2596 ##
2597 { 'command': 'migrate_cancel' }
2598
2599 ##
2600 # @migrate_set_downtime:
2601 #
2602 # Set maximum tolerated downtime for migration.
2603 #
2604 # @value: maximum downtime in seconds
2605 #
2606 # Returns: nothing on success
2607 #
2608 # Notes: This command is deprecated in favor of 'migrate-set-parameters'
2609 #
2610 # Since: 0.14.0
2611 #
2612 # Example:
2613 #
2614 # -> { "execute": "migrate_set_downtime", "arguments": { "value": 0.1 } }
2615 # <- { "return": {} }
2616 #
2617 ##
2618 { 'command': 'migrate_set_downtime', 'data': {'value': 'number'} }
2619
2620 ##
2621 # @migrate_set_speed:
2622 #
2623 # Set maximum speed for migration.
2624 #
2625 # @value: maximum speed in bytes per second.
2626 #
2627 # Returns: nothing on success
2628 #
2629 # Notes: This command is deprecated in favor of 'migrate-set-parameters'
2630 #
2631 # Since: 0.14.0
2632 #
2633 # Example:
2634 #
2635 # -> { "execute": "migrate_set_speed", "arguments": { "value": 1024 } }
2636 # <- { "return": {} }
2637 #
2638 ##
2639 { 'command': 'migrate_set_speed', 'data': {'value': 'int'} }
2640
2641 ##
2642 # @migrate-set-cache-size:
2643 #
2644 # Set XBZRLE cache size
2645 #
2646 # @value: cache size in bytes
2647 #
2648 # The size will be rounded down to the nearest power of 2.
2649 # The cache size can be modified before and during ongoing migration
2650 #
2651 # Returns: nothing on success
2652 #
2653 # Since: 1.2
2654 ##
2655 { 'command': 'migrate-set-cache-size', 'data': {'value': 'int'} }
2656
2657 ##
2658 # @query-migrate-cache-size:
2659 #
2660 # Query migration XBZRLE cache size
2661 #
2662 # Returns: XBZRLE cache size in bytes
2663 #
2664 # Since: 1.2
2665 #
2666 # Example:
2667 #
2668 # -> { "execute": "query-migrate-cache-size" }
2669 # <- { "return": 67108864 }
2670 #
2671 ##
2672 { 'command': 'query-migrate-cache-size', 'returns': 'int' }
2673
2674 ##
2675 # @ObjectPropertyInfo:
2676 #
2677 # @name: the name of the property
2678 #
2679 # @type: the type of the property. This will typically come in one of four
2680 # forms:
2681 #
2682 # 1) A primitive type such as 'u8', 'u16', 'bool', 'str', or 'double'.
2683 # These types are mapped to the appropriate JSON type.
2684 #
2685 # 2) A child type in the form 'child<subtype>' where subtype is a qdev
2686 # device type name. Child properties create the composition tree.
2687 #
2688 # 3) A link type in the form 'link<subtype>' where subtype is a qdev
2689 # device type name. Link properties form the device model graph.
2690 #
2691 # Since: 1.2
2692 ##
2693 { 'struct': 'ObjectPropertyInfo',
2694 'data': { 'name': 'str', 'type': 'str' } }
2695
2696 ##
2697 # @qom-list:
2698 #
2699 # This command will list any properties of a object given a path in the object
2700 # model.
2701 #
2702 # @path: the path within the object model. See @qom-get for a description of
2703 # this parameter.
2704 #
2705 # Returns: a list of @ObjectPropertyInfo that describe the properties of the
2706 # object.
2707 #
2708 # Since: 1.2
2709 ##
2710 { 'command': 'qom-list',
2711 'data': { 'path': 'str' },
2712 'returns': [ 'ObjectPropertyInfo' ] }
2713
2714 ##
2715 # @qom-get:
2716 #
2717 # This command will get a property from a object model path and return the
2718 # value.
2719 #
2720 # @path: The path within the object model. There are two forms of supported
2721 # paths--absolute and partial paths.
2722 #
2723 # Absolute paths are derived from the root object and can follow child<>
2724 # or link<> properties. Since they can follow link<> properties, they
2725 # can be arbitrarily long. Absolute paths look like absolute filenames
2726 # and are prefixed with a leading slash.
2727 #
2728 # Partial paths look like relative filenames. They do not begin
2729 # with a prefix. The matching rules for partial paths are subtle but
2730 # designed to make specifying objects easy. At each level of the
2731 # composition tree, the partial path is matched as an absolute path.
2732 # The first match is not returned. At least two matches are searched
2733 # for. A successful result is only returned if only one match is
2734 # found. If more than one match is found, a flag is return to
2735 # indicate that the match was ambiguous.
2736 #
2737 # @property: The property name to read
2738 #
2739 # Returns: The property value. The type depends on the property
2740 # type. child<> and link<> properties are returned as #str
2741 # pathnames. All integer property types (u8, u16, etc) are
2742 # returned as #int.
2743 #
2744 # Since: 1.2
2745 ##
2746 { 'command': 'qom-get',
2747 'data': { 'path': 'str', 'property': 'str' },
2748 'returns': 'any' }
2749
2750 ##
2751 # @qom-set:
2752 #
2753 # This command will set a property from a object model path.
2754 #
2755 # @path: see @qom-get for a description of this parameter
2756 #
2757 # @property: the property name to set
2758 #
2759 # @value: a value who's type is appropriate for the property type. See @qom-get
2760 # for a description of type mapping.
2761 #
2762 # Since: 1.2
2763 ##
2764 { 'command': 'qom-set',
2765 'data': { 'path': 'str', 'property': 'str', 'value': 'any' } }
2766
2767 ##
2768 # @set_password:
2769 #
2770 # Sets the password of a remote display session.
2771 #
2772 # @protocol: `vnc' to modify the VNC server password
2773 # `spice' to modify the Spice server password
2774 #
2775 # @password: the new password
2776 #
2777 # @connected: #optional how to handle existing clients when changing the
2778 # password. If nothing is specified, defaults to `keep'
2779 # `fail' to fail the command if clients are connected
2780 # `disconnect' to disconnect existing clients
2781 # `keep' to maintain existing clients
2782 #
2783 # Returns: Nothing on success
2784 # If Spice is not enabled, DeviceNotFound
2785 #
2786 # Since: 0.14.0
2787 #
2788 # Example:
2789 #
2790 # -> { "execute": "set_password", "arguments": { "protocol": "vnc",
2791 # "password": "secret" } }
2792 # <- { "return": {} }
2793 #
2794 ##
2795 { 'command': 'set_password',
2796 'data': {'protocol': 'str', 'password': 'str', '*connected': 'str'} }
2797
2798 ##
2799 # @expire_password:
2800 #
2801 # Expire the password of a remote display server.
2802 #
2803 # @protocol: the name of the remote display protocol `vnc' or `spice'
2804 #
2805 # @time: when to expire the password.
2806 # `now' to expire the password immediately
2807 # `never' to cancel password expiration
2808 # `+INT' where INT is the number of seconds from now (integer)
2809 # `INT' where INT is the absolute time in seconds
2810 #
2811 # Returns: Nothing on success
2812 # If @protocol is `spice' and Spice is not active, DeviceNotFound
2813 #
2814 # Since: 0.14.0
2815 #
2816 # Notes: Time is relative to the server and currently there is no way to
2817 # coordinate server time with client time. It is not recommended to
2818 # use the absolute time version of the @time parameter unless you're
2819 # sure you are on the same machine as the QEMU instance.
2820 #
2821 # Example:
2822 #
2823 # -> { "execute": "expire_password", "arguments": { "protocol": "vnc",
2824 # "time": "+60" } }
2825 # <- { "return": {} }
2826 #
2827 ##
2828 { 'command': 'expire_password', 'data': {'protocol': 'str', 'time': 'str'} }
2829
2830 ##
2831 # @change-vnc-password:
2832 #
2833 # Change the VNC server password.
2834 #
2835 # @password: the new password to use with VNC authentication
2836 #
2837 # Since: 1.1
2838 #
2839 # Notes: An empty password in this command will set the password to the empty
2840 # string. Existing clients are unaffected by executing this command.
2841 ##
2842 { 'command': 'change-vnc-password', 'data': {'password': 'str'} }
2843
2844 ##
2845 # @change:
2846 #
2847 # This command is multiple commands multiplexed together.
2848 #
2849 # @device: This is normally the name of a block device but it may also be 'vnc'.
2850 # when it's 'vnc', then sub command depends on @target
2851 #
2852 # @target: If @device is a block device, then this is the new filename.
2853 # If @device is 'vnc', then if the value 'password' selects the vnc
2854 # change password command. Otherwise, this specifies a new server URI
2855 # address to listen to for VNC connections.
2856 #
2857 # @arg: If @device is a block device, then this is an optional format to open
2858 # the device with.
2859 # If @device is 'vnc' and @target is 'password', this is the new VNC
2860 # password to set. If this argument is an empty string, then no future
2861 # logins will be allowed.
2862 #
2863 # Returns: Nothing on success.
2864 # If @device is not a valid block device, DeviceNotFound
2865 # If the new block device is encrypted, DeviceEncrypted. Note that
2866 # if this error is returned, the device has been opened successfully
2867 # and an additional call to @block_passwd is required to set the
2868 # device's password. The behavior of reads and writes to the block
2869 # device between when these calls are executed is undefined.
2870 #
2871 # Notes: This interface is deprecated, and it is strongly recommended that you
2872 # avoid using it. For changing block devices, use
2873 # blockdev-change-medium; for changing VNC parameters, use
2874 # change-vnc-password.
2875 #
2876 # Since: 0.14.0
2877 #
2878 # Example:
2879 #
2880 # 1. Change a removable medium
2881 #
2882 # -> { "execute": "change",
2883 # "arguments": { "device": "ide1-cd0",
2884 # "target": "/srv/images/Fedora-12-x86_64-DVD.iso" } }
2885 # <- { "return": {} }
2886 #
2887 # 2. Change VNC password
2888 #
2889 # -> { "execute": "change",
2890 # "arguments": { "device": "vnc", "target": "password",
2891 # "arg": "foobar1" } }
2892 # <- { "return": {} }
2893 #
2894 ##
2895 { 'command': 'change',
2896 'data': {'device': 'str', 'target': 'str', '*arg': 'str'} }
2897
2898 ##
2899 # @ObjectTypeInfo:
2900 #
2901 # This structure describes a search result from @qom-list-types
2902 #
2903 # @name: the type name found in the search
2904 #
2905 # Since: 1.1
2906 #
2907 # Notes: This command is experimental and may change syntax in future releases.
2908 ##
2909 { 'struct': 'ObjectTypeInfo',
2910 'data': { 'name': 'str' } }
2911
2912 ##
2913 # @qom-list-types:
2914 #
2915 # This command will return a list of types given search parameters
2916 #
2917 # @implements: if specified, only return types that implement this type name
2918 #
2919 # @abstract: if true, include abstract types in the results
2920 #
2921 # Returns: a list of @ObjectTypeInfo or an empty list if no results are found
2922 #
2923 # Since: 1.1
2924 ##
2925 { 'command': 'qom-list-types',
2926 'data': { '*implements': 'str', '*abstract': 'bool' },
2927 'returns': [ 'ObjectTypeInfo' ] }
2928
2929 ##
2930 # @DevicePropertyInfo:
2931 #
2932 # Information about device properties.
2933 #
2934 # @name: the name of the property
2935 # @type: the typename of the property
2936 # @description: #optional if specified, the description of the property.
2937 # (since 2.2)
2938 #
2939 # Since: 1.2
2940 ##
2941 { 'struct': 'DevicePropertyInfo',
2942 'data': { 'name': 'str', 'type': 'str', '*description': 'str' } }
2943
2944 ##
2945 # @device-list-properties:
2946 #
2947 # List properties associated with a device.
2948 #
2949 # @typename: the type name of a device
2950 #
2951 # Returns: a list of DevicePropertyInfo describing a devices properties
2952 #
2953 # Since: 1.2
2954 ##
2955 { 'command': 'device-list-properties',
2956 'data': { 'typename': 'str'},
2957 'returns': [ 'DevicePropertyInfo' ] }
2958
2959 ##
2960 # @migrate:
2961 #
2962 # Migrates the current running guest to another Virtual Machine.
2963 #
2964 # @uri: the Uniform Resource Identifier of the destination VM
2965 #
2966 # @blk: #optional do block migration (full disk copy)
2967 #
2968 # @inc: #optional incremental disk copy migration
2969 #
2970 # @detach: this argument exists only for compatibility reasons and
2971 # is ignored by QEMU
2972 #
2973 # Returns: nothing on success
2974 #
2975 # Since: 0.14.0
2976 #
2977 # Notes:
2978 #
2979 # 1. The 'query-migrate' command should be used to check migration's progress
2980 # and final result (this information is provided by the 'status' member)
2981 #
2982 # 2. All boolean arguments default to false
2983 #
2984 # 3. The user Monitor's "detach" argument is invalid in QMP and should not
2985 # be used
2986 #
2987 # Example:
2988 #
2989 # -> { "execute": "migrate", "arguments": { "uri": "tcp:0:4446" } }
2990 # <- { "return": {} }
2991 #
2992 ##
2993 { 'command': 'migrate',
2994 'data': {'uri': 'str', '*blk': 'bool', '*inc': 'bool', '*detach': 'bool' } }
2995
2996 ##
2997 # @migrate-incoming:
2998 #
2999 # Start an incoming migration, the qemu must have been started
3000 # with -incoming defer
3001 #
3002 # @uri: The Uniform Resource Identifier identifying the source or
3003 # address to listen on
3004 #
3005 # Returns: nothing on success
3006 #
3007 # Since: 2.3
3008 #
3009 # Notes:
3010 #
3011 # 1. It's a bad idea to use a string for the uri, but it needs to stay
3012 # compatible with -incoming and the format of the uri is already exposed
3013 # above libvirt.
3014 #
3015 # 2. QEMU must be started with -incoming defer to allow migrate-incoming to
3016 # be used.
3017 #
3018 # 3. The uri format is the same as for -incoming
3019 #
3020 # Example:
3021 #
3022 # -> { "execute": "migrate-incoming",
3023 # "arguments": { "uri": "tcp::4446" } }
3024 # <- { "return": {} }
3025 #
3026 ##
3027 { 'command': 'migrate-incoming', 'data': {'uri': 'str' } }
3028
3029 ##
3030 # @xen-save-devices-state:
3031 #
3032 # Save the state of all devices to file. The RAM and the block devices
3033 # of the VM are not saved by this command.
3034 #
3035 # @filename: the file to save the state of the devices to as binary
3036 # data. See xen-save-devices-state.txt for a description of the binary
3037 # format.
3038 #
3039 # Returns: Nothing on success
3040 #
3041 # Since: 1.1
3042 ##
3043 { 'command': 'xen-save-devices-state', 'data': {'filename': 'str'} }
3044
3045 ##
3046 # @xen-set-global-dirty-log:
3047 #
3048 # Enable or disable the global dirty log mode.
3049 #
3050 # @enable: true to enable, false to disable.
3051 #
3052 # Returns: nothing
3053 #
3054 # Since: 1.3
3055 ##
3056 { 'command': 'xen-set-global-dirty-log', 'data': { 'enable': 'bool' } }
3057
3058 ##
3059 # @device_add:
3060 #
3061 # @driver: the name of the new device's driver
3062 #
3063 # @bus: #optional the device's parent bus (device tree path)
3064 #
3065 # @id: #optional the device's ID, must be unique
3066 #
3067 # Additional arguments depend on the type.
3068 #
3069 # Add a device.
3070 #
3071 # Notes:
3072 # 1. For detailed information about this command, please refer to the
3073 # 'docs/qdev-device-use.txt' file.
3074 #
3075 # 2. It's possible to list device properties by running QEMU with the
3076 # "-device DEVICE,help" command-line argument, where DEVICE is the
3077 # device's name
3078 #
3079 # Example:
3080 #
3081 # -> { "execute": "device_add",
3082 # "arguments": { "driver": "e1000", "id": "net1",
3083 # "bus": "pci.0",
3084 # "mac": "52:54:00:12:34:56" } }
3085 # <- { "return": {} }
3086 #
3087 # TODO: This command effectively bypasses QAPI completely due to its
3088 # "additional arguments" business. It shouldn't have been added to
3089 # the schema in this form. It should be qapified properly, or
3090 # replaced by a properly qapified command.
3091 #
3092 # Since: 0.13
3093 ##
3094 { 'command': 'device_add',
3095 'data': {'driver': 'str', '*bus': 'str', '*id': 'str'},
3096 'gen': false } # so we can get the additional arguments
3097
3098 ##
3099 # @device_del:
3100 #
3101 # Remove a device from a guest
3102 #
3103 # @id: the name or QOM path of the device
3104 #
3105 # Returns: Nothing on success
3106 # If @id is not a valid device, DeviceNotFound
3107 #
3108 # Notes: When this command completes, the device may not be removed from the
3109 # guest. Hot removal is an operation that requires guest cooperation.
3110 # This command merely requests that the guest begin the hot removal
3111 # process. Completion of the device removal process is signaled with a
3112 # DEVICE_DELETED event. Guest reset will automatically complete removal
3113 # for all devices.
3114 #
3115 # Since: 0.14.0
3116 ##
3117 { 'command': 'device_del', 'data': {'id': 'str'} }
3118
3119 ##
3120 # @DumpGuestMemoryFormat:
3121 #
3122 # An enumeration of guest-memory-dump's format.
3123 #
3124 # @elf: elf format
3125 #
3126 # @kdump-zlib: kdump-compressed format with zlib-compressed
3127 #
3128 # @kdump-lzo: kdump-compressed format with lzo-compressed
3129 #
3130 # @kdump-snappy: kdump-compressed format with snappy-compressed
3131 #
3132 # Since: 2.0
3133 ##
3134 { 'enum': 'DumpGuestMemoryFormat',
3135 'data': [ 'elf', 'kdump-zlib', 'kdump-lzo', 'kdump-snappy' ] }
3136
3137 ##
3138 # @dump-guest-memory:
3139 #
3140 # Dump guest's memory to vmcore. It is a synchronous operation that can take
3141 # very long depending on the amount of guest memory.
3142 #
3143 # @paging: if true, do paging to get guest's memory mapping. This allows
3144 # using gdb to process the core file.
3145 #
3146 # IMPORTANT: this option can make QEMU allocate several gigabytes
3147 # of RAM. This can happen for a large guest, or a
3148 # malicious guest pretending to be large.
3149 #
3150 # Also, paging=true has the following limitations:
3151 #
3152 # 1. The guest may be in a catastrophic state or can have corrupted
3153 # memory, which cannot be trusted
3154 # 2. The guest can be in real-mode even if paging is enabled. For
3155 # example, the guest uses ACPI to sleep, and ACPI sleep state
3156 # goes in real-mode
3157 # 3. Currently only supported on i386 and x86_64.
3158 #
3159 # @protocol: the filename or file descriptor of the vmcore. The supported
3160 # protocols are:
3161 #
3162 # 1. file: the protocol starts with "file:", and the following
3163 # string is the file's path.
3164 # 2. fd: the protocol starts with "fd:", and the following string
3165 # is the fd's name.
3166 #
3167 # @detach: #optional if true, QMP will return immediately rather than
3168 # waiting for the dump to finish. The user can track progress
3169 # using "query-dump". (since 2.6).
3170 #
3171 # @begin: #optional if specified, the starting physical address.
3172 #
3173 # @length: #optional if specified, the memory size, in bytes. If you don't
3174 # want to dump all guest's memory, please specify the start @begin
3175 # and @length
3176 #
3177 # @format: #optional if specified, the format of guest memory dump. But non-elf
3178 # format is conflict with paging and filter, ie. @paging, @begin and
3179 # @length is not allowed to be specified with non-elf @format at the
3180 # same time (since 2.0)
3181 #
3182 # Returns: nothing on success
3183 #
3184 # Since: 1.2
3185 ##
3186 { 'command': 'dump-guest-memory',
3187 'data': { 'paging': 'bool', 'protocol': 'str', '*detach': 'bool',
3188 '*begin': 'int', '*length': 'int',
3189 '*format': 'DumpGuestMemoryFormat'} }
3190
3191 ##
3192 # @DumpStatus:
3193 #
3194 # Describe the status of a long-running background guest memory dump.
3195 #
3196 # @none: no dump-guest-memory has started yet.
3197 #
3198 # @active: there is one dump running in background.
3199 #
3200 # @completed: the last dump has finished successfully.
3201 #
3202 # @failed: the last dump has failed.
3203 #
3204 # Since: 2.6
3205 ##
3206 { 'enum': 'DumpStatus',
3207 'data': [ 'none', 'active', 'completed', 'failed' ] }
3208
3209 ##
3210 # @DumpQueryResult:
3211 #
3212 # The result format for 'query-dump'.
3213 #
3214 # @status: enum of @DumpStatus, which shows current dump status
3215 #
3216 # @completed: bytes written in latest dump (uncompressed)
3217 #
3218 # @total: total bytes to be written in latest dump (uncompressed)
3219 #
3220 # Since: 2.6
3221 ##
3222 { 'struct': 'DumpQueryResult',
3223 'data': { 'status': 'DumpStatus',
3224 'completed': 'int',
3225 'total': 'int' } }
3226
3227 ##
3228 # @query-dump:
3229 #
3230 # Query latest dump status.
3231 #
3232 # Returns: A @DumpStatus object showing the dump status.
3233 #
3234 # Since: 2.6
3235 ##
3236 { 'command': 'query-dump', 'returns': 'DumpQueryResult' }
3237
3238 ##
3239 # @DumpGuestMemoryCapability:
3240 #
3241 # A list of the available formats for dump-guest-memory
3242 #
3243 # Since: 2.0
3244 ##
3245 { 'struct': 'DumpGuestMemoryCapability',
3246 'data': {
3247 'formats': ['DumpGuestMemoryFormat'] } }
3248
3249 ##
3250 # @query-dump-guest-memory-capability:
3251 #
3252 # Returns the available formats for dump-guest-memory
3253 #
3254 # Returns: A @DumpGuestMemoryCapability object listing available formats for
3255 # dump-guest-memory
3256 #
3257 # Since: 2.0
3258 ##
3259 { 'command': 'query-dump-guest-memory-capability',
3260 'returns': 'DumpGuestMemoryCapability' }
3261
3262 ##
3263 # @dump-skeys:
3264 #
3265 # Dump guest's storage keys
3266 #
3267 # @filename: the path to the file to dump to
3268 #
3269 # This command is only supported on s390 architecture.
3270 #
3271 # Since: 2.5
3272 ##
3273 { 'command': 'dump-skeys',
3274 'data': { 'filename': 'str' } }
3275
3276 ##
3277 # @netdev_add:
3278 #
3279 # Add a network backend.
3280 #
3281 # @type: the type of network backend. Current valid values are 'user', 'tap',
3282 # 'vde', 'socket', 'dump' and 'bridge'
3283 #
3284 # @id: the name of the new network backend
3285 #
3286 # Additional arguments depend on the type.
3287 #
3288 # TODO: This command effectively bypasses QAPI completely due to its
3289 # "additional arguments" business. It shouldn't have been added to
3290 # the schema in this form. It should be qapified properly, or
3291 # replaced by a properly qapified command.
3292 #
3293 # Since: 0.14.0
3294 #
3295 # Returns: Nothing on success
3296 # If @type is not a valid network backend, DeviceNotFound
3297 ##
3298 { 'command': 'netdev_add',
3299 'data': {'type': 'str', 'id': 'str'},
3300 'gen': false } # so we can get the additional arguments
3301
3302 ##
3303 # @netdev_del:
3304 #
3305 # Remove a network backend.
3306 #
3307 # @id: the name of the network backend to remove
3308 #
3309 # Returns: Nothing on success
3310 # If @id is not a valid network backend, DeviceNotFound
3311 #
3312 # Since: 0.14.0
3313 ##
3314 { 'command': 'netdev_del', 'data': {'id': 'str'} }
3315
3316 ##
3317 # @object-add:
3318 #
3319 # Create a QOM object.
3320 #
3321 # @qom-type: the class name for the object to be created
3322 #
3323 # @id: the name of the new object
3324 #
3325 # @props: #optional a dictionary of properties to be passed to the backend
3326 #
3327 # Returns: Nothing on success
3328 # Error if @qom-type is not a valid class name
3329 #
3330 # Since: 2.0
3331 ##
3332 { 'command': 'object-add',
3333 'data': {'qom-type': 'str', 'id': 'str', '*props': 'any'} }
3334
3335 ##
3336 # @object-del:
3337 #
3338 # Remove a QOM object.
3339 #
3340 # @id: the name of the QOM object to remove
3341 #
3342 # Returns: Nothing on success
3343 # Error if @id is not a valid id for a QOM object
3344 #
3345 # Since: 2.0
3346 ##
3347 { 'command': 'object-del', 'data': {'id': 'str'} }
3348
3349 ##
3350 # @NetdevNoneOptions:
3351 #
3352 # Use it alone to have zero network devices.
3353 #
3354 # Since: 1.2
3355 ##
3356 { 'struct': 'NetdevNoneOptions',
3357 'data': { } }
3358
3359 ##
3360 # @NetLegacyNicOptions:
3361 #
3362 # Create a new Network Interface Card.
3363 #
3364 # @netdev: #optional id of -netdev to connect to
3365 #
3366 # @macaddr: #optional MAC address
3367 #
3368 # @model: #optional device model (e1000, rtl8139, virtio etc.)
3369 #
3370 # @addr: #optional PCI device address
3371 #
3372 # @vectors: #optional number of MSI-x vectors, 0 to disable MSI-X
3373 #
3374 # Since: 1.2
3375 ##
3376 { 'struct': 'NetLegacyNicOptions',
3377 'data': {
3378 '*netdev': 'str',
3379 '*macaddr': 'str',
3380 '*model': 'str',
3381 '*addr': 'str',
3382 '*vectors': 'uint32' } }
3383
3384 ##
3385 # @String:
3386 #
3387 # A fat type wrapping 'str', to be embedded in lists.
3388 #
3389 # Since: 1.2
3390 ##
3391 { 'struct': 'String',
3392 'data': {
3393 'str': 'str' } }
3394
3395 ##
3396 # @NetdevUserOptions:
3397 #
3398 # Use the user mode network stack which requires no administrator privilege to
3399 # run.
3400 #
3401 # @hostname: #optional client hostname reported by the builtin DHCP server
3402 #
3403 # @restrict: #optional isolate the guest from the host
3404 #
3405 # @ipv4: #optional whether to support IPv4, default true for enabled
3406 # (since 2.6)
3407 #
3408 # @ipv6: #optional whether to support IPv6, default true for enabled
3409 # (since 2.6)
3410 #
3411 # @ip: #optional legacy parameter, use net= instead
3412 #
3413 # @net: #optional IP network address that the guest will see, in the
3414 # form addr[/netmask] The netmask is optional, and can be
3415 # either in the form a.b.c.d or as a number of valid top-most
3416 # bits. Default is 10.0.2.0/24.
3417 #
3418 # @host: #optional guest-visible address of the host
3419 #
3420 # @tftp: #optional root directory of the built-in TFTP server
3421 #
3422 # @bootfile: #optional BOOTP filename, for use with tftp=
3423 #
3424 # @dhcpstart: #optional the first of the 16 IPs the built-in DHCP server can
3425 # assign
3426 #
3427 # @dns: #optional guest-visible address of the virtual nameserver
3428 #
3429 # @dnssearch: #optional list of DNS suffixes to search, passed as DHCP option
3430 # to the guest
3431 #
3432 # @ipv6-prefix: #optional IPv6 network prefix (default is fec0::) (since
3433 # 2.6). The network prefix is given in the usual
3434 # hexadecimal IPv6 address notation.
3435 #
3436 # @ipv6-prefixlen: #optional IPv6 network prefix length (default is 64)
3437 # (since 2.6)
3438 #
3439 # @ipv6-host: #optional guest-visible IPv6 address of the host (since 2.6)
3440 #
3441 # @ipv6-dns: #optional guest-visible IPv6 address of the virtual
3442 # nameserver (since 2.6)
3443 #
3444 # @smb: #optional root directory of the built-in SMB server
3445 #
3446 # @smbserver: #optional IP address of the built-in SMB server
3447 #
3448 # @hostfwd: #optional redirect incoming TCP or UDP host connections to guest
3449 # endpoints
3450 #
3451 # @guestfwd: #optional forward guest TCP connections
3452 #
3453 # Since: 1.2
3454 ##
3455 { 'struct': 'NetdevUserOptions',
3456 'data': {
3457 '*hostname': 'str',
3458 '*restrict': 'bool',
3459 '*ipv4': 'bool',
3460 '*ipv6': 'bool',
3461 '*ip': 'str',
3462 '*net': 'str',
3463 '*host': 'str',
3464 '*tftp': 'str',
3465 '*bootfile': 'str',
3466 '*dhcpstart': 'str',
3467 '*dns': 'str',
3468 '*dnssearch': ['String'],
3469 '*ipv6-prefix': 'str',
3470 '*ipv6-prefixlen': 'int',
3471 '*ipv6-host': 'str',
3472 '*ipv6-dns': 'str',
3473 '*smb': 'str',
3474 '*smbserver': 'str',
3475 '*hostfwd': ['String'],
3476 '*guestfwd': ['String'] } }
3477
3478 ##
3479 # @NetdevTapOptions:
3480 #
3481 # Connect the host TAP network interface name to the VLAN.
3482 #
3483 # @ifname: #optional interface name
3484 #
3485 # @fd: #optional file descriptor of an already opened tap
3486 #
3487 # @fds: #optional multiple file descriptors of already opened multiqueue capable
3488 # tap
3489 #
3490 # @script: #optional script to initialize the interface
3491 #
3492 # @downscript: #optional script to shut down the interface
3493 #
3494 # @br: #optional bridge name (since 2.8)
3495 #
3496 # @helper: #optional command to execute to configure bridge
3497 #
3498 # @sndbuf: #optional send buffer limit. Understands [TGMKkb] suffixes.
3499 #
3500 # @vnet_hdr: #optional enable the IFF_VNET_HDR flag on the tap interface
3501 #
3502 # @vhost: #optional enable vhost-net network accelerator
3503 #
3504 # @vhostfd: #optional file descriptor of an already opened vhost net device
3505 #
3506 # @vhostfds: #optional file descriptors of multiple already opened vhost net
3507 # devices
3508 #
3509 # @vhostforce: #optional vhost on for non-MSIX virtio guests
3510 #
3511 # @queues: #optional number of queues to be created for multiqueue capable tap
3512 #
3513 # @poll-us: #optional maximum number of microseconds that could
3514 # be spent on busy polling for tap (since 2.7)
3515 #
3516 # Since: 1.2
3517 ##
3518 { 'struct': 'NetdevTapOptions',
3519 'data': {
3520 '*ifname': 'str',
3521 '*fd': 'str',
3522 '*fds': 'str',
3523 '*script': 'str',
3524 '*downscript': 'str',
3525 '*br': 'str',
3526 '*helper': 'str',
3527 '*sndbuf': 'size',
3528 '*vnet_hdr': 'bool',
3529 '*vhost': 'bool',
3530 '*vhostfd': 'str',
3531 '*vhostfds': 'str',
3532 '*vhostforce': 'bool',
3533 '*queues': 'uint32',
3534 '*poll-us': 'uint32'} }
3535
3536 ##
3537 # @NetdevSocketOptions:
3538 #
3539 # Connect the VLAN to a remote VLAN in another QEMU virtual machine using a TCP
3540 # socket connection.
3541 #
3542 # @fd: #optional file descriptor of an already opened socket
3543 #
3544 # @listen: #optional port number, and optional hostname, to listen on
3545 #
3546 # @connect: #optional port number, and optional hostname, to connect to
3547 #
3548 # @mcast: #optional UDP multicast address and port number
3549 #
3550 # @localaddr: #optional source address and port for multicast and udp packets
3551 #
3552 # @udp: #optional UDP unicast address and port number
3553 #
3554 # Since: 1.2
3555 ##
3556 { 'struct': 'NetdevSocketOptions',
3557 'data': {
3558 '*fd': 'str',
3559 '*listen': 'str',
3560 '*connect': 'str',
3561 '*mcast': 'str',
3562 '*localaddr': 'str',
3563 '*udp': 'str' } }
3564
3565 ##
3566 # @NetdevL2TPv3Options:
3567 #
3568 # Connect the VLAN to Ethernet over L2TPv3 Static tunnel
3569 #
3570 # @src: source address
3571 #
3572 # @dst: destination address
3573 #
3574 # @srcport: #optional source port - mandatory for udp, optional for ip
3575 #
3576 # @dstport: #optional destination port - mandatory for udp, optional for ip
3577 #
3578 # @ipv6: #optional - force the use of ipv6
3579 #
3580 # @udp: #optional - use the udp version of l2tpv3 encapsulation
3581 #
3582 # @cookie64: #optional - use 64 bit coookies
3583 #
3584 # @counter: #optional have sequence counter
3585 #
3586 # @pincounter: #optional pin sequence counter to zero -
3587 # workaround for buggy implementations or
3588 # networks with packet reorder
3589 #
3590 # @txcookie: #optional 32 or 64 bit transmit cookie
3591 #
3592 # @rxcookie: #optional 32 or 64 bit receive cookie
3593 #
3594 # @txsession: 32 bit transmit session
3595 #
3596 # @rxsession: #optional 32 bit receive session - if not specified
3597 # set to the same value as transmit
3598 #
3599 # @offset: #optional additional offset - allows the insertion of
3600 # additional application-specific data before the packet payload
3601 #
3602 # Since: 2.1
3603 ##
3604 { 'struct': 'NetdevL2TPv3Options',
3605 'data': {
3606 'src': 'str',
3607 'dst': 'str',
3608 '*srcport': 'str',
3609 '*dstport': 'str',
3610 '*ipv6': 'bool',
3611 '*udp': 'bool',
3612 '*cookie64': 'bool',
3613 '*counter': 'bool',
3614 '*pincounter': 'bool',
3615 '*txcookie': 'uint64',
3616 '*rxcookie': 'uint64',
3617 'txsession': 'uint32',
3618 '*rxsession': 'uint32',
3619 '*offset': 'uint32' } }
3620
3621 ##
3622 # @NetdevVdeOptions:
3623 #
3624 # Connect the VLAN to a vde switch running on the host.
3625 #
3626 # @sock: #optional socket path
3627 #
3628 # @port: #optional port number
3629 #
3630 # @group: #optional group owner of socket
3631 #
3632 # @mode: #optional permissions for socket
3633 #
3634 # Since: 1.2
3635 ##
3636 { 'struct': 'NetdevVdeOptions',
3637 'data': {
3638 '*sock': 'str',
3639 '*port': 'uint16',
3640 '*group': 'str',
3641 '*mode': 'uint16' } }
3642
3643 ##
3644 # @NetdevDumpOptions:
3645 #
3646 # Dump VLAN network traffic to a file.
3647 #
3648 # @len: #optional per-packet size limit (64k default). Understands [TGMKkb]
3649 # suffixes.
3650 #
3651 # @file: #optional dump file path (default is qemu-vlan0.pcap)
3652 #
3653 # Since: 1.2
3654 ##
3655 { 'struct': 'NetdevDumpOptions',
3656 'data': {
3657 '*len': 'size',
3658 '*file': 'str' } }
3659
3660 ##
3661 # @NetdevBridgeOptions:
3662 #
3663 # Connect a host TAP network interface to a host bridge device.
3664 #
3665 # @br: #optional bridge name
3666 #
3667 # @helper: #optional command to execute to configure bridge
3668 #
3669 # Since: 1.2
3670 ##
3671 { 'struct': 'NetdevBridgeOptions',
3672 'data': {
3673 '*br': 'str',
3674 '*helper': 'str' } }
3675
3676 ##
3677 # @NetdevHubPortOptions:
3678 #
3679 # Connect two or more net clients through a software hub.
3680 #
3681 # @hubid: hub identifier number
3682 #
3683 # Since: 1.2
3684 ##
3685 { 'struct': 'NetdevHubPortOptions',
3686 'data': {
3687 'hubid': 'int32' } }
3688
3689 ##
3690 # @NetdevNetmapOptions:
3691 #
3692 # Connect a client to a netmap-enabled NIC or to a VALE switch port
3693 #
3694 # @ifname: Either the name of an existing network interface supported by
3695 # netmap, or the name of a VALE port (created on the fly).
3696 # A VALE port name is in the form 'valeXXX:YYY', where XXX and
3697 # YYY are non-negative integers. XXX identifies a switch and
3698 # YYY identifies a port of the switch. VALE ports having the
3699 # same XXX are therefore connected to the same switch.
3700 #
3701 # @devname: #optional path of the netmap device (default: '/dev/netmap').
3702 #
3703 # Since: 2.0
3704 ##
3705 { 'struct': 'NetdevNetmapOptions',
3706 'data': {
3707 'ifname': 'str',
3708 '*devname': 'str' } }
3709
3710 ##
3711 # @NetdevVhostUserOptions:
3712 #
3713 # Vhost-user network backend
3714 #
3715 # @chardev: name of a unix socket chardev
3716 #
3717 # @vhostforce: #optional vhost on for non-MSIX virtio guests (default: false).
3718 #
3719 # @queues: #optional number of queues to be created for multiqueue vhost-user
3720 # (default: 1) (Since 2.5)
3721 #
3722 # Since: 2.1
3723 ##
3724 { 'struct': 'NetdevVhostUserOptions',
3725 'data': {
3726 'chardev': 'str',
3727 '*vhostforce': 'bool',
3728 '*queues': 'int' } }
3729
3730 ##
3731 # @NetClientDriver:
3732 #
3733 # Available netdev drivers.
3734 #
3735 # Since: 2.7
3736 ##
3737 { 'enum': 'NetClientDriver',
3738 'data': [ 'none', 'nic', 'user', 'tap', 'l2tpv3', 'socket', 'vde', 'dump',
3739 'bridge', 'hubport', 'netmap', 'vhost-user' ] }
3740
3741 ##
3742 # @Netdev:
3743 #
3744 # Captures the configuration of a network device.
3745 #
3746 # @id: identifier for monitor commands.
3747 #
3748 # @type: Specify the driver used for interpreting remaining arguments.
3749 #
3750 # Since: 1.2
3751 #
3752 # 'l2tpv3' - since 2.1
3753 ##
3754 { 'union': 'Netdev',
3755 'base': { 'id': 'str', 'type': 'NetClientDriver' },
3756 'discriminator': 'type',
3757 'data': {
3758 'none': 'NetdevNoneOptions',
3759 'nic': 'NetLegacyNicOptions',
3760 'user': 'NetdevUserOptions',
3761 'tap': 'NetdevTapOptions',
3762 'l2tpv3': 'NetdevL2TPv3Options',
3763 'socket': 'NetdevSocketOptions',
3764 'vde': 'NetdevVdeOptions',
3765 'dump': 'NetdevDumpOptions',
3766 'bridge': 'NetdevBridgeOptions',
3767 'hubport': 'NetdevHubPortOptions',
3768 'netmap': 'NetdevNetmapOptions',
3769 'vhost-user': 'NetdevVhostUserOptions' } }
3770
3771 ##
3772 # @NetLegacy:
3773 #
3774 # Captures the configuration of a network device; legacy.
3775 #
3776 # @vlan: #optional vlan number
3777 #
3778 # @id: #optional identifier for monitor commands
3779 #
3780 # @name: #optional identifier for monitor commands, ignored if @id is present
3781 #
3782 # @opts: device type specific properties (legacy)
3783 #
3784 # Since: 1.2
3785 ##
3786 { 'struct': 'NetLegacy',
3787 'data': {
3788 '*vlan': 'int32',
3789 '*id': 'str',
3790 '*name': 'str',
3791 'opts': 'NetLegacyOptions' } }
3792
3793 ##
3794 # @NetLegacyOptions:
3795 #
3796 # Like Netdev, but for use only by the legacy command line options
3797 #
3798 # Since: 1.2
3799 ##
3800 { 'union': 'NetLegacyOptions',
3801 'data': {
3802 'none': 'NetdevNoneOptions',
3803 'nic': 'NetLegacyNicOptions',
3804 'user': 'NetdevUserOptions',
3805 'tap': 'NetdevTapOptions',
3806 'l2tpv3': 'NetdevL2TPv3Options',
3807 'socket': 'NetdevSocketOptions',
3808 'vde': 'NetdevVdeOptions',
3809 'dump': 'NetdevDumpOptions',
3810 'bridge': 'NetdevBridgeOptions',
3811 'netmap': 'NetdevNetmapOptions',
3812 'vhost-user': 'NetdevVhostUserOptions' } }
3813
3814 ##
3815 # @NetFilterDirection:
3816 #
3817 # Indicates whether a netfilter is attached to a netdev's transmit queue or
3818 # receive queue or both.
3819 #
3820 # @all: the filter is attached both to the receive and the transmit
3821 # queue of the netdev (default).
3822 #
3823 # @rx: the filter is attached to the receive queue of the netdev,
3824 # where it will receive packets sent to the netdev.
3825 #
3826 # @tx: the filter is attached to the transmit queue of the netdev,
3827 # where it will receive packets sent by the netdev.
3828 #
3829 # Since: 2.5
3830 ##
3831 { 'enum': 'NetFilterDirection',
3832 'data': [ 'all', 'rx', 'tx' ] }
3833
3834 ##
3835 # @InetSocketAddress:
3836 #
3837 # Captures a socket address or address range in the Internet namespace.
3838 #
3839 # @host: host part of the address
3840 #
3841 # @port: port part of the address, or lowest port if @to is present
3842 #
3843 # @to: highest port to try
3844 #
3845 # @ipv4: whether to accept IPv4 addresses, default try both IPv4 and IPv6
3846 # #optional
3847 #
3848 # @ipv6: whether to accept IPv6 addresses, default try both IPv4 and IPv6
3849 # #optional
3850 #
3851 # Since: 1.3
3852 ##
3853 { 'struct': 'InetSocketAddress',
3854 'data': {
3855 'host': 'str',
3856 'port': 'str',
3857 '*to': 'uint16',
3858 '*ipv4': 'bool',
3859 '*ipv6': 'bool' } }
3860
3861 ##
3862 # @UnixSocketAddress:
3863 #
3864 # Captures a socket address in the local ("Unix socket") namespace.
3865 #
3866 # @path: filesystem path to use
3867 #
3868 # Since: 1.3
3869 ##
3870 { 'struct': 'UnixSocketAddress',
3871 'data': {
3872 'path': 'str' } }
3873
3874 ##
3875 # @VsockSocketAddress:
3876 #
3877 # Captures a socket address in the vsock namespace.
3878 #
3879 # @cid: unique host identifier
3880 # @port: port
3881 #
3882 # Note: string types are used to allow for possible future hostname or
3883 # service resolution support.
3884 #
3885 # Since: 2.8
3886 ##
3887 { 'struct': 'VsockSocketAddress',
3888 'data': {
3889 'cid': 'str',
3890 'port': 'str' } }
3891
3892 ##
3893 # @SocketAddress:
3894 #
3895 # Captures the address of a socket, which could also be a named file descriptor
3896 #
3897 # Since: 1.3
3898 ##
3899 { 'union': 'SocketAddress',
3900 'data': {
3901 'inet': 'InetSocketAddress',
3902 'unix': 'UnixSocketAddress',
3903 'vsock': 'VsockSocketAddress',
3904 'fd': 'String' } }
3905
3906 ##
3907 # @getfd:
3908 #
3909 # Receive a file descriptor via SCM rights and assign it a name
3910 #
3911 # @fdname: file descriptor name
3912 #
3913 # Returns: Nothing on success
3914 #
3915 # Since: 0.14.0
3916 #
3917 # Notes: If @fdname already exists, the file descriptor assigned to
3918 # it will be closed and replaced by the received file
3919 # descriptor.
3920 # The 'closefd' command can be used to explicitly close the
3921 # file descriptor when it is no longer needed.
3922 ##
3923 { 'command': 'getfd', 'data': {'fdname': 'str'} }
3924
3925 ##
3926 # @closefd:
3927 #
3928 # Close a file descriptor previously passed via SCM rights
3929 #
3930 # @fdname: file descriptor name
3931 #
3932 # Returns: Nothing on success
3933 #
3934 # Since: 0.14.0
3935 ##
3936 { 'command': 'closefd', 'data': {'fdname': 'str'} }
3937
3938 ##
3939 # @MachineInfo:
3940 #
3941 # Information describing a machine.
3942 #
3943 # @name: the name of the machine
3944 #
3945 # @alias: #optional an alias for the machine name
3946 #
3947 # @is-default: #optional whether the machine is default
3948 #
3949 # @cpu-max: maximum number of CPUs supported by the machine type
3950 # (since 1.5.0)
3951 #
3952 # @hotpluggable-cpus: cpu hotplug via -device is supported (since 2.7.0)
3953 #
3954 # Since: 1.2.0
3955 ##
3956 { 'struct': 'MachineInfo',
3957 'data': { 'name': 'str', '*alias': 'str',
3958 '*is-default': 'bool', 'cpu-max': 'int',
3959 'hotpluggable-cpus': 'bool'} }
3960
3961 ##
3962 # @query-machines:
3963 #
3964 # Return a list of supported machines
3965 #
3966 # Returns: a list of MachineInfo
3967 #
3968 # Since: 1.2.0
3969 ##
3970 { 'command': 'query-machines', 'returns': ['MachineInfo'] }
3971
3972 ##
3973 # @CpuDefinitionInfo:
3974 #
3975 # Virtual CPU definition.
3976 #
3977 # @name: the name of the CPU definition
3978 #
3979 # @migration-safe: #optional whether a CPU definition can be safely used for
3980 # migration in combination with a QEMU compatibility machine
3981 # when migrating between different QMU versions and between
3982 # hosts with different sets of (hardware or software)
3983 # capabilities. If not provided, information is not available
3984 # and callers should not assume the CPU definition to be
3985 # migration-safe. (since 2.8)
3986 #
3987 # @static: whether a CPU definition is static and will not change depending on
3988 # QEMU version, machine type, machine options and accelerator options.
3989 # A static model is always migration-safe. (since 2.8)
3990 #
3991 # @unavailable-features: #optional List of properties that prevent
3992 # the CPU model from running in the current
3993 # host. (since 2.8)
3994 # @typename: Type name that can be used as argument to @device-list-properties,
3995 # to introspect properties configurable using -cpu or -global.
3996 # (since 2.9)
3997 #
3998 # @unavailable-features is a list of QOM property names that
3999 # represent CPU model attributes that prevent the CPU from running.
4000 # If the QOM property is read-only, that means there's no known
4001 # way to make the CPU model run in the current host. Implementations
4002 # that choose not to provide specific information return the
4003 # property name "type".
4004 # If the property is read-write, it means that it MAY be possible
4005 # to run the CPU model in the current host if that property is
4006 # changed. Management software can use it as hints to suggest or
4007 # choose an alternative for the user, or just to generate meaningful
4008 # error messages explaining why the CPU model can't be used.
4009 # If @unavailable-features is an empty list, the CPU model is
4010 # runnable using the current host and machine-type.
4011 # If @unavailable-features is not present, runnability
4012 # information for the CPU is not available.
4013 #
4014 # Since: 1.2.0
4015 ##
4016 { 'struct': 'CpuDefinitionInfo',
4017 'data': { 'name': 'str', '*migration-safe': 'bool', 'static': 'bool',
4018 '*unavailable-features': [ 'str' ], 'typename': 'str' } }
4019
4020 ##
4021 # @query-cpu-definitions:
4022 #
4023 # Return a list of supported virtual CPU definitions
4024 #
4025 # Returns: a list of CpuDefInfo
4026 #
4027 # Since: 1.2.0
4028 ##
4029 { 'command': 'query-cpu-definitions', 'returns': ['CpuDefinitionInfo'] }
4030
4031 ##
4032 # @CpuModelInfo:
4033 #
4034 # Virtual CPU model.
4035 #
4036 # A CPU model consists of the name of a CPU definition, to which
4037 # delta changes are applied (e.g. features added/removed). Most magic values
4038 # that an architecture might require should be hidden behind the name.
4039 # However, if required, architectures can expose relevant properties.
4040 #
4041 # @name: the name of the CPU definition the model is based on
4042 # @props: #optional a dictionary of QOM properties to be applied
4043 #
4044 # Since: 2.8.0
4045 ##
4046 { 'struct': 'CpuModelInfo',
4047 'data': { 'name': 'str',
4048 '*props': 'any' } }
4049
4050 ##
4051 # @CpuModelExpansionType:
4052 #
4053 # An enumeration of CPU model expansion types.
4054 #
4055 # @static: Expand to a static CPU model, a combination of a static base
4056 # model name and property delta changes. As the static base model will
4057 # never change, the expanded CPU model will be the same, independant of
4058 # independent of QEMU version, machine type, machine options, and
4059 # accelerator options. Therefore, the resulting model can be used by
4060 # tooling without having to specify a compatibility machine - e.g. when
4061 # displaying the "host" model. static CPU models are migration-safe.
4062 #
4063 # @full: Expand all properties. The produced model is not guaranteed to be
4064 # migration-safe, but allows tooling to get an insight and work with
4065 # model details.
4066 #
4067 # Since: 2.8.0
4068 ##
4069 { 'enum': 'CpuModelExpansionType',
4070 'data': [ 'static', 'full' ] }
4071
4072
4073 ##
4074 # @CpuModelExpansionInfo:
4075 #
4076 # The result of a cpu model expansion.
4077 #
4078 # @model: the expanded CpuModelInfo.
4079 #
4080 # Since: 2.8.0
4081 ##
4082 { 'struct': 'CpuModelExpansionInfo',
4083 'data': { 'model': 'CpuModelInfo' } }
4084
4085
4086 ##
4087 # @query-cpu-model-expansion:
4088 #
4089 # Expands a given CPU model (or a combination of CPU model + additional options)
4090 # to different granularities, allowing tooling to get an understanding what a
4091 # specific CPU model looks like in QEMU under a certain configuration.
4092 #
4093 # This interface can be used to query the "host" CPU model.
4094 #
4095 # The data returned by this command may be affected by:
4096 #
4097 # * QEMU version: CPU models may look different depending on the QEMU version.
4098 # (Except for CPU models reported as "static" in query-cpu-definitions.)
4099 # * machine-type: CPU model may look different depending on the machine-type.
4100 # (Except for CPU models reported as "static" in query-cpu-definitions.)
4101 # * machine options (including accelerator): in some architectures, CPU models
4102 # may look different depending on machine and accelerator options. (Except for
4103 # CPU models reported as "static" in query-cpu-definitions.)
4104 # * "-cpu" arguments and global properties: arguments to the -cpu option and
4105 # global properties may affect expansion of CPU models. Using
4106 # query-cpu-model-expansion while using these is not advised.
4107 #
4108 # Some architectures may not support all expansion types. s390x supports
4109 # "full" and "static".
4110 #
4111 # Returns: a CpuModelExpansionInfo. Returns an error if expanding CPU models is
4112 # not supported, if the model cannot be expanded, if the model contains
4113 # an unknown CPU definition name, unknown properties or properties
4114 # with a wrong type. Also returns an error if an expansion type is
4115 # not supported.
4116 #
4117 # Since: 2.8.0
4118 ##
4119 { 'command': 'query-cpu-model-expansion',
4120 'data': { 'type': 'CpuModelExpansionType',
4121 'model': 'CpuModelInfo' },
4122 'returns': 'CpuModelExpansionInfo' }
4123
4124 ##
4125 # @CpuModelCompareResult:
4126 #
4127 # An enumeration of CPU model comparation results. The result is usually
4128 # calculated using e.g. CPU features or CPU generations.
4129 #
4130 # @incompatible: If model A is incompatible to model B, model A is not
4131 # guaranteed to run where model B runs and the other way around.
4132 #
4133 # @identical: If model A is identical to model B, model A is guaranteed to run
4134 # where model B runs and the other way around.
4135 #
4136 # @superset: If model A is a superset of model B, model B is guaranteed to run
4137 # where model A runs. There are no guarantees about the other way.
4138 #
4139 # @subset: If model A is a subset of model B, model A is guaranteed to run
4140 # where model B runs. There are no guarantees about the other way.
4141 #
4142 # Since: 2.8.0
4143 ##
4144 { 'enum': 'CpuModelCompareResult',
4145 'data': [ 'incompatible', 'identical', 'superset', 'subset' ] }
4146
4147 ##
4148 # @CpuModelCompareInfo:
4149 #
4150 # The result of a CPU model comparison.
4151 #
4152 # @result: The result of the compare operation.
4153 # @responsible-properties: List of properties that led to the comparison result
4154 # not being identical.
4155 #
4156 # @responsible-properties is a list of QOM property names that led to
4157 # both CPUs not being detected as identical. For identical models, this
4158 # list is empty.
4159 # If a QOM property is read-only, that means there's no known way to make the
4160 # CPU models identical. If the special property name "type" is included, the
4161 # models are by definition not identical and cannot be made identical.
4162 #
4163 # Since: 2.8.0
4164 ##
4165 { 'struct': 'CpuModelCompareInfo',
4166 'data': {'result': 'CpuModelCompareResult',
4167 'responsible-properties': ['str']
4168 }
4169 }
4170
4171 ##
4172 # @query-cpu-model-comparison:
4173 #
4174 # Compares two CPU models, returning how they compare in a specific
4175 # configuration. The results indicates how both models compare regarding
4176 # runnability. This result can be used by tooling to make decisions if a
4177 # certain CPU model will run in a certain configuration or if a compatible
4178 # CPU model has to be created by baselining.
4179 #
4180 # Usually, a CPU model is compared against the maximum possible CPU model
4181 # of a certain configuration (e.g. the "host" model for KVM). If that CPU
4182 # model is identical or a subset, it will run in that configuration.
4183 #
4184 # The result returned by this command may be affected by:
4185 #
4186 # * QEMU version: CPU models may look different depending on the QEMU version.
4187 # (Except for CPU models reported as "static" in query-cpu-definitions.)
4188 # * machine-type: CPU model may look different depending on the machine-type.
4189 # (Except for CPU models reported as "static" in query-cpu-definitions.)
4190 # * machine options (including accelerator): in some architectures, CPU models
4191 # may look different depending on machine and accelerator options. (Except for
4192 # CPU models reported as "static" in query-cpu-definitions.)
4193 # * "-cpu" arguments and global properties: arguments to the -cpu option and
4194 # global properties may affect expansion of CPU models. Using
4195 # query-cpu-model-expansion while using these is not advised.
4196 #
4197 # Some architectures may not support comparing CPU models. s390x supports
4198 # comparing CPU models.
4199 #
4200 # Returns: a CpuModelBaselineInfo. Returns an error if comparing CPU models is
4201 # not supported, if a model cannot be used, if a model contains
4202 # an unknown cpu definition name, unknown properties or properties
4203 # with wrong types.
4204 #
4205 # Since: 2.8.0
4206 ##
4207 { 'command': 'query-cpu-model-comparison',
4208 'data': { 'modela': 'CpuModelInfo', 'modelb': 'CpuModelInfo' },
4209 'returns': 'CpuModelCompareInfo' }
4210
4211 ##
4212 # @CpuModelBaselineInfo:
4213 #
4214 # The result of a CPU model baseline.
4215 #
4216 # @model: the baselined CpuModelInfo.
4217 #
4218 # Since: 2.8.0
4219 ##
4220 { 'struct': 'CpuModelBaselineInfo',
4221 'data': { 'model': 'CpuModelInfo' } }
4222
4223 ##
4224 # @query-cpu-model-baseline:
4225 #
4226 # Baseline two CPU models, creating a compatible third model. The created
4227 # model will always be a static, migration-safe CPU model (see "static"
4228 # CPU model expansion for details).
4229 #
4230 # This interface can be used by tooling to create a compatible CPU model out
4231 # two CPU models. The created CPU model will be identical to or a subset of
4232 # both CPU models when comparing them. Therefore, the created CPU model is
4233 # guaranteed to run where the given CPU models run.
4234 #
4235 # The result returned by this command may be affected by:
4236 #
4237 # * QEMU version: CPU models may look different depending on the QEMU version.
4238 # (Except for CPU models reported as "static" in query-cpu-definitions.)
4239 # * machine-type: CPU model may look different depending on the machine-type.
4240 # (Except for CPU models reported as "static" in query-cpu-definitions.)
4241 # * machine options (including accelerator): in some architectures, CPU models
4242 # may look different depending on machine and accelerator options. (Except for
4243 # CPU models reported as "static" in query-cpu-definitions.)
4244 # * "-cpu" arguments and global properties: arguments to the -cpu option and
4245 # global properties may affect expansion of CPU models. Using
4246 # query-cpu-model-expansion while using these is not advised.
4247 #
4248 # Some architectures may not support baselining CPU models. s390x supports
4249 # baselining CPU models.
4250 #
4251 # Returns: a CpuModelBaselineInfo. Returns an error if baselining CPU models is
4252 # not supported, if a model cannot be used, if a model contains
4253 # an unknown cpu definition name, unknown properties or properties
4254 # with wrong types.
4255 #
4256 # Since: 2.8.0
4257 ##
4258 { 'command': 'query-cpu-model-baseline',
4259 'data': { 'modela': 'CpuModelInfo',
4260 'modelb': 'CpuModelInfo' },
4261 'returns': 'CpuModelBaselineInfo' }
4262
4263 ##
4264 # @AddfdInfo:
4265 #
4266 # Information about a file descriptor that was added to an fd set.
4267 #
4268 # @fdset-id: The ID of the fd set that @fd was added to.
4269 #
4270 # @fd: The file descriptor that was received via SCM rights and
4271 # added to the fd set.
4272 #
4273 # Since: 1.2.0
4274 ##
4275 { 'struct': 'AddfdInfo', 'data': {'fdset-id': 'int', 'fd': 'int'} }
4276
4277 ##
4278 # @add-fd:
4279 #
4280 # Add a file descriptor, that was passed via SCM rights, to an fd set.
4281 #
4282 # @fdset-id: #optional The ID of the fd set to add the file descriptor to.
4283 #
4284 # @opaque: #optional A free-form string that can be used to describe the fd.
4285 #
4286 # Returns: @AddfdInfo on success
4287 # If file descriptor was not received, FdNotSupplied
4288 # If @fdset-id is a negative value, InvalidParameterValue
4289 #
4290 # Notes: The list of fd sets is shared by all monitor connections.
4291 #
4292 # If @fdset-id is not specified, a new fd set will be created.
4293 #
4294 # Since: 1.2.0
4295 ##
4296 { 'command': 'add-fd', 'data': {'*fdset-id': 'int', '*opaque': 'str'},
4297 'returns': 'AddfdInfo' }
4298
4299 ##
4300 # @remove-fd:
4301 #
4302 # Remove a file descriptor from an fd set.
4303 #
4304 # @fdset-id: The ID of the fd set that the file descriptor belongs to.
4305 #
4306 # @fd: #optional The file descriptor that is to be removed.
4307 #
4308 # Returns: Nothing on success
4309 # If @fdset-id or @fd is not found, FdNotFound
4310 #
4311 # Since: 1.2.0
4312 #
4313 # Notes: The list of fd sets is shared by all monitor connections.
4314 #
4315 # If @fd is not specified, all file descriptors in @fdset-id
4316 # will be removed.
4317 ##
4318 { 'command': 'remove-fd', 'data': {'fdset-id': 'int', '*fd': 'int'} }
4319
4320 ##
4321 # @FdsetFdInfo:
4322 #
4323 # Information about a file descriptor that belongs to an fd set.
4324 #
4325 # @fd: The file descriptor value.
4326 #
4327 # @opaque: #optional A free-form string that can be used to describe the fd.
4328 #
4329 # Since: 1.2.0
4330 ##
4331 { 'struct': 'FdsetFdInfo',
4332 'data': {'fd': 'int', '*opaque': 'str'} }
4333
4334 ##
4335 # @FdsetInfo:
4336 #
4337 # Information about an fd set.
4338 #
4339 # @fdset-id: The ID of the fd set.
4340 #
4341 # @fds: A list of file descriptors that belong to this fd set.
4342 #
4343 # Since: 1.2.0
4344 ##
4345 { 'struct': 'FdsetInfo',
4346 'data': {'fdset-id': 'int', 'fds': ['FdsetFdInfo']} }
4347
4348 ##
4349 # @query-fdsets:
4350 #
4351 # Return information describing all fd sets.
4352 #
4353 # Returns: A list of @FdsetInfo
4354 #
4355 # Since: 1.2.0
4356 #
4357 # Note: The list of fd sets is shared by all monitor connections.
4358 #
4359 ##
4360 { 'command': 'query-fdsets', 'returns': ['FdsetInfo'] }
4361
4362 ##
4363 # @TargetInfo:
4364 #
4365 # Information describing the QEMU target.
4366 #
4367 # @arch: the target architecture (eg "x86_64", "i386", etc)
4368 #
4369 # Since: 1.2.0
4370 ##
4371 { 'struct': 'TargetInfo',
4372 'data': { 'arch': 'str' } }
4373
4374 ##
4375 # @query-target:
4376 #
4377 # Return information about the target for this QEMU
4378 #
4379 # Returns: TargetInfo
4380 #
4381 # Since: 1.2.0
4382 ##
4383 { 'command': 'query-target', 'returns': 'TargetInfo' }
4384
4385 ##
4386 # @QKeyCode:
4387 #
4388 # An enumeration of key name.
4389 #
4390 # This is used by the @send-key command.
4391 #
4392 # @unmapped: since 2.0
4393 # @pause: since 2.0
4394 # @ro: since 2.4
4395 # @kp_comma: since 2.4
4396 # @kp_equals: since 2.6
4397 # @power: since 2.6
4398 # @hiragana: since 2.9
4399 # @henkan: since 2.9
4400 # @yen: since 2.9
4401 #
4402 # Since: 1.3.0
4403 #
4404 ##
4405 { 'enum': 'QKeyCode',
4406 'data': [ 'unmapped',
4407 'shift', 'shift_r', 'alt', 'alt_r', 'altgr', 'altgr_r', 'ctrl',
4408 'ctrl_r', 'menu', 'esc', '1', '2', '3', '4', '5', '6', '7', '8',
4409 '9', '0', 'minus', 'equal', 'backspace', 'tab', 'q', 'w', 'e',
4410 'r', 't', 'y', 'u', 'i', 'o', 'p', 'bracket_left', 'bracket_right',
4411 'ret', 'a', 's', 'd', 'f', 'g', 'h', 'j', 'k', 'l', 'semicolon',
4412 'apostrophe', 'grave_accent', 'backslash', 'z', 'x', 'c', 'v', 'b',
4413 'n', 'm', 'comma', 'dot', 'slash', 'asterisk', 'spc', 'caps_lock',
4414 'f1', 'f2', 'f3', 'f4', 'f5', 'f6', 'f7', 'f8', 'f9', 'f10',
4415 'num_lock', 'scroll_lock', 'kp_divide', 'kp_multiply',
4416 'kp_subtract', 'kp_add', 'kp_enter', 'kp_decimal', 'sysrq', 'kp_0',
4417 'kp_1', 'kp_2', 'kp_3', 'kp_4', 'kp_5', 'kp_6', 'kp_7', 'kp_8',
4418 'kp_9', 'less', 'f11', 'f12', 'print', 'home', 'pgup', 'pgdn', 'end',
4419 'left', 'up', 'down', 'right', 'insert', 'delete', 'stop', 'again',
4420 'props', 'undo', 'front', 'copy', 'open', 'paste', 'find', 'cut',
4421 'lf', 'help', 'meta_l', 'meta_r', 'compose', 'pause',
4422 'ro', 'hiragana', 'henkan', 'yen',
4423 'kp_comma', 'kp_equals', 'power' ] }
4424
4425 ##
4426 # @KeyValue:
4427 #
4428 # Represents a keyboard key.
4429 #
4430 # Since: 1.3.0
4431 ##
4432 { 'union': 'KeyValue',
4433 'data': {
4434 'number': 'int',
4435 'qcode': 'QKeyCode' } }
4436
4437 ##
4438 # @send-key:
4439 #
4440 # Send keys to guest.
4441 #
4442 # @keys: An array of @KeyValue elements. All @KeyValues in this array are
4443 # simultaneously sent to the guest. A @KeyValue.number value is sent
4444 # directly to the guest, while @KeyValue.qcode must be a valid
4445 # @QKeyCode value
4446 #
4447 # @hold-time: #optional time to delay key up events, milliseconds. Defaults
4448 # to 100
4449 #
4450 # Returns: Nothing on success
4451 # If key is unknown or redundant, InvalidParameter
4452 #
4453 # Since: 1.3.0
4454 #
4455 ##
4456 { 'command': 'send-key',
4457 'data': { 'keys': ['KeyValue'], '*hold-time': 'int' } }
4458
4459 ##
4460 # @screendump:
4461 #
4462 # Write a PPM of the VGA screen to a file.
4463 #
4464 # @filename: the path of a new PPM file to store the image
4465 #
4466 # Returns: Nothing on success
4467 #
4468 # Since: 0.14.0
4469 ##
4470 { 'command': 'screendump', 'data': {'filename': 'str'} }
4471
4472
4473 ##
4474 # @ChardevCommon:
4475 #
4476 # Configuration shared across all chardev backends
4477 #
4478 # @logfile: #optional The name of a logfile to save output
4479 # @logappend: #optional true to append instead of truncate
4480 # (default to false to truncate)
4481 #
4482 # Since: 2.6
4483 ##
4484 { 'struct': 'ChardevCommon', 'data': { '*logfile': 'str',
4485 '*logappend': 'bool' } }
4486
4487 ##
4488 # @ChardevFile:
4489 #
4490 # Configuration info for file chardevs.
4491 #
4492 # @in: #optional The name of the input file
4493 # @out: The name of the output file
4494 # @append: #optional Open the file in append mode (default false to
4495 # truncate) (Since 2.6)
4496 #
4497 # Since: 1.4
4498 ##
4499 { 'struct': 'ChardevFile', 'data': { '*in' : 'str',
4500 'out' : 'str',
4501 '*append': 'bool' },
4502 'base': 'ChardevCommon' }
4503
4504 ##
4505 # @ChardevHostdev:
4506 #
4507 # Configuration info for device and pipe chardevs.
4508 #
4509 # @device: The name of the special file for the device,
4510 # i.e. /dev/ttyS0 on Unix or COM1: on Windows
4511 #
4512 # Since: 1.4
4513 ##
4514 { 'struct': 'ChardevHostdev', 'data': { 'device' : 'str' },
4515 'base': 'ChardevCommon' }
4516
4517 ##
4518 # @ChardevSocket:
4519 #
4520 # Configuration info for (stream) socket chardevs.
4521 #
4522 # @addr: socket address to listen on (server=true)
4523 # or connect to (server=false)
4524 # @tls-creds: #optional the ID of the TLS credentials object (since 2.6)
4525 # @server: #optional create server socket (default: true)
4526 # @wait: #optional wait for incoming connection on server
4527 # sockets (default: false).
4528 # @nodelay: #optional set TCP_NODELAY socket option (default: false)
4529 # @telnet: #optional enable telnet protocol on server
4530 # sockets (default: false)
4531 # @reconnect: #optional For a client socket, if a socket is disconnected,
4532 # then attempt a reconnect after the given number of seconds.
4533 # Setting this to zero disables this function. (default: 0)
4534 # (Since: 2.2)
4535 #
4536 # Since: 1.4
4537 ##
4538 { 'struct': 'ChardevSocket', 'data': { 'addr' : 'SocketAddress',
4539 '*tls-creds' : 'str',
4540 '*server' : 'bool',
4541 '*wait' : 'bool',
4542 '*nodelay' : 'bool',
4543 '*telnet' : 'bool',
4544 '*reconnect' : 'int' },
4545 'base': 'ChardevCommon' }
4546
4547 ##
4548 # @ChardevUdp:
4549 #
4550 # Configuration info for datagram socket chardevs.
4551 #
4552 # @remote: remote address
4553 # @local: #optional local address
4554 #
4555 # Since: 1.5
4556 ##
4557 { 'struct': 'ChardevUdp', 'data': { 'remote' : 'SocketAddress',
4558 '*local' : 'SocketAddress' },
4559 'base': 'ChardevCommon' }
4560
4561 ##
4562 # @ChardevMux:
4563 #
4564 # Configuration info for mux chardevs.
4565 #
4566 # @chardev: name of the base chardev.
4567 #
4568 # Since: 1.5
4569 ##
4570 { 'struct': 'ChardevMux', 'data': { 'chardev' : 'str' },
4571 'base': 'ChardevCommon' }
4572
4573 ##
4574 # @ChardevStdio:
4575 #
4576 # Configuration info for stdio chardevs.
4577 #
4578 # @signal: #optional Allow signals (such as SIGINT triggered by ^C)
4579 # be delivered to qemu. Default: true in -nographic mode,
4580 # false otherwise.
4581 #
4582 # Since: 1.5
4583 ##
4584 { 'struct': 'ChardevStdio', 'data': { '*signal' : 'bool' },
4585 'base': 'ChardevCommon' }
4586
4587
4588 ##
4589 # @ChardevSpiceChannel:
4590 #
4591 # Configuration info for spice vm channel chardevs.
4592 #
4593 # @type: kind of channel (for example vdagent).
4594 #
4595 # Since: 1.5
4596 ##
4597 { 'struct': 'ChardevSpiceChannel', 'data': { 'type' : 'str' },
4598 'base': 'ChardevCommon' }
4599
4600 ##
4601 # @ChardevSpicePort:
4602 #
4603 # Configuration info for spice port chardevs.
4604 #
4605 # @fqdn: name of the channel (see docs/spice-port-fqdn.txt)
4606 #
4607 # Since: 1.5
4608 ##
4609 { 'struct': 'ChardevSpicePort', 'data': { 'fqdn' : 'str' },
4610 'base': 'ChardevCommon' }
4611
4612 ##
4613 # @ChardevVC:
4614 #
4615 # Configuration info for virtual console chardevs.
4616 #
4617 # @width: console width, in pixels
4618 # @height: console height, in pixels
4619 # @cols: console width, in chars
4620 # @rows: console height, in chars
4621 #
4622 # Since: 1.5
4623 ##
4624 { 'struct': 'ChardevVC', 'data': { '*width' : 'int',
4625 '*height' : 'int',
4626 '*cols' : 'int',
4627 '*rows' : 'int' },
4628 'base': 'ChardevCommon' }
4629
4630 ##
4631 # @ChardevRingbuf:
4632 #
4633 # Configuration info for ring buffer chardevs.
4634 #
4635 # @size: #optional ring buffer size, must be power of two, default is 65536
4636 #
4637 # Since: 1.5
4638 ##
4639 { 'struct': 'ChardevRingbuf', 'data': { '*size' : 'int' },
4640 'base': 'ChardevCommon' }
4641
4642 ##
4643 # @ChardevBackend:
4644 #
4645 # Configuration info for the new chardev backend.
4646 #
4647 # Since: 1.4 (testdev since 2.2)
4648 ##
4649 { 'union': 'ChardevBackend', 'data': { 'file' : 'ChardevFile',
4650 'serial' : 'ChardevHostdev',
4651 'parallel': 'ChardevHostdev',
4652 'pipe' : 'ChardevHostdev',
4653 'socket' : 'ChardevSocket',
4654 'udp' : 'ChardevUdp',
4655 'pty' : 'ChardevCommon',
4656 'null' : 'ChardevCommon',
4657 'mux' : 'ChardevMux',
4658 'msmouse': 'ChardevCommon',
4659 'braille': 'ChardevCommon',
4660 'testdev': 'ChardevCommon',
4661 'stdio' : 'ChardevStdio',
4662 'console': 'ChardevCommon',
4663 'spicevmc' : 'ChardevSpiceChannel',
4664 'spiceport' : 'ChardevSpicePort',
4665 'vc' : 'ChardevVC',
4666 'ringbuf': 'ChardevRingbuf',
4667 # next one is just for compatibility
4668 'memory' : 'ChardevRingbuf' } }
4669
4670 ##
4671 # @ChardevReturn:
4672 #
4673 # Return info about the chardev backend just created.
4674 #
4675 # @pty: #optional name of the slave pseudoterminal device, present if
4676 # and only if a chardev of type 'pty' was created
4677 #
4678 # Since: 1.4
4679 ##
4680 { 'struct' : 'ChardevReturn', 'data': { '*pty' : 'str' } }
4681
4682 ##
4683 # @chardev-add:
4684 #
4685 # Add a character device backend
4686 #
4687 # @id: the chardev's ID, must be unique
4688 # @backend: backend type and parameters
4689 #
4690 # Returns: ChardevReturn.
4691 #
4692 # Since: 1.4
4693 ##
4694 { 'command': 'chardev-add', 'data': {'id' : 'str',
4695 'backend' : 'ChardevBackend' },
4696 'returns': 'ChardevReturn' }
4697
4698 ##
4699 # @chardev-remove:
4700 #
4701 # Remove a character device backend
4702 #
4703 # @id: the chardev's ID, must exist and not be in use
4704 #
4705 # Returns: Nothing on success
4706 #
4707 # Since: 1.4
4708 ##
4709 { 'command': 'chardev-remove', 'data': {'id': 'str'} }
4710
4711 ##
4712 # @TpmModel:
4713 #
4714 # An enumeration of TPM models
4715 #
4716 # @tpm-tis: TPM TIS model
4717 #
4718 # Since: 1.5
4719 ##
4720 { 'enum': 'TpmModel', 'data': [ 'tpm-tis' ] }
4721
4722 ##
4723 # @query-tpm-models:
4724 #
4725 # Return a list of supported TPM models
4726 #
4727 # Returns: a list of TpmModel
4728 #
4729 # Since: 1.5
4730 ##
4731 { 'command': 'query-tpm-models', 'returns': ['TpmModel'] }
4732
4733 ##
4734 # @TpmType:
4735 #
4736 # An enumeration of TPM types
4737 #
4738 # @passthrough: TPM passthrough type
4739 #
4740 # Since: 1.5
4741 ##
4742 { 'enum': 'TpmType', 'data': [ 'passthrough' ] }
4743
4744 ##
4745 # @query-tpm-types:
4746 #
4747 # Return a list of supported TPM types
4748 #
4749 # Returns: a list of TpmType
4750 #
4751 # Since: 1.5
4752 ##
4753 { 'command': 'query-tpm-types', 'returns': ['TpmType'] }
4754
4755 ##
4756 # @TPMPassthroughOptions:
4757 #
4758 # Information about the TPM passthrough type
4759 #
4760 # @path: #optional string describing the path used for accessing the TPM device
4761 #
4762 # @cancel-path: #optional string showing the TPM's sysfs cancel file
4763 # for cancellation of TPM commands while they are executing
4764 #
4765 # Since: 1.5
4766 ##
4767 { 'struct': 'TPMPassthroughOptions', 'data': { '*path' : 'str',
4768 '*cancel-path' : 'str'} }
4769
4770 ##
4771 # @TpmTypeOptions:
4772 #
4773 # A union referencing different TPM backend types' configuration options
4774 #
4775 # @type: 'passthrough' The configuration options for the TPM passthrough type
4776 #
4777 # Since: 1.5
4778 ##
4779 { 'union': 'TpmTypeOptions',
4780 'data': { 'passthrough' : 'TPMPassthroughOptions' } }
4781
4782 ##
4783 # @TPMInfo:
4784 #
4785 # Information about the TPM
4786 #
4787 # @id: The Id of the TPM
4788 #
4789 # @model: The TPM frontend model
4790 #
4791 # @options: The TPM (backend) type configuration options
4792 #
4793 # Since: 1.5
4794 ##
4795 { 'struct': 'TPMInfo',
4796 'data': {'id': 'str',
4797 'model': 'TpmModel',
4798 'options': 'TpmTypeOptions' } }
4799
4800 ##
4801 # @query-tpm:
4802 #
4803 # Return information about the TPM device
4804 #
4805 # Returns: @TPMInfo on success
4806 #
4807 # Since: 1.5
4808 ##
4809 { 'command': 'query-tpm', 'returns': ['TPMInfo'] }
4810
4811 ##
4812 # @AcpiTableOptions:
4813 #
4814 # Specify an ACPI table on the command line to load.
4815 #
4816 # At most one of @file and @data can be specified. The list of files specified
4817 # by any one of them is loaded and concatenated in order. If both are omitted,
4818 # @data is implied.
4819 #
4820 # Other fields / optargs can be used to override fields of the generic ACPI
4821 # table header; refer to the ACPI specification 5.0, section 5.2.6 System
4822 # Description Table Header. If a header field is not overridden, then the
4823 # corresponding value from the concatenated blob is used (in case of @file), or
4824 # it is filled in with a hard-coded value (in case of @data).
4825 #
4826 # String fields are copied into the matching ACPI member from lowest address
4827 # upwards, and silently truncated / NUL-padded to length.
4828 #
4829 # @sig: #optional table signature / identifier (4 bytes)
4830 #
4831 # @rev: #optional table revision number (dependent on signature, 1 byte)
4832 #
4833 # @oem_id: #optional OEM identifier (6 bytes)
4834 #
4835 # @oem_table_id: #optional OEM table identifier (8 bytes)
4836 #
4837 # @oem_rev: #optional OEM-supplied revision number (4 bytes)
4838 #
4839 # @asl_compiler_id: #optional identifier of the utility that created the table
4840 # (4 bytes)
4841 #
4842 # @asl_compiler_rev: #optional revision number of the utility that created the
4843 # table (4 bytes)
4844 #
4845 # @file: #optional colon (:) separated list of pathnames to load and
4846 # concatenate as table data. The resultant binary blob is expected to
4847 # have an ACPI table header. At least one file is required. This field
4848 # excludes @data.
4849 #
4850 # @data: #optional colon (:) separated list of pathnames to load and
4851 # concatenate as table data. The resultant binary blob must not have an
4852 # ACPI table header. At least one file is required. This field excludes
4853 # @file.
4854 #
4855 # Since: 1.5
4856 ##
4857 { 'struct': 'AcpiTableOptions',
4858 'data': {
4859 '*sig': 'str',
4860 '*rev': 'uint8',
4861 '*oem_id': 'str',
4862 '*oem_table_id': 'str',
4863 '*oem_rev': 'uint32',
4864 '*asl_compiler_id': 'str',
4865 '*asl_compiler_rev': 'uint32',
4866 '*file': 'str',
4867 '*data': 'str' }}
4868
4869 ##
4870 # @CommandLineParameterType:
4871 #
4872 # Possible types for an option parameter.
4873 #
4874 # @string: accepts a character string
4875 #
4876 # @boolean: accepts "on" or "off"
4877 #
4878 # @number: accepts a number
4879 #
4880 # @size: accepts a number followed by an optional suffix (K)ilo,
4881 # (M)ega, (G)iga, (T)era
4882 #
4883 # Since: 1.5
4884 ##
4885 { 'enum': 'CommandLineParameterType',
4886 'data': ['string', 'boolean', 'number', 'size'] }
4887
4888 ##
4889 # @CommandLineParameterInfo:
4890 #
4891 # Details about a single parameter of a command line option.
4892 #
4893 # @name: parameter name
4894 #
4895 # @type: parameter @CommandLineParameterType
4896 #
4897 # @help: #optional human readable text string, not suitable for parsing.
4898 #
4899 # @default: #optional default value string (since 2.1)
4900 #
4901 # Since: 1.5
4902 ##
4903 { 'struct': 'CommandLineParameterInfo',
4904 'data': { 'name': 'str',
4905 'type': 'CommandLineParameterType',
4906 '*help': 'str',
4907 '*default': 'str' } }
4908
4909 ##
4910 # @CommandLineOptionInfo:
4911 #
4912 # Details about a command line option, including its list of parameter details
4913 #
4914 # @option: option name
4915 #
4916 # @parameters: an array of @CommandLineParameterInfo
4917 #
4918 # Since: 1.5
4919 ##
4920 { 'struct': 'CommandLineOptionInfo',
4921 'data': { 'option': 'str', 'parameters': ['CommandLineParameterInfo'] } }
4922
4923 ##
4924 # @query-command-line-options:
4925 #
4926 # Query command line option schema.
4927 #
4928 # @option: #optional option name
4929 #
4930 # Returns: list of @CommandLineOptionInfo for all options (or for the given
4931 # @option). Returns an error if the given @option doesn't exist.
4932 #
4933 # Since: 1.5
4934 ##
4935 {'command': 'query-command-line-options', 'data': { '*option': 'str' },
4936 'returns': ['CommandLineOptionInfo'] }
4937
4938 ##
4939 # @X86CPURegister32:
4940 #
4941 # A X86 32-bit register
4942 #
4943 # Since: 1.5
4944 ##
4945 { 'enum': 'X86CPURegister32',
4946 'data': [ 'EAX', 'EBX', 'ECX', 'EDX', 'ESP', 'EBP', 'ESI', 'EDI' ] }
4947
4948 ##
4949 # @X86CPUFeatureWordInfo:
4950 #
4951 # Information about a X86 CPU feature word
4952 #
4953 # @cpuid-input-eax: Input EAX value for CPUID instruction for that feature word
4954 #
4955 # @cpuid-input-ecx: #optional Input ECX value for CPUID instruction for that
4956 # feature word
4957 #
4958 # @cpuid-register: Output register containing the feature bits
4959 #
4960 # @features: value of output register, containing the feature bits
4961 #
4962 # Since: 1.5
4963 ##
4964 { 'struct': 'X86CPUFeatureWordInfo',
4965 'data': { 'cpuid-input-eax': 'int',
4966 '*cpuid-input-ecx': 'int',
4967 'cpuid-register': 'X86CPURegister32',
4968 'features': 'int' } }
4969
4970 ##
4971 # @DummyForceArrays:
4972 #
4973 # Not used by QMP; hack to let us use X86CPUFeatureWordInfoList internally
4974 #
4975 # Since: 2.5
4976 ##
4977 { 'struct': 'DummyForceArrays',
4978 'data': { 'unused': ['X86CPUFeatureWordInfo'] } }
4979
4980
4981 ##
4982 # @RxState:
4983 #
4984 # Packets receiving state
4985 #
4986 # @normal: filter assigned packets according to the mac-table
4987 #
4988 # @none: don't receive any assigned packet
4989 #
4990 # @all: receive all assigned packets
4991 #
4992 # Since: 1.6
4993 ##
4994 { 'enum': 'RxState', 'data': [ 'normal', 'none', 'all' ] }
4995
4996 ##
4997 # @RxFilterInfo:
4998 #
4999 # Rx-filter information for a NIC.
5000 #
5001 # @name: net client name
5002 #
5003 # @promiscuous: whether promiscuous mode is enabled
5004 #
5005 # @multicast: multicast receive state
5006 #
5007 # @unicast: unicast receive state
5008 #
5009 # @vlan: vlan receive state (Since 2.0)
5010 #
5011 # @broadcast-allowed: whether to receive broadcast
5012 #
5013 # @multicast-overflow: multicast table is overflowed or not
5014 #
5015 # @unicast-overflow: unicast table is overflowed or not
5016 #
5017 # @main-mac: the main macaddr string
5018 #
5019 # @vlan-table: a list of active vlan id
5020 #
5021 # @unicast-table: a list of unicast macaddr string
5022 #
5023 # @multicast-table: a list of multicast macaddr string
5024 #
5025 # Since: 1.6
5026 ##
5027 { 'struct': 'RxFilterInfo',
5028 'data': {
5029 'name': 'str',
5030 'promiscuous': 'bool',
5031 'multicast': 'RxState',
5032 'unicast': 'RxState',
5033 'vlan': 'RxState',
5034 'broadcast-allowed': 'bool',
5035 'multicast-overflow': 'bool',
5036 'unicast-overflow': 'bool',
5037 'main-mac': 'str',
5038 'vlan-table': ['int'],
5039 'unicast-table': ['str'],
5040 'multicast-table': ['str'] }}
5041
5042 ##
5043 # @query-rx-filter:
5044 #
5045 # Return rx-filter information for all NICs (or for the given NIC).
5046 #
5047 # @name: #optional net client name
5048 #
5049 # Returns: list of @RxFilterInfo for all NICs (or for the given NIC).
5050 # Returns an error if the given @name doesn't exist, or given
5051 # NIC doesn't support rx-filter querying, or given net client
5052 # isn't a NIC.
5053 #
5054 # Since: 1.6
5055 ##
5056 { 'command': 'query-rx-filter', 'data': { '*name': 'str' },
5057 'returns': ['RxFilterInfo'] }
5058
5059 ##
5060 # @InputButton:
5061 #
5062 # Button of a pointer input device (mouse, tablet).
5063 #
5064 # Since: 2.0
5065 ##
5066 { 'enum' : 'InputButton',
5067 'data' : [ 'left', 'middle', 'right', 'wheel-up', 'wheel-down' ] }
5068
5069 ##
5070 # @InputAxis:
5071 #
5072 # Position axis of a pointer input device (mouse, tablet).
5073 #
5074 # Since: 2.0
5075 ##
5076 { 'enum' : 'InputAxis',
5077 'data' : [ 'x', 'y' ] }
5078
5079 ##
5080 # @InputKeyEvent:
5081 #
5082 # Keyboard input event.
5083 #
5084 # @key: Which key this event is for.
5085 # @down: True for key-down and false for key-up events.
5086 #
5087 # Since: 2.0
5088 ##
5089 { 'struct' : 'InputKeyEvent',
5090 'data' : { 'key' : 'KeyValue',
5091 'down' : 'bool' } }
5092
5093 ##
5094 # @InputBtnEvent:
5095 #
5096 # Pointer button input event.
5097 #
5098 # @button: Which button this event is for.
5099 # @down: True for key-down and false for key-up events.
5100 #
5101 # Since: 2.0
5102 ##
5103 { 'struct' : 'InputBtnEvent',
5104 'data' : { 'button' : 'InputButton',
5105 'down' : 'bool' } }
5106
5107 ##
5108 # @InputMoveEvent:
5109 #
5110 # Pointer motion input event.
5111 #
5112 # @axis: Which axis is referenced by @value.
5113 # @value: Pointer position. For absolute coordinates the
5114 # valid range is 0 -> 0x7ffff
5115 #
5116 # Since: 2.0
5117 ##
5118 { 'struct' : 'InputMoveEvent',
5119 'data' : { 'axis' : 'InputAxis',
5120 'value' : 'int' } }
5121
5122 ##
5123 # @InputEvent:
5124 #
5125 # Input event union.
5126 #
5127 # @type: the input type, one of:
5128 # - 'key': Input event of Keyboard
5129 # - 'btn': Input event of pointer buttons
5130 # - 'rel': Input event of relative pointer motion
5131 # - 'abs': Input event of absolute pointer motion
5132 #
5133 # Since: 2.0
5134 ##
5135 { 'union' : 'InputEvent',
5136 'data' : { 'key' : 'InputKeyEvent',
5137 'btn' : 'InputBtnEvent',
5138 'rel' : 'InputMoveEvent',
5139 'abs' : 'InputMoveEvent' } }
5140
5141 ##
5142 # @input-send-event:
5143 #
5144 # Send input event(s) to guest.
5145 #
5146 # @device: #optional display device to send event(s) to.
5147 # @head: #optional head to send event(s) to, in case the
5148 # display device supports multiple scanouts.
5149 # @events: List of InputEvent union.
5150 #
5151 # Returns: Nothing on success.
5152 #
5153 # The @display and @head parameters can be used to send the input
5154 # event to specific input devices in case (a) multiple input devices
5155 # of the same kind are added to the virtual machine and (b) you have
5156 # configured input routing (see docs/multiseat.txt) for those input
5157 # devices. The parameters work exactly like the device and head
5158 # properties of input devices. If @device is missing, only devices
5159 # that have no input routing config are admissible. If @device is
5160 # specified, both input devices with and without input routing config
5161 # are admissible, but devices with input routing config take
5162 # precedence.
5163 #
5164 # Since: 2.6
5165 ##
5166 { 'command': 'input-send-event',
5167 'data': { '*device': 'str',
5168 '*head' : 'int',
5169 'events' : [ 'InputEvent' ] } }
5170
5171 ##
5172 # @NumaOptions:
5173 #
5174 # A discriminated record of NUMA options. (for OptsVisitor)
5175 #
5176 # Since: 2.1
5177 ##
5178 { 'union': 'NumaOptions',
5179 'data': {
5180 'node': 'NumaNodeOptions' }}
5181
5182 ##
5183 # @NumaNodeOptions:
5184 #
5185 # Create a guest NUMA node. (for OptsVisitor)
5186 #
5187 # @nodeid: #optional NUMA node ID (increase by 1 from 0 if omitted)
5188 #
5189 # @cpus: #optional VCPUs belonging to this node (assign VCPUS round-robin
5190 # if omitted)
5191 #
5192 # @mem: #optional memory size of this node; mutually exclusive with @memdev.
5193 # Equally divide total memory among nodes if both @mem and @memdev are
5194 # omitted.
5195 #
5196 # @memdev: #optional memory backend object. If specified for one node,
5197 # it must be specified for all nodes.
5198 #
5199 # Since: 2.1
5200 ##
5201 { 'struct': 'NumaNodeOptions',
5202 'data': {
5203 '*nodeid': 'uint16',
5204 '*cpus': ['uint16'],
5205 '*mem': 'size',
5206 '*memdev': 'str' }}
5207
5208 ##
5209 # @HostMemPolicy:
5210 #
5211 # Host memory policy types
5212 #
5213 # @default: restore default policy, remove any nondefault policy
5214 #
5215 # @preferred: set the preferred host nodes for allocation
5216 #
5217 # @bind: a strict policy that restricts memory allocation to the
5218 # host nodes specified
5219 #
5220 # @interleave: memory allocations are interleaved across the set
5221 # of host nodes specified
5222 #
5223 # Since: 2.1
5224 ##
5225 { 'enum': 'HostMemPolicy',
5226 'data': [ 'default', 'preferred', 'bind', 'interleave' ] }
5227
5228 ##
5229 # @Memdev:
5230 #
5231 # Information about memory backend
5232 #
5233 # @id: #optional backend's ID if backend has 'id' property (since 2.9)
5234 #
5235 # @size: memory backend size
5236 #
5237 # @merge: enables or disables memory merge support
5238 #
5239 # @dump: includes memory backend's memory in a core dump or not
5240 #
5241 # @prealloc: enables or disables memory preallocation
5242 #
5243 # @host-nodes: host nodes for its memory policy
5244 #
5245 # @policy: memory policy of memory backend
5246 #
5247 # Since: 2.1
5248 ##
5249 { 'struct': 'Memdev',
5250 'data': {
5251 '*id': 'str',
5252 'size': 'size',
5253 'merge': 'bool',
5254 'dump': 'bool',
5255 'prealloc': 'bool',
5256 'host-nodes': ['uint16'],
5257 'policy': 'HostMemPolicy' }}
5258
5259 ##
5260 # @query-memdev:
5261 #
5262 # Returns information for all memory backends.
5263 #
5264 # Returns: a list of @Memdev.
5265 #
5266 # Since: 2.1
5267 ##
5268 { 'command': 'query-memdev', 'returns': ['Memdev'] }
5269
5270 ##
5271 # @PCDIMMDeviceInfo:
5272 #
5273 # PCDIMMDevice state information
5274 #
5275 # @id: #optional device's ID
5276 #
5277 # @addr: physical address, where device is mapped
5278 #
5279 # @size: size of memory that the device provides
5280 #
5281 # @slot: slot number at which device is plugged in
5282 #
5283 # @node: NUMA node number where device is plugged in
5284 #
5285 # @memdev: memory backend linked with device
5286 #
5287 # @hotplugged: true if device was hotplugged
5288 #
5289 # @hotpluggable: true if device if could be added/removed while machine is running
5290 #
5291 # Since: 2.1
5292 ##
5293 { 'struct': 'PCDIMMDeviceInfo',
5294 'data': { '*id': 'str',
5295 'addr': 'int',
5296 'size': 'int',
5297 'slot': 'int',
5298 'node': 'int',
5299 'memdev': 'str',
5300 'hotplugged': 'bool',
5301 'hotpluggable': 'bool'
5302 }
5303 }
5304
5305 ##
5306 # @MemoryDeviceInfo:
5307 #
5308 # Union containing information about a memory device
5309 #
5310 # Since: 2.1
5311 ##
5312 { 'union': 'MemoryDeviceInfo', 'data': {'dimm': 'PCDIMMDeviceInfo'} }
5313
5314 ##
5315 # @query-memory-devices:
5316 #
5317 # Lists available memory devices and their state
5318 #
5319 # Since: 2.1
5320 ##
5321 { 'command': 'query-memory-devices', 'returns': ['MemoryDeviceInfo'] }
5322
5323 ##
5324 # @ACPISlotType:
5325 #
5326 # @DIMM: memory slot
5327 # @CPU: logical CPU slot (since 2.7)
5328 ##
5329 { 'enum': 'ACPISlotType', 'data': [ 'DIMM', 'CPU' ] }
5330
5331 ##
5332 # @ACPIOSTInfo:
5333 #
5334 # OSPM Status Indication for a device
5335 # For description of possible values of @source and @status fields
5336 # see "_OST (OSPM Status Indication)" chapter of ACPI5.0 spec.
5337 #
5338 # @device: #optional device ID associated with slot
5339 #
5340 # @slot: slot ID, unique per slot of a given @slot-type
5341 #
5342 # @slot-type: type of the slot
5343 #
5344 # @source: an integer containing the source event
5345 #
5346 # @status: an integer containing the status code
5347 #
5348 # Since: 2.1
5349 ##
5350 { 'struct': 'ACPIOSTInfo',
5351 'data' : { '*device': 'str',
5352 'slot': 'str',
5353 'slot-type': 'ACPISlotType',
5354 'source': 'int',
5355 'status': 'int' } }
5356
5357 ##
5358 # @query-acpi-ospm-status:
5359 #
5360 # Lists ACPI OSPM status of ACPI device objects,
5361 # which might be reported via _OST method
5362 #
5363 # Since: 2.1
5364 ##
5365 { 'command': 'query-acpi-ospm-status', 'returns': ['ACPIOSTInfo'] }
5366
5367 ##
5368 # @WatchdogExpirationAction:
5369 #
5370 # An enumeration of the actions taken when the watchdog device's timer is
5371 # expired
5372 #
5373 # @reset: system resets
5374 #
5375 # @shutdown: system shutdown, note that it is similar to @powerdown, which
5376 # tries to set to system status and notify guest
5377 #
5378 # @poweroff: system poweroff, the emulator program exits
5379 #
5380 # @pause: system pauses, similar to @stop
5381 #
5382 # @debug: system enters debug state
5383 #
5384 # @none: nothing is done
5385 #
5386 # @inject-nmi: a non-maskable interrupt is injected into the first VCPU (all
5387 # VCPUS on x86) (since 2.4)
5388 #
5389 # Since: 2.1
5390 ##
5391 { 'enum': 'WatchdogExpirationAction',
5392 'data': [ 'reset', 'shutdown', 'poweroff', 'pause', 'debug', 'none',
5393 'inject-nmi' ] }
5394
5395 ##
5396 # @IoOperationType:
5397 #
5398 # An enumeration of the I/O operation types
5399 #
5400 # @read: read operation
5401 #
5402 # @write: write operation
5403 #
5404 # Since: 2.1
5405 ##
5406 { 'enum': 'IoOperationType',
5407 'data': [ 'read', 'write' ] }
5408
5409 ##
5410 # @GuestPanicAction:
5411 #
5412 # An enumeration of the actions taken when guest OS panic is detected
5413 #
5414 # @pause: system pauses
5415 #
5416 # Since: 2.1 (poweroff since 2.8)
5417 ##
5418 { 'enum': 'GuestPanicAction',
5419 'data': [ 'pause', 'poweroff' ] }
5420
5421 ##
5422 # @rtc-reset-reinjection:
5423 #
5424 # This command will reset the RTC interrupt reinjection backlog.
5425 # Can be used if another mechanism to synchronize guest time
5426 # is in effect, for example QEMU guest agent's guest-set-time
5427 # command.
5428 #
5429 # Since: 2.1
5430 ##
5431 { 'command': 'rtc-reset-reinjection' }
5432
5433 # Rocker ethernet network switch
5434 { 'include': 'qapi/rocker.json' }
5435
5436 ##
5437 # @ReplayMode:
5438 #
5439 # Mode of the replay subsystem.
5440 #
5441 # @none: normal execution mode. Replay or record are not enabled.
5442 #
5443 # @record: record mode. All non-deterministic data is written into the
5444 # replay log.
5445 #
5446 # @play: replay mode. Non-deterministic data required for system execution
5447 # is read from the log.
5448 #
5449 # Since: 2.5
5450 ##
5451 { 'enum': 'ReplayMode',
5452 'data': [ 'none', 'record', 'play' ] }
5453
5454 ##
5455 # @xen-load-devices-state:
5456 #
5457 # Load the state of all devices from file. The RAM and the block devices
5458 # of the VM are not loaded by this command.
5459 #
5460 # @filename: the file to load the state of the devices from as binary
5461 # data. See xen-save-devices-state.txt for a description of the binary
5462 # format.
5463 #
5464 # Since: 2.7
5465 ##
5466 { 'command': 'xen-load-devices-state', 'data': {'filename': 'str'} }
5467
5468 ##
5469 # @GICCapability:
5470 #
5471 # The struct describes capability for a specific GIC (Generic
5472 # Interrupt Controller) version. These bits are not only decided by
5473 # QEMU/KVM software version, but also decided by the hardware that
5474 # the program is running upon.
5475 #
5476 # @version: version of GIC to be described. Currently, only 2 and 3
5477 # are supported.
5478 #
5479 # @emulated: whether current QEMU/hardware supports emulated GIC
5480 # device in user space.
5481 #
5482 # @kernel: whether current QEMU/hardware supports hardware
5483 # accelerated GIC device in kernel.
5484 #
5485 # Since: 2.6
5486 ##
5487 { 'struct': 'GICCapability',
5488 'data': { 'version': 'int',
5489 'emulated': 'bool',
5490 'kernel': 'bool' } }
5491
5492 ##
5493 # @query-gic-capabilities:
5494 #
5495 # This command is ARM-only. It will return a list of GICCapability
5496 # objects that describe its capability bits.
5497 #
5498 # Returns: a list of GICCapability objects.
5499 #
5500 # Since: 2.6
5501 ##
5502 { 'command': 'query-gic-capabilities', 'returns': ['GICCapability'] }
5503
5504 ##
5505 # @CpuInstanceProperties:
5506 #
5507 # List of properties to be used for hotplugging a CPU instance,
5508 # it should be passed by management with device_add command when
5509 # a CPU is being hotplugged.
5510 #
5511 # @node-id: #optional NUMA node ID the CPU belongs to
5512 # @socket-id: #optional socket number within node/board the CPU belongs to
5513 # @core-id: #optional core number within socket the CPU belongs to
5514 # @thread-id: #optional thread number within core the CPU belongs to
5515 #
5516 # Note: currently there are 4 properties that could be present
5517 # but management should be prepared to pass through other
5518 # properties with device_add command to allow for future
5519 # interface extension. This also requires the filed names to be kept in
5520 # sync with the properties passed to -device/device_add.
5521 #
5522 # Since: 2.7
5523 ##
5524 { 'struct': 'CpuInstanceProperties',
5525 'data': { '*node-id': 'int',
5526 '*socket-id': 'int',
5527 '*core-id': 'int',
5528 '*thread-id': 'int'
5529 }
5530 }
5531
5532 ##
5533 # @HotpluggableCPU:
5534 #
5535 # @type: CPU object type for usage with device_add command
5536 # @props: list of properties to be used for hotplugging CPU
5537 # @vcpus-count: number of logical VCPU threads @HotpluggableCPU provides
5538 # @qom-path: #optional link to existing CPU object if CPU is present or
5539 # omitted if CPU is not present.
5540 #
5541 # Since: 2.7
5542 ##
5543 { 'struct': 'HotpluggableCPU',
5544 'data': { 'type': 'str',
5545 'vcpus-count': 'int',
5546 'props': 'CpuInstanceProperties',
5547 '*qom-path': 'str'
5548 }
5549 }
5550
5551 ##
5552 # @query-hotpluggable-cpus:
5553 #
5554 # Returns: a list of HotpluggableCPU objects.
5555 #
5556 # Since: 2.7
5557 ##
5558 { 'command': 'query-hotpluggable-cpus', 'returns': ['HotpluggableCPU'] }