xref: /openbmc/qemu/qapi/block-core.json (revision 3cad405b)
1# -*- Mode: Python -*-
2
3##
4# == Block core (VM unrelated)
5##
6
7{ 'include': 'common.json' }
8{ 'include': 'crypto.json' }
9{ 'include': 'job.json' }
10{ 'include': 'sockets.json' }
11
12##
13# @SnapshotInfo:
14#
15# @id: unique snapshot id
16#
17# @name: user chosen name
18#
19# @vm-state-size: size of the VM state
20#
21# @date-sec: UTC date of the snapshot in seconds
22#
23# @date-nsec: fractional part in nano seconds to be used with date-sec
24#
25# @vm-clock-sec: VM clock relative to boot in seconds
26#
27# @vm-clock-nsec: fractional part in nano seconds to be used with vm-clock-sec
28#
29# Since: 1.3
30#
31##
32{ 'struct': 'SnapshotInfo',
33  'data': { 'id': 'str', 'name': 'str', 'vm-state-size': 'int',
34            'date-sec': 'int', 'date-nsec': 'int',
35            'vm-clock-sec': 'int', 'vm-clock-nsec': 'int' } }
36
37##
38# @ImageInfoSpecificQCow2EncryptionBase:
39#
40# @format: The encryption format
41#
42# Since: 2.10
43##
44{ 'struct': 'ImageInfoSpecificQCow2EncryptionBase',
45  'data': { 'format': 'BlockdevQcow2EncryptionFormat'}}
46
47##
48# @ImageInfoSpecificQCow2Encryption:
49#
50# Since: 2.10
51##
52{ 'union': 'ImageInfoSpecificQCow2Encryption',
53  'base': 'ImageInfoSpecificQCow2EncryptionBase',
54  'discriminator': 'format',
55  'data': { 'luks': 'QCryptoBlockInfoLUKS' } }
56
57##
58# @ImageInfoSpecificQCow2:
59#
60# @compat: compatibility level
61#
62# @data-file: the filename of the external data file that is stored in the
63#             image and used as a default for opening the image (since: 4.0)
64#
65# @data-file-raw: True if the external data file must stay valid as a
66#                 standalone (read-only) raw image without looking at qcow2
67#                 metadata (since: 4.0)
68#
69# @lazy-refcounts: on or off; only valid for compat >= 1.1
70#
71# @corrupt: true if the image has been marked corrupt; only valid for
72#           compat >= 1.1 (since 2.2)
73#
74# @refcount-bits: width of a refcount entry in bits (since 2.3)
75#
76# @encrypt: details about encryption parameters; only set if image
77#           is encrypted (since 2.10)
78#
79# @bitmaps: A list of qcow2 bitmap details (since 4.0)
80#
81# Since: 1.7
82##
83{ 'struct': 'ImageInfoSpecificQCow2',
84  'data': {
85      'compat': 'str',
86      '*data-file': 'str',
87      '*data-file-raw': 'bool',
88      '*lazy-refcounts': 'bool',
89      '*corrupt': 'bool',
90      'refcount-bits': 'int',
91      '*encrypt': 'ImageInfoSpecificQCow2Encryption',
92      '*bitmaps': ['Qcow2BitmapInfo']
93  } }
94
95##
96# @ImageInfoSpecificVmdk:
97#
98# @create-type: The create type of VMDK image
99#
100# @cid: Content id of image
101#
102# @parent-cid: Parent VMDK image's cid
103#
104# @extents: List of extent files
105#
106# Since: 1.7
107##
108{ 'struct': 'ImageInfoSpecificVmdk',
109  'data': {
110      'create-type': 'str',
111      'cid': 'int',
112      'parent-cid': 'int',
113      'extents': ['ImageInfo']
114  } }
115
116##
117# @ImageInfoSpecific:
118#
119# A discriminated record of image format specific information structures.
120#
121# Since: 1.7
122##
123{ 'union': 'ImageInfoSpecific',
124  'data': {
125      'qcow2': 'ImageInfoSpecificQCow2',
126      'vmdk': 'ImageInfoSpecificVmdk',
127      # If we need to add block driver specific parameters for
128      # LUKS in future, then we'll subclass QCryptoBlockInfoLUKS
129      # to define a ImageInfoSpecificLUKS
130      'luks': 'QCryptoBlockInfoLUKS'
131  } }
132
133##
134# @ImageInfo:
135#
136# Information about a QEMU image file
137#
138# @filename: name of the image file
139#
140# @format: format of the image file
141#
142# @virtual-size: maximum capacity in bytes of the image
143#
144# @actual-size: actual size on disk in bytes of the image
145#
146# @dirty-flag: true if image is not cleanly closed
147#
148# @cluster-size: size of a cluster in bytes
149#
150# @encrypted: true if the image is encrypted
151#
152# @compressed: true if the image is compressed (Since 1.7)
153#
154# @backing-filename: name of the backing file
155#
156# @full-backing-filename: full path of the backing file
157#
158# @backing-filename-format: the format of the backing file
159#
160# @snapshots: list of VM snapshots
161#
162# @backing-image: info of the backing image (since 1.6)
163#
164# @format-specific: structure supplying additional format-specific
165# information (since 1.7)
166#
167# Since: 1.3
168#
169##
170{ 'struct': 'ImageInfo',
171  'data': {'filename': 'str', 'format': 'str', '*dirty-flag': 'bool',
172           '*actual-size': 'int', 'virtual-size': 'int',
173           '*cluster-size': 'int', '*encrypted': 'bool', '*compressed': 'bool',
174           '*backing-filename': 'str', '*full-backing-filename': 'str',
175           '*backing-filename-format': 'str', '*snapshots': ['SnapshotInfo'],
176           '*backing-image': 'ImageInfo',
177           '*format-specific': 'ImageInfoSpecific' } }
178
179##
180# @ImageCheck:
181#
182# Information about a QEMU image file check
183#
184# @filename: name of the image file checked
185#
186# @format: format of the image file checked
187#
188# @check-errors: number of unexpected errors occurred during check
189#
190# @image-end-offset: offset (in bytes) where the image ends, this
191#                    field is present if the driver for the image format
192#                    supports it
193#
194# @corruptions: number of corruptions found during the check if any
195#
196# @leaks: number of leaks found during the check if any
197#
198# @corruptions-fixed: number of corruptions fixed during the check
199#                     if any
200#
201# @leaks-fixed: number of leaks fixed during the check if any
202#
203# @total-clusters: total number of clusters, this field is present
204#                  if the driver for the image format supports it
205#
206# @allocated-clusters: total number of allocated clusters, this
207#                      field is present if the driver for the image format
208#                      supports it
209#
210# @fragmented-clusters: total number of fragmented clusters, this
211#                       field is present if the driver for the image format
212#                       supports it
213#
214# @compressed-clusters: total number of compressed clusters, this
215#                       field is present if the driver for the image format
216#                       supports it
217#
218# Since: 1.4
219#
220##
221{ 'struct': 'ImageCheck',
222  'data': {'filename': 'str', 'format': 'str', 'check-errors': 'int',
223           '*image-end-offset': 'int', '*corruptions': 'int', '*leaks': 'int',
224           '*corruptions-fixed': 'int', '*leaks-fixed': 'int',
225           '*total-clusters': 'int', '*allocated-clusters': 'int',
226           '*fragmented-clusters': 'int', '*compressed-clusters': 'int' } }
227
228##
229# @MapEntry:
230#
231# Mapping information from a virtual block range to a host file range
232#
233# @start: the start byte of the mapped virtual range
234#
235# @length: the number of bytes of the mapped virtual range
236#
237# @data: whether the mapped range has data
238#
239# @zero: whether the virtual blocks are zeroed
240#
241# @depth: the depth of the mapping
242#
243# @offset: the offset in file that the virtual sectors are mapped to
244#
245# @filename: filename that is referred to by @offset
246#
247# Since: 2.6
248#
249##
250{ 'struct': 'MapEntry',
251  'data': {'start': 'int', 'length': 'int', 'data': 'bool',
252           'zero': 'bool', 'depth': 'int', '*offset': 'int',
253           '*filename': 'str' } }
254
255##
256# @BlockdevCacheInfo:
257#
258# Cache mode information for a block device
259#
260# @writeback:   true if writeback mode is enabled
261# @direct:      true if the host page cache is bypassed (O_DIRECT)
262# @no-flush:    true if flush requests are ignored for the device
263#
264# Since: 2.3
265##
266{ 'struct': 'BlockdevCacheInfo',
267  'data': { 'writeback': 'bool',
268            'direct': 'bool',
269            'no-flush': 'bool' } }
270
271##
272# @BlockDeviceInfo:
273#
274# Information about the backing device for a block device.
275#
276# @file: the filename of the backing device
277#
278# @node-name: the name of the block driver node (Since 2.0)
279#
280# @ro: true if the backing device was open read-only
281#
282# @drv: the name of the block format used to open the backing device. As of
283#       0.14.0 this can be: 'blkdebug', 'bochs', 'cloop', 'cow', 'dmg',
284#       'file', 'file', 'ftp', 'ftps', 'host_cdrom', 'host_device',
285#       'http', 'https', 'luks', 'nbd', 'parallels', 'qcow',
286#       'qcow2', 'raw', 'vdi', 'vmdk', 'vpc', 'vvfat'
287#       2.2: 'archipelago' added, 'cow' dropped
288#       2.3: 'host_floppy' deprecated
289#       2.5: 'host_floppy' dropped
290#       2.6: 'luks' added
291#       2.8: 'replication' added, 'tftp' dropped
292#       2.9: 'archipelago' dropped
293#
294# @backing_file: the name of the backing file (for copy-on-write)
295#
296# @backing_file_depth: number of files in the backing file chain (since: 1.2)
297#
298# @encrypted: true if the backing device is encrypted
299#
300# @encryption_key_missing: Deprecated; always false
301#
302# @detect_zeroes: detect and optimize zero writes (Since 2.1)
303#
304# @bps: total throughput limit in bytes per second is specified
305#
306# @bps_rd: read throughput limit in bytes per second is specified
307#
308# @bps_wr: write throughput limit in bytes per second is specified
309#
310# @iops: total I/O operations per second is specified
311#
312# @iops_rd: read I/O operations per second is specified
313#
314# @iops_wr: write I/O operations per second is specified
315#
316# @image: the info of image used (since: 1.6)
317#
318# @bps_max: total throughput limit during bursts,
319#                     in bytes (Since 1.7)
320#
321# @bps_rd_max: read throughput limit during bursts,
322#                        in bytes (Since 1.7)
323#
324# @bps_wr_max: write throughput limit during bursts,
325#                        in bytes (Since 1.7)
326#
327# @iops_max: total I/O operations per second during bursts,
328#                      in bytes (Since 1.7)
329#
330# @iops_rd_max: read I/O operations per second during bursts,
331#                         in bytes (Since 1.7)
332#
333# @iops_wr_max: write I/O operations per second during bursts,
334#                         in bytes (Since 1.7)
335#
336# @bps_max_length: maximum length of the @bps_max burst
337#                            period, in seconds. (Since 2.6)
338#
339# @bps_rd_max_length: maximum length of the @bps_rd_max
340#                               burst period, in seconds. (Since 2.6)
341#
342# @bps_wr_max_length: maximum length of the @bps_wr_max
343#                               burst period, in seconds. (Since 2.6)
344#
345# @iops_max_length: maximum length of the @iops burst
346#                             period, in seconds. (Since 2.6)
347#
348# @iops_rd_max_length: maximum length of the @iops_rd_max
349#                                burst period, in seconds. (Since 2.6)
350#
351# @iops_wr_max_length: maximum length of the @iops_wr_max
352#                                burst period, in seconds. (Since 2.6)
353#
354# @iops_size: an I/O size in bytes (Since 1.7)
355#
356# @group: throttle group name (Since 2.4)
357#
358# @cache: the cache mode used for the block device (since: 2.3)
359#
360# @write_threshold: configured write threshold for the device.
361#                   0 if disabled. (Since 2.3)
362#
363# @dirty-bitmaps: dirty bitmaps information (only present if node
364#                 has one or more dirty bitmaps) (Since 4.2)
365#
366# Since: 0.14.0
367#
368##
369{ 'struct': 'BlockDeviceInfo',
370  'data': { 'file': 'str', '*node-name': 'str', 'ro': 'bool', 'drv': 'str',
371            '*backing_file': 'str', 'backing_file_depth': 'int',
372            'encrypted': 'bool', 'encryption_key_missing': 'bool',
373            'detect_zeroes': 'BlockdevDetectZeroesOptions',
374            'bps': 'int', 'bps_rd': 'int', 'bps_wr': 'int',
375            'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
376            'image': 'ImageInfo',
377            '*bps_max': 'int', '*bps_rd_max': 'int',
378            '*bps_wr_max': 'int', '*iops_max': 'int',
379            '*iops_rd_max': 'int', '*iops_wr_max': 'int',
380            '*bps_max_length': 'int', '*bps_rd_max_length': 'int',
381            '*bps_wr_max_length': 'int', '*iops_max_length': 'int',
382            '*iops_rd_max_length': 'int', '*iops_wr_max_length': 'int',
383            '*iops_size': 'int', '*group': 'str', 'cache': 'BlockdevCacheInfo',
384            'write_threshold': 'int', '*dirty-bitmaps': ['BlockDirtyInfo'] } }
385
386##
387# @BlockDeviceIoStatus:
388#
389# An enumeration of block device I/O status.
390#
391# @ok: The last I/O operation has succeeded
392#
393# @failed: The last I/O operation has failed
394#
395# @nospace: The last I/O operation has failed due to a no-space condition
396#
397# Since: 1.0
398##
399{ 'enum': 'BlockDeviceIoStatus', 'data': [ 'ok', 'failed', 'nospace' ] }
400
401##
402# @BlockDeviceMapEntry:
403#
404# Entry in the metadata map of the device (returned by "qemu-img map")
405#
406# @start: Offset in the image of the first byte described by this entry
407#         (in bytes)
408#
409# @length: Length of the range described by this entry (in bytes)
410#
411# @depth: Number of layers (0 = top image, 1 = top image's backing file, etc.)
412#         before reaching one for which the range is allocated.  The value is
413#         in the range 0 to the depth of the image chain - 1.
414#
415# @zero: the sectors in this range read as zeros
416#
417# @data: reading the image will actually read data from a file (in particular,
418#        if @offset is present this means that the sectors are not simply
419#        preallocated, but contain actual data in raw format)
420#
421# @offset: if present, the image file stores the data for this range in
422#          raw format at the given offset.
423#
424# Since: 1.7
425##
426{ 'struct': 'BlockDeviceMapEntry',
427  'data': { 'start': 'int', 'length': 'int', 'depth': 'int', 'zero': 'bool',
428            'data': 'bool', '*offset': 'int' } }
429
430##
431# @DirtyBitmapStatus:
432#
433# An enumeration of possible states that a dirty bitmap can report to the user.
434#
435# @frozen: The bitmap is currently in-use by some operation and is immutable.
436#          If the bitmap was @active prior to the operation, new writes by the
437#          guest are being recorded in a temporary buffer, and will not be lost.
438#          Generally, bitmaps are cleared on successful use in an operation and
439#          the temporary buffer is committed into the bitmap. On failure, the
440#          temporary buffer is merged back into the bitmap without first
441#          clearing it.
442#          Please refer to the documentation for each bitmap-using operation,
443#          See also @blockdev-backup, @drive-backup.
444#
445# @disabled: The bitmap is not currently recording new writes by the guest.
446#            This is requested explicitly via @block-dirty-bitmap-disable.
447#            It can still be cleared, deleted, or used for backup operations.
448#
449# @active: The bitmap is actively monitoring for new writes, and can be cleared,
450#          deleted, or used for backup operations.
451#
452# @locked: The bitmap is currently in-use by some operation and is immutable.
453#          If the bitmap was @active prior to the operation, it is still
454#          recording new writes. If the bitmap was @disabled, it is not
455#          recording new writes. (Since 2.12)
456#
457# @inconsistent: This is a persistent dirty bitmap that was marked in-use on
458#                disk, and is unusable by QEMU. It can only be deleted.
459#                Please rely on the inconsistent field in @BlockDirtyInfo
460#                instead, as the status field is deprecated. (Since 4.0)
461#
462# Since: 2.4
463##
464{ 'enum': 'DirtyBitmapStatus',
465  'data': ['active', 'disabled', 'frozen', 'locked', 'inconsistent'] }
466
467##
468# @BlockDirtyInfo:
469#
470# Block dirty bitmap information.
471#
472# @name: the name of the dirty bitmap (Since 2.4)
473#
474# @count: number of dirty bytes according to the dirty bitmap
475#
476# @granularity: granularity of the dirty bitmap in bytes (since 1.4)
477#
478# @status: Deprecated in favor of @recording and @locked. (since 2.4)
479#
480# @recording: true if the bitmap is recording new writes from the guest.
481#             Replaces `active` and `disabled` statuses. (since 4.0)
482#
483# @busy: true if the bitmap is in-use by some operation (NBD or jobs)
484#        and cannot be modified via QMP or used by another operation.
485#        Replaces `locked` and `frozen` statuses. (since 4.0)
486#
487# @persistent: true if the bitmap was stored on disk, is scheduled to be stored
488#              on disk, or both. (since 4.0)
489#
490# @inconsistent: true if this is a persistent bitmap that was improperly
491#                stored. Implies @persistent to be true; @recording and
492#                @busy to be false. This bitmap cannot be used. To remove
493#                it, use @block-dirty-bitmap-remove. (Since 4.0)
494#
495# Since: 1.3
496##
497{ 'struct': 'BlockDirtyInfo',
498  'data': {'*name': 'str', 'count': 'int', 'granularity': 'uint32',
499           'recording': 'bool', 'busy': 'bool', 'status': 'DirtyBitmapStatus',
500           'persistent': 'bool', '*inconsistent': 'bool' } }
501
502##
503# @Qcow2BitmapInfoFlags:
504#
505# An enumeration of flags that a bitmap can report to the user.
506#
507# @in-use: This flag is set by any process actively modifying the qcow2 file,
508#          and cleared when the updated bitmap is flushed to the qcow2 image.
509#          The presence of this flag in an offline image means that the bitmap
510#          was not saved correctly after its last usage, and may contain
511#          inconsistent data.
512#
513# @auto: The bitmap must reflect all changes of the virtual disk by any
514#        application that would write to this qcow2 file.
515#
516# Since: 4.0
517##
518{ 'enum': 'Qcow2BitmapInfoFlags',
519  'data': ['in-use', 'auto'] }
520
521##
522# @Qcow2BitmapInfo:
523#
524# Qcow2 bitmap information.
525#
526# @name: the name of the bitmap
527#
528# @granularity: granularity of the bitmap in bytes
529#
530# @flags: flags of the bitmap
531#
532# Since: 4.0
533##
534{ 'struct': 'Qcow2BitmapInfo',
535  'data': {'name': 'str', 'granularity': 'uint32',
536           'flags': ['Qcow2BitmapInfoFlags'] } }
537
538##
539# @BlockLatencyHistogramInfo:
540#
541# Block latency histogram.
542#
543# @boundaries: list of interval boundary values in nanoseconds, all greater
544#              than zero and in ascending order.
545#              For example, the list [10, 50, 100] produces the following
546#              histogram intervals: [0, 10), [10, 50), [50, 100), [100, +inf).
547#
548# @bins: list of io request counts corresponding to histogram intervals.
549#        len(@bins) = len(@boundaries) + 1
550#        For the example above, @bins may be something like [3, 1, 5, 2],
551#        and corresponding histogram looks like:
552#
553#        5|           *
554#        4|           *
555#        3| *         *
556#        2| *         *    *
557#        1| *    *    *    *
558#         +------------------
559#             10   50   100
560#
561# Since: 4.0
562##
563{ 'struct': 'BlockLatencyHistogramInfo',
564  'data': {'boundaries': ['uint64'], 'bins': ['uint64'] } }
565
566##
567# @block-latency-histogram-set:
568#
569# Manage read, write and flush latency histograms for the device.
570#
571# If only @id parameter is specified, remove all present latency histograms
572# for the device. Otherwise, add/reset some of (or all) latency histograms.
573#
574# @id: The name or QOM path of the guest device.
575#
576# @boundaries: list of interval boundary values (see description in
577#              BlockLatencyHistogramInfo definition). If specified, all
578#              latency histograms are removed, and empty ones created for all
579#              io types with intervals corresponding to @boundaries (except for
580#              io types, for which specific boundaries are set through the
581#              following parameters).
582#
583# @boundaries-read: list of interval boundary values for read latency
584#                   histogram. If specified, old read latency histogram is
585#                   removed, and empty one created with intervals
586#                   corresponding to @boundaries-read. The parameter has higher
587#                   priority then @boundaries.
588#
589# @boundaries-write: list of interval boundary values for write latency
590#                    histogram.
591#
592# @boundaries-flush: list of interval boundary values for flush latency
593#                    histogram.
594#
595# Returns: error if device is not found or any boundary arrays are invalid.
596#
597# Since: 4.0
598#
599# Example: set new histograms for all io types with intervals
600# [0, 10), [10, 50), [50, 100), [100, +inf):
601#
602# -> { "execute": "block-latency-histogram-set",
603#      "arguments": { "id": "drive0",
604#                     "boundaries": [10, 50, 100] } }
605# <- { "return": {} }
606#
607# Example: set new histogram only for write, other histograms will remain
608# not changed (or not created):
609#
610# -> { "execute": "block-latency-histogram-set",
611#      "arguments": { "id": "drive0",
612#                     "boundaries-write": [10, 50, 100] } }
613# <- { "return": {} }
614#
615# Example: set new histograms with the following intervals:
616#   read, flush: [0, 10), [10, 50), [50, 100), [100, +inf)
617#   write: [0, 1000), [1000, 5000), [5000, +inf)
618#
619# -> { "execute": "block-latency-histogram-set",
620#      "arguments": { "id": "drive0",
621#                     "boundaries": [10, 50, 100],
622#                     "boundaries-write": [1000, 5000] } }
623# <- { "return": {} }
624#
625# Example: remove all latency histograms:
626#
627# -> { "execute": "block-latency-histogram-set",
628#      "arguments": { "id": "drive0" } }
629# <- { "return": {} }
630##
631{ 'command': 'block-latency-histogram-set',
632  'data': {'id': 'str',
633           '*boundaries': ['uint64'],
634           '*boundaries-read': ['uint64'],
635           '*boundaries-write': ['uint64'],
636           '*boundaries-flush': ['uint64'] } }
637
638##
639# @BlockInfo:
640#
641# Block device information.  This structure describes a virtual device and
642# the backing device associated with it.
643#
644# @device: The device name associated with the virtual device.
645#
646# @qdev: The qdev ID, or if no ID is assigned, the QOM path of the block
647#        device. (since 2.10)
648#
649# @type: This field is returned only for compatibility reasons, it should
650#        not be used (always returns 'unknown')
651#
652# @removable: True if the device supports removable media.
653#
654# @locked: True if the guest has locked this device from having its media
655#          removed
656#
657# @tray_open: True if the device's tray is open
658#             (only present if it has a tray)
659#
660# @dirty-bitmaps: dirty bitmaps information (only present if the
661#                 driver has one or more dirty bitmaps) (Since 2.0)
662#                 Deprecated in 4.2; see BlockDeviceInfo instead.
663#
664# @io-status: @BlockDeviceIoStatus. Only present if the device
665#             supports it and the VM is configured to stop on errors
666#             (supported device models: virtio-blk, IDE, SCSI except
667#             scsi-generic)
668#
669# @inserted: @BlockDeviceInfo describing the device if media is
670#            present
671#
672# Since:  0.14.0
673##
674{ 'struct': 'BlockInfo',
675  'data': {'device': 'str', '*qdev': 'str', 'type': 'str', 'removable': 'bool',
676           'locked': 'bool', '*inserted': 'BlockDeviceInfo',
677           '*tray_open': 'bool', '*io-status': 'BlockDeviceIoStatus',
678           '*dirty-bitmaps': ['BlockDirtyInfo'] } }
679
680##
681# @BlockMeasureInfo:
682#
683# Image file size calculation information.  This structure describes the size
684# requirements for creating a new image file.
685#
686# The size requirements depend on the new image file format.  File size always
687# equals virtual disk size for the 'raw' format, even for sparse POSIX files.
688# Compact formats such as 'qcow2' represent unallocated and zero regions
689# efficiently so file size may be smaller than virtual disk size.
690#
691# The values are upper bounds that are guaranteed to fit the new image file.
692# Subsequent modification, such as internal snapshot or bitmap creation, may
693# require additional space and is not covered here.
694#
695# @required: Size required for a new image file, in bytes.
696#
697# @fully-allocated: Image file size, in bytes, once data has been written
698#                   to all sectors.
699#
700# Since: 2.10
701##
702{ 'struct': 'BlockMeasureInfo',
703  'data': {'required': 'int', 'fully-allocated': 'int'} }
704
705##
706# @query-block:
707#
708# Get a list of BlockInfo for all virtual block devices.
709#
710# Returns: a list of @BlockInfo describing each virtual block device. Filter
711# nodes that were created implicitly are skipped over.
712#
713# Since: 0.14.0
714#
715# Example:
716#
717# -> { "execute": "query-block" }
718# <- {
719#       "return":[
720#          {
721#             "io-status": "ok",
722#             "device":"ide0-hd0",
723#             "locked":false,
724#             "removable":false,
725#             "inserted":{
726#                "ro":false,
727#                "drv":"qcow2",
728#                "encrypted":false,
729#                "file":"disks/test.qcow2",
730#                "backing_file_depth":1,
731#                "bps":1000000,
732#                "bps_rd":0,
733#                "bps_wr":0,
734#                "iops":1000000,
735#                "iops_rd":0,
736#                "iops_wr":0,
737#                "bps_max": 8000000,
738#                "bps_rd_max": 0,
739#                "bps_wr_max": 0,
740#                "iops_max": 0,
741#                "iops_rd_max": 0,
742#                "iops_wr_max": 0,
743#                "iops_size": 0,
744#                "detect_zeroes": "on",
745#                "write_threshold": 0,
746#                "image":{
747#                   "filename":"disks/test.qcow2",
748#                   "format":"qcow2",
749#                   "virtual-size":2048000,
750#                   "backing_file":"base.qcow2",
751#                   "full-backing-filename":"disks/base.qcow2",
752#                   "backing-filename-format":"qcow2",
753#                   "snapshots":[
754#                      {
755#                         "id": "1",
756#                         "name": "snapshot1",
757#                         "vm-state-size": 0,
758#                         "date-sec": 10000200,
759#                         "date-nsec": 12,
760#                         "vm-clock-sec": 206,
761#                         "vm-clock-nsec": 30
762#                      }
763#                   ],
764#                   "backing-image":{
765#                       "filename":"disks/base.qcow2",
766#                       "format":"qcow2",
767#                       "virtual-size":2048000
768#                   }
769#                }
770#             },
771#             "qdev": "ide_disk",
772#             "type":"unknown"
773#          },
774#          {
775#             "io-status": "ok",
776#             "device":"ide1-cd0",
777#             "locked":false,
778#             "removable":true,
779#             "qdev": "/machine/unattached/device[23]",
780#             "tray_open": false,
781#             "type":"unknown"
782#          },
783#          {
784#             "device":"floppy0",
785#             "locked":false,
786#             "removable":true,
787#             "qdev": "/machine/unattached/device[20]",
788#             "type":"unknown"
789#          },
790#          {
791#             "device":"sd0",
792#             "locked":false,
793#             "removable":true,
794#             "type":"unknown"
795#          }
796#       ]
797#    }
798#
799##
800{ 'command': 'query-block', 'returns': ['BlockInfo'] }
801
802
803##
804# @BlockDeviceTimedStats:
805#
806# Statistics of a block device during a given interval of time.
807#
808# @interval_length: Interval used for calculating the statistics,
809#                   in seconds.
810#
811# @min_rd_latency_ns: Minimum latency of read operations in the
812#                     defined interval, in nanoseconds.
813#
814# @min_wr_latency_ns: Minimum latency of write operations in the
815#                     defined interval, in nanoseconds.
816#
817# @min_flush_latency_ns: Minimum latency of flush operations in the
818#                        defined interval, in nanoseconds.
819#
820# @max_rd_latency_ns: Maximum latency of read operations in the
821#                     defined interval, in nanoseconds.
822#
823# @max_wr_latency_ns: Maximum latency of write operations in the
824#                     defined interval, in nanoseconds.
825#
826# @max_flush_latency_ns: Maximum latency of flush operations in the
827#                        defined interval, in nanoseconds.
828#
829# @avg_rd_latency_ns: Average latency of read operations in the
830#                     defined interval, in nanoseconds.
831#
832# @avg_wr_latency_ns: Average latency of write operations in the
833#                     defined interval, in nanoseconds.
834#
835# @avg_flush_latency_ns: Average latency of flush operations in the
836#                        defined interval, in nanoseconds.
837#
838# @avg_rd_queue_depth: Average number of pending read operations
839#                      in the defined interval.
840#
841# @avg_wr_queue_depth: Average number of pending write operations
842#                      in the defined interval.
843#
844# Since: 2.5
845##
846{ 'struct': 'BlockDeviceTimedStats',
847  'data': { 'interval_length': 'int', 'min_rd_latency_ns': 'int',
848            'max_rd_latency_ns': 'int', 'avg_rd_latency_ns': 'int',
849            'min_wr_latency_ns': 'int', 'max_wr_latency_ns': 'int',
850            'avg_wr_latency_ns': 'int', 'min_flush_latency_ns': 'int',
851            'max_flush_latency_ns': 'int', 'avg_flush_latency_ns': 'int',
852            'avg_rd_queue_depth': 'number', 'avg_wr_queue_depth': 'number' } }
853
854##
855# @BlockDeviceStats:
856#
857# Statistics of a virtual block device or a block backing device.
858#
859# @rd_bytes:      The number of bytes read by the device.
860#
861# @wr_bytes:      The number of bytes written by the device.
862#
863# @unmap_bytes: The number of bytes unmapped by the device (Since 4.2)
864#
865# @rd_operations: The number of read operations performed by the device.
866#
867# @wr_operations: The number of write operations performed by the device.
868#
869# @flush_operations: The number of cache flush operations performed by the
870#                    device (since 0.15.0)
871#
872# @unmap_operations: The number of unmap operations performed by the device
873#                    (Since 4.2)
874#
875# @rd_total_time_ns: Total time spent on reads in nanoseconds (since 0.15.0).
876#
877# @wr_total_time_ns: Total time spent on writes in nanoseconds (since 0.15.0).
878#
879# @flush_total_time_ns: Total time spent on cache flushes in nanoseconds
880#                       (since 0.15.0).
881#
882# @unmap_total_time_ns: Total time spent on unmap operations in nanoseconds
883#                       (Since 4.2)
884#
885# @wr_highest_offset: The offset after the greatest byte written to the
886#                     device.  The intended use of this information is for
887#                     growable sparse files (like qcow2) that are used on top
888#                     of a physical device.
889#
890# @rd_merged: Number of read requests that have been merged into another
891#             request (Since 2.3).
892#
893# @wr_merged: Number of write requests that have been merged into another
894#             request (Since 2.3).
895#
896# @unmap_merged: Number of unmap requests that have been merged into another
897#                request (Since 4.2)
898#
899# @idle_time_ns: Time since the last I/O operation, in
900#                nanoseconds. If the field is absent it means that
901#                there haven't been any operations yet (Since 2.5).
902#
903# @failed_rd_operations: The number of failed read operations
904#                        performed by the device (Since 2.5)
905#
906# @failed_wr_operations: The number of failed write operations
907#                        performed by the device (Since 2.5)
908#
909# @failed_flush_operations: The number of failed flush operations
910#                           performed by the device (Since 2.5)
911#
912# @failed_unmap_operations: The number of failed unmap operations performed
913#                           by the device (Since 4.2)
914#
915# @invalid_rd_operations: The number of invalid read operations
916#                          performed by the device (Since 2.5)
917#
918# @invalid_wr_operations: The number of invalid write operations
919#                         performed by the device (Since 2.5)
920#
921# @invalid_flush_operations: The number of invalid flush operations
922#                            performed by the device (Since 2.5)
923#
924# @invalid_unmap_operations: The number of invalid unmap operations performed
925#                            by the device (Since 4.2)
926#
927# @account_invalid: Whether invalid operations are included in the
928#                   last access statistics (Since 2.5)
929#
930# @account_failed: Whether failed operations are included in the
931#                  latency and last access statistics (Since 2.5)
932#
933# @timed_stats: Statistics specific to the set of previously defined
934#               intervals of time (Since 2.5)
935#
936# @rd_latency_histogram: @BlockLatencyHistogramInfo. (Since 4.0)
937#
938# @wr_latency_histogram: @BlockLatencyHistogramInfo. (Since 4.0)
939#
940# @flush_latency_histogram: @BlockLatencyHistogramInfo. (Since 4.0)
941#
942# Since: 0.14.0
943##
944{ 'struct': 'BlockDeviceStats',
945  'data': {'rd_bytes': 'int', 'wr_bytes': 'int', 'unmap_bytes' : 'int',
946           'rd_operations': 'int', 'wr_operations': 'int',
947           'flush_operations': 'int', 'unmap_operations': 'int',
948           'rd_total_time_ns': 'int', 'wr_total_time_ns': 'int',
949           'flush_total_time_ns': 'int', 'unmap_total_time_ns': 'int',
950           'wr_highest_offset': 'int',
951           'rd_merged': 'int', 'wr_merged': 'int', 'unmap_merged': 'int',
952           '*idle_time_ns': 'int',
953           'failed_rd_operations': 'int', 'failed_wr_operations': 'int',
954           'failed_flush_operations': 'int', 'failed_unmap_operations': 'int',
955           'invalid_rd_operations': 'int', 'invalid_wr_operations': 'int',
956           'invalid_flush_operations': 'int', 'invalid_unmap_operations': 'int',
957           'account_invalid': 'bool', 'account_failed': 'bool',
958           'timed_stats': ['BlockDeviceTimedStats'],
959           '*rd_latency_histogram': 'BlockLatencyHistogramInfo',
960           '*wr_latency_histogram': 'BlockLatencyHistogramInfo',
961           '*flush_latency_histogram': 'BlockLatencyHistogramInfo' } }
962
963##
964# @BlockStatsSpecificFile:
965#
966# File driver statistics
967#
968# @discard-nb-ok: The number of successful discard operations performed by
969#                 the driver.
970#
971# @discard-nb-failed: The number of failed discard operations performed by
972#                     the driver.
973#
974# @discard-bytes-ok: The number of bytes discarded by the driver.
975#
976# Since: 4.2
977##
978{ 'struct': 'BlockStatsSpecificFile',
979  'data': {
980      'discard-nb-ok': 'uint64',
981      'discard-nb-failed': 'uint64',
982      'discard-bytes-ok': 'uint64' } }
983
984##
985# @BlockStatsSpecific:
986#
987# Block driver specific statistics
988#
989# Since: 4.2
990##
991{ 'union': 'BlockStatsSpecific',
992  'base': { 'driver': 'BlockdevDriver' },
993  'discriminator': 'driver',
994  'data': {
995      'file': 'BlockStatsSpecificFile',
996      'host_device': 'BlockStatsSpecificFile' } }
997
998##
999# @BlockStats:
1000#
1001# Statistics of a virtual block device or a block backing device.
1002#
1003# @device: If the stats are for a virtual block device, the name
1004#          corresponding to the virtual block device.
1005#
1006# @node-name: The node name of the device. (Since 2.3)
1007#
1008# @qdev: The qdev ID, or if no ID is assigned, the QOM path of the block
1009#        device. (since 3.0)
1010#
1011# @stats:  A @BlockDeviceStats for the device.
1012#
1013# @driver-specific: Optional driver-specific stats. (Since 4.2)
1014#
1015# @parent: This describes the file block device if it has one.
1016#          Contains recursively the statistics of the underlying
1017#          protocol (e.g. the host file for a qcow2 image). If there is
1018#          no underlying protocol, this field is omitted
1019#
1020# @backing: This describes the backing block device if it has one.
1021#           (Since 2.0)
1022#
1023# Since: 0.14.0
1024##
1025{ 'struct': 'BlockStats',
1026  'data': {'*device': 'str', '*qdev': 'str', '*node-name': 'str',
1027           'stats': 'BlockDeviceStats',
1028           '*driver-specific': 'BlockStatsSpecific',
1029           '*parent': 'BlockStats',
1030           '*backing': 'BlockStats'} }
1031
1032##
1033# @query-blockstats:
1034#
1035# Query the @BlockStats for all virtual block devices.
1036#
1037# @query-nodes: If true, the command will query all the block nodes
1038#               that have a node name, in a list which will include "parent"
1039#               information, but not "backing".
1040#               If false or omitted, the behavior is as before - query all the
1041#               device backends, recursively including their "parent" and
1042#               "backing". Filter nodes that were created implicitly are
1043#               skipped over in this mode. (Since 2.3)
1044#
1045# Returns: A list of @BlockStats for each virtual block devices.
1046#
1047# Since: 0.14.0
1048#
1049# Example:
1050#
1051# -> { "execute": "query-blockstats" }
1052# <- {
1053#       "return":[
1054#          {
1055#             "device":"ide0-hd0",
1056#             "parent":{
1057#                "stats":{
1058#                   "wr_highest_offset":3686448128,
1059#                   "wr_bytes":9786368,
1060#                   "wr_operations":751,
1061#                   "rd_bytes":122567168,
1062#                   "rd_operations":36772
1063#                   "wr_total_times_ns":313253456
1064#                   "rd_total_times_ns":3465673657
1065#                   "flush_total_times_ns":49653
1066#                   "flush_operations":61,
1067#                   "rd_merged":0,
1068#                   "wr_merged":0,
1069#                   "idle_time_ns":2953431879,
1070#                   "account_invalid":true,
1071#                   "account_failed":false
1072#                }
1073#             },
1074#             "stats":{
1075#                "wr_highest_offset":2821110784,
1076#                "wr_bytes":9786368,
1077#                "wr_operations":692,
1078#                "rd_bytes":122739200,
1079#                "rd_operations":36604
1080#                "flush_operations":51,
1081#                "wr_total_times_ns":313253456
1082#                "rd_total_times_ns":3465673657
1083#                "flush_total_times_ns":49653,
1084#                "rd_merged":0,
1085#                "wr_merged":0,
1086#                "idle_time_ns":2953431879,
1087#                "account_invalid":true,
1088#                "account_failed":false
1089#             },
1090#             "qdev": "/machine/unattached/device[23]"
1091#          },
1092#          {
1093#             "device":"ide1-cd0",
1094#             "stats":{
1095#                "wr_highest_offset":0,
1096#                "wr_bytes":0,
1097#                "wr_operations":0,
1098#                "rd_bytes":0,
1099#                "rd_operations":0
1100#                "flush_operations":0,
1101#                "wr_total_times_ns":0
1102#                "rd_total_times_ns":0
1103#                "flush_total_times_ns":0,
1104#                "rd_merged":0,
1105#                "wr_merged":0,
1106#                "account_invalid":false,
1107#                "account_failed":false
1108#             },
1109#             "qdev": "/machine/unattached/device[24]"
1110#          },
1111#          {
1112#             "device":"floppy0",
1113#             "stats":{
1114#                "wr_highest_offset":0,
1115#                "wr_bytes":0,
1116#                "wr_operations":0,
1117#                "rd_bytes":0,
1118#                "rd_operations":0
1119#                "flush_operations":0,
1120#                "wr_total_times_ns":0
1121#                "rd_total_times_ns":0
1122#                "flush_total_times_ns":0,
1123#                "rd_merged":0,
1124#                "wr_merged":0,
1125#                "account_invalid":false,
1126#                "account_failed":false
1127#             },
1128#             "qdev": "/machine/unattached/device[16]"
1129#          },
1130#          {
1131#             "device":"sd0",
1132#             "stats":{
1133#                "wr_highest_offset":0,
1134#                "wr_bytes":0,
1135#                "wr_operations":0,
1136#                "rd_bytes":0,
1137#                "rd_operations":0
1138#                "flush_operations":0,
1139#                "wr_total_times_ns":0
1140#                "rd_total_times_ns":0
1141#                "flush_total_times_ns":0,
1142#                "rd_merged":0,
1143#                "wr_merged":0,
1144#                "account_invalid":false,
1145#                "account_failed":false
1146#             }
1147#          }
1148#       ]
1149#    }
1150#
1151##
1152{ 'command': 'query-blockstats',
1153  'data': { '*query-nodes': 'bool' },
1154  'returns': ['BlockStats'] }
1155
1156##
1157# @BlockdevOnError:
1158#
1159# An enumeration of possible behaviors for errors on I/O operations.
1160# The exact meaning depends on whether the I/O was initiated by a guest
1161# or by a block job
1162#
1163# @report: for guest operations, report the error to the guest;
1164#          for jobs, cancel the job
1165#
1166# @ignore: ignore the error, only report a QMP event (BLOCK_IO_ERROR
1167#          or BLOCK_JOB_ERROR)
1168#
1169# @enospc: same as @stop on ENOSPC, same as @report otherwise.
1170#
1171# @stop: for guest operations, stop the virtual machine;
1172#        for jobs, pause the job
1173#
1174# @auto: inherit the error handling policy of the backend (since: 2.7)
1175#
1176# Since: 1.3
1177##
1178{ 'enum': 'BlockdevOnError',
1179  'data': ['report', 'ignore', 'enospc', 'stop', 'auto'] }
1180
1181##
1182# @MirrorSyncMode:
1183#
1184# An enumeration of possible behaviors for the initial synchronization
1185# phase of storage mirroring.
1186#
1187# @top: copies data in the topmost image to the destination
1188#
1189# @full: copies data from all images to the destination
1190#
1191# @none: only copy data written from now on
1192#
1193# @incremental: only copy data described by the dirty bitmap. (since: 2.4)
1194#
1195# @bitmap: only copy data described by the dirty bitmap. (since: 4.2)
1196#          Behavior on completion is determined by the BitmapSyncMode.
1197#
1198# Since: 1.3
1199##
1200{ 'enum': 'MirrorSyncMode',
1201  'data': ['top', 'full', 'none', 'incremental', 'bitmap'] }
1202
1203##
1204# @BitmapSyncMode:
1205#
1206# An enumeration of possible behaviors for the synchronization of a bitmap
1207# when used for data copy operations.
1208#
1209# @on-success: The bitmap is only synced when the operation is successful.
1210#              This is the behavior always used for 'INCREMENTAL' backups.
1211#
1212# @never: The bitmap is never synchronized with the operation, and is
1213#         treated solely as a read-only manifest of blocks to copy.
1214#
1215# @always: The bitmap is always synchronized with the operation,
1216#          regardless of whether or not the operation was successful.
1217#
1218# Since: 4.2
1219##
1220{ 'enum': 'BitmapSyncMode',
1221  'data': ['on-success', 'never', 'always'] }
1222
1223##
1224# @MirrorCopyMode:
1225#
1226# An enumeration whose values tell the mirror block job when to
1227# trigger writes to the target.
1228#
1229# @background: copy data in background only.
1230#
1231# @write-blocking: when data is written to the source, write it
1232#                  (synchronously) to the target as well.  In
1233#                  addition, data is copied in background just like in
1234#                  @background mode.
1235#
1236# Since: 3.0
1237##
1238{ 'enum': 'MirrorCopyMode',
1239  'data': ['background', 'write-blocking'] }
1240
1241##
1242# @BlockJobInfo:
1243#
1244# Information about a long-running block device operation.
1245#
1246# @type: the job type ('stream' for image streaming)
1247#
1248# @device: The job identifier. Originally the device name but other
1249#          values are allowed since QEMU 2.7
1250#
1251# @len: Estimated @offset value at the completion of the job. This value can
1252#       arbitrarily change while the job is running, in both directions.
1253#
1254# @offset: Progress made until now. The unit is arbitrary and the value can
1255#          only meaningfully be used for the ratio of @offset to @len. The
1256#          value is monotonically increasing.
1257#
1258# @busy: false if the job is known to be in a quiescent state, with
1259#        no pending I/O.  Since 1.3.
1260#
1261# @paused: whether the job is paused or, if @busy is true, will
1262#          pause itself as soon as possible.  Since 1.3.
1263#
1264# @speed: the rate limit, bytes per second
1265#
1266# @io-status: the status of the job (since 1.3)
1267#
1268# @ready: true if the job may be completed (since 2.2)
1269#
1270# @status: Current job state/status (since 2.12)
1271#
1272# @auto-finalize: Job will finalize itself when PENDING, moving to
1273#                 the CONCLUDED state. (since 2.12)
1274#
1275# @auto-dismiss: Job will dismiss itself when CONCLUDED, moving to the NULL
1276#                state and disappearing from the query list. (since 2.12)
1277#
1278# @error: Error information if the job did not complete successfully.
1279#         Not set if the job completed successfully. (since 2.12.1)
1280#
1281# Since: 1.1
1282##
1283{ 'struct': 'BlockJobInfo',
1284  'data': {'type': 'str', 'device': 'str', 'len': 'int',
1285           'offset': 'int', 'busy': 'bool', 'paused': 'bool', 'speed': 'int',
1286           'io-status': 'BlockDeviceIoStatus', 'ready': 'bool',
1287           'status': 'JobStatus',
1288           'auto-finalize': 'bool', 'auto-dismiss': 'bool',
1289           '*error': 'str' } }
1290
1291##
1292# @query-block-jobs:
1293#
1294# Return information about long-running block device operations.
1295#
1296# Returns: a list of @BlockJobInfo for each active block job
1297#
1298# Since: 1.1
1299##
1300{ 'command': 'query-block-jobs', 'returns': ['BlockJobInfo'] }
1301
1302##
1303# @block_passwd:
1304#
1305# This command sets the password of a block device that has not been open
1306# with a password and requires one.
1307#
1308# This command is now obsolete and will always return an error since 2.10
1309#
1310##
1311{ 'command': 'block_passwd',
1312  'data': { '*device': 'str',
1313            '*node-name': 'str',
1314            'password': 'str' } }
1315
1316##
1317# @block_resize:
1318#
1319# Resize a block image while a guest is running.
1320#
1321# Either @device or @node-name must be set but not both.
1322#
1323# @device: the name of the device to get the image resized
1324#
1325# @node-name: graph node name to get the image resized (Since 2.0)
1326#
1327# @size:  new image size in bytes
1328#
1329# Returns: nothing on success
1330#          If @device is not a valid block device, DeviceNotFound
1331#
1332# Since: 0.14.0
1333#
1334# Example:
1335#
1336# -> { "execute": "block_resize",
1337#      "arguments": { "device": "scratch", "size": 1073741824 } }
1338# <- { "return": {} }
1339#
1340##
1341{ 'command': 'block_resize',
1342  'data': { '*device': 'str',
1343            '*node-name': 'str',
1344            'size': 'int' } }
1345
1346##
1347# @NewImageMode:
1348#
1349# An enumeration that tells QEMU how to set the backing file path in
1350# a new image file.
1351#
1352# @existing: QEMU should look for an existing image file.
1353#
1354# @absolute-paths: QEMU should create a new image with absolute paths
1355# for the backing file. If there is no backing file available, the new
1356# image will not be backed either.
1357#
1358# Since: 1.1
1359##
1360{ 'enum': 'NewImageMode',
1361  'data': [ 'existing', 'absolute-paths' ] }
1362
1363##
1364# @BlockdevSnapshotSync:
1365#
1366# Either @device or @node-name must be set but not both.
1367#
1368# @device: the name of the device to take a snapshot of.
1369#
1370# @node-name: graph node name to generate the snapshot from (Since 2.0)
1371#
1372# @snapshot-file: the target of the new overlay image. If the file
1373# exists, or if it is a device, the overlay will be created in the
1374# existing file/device. Otherwise, a new file will be created.
1375#
1376# @snapshot-node-name: the graph node name of the new image (Since 2.0)
1377#
1378# @format: the format of the overlay image, default is 'qcow2'.
1379#
1380# @mode: whether and how QEMU should create a new image, default is
1381#        'absolute-paths'.
1382##
1383{ 'struct': 'BlockdevSnapshotSync',
1384  'data': { '*device': 'str', '*node-name': 'str',
1385            'snapshot-file': 'str', '*snapshot-node-name': 'str',
1386            '*format': 'str', '*mode': 'NewImageMode' } }
1387
1388##
1389# @BlockdevSnapshot:
1390#
1391# @node: device or node name that will have a snapshot taken.
1392#
1393# @overlay: reference to the existing block device that will become
1394#           the overlay of @node, as part of taking the snapshot.
1395#           It must not have a current backing file (this can be
1396#           achieved by passing "backing": null to blockdev-add).
1397#
1398# Since: 2.5
1399##
1400{ 'struct': 'BlockdevSnapshot',
1401  'data': { 'node': 'str', 'overlay': 'str' } }
1402
1403##
1404# @BackupCommon:
1405#
1406# @job-id: identifier for the newly-created block job. If
1407#          omitted, the device name will be used. (Since 2.7)
1408#
1409# @device: the device name or node-name of a root node which should be copied.
1410#
1411# @sync: what parts of the disk image should be copied to the destination
1412#        (all the disk, only the sectors allocated in the topmost image, from a
1413#        dirty bitmap, or only new I/O).
1414#
1415# @speed: the maximum speed, in bytes per second. The default is 0,
1416#         for unlimited.
1417#
1418# @bitmap: The name of a dirty bitmap to use.
1419#          Must be present if sync is "bitmap" or "incremental".
1420#          Can be present if sync is "full" or "top".
1421#          Must not be present otherwise.
1422#          (Since 2.4 (drive-backup), 3.1 (blockdev-backup))
1423#
1424# @bitmap-mode: Specifies the type of data the bitmap should contain after
1425#               the operation concludes.
1426#               Must be present if a bitmap was provided,
1427#               Must NOT be present otherwise. (Since 4.2)
1428#
1429# @compress: true to compress data, if the target format supports it.
1430#            (default: false) (since 2.8)
1431#
1432# @on-source-error: the action to take on an error on the source,
1433#                   default 'report'.  'stop' and 'enospc' can only be used
1434#                   if the block device supports io-status (see BlockInfo).
1435#
1436# @on-target-error: the action to take on an error on the target,
1437#                   default 'report' (no limitations, since this applies to
1438#                   a different block device than @device).
1439#
1440# @auto-finalize: When false, this job will wait in a PENDING state after it has
1441#                 finished its work, waiting for @block-job-finalize before
1442#                 making any block graph changes.
1443#                 When true, this job will automatically
1444#                 perform its abort or commit actions.
1445#                 Defaults to true. (Since 2.12)
1446#
1447# @auto-dismiss: When false, this job will wait in a CONCLUDED state after it
1448#                has completely ceased all work, and awaits @block-job-dismiss.
1449#                When true, this job will automatically disappear from the query
1450#                list without user intervention.
1451#                Defaults to true. (Since 2.12)
1452#
1453# @filter-node-name: the node name that should be assigned to the
1454#                    filter driver that the backup job inserts into the graph
1455#                    above node specified by @drive. If this option is not given,
1456#                    a node name is autogenerated. (Since: 4.2)
1457#
1458# Note: @on-source-error and @on-target-error only affect background
1459# I/O.  If an error occurs during a guest write request, the device's
1460# rerror/werror actions will be used.
1461#
1462# Since: 4.2
1463##
1464{ 'struct': 'BackupCommon',
1465  'data': { '*job-id': 'str', 'device': 'str',
1466            'sync': 'MirrorSyncMode', '*speed': 'int',
1467            '*bitmap': 'str', '*bitmap-mode': 'BitmapSyncMode',
1468            '*compress': 'bool',
1469            '*on-source-error': 'BlockdevOnError',
1470            '*on-target-error': 'BlockdevOnError',
1471            '*auto-finalize': 'bool', '*auto-dismiss': 'bool',
1472            '*filter-node-name': 'str' } }
1473
1474##
1475# @DriveBackup:
1476#
1477# @target: the target of the new image. If the file exists, or if it
1478#          is a device, the existing file/device will be used as the new
1479#          destination.  If it does not exist, a new file will be created.
1480#
1481# @format: the format of the new destination, default is to
1482#          probe if @mode is 'existing', else the format of the source
1483#
1484# @mode: whether and how QEMU should create a new image, default is
1485#        'absolute-paths'.
1486#
1487# Since: 1.6
1488##
1489{ 'struct': 'DriveBackup',
1490  'base': 'BackupCommon',
1491  'data': { 'target': 'str',
1492            '*format': 'str',
1493            '*mode': 'NewImageMode' } }
1494
1495##
1496# @BlockdevBackup:
1497#
1498# @target: the device name or node-name of the backup target node.
1499#
1500# Since: 2.3
1501##
1502{ 'struct': 'BlockdevBackup',
1503  'base': 'BackupCommon',
1504  'data': { 'target': 'str' } }
1505
1506##
1507# @blockdev-snapshot-sync:
1508#
1509# Takes a synchronous snapshot of a block device.
1510#
1511# For the arguments, see the documentation of BlockdevSnapshotSync.
1512#
1513# Returns: nothing on success
1514#          If @device is not a valid block device, DeviceNotFound
1515#
1516# Since: 0.14.0
1517#
1518# Example:
1519#
1520# -> { "execute": "blockdev-snapshot-sync",
1521#      "arguments": { "device": "ide-hd0",
1522#                     "snapshot-file":
1523#                     "/some/place/my-image",
1524#                     "format": "qcow2" } }
1525# <- { "return": {} }
1526#
1527##
1528{ 'command': 'blockdev-snapshot-sync',
1529  'data': 'BlockdevSnapshotSync' }
1530
1531
1532##
1533# @blockdev-snapshot:
1534#
1535# Takes a snapshot of a block device.
1536#
1537# Take a snapshot, by installing 'node' as the backing image of
1538# 'overlay'. Additionally, if 'node' is associated with a block
1539# device, the block device changes to using 'overlay' as its new active
1540# image.
1541#
1542# For the arguments, see the documentation of BlockdevSnapshot.
1543#
1544# Since: 2.5
1545#
1546# Example:
1547#
1548# -> { "execute": "blockdev-add",
1549#      "arguments": { "driver": "qcow2",
1550#                     "node-name": "node1534",
1551#                     "file": { "driver": "file",
1552#                               "filename": "hd1.qcow2" },
1553#                     "backing": null } }
1554#
1555# <- { "return": {} }
1556#
1557# -> { "execute": "blockdev-snapshot",
1558#      "arguments": { "node": "ide-hd0",
1559#                     "overlay": "node1534" } }
1560# <- { "return": {} }
1561#
1562##
1563{ 'command': 'blockdev-snapshot',
1564  'data': 'BlockdevSnapshot' }
1565
1566##
1567# @change-backing-file:
1568#
1569# Change the backing file in the image file metadata.  This does not
1570# cause QEMU to reopen the image file to reparse the backing filename
1571# (it may, however, perform a reopen to change permissions from
1572# r/o -> r/w -> r/o, if needed). The new backing file string is written
1573# into the image file metadata, and the QEMU internal strings are
1574# updated.
1575#
1576# @image-node-name: The name of the block driver state node of the
1577#                   image to modify. The "device" argument is used
1578#                   to verify "image-node-name" is in the chain
1579#                   described by "device".
1580#
1581# @device:          The device name or node-name of the root node that owns
1582#                   image-node-name.
1583#
1584# @backing-file:    The string to write as the backing file.  This
1585#                   string is not validated, so care should be taken
1586#                   when specifying the string or the image chain may
1587#                   not be able to be reopened again.
1588#
1589# Returns: Nothing on success
1590#
1591#          If "device" does not exist or cannot be determined, DeviceNotFound
1592#
1593# Since: 2.1
1594##
1595{ 'command': 'change-backing-file',
1596  'data': { 'device': 'str', 'image-node-name': 'str',
1597            'backing-file': 'str' } }
1598
1599##
1600# @block-commit:
1601#
1602# Live commit of data from overlay image nodes into backing nodes - i.e.,
1603# writes data between 'top' and 'base' into 'base'.
1604#
1605# @job-id: identifier for the newly-created block job. If
1606#          omitted, the device name will be used. (Since 2.7)
1607#
1608# @device:  the device name or node-name of a root node
1609#
1610# @base-node: The node name of the backing image to write data into.
1611#             If not specified, this is the deepest backing image.
1612#             (since: 3.1)
1613#
1614# @base: Same as @base-node, except that it is a file name rather than a node
1615#        name. This must be the exact filename string that was used to open the
1616#        node; other strings, even if addressing the same file, are not
1617#        accepted (deprecated, use @base-node instead)
1618#
1619# @top-node: The node name of the backing image within the image chain
1620#            which contains the topmost data to be committed down. If
1621#            not specified, this is the active layer. (since: 3.1)
1622#
1623# @top: Same as @top-node, except that it is a file name rather than a node
1624#       name. This must be the exact filename string that was used to open the
1625#       node; other strings, even if addressing the same file, are not
1626#       accepted (deprecated, use @base-node instead)
1627#
1628# @backing-file:  The backing file string to write into the overlay
1629#                           image of 'top'.  If 'top' is the active layer,
1630#                           specifying a backing file string is an error. This
1631#                           filename is not validated.
1632#
1633#                           If a pathname string is such that it cannot be
1634#                           resolved by QEMU, that means that subsequent QMP or
1635#                           HMP commands must use node-names for the image in
1636#                           question, as filename lookup methods will fail.
1637#
1638#                           If not specified, QEMU will automatically determine
1639#                           the backing file string to use, or error out if
1640#                           there is no obvious choice. Care should be taken
1641#                           when specifying the string, to specify a valid
1642#                           filename or protocol.
1643#                           (Since 2.1)
1644#
1645#                    If top == base, that is an error.
1646#                    If top == active, the job will not be completed by itself,
1647#                    user needs to complete the job with the block-job-complete
1648#                    command after getting the ready event. (Since 2.0)
1649#
1650#                    If the base image is smaller than top, then the base image
1651#                    will be resized to be the same size as top.  If top is
1652#                    smaller than the base image, the base will not be
1653#                    truncated.  If you want the base image size to match the
1654#                    size of the smaller top, you can safely truncate it
1655#                    yourself once the commit operation successfully completes.
1656#
1657# @speed:  the maximum speed, in bytes per second
1658#
1659# @filter-node-name: the node name that should be assigned to the
1660#                    filter driver that the commit job inserts into the graph
1661#                    above @top. If this option is not given, a node name is
1662#                    autogenerated. (Since: 2.9)
1663#
1664# @auto-finalize: When false, this job will wait in a PENDING state after it has
1665#                 finished its work, waiting for @block-job-finalize before
1666#                 making any block graph changes.
1667#                 When true, this job will automatically
1668#                 perform its abort or commit actions.
1669#                 Defaults to true. (Since 3.1)
1670#
1671# @auto-dismiss: When false, this job will wait in a CONCLUDED state after it
1672#                has completely ceased all work, and awaits @block-job-dismiss.
1673#                When true, this job will automatically disappear from the query
1674#                list without user intervention.
1675#                Defaults to true. (Since 3.1)
1676#
1677# Returns: Nothing on success
1678#          If @device does not exist, DeviceNotFound
1679#          Any other error returns a GenericError.
1680#
1681# Since: 1.3
1682#
1683# Example:
1684#
1685# -> { "execute": "block-commit",
1686#      "arguments": { "device": "virtio0",
1687#                     "top": "/tmp/snap1.qcow2" } }
1688# <- { "return": {} }
1689#
1690##
1691{ 'command': 'block-commit',
1692  'data': { '*job-id': 'str', 'device': 'str', '*base-node': 'str',
1693            '*base': 'str', '*top-node': 'str', '*top': 'str',
1694            '*backing-file': 'str', '*speed': 'int',
1695            '*filter-node-name': 'str',
1696            '*auto-finalize': 'bool', '*auto-dismiss': 'bool' } }
1697
1698##
1699# @drive-backup:
1700#
1701# Start a point-in-time copy of a block device to a new destination.  The
1702# status of ongoing drive-backup operations can be checked with
1703# query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1704# The operation can be stopped before it has completed using the
1705# block-job-cancel command.
1706#
1707# Returns: nothing on success
1708#          If @device is not a valid block device, GenericError
1709#
1710# Since: 1.6
1711#
1712# Example:
1713#
1714# -> { "execute": "drive-backup",
1715#      "arguments": { "device": "drive0",
1716#                     "sync": "full",
1717#                     "target": "backup.img" } }
1718# <- { "return": {} }
1719#
1720##
1721{ 'command': 'drive-backup', 'boxed': true,
1722  'data': 'DriveBackup' }
1723
1724##
1725# @blockdev-backup:
1726#
1727# Start a point-in-time copy of a block device to a new destination.  The
1728# status of ongoing blockdev-backup operations can be checked with
1729# query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1730# The operation can be stopped before it has completed using the
1731# block-job-cancel command.
1732#
1733# Returns: nothing on success
1734#          If @device is not a valid block device, DeviceNotFound
1735#
1736# Since: 2.3
1737#
1738# Example:
1739# -> { "execute": "blockdev-backup",
1740#      "arguments": { "device": "src-id",
1741#                     "sync": "full",
1742#                     "target": "tgt-id" } }
1743# <- { "return": {} }
1744#
1745##
1746{ 'command': 'blockdev-backup', 'boxed': true,
1747  'data': 'BlockdevBackup' }
1748
1749
1750##
1751# @query-named-block-nodes:
1752#
1753# Get the named block driver list
1754#
1755# Returns: the list of BlockDeviceInfo
1756#
1757# Since: 2.0
1758#
1759# Example:
1760#
1761# -> { "execute": "query-named-block-nodes" }
1762# <- { "return": [ { "ro":false,
1763#                    "drv":"qcow2",
1764#                    "encrypted":false,
1765#                    "file":"disks/test.qcow2",
1766#                    "node-name": "my-node",
1767#                    "backing_file_depth":1,
1768#                    "bps":1000000,
1769#                    "bps_rd":0,
1770#                    "bps_wr":0,
1771#                    "iops":1000000,
1772#                    "iops_rd":0,
1773#                    "iops_wr":0,
1774#                    "bps_max": 8000000,
1775#                    "bps_rd_max": 0,
1776#                    "bps_wr_max": 0,
1777#                    "iops_max": 0,
1778#                    "iops_rd_max": 0,
1779#                    "iops_wr_max": 0,
1780#                    "iops_size": 0,
1781#                    "write_threshold": 0,
1782#                    "image":{
1783#                       "filename":"disks/test.qcow2",
1784#                       "format":"qcow2",
1785#                       "virtual-size":2048000,
1786#                       "backing_file":"base.qcow2",
1787#                       "full-backing-filename":"disks/base.qcow2",
1788#                       "backing-filename-format":"qcow2",
1789#                       "snapshots":[
1790#                          {
1791#                             "id": "1",
1792#                             "name": "snapshot1",
1793#                             "vm-state-size": 0,
1794#                             "date-sec": 10000200,
1795#                             "date-nsec": 12,
1796#                             "vm-clock-sec": 206,
1797#                             "vm-clock-nsec": 30
1798#                          }
1799#                       ],
1800#                       "backing-image":{
1801#                           "filename":"disks/base.qcow2",
1802#                           "format":"qcow2",
1803#                           "virtual-size":2048000
1804#                       }
1805#                    } } ] }
1806#
1807##
1808{ 'command': 'query-named-block-nodes', 'returns': [ 'BlockDeviceInfo' ] }
1809
1810##
1811# @XDbgBlockGraphNodeType:
1812#
1813# @block-backend: corresponds to BlockBackend
1814#
1815# @block-job: corresonds to BlockJob
1816#
1817# @block-driver: corresponds to BlockDriverState
1818#
1819# Since: 4.0
1820##
1821{ 'enum': 'XDbgBlockGraphNodeType',
1822  'data': [ 'block-backend', 'block-job', 'block-driver' ] }
1823
1824##
1825# @XDbgBlockGraphNode:
1826#
1827# @id: Block graph node identifier. This @id is generated only for
1828#      x-debug-query-block-graph and does not relate to any other identifiers in
1829#      Qemu.
1830#
1831# @type: Type of graph node. Can be one of block-backend, block-job or
1832#        block-driver-state.
1833#
1834# @name: Human readable name of the node. Corresponds to node-name for
1835#        block-driver-state nodes; is not guaranteed to be unique in the whole
1836#        graph (with block-jobs and block-backends).
1837#
1838# Since: 4.0
1839##
1840{ 'struct': 'XDbgBlockGraphNode',
1841  'data': { 'id': 'uint64', 'type': 'XDbgBlockGraphNodeType', 'name': 'str' } }
1842
1843##
1844# @BlockPermission:
1845#
1846# Enum of base block permissions.
1847#
1848# @consistent-read: A user that has the "permission" of consistent reads is
1849#                   guaranteed that their view of the contents of the block
1850#                   device is complete and self-consistent, representing the
1851#                   contents of a disk at a specific point.
1852#                   For most block devices (including their backing files) this
1853#                   is true, but the property cannot be maintained in a few
1854#                   situations like for intermediate nodes of a commit block
1855#                   job.
1856#
1857# @write: This permission is required to change the visible disk contents.
1858#
1859# @write-unchanged: This permission (which is weaker than BLK_PERM_WRITE) is
1860#                   both enough and required for writes to the block node when
1861#                   the caller promises that the visible disk content doesn't
1862#                   change.
1863#                   As the BLK_PERM_WRITE permission is strictly stronger,
1864#                   either is sufficient to perform an unchanging write.
1865#
1866# @resize: This permission is required to change the size of a block node.
1867#
1868# @graph-mod: This permission is required to change the node that this
1869#             BdrvChild points to.
1870#
1871# Since: 4.0
1872##
1873  { 'enum': 'BlockPermission',
1874    'data': [ 'consistent-read', 'write', 'write-unchanged', 'resize',
1875              'graph-mod' ] }
1876##
1877# @XDbgBlockGraphEdge:
1878#
1879# Block Graph edge description for x-debug-query-block-graph.
1880#
1881# @parent: parent id
1882#
1883# @child: child id
1884#
1885# @name: name of the relation (examples are 'file' and 'backing')
1886#
1887# @perm: granted permissions for the parent operating on the child
1888#
1889# @shared-perm: permissions that can still be granted to other users of the
1890#               child while it is still attached to this parent
1891#
1892# Since: 4.0
1893##
1894{ 'struct': 'XDbgBlockGraphEdge',
1895  'data': { 'parent': 'uint64', 'child': 'uint64',
1896            'name': 'str', 'perm': [ 'BlockPermission' ],
1897            'shared-perm': [ 'BlockPermission' ] } }
1898
1899##
1900# @XDbgBlockGraph:
1901#
1902# Block Graph - list of nodes and list of edges.
1903#
1904# Since: 4.0
1905##
1906{ 'struct': 'XDbgBlockGraph',
1907  'data': { 'nodes': ['XDbgBlockGraphNode'], 'edges': ['XDbgBlockGraphEdge'] } }
1908
1909##
1910# @x-debug-query-block-graph:
1911#
1912# Get the block graph.
1913#
1914# Since: 4.0
1915##
1916{ 'command': 'x-debug-query-block-graph', 'returns': 'XDbgBlockGraph' }
1917
1918##
1919# @drive-mirror:
1920#
1921# Start mirroring a block device's writes to a new destination. target
1922# specifies the target of the new image. If the file exists, or if it
1923# is a device, it will be used as the new destination for writes. If
1924# it does not exist, a new file will be created. format specifies the
1925# format of the mirror image, default is to probe if mode='existing',
1926# else the format of the source.
1927#
1928# Returns: nothing on success
1929#          If @device is not a valid block device, GenericError
1930#
1931# Since: 1.3
1932#
1933# Example:
1934#
1935# -> { "execute": "drive-mirror",
1936#      "arguments": { "device": "ide-hd0",
1937#                     "target": "/some/place/my-image",
1938#                     "sync": "full",
1939#                     "format": "qcow2" } }
1940# <- { "return": {} }
1941#
1942##
1943{ 'command': 'drive-mirror', 'boxed': true,
1944  'data': 'DriveMirror' }
1945
1946##
1947# @DriveMirror:
1948#
1949# A set of parameters describing drive mirror setup.
1950#
1951# @job-id: identifier for the newly-created block job. If
1952#          omitted, the device name will be used. (Since 2.7)
1953#
1954# @device:  the device name or node-name of a root node whose writes should be
1955#           mirrored.
1956#
1957# @target: the target of the new image. If the file exists, or if it
1958#          is a device, the existing file/device will be used as the new
1959#          destination.  If it does not exist, a new file will be created.
1960#
1961# @format: the format of the new destination, default is to
1962#          probe if @mode is 'existing', else the format of the source
1963#
1964# @node-name: the new block driver state node name in the graph
1965#             (Since 2.1)
1966#
1967# @replaces: with sync=full graph node name to be replaced by the new
1968#            image when a whole image copy is done. This can be used to repair
1969#            broken Quorum files. (Since 2.1)
1970#
1971# @mode: whether and how QEMU should create a new image, default is
1972#        'absolute-paths'.
1973#
1974# @speed:  the maximum speed, in bytes per second
1975#
1976# @sync: what parts of the disk image should be copied to the destination
1977#        (all the disk, only the sectors allocated in the topmost image, or
1978#        only new I/O).
1979#
1980# @granularity: granularity of the dirty bitmap, default is 64K
1981#               if the image format doesn't have clusters, 4K if the clusters
1982#               are smaller than that, else the cluster size.  Must be a
1983#               power of 2 between 512 and 64M (since 1.4).
1984#
1985# @buf-size: maximum amount of data in flight from source to
1986#            target (since 1.4).
1987#
1988# @on-source-error: the action to take on an error on the source,
1989#                   default 'report'.  'stop' and 'enospc' can only be used
1990#                   if the block device supports io-status (see BlockInfo).
1991#
1992# @on-target-error: the action to take on an error on the target,
1993#                   default 'report' (no limitations, since this applies to
1994#                   a different block device than @device).
1995# @unmap: Whether to try to unmap target sectors where source has
1996#         only zero. If true, and target unallocated sectors will read as zero,
1997#         target image sectors will be unmapped; otherwise, zeroes will be
1998#         written. Both will result in identical contents.
1999#         Default is true. (Since 2.4)
2000#
2001# @copy-mode: when to copy data to the destination; defaults to 'background'
2002#             (Since: 3.0)
2003#
2004# @auto-finalize: When false, this job will wait in a PENDING state after it has
2005#                 finished its work, waiting for @block-job-finalize before
2006#                 making any block graph changes.
2007#                 When true, this job will automatically
2008#                 perform its abort or commit actions.
2009#                 Defaults to true. (Since 3.1)
2010#
2011# @auto-dismiss: When false, this job will wait in a CONCLUDED state after it
2012#                has completely ceased all work, and awaits @block-job-dismiss.
2013#                When true, this job will automatically disappear from the query
2014#                list without user intervention.
2015#                Defaults to true. (Since 3.1)
2016# Since: 1.3
2017##
2018{ 'struct': 'DriveMirror',
2019  'data': { '*job-id': 'str', 'device': 'str', 'target': 'str',
2020            '*format': 'str', '*node-name': 'str', '*replaces': 'str',
2021            'sync': 'MirrorSyncMode', '*mode': 'NewImageMode',
2022            '*speed': 'int', '*granularity': 'uint32',
2023            '*buf-size': 'int', '*on-source-error': 'BlockdevOnError',
2024            '*on-target-error': 'BlockdevOnError',
2025            '*unmap': 'bool', '*copy-mode': 'MirrorCopyMode',
2026            '*auto-finalize': 'bool', '*auto-dismiss': 'bool' } }
2027
2028##
2029# @BlockDirtyBitmap:
2030#
2031# @node: name of device/node which the bitmap is tracking
2032#
2033# @name: name of the dirty bitmap
2034#
2035# Since: 2.4
2036##
2037{ 'struct': 'BlockDirtyBitmap',
2038  'data': { 'node': 'str', 'name': 'str' } }
2039
2040##
2041# @BlockDirtyBitmapAdd:
2042#
2043# @node: name of device/node which the bitmap is tracking
2044#
2045# @name: name of the dirty bitmap (must be less than 1024 bytes)
2046#
2047# @granularity: the bitmap granularity, default is 64k for
2048#               block-dirty-bitmap-add
2049#
2050# @persistent: the bitmap is persistent, i.e. it will be saved to the
2051#              corresponding block device image file on its close. For now only
2052#              Qcow2 disks support persistent bitmaps. Default is false for
2053#              block-dirty-bitmap-add. (Since: 2.10)
2054#
2055# @disabled: the bitmap is created in the disabled state, which means that
2056#            it will not track drive changes. The bitmap may be enabled with
2057#            block-dirty-bitmap-enable. Default is false. (Since: 4.0)
2058#
2059# Since: 2.4
2060##
2061{ 'struct': 'BlockDirtyBitmapAdd',
2062  'data': { 'node': 'str', 'name': 'str', '*granularity': 'uint32',
2063            '*persistent': 'bool', '*disabled': 'bool' } }
2064
2065##
2066# @BlockDirtyBitmapMergeSource:
2067#
2068# @local: name of the bitmap, attached to the same node as target bitmap.
2069#
2070# @external: bitmap with specified node
2071#
2072# Since: 4.1
2073##
2074{ 'alternate': 'BlockDirtyBitmapMergeSource',
2075  'data': { 'local': 'str',
2076            'external': 'BlockDirtyBitmap' } }
2077
2078##
2079# @BlockDirtyBitmapMerge:
2080#
2081# @node: name of device/node which the @target bitmap is tracking
2082#
2083# @target: name of the destination dirty bitmap
2084#
2085# @bitmaps: name(s) of the source dirty bitmap(s) at @node and/or fully
2086#           specifed BlockDirtyBitmap elements. The latter are supported
2087#           since 4.1.
2088#
2089# Since: 4.0
2090##
2091{ 'struct': 'BlockDirtyBitmapMerge',
2092  'data': { 'node': 'str', 'target': 'str',
2093            'bitmaps': ['BlockDirtyBitmapMergeSource'] } }
2094
2095##
2096# @block-dirty-bitmap-add:
2097#
2098# Create a dirty bitmap with a name on the node, and start tracking the writes.
2099#
2100# Returns: nothing on success
2101#          If @node is not a valid block device or node, DeviceNotFound
2102#          If @name is already taken, GenericError with an explanation
2103#
2104# Since: 2.4
2105#
2106# Example:
2107#
2108# -> { "execute": "block-dirty-bitmap-add",
2109#      "arguments": { "node": "drive0", "name": "bitmap0" } }
2110# <- { "return": {} }
2111#
2112##
2113{ 'command': 'block-dirty-bitmap-add',
2114  'data': 'BlockDirtyBitmapAdd' }
2115
2116##
2117# @block-dirty-bitmap-remove:
2118#
2119# Stop write tracking and remove the dirty bitmap that was created
2120# with block-dirty-bitmap-add. If the bitmap is persistent, remove it from its
2121# storage too.
2122#
2123# Returns: nothing on success
2124#          If @node is not a valid block device or node, DeviceNotFound
2125#          If @name is not found, GenericError with an explanation
2126#          if @name is frozen by an operation, GenericError
2127#
2128# Since: 2.4
2129#
2130# Example:
2131#
2132# -> { "execute": "block-dirty-bitmap-remove",
2133#      "arguments": { "node": "drive0", "name": "bitmap0" } }
2134# <- { "return": {} }
2135#
2136##
2137{ 'command': 'block-dirty-bitmap-remove',
2138  'data': 'BlockDirtyBitmap' }
2139
2140##
2141# @block-dirty-bitmap-clear:
2142#
2143# Clear (reset) a dirty bitmap on the device, so that an incremental
2144# backup from this point in time forward will only backup clusters
2145# modified after this clear operation.
2146#
2147# Returns: nothing on success
2148#          If @node is not a valid block device, DeviceNotFound
2149#          If @name is not found, GenericError with an explanation
2150#
2151# Since: 2.4
2152#
2153# Example:
2154#
2155# -> { "execute": "block-dirty-bitmap-clear",
2156#      "arguments": { "node": "drive0", "name": "bitmap0" } }
2157# <- { "return": {} }
2158#
2159##
2160{ 'command': 'block-dirty-bitmap-clear',
2161  'data': 'BlockDirtyBitmap' }
2162
2163##
2164# @block-dirty-bitmap-enable:
2165#
2166# Enables a dirty bitmap so that it will begin tracking disk changes.
2167#
2168# Returns: nothing on success
2169#          If @node is not a valid block device, DeviceNotFound
2170#          If @name is not found, GenericError with an explanation
2171#
2172# Since: 4.0
2173#
2174# Example:
2175#
2176# -> { "execute": "block-dirty-bitmap-enable",
2177#      "arguments": { "node": "drive0", "name": "bitmap0" } }
2178# <- { "return": {} }
2179#
2180##
2181  { 'command': 'block-dirty-bitmap-enable',
2182    'data': 'BlockDirtyBitmap' }
2183
2184##
2185# @block-dirty-bitmap-disable:
2186#
2187# Disables a dirty bitmap so that it will stop tracking disk changes.
2188#
2189# Returns: nothing on success
2190#          If @node is not a valid block device, DeviceNotFound
2191#          If @name is not found, GenericError with an explanation
2192#
2193# Since: 4.0
2194#
2195# Example:
2196#
2197# -> { "execute": "block-dirty-bitmap-disable",
2198#      "arguments": { "node": "drive0", "name": "bitmap0" } }
2199# <- { "return": {} }
2200#
2201##
2202    { 'command': 'block-dirty-bitmap-disable',
2203      'data': 'BlockDirtyBitmap' }
2204
2205##
2206# @block-dirty-bitmap-merge:
2207#
2208# Merge dirty bitmaps listed in @bitmaps to the @target dirty bitmap.
2209# Dirty bitmaps in @bitmaps will be unchanged, except if it also appears
2210# as the @target bitmap. Any bits already set in @target will still be
2211# set after the merge, i.e., this operation does not clear the target.
2212# On error, @target is unchanged.
2213#
2214# The resulting bitmap will count as dirty any clusters that were dirty in any
2215# of the source bitmaps. This can be used to achieve backup checkpoints, or in
2216# simpler usages, to copy bitmaps.
2217#
2218# Returns: nothing on success
2219#          If @node is not a valid block device, DeviceNotFound
2220#          If any bitmap in @bitmaps or @target is not found, GenericError
2221#          If any of the bitmaps have different sizes or granularities,
2222#              GenericError
2223#
2224# Since: 4.0
2225#
2226# Example:
2227#
2228# -> { "execute": "block-dirty-bitmap-merge",
2229#      "arguments": { "node": "drive0", "target": "bitmap0",
2230#                     "bitmaps": ["bitmap1"] } }
2231# <- { "return": {} }
2232#
2233##
2234      { 'command': 'block-dirty-bitmap-merge',
2235        'data': 'BlockDirtyBitmapMerge' }
2236
2237##
2238# @BlockDirtyBitmapSha256:
2239#
2240# SHA256 hash of dirty bitmap data
2241#
2242# @sha256: ASCII representation of SHA256 bitmap hash
2243#
2244# Since: 2.10
2245##
2246  { 'struct': 'BlockDirtyBitmapSha256',
2247    'data': {'sha256': 'str'} }
2248
2249##
2250# @x-debug-block-dirty-bitmap-sha256:
2251#
2252# Get bitmap SHA256.
2253#
2254# Returns: BlockDirtyBitmapSha256 on success
2255#          If @node is not a valid block device, DeviceNotFound
2256#          If @name is not found or if hashing has failed, GenericError with an
2257#          explanation
2258#
2259# Since: 2.10
2260##
2261  { 'command': 'x-debug-block-dirty-bitmap-sha256',
2262    'data': 'BlockDirtyBitmap', 'returns': 'BlockDirtyBitmapSha256' }
2263
2264##
2265# @blockdev-mirror:
2266#
2267# Start mirroring a block device's writes to a new destination.
2268#
2269# @job-id: identifier for the newly-created block job. If
2270#          omitted, the device name will be used. (Since 2.7)
2271#
2272# @device: The device name or node-name of a root node whose writes should be
2273#          mirrored.
2274#
2275# @target: the id or node-name of the block device to mirror to. This mustn't be
2276#          attached to guest.
2277#
2278# @replaces: with sync=full graph node name to be replaced by the new
2279#            image when a whole image copy is done. This can be used to repair
2280#            broken Quorum files.
2281#
2282# @speed:  the maximum speed, in bytes per second
2283#
2284# @sync: what parts of the disk image should be copied to the destination
2285#        (all the disk, only the sectors allocated in the topmost image, or
2286#        only new I/O).
2287#
2288# @granularity: granularity of the dirty bitmap, default is 64K
2289#               if the image format doesn't have clusters, 4K if the clusters
2290#               are smaller than that, else the cluster size.  Must be a
2291#               power of 2 between 512 and 64M
2292#
2293# @buf-size: maximum amount of data in flight from source to
2294#            target
2295#
2296# @on-source-error: the action to take on an error on the source,
2297#                   default 'report'.  'stop' and 'enospc' can only be used
2298#                   if the block device supports io-status (see BlockInfo).
2299#
2300# @on-target-error: the action to take on an error on the target,
2301#                   default 'report' (no limitations, since this applies to
2302#                   a different block device than @device).
2303#
2304# @filter-node-name: the node name that should be assigned to the
2305#                    filter driver that the mirror job inserts into the graph
2306#                    above @device. If this option is not given, a node name is
2307#                    autogenerated. (Since: 2.9)
2308#
2309# @copy-mode: when to copy data to the destination; defaults to 'background'
2310#             (Since: 3.0)
2311#
2312# @auto-finalize: When false, this job will wait in a PENDING state after it has
2313#                 finished its work, waiting for @block-job-finalize before
2314#                 making any block graph changes.
2315#                 When true, this job will automatically
2316#                 perform its abort or commit actions.
2317#                 Defaults to true. (Since 3.1)
2318#
2319# @auto-dismiss: When false, this job will wait in a CONCLUDED state after it
2320#                has completely ceased all work, and awaits @block-job-dismiss.
2321#                When true, this job will automatically disappear from the query
2322#                list without user intervention.
2323#                Defaults to true. (Since 3.1)
2324# Returns: nothing on success.
2325#
2326# Since: 2.6
2327#
2328# Example:
2329#
2330# -> { "execute": "blockdev-mirror",
2331#      "arguments": { "device": "ide-hd0",
2332#                     "target": "target0",
2333#                     "sync": "full" } }
2334# <- { "return": {} }
2335#
2336##
2337{ 'command': 'blockdev-mirror',
2338  'data': { '*job-id': 'str', 'device': 'str', 'target': 'str',
2339            '*replaces': 'str',
2340            'sync': 'MirrorSyncMode',
2341            '*speed': 'int', '*granularity': 'uint32',
2342            '*buf-size': 'int', '*on-source-error': 'BlockdevOnError',
2343            '*on-target-error': 'BlockdevOnError',
2344            '*filter-node-name': 'str',
2345            '*copy-mode': 'MirrorCopyMode',
2346            '*auto-finalize': 'bool', '*auto-dismiss': 'bool' } }
2347
2348##
2349# @block_set_io_throttle:
2350#
2351# Change I/O throttle limits for a block drive.
2352#
2353# Since QEMU 2.4, each device with I/O limits is member of a throttle
2354# group.
2355#
2356# If two or more devices are members of the same group, the limits
2357# will apply to the combined I/O of the whole group in a round-robin
2358# fashion. Therefore, setting new I/O limits to a device will affect
2359# the whole group.
2360#
2361# The name of the group can be specified using the 'group' parameter.
2362# If the parameter is unset, it is assumed to be the current group of
2363# that device. If it's not in any group yet, the name of the device
2364# will be used as the name for its group.
2365#
2366# The 'group' parameter can also be used to move a device to a
2367# different group. In this case the limits specified in the parameters
2368# will be applied to the new group only.
2369#
2370# I/O limits can be disabled by setting all of them to 0. In this case
2371# the device will be removed from its group and the rest of its
2372# members will not be affected. The 'group' parameter is ignored.
2373#
2374# Returns: Nothing on success
2375#          If @device is not a valid block device, DeviceNotFound
2376#
2377# Since: 1.1
2378#
2379# Example:
2380#
2381# -> { "execute": "block_set_io_throttle",
2382#      "arguments": { "id": "virtio-blk-pci0/virtio-backend",
2383#                     "bps": 0,
2384#                     "bps_rd": 0,
2385#                     "bps_wr": 0,
2386#                     "iops": 512,
2387#                     "iops_rd": 0,
2388#                     "iops_wr": 0,
2389#                     "bps_max": 0,
2390#                     "bps_rd_max": 0,
2391#                     "bps_wr_max": 0,
2392#                     "iops_max": 0,
2393#                     "iops_rd_max": 0,
2394#                     "iops_wr_max": 0,
2395#                     "bps_max_length": 0,
2396#                     "iops_size": 0 } }
2397# <- { "return": {} }
2398#
2399# -> { "execute": "block_set_io_throttle",
2400#      "arguments": { "id": "ide0-1-0",
2401#                     "bps": 1000000,
2402#                     "bps_rd": 0,
2403#                     "bps_wr": 0,
2404#                     "iops": 0,
2405#                     "iops_rd": 0,
2406#                     "iops_wr": 0,
2407#                     "bps_max": 8000000,
2408#                     "bps_rd_max": 0,
2409#                     "bps_wr_max": 0,
2410#                     "iops_max": 0,
2411#                     "iops_rd_max": 0,
2412#                     "iops_wr_max": 0,
2413#                     "bps_max_length": 60,
2414#                     "iops_size": 0 } }
2415# <- { "return": {} }
2416##
2417{ 'command': 'block_set_io_throttle', 'boxed': true,
2418  'data': 'BlockIOThrottle' }
2419
2420##
2421# @BlockIOThrottle:
2422#
2423# A set of parameters describing block throttling.
2424#
2425# @device: Block device name (deprecated, use @id instead)
2426#
2427# @id: The name or QOM path of the guest device (since: 2.8)
2428#
2429# @bps: total throughput limit in bytes per second
2430#
2431# @bps_rd: read throughput limit in bytes per second
2432#
2433# @bps_wr: write throughput limit in bytes per second
2434#
2435# @iops: total I/O operations per second
2436#
2437# @iops_rd: read I/O operations per second
2438#
2439# @iops_wr: write I/O operations per second
2440#
2441# @bps_max: total throughput limit during bursts,
2442#                     in bytes (Since 1.7)
2443#
2444# @bps_rd_max: read throughput limit during bursts,
2445#                        in bytes (Since 1.7)
2446#
2447# @bps_wr_max: write throughput limit during bursts,
2448#                        in bytes (Since 1.7)
2449#
2450# @iops_max: total I/O operations per second during bursts,
2451#                      in bytes (Since 1.7)
2452#
2453# @iops_rd_max: read I/O operations per second during bursts,
2454#                         in bytes (Since 1.7)
2455#
2456# @iops_wr_max: write I/O operations per second during bursts,
2457#                         in bytes (Since 1.7)
2458#
2459# @bps_max_length: maximum length of the @bps_max burst
2460#                            period, in seconds. It must only
2461#                            be set if @bps_max is set as well.
2462#                            Defaults to 1. (Since 2.6)
2463#
2464# @bps_rd_max_length: maximum length of the @bps_rd_max
2465#                               burst period, in seconds. It must only
2466#                               be set if @bps_rd_max is set as well.
2467#                               Defaults to 1. (Since 2.6)
2468#
2469# @bps_wr_max_length: maximum length of the @bps_wr_max
2470#                               burst period, in seconds. It must only
2471#                               be set if @bps_wr_max is set as well.
2472#                               Defaults to 1. (Since 2.6)
2473#
2474# @iops_max_length: maximum length of the @iops burst
2475#                             period, in seconds. It must only
2476#                             be set if @iops_max is set as well.
2477#                             Defaults to 1. (Since 2.6)
2478#
2479# @iops_rd_max_length: maximum length of the @iops_rd_max
2480#                                burst period, in seconds. It must only
2481#                                be set if @iops_rd_max is set as well.
2482#                                Defaults to 1. (Since 2.6)
2483#
2484# @iops_wr_max_length: maximum length of the @iops_wr_max
2485#                                burst period, in seconds. It must only
2486#                                be set if @iops_wr_max is set as well.
2487#                                Defaults to 1. (Since 2.6)
2488#
2489# @iops_size: an I/O size in bytes (Since 1.7)
2490#
2491# @group: throttle group name (Since 2.4)
2492#
2493# Since: 1.1
2494##
2495{ 'struct': 'BlockIOThrottle',
2496  'data': { '*device': 'str', '*id': 'str', 'bps': 'int', 'bps_rd': 'int',
2497            'bps_wr': 'int', 'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
2498            '*bps_max': 'int', '*bps_rd_max': 'int',
2499            '*bps_wr_max': 'int', '*iops_max': 'int',
2500            '*iops_rd_max': 'int', '*iops_wr_max': 'int',
2501            '*bps_max_length': 'int', '*bps_rd_max_length': 'int',
2502            '*bps_wr_max_length': 'int', '*iops_max_length': 'int',
2503            '*iops_rd_max_length': 'int', '*iops_wr_max_length': 'int',
2504            '*iops_size': 'int', '*group': 'str' } }
2505
2506##
2507# @ThrottleLimits:
2508#
2509# Limit parameters for throttling.
2510# Since some limit combinations are illegal, limits should always be set in one
2511# transaction. All fields are optional. When setting limits, if a field is
2512# missing the current value is not changed.
2513#
2514# @iops-total:             limit total I/O operations per second
2515# @iops-total-max:         I/O operations burst
2516# @iops-total-max-length:  length of the iops-total-max burst period, in seconds
2517#                          It must only be set if @iops-total-max is set as well.
2518# @iops-read:              limit read operations per second
2519# @iops-read-max:          I/O operations read burst
2520# @iops-read-max-length:   length of the iops-read-max burst period, in seconds
2521#                          It must only be set if @iops-read-max is set as well.
2522# @iops-write:             limit write operations per second
2523# @iops-write-max:         I/O operations write burst
2524# @iops-write-max-length:  length of the iops-write-max burst period, in seconds
2525#                          It must only be set if @iops-write-max is set as well.
2526# @bps-total:              limit total bytes per second
2527# @bps-total-max:          total bytes burst
2528# @bps-total-max-length:   length of the bps-total-max burst period, in seconds.
2529#                          It must only be set if @bps-total-max is set as well.
2530# @bps-read:               limit read bytes per second
2531# @bps-read-max:           total bytes read burst
2532# @bps-read-max-length:    length of the bps-read-max burst period, in seconds
2533#                          It must only be set if @bps-read-max is set as well.
2534# @bps-write:              limit write bytes per second
2535# @bps-write-max:          total bytes write burst
2536# @bps-write-max-length:   length of the bps-write-max burst period, in seconds
2537#                          It must only be set if @bps-write-max is set as well.
2538# @iops-size:              when limiting by iops max size of an I/O in bytes
2539#
2540# Since: 2.11
2541##
2542{ 'struct': 'ThrottleLimits',
2543  'data': { '*iops-total' : 'int', '*iops-total-max' : 'int',
2544            '*iops-total-max-length' : 'int', '*iops-read' : 'int',
2545            '*iops-read-max' : 'int', '*iops-read-max-length' : 'int',
2546            '*iops-write' : 'int', '*iops-write-max' : 'int',
2547            '*iops-write-max-length' : 'int', '*bps-total' : 'int',
2548            '*bps-total-max' : 'int', '*bps-total-max-length' : 'int',
2549            '*bps-read' : 'int', '*bps-read-max' : 'int',
2550            '*bps-read-max-length' : 'int', '*bps-write' : 'int',
2551            '*bps-write-max' : 'int', '*bps-write-max-length' : 'int',
2552            '*iops-size' : 'int' } }
2553
2554##
2555# @block-stream:
2556#
2557# Copy data from a backing file into a block device.
2558#
2559# The block streaming operation is performed in the background until the entire
2560# backing file has been copied.  This command returns immediately once streaming
2561# has started.  The status of ongoing block streaming operations can be checked
2562# with query-block-jobs.  The operation can be stopped before it has completed
2563# using the block-job-cancel command.
2564#
2565# The node that receives the data is called the top image, can be located in
2566# any part of the chain (but always above the base image; see below) and can be
2567# specified using its device or node name. Earlier qemu versions only allowed
2568# 'device' to name the top level node; presence of the 'base-node' parameter
2569# during introspection can be used as a witness of the enhanced semantics
2570# of 'device'.
2571#
2572# If a base file is specified then sectors are not copied from that base file and
2573# its backing chain.  When streaming completes the image file will have the base
2574# file as its backing file.  This can be used to stream a subset of the backing
2575# file chain instead of flattening the entire image.
2576#
2577# On successful completion the image file is updated to drop the backing file
2578# and the BLOCK_JOB_COMPLETED event is emitted.
2579#
2580# @job-id: identifier for the newly-created block job. If
2581#          omitted, the device name will be used. (Since 2.7)
2582#
2583# @device: the device or node name of the top image
2584#
2585# @base:   the common backing file name.
2586#                    It cannot be set if @base-node is also set.
2587#
2588# @base-node: the node name of the backing file.
2589#                       It cannot be set if @base is also set. (Since 2.8)
2590#
2591# @backing-file: The backing file string to write into the top
2592#                          image. This filename is not validated.
2593#
2594#                          If a pathname string is such that it cannot be
2595#                          resolved by QEMU, that means that subsequent QMP or
2596#                          HMP commands must use node-names for the image in
2597#                          question, as filename lookup methods will fail.
2598#
2599#                          If not specified, QEMU will automatically determine
2600#                          the backing file string to use, or error out if there
2601#                          is no obvious choice.  Care should be taken when
2602#                          specifying the string, to specify a valid filename or
2603#                          protocol.
2604#                          (Since 2.1)
2605#
2606# @speed:  the maximum speed, in bytes per second
2607#
2608# @on-error: the action to take on an error (default report).
2609#            'stop' and 'enospc' can only be used if the block device
2610#            supports io-status (see BlockInfo).  Since 1.3.
2611#
2612# @auto-finalize: When false, this job will wait in a PENDING state after it has
2613#                 finished its work, waiting for @block-job-finalize before
2614#                 making any block graph changes.
2615#                 When true, this job will automatically
2616#                 perform its abort or commit actions.
2617#                 Defaults to true. (Since 3.1)
2618#
2619# @auto-dismiss: When false, this job will wait in a CONCLUDED state after it
2620#                has completely ceased all work, and awaits @block-job-dismiss.
2621#                When true, this job will automatically disappear from the query
2622#                list without user intervention.
2623#                Defaults to true. (Since 3.1)
2624#
2625# Returns: Nothing on success. If @device does not exist, DeviceNotFound.
2626#
2627# Since: 1.1
2628#
2629# Example:
2630#
2631# -> { "execute": "block-stream",
2632#      "arguments": { "device": "virtio0",
2633#                     "base": "/tmp/master.qcow2" } }
2634# <- { "return": {} }
2635#
2636##
2637{ 'command': 'block-stream',
2638  'data': { '*job-id': 'str', 'device': 'str', '*base': 'str',
2639            '*base-node': 'str', '*backing-file': 'str', '*speed': 'int',
2640            '*on-error': 'BlockdevOnError',
2641            '*auto-finalize': 'bool', '*auto-dismiss': 'bool' } }
2642
2643##
2644# @block-job-set-speed:
2645#
2646# Set maximum speed for a background block operation.
2647#
2648# This command can only be issued when there is an active block job.
2649#
2650# Throttling can be disabled by setting the speed to 0.
2651#
2652# @device: The job identifier. This used to be a device name (hence
2653#          the name of the parameter), but since QEMU 2.7 it can have
2654#          other values.
2655#
2656# @speed:  the maximum speed, in bytes per second, or 0 for unlimited.
2657#          Defaults to 0.
2658#
2659# Returns: Nothing on success
2660#          If no background operation is active on this device, DeviceNotActive
2661#
2662# Since: 1.1
2663##
2664{ 'command': 'block-job-set-speed',
2665  'data': { 'device': 'str', 'speed': 'int' } }
2666
2667##
2668# @block-job-cancel:
2669#
2670# Stop an active background block operation.
2671#
2672# This command returns immediately after marking the active background block
2673# operation for cancellation.  It is an error to call this command if no
2674# operation is in progress.
2675#
2676# The operation will cancel as soon as possible and then emit the
2677# BLOCK_JOB_CANCELLED event.  Before that happens the job is still visible when
2678# enumerated using query-block-jobs.
2679#
2680# Note that if you issue 'block-job-cancel' after 'drive-mirror' has indicated
2681# (via the event BLOCK_JOB_READY) that the source and destination are
2682# synchronized, then the event triggered by this command changes to
2683# BLOCK_JOB_COMPLETED, to indicate that the mirroring has ended and the
2684# destination now has a point-in-time copy tied to the time of the cancellation.
2685#
2686# For streaming, the image file retains its backing file unless the streaming
2687# operation happens to complete just as it is being cancelled.  A new streaming
2688# operation can be started at a later time to finish copying all data from the
2689# backing file.
2690#
2691# @device: The job identifier. This used to be a device name (hence
2692#          the name of the parameter), but since QEMU 2.7 it can have
2693#          other values.
2694#
2695# @force: If true, and the job has already emitted the event BLOCK_JOB_READY,
2696#         abandon the job immediately (even if it is paused) instead of waiting
2697#         for the destination to complete its final synchronization (since 1.3)
2698#
2699# Returns: Nothing on success
2700#          If no background operation is active on this device, DeviceNotActive
2701#
2702# Since: 1.1
2703##
2704{ 'command': 'block-job-cancel', 'data': { 'device': 'str', '*force': 'bool' } }
2705
2706##
2707# @block-job-pause:
2708#
2709# Pause an active background block operation.
2710#
2711# This command returns immediately after marking the active background block
2712# operation for pausing.  It is an error to call this command if no
2713# operation is in progress or if the job is already paused.
2714#
2715# The operation will pause as soon as possible.  No event is emitted when
2716# the operation is actually paused.  Cancelling a paused job automatically
2717# resumes it.
2718#
2719# @device: The job identifier. This used to be a device name (hence
2720#          the name of the parameter), but since QEMU 2.7 it can have
2721#          other values.
2722#
2723# Returns: Nothing on success
2724#          If no background operation is active on this device, DeviceNotActive
2725#
2726# Since: 1.3
2727##
2728{ 'command': 'block-job-pause', 'data': { 'device': 'str' } }
2729
2730##
2731# @block-job-resume:
2732#
2733# Resume an active background block operation.
2734#
2735# This command returns immediately after resuming a paused background block
2736# operation.  It is an error to call this command if no operation is in
2737# progress or if the job is not paused.
2738#
2739# This command also clears the error status of the job.
2740#
2741# @device: The job identifier. This used to be a device name (hence
2742#          the name of the parameter), but since QEMU 2.7 it can have
2743#          other values.
2744#
2745# Returns: Nothing on success
2746#          If no background operation is active on this device, DeviceNotActive
2747#
2748# Since: 1.3
2749##
2750{ 'command': 'block-job-resume', 'data': { 'device': 'str' } }
2751
2752##
2753# @block-job-complete:
2754#
2755# Manually trigger completion of an active background block operation.  This
2756# is supported for drive mirroring, where it also switches the device to
2757# write to the target path only.  The ability to complete is signaled with
2758# a BLOCK_JOB_READY event.
2759#
2760# This command completes an active background block operation synchronously.
2761# The ordering of this command's return with the BLOCK_JOB_COMPLETED event
2762# is not defined.  Note that if an I/O error occurs during the processing of
2763# this command: 1) the command itself will fail; 2) the error will be processed
2764# according to the rerror/werror arguments that were specified when starting
2765# the operation.
2766#
2767# A cancelled or paused job cannot be completed.
2768#
2769# @device: The job identifier. This used to be a device name (hence
2770#          the name of the parameter), but since QEMU 2.7 it can have
2771#          other values.
2772#
2773# Returns: Nothing on success
2774#          If no background operation is active on this device, DeviceNotActive
2775#
2776# Since: 1.3
2777##
2778{ 'command': 'block-job-complete', 'data': { 'device': 'str' } }
2779
2780##
2781# @block-job-dismiss:
2782#
2783# For jobs that have already concluded, remove them from the block-job-query
2784# list. This command only needs to be run for jobs which were started with
2785# QEMU 2.12+ job lifetime management semantics.
2786#
2787# This command will refuse to operate on any job that has not yet reached
2788# its terminal state, JOB_STATUS_CONCLUDED. For jobs that make use of the
2789# BLOCK_JOB_READY event, block-job-cancel or block-job-complete will still need
2790# to be used as appropriate.
2791#
2792# @id: The job identifier.
2793#
2794# Returns: Nothing on success
2795#
2796# Since: 2.12
2797##
2798{ 'command': 'block-job-dismiss', 'data': { 'id': 'str' } }
2799
2800##
2801# @block-job-finalize:
2802#
2803# Once a job that has manual=true reaches the pending state, it can be
2804# instructed to finalize any graph changes and do any necessary cleanup
2805# via this command.
2806# For jobs in a transaction, instructing one job to finalize will force
2807# ALL jobs in the transaction to finalize, so it is only necessary to instruct
2808# a single member job to finalize.
2809#
2810# @id: The job identifier.
2811#
2812# Returns: Nothing on success
2813#
2814# Since: 2.12
2815##
2816{ 'command': 'block-job-finalize', 'data': { 'id': 'str' } }
2817
2818##
2819# @BlockdevDiscardOptions:
2820#
2821# Determines how to handle discard requests.
2822#
2823# @ignore:      Ignore the request
2824# @unmap:       Forward as an unmap request
2825#
2826# Since: 2.9
2827##
2828{ 'enum': 'BlockdevDiscardOptions',
2829  'data': [ 'ignore', 'unmap' ] }
2830
2831##
2832# @BlockdevDetectZeroesOptions:
2833#
2834# Describes the operation mode for the automatic conversion of plain
2835# zero writes by the OS to driver specific optimized zero write commands.
2836#
2837# @off:      Disabled (default)
2838# @on:       Enabled
2839# @unmap:    Enabled and even try to unmap blocks if possible. This requires
2840#            also that @BlockdevDiscardOptions is set to unmap for this device.
2841#
2842# Since: 2.1
2843##
2844{ 'enum': 'BlockdevDetectZeroesOptions',
2845  'data': [ 'off', 'on', 'unmap' ] }
2846
2847##
2848# @BlockdevAioOptions:
2849#
2850# Selects the AIO backend to handle I/O requests
2851#
2852# @threads:     Use qemu's thread pool
2853# @native:      Use native AIO backend (only Linux and Windows)
2854#
2855# Since: 2.9
2856##
2857{ 'enum': 'BlockdevAioOptions',
2858  'data': [ 'threads', 'native' ] }
2859
2860##
2861# @BlockdevCacheOptions:
2862#
2863# Includes cache-related options for block devices
2864#
2865# @direct:      enables use of O_DIRECT (bypass the host page cache;
2866#               default: false)
2867# @no-flush:    ignore any flush requests for the device (default:
2868#               false)
2869#
2870# Since: 2.9
2871##
2872{ 'struct': 'BlockdevCacheOptions',
2873  'data': { '*direct': 'bool',
2874            '*no-flush': 'bool' } }
2875
2876##
2877# @BlockdevDriver:
2878#
2879# Drivers that are supported in block device operations.
2880#
2881# @vxhs: Since 2.10
2882# @throttle: Since 2.11
2883# @nvme: Since 2.12
2884# @copy-on-read: Since 3.0
2885# @blklogwrites: Since 3.0
2886# @blkreplay: Since 4.2
2887#
2888# Since: 2.9
2889##
2890{ 'enum': 'BlockdevDriver',
2891  'data': [ 'blkdebug', 'blklogwrites', 'blkreplay', 'blkverify', 'bochs',
2892            'cloop', 'copy-on-read', 'dmg', 'file', 'ftp', 'ftps', 'gluster',
2893            'host_cdrom', 'host_device', 'http', 'https', 'iscsi', 'luks',
2894            'nbd', 'nfs', 'null-aio', 'null-co', 'nvme', 'parallels', 'qcow',
2895            'qcow2', 'qed', 'quorum', 'raw', 'rbd',
2896            { 'name': 'replication', 'if': 'defined(CONFIG_REPLICATION)' },
2897            'sheepdog',
2898            'ssh', 'throttle', 'vdi', 'vhdx', 'vmdk', 'vpc', 'vvfat', 'vxhs' ] }
2899
2900##
2901# @BlockdevOptionsFile:
2902#
2903# Driver specific block device options for the file backend.
2904#
2905# @filename:    path to the image file
2906# @pr-manager:  the id for the object that will handle persistent reservations
2907#               for this device (default: none, forward the commands via SG_IO;
2908#               since 2.11)
2909# @aio:         AIO backend (default: threads) (since: 2.8)
2910# @locking:     whether to enable file locking. If set to 'auto', only enable
2911#               when Open File Descriptor (OFD) locking API is available
2912#               (default: auto, since 2.10)
2913# @drop-cache:  invalidate page cache during live migration.  This prevents
2914#               stale data on the migration destination with cache.direct=off.
2915#               Currently only supported on Linux hosts.
2916#               (default: on, since: 4.0)
2917# @x-check-cache-dropped: whether to check that page cache was dropped on live
2918#                         migration.  May cause noticeable delays if the image
2919#                         file is large, do not use in production.
2920#                         (default: off) (since: 3.0)
2921#
2922# Features:
2923# @dynamic-auto-read-only: If present, enabled auto-read-only means that the
2924#                          driver will open the image read-only at first,
2925#                          dynamically reopen the image file read-write when
2926#                          the first writer is attached to the node and reopen
2927#                          read-only when the last writer is detached. This
2928#                          allows giving QEMU write permissions only on demand
2929#                          when an operation actually needs write access.
2930#
2931# Since: 2.9
2932##
2933{ 'struct': 'BlockdevOptionsFile',
2934  'data': { 'filename': 'str',
2935            '*pr-manager': 'str',
2936            '*locking': 'OnOffAuto',
2937            '*aio': 'BlockdevAioOptions',
2938	    '*drop-cache': {'type': 'bool',
2939	                    'if': 'defined(CONFIG_LINUX)'},
2940            '*x-check-cache-dropped': 'bool' },
2941  'features': [ { 'name': 'dynamic-auto-read-only',
2942                  'if': 'defined(CONFIG_POSIX)' } ] }
2943
2944##
2945# @BlockdevOptionsNull:
2946#
2947# Driver specific block device options for the null backend.
2948#
2949# @size:    size of the device in bytes.
2950# @latency-ns: emulated latency (in nanoseconds) in processing
2951#              requests. Default to zero which completes requests immediately.
2952#              (Since 2.4)
2953# @read-zeroes: if true, reads from the device produce zeroes; if false, the
2954#               buffer is left unchanged. (default: false; since: 4.1)
2955#
2956# Since: 2.9
2957##
2958{ 'struct': 'BlockdevOptionsNull',
2959  'data': { '*size': 'int', '*latency-ns': 'uint64', '*read-zeroes': 'bool' } }
2960
2961##
2962# @BlockdevOptionsNVMe:
2963#
2964# Driver specific block device options for the NVMe backend.
2965#
2966# @device:    PCI controller address of the NVMe device in
2967#             format hhhh:bb:ss.f (host:bus:slot.function)
2968# @namespace: namespace number of the device, starting from 1.
2969#
2970# Note that the PCI @device must have been unbound from any host
2971# kernel driver before instructing QEMU to add the blockdev.
2972#
2973# Since: 2.12
2974##
2975{ 'struct': 'BlockdevOptionsNVMe',
2976  'data': { 'device': 'str', 'namespace': 'int' } }
2977
2978##
2979# @BlockdevOptionsVVFAT:
2980#
2981# Driver specific block device options for the vvfat protocol.
2982#
2983# @dir:         directory to be exported as FAT image
2984# @fat-type:    FAT type: 12, 16 or 32
2985# @floppy:      whether to export a floppy image (true) or
2986#               partitioned hard disk (false; default)
2987# @label:       set the volume label, limited to 11 bytes. FAT16 and
2988#               FAT32 traditionally have some restrictions on labels, which are
2989#               ignored by most operating systems. Defaults to "QEMU VVFAT".
2990#               (since 2.4)
2991# @rw:          whether to allow write operations (default: false)
2992#
2993# Since: 2.9
2994##
2995{ 'struct': 'BlockdevOptionsVVFAT',
2996  'data': { 'dir': 'str', '*fat-type': 'int', '*floppy': 'bool',
2997            '*label': 'str', '*rw': 'bool' } }
2998
2999##
3000# @BlockdevOptionsGenericFormat:
3001#
3002# Driver specific block device options for image format that have no option
3003# besides their data source.
3004#
3005# @file:        reference to or definition of the data source block device
3006#
3007# Since: 2.9
3008##
3009{ 'struct': 'BlockdevOptionsGenericFormat',
3010  'data': { 'file': 'BlockdevRef' } }
3011
3012##
3013# @BlockdevOptionsLUKS:
3014#
3015# Driver specific block device options for LUKS.
3016#
3017# @key-secret: the ID of a QCryptoSecret object providing
3018#              the decryption key (since 2.6). Mandatory except when
3019#              doing a metadata-only probe of the image.
3020#
3021# Since: 2.9
3022##
3023{ 'struct': 'BlockdevOptionsLUKS',
3024  'base': 'BlockdevOptionsGenericFormat',
3025  'data': { '*key-secret': 'str' } }
3026
3027
3028##
3029# @BlockdevOptionsGenericCOWFormat:
3030#
3031# Driver specific block device options for image format that have no option
3032# besides their data source and an optional backing file.
3033#
3034# @backing:     reference to or definition of the backing file block
3035#               device, null disables the backing file entirely.
3036#               Defaults to the backing file stored the image file.
3037#
3038# Since: 2.9
3039##
3040{ 'struct': 'BlockdevOptionsGenericCOWFormat',
3041  'base': 'BlockdevOptionsGenericFormat',
3042  'data': { '*backing': 'BlockdevRefOrNull' } }
3043
3044##
3045# @Qcow2OverlapCheckMode:
3046#
3047# General overlap check modes.
3048#
3049# @none:        Do not perform any checks
3050#
3051# @constant:    Perform only checks which can be done in constant time and
3052#               without reading anything from disk
3053#
3054# @cached:      Perform only checks which can be done without reading anything
3055#               from disk
3056#
3057# @all:         Perform all available overlap checks
3058#
3059# Since: 2.9
3060##
3061{ 'enum': 'Qcow2OverlapCheckMode',
3062  'data': [ 'none', 'constant', 'cached', 'all' ] }
3063
3064##
3065# @Qcow2OverlapCheckFlags:
3066#
3067# Structure of flags for each metadata structure. Setting a field to 'true'
3068# makes qemu guard that structure against unintended overwriting. The default
3069# value is chosen according to the template given.
3070#
3071# @template: Specifies a template mode which can be adjusted using the other
3072#            flags, defaults to 'cached'
3073#
3074# @bitmap-directory: since 3.0
3075#
3076# Since: 2.9
3077##
3078{ 'struct': 'Qcow2OverlapCheckFlags',
3079  'data': { '*template':         'Qcow2OverlapCheckMode',
3080            '*main-header':      'bool',
3081            '*active-l1':        'bool',
3082            '*active-l2':        'bool',
3083            '*refcount-table':   'bool',
3084            '*refcount-block':   'bool',
3085            '*snapshot-table':   'bool',
3086            '*inactive-l1':      'bool',
3087            '*inactive-l2':      'bool',
3088            '*bitmap-directory': 'bool' } }
3089
3090##
3091# @Qcow2OverlapChecks:
3092#
3093# Specifies which metadata structures should be guarded against unintended
3094# overwriting.
3095#
3096# @flags:   set of flags for separate specification of each metadata structure
3097#           type
3098#
3099# @mode:    named mode which chooses a specific set of flags
3100#
3101# Since: 2.9
3102##
3103{ 'alternate': 'Qcow2OverlapChecks',
3104  'data': { 'flags': 'Qcow2OverlapCheckFlags',
3105            'mode':  'Qcow2OverlapCheckMode' } }
3106
3107##
3108# @BlockdevQcowEncryptionFormat:
3109#
3110# @aes: AES-CBC with plain64 initialization vectors
3111#
3112# Since: 2.10
3113##
3114{ 'enum': 'BlockdevQcowEncryptionFormat',
3115  'data': [ 'aes' ] }
3116
3117##
3118# @BlockdevQcowEncryption:
3119#
3120# Since: 2.10
3121##
3122{ 'union': 'BlockdevQcowEncryption',
3123  'base': { 'format': 'BlockdevQcowEncryptionFormat' },
3124  'discriminator': 'format',
3125  'data': { 'aes': 'QCryptoBlockOptionsQCow' } }
3126
3127##
3128# @BlockdevOptionsQcow:
3129#
3130# Driver specific block device options for qcow.
3131#
3132# @encrypt:               Image decryption options. Mandatory for
3133#                         encrypted images, except when doing a metadata-only
3134#                         probe of the image.
3135#
3136# Since: 2.10
3137##
3138{ 'struct': 'BlockdevOptionsQcow',
3139  'base': 'BlockdevOptionsGenericCOWFormat',
3140  'data': { '*encrypt': 'BlockdevQcowEncryption' } }
3141
3142
3143
3144##
3145# @BlockdevQcow2EncryptionFormat:
3146# @aes: AES-CBC with plain64 initialization vectors
3147#
3148# Since: 2.10
3149##
3150{ 'enum': 'BlockdevQcow2EncryptionFormat',
3151  'data': [ 'aes', 'luks' ] }
3152
3153##
3154# @BlockdevQcow2Encryption:
3155#
3156# Since: 2.10
3157##
3158{ 'union': 'BlockdevQcow2Encryption',
3159  'base': { 'format': 'BlockdevQcow2EncryptionFormat' },
3160  'discriminator': 'format',
3161  'data': { 'aes': 'QCryptoBlockOptionsQCow',
3162            'luks': 'QCryptoBlockOptionsLUKS'} }
3163
3164##
3165# @BlockdevOptionsQcow2:
3166#
3167# Driver specific block device options for qcow2.
3168#
3169# @lazy-refcounts:        whether to enable the lazy refcounts
3170#                         feature (default is taken from the image file)
3171#
3172# @pass-discard-request:  whether discard requests to the qcow2
3173#                         device should be forwarded to the data source
3174#
3175# @pass-discard-snapshot: whether discard requests for the data source
3176#                         should be issued when a snapshot operation (e.g.
3177#                         deleting a snapshot) frees clusters in the qcow2 file
3178#
3179# @pass-discard-other:    whether discard requests for the data source
3180#                         should be issued on other occasions where a cluster
3181#                         gets freed
3182#
3183# @overlap-check:         which overlap checks to perform for writes
3184#                         to the image, defaults to 'cached' (since 2.2)
3185#
3186# @cache-size:            the maximum total size of the L2 table and
3187#                         refcount block caches in bytes (since 2.2)
3188#
3189# @l2-cache-size:         the maximum size of the L2 table cache in
3190#                         bytes (since 2.2)
3191#
3192# @l2-cache-entry-size:   the size of each entry in the L2 cache in
3193#                         bytes. It must be a power of two between 512
3194#                         and the cluster size. The default value is
3195#                         the cluster size (since 2.12)
3196#
3197# @refcount-cache-size:   the maximum size of the refcount block cache
3198#                         in bytes (since 2.2)
3199#
3200# @cache-clean-interval:  clean unused entries in the L2 and refcount
3201#                         caches. The interval is in seconds. The default value
3202#                         is 600 on supporting platforms, and 0 on other
3203#                         platforms. 0 disables this feature. (since 2.5)
3204#
3205# @encrypt:               Image decryption options. Mandatory for
3206#                         encrypted images, except when doing a metadata-only
3207#                         probe of the image. (since 2.10)
3208#
3209# @data-file:             reference to or definition of the external data file.
3210#                         This may only be specified for images that require an
3211#                         external data file. If it is not specified for such
3212#                         an image, the data file name is loaded from the image
3213#                         file. (since 4.0)
3214#
3215# Since: 2.9
3216##
3217{ 'struct': 'BlockdevOptionsQcow2',
3218  'base': 'BlockdevOptionsGenericCOWFormat',
3219  'data': { '*lazy-refcounts': 'bool',
3220            '*pass-discard-request': 'bool',
3221            '*pass-discard-snapshot': 'bool',
3222            '*pass-discard-other': 'bool',
3223            '*overlap-check': 'Qcow2OverlapChecks',
3224            '*cache-size': 'int',
3225            '*l2-cache-size': 'int',
3226            '*l2-cache-entry-size': 'int',
3227            '*refcount-cache-size': 'int',
3228            '*cache-clean-interval': 'int',
3229            '*encrypt': 'BlockdevQcow2Encryption',
3230            '*data-file': 'BlockdevRef' } }
3231
3232##
3233# @SshHostKeyCheckMode:
3234#
3235# @none             Don't check the host key at all
3236# @hash             Compare the host key with a given hash
3237# @known_hosts      Check the host key against the known_hosts file
3238#
3239# Since: 2.12
3240##
3241{ 'enum': 'SshHostKeyCheckMode',
3242  'data': [ 'none', 'hash', 'known_hosts' ] }
3243
3244##
3245# @SshHostKeyCheckHashType:
3246#
3247# @md5              The given hash is an md5 hash
3248# @sha1             The given hash is an sha1 hash
3249#
3250# Since: 2.12
3251##
3252{ 'enum': 'SshHostKeyCheckHashType',
3253  'data': [ 'md5', 'sha1' ] }
3254
3255##
3256# @SshHostKeyHash:
3257#
3258# @type             The hash algorithm used for the hash
3259# @hash             The expected hash value
3260#
3261# Since: 2.12
3262##
3263{ 'struct': 'SshHostKeyHash',
3264  'data': { 'type': 'SshHostKeyCheckHashType',
3265            'hash': 'str' }}
3266
3267##
3268# @SshHostKeyCheck:
3269#
3270# Since: 2.12
3271##
3272{ 'union': 'SshHostKeyCheck',
3273  'base': { 'mode': 'SshHostKeyCheckMode' },
3274  'discriminator': 'mode',
3275  'data': { 'hash': 'SshHostKeyHash' } }
3276
3277##
3278# @BlockdevOptionsSsh:
3279#
3280# @server:              host address
3281#
3282# @path:                path to the image on the host
3283#
3284# @user:                user as which to connect, defaults to current
3285#                       local user name
3286#
3287# @host-key-check:      Defines how and what to check the host key against
3288#                       (default: known_hosts)
3289#
3290# Since: 2.9
3291##
3292{ 'struct': 'BlockdevOptionsSsh',
3293  'data': { 'server': 'InetSocketAddress',
3294            'path': 'str',
3295            '*user': 'str',
3296            '*host-key-check': 'SshHostKeyCheck' } }
3297
3298
3299##
3300# @BlkdebugEvent:
3301#
3302# Trigger events supported by blkdebug.
3303#
3304# @l1_shrink_write_table:      write zeros to the l1 table to shrink image.
3305#                              (since 2.11)
3306#
3307# @l1_shrink_free_l2_clusters: discard the l2 tables. (since 2.11)
3308#
3309# @cor_write: a write due to copy-on-read (since 2.11)
3310#
3311# @cluster_alloc_space: an allocation of file space for a cluster (since 4.1)
3312#
3313# @none: triggers once at creation of the blkdebug node (since 4.1)
3314#
3315# Since: 2.9
3316##
3317{ 'enum': 'BlkdebugEvent', 'prefix': 'BLKDBG',
3318  'data': [ 'l1_update', 'l1_grow_alloc_table', 'l1_grow_write_table',
3319            'l1_grow_activate_table', 'l2_load', 'l2_update',
3320            'l2_update_compressed', 'l2_alloc_cow_read', 'l2_alloc_write',
3321            'read_aio', 'read_backing_aio', 'read_compressed', 'write_aio',
3322            'write_compressed', 'vmstate_load', 'vmstate_save', 'cow_read',
3323            'cow_write', 'reftable_load', 'reftable_grow', 'reftable_update',
3324            'refblock_load', 'refblock_update', 'refblock_update_part',
3325            'refblock_alloc', 'refblock_alloc_hookup', 'refblock_alloc_write',
3326            'refblock_alloc_write_blocks', 'refblock_alloc_write_table',
3327            'refblock_alloc_switch_table', 'cluster_alloc',
3328            'cluster_alloc_bytes', 'cluster_free', 'flush_to_os',
3329            'flush_to_disk', 'pwritev_rmw_head', 'pwritev_rmw_after_head',
3330            'pwritev_rmw_tail', 'pwritev_rmw_after_tail', 'pwritev',
3331            'pwritev_zero', 'pwritev_done', 'empty_image_prepare',
3332            'l1_shrink_write_table', 'l1_shrink_free_l2_clusters',
3333            'cor_write', 'cluster_alloc_space', 'none'] }
3334
3335##
3336# @BlkdebugIOType:
3337#
3338# Kinds of I/O that blkdebug can inject errors in.
3339#
3340# @read: .bdrv_co_preadv()
3341#
3342# @write: .bdrv_co_pwritev()
3343#
3344# @write-zeroes: .bdrv_co_pwrite_zeroes()
3345#
3346# @discard: .bdrv_co_pdiscard()
3347#
3348# @flush: .bdrv_co_flush_to_disk()
3349#
3350# @block-status: .bdrv_co_block_status()
3351#
3352# Since: 4.1
3353##
3354{ 'enum': 'BlkdebugIOType', 'prefix': 'BLKDEBUG_IO_TYPE',
3355  'data': [ 'read', 'write', 'write-zeroes', 'discard', 'flush',
3356            'block-status' ] }
3357
3358##
3359# @BlkdebugInjectErrorOptions:
3360#
3361# Describes a single error injection for blkdebug.
3362#
3363# @event:       trigger event
3364#
3365# @state:       the state identifier blkdebug needs to be in to
3366#               actually trigger the event; defaults to "any"
3367#
3368# @iotype:      the type of I/O operations on which this error should
3369#               be injected; defaults to "all read, write,
3370#               write-zeroes, discard, and flush operations"
3371#               (since: 4.1)
3372#
3373# @errno:       error identifier (errno) to be returned; defaults to
3374#               EIO
3375#
3376# @sector:      specifies the sector index which has to be affected
3377#               in order to actually trigger the event; defaults to "any
3378#               sector"
3379#
3380# @once:        disables further events after this one has been
3381#               triggered; defaults to false
3382#
3383# @immediately: fail immediately; defaults to false
3384#
3385# Since: 2.9
3386##
3387{ 'struct': 'BlkdebugInjectErrorOptions',
3388  'data': { 'event': 'BlkdebugEvent',
3389            '*state': 'int',
3390            '*iotype': 'BlkdebugIOType',
3391            '*errno': 'int',
3392            '*sector': 'int',
3393            '*once': 'bool',
3394            '*immediately': 'bool' } }
3395
3396##
3397# @BlkdebugSetStateOptions:
3398#
3399# Describes a single state-change event for blkdebug.
3400#
3401# @event:       trigger event
3402#
3403# @state:       the current state identifier blkdebug needs to be in;
3404#               defaults to "any"
3405#
3406# @new_state:   the state identifier blkdebug is supposed to assume if
3407#               this event is triggered
3408#
3409# Since: 2.9
3410##
3411{ 'struct': 'BlkdebugSetStateOptions',
3412  'data': { 'event': 'BlkdebugEvent',
3413            '*state': 'int',
3414            'new_state': 'int' } }
3415
3416##
3417# @BlockdevOptionsBlkdebug:
3418#
3419# Driver specific block device options for blkdebug.
3420#
3421# @image:           underlying raw block device (or image file)
3422#
3423# @config:          filename of the configuration file
3424#
3425# @align:           required alignment for requests in bytes, must be
3426#                   positive power of 2, or 0 for default
3427#
3428# @max-transfer:    maximum size for I/O transfers in bytes, must be
3429#                   positive multiple of @align and of the underlying
3430#                   file's request alignment (but need not be a power of
3431#                   2), or 0 for default (since 2.10)
3432#
3433# @opt-write-zero:  preferred alignment for write zero requests in bytes,
3434#                   must be positive multiple of @align and of the
3435#                   underlying file's request alignment (but need not be a
3436#                   power of 2), or 0 for default (since 2.10)
3437#
3438# @max-write-zero:  maximum size for write zero requests in bytes, must be
3439#                   positive multiple of @align, of @opt-write-zero, and of
3440#                   the underlying file's request alignment (but need not
3441#                   be a power of 2), or 0 for default (since 2.10)
3442#
3443# @opt-discard:     preferred alignment for discard requests in bytes, must
3444#                   be positive multiple of @align and of the underlying
3445#                   file's request alignment (but need not be a power of
3446#                   2), or 0 for default (since 2.10)
3447#
3448# @max-discard:     maximum size for discard requests in bytes, must be
3449#                   positive multiple of @align, of @opt-discard, and of
3450#                   the underlying file's request alignment (but need not
3451#                   be a power of 2), or 0 for default (since 2.10)
3452#
3453# @inject-error:    array of error injection descriptions
3454#
3455# @set-state:       array of state-change descriptions
3456#
3457# Since: 2.9
3458##
3459{ 'struct': 'BlockdevOptionsBlkdebug',
3460  'data': { 'image': 'BlockdevRef',
3461            '*config': 'str',
3462            '*align': 'int', '*max-transfer': 'int32',
3463            '*opt-write-zero': 'int32', '*max-write-zero': 'int32',
3464            '*opt-discard': 'int32', '*max-discard': 'int32',
3465            '*inject-error': ['BlkdebugInjectErrorOptions'],
3466            '*set-state': ['BlkdebugSetStateOptions'] } }
3467
3468##
3469# @BlockdevOptionsBlklogwrites:
3470#
3471# Driver specific block device options for blklogwrites.
3472#
3473# @file:            block device
3474#
3475# @log:             block device used to log writes to @file
3476#
3477# @log-sector-size: sector size used in logging writes to @file, determines
3478#                   granularity of offsets and sizes of writes (default: 512)
3479#
3480# @log-append:      append to an existing log (default: false)
3481#
3482# @log-super-update-interval: interval of write requests after which the log
3483#                             super block is updated to disk (default: 4096)
3484#
3485# Since: 3.0
3486##
3487{ 'struct': 'BlockdevOptionsBlklogwrites',
3488  'data': { 'file': 'BlockdevRef',
3489            'log': 'BlockdevRef',
3490            '*log-sector-size': 'uint32',
3491            '*log-append': 'bool',
3492            '*log-super-update-interval': 'uint64' } }
3493
3494##
3495# @BlockdevOptionsBlkverify:
3496#
3497# Driver specific block device options for blkverify.
3498#
3499# @test:    block device to be tested
3500#
3501# @raw:     raw image used for verification
3502#
3503# Since: 2.9
3504##
3505{ 'struct': 'BlockdevOptionsBlkverify',
3506  'data': { 'test': 'BlockdevRef',
3507            'raw': 'BlockdevRef' } }
3508
3509##
3510# @BlockdevOptionsBlkreplay:
3511#
3512# Driver specific block device options for blkreplay.
3513#
3514# @image:     disk image which should be controlled with blkreplay
3515#
3516# Since: 4.2
3517##
3518{ 'struct': 'BlockdevOptionsBlkreplay',
3519  'data': { 'image': 'BlockdevRef' } }
3520
3521##
3522# @QuorumReadPattern:
3523#
3524# An enumeration of quorum read patterns.
3525#
3526# @quorum: read all the children and do a quorum vote on reads
3527#
3528# @fifo: read only from the first child that has not failed
3529#
3530# Since: 2.9
3531##
3532{ 'enum': 'QuorumReadPattern', 'data': [ 'quorum', 'fifo' ] }
3533
3534##
3535# @BlockdevOptionsQuorum:
3536#
3537# Driver specific block device options for Quorum
3538#
3539# @blkverify:      true if the driver must print content mismatch
3540#                  set to false by default
3541#
3542# @children:       the children block devices to use
3543#
3544# @vote-threshold: the vote limit under which a read will fail
3545#
3546# @rewrite-corrupted: rewrite corrupted data when quorum is reached
3547#                     (Since 2.1)
3548#
3549# @read-pattern: choose read pattern and set to quorum by default
3550#                (Since 2.2)
3551#
3552# Since: 2.9
3553##
3554{ 'struct': 'BlockdevOptionsQuorum',
3555  'data': { '*blkverify': 'bool',
3556            'children': [ 'BlockdevRef' ],
3557            'vote-threshold': 'int',
3558            '*rewrite-corrupted': 'bool',
3559            '*read-pattern': 'QuorumReadPattern' } }
3560
3561##
3562# @BlockdevOptionsGluster:
3563#
3564# Driver specific block device options for Gluster
3565#
3566# @volume:      name of gluster volume where VM image resides
3567#
3568# @path:        absolute path to image file in gluster volume
3569#
3570# @server:      gluster servers description
3571#
3572# @debug:       libgfapi log level (default '4' which is Error)
3573#               (Since 2.8)
3574#
3575# @logfile:     libgfapi log file (default /dev/stderr) (Since 2.8)
3576#
3577# Since: 2.9
3578##
3579{ 'struct': 'BlockdevOptionsGluster',
3580  'data': { 'volume': 'str',
3581            'path': 'str',
3582            'server': ['SocketAddress'],
3583            '*debug': 'int',
3584            '*logfile': 'str' } }
3585
3586##
3587# @IscsiTransport:
3588#
3589# An enumeration of libiscsi transport types
3590#
3591# Since: 2.9
3592##
3593{ 'enum': 'IscsiTransport',
3594  'data': [ 'tcp', 'iser' ] }
3595
3596##
3597# @IscsiHeaderDigest:
3598#
3599# An enumeration of header digests supported by libiscsi
3600#
3601# Since: 2.9
3602##
3603{ 'enum': 'IscsiHeaderDigest',
3604  'prefix': 'QAPI_ISCSI_HEADER_DIGEST',
3605  'data': [ 'crc32c', 'none', 'crc32c-none', 'none-crc32c' ] }
3606
3607##
3608# @BlockdevOptionsIscsi:
3609#
3610# @transport:       The iscsi transport type
3611#
3612# @portal:          The address of the iscsi portal
3613#
3614# @target:          The target iqn name
3615#
3616# @lun:             LUN to connect to. Defaults to 0.
3617#
3618# @user:            User name to log in with. If omitted, no CHAP
3619#                   authentication is performed.
3620#
3621# @password-secret: The ID of a QCryptoSecret object providing
3622#                   the password for the login. This option is required if
3623#                   @user is specified.
3624#
3625# @initiator-name:  The iqn name we want to identify to the target
3626#                   as. If this option is not specified, an initiator name is
3627#                   generated automatically.
3628#
3629# @header-digest:   The desired header digest. Defaults to
3630#                   none-crc32c.
3631#
3632# @timeout:         Timeout in seconds after which a request will
3633#                   timeout. 0 means no timeout and is the default.
3634#
3635# Driver specific block device options for iscsi
3636#
3637# Since: 2.9
3638##
3639{ 'struct': 'BlockdevOptionsIscsi',
3640  'data': { 'transport': 'IscsiTransport',
3641            'portal': 'str',
3642            'target': 'str',
3643            '*lun': 'int',
3644            '*user': 'str',
3645            '*password-secret': 'str',
3646            '*initiator-name': 'str',
3647            '*header-digest': 'IscsiHeaderDigest',
3648            '*timeout': 'int' } }
3649
3650
3651##
3652# @RbdAuthMode:
3653#
3654# Since: 3.0
3655##
3656{ 'enum': 'RbdAuthMode',
3657  'data': [ 'cephx', 'none' ] }
3658
3659##
3660# @BlockdevOptionsRbd:
3661#
3662# @pool:               Ceph pool name.
3663#
3664# @image:              Image name in the Ceph pool.
3665#
3666# @conf:               path to Ceph configuration file.  Values
3667#                      in the configuration file will be overridden by
3668#                      options specified via QAPI.
3669#
3670# @snapshot:           Ceph snapshot name.
3671#
3672# @user:               Ceph id name.
3673#
3674# @auth-client-required: Acceptable authentication modes.
3675#                      This maps to Ceph configuration option
3676#                      "auth_client_required".  (Since 3.0)
3677#
3678# @key-secret:         ID of a QCryptoSecret object providing a key
3679#                      for cephx authentication.
3680#                      This maps to Ceph configuration option
3681#                      "key".  (Since 3.0)
3682#
3683# @server:             Monitor host address and port.  This maps
3684#                      to the "mon_host" Ceph option.
3685#
3686# Since: 2.9
3687##
3688{ 'struct': 'BlockdevOptionsRbd',
3689  'data': { 'pool': 'str',
3690            'image': 'str',
3691            '*conf': 'str',
3692            '*snapshot': 'str',
3693            '*user': 'str',
3694            '*auth-client-required': ['RbdAuthMode'],
3695            '*key-secret': 'str',
3696            '*server': ['InetSocketAddressBase'] } }
3697
3698##
3699# @BlockdevOptionsSheepdog:
3700#
3701# Driver specific block device options for sheepdog
3702#
3703# @vdi:         Virtual disk image name
3704# @server:      The Sheepdog server to connect to
3705# @snap-id:     Snapshot ID
3706# @tag:         Snapshot tag name
3707#
3708# Only one of @snap-id and @tag may be present.
3709#
3710# Since: 2.9
3711##
3712{ 'struct': 'BlockdevOptionsSheepdog',
3713  'data': { 'server': 'SocketAddress',
3714            'vdi': 'str',
3715            '*snap-id': 'uint32',
3716            '*tag': 'str' } }
3717
3718##
3719# @ReplicationMode:
3720#
3721# An enumeration of replication modes.
3722#
3723# @primary: Primary mode, the vm's state will be sent to secondary QEMU.
3724#
3725# @secondary: Secondary mode, receive the vm's state from primary QEMU.
3726#
3727# Since: 2.9
3728##
3729{ 'enum' : 'ReplicationMode', 'data' : [ 'primary', 'secondary' ],
3730  'if': 'defined(CONFIG_REPLICATION)' }
3731
3732##
3733# @BlockdevOptionsReplication:
3734#
3735# Driver specific block device options for replication
3736#
3737# @mode: the replication mode
3738#
3739# @top-id: In secondary mode, node name or device ID of the root
3740#          node who owns the replication node chain. Must not be given in
3741#          primary mode.
3742#
3743# Since: 2.9
3744##
3745{ 'struct': 'BlockdevOptionsReplication',
3746  'base': 'BlockdevOptionsGenericFormat',
3747  'data': { 'mode': 'ReplicationMode',
3748            '*top-id': 'str' },
3749  'if': 'defined(CONFIG_REPLICATION)' }
3750
3751##
3752# @NFSTransport:
3753#
3754# An enumeration of NFS transport types
3755#
3756# @inet:        TCP transport
3757#
3758# Since: 2.9
3759##
3760{ 'enum': 'NFSTransport',
3761  'data': [ 'inet' ] }
3762
3763##
3764# @NFSServer:
3765#
3766# Captures the address of the socket
3767#
3768# @type:        transport type used for NFS (only TCP supported)
3769#
3770# @host:        host address for NFS server
3771#
3772# Since: 2.9
3773##
3774{ 'struct': 'NFSServer',
3775  'data': { 'type': 'NFSTransport',
3776            'host': 'str' } }
3777
3778##
3779# @BlockdevOptionsNfs:
3780#
3781# Driver specific block device option for NFS
3782#
3783# @server:                  host address
3784#
3785# @path:                    path of the image on the host
3786#
3787# @user:                    UID value to use when talking to the
3788#                           server (defaults to 65534 on Windows and getuid()
3789#                           on unix)
3790#
3791# @group:                   GID value to use when talking to the
3792#                           server (defaults to 65534 on Windows and getgid()
3793#                           in unix)
3794#
3795# @tcp-syn-count:           number of SYNs during the session
3796#                           establishment (defaults to libnfs default)
3797#
3798# @readahead-size:          set the readahead size in bytes (defaults
3799#                           to libnfs default)
3800#
3801# @page-cache-size:         set the pagecache size in bytes (defaults
3802#                           to libnfs default)
3803#
3804# @debug:                   set the NFS debug level (max 2) (defaults
3805#                           to libnfs default)
3806#
3807# Since: 2.9
3808##
3809{ 'struct': 'BlockdevOptionsNfs',
3810  'data': { 'server': 'NFSServer',
3811            'path': 'str',
3812            '*user': 'int',
3813            '*group': 'int',
3814            '*tcp-syn-count': 'int',
3815            '*readahead-size': 'int',
3816            '*page-cache-size': 'int',
3817            '*debug': 'int' } }
3818
3819##
3820# @BlockdevOptionsCurlBase:
3821#
3822# Driver specific block device options shared by all protocols supported by the
3823# curl backend.
3824#
3825# @url:                     URL of the image file
3826#
3827# @readahead:               Size of the read-ahead cache; must be a multiple of
3828#                           512 (defaults to 256 kB)
3829#
3830# @timeout:                 Timeout for connections, in seconds (defaults to 5)
3831#
3832# @username:                Username for authentication (defaults to none)
3833#
3834# @password-secret:         ID of a QCryptoSecret object providing a password
3835#                           for authentication (defaults to no password)
3836#
3837# @proxy-username:          Username for proxy authentication (defaults to none)
3838#
3839# @proxy-password-secret:   ID of a QCryptoSecret object providing a password
3840#                           for proxy authentication (defaults to no password)
3841#
3842# Since: 2.9
3843##
3844{ 'struct': 'BlockdevOptionsCurlBase',
3845  'data': { 'url': 'str',
3846            '*readahead': 'int',
3847            '*timeout': 'int',
3848            '*username': 'str',
3849            '*password-secret': 'str',
3850            '*proxy-username': 'str',
3851            '*proxy-password-secret': 'str' } }
3852
3853##
3854# @BlockdevOptionsCurlHttp:
3855#
3856# Driver specific block device options for HTTP connections over the curl
3857# backend.  URLs must start with "http://".
3858#
3859# @cookie:      List of cookies to set; format is
3860#               "name1=content1; name2=content2;" as explained by
3861#               CURLOPT_COOKIE(3). Defaults to no cookies.
3862#
3863# @cookie-secret: ID of a QCryptoSecret object providing the cookie data in a
3864#                 secure way. See @cookie for the format. (since 2.10)
3865#
3866# Since: 2.9
3867##
3868{ 'struct': 'BlockdevOptionsCurlHttp',
3869  'base': 'BlockdevOptionsCurlBase',
3870  'data': { '*cookie': 'str',
3871            '*cookie-secret': 'str'} }
3872
3873##
3874# @BlockdevOptionsCurlHttps:
3875#
3876# Driver specific block device options for HTTPS connections over the curl
3877# backend.  URLs must start with "https://".
3878#
3879# @cookie:      List of cookies to set; format is
3880#               "name1=content1; name2=content2;" as explained by
3881#               CURLOPT_COOKIE(3). Defaults to no cookies.
3882#
3883# @sslverify:   Whether to verify the SSL certificate's validity (defaults to
3884#               true)
3885#
3886# @cookie-secret: ID of a QCryptoSecret object providing the cookie data in a
3887#                 secure way. See @cookie for the format. (since 2.10)
3888#
3889# Since: 2.9
3890##
3891{ 'struct': 'BlockdevOptionsCurlHttps',
3892  'base': 'BlockdevOptionsCurlBase',
3893  'data': { '*cookie': 'str',
3894            '*sslverify': 'bool',
3895            '*cookie-secret': 'str'} }
3896
3897##
3898# @BlockdevOptionsCurlFtp:
3899#
3900# Driver specific block device options for FTP connections over the curl
3901# backend.  URLs must start with "ftp://".
3902#
3903# Since: 2.9
3904##
3905{ 'struct': 'BlockdevOptionsCurlFtp',
3906  'base': 'BlockdevOptionsCurlBase',
3907  'data': { } }
3908
3909##
3910# @BlockdevOptionsCurlFtps:
3911#
3912# Driver specific block device options for FTPS connections over the curl
3913# backend.  URLs must start with "ftps://".
3914#
3915# @sslverify:   Whether to verify the SSL certificate's validity (defaults to
3916#               true)
3917#
3918# Since: 2.9
3919##
3920{ 'struct': 'BlockdevOptionsCurlFtps',
3921  'base': 'BlockdevOptionsCurlBase',
3922  'data': { '*sslverify': 'bool' } }
3923
3924##
3925# @BlockdevOptionsNbd:
3926#
3927# Driver specific block device options for NBD.
3928#
3929# @server:      NBD server address
3930#
3931# @export:      export name
3932#
3933# @tls-creds:   TLS credentials ID
3934#
3935# @x-dirty-bitmap: A "qemu:dirty-bitmap:NAME" string to query in place of
3936#                  traditional "base:allocation" block status (see
3937#                  NBD_OPT_LIST_META_CONTEXT in the NBD protocol) (since 3.0)
3938#
3939# @reconnect-delay: On an unexpected disconnect, the nbd client tries to
3940#                   connect again until succeeding or encountering a serious
3941#                   error.  During the first @reconnect-delay seconds, all
3942#                   requests are paused and will be rerun on a successful
3943#                   reconnect. After that time, any delayed requests and all
3944#                   future requests before a successful reconnect will
3945#                   immediately fail. Default 0 (Since 4.2)
3946#
3947# Since: 2.9
3948##
3949{ 'struct': 'BlockdevOptionsNbd',
3950  'data': { 'server': 'SocketAddress',
3951            '*export': 'str',
3952            '*tls-creds': 'str',
3953            '*x-dirty-bitmap': 'str',
3954            '*reconnect-delay': 'uint32' } }
3955
3956##
3957# @BlockdevOptionsRaw:
3958#
3959# Driver specific block device options for the raw driver.
3960#
3961# @offset:      position where the block device starts
3962# @size:        the assumed size of the device
3963#
3964# Since: 2.9
3965##
3966{ 'struct': 'BlockdevOptionsRaw',
3967  'base': 'BlockdevOptionsGenericFormat',
3968  'data': { '*offset': 'int', '*size': 'int' } }
3969
3970##
3971# @BlockdevOptionsVxHS:
3972#
3973# Driver specific block device options for VxHS
3974#
3975# @vdisk-id:    UUID of VxHS volume
3976# @server:      vxhs server IP, port
3977# @tls-creds:   TLS credentials ID
3978#
3979# Since: 2.10
3980##
3981{ 'struct': 'BlockdevOptionsVxHS',
3982  'data': { 'vdisk-id': 'str',
3983            'server': 'InetSocketAddressBase',
3984            '*tls-creds': 'str' } }
3985
3986##
3987# @BlockdevOptionsThrottle:
3988#
3989# Driver specific block device options for the throttle driver
3990#
3991# @throttle-group:   the name of the throttle-group object to use. It
3992#                    must already exist.
3993# @file:             reference to or definition of the data source block device
3994# Since: 2.11
3995##
3996{ 'struct': 'BlockdevOptionsThrottle',
3997  'data': { 'throttle-group': 'str',
3998            'file' : 'BlockdevRef'
3999             } }
4000##
4001# @BlockdevOptions:
4002#
4003# Options for creating a block device.  Many options are available for all
4004# block devices, independent of the block driver:
4005#
4006# @driver:        block driver name
4007# @node-name:     the node name of the new node (Since 2.0).
4008#                 This option is required on the top level of blockdev-add.
4009#                 Valid node names start with an alphabetic character and may
4010#                 contain only alphanumeric characters, '-', '.' and '_'. Their
4011#                 maximum length is 31 characters.
4012# @discard:       discard-related options (default: ignore)
4013# @cache:         cache-related options
4014# @read-only:     whether the block device should be read-only (default: false).
4015#                 Note that some block drivers support only read-only access,
4016#                 either generally or in certain configurations. In this case,
4017#                 the default value does not work and the option must be
4018#                 specified explicitly.
4019# @auto-read-only: if true and @read-only is false, QEMU may automatically
4020#                  decide not to open the image read-write as requested, but
4021#                  fall back to read-only instead (and switch between the modes
4022#                  later), e.g. depending on whether the image file is writable
4023#                  or whether a writing user is attached to the node
4024#                  (default: false, since 3.1)
4025# @detect-zeroes: detect and optimize zero writes (Since 2.1)
4026#                 (default: off)
4027# @force-share:   force share all permission on added nodes.
4028#                 Requires read-only=true. (Since 2.10)
4029#
4030# Remaining options are determined by the block driver.
4031#
4032# Since: 2.9
4033##
4034{ 'union': 'BlockdevOptions',
4035  'base': { 'driver': 'BlockdevDriver',
4036            '*node-name': 'str',
4037            '*discard': 'BlockdevDiscardOptions',
4038            '*cache': 'BlockdevCacheOptions',
4039            '*read-only': 'bool',
4040            '*auto-read-only': 'bool',
4041            '*force-share': 'bool',
4042            '*detect-zeroes': 'BlockdevDetectZeroesOptions' },
4043  'discriminator': 'driver',
4044  'data': {
4045      'blkdebug':   'BlockdevOptionsBlkdebug',
4046      'blklogwrites':'BlockdevOptionsBlklogwrites',
4047      'blkverify':  'BlockdevOptionsBlkverify',
4048      'blkreplay':  'BlockdevOptionsBlkreplay',
4049      'bochs':      'BlockdevOptionsGenericFormat',
4050      'cloop':      'BlockdevOptionsGenericFormat',
4051      'copy-on-read':'BlockdevOptionsGenericFormat',
4052      'dmg':        'BlockdevOptionsGenericFormat',
4053      'file':       'BlockdevOptionsFile',
4054      'ftp':        'BlockdevOptionsCurlFtp',
4055      'ftps':       'BlockdevOptionsCurlFtps',
4056      'gluster':    'BlockdevOptionsGluster',
4057      'host_cdrom': 'BlockdevOptionsFile',
4058      'host_device':'BlockdevOptionsFile',
4059      'http':       'BlockdevOptionsCurlHttp',
4060      'https':      'BlockdevOptionsCurlHttps',
4061      'iscsi':      'BlockdevOptionsIscsi',
4062      'luks':       'BlockdevOptionsLUKS',
4063      'nbd':        'BlockdevOptionsNbd',
4064      'nfs':        'BlockdevOptionsNfs',
4065      'null-aio':   'BlockdevOptionsNull',
4066      'null-co':    'BlockdevOptionsNull',
4067      'nvme':       'BlockdevOptionsNVMe',
4068      'parallels':  'BlockdevOptionsGenericFormat',
4069      'qcow2':      'BlockdevOptionsQcow2',
4070      'qcow':       'BlockdevOptionsQcow',
4071      'qed':        'BlockdevOptionsGenericCOWFormat',
4072      'quorum':     'BlockdevOptionsQuorum',
4073      'raw':        'BlockdevOptionsRaw',
4074      'rbd':        'BlockdevOptionsRbd',
4075      'replication': { 'type': 'BlockdevOptionsReplication',
4076                       'if': 'defined(CONFIG_REPLICATION)' },
4077      'sheepdog':   'BlockdevOptionsSheepdog',
4078      'ssh':        'BlockdevOptionsSsh',
4079      'throttle':   'BlockdevOptionsThrottle',
4080      'vdi':        'BlockdevOptionsGenericFormat',
4081      'vhdx':       'BlockdevOptionsGenericFormat',
4082      'vmdk':       'BlockdevOptionsGenericCOWFormat',
4083      'vpc':        'BlockdevOptionsGenericFormat',
4084      'vvfat':      'BlockdevOptionsVVFAT',
4085      'vxhs':       'BlockdevOptionsVxHS'
4086  } }
4087
4088##
4089# @BlockdevRef:
4090#
4091# Reference to a block device.
4092#
4093# @definition:      defines a new block device inline
4094# @reference:       references the ID of an existing block device
4095#
4096# Since: 2.9
4097##
4098{ 'alternate': 'BlockdevRef',
4099  'data': { 'definition': 'BlockdevOptions',
4100            'reference': 'str' } }
4101
4102##
4103# @BlockdevRefOrNull:
4104#
4105# Reference to a block device.
4106#
4107# @definition:      defines a new block device inline
4108# @reference:       references the ID of an existing block device.
4109#                   An empty string means that no block device should
4110#                   be referenced.  Deprecated; use null instead.
4111# @null:            No block device should be referenced (since 2.10)
4112#
4113# Since: 2.9
4114##
4115{ 'alternate': 'BlockdevRefOrNull',
4116  'data': { 'definition': 'BlockdevOptions',
4117            'reference': 'str',
4118            'null': 'null' } }
4119
4120##
4121# @blockdev-add:
4122#
4123# Creates a new block device. If the @id option is given at the top level, a
4124# BlockBackend will be created; otherwise, @node-name is mandatory at the top
4125# level and no BlockBackend will be created.
4126#
4127# Since: 2.9
4128#
4129# Example:
4130#
4131# 1.
4132# -> { "execute": "blockdev-add",
4133#      "arguments": {
4134#           "driver": "qcow2",
4135#           "node-name": "test1",
4136#           "file": {
4137#               "driver": "file",
4138#               "filename": "test.qcow2"
4139#            }
4140#       }
4141#     }
4142# <- { "return": {} }
4143#
4144# 2.
4145# -> { "execute": "blockdev-add",
4146#      "arguments": {
4147#           "driver": "qcow2",
4148#           "node-name": "node0",
4149#           "discard": "unmap",
4150#           "cache": {
4151#              "direct": true
4152#            },
4153#            "file": {
4154#              "driver": "file",
4155#              "filename": "/tmp/test.qcow2"
4156#            },
4157#            "backing": {
4158#               "driver": "raw",
4159#               "file": {
4160#                  "driver": "file",
4161#                  "filename": "/dev/fdset/4"
4162#                }
4163#            }
4164#        }
4165#      }
4166#
4167# <- { "return": {} }
4168#
4169##
4170{ 'command': 'blockdev-add', 'data': 'BlockdevOptions', 'boxed': true }
4171
4172##
4173# @x-blockdev-reopen:
4174#
4175# Reopens a block device using the given set of options. Any option
4176# not specified will be reset to its default value regardless of its
4177# previous status. If an option cannot be changed or a particular
4178# driver does not support reopening then the command will return an
4179# error.
4180#
4181# The top-level @node-name option (from BlockdevOptions) must be
4182# specified and is used to select the block device to be reopened.
4183# Other @node-name options must be either omitted or set to the
4184# current name of the appropriate node. This command won't change any
4185# node name and any attempt to do it will result in an error.
4186#
4187# In the case of options that refer to child nodes, the behavior of
4188# this command depends on the value:
4189#
4190#  1) A set of options (BlockdevOptions): the child is reopened with
4191#     the specified set of options.
4192#
4193#  2) A reference to the current child: the child is reopened using
4194#     its existing set of options.
4195#
4196#  3) A reference to a different node: the current child is replaced
4197#     with the specified one.
4198#
4199#  4) NULL: the current child (if any) is detached.
4200#
4201# Options (1) and (2) are supported in all cases, but at the moment
4202# only @backing allows replacing or detaching an existing child.
4203#
4204# Unlike with blockdev-add, the @backing option must always be present
4205# unless the node being reopened does not have a backing file and its
4206# image does not have a default backing file name as part of its
4207# metadata.
4208#
4209# Since: 4.0
4210##
4211{ 'command': 'x-blockdev-reopen',
4212  'data': 'BlockdevOptions', 'boxed': true }
4213
4214##
4215# @blockdev-del:
4216#
4217# Deletes a block device that has been added using blockdev-add.
4218# The command will fail if the node is attached to a device or is
4219# otherwise being used.
4220#
4221# @node-name: Name of the graph node to delete.
4222#
4223# Since: 2.9
4224#
4225# Example:
4226#
4227# -> { "execute": "blockdev-add",
4228#      "arguments": {
4229#           "driver": "qcow2",
4230#           "node-name": "node0",
4231#           "file": {
4232#               "driver": "file",
4233#               "filename": "test.qcow2"
4234#           }
4235#      }
4236#    }
4237# <- { "return": {} }
4238#
4239# -> { "execute": "blockdev-del",
4240#      "arguments": { "node-name": "node0" }
4241#    }
4242# <- { "return": {} }
4243#
4244##
4245{ 'command': 'blockdev-del', 'data': { 'node-name': 'str' } }
4246
4247##
4248# @BlockdevCreateOptionsFile:
4249#
4250# Driver specific image creation options for file.
4251#
4252# @filename         Filename for the new image file
4253# @size             Size of the virtual disk in bytes
4254# @preallocation    Preallocation mode for the new image (default: off;
4255#                   allowed values: off,
4256#                   falloc (if defined CONFIG_POSIX_FALLOCATE),
4257#                   full (if defined CONFIG_POSIX))
4258# @nocow            Turn off copy-on-write (valid only on btrfs; default: off)
4259#
4260# Since: 2.12
4261##
4262{ 'struct': 'BlockdevCreateOptionsFile',
4263  'data': { 'filename':         'str',
4264            'size':             'size',
4265            '*preallocation':   'PreallocMode',
4266            '*nocow':           'bool' } }
4267
4268##
4269# @BlockdevCreateOptionsGluster:
4270#
4271# Driver specific image creation options for gluster.
4272#
4273# @location         Where to store the new image file
4274# @size             Size of the virtual disk in bytes
4275# @preallocation    Preallocation mode for the new image (default: off;
4276#                   allowed values: off,
4277#                   falloc (if defined CONFIG_GLUSTERFS_FALLOCATE),
4278#                   full (if defined CONFIG_GLUSTERFS_ZEROFILL))
4279#
4280# Since: 2.12
4281##
4282{ 'struct': 'BlockdevCreateOptionsGluster',
4283  'data': { 'location':         'BlockdevOptionsGluster',
4284            'size':             'size',
4285            '*preallocation':   'PreallocMode' } }
4286
4287##
4288# @BlockdevCreateOptionsLUKS:
4289#
4290# Driver specific image creation options for LUKS.
4291#
4292# @file             Node to create the image format on
4293# @size             Size of the virtual disk in bytes
4294# @preallocation    Preallocation mode for the new image
4295#                   (since: 4.2)
4296#                   (default: off; allowed values: off, metadata, falloc, full)
4297#
4298# Since: 2.12
4299##
4300{ 'struct': 'BlockdevCreateOptionsLUKS',
4301  'base': 'QCryptoBlockCreateOptionsLUKS',
4302  'data': { 'file':             'BlockdevRef',
4303            'size':             'size',
4304            '*preallocation':   'PreallocMode' } }
4305
4306##
4307# @BlockdevCreateOptionsNfs:
4308#
4309# Driver specific image creation options for NFS.
4310#
4311# @location         Where to store the new image file
4312# @size             Size of the virtual disk in bytes
4313#
4314# Since: 2.12
4315##
4316{ 'struct': 'BlockdevCreateOptionsNfs',
4317  'data': { 'location':         'BlockdevOptionsNfs',
4318            'size':             'size' } }
4319
4320##
4321# @BlockdevCreateOptionsParallels:
4322#
4323# Driver specific image creation options for parallels.
4324#
4325# @file             Node to create the image format on
4326# @size             Size of the virtual disk in bytes
4327# @cluster-size     Cluster size in bytes (default: 1 MB)
4328#
4329# Since: 2.12
4330##
4331{ 'struct': 'BlockdevCreateOptionsParallels',
4332  'data': { 'file':             'BlockdevRef',
4333            'size':             'size',
4334            '*cluster-size':    'size' } }
4335
4336##
4337# @BlockdevCreateOptionsQcow:
4338#
4339# Driver specific image creation options for qcow.
4340#
4341# @file             Node to create the image format on
4342# @size             Size of the virtual disk in bytes
4343# @backing-file     File name of the backing file if a backing file
4344#                   should be used
4345# @encrypt          Encryption options if the image should be encrypted
4346#
4347# Since: 2.12
4348##
4349{ 'struct': 'BlockdevCreateOptionsQcow',
4350  'data': { 'file':             'BlockdevRef',
4351            'size':             'size',
4352            '*backing-file':    'str',
4353            '*encrypt':         'QCryptoBlockCreateOptions' } }
4354
4355##
4356# @BlockdevQcow2Version:
4357#
4358# @v2:  The original QCOW2 format as introduced in qemu 0.10 (version 2)
4359# @v3:  The extended QCOW2 format as introduced in qemu 1.1 (version 3)
4360#
4361# Since: 2.12
4362##
4363{ 'enum': 'BlockdevQcow2Version',
4364  'data': [ 'v2', 'v3' ] }
4365
4366
4367##
4368# @BlockdevCreateOptionsQcow2:
4369#
4370# Driver specific image creation options for qcow2.
4371#
4372# @file             Node to create the image format on
4373# @data-file        Node to use as an external data file in which all guest
4374#                   data is stored so that only metadata remains in the qcow2
4375#                   file (since: 4.0)
4376# @data-file-raw    True if the external data file must stay valid as a
4377#                   standalone (read-only) raw image without looking at qcow2
4378#                   metadata (default: false; since: 4.0)
4379# @size             Size of the virtual disk in bytes
4380# @version          Compatibility level (default: v3)
4381# @backing-file     File name of the backing file if a backing file
4382#                   should be used
4383# @backing-fmt      Name of the block driver to use for the backing file
4384# @encrypt          Encryption options if the image should be encrypted
4385# @cluster-size     qcow2 cluster size in bytes (default: 65536)
4386# @preallocation    Preallocation mode for the new image (default: off;
4387#                   allowed values: off, falloc, full, metadata)
4388# @lazy-refcounts   True if refcounts may be updated lazily (default: off)
4389# @refcount-bits    Width of reference counts in bits (default: 16)
4390#
4391# Since: 2.12
4392##
4393{ 'struct': 'BlockdevCreateOptionsQcow2',
4394  'data': { 'file':             'BlockdevRef',
4395            '*data-file':       'BlockdevRef',
4396            '*data-file-raw':   'bool',
4397            'size':             'size',
4398            '*version':         'BlockdevQcow2Version',
4399            '*backing-file':    'str',
4400            '*backing-fmt':     'BlockdevDriver',
4401            '*encrypt':         'QCryptoBlockCreateOptions',
4402            '*cluster-size':    'size',
4403            '*preallocation':   'PreallocMode',
4404            '*lazy-refcounts':  'bool',
4405            '*refcount-bits':   'int' } }
4406
4407##
4408# @BlockdevCreateOptionsQed:
4409#
4410# Driver specific image creation options for qed.
4411#
4412# @file             Node to create the image format on
4413# @size             Size of the virtual disk in bytes
4414# @backing-file     File name of the backing file if a backing file
4415#                   should be used
4416# @backing-fmt      Name of the block driver to use for the backing file
4417# @cluster-size     Cluster size in bytes (default: 65536)
4418# @table-size       L1/L2 table size (in clusters)
4419#
4420# Since: 2.12
4421##
4422{ 'struct': 'BlockdevCreateOptionsQed',
4423  'data': { 'file':             'BlockdevRef',
4424            'size':             'size',
4425            '*backing-file':    'str',
4426            '*backing-fmt':     'BlockdevDriver',
4427            '*cluster-size':    'size',
4428            '*table-size':      'int' } }
4429
4430##
4431# @BlockdevCreateOptionsRbd:
4432#
4433# Driver specific image creation options for rbd/Ceph.
4434#
4435# @location         Where to store the new image file. This location cannot
4436#                   point to a snapshot.
4437# @size             Size of the virtual disk in bytes
4438# @cluster-size     RBD object size
4439#
4440# Since: 2.12
4441##
4442{ 'struct': 'BlockdevCreateOptionsRbd',
4443  'data': { 'location':         'BlockdevOptionsRbd',
4444            'size':             'size',
4445            '*cluster-size' :   'size' } }
4446
4447##
4448# @BlockdevVmdkSubformat:
4449#
4450# Subformat options for VMDK images
4451#
4452# @monolithicSparse:     Single file image with sparse cluster allocation
4453#
4454# @monolithicFlat:       Single flat data image and a descriptor file
4455#
4456# @twoGbMaxExtentSparse: Data is split into 2GB (per virtual LBA) sparse extent
4457#                        files, in addition to a descriptor file
4458#
4459# @twoGbMaxExtentFlat:   Data is split into 2GB (per virtual LBA) flat extent
4460#                        files, in addition to a descriptor file
4461#
4462# @streamOptimized:      Single file image sparse cluster allocation, optimized
4463#                        for streaming over network.
4464#
4465# Since: 4.0
4466##
4467{ 'enum': 'BlockdevVmdkSubformat',
4468  'data': [ 'monolithicSparse', 'monolithicFlat', 'twoGbMaxExtentSparse',
4469            'twoGbMaxExtentFlat', 'streamOptimized'] }
4470
4471##
4472# @BlockdevVmdkAdapterType:
4473#
4474# Adapter type info for VMDK images
4475#
4476# Since: 4.0
4477##
4478{ 'enum': 'BlockdevVmdkAdapterType',
4479  'data': [ 'ide', 'buslogic', 'lsilogic', 'legacyESX'] }
4480
4481##
4482# @BlockdevCreateOptionsVmdk:
4483#
4484# Driver specific image creation options for VMDK.
4485#
4486# @file         Where to store the new image file. This refers to the image
4487#               file for monolithcSparse and streamOptimized format, or the
4488#               descriptor file for other formats.
4489# @size         Size of the virtual disk in bytes
4490# @extents      Where to store the data extents. Required for monolithcFlat,
4491#               twoGbMaxExtentSparse and twoGbMaxExtentFlat formats. For
4492#               monolithicFlat, only one entry is required; for
4493#               twoGbMaxExtent* formats, the number of entries required is
4494#               calculated as extent_number = virtual_size / 2GB. Providing
4495#               more extents than will be used is an error.
4496# @subformat    The subformat of the VMDK image. Default: "monolithicSparse".
4497# @backing-file The path of backing file. Default: no backing file is used.
4498# @adapter-type The adapter type used to fill in the descriptor. Default: ide.
4499# @hwversion    Hardware version. The meaningful options are "4" or "6".
4500#               Default: "4".
4501# @zeroed-grain Whether to enable zeroed-grain feature for sparse subformats.
4502#               Default: false.
4503#
4504# Since: 4.0
4505##
4506{ 'struct': 'BlockdevCreateOptionsVmdk',
4507  'data': { 'file':             'BlockdevRef',
4508            'size':             'size',
4509            '*extents':          ['BlockdevRef'],
4510            '*subformat':       'BlockdevVmdkSubformat',
4511            '*backing-file':    'str',
4512            '*adapter-type':    'BlockdevVmdkAdapterType',
4513            '*hwversion':       'str',
4514            '*zeroed-grain':    'bool' } }
4515
4516
4517##
4518# @SheepdogRedundancyType:
4519#
4520# @full             Create a fully replicated vdi with x copies
4521# @erasure-coded    Create an erasure coded vdi with x data strips and
4522#                   y parity strips
4523#
4524# Since: 2.12
4525##
4526{ 'enum': 'SheepdogRedundancyType',
4527  'data': [ 'full', 'erasure-coded' ] }
4528
4529##
4530# @SheepdogRedundancyFull:
4531#
4532# @copies           Number of copies to use (between 1 and 31)
4533#
4534# Since: 2.12
4535##
4536{ 'struct': 'SheepdogRedundancyFull',
4537  'data': { 'copies': 'int' }}
4538
4539##
4540# @SheepdogRedundancyErasureCoded:
4541#
4542# @data-strips      Number of data strips to use (one of {2,4,8,16})
4543# @parity-strips    Number of parity strips to use (between 1 and 15)
4544#
4545# Since: 2.12
4546##
4547{ 'struct': 'SheepdogRedundancyErasureCoded',
4548  'data': { 'data-strips': 'int',
4549            'parity-strips': 'int' }}
4550
4551##
4552# @SheepdogRedundancy:
4553#
4554# Since: 2.12
4555##
4556{ 'union': 'SheepdogRedundancy',
4557  'base': { 'type': 'SheepdogRedundancyType' },
4558  'discriminator': 'type',
4559  'data': { 'full': 'SheepdogRedundancyFull',
4560            'erasure-coded': 'SheepdogRedundancyErasureCoded' } }
4561
4562##
4563# @BlockdevCreateOptionsSheepdog:
4564#
4565# Driver specific image creation options for Sheepdog.
4566#
4567# @location         Where to store the new image file
4568# @size             Size of the virtual disk in bytes
4569# @backing-file     File name of a base image
4570# @preallocation    Preallocation mode for the new image (default: off;
4571#                   allowed values: off, full)
4572# @redundancy       Redundancy of the image
4573# @object-size      Object size of the image
4574#
4575# Since: 2.12
4576##
4577{ 'struct': 'BlockdevCreateOptionsSheepdog',
4578  'data': { 'location':         'BlockdevOptionsSheepdog',
4579            'size':             'size',
4580            '*backing-file':    'str',
4581            '*preallocation':   'PreallocMode',
4582            '*redundancy':      'SheepdogRedundancy',
4583            '*object-size':     'size' } }
4584
4585##
4586# @BlockdevCreateOptionsSsh:
4587#
4588# Driver specific image creation options for SSH.
4589#
4590# @location         Where to store the new image file
4591# @size             Size of the virtual disk in bytes
4592#
4593# Since: 2.12
4594##
4595{ 'struct': 'BlockdevCreateOptionsSsh',
4596  'data': { 'location':         'BlockdevOptionsSsh',
4597            'size':             'size' } }
4598
4599##
4600# @BlockdevCreateOptionsVdi:
4601#
4602# Driver specific image creation options for VDI.
4603#
4604# @file             Node to create the image format on
4605# @size             Size of the virtual disk in bytes
4606# @preallocation    Preallocation mode for the new image (default: off;
4607#                   allowed values: off, metadata)
4608#
4609# Since: 2.12
4610##
4611{ 'struct': 'BlockdevCreateOptionsVdi',
4612  'data': { 'file':             'BlockdevRef',
4613            'size':             'size',
4614            '*preallocation':   'PreallocMode' } }
4615
4616##
4617# @BlockdevVhdxSubformat:
4618#
4619# @dynamic: Growing image file
4620# @fixed:   Preallocated fixed-size image file
4621#
4622# Since: 2.12
4623##
4624{ 'enum': 'BlockdevVhdxSubformat',
4625  'data': [ 'dynamic', 'fixed' ] }
4626
4627##
4628# @BlockdevCreateOptionsVhdx:
4629#
4630# Driver specific image creation options for vhdx.
4631#
4632# @file             Node to create the image format on
4633# @size             Size of the virtual disk in bytes
4634# @log-size         Log size in bytes, must be a multiple of 1 MB
4635#                   (default: 1 MB)
4636# @block-size       Block size in bytes, must be a multiple of 1 MB and not
4637#                   larger than 256 MB (default: automatically choose a block
4638#                   size depending on the image size)
4639# @subformat        vhdx subformat (default: dynamic)
4640# @block-state-zero Force use of payload blocks of type 'ZERO'. Non-standard,
4641#                   but default.  Do not set to 'off' when using 'qemu-img
4642#                   convert' with subformat=dynamic.
4643#
4644# Since: 2.12
4645##
4646{ 'struct': 'BlockdevCreateOptionsVhdx',
4647  'data': { 'file':                 'BlockdevRef',
4648            'size':                 'size',
4649            '*log-size':            'size',
4650            '*block-size':          'size',
4651            '*subformat':           'BlockdevVhdxSubformat',
4652            '*block-state-zero':    'bool' } }
4653
4654##
4655# @BlockdevVpcSubformat:
4656#
4657# @dynamic: Growing image file
4658# @fixed:   Preallocated fixed-size image file
4659#
4660# Since: 2.12
4661##
4662{ 'enum': 'BlockdevVpcSubformat',
4663  'data': [ 'dynamic', 'fixed' ] }
4664
4665##
4666# @BlockdevCreateOptionsVpc:
4667#
4668# Driver specific image creation options for vpc (VHD).
4669#
4670# @file             Node to create the image format on
4671# @size             Size of the virtual disk in bytes
4672# @subformat        vhdx subformat (default: dynamic)
4673# @force-size       Force use of the exact byte size instead of rounding to the
4674#                   next size that can be represented in CHS geometry
4675#                   (default: false)
4676#
4677# Since: 2.12
4678##
4679{ 'struct': 'BlockdevCreateOptionsVpc',
4680  'data': { 'file':                 'BlockdevRef',
4681            'size':                 'size',
4682            '*subformat':           'BlockdevVpcSubformat',
4683            '*force-size':          'bool' } }
4684
4685##
4686# @BlockdevCreateOptions:
4687#
4688# Options for creating an image format on a given node.
4689#
4690# @driver           block driver to create the image format
4691#
4692# Since: 2.12
4693##
4694{ 'union': 'BlockdevCreateOptions',
4695  'base': {
4696      'driver':         'BlockdevDriver' },
4697  'discriminator': 'driver',
4698  'data': {
4699      'file':           'BlockdevCreateOptionsFile',
4700      'gluster':        'BlockdevCreateOptionsGluster',
4701      'luks':           'BlockdevCreateOptionsLUKS',
4702      'nfs':            'BlockdevCreateOptionsNfs',
4703      'parallels':      'BlockdevCreateOptionsParallels',
4704      'qcow':           'BlockdevCreateOptionsQcow',
4705      'qcow2':          'BlockdevCreateOptionsQcow2',
4706      'qed':            'BlockdevCreateOptionsQed',
4707      'rbd':            'BlockdevCreateOptionsRbd',
4708      'sheepdog':       'BlockdevCreateOptionsSheepdog',
4709      'ssh':            'BlockdevCreateOptionsSsh',
4710      'vdi':            'BlockdevCreateOptionsVdi',
4711      'vhdx':           'BlockdevCreateOptionsVhdx',
4712      'vmdk':           'BlockdevCreateOptionsVmdk',
4713      'vpc':            'BlockdevCreateOptionsVpc'
4714  } }
4715
4716##
4717# @blockdev-create:
4718#
4719# Starts a job to create an image format on a given node. The job is
4720# automatically finalized, but a manual job-dismiss is required.
4721#
4722# @job-id:          Identifier for the newly created job.
4723#
4724# @options:         Options for the image creation.
4725#
4726# Since: 3.0
4727##
4728{ 'command': 'blockdev-create',
4729  'data': { 'job-id': 'str',
4730            'options': 'BlockdevCreateOptions' } }
4731
4732##
4733# @blockdev-open-tray:
4734#
4735# Opens a block device's tray. If there is a block driver state tree inserted as
4736# a medium, it will become inaccessible to the guest (but it will remain
4737# associated to the block device, so closing the tray will make it accessible
4738# again).
4739#
4740# If the tray was already open before, this will be a no-op.
4741#
4742# Once the tray opens, a DEVICE_TRAY_MOVED event is emitted. There are cases in
4743# which no such event will be generated, these include:
4744# - if the guest has locked the tray, @force is false and the guest does not
4745#   respond to the eject request
4746# - if the BlockBackend denoted by @device does not have a guest device attached
4747#   to it
4748# - if the guest device does not have an actual tray
4749#
4750# @device: Block device name (deprecated, use @id instead)
4751#
4752# @id:     The name or QOM path of the guest device (since: 2.8)
4753#
4754# @force:  if false (the default), an eject request will be sent to
4755#          the guest if it has locked the tray (and the tray will not be opened
4756#          immediately); if true, the tray will be opened regardless of whether
4757#          it is locked
4758#
4759# Since: 2.5
4760#
4761# Example:
4762#
4763# -> { "execute": "blockdev-open-tray",
4764#      "arguments": { "id": "ide0-1-0" } }
4765#
4766# <- { "timestamp": { "seconds": 1418751016,
4767#                     "microseconds": 716996 },
4768#      "event": "DEVICE_TRAY_MOVED",
4769#      "data": { "device": "ide1-cd0",
4770#                "id": "ide0-1-0",
4771#                "tray-open": true } }
4772#
4773# <- { "return": {} }
4774#
4775##
4776{ 'command': 'blockdev-open-tray',
4777  'data': { '*device': 'str',
4778            '*id': 'str',
4779            '*force': 'bool' } }
4780
4781##
4782# @blockdev-close-tray:
4783#
4784# Closes a block device's tray. If there is a block driver state tree associated
4785# with the block device (which is currently ejected), that tree will be loaded
4786# as the medium.
4787#
4788# If the tray was already closed before, this will be a no-op.
4789#
4790# @device:  Block device name (deprecated, use @id instead)
4791#
4792# @id:      The name or QOM path of the guest device (since: 2.8)
4793#
4794# Since: 2.5
4795#
4796# Example:
4797#
4798# -> { "execute": "blockdev-close-tray",
4799#      "arguments": { "id": "ide0-1-0" } }
4800#
4801# <- { "timestamp": { "seconds": 1418751345,
4802#                     "microseconds": 272147 },
4803#      "event": "DEVICE_TRAY_MOVED",
4804#      "data": { "device": "ide1-cd0",
4805#                "id": "ide0-1-0",
4806#                "tray-open": false } }
4807#
4808# <- { "return": {} }
4809#
4810##
4811{ 'command': 'blockdev-close-tray',
4812  'data': { '*device': 'str',
4813            '*id': 'str' } }
4814
4815##
4816# @blockdev-remove-medium:
4817#
4818# Removes a medium (a block driver state tree) from a block device. That block
4819# device's tray must currently be open (unless there is no attached guest
4820# device).
4821#
4822# If the tray is open and there is no medium inserted, this will be a no-op.
4823#
4824# @id:     The name or QOM path of the guest device
4825#
4826# Since: 2.12
4827#
4828# Example:
4829#
4830# -> { "execute": "blockdev-remove-medium",
4831#      "arguments": { "id": "ide0-1-0" } }
4832#
4833# <- { "error": { "class": "GenericError",
4834#                 "desc": "Tray of device 'ide0-1-0' is not open" } }
4835#
4836# -> { "execute": "blockdev-open-tray",
4837#      "arguments": { "id": "ide0-1-0" } }
4838#
4839# <- { "timestamp": { "seconds": 1418751627,
4840#                     "microseconds": 549958 },
4841#      "event": "DEVICE_TRAY_MOVED",
4842#      "data": { "device": "ide1-cd0",
4843#                "id": "ide0-1-0",
4844#                "tray-open": true } }
4845#
4846# <- { "return": {} }
4847#
4848# -> { "execute": "blockdev-remove-medium",
4849#      "arguments": { "id": "ide0-1-0" } }
4850#
4851# <- { "return": {} }
4852#
4853##
4854{ 'command': 'blockdev-remove-medium',
4855  'data': { 'id': 'str' } }
4856
4857##
4858# @blockdev-insert-medium:
4859#
4860# Inserts a medium (a block driver state tree) into a block device. That block
4861# device's tray must currently be open (unless there is no attached guest
4862# device) and there must be no medium inserted already.
4863#
4864# @id:        The name or QOM path of the guest device
4865#
4866# @node-name: name of a node in the block driver state graph
4867#
4868# Since: 2.12
4869#
4870# Example:
4871#
4872# -> { "execute": "blockdev-add",
4873#      "arguments": {
4874#          "node-name": "node0",
4875#          "driver": "raw",
4876#          "file": { "driver": "file",
4877#                    "filename": "fedora.iso" } } }
4878# <- { "return": {} }
4879#
4880# -> { "execute": "blockdev-insert-medium",
4881#      "arguments": { "id": "ide0-1-0",
4882#                     "node-name": "node0" } }
4883#
4884# <- { "return": {} }
4885#
4886##
4887{ 'command': 'blockdev-insert-medium',
4888  'data': { 'id': 'str',
4889            'node-name': 'str'} }
4890
4891
4892##
4893# @BlockdevChangeReadOnlyMode:
4894#
4895# Specifies the new read-only mode of a block device subject to the
4896# @blockdev-change-medium command.
4897#
4898# @retain:      Retains the current read-only mode
4899#
4900# @read-only:   Makes the device read-only
4901#
4902# @read-write:  Makes the device writable
4903#
4904# Since: 2.3
4905#
4906##
4907{ 'enum': 'BlockdevChangeReadOnlyMode',
4908  'data': ['retain', 'read-only', 'read-write'] }
4909
4910
4911##
4912# @blockdev-change-medium:
4913#
4914# Changes the medium inserted into a block device by ejecting the current medium
4915# and loading a new image file which is inserted as the new medium (this command
4916# combines blockdev-open-tray, blockdev-remove-medium, blockdev-insert-medium
4917# and blockdev-close-tray).
4918#
4919# @device:          Block device name (deprecated, use @id instead)
4920#
4921# @id:              The name or QOM path of the guest device
4922#                   (since: 2.8)
4923#
4924# @filename:        filename of the new image to be loaded
4925#
4926# @format:          format to open the new image with (defaults to
4927#                   the probed format)
4928#
4929# @read-only-mode:  change the read-only mode of the device; defaults
4930#                   to 'retain'
4931#
4932# Since: 2.5
4933#
4934# Examples:
4935#
4936# 1. Change a removable medium
4937#
4938# -> { "execute": "blockdev-change-medium",
4939#      "arguments": { "id": "ide0-1-0",
4940#                     "filename": "/srv/images/Fedora-12-x86_64-DVD.iso",
4941#                     "format": "raw" } }
4942# <- { "return": {} }
4943#
4944# 2. Load a read-only medium into a writable drive
4945#
4946# -> { "execute": "blockdev-change-medium",
4947#      "arguments": { "id": "floppyA",
4948#                     "filename": "/srv/images/ro.img",
4949#                     "format": "raw",
4950#                     "read-only-mode": "retain" } }
4951#
4952# <- { "error":
4953#      { "class": "GenericError",
4954#        "desc": "Could not open '/srv/images/ro.img': Permission denied" } }
4955#
4956# -> { "execute": "blockdev-change-medium",
4957#      "arguments": { "id": "floppyA",
4958#                     "filename": "/srv/images/ro.img",
4959#                     "format": "raw",
4960#                     "read-only-mode": "read-only" } }
4961#
4962# <- { "return": {} }
4963#
4964##
4965{ 'command': 'blockdev-change-medium',
4966  'data': { '*device': 'str',
4967            '*id': 'str',
4968            'filename': 'str',
4969            '*format': 'str',
4970            '*read-only-mode': 'BlockdevChangeReadOnlyMode' } }
4971
4972
4973##
4974# @BlockErrorAction:
4975#
4976# An enumeration of action that has been taken when a DISK I/O occurs
4977#
4978# @ignore: error has been ignored
4979#
4980# @report: error has been reported to the device
4981#
4982# @stop: error caused VM to be stopped
4983#
4984# Since: 2.1
4985##
4986{ 'enum': 'BlockErrorAction',
4987  'data': [ 'ignore', 'report', 'stop' ] }
4988
4989
4990##
4991# @BLOCK_IMAGE_CORRUPTED:
4992#
4993# Emitted when a disk image is being marked corrupt. The image can be
4994# identified by its device or node name. The 'device' field is always
4995# present for compatibility reasons, but it can be empty ("") if the
4996# image does not have a device name associated.
4997#
4998# @device: device name. This is always present for compatibility
4999#          reasons, but it can be empty ("") if the image does not
5000#          have a device name associated.
5001#
5002# @node-name: node name (Since: 2.4)
5003#
5004# @msg: informative message for human consumption, such as the kind of
5005#       corruption being detected. It should not be parsed by machine as it is
5006#       not guaranteed to be stable
5007#
5008# @offset: if the corruption resulted from an image access, this is
5009#          the host's access offset into the image
5010#
5011# @size: if the corruption resulted from an image access, this is
5012#        the access size
5013#
5014# @fatal: if set, the image is marked corrupt and therefore unusable after this
5015#        event and must be repaired (Since 2.2; before, every
5016#        BLOCK_IMAGE_CORRUPTED event was fatal)
5017#
5018# Note: If action is "stop", a STOP event will eventually follow the
5019#       BLOCK_IO_ERROR event.
5020#
5021# Example:
5022#
5023# <- { "event": "BLOCK_IMAGE_CORRUPTED",
5024#      "data": { "device": "ide0-hd0", "node-name": "node0",
5025#                "msg": "Prevented active L1 table overwrite", "offset": 196608,
5026#                "size": 65536 },
5027#      "timestamp": { "seconds": 1378126126, "microseconds": 966463 } }
5028#
5029# Since: 1.7
5030##
5031{ 'event': 'BLOCK_IMAGE_CORRUPTED',
5032  'data': { 'device'     : 'str',
5033            '*node-name' : 'str',
5034            'msg'        : 'str',
5035            '*offset'    : 'int',
5036            '*size'      : 'int',
5037            'fatal'      : 'bool' } }
5038
5039##
5040# @BLOCK_IO_ERROR:
5041#
5042# Emitted when a disk I/O error occurs
5043#
5044# @device: device name. This is always present for compatibility
5045#          reasons, but it can be empty ("") if the image does not
5046#          have a device name associated.
5047#
5048# @node-name: node name. Note that errors may be reported for the root node
5049#             that is directly attached to a guest device rather than for the
5050#             node where the error occurred. The node name is not present if
5051#             the drive is empty. (Since: 2.8)
5052#
5053# @operation: I/O operation
5054#
5055# @action: action that has been taken
5056#
5057# @nospace: true if I/O error was caused due to a no-space
5058#           condition. This key is only present if query-block's
5059#           io-status is present, please see query-block documentation
5060#           for more information (since: 2.2)
5061#
5062# @reason: human readable string describing the error cause.
5063#          (This field is a debugging aid for humans, it should not
5064#           be parsed by applications) (since: 2.2)
5065#
5066# Note: If action is "stop", a STOP event will eventually follow the
5067# BLOCK_IO_ERROR event
5068#
5069# Since: 0.13.0
5070#
5071# Example:
5072#
5073# <- { "event": "BLOCK_IO_ERROR",
5074#      "data": { "device": "ide0-hd1",
5075#                "node-name": "#block212",
5076#                "operation": "write",
5077#                "action": "stop" },
5078#      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
5079#
5080##
5081{ 'event': 'BLOCK_IO_ERROR',
5082  'data': { 'device': 'str', '*node-name': 'str',
5083            'operation': 'IoOperationType',
5084            'action': 'BlockErrorAction', '*nospace': 'bool',
5085            'reason': 'str' } }
5086
5087##
5088# @BLOCK_JOB_COMPLETED:
5089#
5090# Emitted when a block job has completed
5091#
5092# @type: job type
5093#
5094# @device: The job identifier. Originally the device name but other
5095#          values are allowed since QEMU 2.7
5096#
5097# @len: maximum progress value
5098#
5099# @offset: current progress value. On success this is equal to len.
5100#          On failure this is less than len
5101#
5102# @speed: rate limit, bytes per second
5103#
5104# @error: error message. Only present on failure. This field
5105#         contains a human-readable error message. There are no semantics
5106#         other than that streaming has failed and clients should not try to
5107#         interpret the error string
5108#
5109# Since: 1.1
5110#
5111# Example:
5112#
5113# <- { "event": "BLOCK_JOB_COMPLETED",
5114#      "data": { "type": "stream", "device": "virtio-disk0",
5115#                "len": 10737418240, "offset": 10737418240,
5116#                "speed": 0 },
5117#      "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
5118#
5119##
5120{ 'event': 'BLOCK_JOB_COMPLETED',
5121  'data': { 'type'  : 'JobType',
5122            'device': 'str',
5123            'len'   : 'int',
5124            'offset': 'int',
5125            'speed' : 'int',
5126            '*error': 'str' } }
5127
5128##
5129# @BLOCK_JOB_CANCELLED:
5130#
5131# Emitted when a block job has been cancelled
5132#
5133# @type: job type
5134#
5135# @device: The job identifier. Originally the device name but other
5136#          values are allowed since QEMU 2.7
5137#
5138# @len: maximum progress value
5139#
5140# @offset: current progress value. On success this is equal to len.
5141#          On failure this is less than len
5142#
5143# @speed: rate limit, bytes per second
5144#
5145# Since: 1.1
5146#
5147# Example:
5148#
5149# <- { "event": "BLOCK_JOB_CANCELLED",
5150#      "data": { "type": "stream", "device": "virtio-disk0",
5151#                "len": 10737418240, "offset": 134217728,
5152#                "speed": 0 },
5153#      "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
5154#
5155##
5156{ 'event': 'BLOCK_JOB_CANCELLED',
5157  'data': { 'type'  : 'JobType',
5158            'device': 'str',
5159            'len'   : 'int',
5160            'offset': 'int',
5161            'speed' : 'int' } }
5162
5163##
5164# @BLOCK_JOB_ERROR:
5165#
5166# Emitted when a block job encounters an error
5167#
5168# @device: The job identifier. Originally the device name but other
5169#          values are allowed since QEMU 2.7
5170#
5171# @operation: I/O operation
5172#
5173# @action: action that has been taken
5174#
5175# Since: 1.3
5176#
5177# Example:
5178#
5179# <- { "event": "BLOCK_JOB_ERROR",
5180#      "data": { "device": "ide0-hd1",
5181#                "operation": "write",
5182#                "action": "stop" },
5183#      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
5184#
5185##
5186{ 'event': 'BLOCK_JOB_ERROR',
5187  'data': { 'device'   : 'str',
5188            'operation': 'IoOperationType',
5189            'action'   : 'BlockErrorAction' } }
5190
5191##
5192# @BLOCK_JOB_READY:
5193#
5194# Emitted when a block job is ready to complete
5195#
5196# @type: job type
5197#
5198# @device: The job identifier. Originally the device name but other
5199#          values are allowed since QEMU 2.7
5200#
5201# @len: maximum progress value
5202#
5203# @offset: current progress value. On success this is equal to len.
5204#          On failure this is less than len
5205#
5206# @speed: rate limit, bytes per second
5207#
5208# Note: The "ready to complete" status is always reset by a @BLOCK_JOB_ERROR
5209# event
5210#
5211# Since: 1.3
5212#
5213# Example:
5214#
5215# <- { "event": "BLOCK_JOB_READY",
5216#      "data": { "device": "drive0", "type": "mirror", "speed": 0,
5217#                "len": 2097152, "offset": 2097152 }
5218#      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
5219#
5220##
5221{ 'event': 'BLOCK_JOB_READY',
5222  'data': { 'type'  : 'JobType',
5223            'device': 'str',
5224            'len'   : 'int',
5225            'offset': 'int',
5226            'speed' : 'int' } }
5227
5228##
5229# @BLOCK_JOB_PENDING:
5230#
5231# Emitted when a block job is awaiting explicit authorization to finalize graph
5232# changes via @block-job-finalize. If this job is part of a transaction, it will
5233# not emit this event until the transaction has converged first.
5234#
5235# @type: job type
5236#
5237# @id: The job identifier.
5238#
5239# Since: 2.12
5240#
5241# Example:
5242#
5243# <- { "event": "BLOCK_JOB_WAITING",
5244#      "data": { "device": "drive0", "type": "mirror" },
5245#      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
5246#
5247##
5248{ 'event': 'BLOCK_JOB_PENDING',
5249  'data': { 'type'  : 'JobType',
5250            'id'    : 'str' } }
5251
5252##
5253# @PreallocMode:
5254#
5255# Preallocation mode of QEMU image file
5256#
5257# @off: no preallocation
5258# @metadata: preallocate only for metadata
5259# @falloc: like @full preallocation but allocate disk space by
5260#          posix_fallocate() rather than writing data.
5261# @full: preallocate all data by writing it to the device to ensure
5262#        disk space is really available. This data may or may not be
5263#        zero, depending on the image format and storage.
5264#        @full preallocation also sets up metadata correctly.
5265#
5266# Since: 2.2
5267##
5268{ 'enum': 'PreallocMode',
5269  'data': [ 'off', 'metadata', 'falloc', 'full' ] }
5270
5271##
5272# @BLOCK_WRITE_THRESHOLD:
5273#
5274# Emitted when writes on block device reaches or exceeds the
5275# configured write threshold. For thin-provisioned devices, this
5276# means the device should be extended to avoid pausing for
5277# disk exhaustion.
5278# The event is one shot. Once triggered, it needs to be
5279# re-registered with another block-set-write-threshold command.
5280#
5281# @node-name: graph node name on which the threshold was exceeded.
5282#
5283# @amount-exceeded: amount of data which exceeded the threshold, in bytes.
5284#
5285# @write-threshold: last configured threshold, in bytes.
5286#
5287# Since: 2.3
5288##
5289{ 'event': 'BLOCK_WRITE_THRESHOLD',
5290  'data': { 'node-name': 'str',
5291            'amount-exceeded': 'uint64',
5292            'write-threshold': 'uint64' } }
5293
5294##
5295# @block-set-write-threshold:
5296#
5297# Change the write threshold for a block drive. An event will be
5298# delivered if a write to this block drive crosses the configured
5299# threshold.  The threshold is an offset, thus must be
5300# non-negative. Default is no write threshold. Setting the threshold
5301# to zero disables it.
5302#
5303# This is useful to transparently resize thin-provisioned drives without
5304# the guest OS noticing.
5305#
5306# @node-name: graph node name on which the threshold must be set.
5307#
5308# @write-threshold: configured threshold for the block device, bytes.
5309#                   Use 0 to disable the threshold.
5310#
5311# Since: 2.3
5312#
5313# Example:
5314#
5315# -> { "execute": "block-set-write-threshold",
5316#      "arguments": { "node-name": "mydev",
5317#                     "write-threshold": 17179869184 } }
5318# <- { "return": {} }
5319#
5320##
5321{ 'command': 'block-set-write-threshold',
5322  'data': { 'node-name': 'str', 'write-threshold': 'uint64' } }
5323
5324##
5325# @x-blockdev-change:
5326#
5327# Dynamically reconfigure the block driver state graph. It can be used
5328# to add, remove, insert or replace a graph node. Currently only the
5329# Quorum driver implements this feature to add or remove its child. This
5330# is useful to fix a broken quorum child.
5331#
5332# If @node is specified, it will be inserted under @parent. @child
5333# may not be specified in this case. If both @parent and @child are
5334# specified but @node is not, @child will be detached from @parent.
5335#
5336# @parent: the id or name of the parent node.
5337#
5338# @child: the name of a child under the given parent node.
5339#
5340# @node: the name of the node that will be added.
5341#
5342# Note: this command is experimental, and its API is not stable. It
5343# does not support all kinds of operations, all kinds of children, nor
5344# all block drivers.
5345#
5346# FIXME Removing children from a quorum node means introducing gaps in the
5347# child indices. This cannot be represented in the 'children' list of
5348# BlockdevOptionsQuorum, as returned by .bdrv_refresh_filename().
5349#
5350# Warning: The data in a new quorum child MUST be consistent with that of
5351# the rest of the array.
5352#
5353# Since: 2.7
5354#
5355# Example:
5356#
5357# 1. Add a new node to a quorum
5358# -> { "execute": "blockdev-add",
5359#      "arguments": {
5360#          "driver": "raw",
5361#          "node-name": "new_node",
5362#          "file": { "driver": "file",
5363#                    "filename": "test.raw" } } }
5364# <- { "return": {} }
5365# -> { "execute": "x-blockdev-change",
5366#      "arguments": { "parent": "disk1",
5367#                     "node": "new_node" } }
5368# <- { "return": {} }
5369#
5370# 2. Delete a quorum's node
5371# -> { "execute": "x-blockdev-change",
5372#      "arguments": { "parent": "disk1",
5373#                     "child": "children.1" } }
5374# <- { "return": {} }
5375#
5376##
5377{ 'command': 'x-blockdev-change',
5378  'data' : { 'parent': 'str',
5379             '*child': 'str',
5380             '*node': 'str' } }
5381
5382##
5383# @x-blockdev-set-iothread:
5384#
5385# Move @node and its children into the @iothread.  If @iothread is null then
5386# move @node and its children into the main loop.
5387#
5388# The node must not be attached to a BlockBackend.
5389#
5390# @node-name: the name of the block driver node
5391#
5392# @iothread: the name of the IOThread object or null for the main loop
5393#
5394# @force: true if the node and its children should be moved when a BlockBackend
5395#         is already attached
5396#
5397# Note: this command is experimental and intended for test cases that need
5398# control over IOThreads only.
5399#
5400# Since: 2.12
5401#
5402# Example:
5403#
5404# 1. Move a node into an IOThread
5405# -> { "execute": "x-blockdev-set-iothread",
5406#      "arguments": { "node-name": "disk1",
5407#                     "iothread": "iothread0" } }
5408# <- { "return": {} }
5409#
5410# 2. Move a node into the main loop
5411# -> { "execute": "x-blockdev-set-iothread",
5412#      "arguments": { "node-name": "disk1",
5413#                     "iothread": null } }
5414# <- { "return": {} }
5415#
5416##
5417{ 'command': 'x-blockdev-set-iothread',
5418  'data' : { 'node-name': 'str',
5419             'iothread': 'StrOrNull',
5420             '*force': 'bool' } }
5421