]> git.proxmox.com Git - mirror_qemu.git/blob - qapi-schema.json
qmp-commands: move 'query-spice' 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 # If the balloon driver is enabled but not functional because the KVM
1797 # kernel module cannot support it, KvmMissingCap
1798 # If no balloon device is present, DeviceNotActive
1799 #
1800 # Since: 0.14.0
1801 ##
1802 { 'command': 'query-balloon', 'returns': 'BalloonInfo' }
1803
1804 ##
1805 # @PciMemoryRange:
1806 #
1807 # A PCI device memory region
1808 #
1809 # @base: the starting address (guest physical)
1810 #
1811 # @limit: the ending address (guest physical)
1812 #
1813 # Since: 0.14.0
1814 ##
1815 { 'struct': 'PciMemoryRange', 'data': {'base': 'int', 'limit': 'int'} }
1816
1817 ##
1818 # @PciMemoryRegion:
1819 #
1820 # Information about a PCI device I/O region.
1821 #
1822 # @bar: the index of the Base Address Register for this region
1823 #
1824 # @type: 'io' if the region is a PIO region
1825 # 'memory' if the region is a MMIO region
1826 #
1827 # @prefetch: #optional if @type is 'memory', true if the memory is prefetchable
1828 #
1829 # @mem_type_64: #optional if @type is 'memory', true if the BAR is 64-bit
1830 #
1831 # Since: 0.14.0
1832 ##
1833 { 'struct': 'PciMemoryRegion',
1834 'data': {'bar': 'int', 'type': 'str', 'address': 'int', 'size': 'int',
1835 '*prefetch': 'bool', '*mem_type_64': 'bool' } }
1836
1837 ##
1838 # @PciBusInfo:
1839 #
1840 # Information about a bus of a PCI Bridge device
1841 #
1842 # @number: primary bus interface number. This should be the number of the
1843 # bus the device resides on.
1844 #
1845 # @secondary: secondary bus interface number. This is the number of the
1846 # main bus for the bridge
1847 #
1848 # @subordinate: This is the highest number bus that resides below the
1849 # bridge.
1850 #
1851 # @io_range: The PIO range for all devices on this bridge
1852 #
1853 # @memory_range: The MMIO range for all devices on this bridge
1854 #
1855 # @prefetchable_range: The range of prefetchable MMIO for all devices on
1856 # this bridge
1857 #
1858 # Since: 2.4
1859 ##
1860 { 'struct': 'PciBusInfo',
1861 'data': {'number': 'int', 'secondary': 'int', 'subordinate': 'int',
1862 'io_range': 'PciMemoryRange',
1863 'memory_range': 'PciMemoryRange',
1864 'prefetchable_range': 'PciMemoryRange' } }
1865
1866 ##
1867 # @PciBridgeInfo:
1868 #
1869 # Information about a PCI Bridge device
1870 #
1871 # @bus: information about the bus the device resides on
1872 #
1873 # @devices: a list of @PciDeviceInfo for each device on this bridge
1874 #
1875 # Since: 0.14.0
1876 ##
1877 { 'struct': 'PciBridgeInfo',
1878 'data': {'bus': 'PciBusInfo', '*devices': ['PciDeviceInfo']} }
1879
1880 ##
1881 # @PciDeviceClass:
1882 #
1883 # Information about the Class of a PCI device
1884 #
1885 # @desc: #optional a string description of the device's class
1886 #
1887 # @class: the class code of the device
1888 #
1889 # Since: 2.4
1890 ##
1891 { 'struct': 'PciDeviceClass',
1892 'data': {'*desc': 'str', 'class': 'int'} }
1893
1894 ##
1895 # @PciDeviceId:
1896 #
1897 # Information about the Id of a PCI device
1898 #
1899 # @device: the PCI device id
1900 #
1901 # @vendor: the PCI vendor id
1902 #
1903 # Since: 2.4
1904 ##
1905 { 'struct': 'PciDeviceId',
1906 'data': {'device': 'int', 'vendor': 'int'} }
1907
1908 ##
1909 # @PciDeviceInfo:
1910 #
1911 # Information about a PCI device
1912 #
1913 # @bus: the bus number of the device
1914 #
1915 # @slot: the slot the device is located in
1916 #
1917 # @function: the function of the slot used by the device
1918 #
1919 # @class_info: the class of the device
1920 #
1921 # @id: the PCI device id
1922 #
1923 # @irq: #optional if an IRQ is assigned to the device, the IRQ number
1924 #
1925 # @qdev_id: the device name of the PCI device
1926 #
1927 # @pci_bridge: if the device is a PCI bridge, the bridge information
1928 #
1929 # @regions: a list of the PCI I/O regions associated with the device
1930 #
1931 # Notes: the contents of @class_info.desc are not stable and should only be
1932 # treated as informational.
1933 #
1934 # Since: 0.14.0
1935 ##
1936 { 'struct': 'PciDeviceInfo',
1937 'data': {'bus': 'int', 'slot': 'int', 'function': 'int',
1938 'class_info': 'PciDeviceClass', 'id': 'PciDeviceId',
1939 '*irq': 'int', 'qdev_id': 'str', '*pci_bridge': 'PciBridgeInfo',
1940 'regions': ['PciMemoryRegion']} }
1941
1942 ##
1943 # @PciInfo:
1944 #
1945 # Information about a PCI bus
1946 #
1947 # @bus: the bus index
1948 #
1949 # @devices: a list of devices on this bus
1950 #
1951 # Since: 0.14.0
1952 ##
1953 { 'struct': 'PciInfo', 'data': {'bus': 'int', 'devices': ['PciDeviceInfo']} }
1954
1955 ##
1956 # @query-pci:
1957 #
1958 # Return information about the PCI bus topology of the guest.
1959 #
1960 # Returns: a list of @PciInfo for each PCI bus
1961 #
1962 # Since: 0.14.0
1963 ##
1964 { 'command': 'query-pci', 'returns': ['PciInfo'] }
1965
1966 ##
1967 # @quit:
1968 #
1969 # This command will cause the QEMU process to exit gracefully. While every
1970 # attempt is made to send the QMP response before terminating, this is not
1971 # guaranteed. When using this interface, a premature EOF would not be
1972 # unexpected.
1973 #
1974 # Since: 0.14.0
1975 ##
1976 { 'command': 'quit' }
1977
1978 ##
1979 # @stop:
1980 #
1981 # Stop all guest VCPU execution.
1982 #
1983 # Since: 0.14.0
1984 #
1985 # Notes: This function will succeed even if the guest is already in the stopped
1986 # state. In "inmigrate" state, it will ensure that the guest
1987 # remains paused once migration finishes, as if the -S option was
1988 # passed on the command line.
1989 ##
1990 { 'command': 'stop' }
1991
1992 ##
1993 # @system_reset:
1994 #
1995 # Performs a hard reset of a guest.
1996 #
1997 # Since: 0.14.0
1998 ##
1999 { 'command': 'system_reset' }
2000
2001 ##
2002 # @system_powerdown:
2003 #
2004 # Requests that a guest perform a powerdown operation.
2005 #
2006 # Since: 0.14.0
2007 #
2008 # Notes: A guest may or may not respond to this command. This command
2009 # returning does not indicate that a guest has accepted the request or
2010 # that it has shut down. Many guests will respond to this command by
2011 # prompting the user in some way.
2012 ##
2013 { 'command': 'system_powerdown' }
2014
2015 ##
2016 # @cpu:
2017 #
2018 # This command is a nop that is only provided for the purposes of compatibility.
2019 #
2020 # Since: 0.14.0
2021 #
2022 # Notes: Do not use this command.
2023 ##
2024 { 'command': 'cpu', 'data': {'index': 'int'} }
2025
2026 ##
2027 # @cpu-add:
2028 #
2029 # Adds CPU with specified ID
2030 #
2031 # @id: ID of CPU to be created, valid values [0..max_cpus)
2032 #
2033 # Returns: Nothing on success
2034 #
2035 # Since: 1.5
2036 ##
2037 { 'command': 'cpu-add', 'data': {'id': 'int'} }
2038
2039 ##
2040 # @memsave:
2041 #
2042 # Save a portion of guest memory to a file.
2043 #
2044 # @val: the virtual address of the guest to start from
2045 #
2046 # @size: the size of memory region to save
2047 #
2048 # @filename: the file to save the memory to as binary data
2049 #
2050 # @cpu-index: #optional the index of the virtual CPU to use for translating the
2051 # virtual address (defaults to CPU 0)
2052 #
2053 # Returns: Nothing on success
2054 #
2055 # Since: 0.14.0
2056 #
2057 # Notes: Errors were not reliably returned until 1.1
2058 ##
2059 { 'command': 'memsave',
2060 'data': {'val': 'int', 'size': 'int', 'filename': 'str', '*cpu-index': 'int'} }
2061
2062 ##
2063 # @pmemsave:
2064 #
2065 # Save a portion of guest physical memory to a file.
2066 #
2067 # @val: the physical address of the guest to start from
2068 #
2069 # @size: the size of memory region to save
2070 #
2071 # @filename: the file to save the memory to as binary data
2072 #
2073 # Returns: Nothing on success
2074 #
2075 # Since: 0.14.0
2076 #
2077 # Notes: Errors were not reliably returned until 1.1
2078 ##
2079 { 'command': 'pmemsave',
2080 'data': {'val': 'int', 'size': 'int', 'filename': 'str'} }
2081
2082 ##
2083 # @cont:
2084 #
2085 # Resume guest VCPU execution.
2086 #
2087 # Since: 0.14.0
2088 #
2089 # Returns: If successful, nothing
2090 # If QEMU was started with an encrypted block device and a key has
2091 # not yet been set, DeviceEncrypted.
2092 #
2093 # Notes: This command will succeed if the guest is currently running. It
2094 # will also succeed if the guest is in the "inmigrate" state; in
2095 # this case, the effect of the command is to make sure the guest
2096 # starts once migration finishes, removing the effect of the -S
2097 # command line option if it was passed.
2098 ##
2099 { 'command': 'cont' }
2100
2101 ##
2102 # @system_wakeup:
2103 #
2104 # Wakeup guest from suspend. Does nothing in case the guest isn't suspended.
2105 #
2106 # Since: 1.1
2107 #
2108 # Returns: nothing.
2109 ##
2110 { 'command': 'system_wakeup' }
2111
2112 ##
2113 # @inject-nmi:
2114 #
2115 # Injects a Non-Maskable Interrupt into the default CPU (x86/s390) or all CPUs (ppc64).
2116 #
2117 # Returns: If successful, nothing
2118 #
2119 # Since: 0.14.0
2120 #
2121 # Note: prior to 2.1, this command was only supported for x86 and s390 VMs
2122 ##
2123 { 'command': 'inject-nmi' }
2124
2125 ##
2126 # @set_link:
2127 #
2128 # Sets the link status of a virtual network adapter.
2129 #
2130 # @name: the device name of the virtual network adapter
2131 #
2132 # @up: true to set the link status to be up
2133 #
2134 # Returns: Nothing on success
2135 # If @name is not a valid network device, DeviceNotFound
2136 #
2137 # Since: 0.14.0
2138 #
2139 # Notes: Not all network adapters support setting link status. This command
2140 # will succeed even if the network adapter does not support link status
2141 # notification.
2142 ##
2143 { 'command': 'set_link', 'data': {'name': 'str', 'up': 'bool'} }
2144
2145 ##
2146 # @balloon:
2147 #
2148 # Request the balloon driver to change its balloon size.
2149 #
2150 # @value: the target size of the balloon in bytes
2151 #
2152 # Returns: Nothing on success
2153 # If the balloon driver is enabled but not functional because the KVM
2154 # kernel module cannot support it, KvmMissingCap
2155 # If no balloon device is present, DeviceNotActive
2156 #
2157 # Notes: This command just issues a request to the guest. When it returns,
2158 # the balloon size may not have changed. A guest can change the balloon
2159 # size independent of this command.
2160 #
2161 # Since: 0.14.0
2162 ##
2163 { 'command': 'balloon', 'data': {'value': 'int'} }
2164
2165 ##
2166 # @Abort:
2167 #
2168 # This action can be used to test transaction failure.
2169 #
2170 # Since: 1.6
2171 ##
2172 { 'struct': 'Abort',
2173 'data': { } }
2174
2175 ##
2176 # @ActionCompletionMode:
2177 #
2178 # An enumeration of Transactional completion modes.
2179 #
2180 # @individual: Do not attempt to cancel any other Actions if any Actions fail
2181 # after the Transaction request succeeds. All Actions that
2182 # can complete successfully will do so without waiting on others.
2183 # This is the default.
2184 #
2185 # @grouped: If any Action fails after the Transaction succeeds, cancel all
2186 # Actions. Actions do not complete until all Actions are ready to
2187 # complete. May be rejected by Actions that do not support this
2188 # completion mode.
2189 #
2190 # Since: 2.5
2191 ##
2192 { 'enum': 'ActionCompletionMode',
2193 'data': [ 'individual', 'grouped' ] }
2194
2195 ##
2196 # @TransactionAction:
2197 #
2198 # A discriminated record of operations that can be performed with
2199 # @transaction. Action @type can be:
2200 #
2201 # - @abort: since 1.6
2202 # - @block-dirty-bitmap-add: since 2.5
2203 # - @block-dirty-bitmap-clear: since 2.5
2204 # - @blockdev-backup: since 2.3
2205 # - @blockdev-snapshot: since 2.5
2206 # - @blockdev-snapshot-internal-sync: since 1.7
2207 # - @blockdev-snapshot-sync: since 1.1
2208 # - @drive-backup: since 1.6
2209 #
2210 # Since: 1.1
2211 ##
2212 { 'union': 'TransactionAction',
2213 'data': {
2214 'abort': 'Abort',
2215 'block-dirty-bitmap-add': 'BlockDirtyBitmapAdd',
2216 'block-dirty-bitmap-clear': 'BlockDirtyBitmap',
2217 'blockdev-backup': 'BlockdevBackup',
2218 'blockdev-snapshot': 'BlockdevSnapshot',
2219 'blockdev-snapshot-internal-sync': 'BlockdevSnapshotInternal',
2220 'blockdev-snapshot-sync': 'BlockdevSnapshotSync',
2221 'drive-backup': 'DriveBackup'
2222 } }
2223
2224 ##
2225 # @TransactionProperties:
2226 #
2227 # Optional arguments to modify the behavior of a Transaction.
2228 #
2229 # @completion-mode: #optional Controls how jobs launched asynchronously by
2230 # Actions will complete or fail as a group.
2231 # See @ActionCompletionMode for details.
2232 #
2233 # Since: 2.5
2234 ##
2235 { 'struct': 'TransactionProperties',
2236 'data': {
2237 '*completion-mode': 'ActionCompletionMode'
2238 }
2239 }
2240
2241 ##
2242 # @transaction:
2243 #
2244 # Executes a number of transactionable QMP commands atomically. If any
2245 # operation fails, then the entire set of actions will be abandoned and the
2246 # appropriate error returned.
2247 #
2248 # @actions: List of @TransactionAction;
2249 # information needed for the respective operations.
2250 #
2251 # @properties: #optional structure of additional options to control the
2252 # execution of the transaction. See @TransactionProperties
2253 # for additional detail.
2254 #
2255 # Returns: nothing on success
2256 # Errors depend on the operations of the transaction
2257 #
2258 # Note: The transaction aborts on the first failure. Therefore, there will be
2259 # information on only one failed operation returned in an error condition, and
2260 # subsequent actions will not have been attempted.
2261 #
2262 # Since: 1.1
2263 ##
2264 { 'command': 'transaction',
2265 'data': { 'actions': [ 'TransactionAction' ],
2266 '*properties': 'TransactionProperties'
2267 }
2268 }
2269
2270 ##
2271 # @human-monitor-command:
2272 #
2273 # Execute a command on the human monitor and return the output.
2274 #
2275 # @command-line: the command to execute in the human monitor
2276 #
2277 # @cpu-index: #optional The CPU to use for commands that require an implicit CPU
2278 #
2279 # Returns: the output of the command as a string
2280 #
2281 # Since: 0.14.0
2282 #
2283 # Notes: This command only exists as a stop-gap. Its use is highly
2284 # discouraged. The semantics of this command are not guaranteed.
2285 #
2286 # Known limitations:
2287 #
2288 # * This command is stateless, this means that commands that depend
2289 # on state information (such as getfd) might not work
2290 #
2291 # * Commands that prompt the user for data (eg. 'cont' when the block
2292 # device is encrypted) don't currently work
2293 ##
2294 { 'command': 'human-monitor-command',
2295 'data': {'command-line': 'str', '*cpu-index': 'int'},
2296 'returns': 'str' }
2297
2298 ##
2299 # @migrate_cancel:
2300 #
2301 # Cancel the current executing migration process.
2302 #
2303 # Returns: nothing on success
2304 #
2305 # Notes: This command succeeds even if there is no migration process running.
2306 #
2307 # Since: 0.14.0
2308 ##
2309 { 'command': 'migrate_cancel' }
2310
2311 ##
2312 # @migrate_set_downtime:
2313 #
2314 # Set maximum tolerated downtime for migration.
2315 #
2316 # @value: maximum downtime in seconds
2317 #
2318 # Returns: nothing on success
2319 #
2320 # Notes: This command is deprecated in favor of 'migrate-set-parameters'
2321 #
2322 # Since: 0.14.0
2323 ##
2324 { 'command': 'migrate_set_downtime', 'data': {'value': 'number'} }
2325
2326 ##
2327 # @migrate_set_speed:
2328 #
2329 # Set maximum speed for migration.
2330 #
2331 # @value: maximum speed in bytes.
2332 #
2333 # Returns: nothing on success
2334 #
2335 # Notes: This command is deprecated in favor of 'migrate-set-parameters'
2336 #
2337 # Since: 0.14.0
2338 ##
2339 { 'command': 'migrate_set_speed', 'data': {'value': 'int'} }
2340
2341 ##
2342 # @migrate-set-cache-size:
2343 #
2344 # Set XBZRLE cache size
2345 #
2346 # @value: cache size in bytes
2347 #
2348 # The size will be rounded down to the nearest power of 2.
2349 # The cache size can be modified before and during ongoing migration
2350 #
2351 # Returns: nothing on success
2352 #
2353 # Since: 1.2
2354 ##
2355 { 'command': 'migrate-set-cache-size', 'data': {'value': 'int'} }
2356
2357 ##
2358 # @query-migrate-cache-size:
2359 #
2360 # query XBZRLE cache size
2361 #
2362 # Returns: XBZRLE cache size in bytes
2363 #
2364 # Since: 1.2
2365 ##
2366 { 'command': 'query-migrate-cache-size', 'returns': 'int' }
2367
2368 ##
2369 # @ObjectPropertyInfo:
2370 #
2371 # @name: the name of the property
2372 #
2373 # @type: the type of the property. This will typically come in one of four
2374 # forms:
2375 #
2376 # 1) A primitive type such as 'u8', 'u16', 'bool', 'str', or 'double'.
2377 # These types are mapped to the appropriate JSON type.
2378 #
2379 # 2) A child type in the form 'child<subtype>' where subtype is a qdev
2380 # device type name. Child properties create the composition tree.
2381 #
2382 # 3) A link type in the form 'link<subtype>' where subtype is a qdev
2383 # device type name. Link properties form the device model graph.
2384 #
2385 # Since: 1.2
2386 ##
2387 { 'struct': 'ObjectPropertyInfo',
2388 'data': { 'name': 'str', 'type': 'str' } }
2389
2390 ##
2391 # @qom-list:
2392 #
2393 # This command will list any properties of a object given a path in the object
2394 # model.
2395 #
2396 # @path: the path within the object model. See @qom-get for a description of
2397 # this parameter.
2398 #
2399 # Returns: a list of @ObjectPropertyInfo that describe the properties of the
2400 # object.
2401 #
2402 # Since: 1.2
2403 ##
2404 { 'command': 'qom-list',
2405 'data': { 'path': 'str' },
2406 'returns': [ 'ObjectPropertyInfo' ] }
2407
2408 ##
2409 # @qom-get:
2410 #
2411 # This command will get a property from a object model path and return the
2412 # value.
2413 #
2414 # @path: The path within the object model. There are two forms of supported
2415 # paths--absolute and partial paths.
2416 #
2417 # Absolute paths are derived from the root object and can follow child<>
2418 # or link<> properties. Since they can follow link<> properties, they
2419 # can be arbitrarily long. Absolute paths look like absolute filenames
2420 # and are prefixed with a leading slash.
2421 #
2422 # Partial paths look like relative filenames. They do not begin
2423 # with a prefix. The matching rules for partial paths are subtle but
2424 # designed to make specifying objects easy. At each level of the
2425 # composition tree, the partial path is matched as an absolute path.
2426 # The first match is not returned. At least two matches are searched
2427 # for. A successful result is only returned if only one match is
2428 # found. If more than one match is found, a flag is return to
2429 # indicate that the match was ambiguous.
2430 #
2431 # @property: The property name to read
2432 #
2433 # Returns: The property value. The type depends on the property
2434 # type. child<> and link<> properties are returned as #str
2435 # pathnames. All integer property types (u8, u16, etc) are
2436 # returned as #int.
2437 #
2438 # Since: 1.2
2439 ##
2440 { 'command': 'qom-get',
2441 'data': { 'path': 'str', 'property': 'str' },
2442 'returns': 'any' }
2443
2444 ##
2445 # @qom-set:
2446 #
2447 # This command will set a property from a object model path.
2448 #
2449 # @path: see @qom-get for a description of this parameter
2450 #
2451 # @property: the property name to set
2452 #
2453 # @value: a value who's type is appropriate for the property type. See @qom-get
2454 # for a description of type mapping.
2455 #
2456 # Since: 1.2
2457 ##
2458 { 'command': 'qom-set',
2459 'data': { 'path': 'str', 'property': 'str', 'value': 'any' } }
2460
2461 ##
2462 # @set_password:
2463 #
2464 # Sets the password of a remote display session.
2465 #
2466 # @protocol: `vnc' to modify the VNC server password
2467 # `spice' to modify the Spice server password
2468 #
2469 # @password: the new password
2470 #
2471 # @connected: #optional how to handle existing clients when changing the
2472 # password. If nothing is specified, defaults to `keep'
2473 # `fail' to fail the command if clients are connected
2474 # `disconnect' to disconnect existing clients
2475 # `keep' to maintain existing clients
2476 #
2477 # Returns: Nothing on success
2478 # If Spice is not enabled, DeviceNotFound
2479 #
2480 # Since: 0.14.0
2481 ##
2482 { 'command': 'set_password',
2483 'data': {'protocol': 'str', 'password': 'str', '*connected': 'str'} }
2484
2485 ##
2486 # @expire_password:
2487 #
2488 # Expire the password of a remote display server.
2489 #
2490 # @protocol: the name of the remote display protocol `vnc' or `spice'
2491 #
2492 # @time: when to expire the password.
2493 # `now' to expire the password immediately
2494 # `never' to cancel password expiration
2495 # `+INT' where INT is the number of seconds from now (integer)
2496 # `INT' where INT is the absolute time in seconds
2497 #
2498 # Returns: Nothing on success
2499 # If @protocol is `spice' and Spice is not active, DeviceNotFound
2500 #
2501 # Since: 0.14.0
2502 #
2503 # Notes: Time is relative to the server and currently there is no way to
2504 # coordinate server time with client time. It is not recommended to
2505 # use the absolute time version of the @time parameter unless you're
2506 # sure you are on the same machine as the QEMU instance.
2507 ##
2508 { 'command': 'expire_password', 'data': {'protocol': 'str', 'time': 'str'} }
2509
2510 ##
2511 # @change-vnc-password:
2512 #
2513 # Change the VNC server password.
2514 #
2515 # @password: the new password to use with VNC authentication
2516 #
2517 # Since: 1.1
2518 #
2519 # Notes: An empty password in this command will set the password to the empty
2520 # string. Existing clients are unaffected by executing this command.
2521 ##
2522 { 'command': 'change-vnc-password', 'data': {'password': 'str'} }
2523
2524 ##
2525 # @change:
2526 #
2527 # This command is multiple commands multiplexed together.
2528 #
2529 # @device: This is normally the name of a block device but it may also be 'vnc'.
2530 # when it's 'vnc', then sub command depends on @target
2531 #
2532 # @target: If @device is a block device, then this is the new filename.
2533 # If @device is 'vnc', then if the value 'password' selects the vnc
2534 # change password command. Otherwise, this specifies a new server URI
2535 # address to listen to for VNC connections.
2536 #
2537 # @arg: If @device is a block device, then this is an optional format to open
2538 # the device with.
2539 # If @device is 'vnc' and @target is 'password', this is the new VNC
2540 # password to set. If this argument is an empty string, then no future
2541 # logins will be allowed.
2542 #
2543 # Returns: Nothing on success.
2544 # If @device is not a valid block device, DeviceNotFound
2545 # If the new block device is encrypted, DeviceEncrypted. Note that
2546 # if this error is returned, the device has been opened successfully
2547 # and an additional call to @block_passwd is required to set the
2548 # device's password. The behavior of reads and writes to the block
2549 # device between when these calls are executed is undefined.
2550 #
2551 # Notes: This interface is deprecated, and it is strongly recommended that you
2552 # avoid using it. For changing block devices, use
2553 # blockdev-change-medium; for changing VNC parameters, use
2554 # change-vnc-password.
2555 #
2556 # Since: 0.14.0
2557 ##
2558 { 'command': 'change',
2559 'data': {'device': 'str', 'target': 'str', '*arg': 'str'} }
2560
2561 ##
2562 # @ObjectTypeInfo:
2563 #
2564 # This structure describes a search result from @qom-list-types
2565 #
2566 # @name: the type name found in the search
2567 #
2568 # Since: 1.1
2569 #
2570 # Notes: This command is experimental and may change syntax in future releases.
2571 ##
2572 { 'struct': 'ObjectTypeInfo',
2573 'data': { 'name': 'str' } }
2574
2575 ##
2576 # @qom-list-types:
2577 #
2578 # This command will return a list of types given search parameters
2579 #
2580 # @implements: if specified, only return types that implement this type name
2581 #
2582 # @abstract: if true, include abstract types in the results
2583 #
2584 # Returns: a list of @ObjectTypeInfo or an empty list if no results are found
2585 #
2586 # Since: 1.1
2587 ##
2588 { 'command': 'qom-list-types',
2589 'data': { '*implements': 'str', '*abstract': 'bool' },
2590 'returns': [ 'ObjectTypeInfo' ] }
2591
2592 ##
2593 # @DevicePropertyInfo:
2594 #
2595 # Information about device properties.
2596 #
2597 # @name: the name of the property
2598 # @type: the typename of the property
2599 # @description: #optional if specified, the description of the property.
2600 # (since 2.2)
2601 #
2602 # Since: 1.2
2603 ##
2604 { 'struct': 'DevicePropertyInfo',
2605 'data': { 'name': 'str', 'type': 'str', '*description': 'str' } }
2606
2607 ##
2608 # @device-list-properties:
2609 #
2610 # List properties associated with a device.
2611 #
2612 # @typename: the type name of a device
2613 #
2614 # Returns: a list of DevicePropertyInfo describing a devices properties
2615 #
2616 # Since: 1.2
2617 ##
2618 { 'command': 'device-list-properties',
2619 'data': { 'typename': 'str'},
2620 'returns': [ 'DevicePropertyInfo' ] }
2621
2622 ##
2623 # @migrate:
2624 #
2625 # Migrates the current running guest to another Virtual Machine.
2626 #
2627 # @uri: the Uniform Resource Identifier of the destination VM
2628 #
2629 # @blk: #optional do block migration (full disk copy)
2630 #
2631 # @inc: #optional incremental disk copy migration
2632 #
2633 # @detach: this argument exists only for compatibility reasons and
2634 # is ignored by QEMU
2635 #
2636 # Returns: nothing on success
2637 #
2638 # Since: 0.14.0
2639 ##
2640 { 'command': 'migrate',
2641 'data': {'uri': 'str', '*blk': 'bool', '*inc': 'bool', '*detach': 'bool' } }
2642
2643 ##
2644 # @migrate-incoming:
2645 #
2646 # Start an incoming migration, the qemu must have been started
2647 # with -incoming defer
2648 #
2649 # @uri: The Uniform Resource Identifier identifying the source or
2650 # address to listen on
2651 #
2652 # Returns: nothing on success
2653 #
2654 # Since: 2.3
2655 # Note: It's a bad idea to use a string for the uri, but it needs to stay
2656 # compatible with -incoming and the format of the uri is already exposed
2657 # above libvirt
2658 ##
2659 { 'command': 'migrate-incoming', 'data': {'uri': 'str' } }
2660
2661 ##
2662 # @xen-save-devices-state:
2663 #
2664 # Save the state of all devices to file. The RAM and the block devices
2665 # of the VM are not saved by this command.
2666 #
2667 # @filename: the file to save the state of the devices to as binary
2668 # data. See xen-save-devices-state.txt for a description of the binary
2669 # format.
2670 #
2671 # Returns: Nothing on success
2672 #
2673 # Since: 1.1
2674 ##
2675 { 'command': 'xen-save-devices-state', 'data': {'filename': 'str'} }
2676
2677 ##
2678 # @xen-set-global-dirty-log:
2679 #
2680 # Enable or disable the global dirty log mode.
2681 #
2682 # @enable: true to enable, false to disable.
2683 #
2684 # Returns: nothing
2685 #
2686 # Since: 1.3
2687 ##
2688 { 'command': 'xen-set-global-dirty-log', 'data': { 'enable': 'bool' } }
2689
2690 ##
2691 # @device_add:
2692 #
2693 # @driver: the name of the new device's driver
2694 #
2695 # @bus: #optional the device's parent bus (device tree path)
2696 #
2697 # @id: #optional the device's ID, must be unique
2698 #
2699 # Additional arguments depend on the type.
2700 #
2701 # Add a device.
2702 #
2703 # Notes:
2704 # 1. For detailed information about this command, please refer to the
2705 # 'docs/qdev-device-use.txt' file.
2706 #
2707 # 2. It's possible to list device properties by running QEMU with the
2708 # "-device DEVICE,help" command-line argument, where DEVICE is the
2709 # device's name
2710 #
2711 # Example:
2712 #
2713 # -> { "execute": "device_add",
2714 # "arguments": { "driver": "e1000", "id": "net1",
2715 # "bus": "pci.0",
2716 # "mac": "52:54:00:12:34:56" } }
2717 # <- { "return": {} }
2718 #
2719 # TODO: This command effectively bypasses QAPI completely due to its
2720 # "additional arguments" business. It shouldn't have been added to
2721 # the schema in this form. It should be qapified properly, or
2722 # replaced by a properly qapified command.
2723 #
2724 # Since: 0.13
2725 ##
2726 { 'command': 'device_add',
2727 'data': {'driver': 'str', '*bus': 'str', '*id': 'str'},
2728 'gen': false } # so we can get the additional arguments
2729
2730 ##
2731 # @device_del:
2732 #
2733 # Remove a device from a guest
2734 #
2735 # @id: the name or QOM path of the device
2736 #
2737 # Returns: Nothing on success
2738 # If @id is not a valid device, DeviceNotFound
2739 #
2740 # Notes: When this command completes, the device may not be removed from the
2741 # guest. Hot removal is an operation that requires guest cooperation.
2742 # This command merely requests that the guest begin the hot removal
2743 # process. Completion of the device removal process is signaled with a
2744 # DEVICE_DELETED event. Guest reset will automatically complete removal
2745 # for all devices.
2746 #
2747 # Since: 0.14.0
2748 ##
2749 { 'command': 'device_del', 'data': {'id': 'str'} }
2750
2751 ##
2752 # @DumpGuestMemoryFormat:
2753 #
2754 # An enumeration of guest-memory-dump's format.
2755 #
2756 # @elf: elf format
2757 #
2758 # @kdump-zlib: kdump-compressed format with zlib-compressed
2759 #
2760 # @kdump-lzo: kdump-compressed format with lzo-compressed
2761 #
2762 # @kdump-snappy: kdump-compressed format with snappy-compressed
2763 #
2764 # Since: 2.0
2765 ##
2766 { 'enum': 'DumpGuestMemoryFormat',
2767 'data': [ 'elf', 'kdump-zlib', 'kdump-lzo', 'kdump-snappy' ] }
2768
2769 ##
2770 # @dump-guest-memory:
2771 #
2772 # Dump guest's memory to vmcore. It is a synchronous operation that can take
2773 # very long depending on the amount of guest memory.
2774 #
2775 # @paging: if true, do paging to get guest's memory mapping. This allows
2776 # using gdb to process the core file.
2777 #
2778 # IMPORTANT: this option can make QEMU allocate several gigabytes
2779 # of RAM. This can happen for a large guest, or a
2780 # malicious guest pretending to be large.
2781 #
2782 # Also, paging=true has the following limitations:
2783 #
2784 # 1. The guest may be in a catastrophic state or can have corrupted
2785 # memory, which cannot be trusted
2786 # 2. The guest can be in real-mode even if paging is enabled. For
2787 # example, the guest uses ACPI to sleep, and ACPI sleep state
2788 # goes in real-mode
2789 # 3. Currently only supported on i386 and x86_64.
2790 #
2791 # @protocol: the filename or file descriptor of the vmcore. The supported
2792 # protocols are:
2793 #
2794 # 1. file: the protocol starts with "file:", and the following
2795 # string is the file's path.
2796 # 2. fd: the protocol starts with "fd:", and the following string
2797 # is the fd's name.
2798 #
2799 # @detach: #optional if true, QMP will return immediately rather than
2800 # waiting for the dump to finish. The user can track progress
2801 # using "query-dump". (since 2.6).
2802 #
2803 # @begin: #optional if specified, the starting physical address.
2804 #
2805 # @length: #optional if specified, the memory size, in bytes. If you don't
2806 # want to dump all guest's memory, please specify the start @begin
2807 # and @length
2808 #
2809 # @format: #optional if specified, the format of guest memory dump. But non-elf
2810 # format is conflict with paging and filter, ie. @paging, @begin and
2811 # @length is not allowed to be specified with non-elf @format at the
2812 # same time (since 2.0)
2813 #
2814 # Returns: nothing on success
2815 #
2816 # Since: 1.2
2817 ##
2818 { 'command': 'dump-guest-memory',
2819 'data': { 'paging': 'bool', 'protocol': 'str', '*detach': 'bool',
2820 '*begin': 'int', '*length': 'int',
2821 '*format': 'DumpGuestMemoryFormat'} }
2822
2823 ##
2824 # @DumpStatus:
2825 #
2826 # Describe the status of a long-running background guest memory dump.
2827 #
2828 # @none: no dump-guest-memory has started yet.
2829 #
2830 # @active: there is one dump running in background.
2831 #
2832 # @completed: the last dump has finished successfully.
2833 #
2834 # @failed: the last dump has failed.
2835 #
2836 # Since: 2.6
2837 ##
2838 { 'enum': 'DumpStatus',
2839 'data': [ 'none', 'active', 'completed', 'failed' ] }
2840
2841 ##
2842 # @DumpQueryResult:
2843 #
2844 # The result format for 'query-dump'.
2845 #
2846 # @status: enum of @DumpStatus, which shows current dump status
2847 #
2848 # @completed: bytes written in latest dump (uncompressed)
2849 #
2850 # @total: total bytes to be written in latest dump (uncompressed)
2851 #
2852 # Since: 2.6
2853 ##
2854 { 'struct': 'DumpQueryResult',
2855 'data': { 'status': 'DumpStatus',
2856 'completed': 'int',
2857 'total': 'int' } }
2858
2859 ##
2860 # @query-dump:
2861 #
2862 # Query latest dump status.
2863 #
2864 # Returns: A @DumpStatus object showing the dump status.
2865 #
2866 # Since: 2.6
2867 ##
2868 { 'command': 'query-dump', 'returns': 'DumpQueryResult' }
2869
2870 ##
2871 # @DumpGuestMemoryCapability:
2872 #
2873 # A list of the available formats for dump-guest-memory
2874 #
2875 # Since: 2.0
2876 ##
2877 { 'struct': 'DumpGuestMemoryCapability',
2878 'data': {
2879 'formats': ['DumpGuestMemoryFormat'] } }
2880
2881 ##
2882 # @query-dump-guest-memory-capability:
2883 #
2884 # Returns the available formats for dump-guest-memory
2885 #
2886 # Returns: A @DumpGuestMemoryCapability object listing available formats for
2887 # dump-guest-memory
2888 #
2889 # Since: 2.0
2890 ##
2891 { 'command': 'query-dump-guest-memory-capability',
2892 'returns': 'DumpGuestMemoryCapability' }
2893
2894 ##
2895 # @dump-skeys:
2896 #
2897 # Dump guest's storage keys
2898 #
2899 # @filename: the path to the file to dump to
2900 #
2901 # This command is only supported on s390 architecture.
2902 #
2903 # Since: 2.5
2904 ##
2905 { 'command': 'dump-skeys',
2906 'data': { 'filename': 'str' } }
2907
2908 ##
2909 # @netdev_add:
2910 #
2911 # Add a network backend.
2912 #
2913 # @type: the type of network backend. Current valid values are 'user', 'tap',
2914 # 'vde', 'socket', 'dump' and 'bridge'
2915 #
2916 # @id: the name of the new network backend
2917 #
2918 # Additional arguments depend on the type.
2919 #
2920 # TODO: This command effectively bypasses QAPI completely due to its
2921 # "additional arguments" business. It shouldn't have been added to
2922 # the schema in this form. It should be qapified properly, or
2923 # replaced by a properly qapified command.
2924 #
2925 # Since: 0.14.0
2926 #
2927 # Returns: Nothing on success
2928 # If @type is not a valid network backend, DeviceNotFound
2929 ##
2930 { 'command': 'netdev_add',
2931 'data': {'type': 'str', 'id': 'str'},
2932 'gen': false } # so we can get the additional arguments
2933
2934 ##
2935 # @netdev_del:
2936 #
2937 # Remove a network backend.
2938 #
2939 # @id: the name of the network backend to remove
2940 #
2941 # Returns: Nothing on success
2942 # If @id is not a valid network backend, DeviceNotFound
2943 #
2944 # Since: 0.14.0
2945 ##
2946 { 'command': 'netdev_del', 'data': {'id': 'str'} }
2947
2948 ##
2949 # @object-add:
2950 #
2951 # Create a QOM object.
2952 #
2953 # @qom-type: the class name for the object to be created
2954 #
2955 # @id: the name of the new object
2956 #
2957 # @props: #optional a dictionary of properties to be passed to the backend
2958 #
2959 # Returns: Nothing on success
2960 # Error if @qom-type is not a valid class name
2961 #
2962 # Since: 2.0
2963 ##
2964 { 'command': 'object-add',
2965 'data': {'qom-type': 'str', 'id': 'str', '*props': 'any'} }
2966
2967 ##
2968 # @object-del:
2969 #
2970 # Remove a QOM object.
2971 #
2972 # @id: the name of the QOM object to remove
2973 #
2974 # Returns: Nothing on success
2975 # Error if @id is not a valid id for a QOM object
2976 #
2977 # Since: 2.0
2978 ##
2979 { 'command': 'object-del', 'data': {'id': 'str'} }
2980
2981 ##
2982 # @NetdevNoneOptions:
2983 #
2984 # Use it alone to have zero network devices.
2985 #
2986 # Since: 1.2
2987 ##
2988 { 'struct': 'NetdevNoneOptions',
2989 'data': { } }
2990
2991 ##
2992 # @NetLegacyNicOptions:
2993 #
2994 # Create a new Network Interface Card.
2995 #
2996 # @netdev: #optional id of -netdev to connect to
2997 #
2998 # @macaddr: #optional MAC address
2999 #
3000 # @model: #optional device model (e1000, rtl8139, virtio etc.)
3001 #
3002 # @addr: #optional PCI device address
3003 #
3004 # @vectors: #optional number of MSI-x vectors, 0 to disable MSI-X
3005 #
3006 # Since: 1.2
3007 ##
3008 { 'struct': 'NetLegacyNicOptions',
3009 'data': {
3010 '*netdev': 'str',
3011 '*macaddr': 'str',
3012 '*model': 'str',
3013 '*addr': 'str',
3014 '*vectors': 'uint32' } }
3015
3016 ##
3017 # @String:
3018 #
3019 # A fat type wrapping 'str', to be embedded in lists.
3020 #
3021 # Since: 1.2
3022 ##
3023 { 'struct': 'String',
3024 'data': {
3025 'str': 'str' } }
3026
3027 ##
3028 # @NetdevUserOptions:
3029 #
3030 # Use the user mode network stack which requires no administrator privilege to
3031 # run.
3032 #
3033 # @hostname: #optional client hostname reported by the builtin DHCP server
3034 #
3035 # @restrict: #optional isolate the guest from the host
3036 #
3037 # @ipv4: #optional whether to support IPv4, default true for enabled
3038 # (since 2.6)
3039 #
3040 # @ipv6: #optional whether to support IPv6, default true for enabled
3041 # (since 2.6)
3042 #
3043 # @ip: #optional legacy parameter, use net= instead
3044 #
3045 # @net: #optional IP network address that the guest will see, in the
3046 # form addr[/netmask] The netmask is optional, and can be
3047 # either in the form a.b.c.d or as a number of valid top-most
3048 # bits. Default is 10.0.2.0/24.
3049 #
3050 # @host: #optional guest-visible address of the host
3051 #
3052 # @tftp: #optional root directory of the built-in TFTP server
3053 #
3054 # @bootfile: #optional BOOTP filename, for use with tftp=
3055 #
3056 # @dhcpstart: #optional the first of the 16 IPs the built-in DHCP server can
3057 # assign
3058 #
3059 # @dns: #optional guest-visible address of the virtual nameserver
3060 #
3061 # @dnssearch: #optional list of DNS suffixes to search, passed as DHCP option
3062 # to the guest
3063 #
3064 # @ipv6-prefix: #optional IPv6 network prefix (default is fec0::) (since
3065 # 2.6). The network prefix is given in the usual
3066 # hexadecimal IPv6 address notation.
3067 #
3068 # @ipv6-prefixlen: #optional IPv6 network prefix length (default is 64)
3069 # (since 2.6)
3070 #
3071 # @ipv6-host: #optional guest-visible IPv6 address of the host (since 2.6)
3072 #
3073 # @ipv6-dns: #optional guest-visible IPv6 address of the virtual
3074 # nameserver (since 2.6)
3075 #
3076 # @smb: #optional root directory of the built-in SMB server
3077 #
3078 # @smbserver: #optional IP address of the built-in SMB server
3079 #
3080 # @hostfwd: #optional redirect incoming TCP or UDP host connections to guest
3081 # endpoints
3082 #
3083 # @guestfwd: #optional forward guest TCP connections
3084 #
3085 # Since: 1.2
3086 ##
3087 { 'struct': 'NetdevUserOptions',
3088 'data': {
3089 '*hostname': 'str',
3090 '*restrict': 'bool',
3091 '*ipv4': 'bool',
3092 '*ipv6': 'bool',
3093 '*ip': 'str',
3094 '*net': 'str',
3095 '*host': 'str',
3096 '*tftp': 'str',
3097 '*bootfile': 'str',
3098 '*dhcpstart': 'str',
3099 '*dns': 'str',
3100 '*dnssearch': ['String'],
3101 '*ipv6-prefix': 'str',
3102 '*ipv6-prefixlen': 'int',
3103 '*ipv6-host': 'str',
3104 '*ipv6-dns': 'str',
3105 '*smb': 'str',
3106 '*smbserver': 'str',
3107 '*hostfwd': ['String'],
3108 '*guestfwd': ['String'] } }
3109
3110 ##
3111 # @NetdevTapOptions:
3112 #
3113 # Connect the host TAP network interface name to the VLAN.
3114 #
3115 # @ifname: #optional interface name
3116 #
3117 # @fd: #optional file descriptor of an already opened tap
3118 #
3119 # @fds: #optional multiple file descriptors of already opened multiqueue capable
3120 # tap
3121 #
3122 # @script: #optional script to initialize the interface
3123 #
3124 # @downscript: #optional script to shut down the interface
3125 #
3126 # @br: #optional bridge name (since 2.8)
3127 #
3128 # @helper: #optional command to execute to configure bridge
3129 #
3130 # @sndbuf: #optional send buffer limit. Understands [TGMKkb] suffixes.
3131 #
3132 # @vnet_hdr: #optional enable the IFF_VNET_HDR flag on the tap interface
3133 #
3134 # @vhost: #optional enable vhost-net network accelerator
3135 #
3136 # @vhostfd: #optional file descriptor of an already opened vhost net device
3137 #
3138 # @vhostfds: #optional file descriptors of multiple already opened vhost net
3139 # devices
3140 #
3141 # @vhostforce: #optional vhost on for non-MSIX virtio guests
3142 #
3143 # @queues: #optional number of queues to be created for multiqueue capable tap
3144 #
3145 # @poll-us: #optional maximum number of microseconds that could
3146 # be spent on busy polling for tap (since 2.7)
3147 #
3148 # Since: 1.2
3149 ##
3150 { 'struct': 'NetdevTapOptions',
3151 'data': {
3152 '*ifname': 'str',
3153 '*fd': 'str',
3154 '*fds': 'str',
3155 '*script': 'str',
3156 '*downscript': 'str',
3157 '*br': 'str',
3158 '*helper': 'str',
3159 '*sndbuf': 'size',
3160 '*vnet_hdr': 'bool',
3161 '*vhost': 'bool',
3162 '*vhostfd': 'str',
3163 '*vhostfds': 'str',
3164 '*vhostforce': 'bool',
3165 '*queues': 'uint32',
3166 '*poll-us': 'uint32'} }
3167
3168 ##
3169 # @NetdevSocketOptions:
3170 #
3171 # Connect the VLAN to a remote VLAN in another QEMU virtual machine using a TCP
3172 # socket connection.
3173 #
3174 # @fd: #optional file descriptor of an already opened socket
3175 #
3176 # @listen: #optional port number, and optional hostname, to listen on
3177 #
3178 # @connect: #optional port number, and optional hostname, to connect to
3179 #
3180 # @mcast: #optional UDP multicast address and port number
3181 #
3182 # @localaddr: #optional source address and port for multicast and udp packets
3183 #
3184 # @udp: #optional UDP unicast address and port number
3185 #
3186 # Since: 1.2
3187 ##
3188 { 'struct': 'NetdevSocketOptions',
3189 'data': {
3190 '*fd': 'str',
3191 '*listen': 'str',
3192 '*connect': 'str',
3193 '*mcast': 'str',
3194 '*localaddr': 'str',
3195 '*udp': 'str' } }
3196
3197 ##
3198 # @NetdevL2TPv3Options:
3199 #
3200 # Connect the VLAN to Ethernet over L2TPv3 Static tunnel
3201 #
3202 # @src: source address
3203 #
3204 # @dst: destination address
3205 #
3206 # @srcport: #optional source port - mandatory for udp, optional for ip
3207 #
3208 # @dstport: #optional destination port - mandatory for udp, optional for ip
3209 #
3210 # @ipv6: #optional - force the use of ipv6
3211 #
3212 # @udp: #optional - use the udp version of l2tpv3 encapsulation
3213 #
3214 # @cookie64: #optional - use 64 bit coookies
3215 #
3216 # @counter: #optional have sequence counter
3217 #
3218 # @pincounter: #optional pin sequence counter to zero -
3219 # workaround for buggy implementations or
3220 # networks with packet reorder
3221 #
3222 # @txcookie: #optional 32 or 64 bit transmit cookie
3223 #
3224 # @rxcookie: #optional 32 or 64 bit receive cookie
3225 #
3226 # @txsession: 32 bit transmit session
3227 #
3228 # @rxsession: #optional 32 bit receive session - if not specified
3229 # set to the same value as transmit
3230 #
3231 # @offset: #optional additional offset - allows the insertion of
3232 # additional application-specific data before the packet payload
3233 #
3234 # Since: 2.1
3235 ##
3236 { 'struct': 'NetdevL2TPv3Options',
3237 'data': {
3238 'src': 'str',
3239 'dst': 'str',
3240 '*srcport': 'str',
3241 '*dstport': 'str',
3242 '*ipv6': 'bool',
3243 '*udp': 'bool',
3244 '*cookie64': 'bool',
3245 '*counter': 'bool',
3246 '*pincounter': 'bool',
3247 '*txcookie': 'uint64',
3248 '*rxcookie': 'uint64',
3249 'txsession': 'uint32',
3250 '*rxsession': 'uint32',
3251 '*offset': 'uint32' } }
3252
3253 ##
3254 # @NetdevVdeOptions:
3255 #
3256 # Connect the VLAN to a vde switch running on the host.
3257 #
3258 # @sock: #optional socket path
3259 #
3260 # @port: #optional port number
3261 #
3262 # @group: #optional group owner of socket
3263 #
3264 # @mode: #optional permissions for socket
3265 #
3266 # Since: 1.2
3267 ##
3268 { 'struct': 'NetdevVdeOptions',
3269 'data': {
3270 '*sock': 'str',
3271 '*port': 'uint16',
3272 '*group': 'str',
3273 '*mode': 'uint16' } }
3274
3275 ##
3276 # @NetdevDumpOptions:
3277 #
3278 # Dump VLAN network traffic to a file.
3279 #
3280 # @len: #optional per-packet size limit (64k default). Understands [TGMKkb]
3281 # suffixes.
3282 #
3283 # @file: #optional dump file path (default is qemu-vlan0.pcap)
3284 #
3285 # Since: 1.2
3286 ##
3287 { 'struct': 'NetdevDumpOptions',
3288 'data': {
3289 '*len': 'size',
3290 '*file': 'str' } }
3291
3292 ##
3293 # @NetdevBridgeOptions:
3294 #
3295 # Connect a host TAP network interface to a host bridge device.
3296 #
3297 # @br: #optional bridge name
3298 #
3299 # @helper: #optional command to execute to configure bridge
3300 #
3301 # Since: 1.2
3302 ##
3303 { 'struct': 'NetdevBridgeOptions',
3304 'data': {
3305 '*br': 'str',
3306 '*helper': 'str' } }
3307
3308 ##
3309 # @NetdevHubPortOptions:
3310 #
3311 # Connect two or more net clients through a software hub.
3312 #
3313 # @hubid: hub identifier number
3314 #
3315 # Since: 1.2
3316 ##
3317 { 'struct': 'NetdevHubPortOptions',
3318 'data': {
3319 'hubid': 'int32' } }
3320
3321 ##
3322 # @NetdevNetmapOptions:
3323 #
3324 # Connect a client to a netmap-enabled NIC or to a VALE switch port
3325 #
3326 # @ifname: Either the name of an existing network interface supported by
3327 # netmap, or the name of a VALE port (created on the fly).
3328 # A VALE port name is in the form 'valeXXX:YYY', where XXX and
3329 # YYY are non-negative integers. XXX identifies a switch and
3330 # YYY identifies a port of the switch. VALE ports having the
3331 # same XXX are therefore connected to the same switch.
3332 #
3333 # @devname: #optional path of the netmap device (default: '/dev/netmap').
3334 #
3335 # Since: 2.0
3336 ##
3337 { 'struct': 'NetdevNetmapOptions',
3338 'data': {
3339 'ifname': 'str',
3340 '*devname': 'str' } }
3341
3342 ##
3343 # @NetdevVhostUserOptions:
3344 #
3345 # Vhost-user network backend
3346 #
3347 # @chardev: name of a unix socket chardev
3348 #
3349 # @vhostforce: #optional vhost on for non-MSIX virtio guests (default: false).
3350 #
3351 # @queues: #optional number of queues to be created for multiqueue vhost-user
3352 # (default: 1) (Since 2.5)
3353 #
3354 # Since: 2.1
3355 ##
3356 { 'struct': 'NetdevVhostUserOptions',
3357 'data': {
3358 'chardev': 'str',
3359 '*vhostforce': 'bool',
3360 '*queues': 'int' } }
3361
3362 ##
3363 # @NetClientDriver:
3364 #
3365 # Available netdev drivers.
3366 #
3367 # Since: 2.7
3368 ##
3369 { 'enum': 'NetClientDriver',
3370 'data': [ 'none', 'nic', 'user', 'tap', 'l2tpv3', 'socket', 'vde', 'dump',
3371 'bridge', 'hubport', 'netmap', 'vhost-user' ] }
3372
3373 ##
3374 # @Netdev:
3375 #
3376 # Captures the configuration of a network device.
3377 #
3378 # @id: identifier for monitor commands.
3379 #
3380 # @type: Specify the driver used for interpreting remaining arguments.
3381 #
3382 # Since: 1.2
3383 #
3384 # 'l2tpv3' - since 2.1
3385 ##
3386 { 'union': 'Netdev',
3387 'base': { 'id': 'str', 'type': 'NetClientDriver' },
3388 'discriminator': 'type',
3389 'data': {
3390 'none': 'NetdevNoneOptions',
3391 'nic': 'NetLegacyNicOptions',
3392 'user': 'NetdevUserOptions',
3393 'tap': 'NetdevTapOptions',
3394 'l2tpv3': 'NetdevL2TPv3Options',
3395 'socket': 'NetdevSocketOptions',
3396 'vde': 'NetdevVdeOptions',
3397 'dump': 'NetdevDumpOptions',
3398 'bridge': 'NetdevBridgeOptions',
3399 'hubport': 'NetdevHubPortOptions',
3400 'netmap': 'NetdevNetmapOptions',
3401 'vhost-user': 'NetdevVhostUserOptions' } }
3402
3403 ##
3404 # @NetLegacy:
3405 #
3406 # Captures the configuration of a network device; legacy.
3407 #
3408 # @vlan: #optional vlan number
3409 #
3410 # @id: #optional identifier for monitor commands
3411 #
3412 # @name: #optional identifier for monitor commands, ignored if @id is present
3413 #
3414 # @opts: device type specific properties (legacy)
3415 #
3416 # Since: 1.2
3417 ##
3418 { 'struct': 'NetLegacy',
3419 'data': {
3420 '*vlan': 'int32',
3421 '*id': 'str',
3422 '*name': 'str',
3423 'opts': 'NetLegacyOptions' } }
3424
3425 ##
3426 # @NetLegacyOptions:
3427 #
3428 # Like Netdev, but for use only by the legacy command line options
3429 #
3430 # Since: 1.2
3431 ##
3432 { 'union': 'NetLegacyOptions',
3433 'data': {
3434 'none': 'NetdevNoneOptions',
3435 'nic': 'NetLegacyNicOptions',
3436 'user': 'NetdevUserOptions',
3437 'tap': 'NetdevTapOptions',
3438 'l2tpv3': 'NetdevL2TPv3Options',
3439 'socket': 'NetdevSocketOptions',
3440 'vde': 'NetdevVdeOptions',
3441 'dump': 'NetdevDumpOptions',
3442 'bridge': 'NetdevBridgeOptions',
3443 'netmap': 'NetdevNetmapOptions',
3444 'vhost-user': 'NetdevVhostUserOptions' } }
3445
3446 ##
3447 # @NetFilterDirection:
3448 #
3449 # Indicates whether a netfilter is attached to a netdev's transmit queue or
3450 # receive queue or both.
3451 #
3452 # @all: the filter is attached both to the receive and the transmit
3453 # queue of the netdev (default).
3454 #
3455 # @rx: the filter is attached to the receive queue of the netdev,
3456 # where it will receive packets sent to the netdev.
3457 #
3458 # @tx: the filter is attached to the transmit queue of the netdev,
3459 # where it will receive packets sent by the netdev.
3460 #
3461 # Since: 2.5
3462 ##
3463 { 'enum': 'NetFilterDirection',
3464 'data': [ 'all', 'rx', 'tx' ] }
3465
3466 ##
3467 # @InetSocketAddress:
3468 #
3469 # Captures a socket address or address range in the Internet namespace.
3470 #
3471 # @host: host part of the address
3472 #
3473 # @port: port part of the address, or lowest port if @to is present
3474 #
3475 # @to: highest port to try
3476 #
3477 # @ipv4: whether to accept IPv4 addresses, default try both IPv4 and IPv6
3478 # #optional
3479 #
3480 # @ipv6: whether to accept IPv6 addresses, default try both IPv4 and IPv6
3481 # #optional
3482 #
3483 # Since: 1.3
3484 ##
3485 { 'struct': 'InetSocketAddress',
3486 'data': {
3487 'host': 'str',
3488 'port': 'str',
3489 '*to': 'uint16',
3490 '*ipv4': 'bool',
3491 '*ipv6': 'bool' } }
3492
3493 ##
3494 # @UnixSocketAddress:
3495 #
3496 # Captures a socket address in the local ("Unix socket") namespace.
3497 #
3498 # @path: filesystem path to use
3499 #
3500 # Since: 1.3
3501 ##
3502 { 'struct': 'UnixSocketAddress',
3503 'data': {
3504 'path': 'str' } }
3505
3506 ##
3507 # @VsockSocketAddress:
3508 #
3509 # Captures a socket address in the vsock namespace.
3510 #
3511 # @cid: unique host identifier
3512 # @port: port
3513 #
3514 # Note: string types are used to allow for possible future hostname or
3515 # service resolution support.
3516 #
3517 # Since: 2.8
3518 ##
3519 { 'struct': 'VsockSocketAddress',
3520 'data': {
3521 'cid': 'str',
3522 'port': 'str' } }
3523
3524 ##
3525 # @SocketAddress:
3526 #
3527 # Captures the address of a socket, which could also be a named file descriptor
3528 #
3529 # Since: 1.3
3530 ##
3531 { 'union': 'SocketAddress',
3532 'data': {
3533 'inet': 'InetSocketAddress',
3534 'unix': 'UnixSocketAddress',
3535 'vsock': 'VsockSocketAddress',
3536 'fd': 'String' } }
3537
3538 ##
3539 # @getfd:
3540 #
3541 # Receive a file descriptor via SCM rights and assign it a name
3542 #
3543 # @fdname: file descriptor name
3544 #
3545 # Returns: Nothing on success
3546 #
3547 # Since: 0.14.0
3548 #
3549 # Notes: If @fdname already exists, the file descriptor assigned to
3550 # it will be closed and replaced by the received file
3551 # descriptor.
3552 # The 'closefd' command can be used to explicitly close the
3553 # file descriptor when it is no longer needed.
3554 ##
3555 { 'command': 'getfd', 'data': {'fdname': 'str'} }
3556
3557 ##
3558 # @closefd:
3559 #
3560 # Close a file descriptor previously passed via SCM rights
3561 #
3562 # @fdname: file descriptor name
3563 #
3564 # Returns: Nothing on success
3565 #
3566 # Since: 0.14.0
3567 ##
3568 { 'command': 'closefd', 'data': {'fdname': 'str'} }
3569
3570 ##
3571 # @MachineInfo:
3572 #
3573 # Information describing a machine.
3574 #
3575 # @name: the name of the machine
3576 #
3577 # @alias: #optional an alias for the machine name
3578 #
3579 # @is-default: #optional whether the machine is default
3580 #
3581 # @cpu-max: maximum number of CPUs supported by the machine type
3582 # (since 1.5.0)
3583 #
3584 # @hotpluggable-cpus: cpu hotplug via -device is supported (since 2.7.0)
3585 #
3586 # Since: 1.2.0
3587 ##
3588 { 'struct': 'MachineInfo',
3589 'data': { 'name': 'str', '*alias': 'str',
3590 '*is-default': 'bool', 'cpu-max': 'int',
3591 'hotpluggable-cpus': 'bool'} }
3592
3593 ##
3594 # @query-machines:
3595 #
3596 # Return a list of supported machines
3597 #
3598 # Returns: a list of MachineInfo
3599 #
3600 # Since: 1.2.0
3601 ##
3602 { 'command': 'query-machines', 'returns': ['MachineInfo'] }
3603
3604 ##
3605 # @CpuDefinitionInfo:
3606 #
3607 # Virtual CPU definition.
3608 #
3609 # @name: the name of the CPU definition
3610 #
3611 # @migration-safe: #optional whether a CPU definition can be safely used for
3612 # migration in combination with a QEMU compatibility machine
3613 # when migrating between different QMU versions and between
3614 # hosts with different sets of (hardware or software)
3615 # capabilities. If not provided, information is not available
3616 # and callers should not assume the CPU definition to be
3617 # migration-safe. (since 2.8)
3618 #
3619 # @static: whether a CPU definition is static and will not change depending on
3620 # QEMU version, machine type, machine options and accelerator options.
3621 # A static model is always migration-safe. (since 2.8)
3622 #
3623 # @unavailable-features: #optional List of properties that prevent
3624 # the CPU model from running in the current
3625 # host. (since 2.8)
3626 # @typename: Type name that can be used as argument to @device-list-properties,
3627 # to introspect properties configurable using -cpu or -global.
3628 # (since 2.9)
3629 #
3630 # @unavailable-features is a list of QOM property names that
3631 # represent CPU model attributes that prevent the CPU from running.
3632 # If the QOM property is read-only, that means there's no known
3633 # way to make the CPU model run in the current host. Implementations
3634 # that choose not to provide specific information return the
3635 # property name "type".
3636 # If the property is read-write, it means that it MAY be possible
3637 # to run the CPU model in the current host if that property is
3638 # changed. Management software can use it as hints to suggest or
3639 # choose an alternative for the user, or just to generate meaningful
3640 # error messages explaining why the CPU model can't be used.
3641 # If @unavailable-features is an empty list, the CPU model is
3642 # runnable using the current host and machine-type.
3643 # If @unavailable-features is not present, runnability
3644 # information for the CPU is not available.
3645 #
3646 # Since: 1.2.0
3647 ##
3648 { 'struct': 'CpuDefinitionInfo',
3649 'data': { 'name': 'str', '*migration-safe': 'bool', 'static': 'bool',
3650 '*unavailable-features': [ 'str' ], 'typename': 'str' } }
3651
3652 ##
3653 # @query-cpu-definitions:
3654 #
3655 # Return a list of supported virtual CPU definitions
3656 #
3657 # Returns: a list of CpuDefInfo
3658 #
3659 # Since: 1.2.0
3660 ##
3661 { 'command': 'query-cpu-definitions', 'returns': ['CpuDefinitionInfo'] }
3662
3663 ##
3664 # @CpuModelInfo:
3665 #
3666 # Virtual CPU model.
3667 #
3668 # A CPU model consists of the name of a CPU definition, to which
3669 # delta changes are applied (e.g. features added/removed). Most magic values
3670 # that an architecture might require should be hidden behind the name.
3671 # However, if required, architectures can expose relevant properties.
3672 #
3673 # @name: the name of the CPU definition the model is based on
3674 # @props: #optional a dictionary of QOM properties to be applied
3675 #
3676 # Since: 2.8.0
3677 ##
3678 { 'struct': 'CpuModelInfo',
3679 'data': { 'name': 'str',
3680 '*props': 'any' } }
3681
3682 ##
3683 # @CpuModelExpansionType:
3684 #
3685 # An enumeration of CPU model expansion types.
3686 #
3687 # @static: Expand to a static CPU model, a combination of a static base
3688 # model name and property delta changes. As the static base model will
3689 # never change, the expanded CPU model will be the same, independant of
3690 # independent of QEMU version, machine type, machine options, and
3691 # accelerator options. Therefore, the resulting model can be used by
3692 # tooling without having to specify a compatibility machine - e.g. when
3693 # displaying the "host" model. static CPU models are migration-safe.
3694 #
3695 # @full: Expand all properties. The produced model is not guaranteed to be
3696 # migration-safe, but allows tooling to get an insight and work with
3697 # model details.
3698 #
3699 # Since: 2.8.0
3700 ##
3701 { 'enum': 'CpuModelExpansionType',
3702 'data': [ 'static', 'full' ] }
3703
3704
3705 ##
3706 # @CpuModelExpansionInfo:
3707 #
3708 # The result of a cpu model expansion.
3709 #
3710 # @model: the expanded CpuModelInfo.
3711 #
3712 # Since: 2.8.0
3713 ##
3714 { 'struct': 'CpuModelExpansionInfo',
3715 'data': { 'model': 'CpuModelInfo' } }
3716
3717
3718 ##
3719 # @query-cpu-model-expansion:
3720 #
3721 # Expands a given CPU model (or a combination of CPU model + additional options)
3722 # to different granularities, allowing tooling to get an understanding what a
3723 # specific CPU model looks like in QEMU under a certain configuration.
3724 #
3725 # This interface can be used to query the "host" CPU model.
3726 #
3727 # The data returned by this command may be affected by:
3728 #
3729 # * QEMU version: CPU models may look different depending on the QEMU version.
3730 # (Except for CPU models reported as "static" in query-cpu-definitions.)
3731 # * machine-type: CPU model may look different depending on the machine-type.
3732 # (Except for CPU models reported as "static" in query-cpu-definitions.)
3733 # * machine options (including accelerator): in some architectures, CPU models
3734 # may look different depending on machine and accelerator options. (Except for
3735 # CPU models reported as "static" in query-cpu-definitions.)
3736 # * "-cpu" arguments and global properties: arguments to the -cpu option and
3737 # global properties may affect expansion of CPU models. Using
3738 # query-cpu-model-expansion while using these is not advised.
3739 #
3740 # Some architectures may not support all expansion types. s390x supports
3741 # "full" and "static".
3742 #
3743 # Returns: a CpuModelExpansionInfo. Returns an error if expanding CPU models is
3744 # not supported, if the model cannot be expanded, if the model contains
3745 # an unknown CPU definition name, unknown properties or properties
3746 # with a wrong type. Also returns an error if an expansion type is
3747 # not supported.
3748 #
3749 # Since: 2.8.0
3750 ##
3751 { 'command': 'query-cpu-model-expansion',
3752 'data': { 'type': 'CpuModelExpansionType',
3753 'model': 'CpuModelInfo' },
3754 'returns': 'CpuModelExpansionInfo' }
3755
3756 ##
3757 # @CpuModelCompareResult:
3758 #
3759 # An enumeration of CPU model comparation results. The result is usually
3760 # calculated using e.g. CPU features or CPU generations.
3761 #
3762 # @incompatible: If model A is incompatible to model B, model A is not
3763 # guaranteed to run where model B runs and the other way around.
3764 #
3765 # @identical: If model A is identical to model B, model A is guaranteed to run
3766 # where model B runs and the other way around.
3767 #
3768 # @superset: If model A is a superset of model B, model B is guaranteed to run
3769 # where model A runs. There are no guarantees about the other way.
3770 #
3771 # @subset: If model A is a subset of model B, model A is guaranteed to run
3772 # where model B runs. There are no guarantees about the other way.
3773 #
3774 # Since: 2.8.0
3775 ##
3776 { 'enum': 'CpuModelCompareResult',
3777 'data': [ 'incompatible', 'identical', 'superset', 'subset' ] }
3778
3779 ##
3780 # @CpuModelCompareInfo:
3781 #
3782 # The result of a CPU model comparison.
3783 #
3784 # @result: The result of the compare operation.
3785 # @responsible-properties: List of properties that led to the comparison result
3786 # not being identical.
3787 #
3788 # @responsible-properties is a list of QOM property names that led to
3789 # both CPUs not being detected as identical. For identical models, this
3790 # list is empty.
3791 # If a QOM property is read-only, that means there's no known way to make the
3792 # CPU models identical. If the special property name "type" is included, the
3793 # models are by definition not identical and cannot be made identical.
3794 #
3795 # Since: 2.8.0
3796 ##
3797 { 'struct': 'CpuModelCompareInfo',
3798 'data': {'result': 'CpuModelCompareResult',
3799 'responsible-properties': ['str']
3800 }
3801 }
3802
3803 ##
3804 # @query-cpu-model-comparison:
3805 #
3806 # Compares two CPU models, returning how they compare in a specific
3807 # configuration. The results indicates how both models compare regarding
3808 # runnability. This result can be used by tooling to make decisions if a
3809 # certain CPU model will run in a certain configuration or if a compatible
3810 # CPU model has to be created by baselining.
3811 #
3812 # Usually, a CPU model is compared against the maximum possible CPU model
3813 # of a certain configuration (e.g. the "host" model for KVM). If that CPU
3814 # model is identical or a subset, it will run in that configuration.
3815 #
3816 # The result returned by this command may be affected by:
3817 #
3818 # * QEMU version: CPU models may look different depending on the QEMU version.
3819 # (Except for CPU models reported as "static" in query-cpu-definitions.)
3820 # * machine-type: CPU model may look different depending on the machine-type.
3821 # (Except for CPU models reported as "static" in query-cpu-definitions.)
3822 # * machine options (including accelerator): in some architectures, CPU models
3823 # may look different depending on machine and accelerator options. (Except for
3824 # CPU models reported as "static" in query-cpu-definitions.)
3825 # * "-cpu" arguments and global properties: arguments to the -cpu option and
3826 # global properties may affect expansion of CPU models. Using
3827 # query-cpu-model-expansion while using these is not advised.
3828 #
3829 # Some architectures may not support comparing CPU models. s390x supports
3830 # comparing CPU models.
3831 #
3832 # Returns: a CpuModelBaselineInfo. Returns an error if comparing CPU models is
3833 # not supported, if a model cannot be used, if a model contains
3834 # an unknown cpu definition name, unknown properties or properties
3835 # with wrong types.
3836 #
3837 # Since: 2.8.0
3838 ##
3839 { 'command': 'query-cpu-model-comparison',
3840 'data': { 'modela': 'CpuModelInfo', 'modelb': 'CpuModelInfo' },
3841 'returns': 'CpuModelCompareInfo' }
3842
3843 ##
3844 # @CpuModelBaselineInfo:
3845 #
3846 # The result of a CPU model baseline.
3847 #
3848 # @model: the baselined CpuModelInfo.
3849 #
3850 # Since: 2.8.0
3851 ##
3852 { 'struct': 'CpuModelBaselineInfo',
3853 'data': { 'model': 'CpuModelInfo' } }
3854
3855 ##
3856 # @query-cpu-model-baseline:
3857 #
3858 # Baseline two CPU models, creating a compatible third model. The created
3859 # model will always be a static, migration-safe CPU model (see "static"
3860 # CPU model expansion for details).
3861 #
3862 # This interface can be used by tooling to create a compatible CPU model out
3863 # two CPU models. The created CPU model will be identical to or a subset of
3864 # both CPU models when comparing them. Therefore, the created CPU model is
3865 # guaranteed to run where the given CPU models run.
3866 #
3867 # The result returned by this command may be affected by:
3868 #
3869 # * QEMU version: CPU models may look different depending on the QEMU version.
3870 # (Except for CPU models reported as "static" in query-cpu-definitions.)
3871 # * machine-type: CPU model may look different depending on the machine-type.
3872 # (Except for CPU models reported as "static" in query-cpu-definitions.)
3873 # * machine options (including accelerator): in some architectures, CPU models
3874 # may look different depending on machine and accelerator options. (Except for
3875 # CPU models reported as "static" in query-cpu-definitions.)
3876 # * "-cpu" arguments and global properties: arguments to the -cpu option and
3877 # global properties may affect expansion of CPU models. Using
3878 # query-cpu-model-expansion while using these is not advised.
3879 #
3880 # Some architectures may not support baselining CPU models. s390x supports
3881 # baselining CPU models.
3882 #
3883 # Returns: a CpuModelBaselineInfo. Returns an error if baselining CPU models is
3884 # not supported, if a model cannot be used, if a model contains
3885 # an unknown cpu definition name, unknown properties or properties
3886 # with wrong types.
3887 #
3888 # Since: 2.8.0
3889 ##
3890 { 'command': 'query-cpu-model-baseline',
3891 'data': { 'modela': 'CpuModelInfo',
3892 'modelb': 'CpuModelInfo' },
3893 'returns': 'CpuModelBaselineInfo' }
3894
3895 ##
3896 # @AddfdInfo:
3897 #
3898 # Information about a file descriptor that was added to an fd set.
3899 #
3900 # @fdset-id: The ID of the fd set that @fd was added to.
3901 #
3902 # @fd: The file descriptor that was received via SCM rights and
3903 # added to the fd set.
3904 #
3905 # Since: 1.2.0
3906 ##
3907 { 'struct': 'AddfdInfo', 'data': {'fdset-id': 'int', 'fd': 'int'} }
3908
3909 ##
3910 # @add-fd:
3911 #
3912 # Add a file descriptor, that was passed via SCM rights, to an fd set.
3913 #
3914 # @fdset-id: #optional The ID of the fd set to add the file descriptor to.
3915 #
3916 # @opaque: #optional A free-form string that can be used to describe the fd.
3917 #
3918 # Returns: @AddfdInfo on success
3919 # If file descriptor was not received, FdNotSupplied
3920 # If @fdset-id is a negative value, InvalidParameterValue
3921 #
3922 # Notes: The list of fd sets is shared by all monitor connections.
3923 #
3924 # If @fdset-id is not specified, a new fd set will be created.
3925 #
3926 # Since: 1.2.0
3927 ##
3928 { 'command': 'add-fd', 'data': {'*fdset-id': 'int', '*opaque': 'str'},
3929 'returns': 'AddfdInfo' }
3930
3931 ##
3932 # @remove-fd:
3933 #
3934 # Remove a file descriptor from an fd set.
3935 #
3936 # @fdset-id: The ID of the fd set that the file descriptor belongs to.
3937 #
3938 # @fd: #optional The file descriptor that is to be removed.
3939 #
3940 # Returns: Nothing on success
3941 # If @fdset-id or @fd is not found, FdNotFound
3942 #
3943 # Since: 1.2.0
3944 #
3945 # Notes: The list of fd sets is shared by all monitor connections.
3946 #
3947 # If @fd is not specified, all file descriptors in @fdset-id
3948 # will be removed.
3949 ##
3950 { 'command': 'remove-fd', 'data': {'fdset-id': 'int', '*fd': 'int'} }
3951
3952 ##
3953 # @FdsetFdInfo:
3954 #
3955 # Information about a file descriptor that belongs to an fd set.
3956 #
3957 # @fd: The file descriptor value.
3958 #
3959 # @opaque: #optional A free-form string that can be used to describe the fd.
3960 #
3961 # Since: 1.2.0
3962 ##
3963 { 'struct': 'FdsetFdInfo',
3964 'data': {'fd': 'int', '*opaque': 'str'} }
3965
3966 ##
3967 # @FdsetInfo:
3968 #
3969 # Information about an fd set.
3970 #
3971 # @fdset-id: The ID of the fd set.
3972 #
3973 # @fds: A list of file descriptors that belong to this fd set.
3974 #
3975 # Since: 1.2.0
3976 ##
3977 { 'struct': 'FdsetInfo',
3978 'data': {'fdset-id': 'int', 'fds': ['FdsetFdInfo']} }
3979
3980 ##
3981 # @query-fdsets:
3982 #
3983 # Return information describing all fd sets.
3984 #
3985 # Returns: A list of @FdsetInfo
3986 #
3987 # Since: 1.2.0
3988 #
3989 # Note: The list of fd sets is shared by all monitor connections.
3990 #
3991 ##
3992 { 'command': 'query-fdsets', 'returns': ['FdsetInfo'] }
3993
3994 ##
3995 # @TargetInfo:
3996 #
3997 # Information describing the QEMU target.
3998 #
3999 # @arch: the target architecture (eg "x86_64", "i386", etc)
4000 #
4001 # Since: 1.2.0
4002 ##
4003 { 'struct': 'TargetInfo',
4004 'data': { 'arch': 'str' } }
4005
4006 ##
4007 # @query-target:
4008 #
4009 # Return information about the target for this QEMU
4010 #
4011 # Returns: TargetInfo
4012 #
4013 # Since: 1.2.0
4014 ##
4015 { 'command': 'query-target', 'returns': 'TargetInfo' }
4016
4017 ##
4018 # @QKeyCode:
4019 #
4020 # An enumeration of key name.
4021 #
4022 # This is used by the @send-key command.
4023 #
4024 # @unmapped: since 2.0
4025 # @pause: since 2.0
4026 # @ro: since 2.4
4027 # @kp_comma: since 2.4
4028 # @kp_equals: since 2.6
4029 # @power: since 2.6
4030 # @hiragana: since 2.9
4031 # @henkan: since 2.9
4032 # @yen: since 2.9
4033 #
4034 # Since: 1.3.0
4035 #
4036 ##
4037 { 'enum': 'QKeyCode',
4038 'data': [ 'unmapped',
4039 'shift', 'shift_r', 'alt', 'alt_r', 'altgr', 'altgr_r', 'ctrl',
4040 'ctrl_r', 'menu', 'esc', '1', '2', '3', '4', '5', '6', '7', '8',
4041 '9', '0', 'minus', 'equal', 'backspace', 'tab', 'q', 'w', 'e',
4042 'r', 't', 'y', 'u', 'i', 'o', 'p', 'bracket_left', 'bracket_right',
4043 'ret', 'a', 's', 'd', 'f', 'g', 'h', 'j', 'k', 'l', 'semicolon',
4044 'apostrophe', 'grave_accent', 'backslash', 'z', 'x', 'c', 'v', 'b',
4045 'n', 'm', 'comma', 'dot', 'slash', 'asterisk', 'spc', 'caps_lock',
4046 'f1', 'f2', 'f3', 'f4', 'f5', 'f6', 'f7', 'f8', 'f9', 'f10',
4047 'num_lock', 'scroll_lock', 'kp_divide', 'kp_multiply',
4048 'kp_subtract', 'kp_add', 'kp_enter', 'kp_decimal', 'sysrq', 'kp_0',
4049 'kp_1', 'kp_2', 'kp_3', 'kp_4', 'kp_5', 'kp_6', 'kp_7', 'kp_8',
4050 'kp_9', 'less', 'f11', 'f12', 'print', 'home', 'pgup', 'pgdn', 'end',
4051 'left', 'up', 'down', 'right', 'insert', 'delete', 'stop', 'again',
4052 'props', 'undo', 'front', 'copy', 'open', 'paste', 'find', 'cut',
4053 'lf', 'help', 'meta_l', 'meta_r', 'compose', 'pause',
4054 'ro', 'hiragana', 'henkan', 'yen',
4055 'kp_comma', 'kp_equals', 'power' ] }
4056
4057 ##
4058 # @KeyValue:
4059 #
4060 # Represents a keyboard key.
4061 #
4062 # Since: 1.3.0
4063 ##
4064 { 'union': 'KeyValue',
4065 'data': {
4066 'number': 'int',
4067 'qcode': 'QKeyCode' } }
4068
4069 ##
4070 # @send-key:
4071 #
4072 # Send keys to guest.
4073 #
4074 # @keys: An array of @KeyValue elements. All @KeyValues in this array are
4075 # simultaneously sent to the guest. A @KeyValue.number value is sent
4076 # directly to the guest, while @KeyValue.qcode must be a valid
4077 # @QKeyCode value
4078 #
4079 # @hold-time: #optional time to delay key up events, milliseconds. Defaults
4080 # to 100
4081 #
4082 # Returns: Nothing on success
4083 # If key is unknown or redundant, InvalidParameter
4084 #
4085 # Since: 1.3.0
4086 #
4087 ##
4088 { 'command': 'send-key',
4089 'data': { 'keys': ['KeyValue'], '*hold-time': 'int' } }
4090
4091 ##
4092 # @screendump:
4093 #
4094 # Write a PPM of the VGA screen to a file.
4095 #
4096 # @filename: the path of a new PPM file to store the image
4097 #
4098 # Returns: Nothing on success
4099 #
4100 # Since: 0.14.0
4101 ##
4102 { 'command': 'screendump', 'data': {'filename': 'str'} }
4103
4104
4105 ##
4106 # @ChardevCommon:
4107 #
4108 # Configuration shared across all chardev backends
4109 #
4110 # @logfile: #optional The name of a logfile to save output
4111 # @logappend: #optional true to append instead of truncate
4112 # (default to false to truncate)
4113 #
4114 # Since: 2.6
4115 ##
4116 { 'struct': 'ChardevCommon', 'data': { '*logfile': 'str',
4117 '*logappend': 'bool' } }
4118
4119 ##
4120 # @ChardevFile:
4121 #
4122 # Configuration info for file chardevs.
4123 #
4124 # @in: #optional The name of the input file
4125 # @out: The name of the output file
4126 # @append: #optional Open the file in append mode (default false to
4127 # truncate) (Since 2.6)
4128 #
4129 # Since: 1.4
4130 ##
4131 { 'struct': 'ChardevFile', 'data': { '*in' : 'str',
4132 'out' : 'str',
4133 '*append': 'bool' },
4134 'base': 'ChardevCommon' }
4135
4136 ##
4137 # @ChardevHostdev:
4138 #
4139 # Configuration info for device and pipe chardevs.
4140 #
4141 # @device: The name of the special file for the device,
4142 # i.e. /dev/ttyS0 on Unix or COM1: on Windows
4143 #
4144 # Since: 1.4
4145 ##
4146 { 'struct': 'ChardevHostdev', 'data': { 'device' : 'str' },
4147 'base': 'ChardevCommon' }
4148
4149 ##
4150 # @ChardevSocket:
4151 #
4152 # Configuration info for (stream) socket chardevs.
4153 #
4154 # @addr: socket address to listen on (server=true)
4155 # or connect to (server=false)
4156 # @tls-creds: #optional the ID of the TLS credentials object (since 2.6)
4157 # @server: #optional create server socket (default: true)
4158 # @wait: #optional wait for incoming connection on server
4159 # sockets (default: false).
4160 # @nodelay: #optional set TCP_NODELAY socket option (default: false)
4161 # @telnet: #optional enable telnet protocol on server
4162 # sockets (default: false)
4163 # @reconnect: #optional For a client socket, if a socket is disconnected,
4164 # then attempt a reconnect after the given number of seconds.
4165 # Setting this to zero disables this function. (default: 0)
4166 # (Since: 2.2)
4167 #
4168 # Since: 1.4
4169 ##
4170 { 'struct': 'ChardevSocket', 'data': { 'addr' : 'SocketAddress',
4171 '*tls-creds' : 'str',
4172 '*server' : 'bool',
4173 '*wait' : 'bool',
4174 '*nodelay' : 'bool',
4175 '*telnet' : 'bool',
4176 '*reconnect' : 'int' },
4177 'base': 'ChardevCommon' }
4178
4179 ##
4180 # @ChardevUdp:
4181 #
4182 # Configuration info for datagram socket chardevs.
4183 #
4184 # @remote: remote address
4185 # @local: #optional local address
4186 #
4187 # Since: 1.5
4188 ##
4189 { 'struct': 'ChardevUdp', 'data': { 'remote' : 'SocketAddress',
4190 '*local' : 'SocketAddress' },
4191 'base': 'ChardevCommon' }
4192
4193 ##
4194 # @ChardevMux:
4195 #
4196 # Configuration info for mux chardevs.
4197 #
4198 # @chardev: name of the base chardev.
4199 #
4200 # Since: 1.5
4201 ##
4202 { 'struct': 'ChardevMux', 'data': { 'chardev' : 'str' },
4203 'base': 'ChardevCommon' }
4204
4205 ##
4206 # @ChardevStdio:
4207 #
4208 # Configuration info for stdio chardevs.
4209 #
4210 # @signal: #optional Allow signals (such as SIGINT triggered by ^C)
4211 # be delivered to qemu. Default: true in -nographic mode,
4212 # false otherwise.
4213 #
4214 # Since: 1.5
4215 ##
4216 { 'struct': 'ChardevStdio', 'data': { '*signal' : 'bool' },
4217 'base': 'ChardevCommon' }
4218
4219
4220 ##
4221 # @ChardevSpiceChannel:
4222 #
4223 # Configuration info for spice vm channel chardevs.
4224 #
4225 # @type: kind of channel (for example vdagent).
4226 #
4227 # Since: 1.5
4228 ##
4229 { 'struct': 'ChardevSpiceChannel', 'data': { 'type' : 'str' },
4230 'base': 'ChardevCommon' }
4231
4232 ##
4233 # @ChardevSpicePort:
4234 #
4235 # Configuration info for spice port chardevs.
4236 #
4237 # @fqdn: name of the channel (see docs/spice-port-fqdn.txt)
4238 #
4239 # Since: 1.5
4240 ##
4241 { 'struct': 'ChardevSpicePort', 'data': { 'fqdn' : 'str' },
4242 'base': 'ChardevCommon' }
4243
4244 ##
4245 # @ChardevVC:
4246 #
4247 # Configuration info for virtual console chardevs.
4248 #
4249 # @width: console width, in pixels
4250 # @height: console height, in pixels
4251 # @cols: console width, in chars
4252 # @rows: console height, in chars
4253 #
4254 # Since: 1.5
4255 ##
4256 { 'struct': 'ChardevVC', 'data': { '*width' : 'int',
4257 '*height' : 'int',
4258 '*cols' : 'int',
4259 '*rows' : 'int' },
4260 'base': 'ChardevCommon' }
4261
4262 ##
4263 # @ChardevRingbuf:
4264 #
4265 # Configuration info for ring buffer chardevs.
4266 #
4267 # @size: #optional ring buffer size, must be power of two, default is 65536
4268 #
4269 # Since: 1.5
4270 ##
4271 { 'struct': 'ChardevRingbuf', 'data': { '*size' : 'int' },
4272 'base': 'ChardevCommon' }
4273
4274 ##
4275 # @ChardevBackend:
4276 #
4277 # Configuration info for the new chardev backend.
4278 #
4279 # Since: 1.4 (testdev since 2.2)
4280 ##
4281 { 'union': 'ChardevBackend', 'data': { 'file' : 'ChardevFile',
4282 'serial' : 'ChardevHostdev',
4283 'parallel': 'ChardevHostdev',
4284 'pipe' : 'ChardevHostdev',
4285 'socket' : 'ChardevSocket',
4286 'udp' : 'ChardevUdp',
4287 'pty' : 'ChardevCommon',
4288 'null' : 'ChardevCommon',
4289 'mux' : 'ChardevMux',
4290 'msmouse': 'ChardevCommon',
4291 'braille': 'ChardevCommon',
4292 'testdev': 'ChardevCommon',
4293 'stdio' : 'ChardevStdio',
4294 'console': 'ChardevCommon',
4295 'spicevmc' : 'ChardevSpiceChannel',
4296 'spiceport' : 'ChardevSpicePort',
4297 'vc' : 'ChardevVC',
4298 'ringbuf': 'ChardevRingbuf',
4299 # next one is just for compatibility
4300 'memory' : 'ChardevRingbuf' } }
4301
4302 ##
4303 # @ChardevReturn:
4304 #
4305 # Return info about the chardev backend just created.
4306 #
4307 # @pty: #optional name of the slave pseudoterminal device, present if
4308 # and only if a chardev of type 'pty' was created
4309 #
4310 # Since: 1.4
4311 ##
4312 { 'struct' : 'ChardevReturn', 'data': { '*pty' : 'str' } }
4313
4314 ##
4315 # @chardev-add:
4316 #
4317 # Add a character device backend
4318 #
4319 # @id: the chardev's ID, must be unique
4320 # @backend: backend type and parameters
4321 #
4322 # Returns: ChardevReturn.
4323 #
4324 # Since: 1.4
4325 ##
4326 { 'command': 'chardev-add', 'data': {'id' : 'str',
4327 'backend' : 'ChardevBackend' },
4328 'returns': 'ChardevReturn' }
4329
4330 ##
4331 # @chardev-remove:
4332 #
4333 # Remove a character device backend
4334 #
4335 # @id: the chardev's ID, must exist and not be in use
4336 #
4337 # Returns: Nothing on success
4338 #
4339 # Since: 1.4
4340 ##
4341 { 'command': 'chardev-remove', 'data': {'id': 'str'} }
4342
4343 ##
4344 # @TpmModel:
4345 #
4346 # An enumeration of TPM models
4347 #
4348 # @tpm-tis: TPM TIS model
4349 #
4350 # Since: 1.5
4351 ##
4352 { 'enum': 'TpmModel', 'data': [ 'tpm-tis' ] }
4353
4354 ##
4355 # @query-tpm-models:
4356 #
4357 # Return a list of supported TPM models
4358 #
4359 # Returns: a list of TpmModel
4360 #
4361 # Since: 1.5
4362 ##
4363 { 'command': 'query-tpm-models', 'returns': ['TpmModel'] }
4364
4365 ##
4366 # @TpmType:
4367 #
4368 # An enumeration of TPM types
4369 #
4370 # @passthrough: TPM passthrough type
4371 #
4372 # Since: 1.5
4373 ##
4374 { 'enum': 'TpmType', 'data': [ 'passthrough' ] }
4375
4376 ##
4377 # @query-tpm-types:
4378 #
4379 # Return a list of supported TPM types
4380 #
4381 # Returns: a list of TpmType
4382 #
4383 # Since: 1.5
4384 ##
4385 { 'command': 'query-tpm-types', 'returns': ['TpmType'] }
4386
4387 ##
4388 # @TPMPassthroughOptions:
4389 #
4390 # Information about the TPM passthrough type
4391 #
4392 # @path: #optional string describing the path used for accessing the TPM device
4393 #
4394 # @cancel-path: #optional string showing the TPM's sysfs cancel file
4395 # for cancellation of TPM commands while they are executing
4396 #
4397 # Since: 1.5
4398 ##
4399 { 'struct': 'TPMPassthroughOptions', 'data': { '*path' : 'str',
4400 '*cancel-path' : 'str'} }
4401
4402 ##
4403 # @TpmTypeOptions:
4404 #
4405 # A union referencing different TPM backend types' configuration options
4406 #
4407 # @type: 'passthrough' The configuration options for the TPM passthrough type
4408 #
4409 # Since: 1.5
4410 ##
4411 { 'union': 'TpmTypeOptions',
4412 'data': { 'passthrough' : 'TPMPassthroughOptions' } }
4413
4414 ##
4415 # @TPMInfo:
4416 #
4417 # Information about the TPM
4418 #
4419 # @id: The Id of the TPM
4420 #
4421 # @model: The TPM frontend model
4422 #
4423 # @options: The TPM (backend) type configuration options
4424 #
4425 # Since: 1.5
4426 ##
4427 { 'struct': 'TPMInfo',
4428 'data': {'id': 'str',
4429 'model': 'TpmModel',
4430 'options': 'TpmTypeOptions' } }
4431
4432 ##
4433 # @query-tpm:
4434 #
4435 # Return information about the TPM device
4436 #
4437 # Returns: @TPMInfo on success
4438 #
4439 # Since: 1.5
4440 ##
4441 { 'command': 'query-tpm', 'returns': ['TPMInfo'] }
4442
4443 ##
4444 # @AcpiTableOptions:
4445 #
4446 # Specify an ACPI table on the command line to load.
4447 #
4448 # At most one of @file and @data can be specified. The list of files specified
4449 # by any one of them is loaded and concatenated in order. If both are omitted,
4450 # @data is implied.
4451 #
4452 # Other fields / optargs can be used to override fields of the generic ACPI
4453 # table header; refer to the ACPI specification 5.0, section 5.2.6 System
4454 # Description Table Header. If a header field is not overridden, then the
4455 # corresponding value from the concatenated blob is used (in case of @file), or
4456 # it is filled in with a hard-coded value (in case of @data).
4457 #
4458 # String fields are copied into the matching ACPI member from lowest address
4459 # upwards, and silently truncated / NUL-padded to length.
4460 #
4461 # @sig: #optional table signature / identifier (4 bytes)
4462 #
4463 # @rev: #optional table revision number (dependent on signature, 1 byte)
4464 #
4465 # @oem_id: #optional OEM identifier (6 bytes)
4466 #
4467 # @oem_table_id: #optional OEM table identifier (8 bytes)
4468 #
4469 # @oem_rev: #optional OEM-supplied revision number (4 bytes)
4470 #
4471 # @asl_compiler_id: #optional identifier of the utility that created the table
4472 # (4 bytes)
4473 #
4474 # @asl_compiler_rev: #optional revision number of the utility that created the
4475 # table (4 bytes)
4476 #
4477 # @file: #optional colon (:) separated list of pathnames to load and
4478 # concatenate as table data. The resultant binary blob is expected to
4479 # have an ACPI table header. At least one file is required. This field
4480 # excludes @data.
4481 #
4482 # @data: #optional colon (:) separated list of pathnames to load and
4483 # concatenate as table data. The resultant binary blob must not have an
4484 # ACPI table header. At least one file is required. This field excludes
4485 # @file.
4486 #
4487 # Since: 1.5
4488 ##
4489 { 'struct': 'AcpiTableOptions',
4490 'data': {
4491 '*sig': 'str',
4492 '*rev': 'uint8',
4493 '*oem_id': 'str',
4494 '*oem_table_id': 'str',
4495 '*oem_rev': 'uint32',
4496 '*asl_compiler_id': 'str',
4497 '*asl_compiler_rev': 'uint32',
4498 '*file': 'str',
4499 '*data': 'str' }}
4500
4501 ##
4502 # @CommandLineParameterType:
4503 #
4504 # Possible types for an option parameter.
4505 #
4506 # @string: accepts a character string
4507 #
4508 # @boolean: accepts "on" or "off"
4509 #
4510 # @number: accepts a number
4511 #
4512 # @size: accepts a number followed by an optional suffix (K)ilo,
4513 # (M)ega, (G)iga, (T)era
4514 #
4515 # Since: 1.5
4516 ##
4517 { 'enum': 'CommandLineParameterType',
4518 'data': ['string', 'boolean', 'number', 'size'] }
4519
4520 ##
4521 # @CommandLineParameterInfo:
4522 #
4523 # Details about a single parameter of a command line option.
4524 #
4525 # @name: parameter name
4526 #
4527 # @type: parameter @CommandLineParameterType
4528 #
4529 # @help: #optional human readable text string, not suitable for parsing.
4530 #
4531 # @default: #optional default value string (since 2.1)
4532 #
4533 # Since: 1.5
4534 ##
4535 { 'struct': 'CommandLineParameterInfo',
4536 'data': { 'name': 'str',
4537 'type': 'CommandLineParameterType',
4538 '*help': 'str',
4539 '*default': 'str' } }
4540
4541 ##
4542 # @CommandLineOptionInfo:
4543 #
4544 # Details about a command line option, including its list of parameter details
4545 #
4546 # @option: option name
4547 #
4548 # @parameters: an array of @CommandLineParameterInfo
4549 #
4550 # Since: 1.5
4551 ##
4552 { 'struct': 'CommandLineOptionInfo',
4553 'data': { 'option': 'str', 'parameters': ['CommandLineParameterInfo'] } }
4554
4555 ##
4556 # @query-command-line-options:
4557 #
4558 # Query command line option schema.
4559 #
4560 # @option: #optional option name
4561 #
4562 # Returns: list of @CommandLineOptionInfo for all options (or for the given
4563 # @option). Returns an error if the given @option doesn't exist.
4564 #
4565 # Since: 1.5
4566 ##
4567 {'command': 'query-command-line-options', 'data': { '*option': 'str' },
4568 'returns': ['CommandLineOptionInfo'] }
4569
4570 ##
4571 # @X86CPURegister32:
4572 #
4573 # A X86 32-bit register
4574 #
4575 # Since: 1.5
4576 ##
4577 { 'enum': 'X86CPURegister32',
4578 'data': [ 'EAX', 'EBX', 'ECX', 'EDX', 'ESP', 'EBP', 'ESI', 'EDI' ] }
4579
4580 ##
4581 # @X86CPUFeatureWordInfo:
4582 #
4583 # Information about a X86 CPU feature word
4584 #
4585 # @cpuid-input-eax: Input EAX value for CPUID instruction for that feature word
4586 #
4587 # @cpuid-input-ecx: #optional Input ECX value for CPUID instruction for that
4588 # feature word
4589 #
4590 # @cpuid-register: Output register containing the feature bits
4591 #
4592 # @features: value of output register, containing the feature bits
4593 #
4594 # Since: 1.5
4595 ##
4596 { 'struct': 'X86CPUFeatureWordInfo',
4597 'data': { 'cpuid-input-eax': 'int',
4598 '*cpuid-input-ecx': 'int',
4599 'cpuid-register': 'X86CPURegister32',
4600 'features': 'int' } }
4601
4602 ##
4603 # @DummyForceArrays:
4604 #
4605 # Not used by QMP; hack to let us use X86CPUFeatureWordInfoList internally
4606 #
4607 # Since: 2.5
4608 ##
4609 { 'struct': 'DummyForceArrays',
4610 'data': { 'unused': ['X86CPUFeatureWordInfo'] } }
4611
4612
4613 ##
4614 # @RxState:
4615 #
4616 # Packets receiving state
4617 #
4618 # @normal: filter assigned packets according to the mac-table
4619 #
4620 # @none: don't receive any assigned packet
4621 #
4622 # @all: receive all assigned packets
4623 #
4624 # Since: 1.6
4625 ##
4626 { 'enum': 'RxState', 'data': [ 'normal', 'none', 'all' ] }
4627
4628 ##
4629 # @RxFilterInfo:
4630 #
4631 # Rx-filter information for a NIC.
4632 #
4633 # @name: net client name
4634 #
4635 # @promiscuous: whether promiscuous mode is enabled
4636 #
4637 # @multicast: multicast receive state
4638 #
4639 # @unicast: unicast receive state
4640 #
4641 # @vlan: vlan receive state (Since 2.0)
4642 #
4643 # @broadcast-allowed: whether to receive broadcast
4644 #
4645 # @multicast-overflow: multicast table is overflowed or not
4646 #
4647 # @unicast-overflow: unicast table is overflowed or not
4648 #
4649 # @main-mac: the main macaddr string
4650 #
4651 # @vlan-table: a list of active vlan id
4652 #
4653 # @unicast-table: a list of unicast macaddr string
4654 #
4655 # @multicast-table: a list of multicast macaddr string
4656 #
4657 # Since: 1.6
4658 ##
4659 { 'struct': 'RxFilterInfo',
4660 'data': {
4661 'name': 'str',
4662 'promiscuous': 'bool',
4663 'multicast': 'RxState',
4664 'unicast': 'RxState',
4665 'vlan': 'RxState',
4666 'broadcast-allowed': 'bool',
4667 'multicast-overflow': 'bool',
4668 'unicast-overflow': 'bool',
4669 'main-mac': 'str',
4670 'vlan-table': ['int'],
4671 'unicast-table': ['str'],
4672 'multicast-table': ['str'] }}
4673
4674 ##
4675 # @query-rx-filter:
4676 #
4677 # Return rx-filter information for all NICs (or for the given NIC).
4678 #
4679 # @name: #optional net client name
4680 #
4681 # Returns: list of @RxFilterInfo for all NICs (or for the given NIC).
4682 # Returns an error if the given @name doesn't exist, or given
4683 # NIC doesn't support rx-filter querying, or given net client
4684 # isn't a NIC.
4685 #
4686 # Since: 1.6
4687 ##
4688 { 'command': 'query-rx-filter', 'data': { '*name': 'str' },
4689 'returns': ['RxFilterInfo'] }
4690
4691 ##
4692 # @InputButton:
4693 #
4694 # Button of a pointer input device (mouse, tablet).
4695 #
4696 # Since: 2.0
4697 ##
4698 { 'enum' : 'InputButton',
4699 'data' : [ 'left', 'middle', 'right', 'wheel-up', 'wheel-down' ] }
4700
4701 ##
4702 # @InputAxis:
4703 #
4704 # Position axis of a pointer input device (mouse, tablet).
4705 #
4706 # Since: 2.0
4707 ##
4708 { 'enum' : 'InputAxis',
4709 'data' : [ 'x', 'y' ] }
4710
4711 ##
4712 # @InputKeyEvent:
4713 #
4714 # Keyboard input event.
4715 #
4716 # @key: Which key this event is for.
4717 # @down: True for key-down and false for key-up events.
4718 #
4719 # Since: 2.0
4720 ##
4721 { 'struct' : 'InputKeyEvent',
4722 'data' : { 'key' : 'KeyValue',
4723 'down' : 'bool' } }
4724
4725 ##
4726 # @InputBtnEvent:
4727 #
4728 # Pointer button input event.
4729 #
4730 # @button: Which button this event is for.
4731 # @down: True for key-down and false for key-up events.
4732 #
4733 # Since: 2.0
4734 ##
4735 { 'struct' : 'InputBtnEvent',
4736 'data' : { 'button' : 'InputButton',
4737 'down' : 'bool' } }
4738
4739 ##
4740 # @InputMoveEvent:
4741 #
4742 # Pointer motion input event.
4743 #
4744 # @axis: Which axis is referenced by @value.
4745 # @value: Pointer position. For absolute coordinates the
4746 # valid range is 0 -> 0x7ffff
4747 #
4748 # Since: 2.0
4749 ##
4750 { 'struct' : 'InputMoveEvent',
4751 'data' : { 'axis' : 'InputAxis',
4752 'value' : 'int' } }
4753
4754 ##
4755 # @InputEvent:
4756 #
4757 # Input event union.
4758 #
4759 # @type: the input type, one of:
4760 # - 'key': Input event of Keyboard
4761 # - 'btn': Input event of pointer buttons
4762 # - 'rel': Input event of relative pointer motion
4763 # - 'abs': Input event of absolute pointer motion
4764 #
4765 # Since: 2.0
4766 ##
4767 { 'union' : 'InputEvent',
4768 'data' : { 'key' : 'InputKeyEvent',
4769 'btn' : 'InputBtnEvent',
4770 'rel' : 'InputMoveEvent',
4771 'abs' : 'InputMoveEvent' } }
4772
4773 ##
4774 # @input-send-event:
4775 #
4776 # Send input event(s) to guest.
4777 #
4778 # @device: #optional display device to send event(s) to.
4779 # @head: #optional head to send event(s) to, in case the
4780 # display device supports multiple scanouts.
4781 # @events: List of InputEvent union.
4782 #
4783 # Returns: Nothing on success.
4784 #
4785 # The @display and @head parameters can be used to send the input
4786 # event to specific input devices in case (a) multiple input devices
4787 # of the same kind are added to the virtual machine and (b) you have
4788 # configured input routing (see docs/multiseat.txt) for those input
4789 # devices. The parameters work exactly like the device and head
4790 # properties of input devices. If @device is missing, only devices
4791 # that have no input routing config are admissible. If @device is
4792 # specified, both input devices with and without input routing config
4793 # are admissible, but devices with input routing config take
4794 # precedence.
4795 #
4796 # Since: 2.6
4797 ##
4798 { 'command': 'input-send-event',
4799 'data': { '*device': 'str',
4800 '*head' : 'int',
4801 'events' : [ 'InputEvent' ] } }
4802
4803 ##
4804 # @NumaOptions:
4805 #
4806 # A discriminated record of NUMA options. (for OptsVisitor)
4807 #
4808 # Since: 2.1
4809 ##
4810 { 'union': 'NumaOptions',
4811 'data': {
4812 'node': 'NumaNodeOptions' }}
4813
4814 ##
4815 # @NumaNodeOptions:
4816 #
4817 # Create a guest NUMA node. (for OptsVisitor)
4818 #
4819 # @nodeid: #optional NUMA node ID (increase by 1 from 0 if omitted)
4820 #
4821 # @cpus: #optional VCPUs belonging to this node (assign VCPUS round-robin
4822 # if omitted)
4823 #
4824 # @mem: #optional memory size of this node; mutually exclusive with @memdev.
4825 # Equally divide total memory among nodes if both @mem and @memdev are
4826 # omitted.
4827 #
4828 # @memdev: #optional memory backend object. If specified for one node,
4829 # it must be specified for all nodes.
4830 #
4831 # Since: 2.1
4832 ##
4833 { 'struct': 'NumaNodeOptions',
4834 'data': {
4835 '*nodeid': 'uint16',
4836 '*cpus': ['uint16'],
4837 '*mem': 'size',
4838 '*memdev': 'str' }}
4839
4840 ##
4841 # @HostMemPolicy:
4842 #
4843 # Host memory policy types
4844 #
4845 # @default: restore default policy, remove any nondefault policy
4846 #
4847 # @preferred: set the preferred host nodes for allocation
4848 #
4849 # @bind: a strict policy that restricts memory allocation to the
4850 # host nodes specified
4851 #
4852 # @interleave: memory allocations are interleaved across the set
4853 # of host nodes specified
4854 #
4855 # Since: 2.1
4856 ##
4857 { 'enum': 'HostMemPolicy',
4858 'data': [ 'default', 'preferred', 'bind', 'interleave' ] }
4859
4860 ##
4861 # @Memdev:
4862 #
4863 # Information about memory backend
4864 #
4865 # @id: #optional backend's ID if backend has 'id' property (since 2.9)
4866 #
4867 # @size: memory backend size
4868 #
4869 # @merge: enables or disables memory merge support
4870 #
4871 # @dump: includes memory backend's memory in a core dump or not
4872 #
4873 # @prealloc: enables or disables memory preallocation
4874 #
4875 # @host-nodes: host nodes for its memory policy
4876 #
4877 # @policy: memory policy of memory backend
4878 #
4879 # Since: 2.1
4880 ##
4881 { 'struct': 'Memdev',
4882 'data': {
4883 '*id': 'str',
4884 'size': 'size',
4885 'merge': 'bool',
4886 'dump': 'bool',
4887 'prealloc': 'bool',
4888 'host-nodes': ['uint16'],
4889 'policy': 'HostMemPolicy' }}
4890
4891 ##
4892 # @query-memdev:
4893 #
4894 # Returns information for all memory backends.
4895 #
4896 # Returns: a list of @Memdev.
4897 #
4898 # Since: 2.1
4899 ##
4900 { 'command': 'query-memdev', 'returns': ['Memdev'] }
4901
4902 ##
4903 # @PCDIMMDeviceInfo:
4904 #
4905 # PCDIMMDevice state information
4906 #
4907 # @id: #optional device's ID
4908 #
4909 # @addr: physical address, where device is mapped
4910 #
4911 # @size: size of memory that the device provides
4912 #
4913 # @slot: slot number at which device is plugged in
4914 #
4915 # @node: NUMA node number where device is plugged in
4916 #
4917 # @memdev: memory backend linked with device
4918 #
4919 # @hotplugged: true if device was hotplugged
4920 #
4921 # @hotpluggable: true if device if could be added/removed while machine is running
4922 #
4923 # Since: 2.1
4924 ##
4925 { 'struct': 'PCDIMMDeviceInfo',
4926 'data': { '*id': 'str',
4927 'addr': 'int',
4928 'size': 'int',
4929 'slot': 'int',
4930 'node': 'int',
4931 'memdev': 'str',
4932 'hotplugged': 'bool',
4933 'hotpluggable': 'bool'
4934 }
4935 }
4936
4937 ##
4938 # @MemoryDeviceInfo:
4939 #
4940 # Union containing information about a memory device
4941 #
4942 # Since: 2.1
4943 ##
4944 { 'union': 'MemoryDeviceInfo', 'data': {'dimm': 'PCDIMMDeviceInfo'} }
4945
4946 ##
4947 # @query-memory-devices:
4948 #
4949 # Lists available memory devices and their state
4950 #
4951 # Since: 2.1
4952 ##
4953 { 'command': 'query-memory-devices', 'returns': ['MemoryDeviceInfo'] }
4954
4955 ##
4956 # @ACPISlotType:
4957 #
4958 # @DIMM: memory slot
4959 # @CPU: logical CPU slot (since 2.7)
4960 ##
4961 { 'enum': 'ACPISlotType', 'data': [ 'DIMM', 'CPU' ] }
4962
4963 ##
4964 # @ACPIOSTInfo:
4965 #
4966 # OSPM Status Indication for a device
4967 # For description of possible values of @source and @status fields
4968 # see "_OST (OSPM Status Indication)" chapter of ACPI5.0 spec.
4969 #
4970 # @device: #optional device ID associated with slot
4971 #
4972 # @slot: slot ID, unique per slot of a given @slot-type
4973 #
4974 # @slot-type: type of the slot
4975 #
4976 # @source: an integer containing the source event
4977 #
4978 # @status: an integer containing the status code
4979 #
4980 # Since: 2.1
4981 ##
4982 { 'struct': 'ACPIOSTInfo',
4983 'data' : { '*device': 'str',
4984 'slot': 'str',
4985 'slot-type': 'ACPISlotType',
4986 'source': 'int',
4987 'status': 'int' } }
4988
4989 ##
4990 # @query-acpi-ospm-status:
4991 #
4992 # Lists ACPI OSPM status of ACPI device objects,
4993 # which might be reported via _OST method
4994 #
4995 # Since: 2.1
4996 ##
4997 { 'command': 'query-acpi-ospm-status', 'returns': ['ACPIOSTInfo'] }
4998
4999 ##
5000 # @WatchdogExpirationAction:
5001 #
5002 # An enumeration of the actions taken when the watchdog device's timer is
5003 # expired
5004 #
5005 # @reset: system resets
5006 #
5007 # @shutdown: system shutdown, note that it is similar to @powerdown, which
5008 # tries to set to system status and notify guest
5009 #
5010 # @poweroff: system poweroff, the emulator program exits
5011 #
5012 # @pause: system pauses, similar to @stop
5013 #
5014 # @debug: system enters debug state
5015 #
5016 # @none: nothing is done
5017 #
5018 # @inject-nmi: a non-maskable interrupt is injected into the first VCPU (all
5019 # VCPUS on x86) (since 2.4)
5020 #
5021 # Since: 2.1
5022 ##
5023 { 'enum': 'WatchdogExpirationAction',
5024 'data': [ 'reset', 'shutdown', 'poweroff', 'pause', 'debug', 'none',
5025 'inject-nmi' ] }
5026
5027 ##
5028 # @IoOperationType:
5029 #
5030 # An enumeration of the I/O operation types
5031 #
5032 # @read: read operation
5033 #
5034 # @write: write operation
5035 #
5036 # Since: 2.1
5037 ##
5038 { 'enum': 'IoOperationType',
5039 'data': [ 'read', 'write' ] }
5040
5041 ##
5042 # @GuestPanicAction:
5043 #
5044 # An enumeration of the actions taken when guest OS panic is detected
5045 #
5046 # @pause: system pauses
5047 #
5048 # Since: 2.1 (poweroff since 2.8)
5049 ##
5050 { 'enum': 'GuestPanicAction',
5051 'data': [ 'pause', 'poweroff' ] }
5052
5053 ##
5054 # @rtc-reset-reinjection:
5055 #
5056 # This command will reset the RTC interrupt reinjection backlog.
5057 # Can be used if another mechanism to synchronize guest time
5058 # is in effect, for example QEMU guest agent's guest-set-time
5059 # command.
5060 #
5061 # Since: 2.1
5062 ##
5063 { 'command': 'rtc-reset-reinjection' }
5064
5065 # Rocker ethernet network switch
5066 { 'include': 'qapi/rocker.json' }
5067
5068 ##
5069 # @ReplayMode:
5070 #
5071 # Mode of the replay subsystem.
5072 #
5073 # @none: normal execution mode. Replay or record are not enabled.
5074 #
5075 # @record: record mode. All non-deterministic data is written into the
5076 # replay log.
5077 #
5078 # @play: replay mode. Non-deterministic data required for system execution
5079 # is read from the log.
5080 #
5081 # Since: 2.5
5082 ##
5083 { 'enum': 'ReplayMode',
5084 'data': [ 'none', 'record', 'play' ] }
5085
5086 ##
5087 # @xen-load-devices-state:
5088 #
5089 # Load the state of all devices from file. The RAM and the block devices
5090 # of the VM are not loaded by this command.
5091 #
5092 # @filename: the file to load the state of the devices from as binary
5093 # data. See xen-save-devices-state.txt for a description of the binary
5094 # format.
5095 #
5096 # Since: 2.7
5097 ##
5098 { 'command': 'xen-load-devices-state', 'data': {'filename': 'str'} }
5099
5100 ##
5101 # @GICCapability:
5102 #
5103 # The struct describes capability for a specific GIC (Generic
5104 # Interrupt Controller) version. These bits are not only decided by
5105 # QEMU/KVM software version, but also decided by the hardware that
5106 # the program is running upon.
5107 #
5108 # @version: version of GIC to be described. Currently, only 2 and 3
5109 # are supported.
5110 #
5111 # @emulated: whether current QEMU/hardware supports emulated GIC
5112 # device in user space.
5113 #
5114 # @kernel: whether current QEMU/hardware supports hardware
5115 # accelerated GIC device in kernel.
5116 #
5117 # Since: 2.6
5118 ##
5119 { 'struct': 'GICCapability',
5120 'data': { 'version': 'int',
5121 'emulated': 'bool',
5122 'kernel': 'bool' } }
5123
5124 ##
5125 # @query-gic-capabilities:
5126 #
5127 # This command is ARM-only. It will return a list of GICCapability
5128 # objects that describe its capability bits.
5129 #
5130 # Returns: a list of GICCapability objects.
5131 #
5132 # Since: 2.6
5133 ##
5134 { 'command': 'query-gic-capabilities', 'returns': ['GICCapability'] }
5135
5136 ##
5137 # @CpuInstanceProperties:
5138 #
5139 # List of properties to be used for hotplugging a CPU instance,
5140 # it should be passed by management with device_add command when
5141 # a CPU is being hotplugged.
5142 #
5143 # @node-id: #optional NUMA node ID the CPU belongs to
5144 # @socket-id: #optional socket number within node/board the CPU belongs to
5145 # @core-id: #optional core number within socket the CPU belongs to
5146 # @thread-id: #optional thread number within core the CPU belongs to
5147 #
5148 # Note: currently there are 4 properties that could be present
5149 # but management should be prepared to pass through other
5150 # properties with device_add command to allow for future
5151 # interface extension. This also requires the filed names to be kept in
5152 # sync with the properties passed to -device/device_add.
5153 #
5154 # Since: 2.7
5155 ##
5156 { 'struct': 'CpuInstanceProperties',
5157 'data': { '*node-id': 'int',
5158 '*socket-id': 'int',
5159 '*core-id': 'int',
5160 '*thread-id': 'int'
5161 }
5162 }
5163
5164 ##
5165 # @HotpluggableCPU:
5166 #
5167 # @type: CPU object type for usage with device_add command
5168 # @props: list of properties to be used for hotplugging CPU
5169 # @vcpus-count: number of logical VCPU threads @HotpluggableCPU provides
5170 # @qom-path: #optional link to existing CPU object if CPU is present or
5171 # omitted if CPU is not present.
5172 #
5173 # Since: 2.7
5174 ##
5175 { 'struct': 'HotpluggableCPU',
5176 'data': { 'type': 'str',
5177 'vcpus-count': 'int',
5178 'props': 'CpuInstanceProperties',
5179 '*qom-path': 'str'
5180 }
5181 }
5182
5183 ##
5184 # @query-hotpluggable-cpus:
5185 #
5186 # Returns: a list of HotpluggableCPU objects.
5187 #
5188 # Since: 2.7
5189 ##
5190 { 'command': 'query-hotpluggable-cpus', 'returns': ['HotpluggableCPU'] }