xref: /openbmc/qemu/qapi/block-core.json (revision dc5bd18f)
1# -*- Mode: Python -*-
2
3##
4# == Block core (VM unrelated)
5##
6
7{ 'include': 'common.json' }
8{ 'include': 'crypto.json' }
9{ 'include': 'sockets.json' }
10
11##
12# @SnapshotInfo:
13#
14# @id: unique snapshot id
15#
16# @name: user chosen name
17#
18# @vm-state-size: size of the VM state
19#
20# @date-sec: UTC date of the snapshot in seconds
21#
22# @date-nsec: fractional part in nano seconds to be used with date-sec
23#
24# @vm-clock-sec: VM clock relative to boot in seconds
25#
26# @vm-clock-nsec: fractional part in nano seconds to be used with vm-clock-sec
27#
28# Since: 1.3
29#
30##
31{ 'struct': 'SnapshotInfo',
32  'data': { 'id': 'str', 'name': 'str', 'vm-state-size': 'int',
33            'date-sec': 'int', 'date-nsec': 'int',
34            'vm-clock-sec': 'int', 'vm-clock-nsec': 'int' } }
35
36##
37# @ImageInfoSpecificQCow2EncryptionBase:
38#
39# @format: The encryption format
40#
41# Since: 2.10
42##
43{ 'struct': 'ImageInfoSpecificQCow2EncryptionBase',
44  'data': { 'format': 'BlockdevQcow2EncryptionFormat'}}
45
46##
47# @ImageInfoSpecificQCow2Encryption:
48#
49# Since: 2.10
50##
51{ 'union': 'ImageInfoSpecificQCow2Encryption',
52  'base': 'ImageInfoSpecificQCow2EncryptionBase',
53  'discriminator': 'format',
54  'data': { 'aes': 'QCryptoBlockInfoQCow',
55            'luks': 'QCryptoBlockInfoLUKS' } }
56
57##
58# @ImageInfoSpecificQCow2:
59#
60# @compat: compatibility level
61#
62# @lazy-refcounts: on or off; only valid for compat >= 1.1
63#
64# @corrupt: true if the image has been marked corrupt; only valid for
65#           compat >= 1.1 (since 2.2)
66#
67# @refcount-bits: width of a refcount entry in bits (since 2.3)
68#
69# @encrypt: details about encryption parameters; only set if image
70#           is encrypted (since 2.10)
71#
72# Since: 1.7
73##
74{ 'struct': 'ImageInfoSpecificQCow2',
75  'data': {
76      'compat': 'str',
77      '*lazy-refcounts': 'bool',
78      '*corrupt': 'bool',
79      'refcount-bits': 'int',
80      '*encrypt': 'ImageInfoSpecificQCow2Encryption'
81  } }
82
83##
84# @ImageInfoSpecificVmdk:
85#
86# @create-type: The create type of VMDK image
87#
88# @cid: Content id of image
89#
90# @parent-cid: Parent VMDK image's cid
91#
92# @extents: List of extent files
93#
94# Since: 1.7
95##
96{ 'struct': 'ImageInfoSpecificVmdk',
97  'data': {
98      'create-type': 'str',
99      'cid': 'int',
100      'parent-cid': 'int',
101      'extents': ['ImageInfo']
102  } }
103
104##
105# @ImageInfoSpecific:
106#
107# A discriminated record of image format specific information structures.
108#
109# Since: 1.7
110##
111{ 'union': 'ImageInfoSpecific',
112  'data': {
113      'qcow2': 'ImageInfoSpecificQCow2',
114      'vmdk': 'ImageInfoSpecificVmdk',
115      # If we need to add block driver specific parameters for
116      # LUKS in future, then we'll subclass QCryptoBlockInfoLUKS
117      # to define a ImageInfoSpecificLUKS
118      'luks': 'QCryptoBlockInfoLUKS'
119  } }
120
121##
122# @ImageInfo:
123#
124# Information about a QEMU image file
125#
126# @filename: name of the image file
127#
128# @format: format of the image file
129#
130# @virtual-size: maximum capacity in bytes of the image
131#
132# @actual-size: actual size on disk in bytes of the image
133#
134# @dirty-flag: true if image is not cleanly closed
135#
136# @cluster-size: size of a cluster in bytes
137#
138# @encrypted: true if the image is encrypted
139#
140# @compressed: true if the image is compressed (Since 1.7)
141#
142# @backing-filename: name of the backing file
143#
144# @full-backing-filename: full path of the backing file
145#
146# @backing-filename-format: the format of the backing file
147#
148# @snapshots: list of VM snapshots
149#
150# @backing-image: info of the backing image (since 1.6)
151#
152# @format-specific: structure supplying additional format-specific
153# information (since 1.7)
154#
155# Since: 1.3
156#
157##
158{ 'struct': 'ImageInfo',
159  'data': {'filename': 'str', 'format': 'str', '*dirty-flag': 'bool',
160           '*actual-size': 'int', 'virtual-size': 'int',
161           '*cluster-size': 'int', '*encrypted': 'bool', '*compressed': 'bool',
162           '*backing-filename': 'str', '*full-backing-filename': 'str',
163           '*backing-filename-format': 'str', '*snapshots': ['SnapshotInfo'],
164           '*backing-image': 'ImageInfo',
165           '*format-specific': 'ImageInfoSpecific' } }
166
167##
168# @ImageCheck:
169#
170# Information about a QEMU image file check
171#
172# @filename: name of the image file checked
173#
174# @format: format of the image file checked
175#
176# @check-errors: number of unexpected errors occurred during check
177#
178# @image-end-offset: offset (in bytes) where the image ends, this
179#                    field is present if the driver for the image format
180#                    supports it
181#
182# @corruptions: number of corruptions found during the check if any
183#
184# @leaks: number of leaks found during the check if any
185#
186# @corruptions-fixed: number of corruptions fixed during the check
187#                     if any
188#
189# @leaks-fixed: number of leaks fixed during the check if any
190#
191# @total-clusters: total number of clusters, this field is present
192#                  if the driver for the image format supports it
193#
194# @allocated-clusters: total number of allocated clusters, this
195#                      field is present if the driver for the image format
196#                      supports it
197#
198# @fragmented-clusters: total number of fragmented clusters, this
199#                       field is present if the driver for the image format
200#                       supports it
201#
202# @compressed-clusters: total number of compressed clusters, this
203#                       field is present if the driver for the image format
204#                       supports it
205#
206# Since: 1.4
207#
208##
209{ 'struct': 'ImageCheck',
210  'data': {'filename': 'str', 'format': 'str', 'check-errors': 'int',
211           '*image-end-offset': 'int', '*corruptions': 'int', '*leaks': 'int',
212           '*corruptions-fixed': 'int', '*leaks-fixed': 'int',
213           '*total-clusters': 'int', '*allocated-clusters': 'int',
214           '*fragmented-clusters': 'int', '*compressed-clusters': 'int' } }
215
216##
217# @MapEntry:
218#
219# Mapping information from a virtual block range to a host file range
220#
221# @start: the start byte of the mapped virtual range
222#
223# @length: the number of bytes of the mapped virtual range
224#
225# @data: whether the mapped range has data
226#
227# @zero: whether the virtual blocks are zeroed
228#
229# @depth: the depth of the mapping
230#
231# @offset: the offset in file that the virtual sectors are mapped to
232#
233# @filename: filename that is referred to by @offset
234#
235# Since: 2.6
236#
237##
238{ 'struct': 'MapEntry',
239  'data': {'start': 'int', 'length': 'int', 'data': 'bool',
240           'zero': 'bool', 'depth': 'int', '*offset': 'int',
241           '*filename': 'str' } }
242
243##
244# @BlockdevCacheInfo:
245#
246# Cache mode information for a block device
247#
248# @writeback:   true if writeback mode is enabled
249# @direct:      true if the host page cache is bypassed (O_DIRECT)
250# @no-flush:    true if flush requests are ignored for the device
251#
252# Since: 2.3
253##
254{ 'struct': 'BlockdevCacheInfo',
255  'data': { 'writeback': 'bool',
256            'direct': 'bool',
257            'no-flush': 'bool' } }
258
259##
260# @BlockDeviceInfo:
261#
262# Information about the backing device for a block device.
263#
264# @file: the filename of the backing device
265#
266# @node-name: the name of the block driver node (Since 2.0)
267#
268# @ro: true if the backing device was open read-only
269#
270# @drv: the name of the block format used to open the backing device. As of
271#       0.14.0 this can be: 'blkdebug', 'bochs', 'cloop', 'cow', 'dmg',
272#       'file', 'file', 'ftp', 'ftps', 'host_cdrom', 'host_device',
273#       'http', 'https', 'luks', 'nbd', 'parallels', 'qcow',
274#       'qcow2', 'raw', 'vdi', 'vmdk', 'vpc', 'vvfat'
275#       2.2: 'archipelago' added, 'cow' dropped
276#       2.3: 'host_floppy' deprecated
277#       2.5: 'host_floppy' dropped
278#       2.6: 'luks' added
279#       2.8: 'replication' added, 'tftp' dropped
280#       2.9: 'archipelago' dropped
281#
282# @backing_file: the name of the backing file (for copy-on-write)
283#
284# @backing_file_depth: number of files in the backing file chain (since: 1.2)
285#
286# @encrypted: true if the backing device is encrypted
287#
288# @encryption_key_missing: Deprecated; always false
289#
290# @detect_zeroes: detect and optimize zero writes (Since 2.1)
291#
292# @bps: total throughput limit in bytes per second is specified
293#
294# @bps_rd: read throughput limit in bytes per second is specified
295#
296# @bps_wr: write throughput limit in bytes per second is specified
297#
298# @iops: total I/O operations per second is specified
299#
300# @iops_rd: read I/O operations per second is specified
301#
302# @iops_wr: write I/O operations per second is specified
303#
304# @image: the info of image used (since: 1.6)
305#
306# @bps_max: total throughput limit during bursts,
307#                     in bytes (Since 1.7)
308#
309# @bps_rd_max: read throughput limit during bursts,
310#                        in bytes (Since 1.7)
311#
312# @bps_wr_max: write throughput limit during bursts,
313#                        in bytes (Since 1.7)
314#
315# @iops_max: total I/O operations per second during bursts,
316#                      in bytes (Since 1.7)
317#
318# @iops_rd_max: read I/O operations per second during bursts,
319#                         in bytes (Since 1.7)
320#
321# @iops_wr_max: write I/O operations per second during bursts,
322#                         in bytes (Since 1.7)
323#
324# @bps_max_length: maximum length of the @bps_max burst
325#                            period, in seconds. (Since 2.6)
326#
327# @bps_rd_max_length: maximum length of the @bps_rd_max
328#                               burst period, in seconds. (Since 2.6)
329#
330# @bps_wr_max_length: maximum length of the @bps_wr_max
331#                               burst period, in seconds. (Since 2.6)
332#
333# @iops_max_length: maximum length of the @iops burst
334#                             period, in seconds. (Since 2.6)
335#
336# @iops_rd_max_length: maximum length of the @iops_rd_max
337#                                burst period, in seconds. (Since 2.6)
338#
339# @iops_wr_max_length: maximum length of the @iops_wr_max
340#                                burst period, in seconds. (Since 2.6)
341#
342# @iops_size: an I/O size in bytes (Since 1.7)
343#
344# @group: throttle group name (Since 2.4)
345#
346# @cache: the cache mode used for the block device (since: 2.3)
347#
348# @write_threshold: configured write threshold for the device.
349#                   0 if disabled. (Since 2.3)
350#
351# Since: 0.14.0
352#
353##
354{ 'struct': 'BlockDeviceInfo',
355  'data': { 'file': 'str', '*node-name': 'str', 'ro': 'bool', 'drv': 'str',
356            '*backing_file': 'str', 'backing_file_depth': 'int',
357            'encrypted': 'bool', 'encryption_key_missing': 'bool',
358            'detect_zeroes': 'BlockdevDetectZeroesOptions',
359            'bps': 'int', 'bps_rd': 'int', 'bps_wr': 'int',
360            'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
361            'image': 'ImageInfo',
362            '*bps_max': 'int', '*bps_rd_max': 'int',
363            '*bps_wr_max': 'int', '*iops_max': 'int',
364            '*iops_rd_max': 'int', '*iops_wr_max': 'int',
365            '*bps_max_length': 'int', '*bps_rd_max_length': 'int',
366            '*bps_wr_max_length': 'int', '*iops_max_length': 'int',
367            '*iops_rd_max_length': 'int', '*iops_wr_max_length': 'int',
368            '*iops_size': 'int', '*group': 'str', 'cache': 'BlockdevCacheInfo',
369            'write_threshold': 'int' } }
370
371##
372# @BlockDeviceIoStatus:
373#
374# An enumeration of block device I/O status.
375#
376# @ok: The last I/O operation has succeeded
377#
378# @failed: The last I/O operation has failed
379#
380# @nospace: The last I/O operation has failed due to a no-space condition
381#
382# Since: 1.0
383##
384{ 'enum': 'BlockDeviceIoStatus', 'data': [ 'ok', 'failed', 'nospace' ] }
385
386##
387# @BlockDeviceMapEntry:
388#
389# Entry in the metadata map of the device (returned by "qemu-img map")
390#
391# @start: Offset in the image of the first byte described by this entry
392#         (in bytes)
393#
394# @length: Length of the range described by this entry (in bytes)
395#
396# @depth: Number of layers (0 = top image, 1 = top image's backing file, etc.)
397#         before reaching one for which the range is allocated.  The value is
398#         in the range 0 to the depth of the image chain - 1.
399#
400# @zero: the sectors in this range read as zeros
401#
402# @data: reading the image will actually read data from a file (in particular,
403#        if @offset is present this means that the sectors are not simply
404#        preallocated, but contain actual data in raw format)
405#
406# @offset: if present, the image file stores the data for this range in
407#          raw format at the given offset.
408#
409# Since: 1.7
410##
411{ 'struct': 'BlockDeviceMapEntry',
412  'data': { 'start': 'int', 'length': 'int', 'depth': 'int', 'zero': 'bool',
413            'data': 'bool', '*offset': 'int' } }
414
415##
416# @DirtyBitmapStatus:
417#
418# An enumeration of possible states that a dirty bitmap can report to the user.
419#
420# @frozen: The bitmap is currently in-use by a backup operation or block job,
421#          and is immutable.
422#
423# @disabled: The bitmap is currently in-use by an internal operation and is
424#            read-only. It can still be deleted.
425#
426# @active: The bitmap is actively monitoring for new writes, and can be cleared,
427#          deleted, or used for backup operations.
428#
429# Since: 2.4
430##
431{ 'enum': 'DirtyBitmapStatus',
432  'data': ['active', 'disabled', 'frozen'] }
433
434##
435# @BlockDirtyInfo:
436#
437# Block dirty bitmap information.
438#
439# @name: the name of the dirty bitmap (Since 2.4)
440#
441# @count: number of dirty bytes according to the dirty bitmap
442#
443# @granularity: granularity of the dirty bitmap in bytes (since 1.4)
444#
445# @status: current status of the dirty bitmap (since 2.4)
446#
447# Since: 1.3
448##
449{ 'struct': 'BlockDirtyInfo',
450  'data': {'*name': 'str', 'count': 'int', 'granularity': 'uint32',
451           'status': 'DirtyBitmapStatus'} }
452
453##
454# @BlockInfo:
455#
456# Block device information.  This structure describes a virtual device and
457# the backing device associated with it.
458#
459# @device: The device name associated with the virtual device.
460#
461# @qdev: The qdev ID, or if no ID is assigned, the QOM path of the block
462#        device. (since 2.10)
463#
464# @type: This field is returned only for compatibility reasons, it should
465#        not be used (always returns 'unknown')
466#
467# @removable: True if the device supports removable media.
468#
469# @locked: True if the guest has locked this device from having its media
470#          removed
471#
472# @tray_open: True if the device's tray is open
473#             (only present if it has a tray)
474#
475# @dirty-bitmaps: dirty bitmaps information (only present if the
476#                 driver has one or more dirty bitmaps) (Since 2.0)
477#
478# @io-status: @BlockDeviceIoStatus. Only present if the device
479#             supports it and the VM is configured to stop on errors
480#             (supported device models: virtio-blk, IDE, SCSI except
481#             scsi-generic)
482#
483# @inserted: @BlockDeviceInfo describing the device if media is
484#            present
485#
486# Since:  0.14.0
487##
488{ 'struct': 'BlockInfo',
489  'data': {'device': 'str', '*qdev': 'str', 'type': 'str', 'removable': 'bool',
490           'locked': 'bool', '*inserted': 'BlockDeviceInfo',
491           '*tray_open': 'bool', '*io-status': 'BlockDeviceIoStatus',
492           '*dirty-bitmaps': ['BlockDirtyInfo'] } }
493
494##
495# @BlockMeasureInfo:
496#
497# Image file size calculation information.  This structure describes the size
498# requirements for creating a new image file.
499#
500# The size requirements depend on the new image file format.  File size always
501# equals virtual disk size for the 'raw' format, even for sparse POSIX files.
502# Compact formats such as 'qcow2' represent unallocated and zero regions
503# efficiently so file size may be smaller than virtual disk size.
504#
505# The values are upper bounds that are guaranteed to fit the new image file.
506# Subsequent modification, such as internal snapshot or bitmap creation, may
507# require additional space and is not covered here.
508#
509# @required: Size required for a new image file, in bytes.
510#
511# @fully-allocated: Image file size, in bytes, once data has been written
512#                   to all sectors.
513#
514# Since: 2.10
515##
516{ 'struct': 'BlockMeasureInfo',
517  'data': {'required': 'int', 'fully-allocated': 'int'} }
518
519##
520# @query-block:
521#
522# Get a list of BlockInfo for all virtual block devices.
523#
524# Returns: a list of @BlockInfo describing each virtual block device. Filter
525# nodes that were created implicitly are skipped over.
526#
527# Since: 0.14.0
528#
529# Example:
530#
531# -> { "execute": "query-block" }
532# <- {
533#       "return":[
534#          {
535#             "io-status": "ok",
536#             "device":"ide0-hd0",
537#             "locked":false,
538#             "removable":false,
539#             "inserted":{
540#                "ro":false,
541#                "drv":"qcow2",
542#                "encrypted":false,
543#                "file":"disks/test.qcow2",
544#                "backing_file_depth":1,
545#                "bps":1000000,
546#                "bps_rd":0,
547#                "bps_wr":0,
548#                "iops":1000000,
549#                "iops_rd":0,
550#                "iops_wr":0,
551#                "bps_max": 8000000,
552#                "bps_rd_max": 0,
553#                "bps_wr_max": 0,
554#                "iops_max": 0,
555#                "iops_rd_max": 0,
556#                "iops_wr_max": 0,
557#                "iops_size": 0,
558#                "detect_zeroes": "on",
559#                "write_threshold": 0,
560#                "image":{
561#                   "filename":"disks/test.qcow2",
562#                   "format":"qcow2",
563#                   "virtual-size":2048000,
564#                   "backing_file":"base.qcow2",
565#                   "full-backing-filename":"disks/base.qcow2",
566#                   "backing-filename-format":"qcow2",
567#                   "snapshots":[
568#                      {
569#                         "id": "1",
570#                         "name": "snapshot1",
571#                         "vm-state-size": 0,
572#                         "date-sec": 10000200,
573#                         "date-nsec": 12,
574#                         "vm-clock-sec": 206,
575#                         "vm-clock-nsec": 30
576#                      }
577#                   ],
578#                   "backing-image":{
579#                       "filename":"disks/base.qcow2",
580#                       "format":"qcow2",
581#                       "virtual-size":2048000
582#                   }
583#                }
584#             },
585#             "qdev": "ide_disk",
586#             "type":"unknown"
587#          },
588#          {
589#             "io-status": "ok",
590#             "device":"ide1-cd0",
591#             "locked":false,
592#             "removable":true,
593#             "qdev": "/machine/unattached/device[23]",
594#             "tray_open": false,
595#             "type":"unknown"
596#          },
597#          {
598#             "device":"floppy0",
599#             "locked":false,
600#             "removable":true,
601#             "qdev": "/machine/unattached/device[20]",
602#             "type":"unknown"
603#          },
604#          {
605#             "device":"sd0",
606#             "locked":false,
607#             "removable":true,
608#             "type":"unknown"
609#          }
610#       ]
611#    }
612#
613##
614{ 'command': 'query-block', 'returns': ['BlockInfo'] }
615
616
617##
618# @BlockDeviceTimedStats:
619#
620# Statistics of a block device during a given interval of time.
621#
622# @interval_length: Interval used for calculating the statistics,
623#                   in seconds.
624#
625# @min_rd_latency_ns: Minimum latency of read operations in the
626#                     defined interval, in nanoseconds.
627#
628# @min_wr_latency_ns: Minimum latency of write operations in the
629#                     defined interval, in nanoseconds.
630#
631# @min_flush_latency_ns: Minimum latency of flush operations in the
632#                        defined interval, in nanoseconds.
633#
634# @max_rd_latency_ns: Maximum latency of read operations in the
635#                     defined interval, in nanoseconds.
636#
637# @max_wr_latency_ns: Maximum latency of write operations in the
638#                     defined interval, in nanoseconds.
639#
640# @max_flush_latency_ns: Maximum latency of flush operations in the
641#                        defined interval, in nanoseconds.
642#
643# @avg_rd_latency_ns: Average latency of read operations in the
644#                     defined interval, in nanoseconds.
645#
646# @avg_wr_latency_ns: Average latency of write operations in the
647#                     defined interval, in nanoseconds.
648#
649# @avg_flush_latency_ns: Average latency of flush operations in the
650#                        defined interval, in nanoseconds.
651#
652# @avg_rd_queue_depth: Average number of pending read operations
653#                      in the defined interval.
654#
655# @avg_wr_queue_depth: Average number of pending write operations
656#                      in the defined interval.
657#
658# Since: 2.5
659##
660{ 'struct': 'BlockDeviceTimedStats',
661  'data': { 'interval_length': 'int', 'min_rd_latency_ns': 'int',
662            'max_rd_latency_ns': 'int', 'avg_rd_latency_ns': 'int',
663            'min_wr_latency_ns': 'int', 'max_wr_latency_ns': 'int',
664            'avg_wr_latency_ns': 'int', 'min_flush_latency_ns': 'int',
665            'max_flush_latency_ns': 'int', 'avg_flush_latency_ns': 'int',
666            'avg_rd_queue_depth': 'number', 'avg_wr_queue_depth': 'number' } }
667
668##
669# @BlockDeviceStats:
670#
671# Statistics of a virtual block device or a block backing device.
672#
673# @rd_bytes:      The number of bytes read by the device.
674#
675# @wr_bytes:      The number of bytes written by the device.
676#
677# @rd_operations: The number of read operations performed by the device.
678#
679# @wr_operations: The number of write operations performed by the device.
680#
681# @flush_operations: The number of cache flush operations performed by the
682#                    device (since 0.15.0)
683#
684# @flush_total_time_ns: Total time spend on cache flushes in nano-seconds
685#                       (since 0.15.0).
686#
687# @wr_total_time_ns: Total time spend on writes in nano-seconds (since 0.15.0).
688#
689# @rd_total_time_ns: Total_time_spend on reads in nano-seconds (since 0.15.0).
690#
691# @wr_highest_offset: The offset after the greatest byte written to the
692#                     device.  The intended use of this information is for
693#                     growable sparse files (like qcow2) that are used on top
694#                     of a physical device.
695#
696# @rd_merged: Number of read requests that have been merged into another
697#             request (Since 2.3).
698#
699# @wr_merged: Number of write requests that have been merged into another
700#             request (Since 2.3).
701#
702# @idle_time_ns: Time since the last I/O operation, in
703#                nanoseconds. If the field is absent it means that
704#                there haven't been any operations yet (Since 2.5).
705#
706# @failed_rd_operations: The number of failed read operations
707#                        performed by the device (Since 2.5)
708#
709# @failed_wr_operations: The number of failed write operations
710#                        performed by the device (Since 2.5)
711#
712# @failed_flush_operations: The number of failed flush operations
713#                           performed by the device (Since 2.5)
714#
715# @invalid_rd_operations: The number of invalid read operations
716#                          performed by the device (Since 2.5)
717#
718# @invalid_wr_operations: The number of invalid write operations
719#                         performed by the device (Since 2.5)
720#
721# @invalid_flush_operations: The number of invalid flush operations
722#                            performed by the device (Since 2.5)
723#
724# @account_invalid: Whether invalid operations are included in the
725#                   last access statistics (Since 2.5)
726#
727# @account_failed: Whether failed operations are included in the
728#                  latency and last access statistics (Since 2.5)
729#
730# @timed_stats: Statistics specific to the set of previously defined
731#               intervals of time (Since 2.5)
732#
733# Since: 0.14.0
734##
735{ 'struct': 'BlockDeviceStats',
736  'data': {'rd_bytes': 'int', 'wr_bytes': 'int', 'rd_operations': 'int',
737           'wr_operations': 'int', 'flush_operations': 'int',
738           'flush_total_time_ns': 'int', 'wr_total_time_ns': 'int',
739           'rd_total_time_ns': 'int', 'wr_highest_offset': 'int',
740           'rd_merged': 'int', 'wr_merged': 'int', '*idle_time_ns': 'int',
741           'failed_rd_operations': 'int', 'failed_wr_operations': 'int',
742           'failed_flush_operations': 'int', 'invalid_rd_operations': 'int',
743           'invalid_wr_operations': 'int', 'invalid_flush_operations': 'int',
744           'account_invalid': 'bool', 'account_failed': 'bool',
745           'timed_stats': ['BlockDeviceTimedStats'] } }
746
747##
748# @BlockStats:
749#
750# Statistics of a virtual block device or a block backing device.
751#
752# @device: If the stats are for a virtual block device, the name
753#          corresponding to the virtual block device.
754#
755# @node-name: The node name of the device. (Since 2.3)
756#
757# @stats:  A @BlockDeviceStats for the device.
758#
759# @parent: This describes the file block device if it has one.
760#          Contains recursively the statistics of the underlying
761#          protocol (e.g. the host file for a qcow2 image). If there is
762#          no underlying protocol, this field is omitted
763#
764# @backing: This describes the backing block device if it has one.
765#           (Since 2.0)
766#
767# Since: 0.14.0
768##
769{ 'struct': 'BlockStats',
770  'data': {'*device': 'str', '*node-name': 'str',
771           'stats': 'BlockDeviceStats',
772           '*parent': 'BlockStats',
773           '*backing': 'BlockStats'} }
774
775##
776# @query-blockstats:
777#
778# Query the @BlockStats for all virtual block devices.
779#
780# @query-nodes: If true, the command will query all the block nodes
781#               that have a node name, in a list which will include "parent"
782#               information, but not "backing".
783#               If false or omitted, the behavior is as before - query all the
784#               device backends, recursively including their "parent" and
785#               "backing". Filter nodes that were created implicitly are
786#               skipped over in this mode. (Since 2.3)
787#
788# Returns: A list of @BlockStats for each virtual block devices.
789#
790# Since: 0.14.0
791#
792# Example:
793#
794# -> { "execute": "query-blockstats" }
795# <- {
796#       "return":[
797#          {
798#             "device":"ide0-hd0",
799#             "parent":{
800#                "stats":{
801#                   "wr_highest_offset":3686448128,
802#                   "wr_bytes":9786368,
803#                   "wr_operations":751,
804#                   "rd_bytes":122567168,
805#                   "rd_operations":36772
806#                   "wr_total_times_ns":313253456
807#                   "rd_total_times_ns":3465673657
808#                   "flush_total_times_ns":49653
809#                   "flush_operations":61,
810#                   "rd_merged":0,
811#                   "wr_merged":0,
812#                   "idle_time_ns":2953431879,
813#                   "account_invalid":true,
814#                   "account_failed":false
815#                }
816#             },
817#             "stats":{
818#                "wr_highest_offset":2821110784,
819#                "wr_bytes":9786368,
820#                "wr_operations":692,
821#                "rd_bytes":122739200,
822#                "rd_operations":36604
823#                "flush_operations":51,
824#                "wr_total_times_ns":313253456
825#                "rd_total_times_ns":3465673657
826#                "flush_total_times_ns":49653,
827#                "rd_merged":0,
828#                "wr_merged":0,
829#                "idle_time_ns":2953431879,
830#                "account_invalid":true,
831#                "account_failed":false
832#             }
833#          },
834#          {
835#             "device":"ide1-cd0",
836#             "stats":{
837#                "wr_highest_offset":0,
838#                "wr_bytes":0,
839#                "wr_operations":0,
840#                "rd_bytes":0,
841#                "rd_operations":0
842#                "flush_operations":0,
843#                "wr_total_times_ns":0
844#                "rd_total_times_ns":0
845#                "flush_total_times_ns":0,
846#                "rd_merged":0,
847#                "wr_merged":0,
848#                "account_invalid":false,
849#                "account_failed":false
850#             }
851#          },
852#          {
853#             "device":"floppy0",
854#             "stats":{
855#                "wr_highest_offset":0,
856#                "wr_bytes":0,
857#                "wr_operations":0,
858#                "rd_bytes":0,
859#                "rd_operations":0
860#                "flush_operations":0,
861#                "wr_total_times_ns":0
862#                "rd_total_times_ns":0
863#                "flush_total_times_ns":0,
864#                "rd_merged":0,
865#                "wr_merged":0,
866#                "account_invalid":false,
867#                "account_failed":false
868#             }
869#          },
870#          {
871#             "device":"sd0",
872#             "stats":{
873#                "wr_highest_offset":0,
874#                "wr_bytes":0,
875#                "wr_operations":0,
876#                "rd_bytes":0,
877#                "rd_operations":0
878#                "flush_operations":0,
879#                "wr_total_times_ns":0
880#                "rd_total_times_ns":0
881#                "flush_total_times_ns":0,
882#                "rd_merged":0,
883#                "wr_merged":0,
884#                "account_invalid":false,
885#                "account_failed":false
886#             }
887#          }
888#       ]
889#    }
890#
891##
892{ 'command': 'query-blockstats',
893  'data': { '*query-nodes': 'bool' },
894  'returns': ['BlockStats'] }
895
896##
897# @BlockdevOnError:
898#
899# An enumeration of possible behaviors for errors on I/O operations.
900# The exact meaning depends on whether the I/O was initiated by a guest
901# or by a block job
902#
903# @report: for guest operations, report the error to the guest;
904#          for jobs, cancel the job
905#
906# @ignore: ignore the error, only report a QMP event (BLOCK_IO_ERROR
907#          or BLOCK_JOB_ERROR)
908#
909# @enospc: same as @stop on ENOSPC, same as @report otherwise.
910#
911# @stop: for guest operations, stop the virtual machine;
912#        for jobs, pause the job
913#
914# @auto: inherit the error handling policy of the backend (since: 2.7)
915#
916# Since: 1.3
917##
918{ 'enum': 'BlockdevOnError',
919  'data': ['report', 'ignore', 'enospc', 'stop', 'auto'] }
920
921##
922# @MirrorSyncMode:
923#
924# An enumeration of possible behaviors for the initial synchronization
925# phase of storage mirroring.
926#
927# @top: copies data in the topmost image to the destination
928#
929# @full: copies data from all images to the destination
930#
931# @none: only copy data written from now on
932#
933# @incremental: only copy data described by the dirty bitmap. Since: 2.4
934#
935# Since: 1.3
936##
937{ 'enum': 'MirrorSyncMode',
938  'data': ['top', 'full', 'none', 'incremental'] }
939
940##
941# @BlockJobType:
942#
943# Type of a block job.
944#
945# @commit: block commit job type, see "block-commit"
946#
947# @stream: block stream job type, see "block-stream"
948#
949# @mirror: drive mirror job type, see "drive-mirror"
950#
951# @backup: drive backup job type, see "drive-backup"
952#
953# Since: 1.7
954##
955{ 'enum': 'BlockJobType',
956  'data': ['commit', 'stream', 'mirror', 'backup'] }
957
958##
959# @BlockJobInfo:
960#
961# Information about a long-running block device operation.
962#
963# @type: the job type ('stream' for image streaming)
964#
965# @device: The job identifier. Originally the device name but other
966#          values are allowed since QEMU 2.7
967#
968# @len: the maximum progress value
969#
970# @busy: false if the job is known to be in a quiescent state, with
971#        no pending I/O.  Since 1.3.
972#
973# @paused: whether the job is paused or, if @busy is true, will
974#          pause itself as soon as possible.  Since 1.3.
975#
976# @offset: the current progress value
977#
978# @speed: the rate limit, bytes per second
979#
980# @io-status: the status of the job (since 1.3)
981#
982# @ready: true if the job may be completed (since 2.2)
983#
984# Since: 1.1
985##
986{ 'struct': 'BlockJobInfo',
987  'data': {'type': 'str', 'device': 'str', 'len': 'int',
988           'offset': 'int', 'busy': 'bool', 'paused': 'bool', 'speed': 'int',
989           'io-status': 'BlockDeviceIoStatus', 'ready': 'bool'} }
990
991##
992# @query-block-jobs:
993#
994# Return information about long-running block device operations.
995#
996# Returns: a list of @BlockJobInfo for each active block job
997#
998# Since: 1.1
999##
1000{ 'command': 'query-block-jobs', 'returns': ['BlockJobInfo'] }
1001
1002##
1003# @block_passwd:
1004#
1005# This command sets the password of a block device that has not been open
1006# with a password and requires one.
1007#
1008# This command is now obsolete and will always return an error since 2.10
1009#
1010##
1011{ 'command': 'block_passwd', 'data': {'*device': 'str',
1012                                      '*node-name': 'str', 'password': 'str'} }
1013
1014##
1015# @block_resize:
1016#
1017# Resize a block image while a guest is running.
1018#
1019# Either @device or @node-name must be set but not both.
1020#
1021# @device: the name of the device to get the image resized
1022#
1023# @node-name: graph node name to get the image resized (Since 2.0)
1024#
1025# @size:  new image size in bytes
1026#
1027# Returns: nothing on success
1028#          If @device is not a valid block device, DeviceNotFound
1029#
1030# Since: 0.14.0
1031#
1032# Example:
1033#
1034# -> { "execute": "block_resize",
1035#      "arguments": { "device": "scratch", "size": 1073741824 } }
1036# <- { "return": {} }
1037#
1038##
1039{ 'command': 'block_resize', 'data': { '*device': 'str',
1040                                       '*node-name': 'str',
1041                                       'size': 'int' }}
1042
1043##
1044# @NewImageMode:
1045#
1046# An enumeration that tells QEMU how to set the backing file path in
1047# a new image file.
1048#
1049# @existing: QEMU should look for an existing image file.
1050#
1051# @absolute-paths: QEMU should create a new image with absolute paths
1052# for the backing file. If there is no backing file available, the new
1053# image will not be backed either.
1054#
1055# Since: 1.1
1056##
1057{ 'enum': 'NewImageMode',
1058  'data': [ 'existing', 'absolute-paths' ] }
1059
1060##
1061# @BlockdevSnapshotSync:
1062#
1063# Either @device or @node-name must be set but not both.
1064#
1065# @device: the name of the device to generate the snapshot from.
1066#
1067# @node-name: graph node name to generate the snapshot from (Since 2.0)
1068#
1069# @snapshot-file: the target of the new image. If the file exists, or
1070# if it is a device, the snapshot will be created in the existing
1071# file/device. Otherwise, a new file will be created.
1072#
1073# @snapshot-node-name: the graph node name of the new image (Since 2.0)
1074#
1075# @format: the format of the snapshot image, default is 'qcow2'.
1076#
1077# @mode: whether and how QEMU should create a new image, default is
1078#        'absolute-paths'.
1079##
1080{ 'struct': 'BlockdevSnapshotSync',
1081  'data': { '*device': 'str', '*node-name': 'str',
1082            'snapshot-file': 'str', '*snapshot-node-name': 'str',
1083            '*format': 'str', '*mode': 'NewImageMode' } }
1084
1085##
1086# @BlockdevSnapshot:
1087#
1088# @node: device or node name that will have a snapshot created.
1089#
1090# @overlay: reference to the existing block device that will become
1091#           the overlay of @node, as part of creating the snapshot.
1092#           It must not have a current backing file (this can be
1093#           achieved by passing "backing": "" to blockdev-add).
1094#
1095# Since: 2.5
1096##
1097{ 'struct': 'BlockdevSnapshot',
1098  'data': { 'node': 'str', 'overlay': 'str' } }
1099
1100##
1101# @DriveBackup:
1102#
1103# @job-id: identifier for the newly-created block job. If
1104#          omitted, the device name will be used. (Since 2.7)
1105#
1106# @device: the device name or node-name of a root node which should be copied.
1107#
1108# @target: the target of the new image. If the file exists, or if it
1109#          is a device, the existing file/device will be used as the new
1110#          destination.  If it does not exist, a new file will be created.
1111#
1112# @format: the format of the new destination, default is to
1113#          probe if @mode is 'existing', else the format of the source
1114#
1115# @sync: what parts of the disk image should be copied to the destination
1116#        (all the disk, only the sectors allocated in the topmost image, from a
1117#        dirty bitmap, or only new I/O).
1118#
1119# @mode: whether and how QEMU should create a new image, default is
1120#        'absolute-paths'.
1121#
1122# @speed: the maximum speed, in bytes per second
1123#
1124# @bitmap: the name of dirty bitmap if sync is "incremental".
1125#          Must be present if sync is "incremental", must NOT be present
1126#          otherwise. (Since 2.4)
1127#
1128# @compress: true to compress data, if the target format supports it.
1129#            (default: false) (since 2.8)
1130#
1131# @on-source-error: the action to take on an error on the source,
1132#                   default 'report'.  'stop' and 'enospc' can only be used
1133#                   if the block device supports io-status (see BlockInfo).
1134#
1135# @on-target-error: the action to take on an error on the target,
1136#                   default 'report' (no limitations, since this applies to
1137#                   a different block device than @device).
1138#
1139# Note: @on-source-error and @on-target-error only affect background
1140# I/O.  If an error occurs during a guest write request, the device's
1141# rerror/werror actions will be used.
1142#
1143# Since: 1.6
1144##
1145{ 'struct': 'DriveBackup',
1146  'data': { '*job-id': 'str', 'device': 'str', 'target': 'str',
1147            '*format': 'str', 'sync': 'MirrorSyncMode', '*mode': 'NewImageMode',
1148            '*speed': 'int', '*bitmap': 'str', '*compress': 'bool',
1149            '*on-source-error': 'BlockdevOnError',
1150            '*on-target-error': 'BlockdevOnError' } }
1151
1152##
1153# @BlockdevBackup:
1154#
1155# @job-id: identifier for the newly-created block job. If
1156#          omitted, the device name will be used. (Since 2.7)
1157#
1158# @device: the device name or node-name of a root node which should be copied.
1159#
1160# @target: the device name or node-name of the backup target node.
1161#
1162# @sync: what parts of the disk image should be copied to the destination
1163#        (all the disk, only the sectors allocated in the topmost image, or
1164#        only new I/O).
1165#
1166# @speed: the maximum speed, in bytes per second. The default is 0,
1167#         for unlimited.
1168#
1169# @compress: true to compress data, if the target format supports it.
1170#            (default: false) (since 2.8)
1171#
1172# @on-source-error: the action to take on an error on the source,
1173#                   default 'report'.  'stop' and 'enospc' can only be used
1174#                   if the block device supports io-status (see BlockInfo).
1175#
1176# @on-target-error: the action to take on an error on the target,
1177#                   default 'report' (no limitations, since this applies to
1178#                   a different block device than @device).
1179#
1180# Note: @on-source-error and @on-target-error only affect background
1181# I/O.  If an error occurs during a guest write request, the device's
1182# rerror/werror actions will be used.
1183#
1184# Since: 2.3
1185##
1186{ 'struct': 'BlockdevBackup',
1187  'data': { '*job-id': 'str', 'device': 'str', 'target': 'str',
1188            'sync': 'MirrorSyncMode',
1189            '*speed': 'int',
1190            '*compress': 'bool',
1191            '*on-source-error': 'BlockdevOnError',
1192            '*on-target-error': 'BlockdevOnError' } }
1193
1194##
1195# @blockdev-snapshot-sync:
1196#
1197# Generates a synchronous snapshot of a block device.
1198#
1199# For the arguments, see the documentation of BlockdevSnapshotSync.
1200#
1201# Returns: nothing on success
1202#          If @device is not a valid block device, DeviceNotFound
1203#
1204# Since: 0.14.0
1205#
1206# Example:
1207#
1208# -> { "execute": "blockdev-snapshot-sync",
1209#      "arguments": { "device": "ide-hd0",
1210#                     "snapshot-file":
1211#                     "/some/place/my-image",
1212#                     "format": "qcow2" } }
1213# <- { "return": {} }
1214#
1215##
1216{ 'command': 'blockdev-snapshot-sync',
1217  'data': 'BlockdevSnapshotSync' }
1218
1219
1220##
1221# @blockdev-snapshot:
1222#
1223# Generates a snapshot of a block device.
1224#
1225# Create a snapshot, by installing 'node' as the backing image of
1226# 'overlay'. Additionally, if 'node' is associated with a block
1227# device, the block device changes to using 'overlay' as its new active
1228# image.
1229#
1230# For the arguments, see the documentation of BlockdevSnapshot.
1231#
1232# Since: 2.5
1233#
1234# Example:
1235#
1236# -> { "execute": "blockdev-add",
1237#      "arguments": { "driver": "qcow2",
1238#                     "node-name": "node1534",
1239#                     "file": { "driver": "file",
1240#                               "filename": "hd1.qcow2" },
1241#                     "backing": "" } }
1242#
1243# <- { "return": {} }
1244#
1245# -> { "execute": "blockdev-snapshot",
1246#      "arguments": { "node": "ide-hd0",
1247#                     "overlay": "node1534" } }
1248# <- { "return": {} }
1249#
1250##
1251{ 'command': 'blockdev-snapshot',
1252  'data': 'BlockdevSnapshot' }
1253
1254##
1255# @change-backing-file:
1256#
1257# Change the backing file in the image file metadata.  This does not
1258# cause QEMU to reopen the image file to reparse the backing filename
1259# (it may, however, perform a reopen to change permissions from
1260# r/o -> r/w -> r/o, if needed). The new backing file string is written
1261# into the image file metadata, and the QEMU internal strings are
1262# updated.
1263#
1264# @image-node-name: The name of the block driver state node of the
1265#                   image to modify. The "device" argument is used
1266#                   to verify "image-node-name" is in the chain
1267#                   described by "device".
1268#
1269# @device:          The device name or node-name of the root node that owns
1270#                   image-node-name.
1271#
1272# @backing-file:    The string to write as the backing file.  This
1273#                   string is not validated, so care should be taken
1274#                   when specifying the string or the image chain may
1275#                   not be able to be reopened again.
1276#
1277# Returns: Nothing on success
1278#
1279#          If "device" does not exist or cannot be determined, DeviceNotFound
1280#
1281# Since: 2.1
1282##
1283{ 'command': 'change-backing-file',
1284  'data': { 'device': 'str', 'image-node-name': 'str',
1285            'backing-file': 'str' } }
1286
1287##
1288# @block-commit:
1289#
1290# Live commit of data from overlay image nodes into backing nodes - i.e.,
1291# writes data between 'top' and 'base' into 'base'.
1292#
1293# @job-id: identifier for the newly-created block job. If
1294#          omitted, the device name will be used. (Since 2.7)
1295#
1296# @device:  the device name or node-name of a root node
1297#
1298# @base:   The file name of the backing image to write data into.
1299#                    If not specified, this is the deepest backing image.
1300#
1301# @top:    The file name of the backing image within the image chain,
1302#                    which contains the topmost data to be committed down. If
1303#                    not specified, this is the active layer.
1304#
1305# @backing-file:  The backing file string to write into the overlay
1306#                           image of 'top'.  If 'top' is the active layer,
1307#                           specifying a backing file string is an error. This
1308#                           filename is not validated.
1309#
1310#                           If a pathname string is such that it cannot be
1311#                           resolved by QEMU, that means that subsequent QMP or
1312#                           HMP commands must use node-names for the image in
1313#                           question, as filename lookup methods will fail.
1314#
1315#                           If not specified, QEMU will automatically determine
1316#                           the backing file string to use, or error out if
1317#                           there is no obvious choice. Care should be taken
1318#                           when specifying the string, to specify a valid
1319#                           filename or protocol.
1320#                           (Since 2.1)
1321#
1322#                    If top == base, that is an error.
1323#                    If top == active, the job will not be completed by itself,
1324#                    user needs to complete the job with the block-job-complete
1325#                    command after getting the ready event. (Since 2.0)
1326#
1327#                    If the base image is smaller than top, then the base image
1328#                    will be resized to be the same size as top.  If top is
1329#                    smaller than the base image, the base will not be
1330#                    truncated.  If you want the base image size to match the
1331#                    size of the smaller top, you can safely truncate it
1332#                    yourself once the commit operation successfully completes.
1333#
1334# @speed:  the maximum speed, in bytes per second
1335#
1336# @filter-node-name: the node name that should be assigned to the
1337#                    filter driver that the commit job inserts into the graph
1338#                    above @top. If this option is not given, a node name is
1339#                    autogenerated. (Since: 2.9)
1340#
1341# Returns: Nothing on success
1342#          If commit or stream is already active on this device, DeviceInUse
1343#          If @device does not exist, DeviceNotFound
1344#          If image commit is not supported by this device, NotSupported
1345#          If @base or @top is invalid, a generic error is returned
1346#          If @speed is invalid, InvalidParameter
1347#
1348# Since: 1.3
1349#
1350# Example:
1351#
1352# -> { "execute": "block-commit",
1353#      "arguments": { "device": "virtio0",
1354#                     "top": "/tmp/snap1.qcow2" } }
1355# <- { "return": {} }
1356#
1357##
1358{ 'command': 'block-commit',
1359  'data': { '*job-id': 'str', 'device': 'str', '*base': 'str', '*top': 'str',
1360            '*backing-file': 'str', '*speed': 'int',
1361            '*filter-node-name': 'str' } }
1362
1363##
1364# @drive-backup:
1365#
1366# Start a point-in-time copy of a block device to a new destination.  The
1367# status of ongoing drive-backup operations can be checked with
1368# query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1369# The operation can be stopped before it has completed using the
1370# block-job-cancel command.
1371#
1372# Returns: nothing on success
1373#          If @device is not a valid block device, GenericError
1374#
1375# Since: 1.6
1376#
1377# Example:
1378#
1379# -> { "execute": "drive-backup",
1380#      "arguments": { "device": "drive0",
1381#                     "sync": "full",
1382#                     "target": "backup.img" } }
1383# <- { "return": {} }
1384#
1385##
1386{ 'command': 'drive-backup', 'boxed': true,
1387  'data': 'DriveBackup' }
1388
1389##
1390# @blockdev-backup:
1391#
1392# Start a point-in-time copy of a block device to a new destination.  The
1393# status of ongoing blockdev-backup operations can be checked with
1394# query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1395# The operation can be stopped before it has completed using the
1396# block-job-cancel command.
1397#
1398# Returns: nothing on success
1399#          If @device is not a valid block device, DeviceNotFound
1400#
1401# Since: 2.3
1402#
1403# Example:
1404# -> { "execute": "blockdev-backup",
1405#      "arguments": { "device": "src-id",
1406#                     "sync": "full",
1407#                     "target": "tgt-id" } }
1408# <- { "return": {} }
1409#
1410##
1411{ 'command': 'blockdev-backup', 'boxed': true,
1412  'data': 'BlockdevBackup' }
1413
1414
1415##
1416# @query-named-block-nodes:
1417#
1418# Get the named block driver list
1419#
1420# Returns: the list of BlockDeviceInfo
1421#
1422# Since: 2.0
1423#
1424# Example:
1425#
1426# -> { "execute": "query-named-block-nodes" }
1427# <- { "return": [ { "ro":false,
1428#                    "drv":"qcow2",
1429#                    "encrypted":false,
1430#                    "file":"disks/test.qcow2",
1431#                    "node-name": "my-node",
1432#                    "backing_file_depth":1,
1433#                    "bps":1000000,
1434#                    "bps_rd":0,
1435#                    "bps_wr":0,
1436#                    "iops":1000000,
1437#                    "iops_rd":0,
1438#                    "iops_wr":0,
1439#                    "bps_max": 8000000,
1440#                    "bps_rd_max": 0,
1441#                    "bps_wr_max": 0,
1442#                    "iops_max": 0,
1443#                    "iops_rd_max": 0,
1444#                    "iops_wr_max": 0,
1445#                    "iops_size": 0,
1446#                    "write_threshold": 0,
1447#                    "image":{
1448#                       "filename":"disks/test.qcow2",
1449#                       "format":"qcow2",
1450#                       "virtual-size":2048000,
1451#                       "backing_file":"base.qcow2",
1452#                       "full-backing-filename":"disks/base.qcow2",
1453#                       "backing-filename-format":"qcow2",
1454#                       "snapshots":[
1455#                          {
1456#                             "id": "1",
1457#                             "name": "snapshot1",
1458#                             "vm-state-size": 0,
1459#                             "date-sec": 10000200,
1460#                             "date-nsec": 12,
1461#                             "vm-clock-sec": 206,
1462#                             "vm-clock-nsec": 30
1463#                          }
1464#                       ],
1465#                       "backing-image":{
1466#                           "filename":"disks/base.qcow2",
1467#                           "format":"qcow2",
1468#                           "virtual-size":2048000
1469#                       }
1470#                    } } ] }
1471#
1472##
1473{ 'command': 'query-named-block-nodes', 'returns': [ 'BlockDeviceInfo' ] }
1474
1475##
1476# @drive-mirror:
1477#
1478# Start mirroring a block device's writes to a new destination. target
1479# specifies the target of the new image. If the file exists, or if it
1480# is a device, it will be used as the new destination for writes. If
1481# it does not exist, a new file will be created. format specifies the
1482# format of the mirror image, default is to probe if mode='existing',
1483# else the format of the source.
1484#
1485# Returns: nothing on success
1486#          If @device is not a valid block device, GenericError
1487#
1488# Since: 1.3
1489#
1490# Example:
1491#
1492# -> { "execute": "drive-mirror",
1493#      "arguments": { "device": "ide-hd0",
1494#                     "target": "/some/place/my-image",
1495#                     "sync": "full",
1496#                     "format": "qcow2" } }
1497# <- { "return": {} }
1498#
1499##
1500{ 'command': 'drive-mirror', 'boxed': true,
1501  'data': 'DriveMirror' }
1502
1503##
1504# @DriveMirror:
1505#
1506# A set of parameters describing drive mirror setup.
1507#
1508# @job-id: identifier for the newly-created block job. If
1509#          omitted, the device name will be used. (Since 2.7)
1510#
1511# @device:  the device name or node-name of a root node whose writes should be
1512#           mirrored.
1513#
1514# @target: the target of the new image. If the file exists, or if it
1515#          is a device, the existing file/device will be used as the new
1516#          destination.  If it does not exist, a new file will be created.
1517#
1518# @format: the format of the new destination, default is to
1519#          probe if @mode is 'existing', else the format of the source
1520#
1521# @node-name: the new block driver state node name in the graph
1522#             (Since 2.1)
1523#
1524# @replaces: with sync=full graph node name to be replaced by the new
1525#            image when a whole image copy is done. This can be used to repair
1526#            broken Quorum files. (Since 2.1)
1527#
1528# @mode: whether and how QEMU should create a new image, default is
1529#        'absolute-paths'.
1530#
1531# @speed:  the maximum speed, in bytes per second
1532#
1533# @sync: what parts of the disk image should be copied to the destination
1534#        (all the disk, only the sectors allocated in the topmost image, or
1535#        only new I/O).
1536#
1537# @granularity: granularity of the dirty bitmap, default is 64K
1538#               if the image format doesn't have clusters, 4K if the clusters
1539#               are smaller than that, else the cluster size.  Must be a
1540#               power of 2 between 512 and 64M (since 1.4).
1541#
1542# @buf-size: maximum amount of data in flight from source to
1543#            target (since 1.4).
1544#
1545# @on-source-error: the action to take on an error on the source,
1546#                   default 'report'.  'stop' and 'enospc' can only be used
1547#                   if the block device supports io-status (see BlockInfo).
1548#
1549# @on-target-error: the action to take on an error on the target,
1550#                   default 'report' (no limitations, since this applies to
1551#                   a different block device than @device).
1552# @unmap: Whether to try to unmap target sectors where source has
1553#         only zero. If true, and target unallocated sectors will read as zero,
1554#         target image sectors will be unmapped; otherwise, zeroes will be
1555#         written. Both will result in identical contents.
1556#         Default is true. (Since 2.4)
1557#
1558# Since: 1.3
1559##
1560{ 'struct': 'DriveMirror',
1561  'data': { '*job-id': 'str', 'device': 'str', 'target': 'str',
1562            '*format': 'str', '*node-name': 'str', '*replaces': 'str',
1563            'sync': 'MirrorSyncMode', '*mode': 'NewImageMode',
1564            '*speed': 'int', '*granularity': 'uint32',
1565            '*buf-size': 'int', '*on-source-error': 'BlockdevOnError',
1566            '*on-target-error': 'BlockdevOnError',
1567            '*unmap': 'bool' } }
1568
1569##
1570# @BlockDirtyBitmap:
1571#
1572# @node: name of device/node which the bitmap is tracking
1573#
1574# @name: name of the dirty bitmap
1575#
1576# Since: 2.4
1577##
1578{ 'struct': 'BlockDirtyBitmap',
1579  'data': { 'node': 'str', 'name': 'str' } }
1580
1581##
1582# @BlockDirtyBitmapAdd:
1583#
1584# @node: name of device/node which the bitmap is tracking
1585#
1586# @name: name of the dirty bitmap
1587#
1588# @granularity: the bitmap granularity, default is 64k for
1589#               block-dirty-bitmap-add
1590#
1591# @persistent: the bitmap is persistent, i.e. it will be saved to the
1592#              corresponding block device image file on its close. For now only
1593#              Qcow2 disks support persistent bitmaps. Default is false for
1594#              block-dirty-bitmap-add. (Since: 2.10)
1595#
1596# @autoload: ignored and deprecated since 2.12.
1597#            Currently, all dirty tracking bitmaps are loaded from Qcow2 on
1598#            open.
1599#
1600# Since: 2.4
1601##
1602{ 'struct': 'BlockDirtyBitmapAdd',
1603  'data': { 'node': 'str', 'name': 'str', '*granularity': 'uint32',
1604            '*persistent': 'bool', '*autoload': 'bool' } }
1605
1606##
1607# @block-dirty-bitmap-add:
1608#
1609# Create a dirty bitmap with a name on the node, and start tracking the writes.
1610#
1611# Returns: nothing on success
1612#          If @node is not a valid block device or node, DeviceNotFound
1613#          If @name is already taken, GenericError with an explanation
1614#
1615# Since: 2.4
1616#
1617# Example:
1618#
1619# -> { "execute": "block-dirty-bitmap-add",
1620#      "arguments": { "node": "drive0", "name": "bitmap0" } }
1621# <- { "return": {} }
1622#
1623##
1624{ 'command': 'block-dirty-bitmap-add',
1625  'data': 'BlockDirtyBitmapAdd' }
1626
1627##
1628# @block-dirty-bitmap-remove:
1629#
1630# Stop write tracking and remove the dirty bitmap that was created
1631# with block-dirty-bitmap-add. If the bitmap is persistent, remove it from its
1632# storage too.
1633#
1634# Returns: nothing on success
1635#          If @node is not a valid block device or node, DeviceNotFound
1636#          If @name is not found, GenericError with an explanation
1637#          if @name is frozen by an operation, GenericError
1638#
1639# Since: 2.4
1640#
1641# Example:
1642#
1643# -> { "execute": "block-dirty-bitmap-remove",
1644#      "arguments": { "node": "drive0", "name": "bitmap0" } }
1645# <- { "return": {} }
1646#
1647##
1648{ 'command': 'block-dirty-bitmap-remove',
1649  'data': 'BlockDirtyBitmap' }
1650
1651##
1652# @block-dirty-bitmap-clear:
1653#
1654# Clear (reset) a dirty bitmap on the device, so that an incremental
1655# backup from this point in time forward will only backup clusters
1656# modified after this clear operation.
1657#
1658# Returns: nothing on success
1659#          If @node is not a valid block device, DeviceNotFound
1660#          If @name is not found, GenericError with an explanation
1661#
1662# Since: 2.4
1663#
1664# Example:
1665#
1666# -> { "execute": "block-dirty-bitmap-clear",
1667#      "arguments": { "node": "drive0", "name": "bitmap0" } }
1668# <- { "return": {} }
1669#
1670##
1671{ 'command': 'block-dirty-bitmap-clear',
1672  'data': 'BlockDirtyBitmap' }
1673
1674##
1675# @BlockDirtyBitmapSha256:
1676#
1677# SHA256 hash of dirty bitmap data
1678#
1679# @sha256: ASCII representation of SHA256 bitmap hash
1680#
1681# Since: 2.10
1682##
1683  { 'struct': 'BlockDirtyBitmapSha256',
1684    'data': {'sha256': 'str'} }
1685
1686##
1687# @x-debug-block-dirty-bitmap-sha256:
1688#
1689# Get bitmap SHA256
1690#
1691# Returns: BlockDirtyBitmapSha256 on success
1692#          If @node is not a valid block device, DeviceNotFound
1693#          If @name is not found or if hashing has failed, GenericError with an
1694#          explanation
1695#
1696# Since: 2.10
1697##
1698  { 'command': 'x-debug-block-dirty-bitmap-sha256',
1699    'data': 'BlockDirtyBitmap', 'returns': 'BlockDirtyBitmapSha256' }
1700
1701##
1702# @blockdev-mirror:
1703#
1704# Start mirroring a block device's writes to a new destination.
1705#
1706# @job-id: identifier for the newly-created block job. If
1707#          omitted, the device name will be used. (Since 2.7)
1708#
1709# @device: The device name or node-name of a root node whose writes should be
1710#          mirrored.
1711#
1712# @target: the id or node-name of the block device to mirror to. This mustn't be
1713#          attached to guest.
1714#
1715# @replaces: with sync=full graph node name to be replaced by the new
1716#            image when a whole image copy is done. This can be used to repair
1717#            broken Quorum files.
1718#
1719# @speed:  the maximum speed, in bytes per second
1720#
1721# @sync: what parts of the disk image should be copied to the destination
1722#        (all the disk, only the sectors allocated in the topmost image, or
1723#        only new I/O).
1724#
1725# @granularity: granularity of the dirty bitmap, default is 64K
1726#               if the image format doesn't have clusters, 4K if the clusters
1727#               are smaller than that, else the cluster size.  Must be a
1728#               power of 2 between 512 and 64M
1729#
1730# @buf-size: maximum amount of data in flight from source to
1731#            target
1732#
1733# @on-source-error: the action to take on an error on the source,
1734#                   default 'report'.  'stop' and 'enospc' can only be used
1735#                   if the block device supports io-status (see BlockInfo).
1736#
1737# @on-target-error: the action to take on an error on the target,
1738#                   default 'report' (no limitations, since this applies to
1739#                   a different block device than @device).
1740#
1741# @filter-node-name: the node name that should be assigned to the
1742#                    filter driver that the mirror job inserts into the graph
1743#                    above @device. If this option is not given, a node name is
1744#                    autogenerated. (Since: 2.9)
1745#
1746# Returns: nothing on success.
1747#
1748# Since: 2.6
1749#
1750# Example:
1751#
1752# -> { "execute": "blockdev-mirror",
1753#      "arguments": { "device": "ide-hd0",
1754#                     "target": "target0",
1755#                     "sync": "full" } }
1756# <- { "return": {} }
1757#
1758##
1759{ 'command': 'blockdev-mirror',
1760  'data': { '*job-id': 'str', 'device': 'str', 'target': 'str',
1761            '*replaces': 'str',
1762            'sync': 'MirrorSyncMode',
1763            '*speed': 'int', '*granularity': 'uint32',
1764            '*buf-size': 'int', '*on-source-error': 'BlockdevOnError',
1765            '*on-target-error': 'BlockdevOnError',
1766            '*filter-node-name': 'str' } }
1767
1768##
1769# @block_set_io_throttle:
1770#
1771# Change I/O throttle limits for a block drive.
1772#
1773# Since QEMU 2.4, each device with I/O limits is member of a throttle
1774# group.
1775#
1776# If two or more devices are members of the same group, the limits
1777# will apply to the combined I/O of the whole group in a round-robin
1778# fashion. Therefore, setting new I/O limits to a device will affect
1779# the whole group.
1780#
1781# The name of the group can be specified using the 'group' parameter.
1782# If the parameter is unset, it is assumed to be the current group of
1783# that device. If it's not in any group yet, the name of the device
1784# will be used as the name for its group.
1785#
1786# The 'group' parameter can also be used to move a device to a
1787# different group. In this case the limits specified in the parameters
1788# will be applied to the new group only.
1789#
1790# I/O limits can be disabled by setting all of them to 0. In this case
1791# the device will be removed from its group and the rest of its
1792# members will not be affected. The 'group' parameter is ignored.
1793#
1794# Returns: Nothing on success
1795#          If @device is not a valid block device, DeviceNotFound
1796#
1797# Since: 1.1
1798#
1799# Example:
1800#
1801# -> { "execute": "block_set_io_throttle",
1802#      "arguments": { "id": "virtio-blk-pci0/virtio-backend",
1803#                     "bps": 0,
1804#                     "bps_rd": 0,
1805#                     "bps_wr": 0,
1806#                     "iops": 512,
1807#                     "iops_rd": 0,
1808#                     "iops_wr": 0,
1809#                     "bps_max": 0,
1810#                     "bps_rd_max": 0,
1811#                     "bps_wr_max": 0,
1812#                     "iops_max": 0,
1813#                     "iops_rd_max": 0,
1814#                     "iops_wr_max": 0,
1815#                     "bps_max_length": 0,
1816#                     "iops_size": 0 } }
1817# <- { "return": {} }
1818#
1819# -> { "execute": "block_set_io_throttle",
1820#      "arguments": { "id": "ide0-1-0",
1821#                     "bps": 1000000,
1822#                     "bps_rd": 0,
1823#                     "bps_wr": 0,
1824#                     "iops": 0,
1825#                     "iops_rd": 0,
1826#                     "iops_wr": 0,
1827#                     "bps_max": 8000000,
1828#                     "bps_rd_max": 0,
1829#                     "bps_wr_max": 0,
1830#                     "iops_max": 0,
1831#                     "iops_rd_max": 0,
1832#                     "iops_wr_max": 0,
1833#                     "bps_max_length": 60,
1834#                     "iops_size": 0 } }
1835# <- { "return": {} }
1836##
1837{ 'command': 'block_set_io_throttle', 'boxed': true,
1838  'data': 'BlockIOThrottle' }
1839
1840##
1841# @BlockIOThrottle:
1842#
1843# A set of parameters describing block throttling.
1844#
1845# @device: Block device name (deprecated, use @id instead)
1846#
1847# @id: The name or QOM path of the guest device (since: 2.8)
1848#
1849# @bps: total throughput limit in bytes per second
1850#
1851# @bps_rd: read throughput limit in bytes per second
1852#
1853# @bps_wr: write throughput limit in bytes per second
1854#
1855# @iops: total I/O operations per second
1856#
1857# @iops_rd: read I/O operations per second
1858#
1859# @iops_wr: write I/O operations per second
1860#
1861# @bps_max: total throughput limit during bursts,
1862#                     in bytes (Since 1.7)
1863#
1864# @bps_rd_max: read throughput limit during bursts,
1865#                        in bytes (Since 1.7)
1866#
1867# @bps_wr_max: write throughput limit during bursts,
1868#                        in bytes (Since 1.7)
1869#
1870# @iops_max: total I/O operations per second during bursts,
1871#                      in bytes (Since 1.7)
1872#
1873# @iops_rd_max: read I/O operations per second during bursts,
1874#                         in bytes (Since 1.7)
1875#
1876# @iops_wr_max: write I/O operations per second during bursts,
1877#                         in bytes (Since 1.7)
1878#
1879# @bps_max_length: maximum length of the @bps_max burst
1880#                            period, in seconds. It must only
1881#                            be set if @bps_max is set as well.
1882#                            Defaults to 1. (Since 2.6)
1883#
1884# @bps_rd_max_length: maximum length of the @bps_rd_max
1885#                               burst period, in seconds. It must only
1886#                               be set if @bps_rd_max is set as well.
1887#                               Defaults to 1. (Since 2.6)
1888#
1889# @bps_wr_max_length: maximum length of the @bps_wr_max
1890#                               burst period, in seconds. It must only
1891#                               be set if @bps_wr_max is set as well.
1892#                               Defaults to 1. (Since 2.6)
1893#
1894# @iops_max_length: maximum length of the @iops burst
1895#                             period, in seconds. It must only
1896#                             be set if @iops_max is set as well.
1897#                             Defaults to 1. (Since 2.6)
1898#
1899# @iops_rd_max_length: maximum length of the @iops_rd_max
1900#                                burst period, in seconds. It must only
1901#                                be set if @iops_rd_max is set as well.
1902#                                Defaults to 1. (Since 2.6)
1903#
1904# @iops_wr_max_length: maximum length of the @iops_wr_max
1905#                                burst period, in seconds. It must only
1906#                                be set if @iops_wr_max is set as well.
1907#                                Defaults to 1. (Since 2.6)
1908#
1909# @iops_size: an I/O size in bytes (Since 1.7)
1910#
1911# @group: throttle group name (Since 2.4)
1912#
1913# Since: 1.1
1914##
1915{ 'struct': 'BlockIOThrottle',
1916  'data': { '*device': 'str', '*id': 'str', 'bps': 'int', 'bps_rd': 'int',
1917            'bps_wr': 'int', 'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
1918            '*bps_max': 'int', '*bps_rd_max': 'int',
1919            '*bps_wr_max': 'int', '*iops_max': 'int',
1920            '*iops_rd_max': 'int', '*iops_wr_max': 'int',
1921            '*bps_max_length': 'int', '*bps_rd_max_length': 'int',
1922            '*bps_wr_max_length': 'int', '*iops_max_length': 'int',
1923            '*iops_rd_max_length': 'int', '*iops_wr_max_length': 'int',
1924            '*iops_size': 'int', '*group': 'str' } }
1925
1926##
1927# @ThrottleLimits:
1928#
1929# Limit parameters for throttling.
1930# Since some limit combinations are illegal, limits should always be set in one
1931# transaction. All fields are optional. When setting limits, if a field is
1932# missing the current value is not changed.
1933#
1934# @iops-total:             limit total I/O operations per second
1935# @iops-total-max:         I/O operations burst
1936# @iops-total-max-length:  length of the iops-total-max burst period, in seconds
1937#                          It must only be set if @iops-total-max is set as well.
1938# @iops-read:              limit read operations per second
1939# @iops-read-max:          I/O operations read burst
1940# @iops-read-max-length:   length of the iops-read-max burst period, in seconds
1941#                          It must only be set if @iops-read-max is set as well.
1942# @iops-write:             limit write operations per second
1943# @iops-write-max:         I/O operations write burst
1944# @iops-write-max-length:  length of the iops-write-max burst period, in seconds
1945#                          It must only be set if @iops-write-max is set as well.
1946# @bps-total:              limit total bytes per second
1947# @bps-total-max:          total bytes burst
1948# @bps-total-max-length:   length of the bps-total-max burst period, in seconds.
1949#                          It must only be set if @bps-total-max is set as well.
1950# @bps-read:               limit read bytes per second
1951# @bps-read-max:           total bytes read burst
1952# @bps-read-max-length:    length of the bps-read-max burst period, in seconds
1953#                          It must only be set if @bps-read-max is set as well.
1954# @bps-write:              limit write bytes per second
1955# @bps-write-max:          total bytes write burst
1956# @bps-write-max-length:   length of the bps-write-max burst period, in seconds
1957#                          It must only be set if @bps-write-max is set as well.
1958# @iops-size:              when limiting by iops max size of an I/O in bytes
1959#
1960# Since: 2.11
1961##
1962{ 'struct': 'ThrottleLimits',
1963  'data': { '*iops-total' : 'int', '*iops-total-max' : 'int',
1964            '*iops-total-max-length' : 'int', '*iops-read' : 'int',
1965            '*iops-read-max' : 'int', '*iops-read-max-length' : 'int',
1966            '*iops-write' : 'int', '*iops-write-max' : 'int',
1967            '*iops-write-max-length' : 'int', '*bps-total' : 'int',
1968            '*bps-total-max' : 'int', '*bps-total-max-length' : 'int',
1969            '*bps-read' : 'int', '*bps-read-max' : 'int',
1970            '*bps-read-max-length' : 'int', '*bps-write' : 'int',
1971            '*bps-write-max' : 'int', '*bps-write-max-length' : 'int',
1972            '*iops-size' : 'int' } }
1973
1974##
1975# @block-stream:
1976#
1977# Copy data from a backing file into a block device.
1978#
1979# The block streaming operation is performed in the background until the entire
1980# backing file has been copied.  This command returns immediately once streaming
1981# has started.  The status of ongoing block streaming operations can be checked
1982# with query-block-jobs.  The operation can be stopped before it has completed
1983# using the block-job-cancel command.
1984#
1985# The node that receives the data is called the top image, can be located in
1986# any part of the chain (but always above the base image; see below) and can be
1987# specified using its device or node name. Earlier qemu versions only allowed
1988# 'device' to name the top level node; presence of the 'base-node' parameter
1989# during introspection can be used as a witness of the enhanced semantics
1990# of 'device'.
1991#
1992# If a base file is specified then sectors are not copied from that base file and
1993# its backing chain.  When streaming completes the image file will have the base
1994# file as its backing file.  This can be used to stream a subset of the backing
1995# file chain instead of flattening the entire image.
1996#
1997# On successful completion the image file is updated to drop the backing file
1998# and the BLOCK_JOB_COMPLETED event is emitted.
1999#
2000# @job-id: identifier for the newly-created block job. If
2001#          omitted, the device name will be used. (Since 2.7)
2002#
2003# @device: the device or node name of the top image
2004#
2005# @base:   the common backing file name.
2006#                    It cannot be set if @base-node is also set.
2007#
2008# @base-node: the node name of the backing file.
2009#                       It cannot be set if @base is also set. (Since 2.8)
2010#
2011# @backing-file: The backing file string to write into the top
2012#                          image. This filename is not validated.
2013#
2014#                          If a pathname string is such that it cannot be
2015#                          resolved by QEMU, that means that subsequent QMP or
2016#                          HMP commands must use node-names for the image in
2017#                          question, as filename lookup methods will fail.
2018#
2019#                          If not specified, QEMU will automatically determine
2020#                          the backing file string to use, or error out if there
2021#                          is no obvious choice.  Care should be taken when
2022#                          specifying the string, to specify a valid filename or
2023#                          protocol.
2024#                          (Since 2.1)
2025#
2026# @speed:  the maximum speed, in bytes per second
2027#
2028# @on-error: the action to take on an error (default report).
2029#            'stop' and 'enospc' can only be used if the block device
2030#            supports io-status (see BlockInfo).  Since 1.3.
2031#
2032# Returns: Nothing on success. If @device does not exist, DeviceNotFound.
2033#
2034# Since: 1.1
2035#
2036# Example:
2037#
2038# -> { "execute": "block-stream",
2039#      "arguments": { "device": "virtio0",
2040#                     "base": "/tmp/master.qcow2" } }
2041# <- { "return": {} }
2042#
2043##
2044{ 'command': 'block-stream',
2045  'data': { '*job-id': 'str', 'device': 'str', '*base': 'str',
2046            '*base-node': 'str', '*backing-file': 'str', '*speed': 'int',
2047            '*on-error': 'BlockdevOnError' } }
2048
2049##
2050# @block-job-set-speed:
2051#
2052# Set maximum speed for a background block operation.
2053#
2054# This command can only be issued when there is an active block job.
2055#
2056# Throttling can be disabled by setting the speed to 0.
2057#
2058# @device: The job identifier. This used to be a device name (hence
2059#          the name of the parameter), but since QEMU 2.7 it can have
2060#          other values.
2061#
2062# @speed:  the maximum speed, in bytes per second, or 0 for unlimited.
2063#          Defaults to 0.
2064#
2065# Returns: Nothing on success
2066#          If no background operation is active on this device, DeviceNotActive
2067#
2068# Since: 1.1
2069##
2070{ 'command': 'block-job-set-speed',
2071  'data': { 'device': 'str', 'speed': 'int' } }
2072
2073##
2074# @block-job-cancel:
2075#
2076# Stop an active background block operation.
2077#
2078# This command returns immediately after marking the active background block
2079# operation for cancellation.  It is an error to call this command if no
2080# operation is in progress.
2081#
2082# The operation will cancel as soon as possible and then emit the
2083# BLOCK_JOB_CANCELLED event.  Before that happens the job is still visible when
2084# enumerated using query-block-jobs.
2085#
2086# Note that if you issue 'block-job-cancel' after 'drive-mirror' has indicated
2087# (via the event BLOCK_JOB_READY) that the source and destination are
2088# synchronized, then the event triggered by this command changes to
2089# BLOCK_JOB_COMPLETED, to indicate that the mirroring has ended and the
2090# destination now has a point-in-time copy tied to the time of the cancellation.
2091#
2092# For streaming, the image file retains its backing file unless the streaming
2093# operation happens to complete just as it is being cancelled.  A new streaming
2094# operation can be started at a later time to finish copying all data from the
2095# backing file.
2096#
2097# @device: The job identifier. This used to be a device name (hence
2098#          the name of the parameter), but since QEMU 2.7 it can have
2099#          other values.
2100#
2101# @force: whether to allow cancellation of a paused job (default
2102#         false).  Since 1.3.
2103#
2104# Returns: Nothing on success
2105#          If no background operation is active on this device, DeviceNotActive
2106#
2107# Since: 1.1
2108##
2109{ 'command': 'block-job-cancel', 'data': { 'device': 'str', '*force': 'bool' } }
2110
2111##
2112# @block-job-pause:
2113#
2114# Pause an active background block operation.
2115#
2116# This command returns immediately after marking the active background block
2117# operation for pausing.  It is an error to call this command if no
2118# operation is in progress.  Pausing an already paused job has no cumulative
2119# effect; a single block-job-resume command will resume the job.
2120#
2121# The operation will pause as soon as possible.  No event is emitted when
2122# the operation is actually paused.  Cancelling a paused job automatically
2123# resumes it.
2124#
2125# @device: The job identifier. This used to be a device name (hence
2126#          the name of the parameter), but since QEMU 2.7 it can have
2127#          other values.
2128#
2129# Returns: Nothing on success
2130#          If no background operation is active on this device, DeviceNotActive
2131#
2132# Since: 1.3
2133##
2134{ 'command': 'block-job-pause', 'data': { 'device': 'str' } }
2135
2136##
2137# @block-job-resume:
2138#
2139# Resume an active background block operation.
2140#
2141# This command returns immediately after resuming a paused background block
2142# operation.  It is an error to call this command if no operation is in
2143# progress.  Resuming an already running job is not an error.
2144#
2145# This command also clears the error status of the job.
2146#
2147# @device: The job identifier. This used to be a device name (hence
2148#          the name of the parameter), but since QEMU 2.7 it can have
2149#          other values.
2150#
2151# Returns: Nothing on success
2152#          If no background operation is active on this device, DeviceNotActive
2153#
2154# Since: 1.3
2155##
2156{ 'command': 'block-job-resume', 'data': { 'device': 'str' } }
2157
2158##
2159# @block-job-complete:
2160#
2161# Manually trigger completion of an active background block operation.  This
2162# is supported for drive mirroring, where it also switches the device to
2163# write to the target path only.  The ability to complete is signaled with
2164# a BLOCK_JOB_READY event.
2165#
2166# This command completes an active background block operation synchronously.
2167# The ordering of this command's return with the BLOCK_JOB_COMPLETED event
2168# is not defined.  Note that if an I/O error occurs during the processing of
2169# this command: 1) the command itself will fail; 2) the error will be processed
2170# according to the rerror/werror arguments that were specified when starting
2171# the operation.
2172#
2173# A cancelled or paused job cannot be completed.
2174#
2175# @device: The job identifier. This used to be a device name (hence
2176#          the name of the parameter), but since QEMU 2.7 it can have
2177#          other values.
2178#
2179# Returns: Nothing on success
2180#          If no background operation is active on this device, DeviceNotActive
2181#
2182# Since: 1.3
2183##
2184{ 'command': 'block-job-complete', 'data': { 'device': 'str' } }
2185
2186##
2187# @BlockdevDiscardOptions:
2188#
2189# Determines how to handle discard requests.
2190#
2191# @ignore:      Ignore the request
2192# @unmap:       Forward as an unmap request
2193#
2194# Since: 2.9
2195##
2196{ 'enum': 'BlockdevDiscardOptions',
2197  'data': [ 'ignore', 'unmap' ] }
2198
2199##
2200# @BlockdevDetectZeroesOptions:
2201#
2202# Describes the operation mode for the automatic conversion of plain
2203# zero writes by the OS to driver specific optimized zero write commands.
2204#
2205# @off:      Disabled (default)
2206# @on:       Enabled
2207# @unmap:    Enabled and even try to unmap blocks if possible. This requires
2208#            also that @BlockdevDiscardOptions is set to unmap for this device.
2209#
2210# Since: 2.1
2211##
2212{ 'enum': 'BlockdevDetectZeroesOptions',
2213  'data': [ 'off', 'on', 'unmap' ] }
2214
2215##
2216# @BlockdevAioOptions:
2217#
2218# Selects the AIO backend to handle I/O requests
2219#
2220# @threads:     Use qemu's thread pool
2221# @native:      Use native AIO backend (only Linux and Windows)
2222#
2223# Since: 2.9
2224##
2225{ 'enum': 'BlockdevAioOptions',
2226  'data': [ 'threads', 'native' ] }
2227
2228##
2229# @BlockdevCacheOptions:
2230#
2231# Includes cache-related options for block devices
2232#
2233# @direct:      enables use of O_DIRECT (bypass the host page cache;
2234#               default: false)
2235# @no-flush:    ignore any flush requests for the device (default:
2236#               false)
2237#
2238# Since: 2.9
2239##
2240{ 'struct': 'BlockdevCacheOptions',
2241  'data': { '*direct': 'bool',
2242            '*no-flush': 'bool' } }
2243
2244##
2245# @BlockdevDriver:
2246#
2247# Drivers that are supported in block device operations.
2248#
2249# @vxhs: Since 2.10
2250# @throttle: Since 2.11
2251# @nvme: Since 2.12
2252#
2253# Since: 2.9
2254##
2255{ 'enum': 'BlockdevDriver',
2256  'data': [ 'blkdebug', 'blkverify', 'bochs', 'cloop',
2257            'dmg', 'file', 'ftp', 'ftps', 'gluster', 'host_cdrom',
2258            'host_device', 'http', 'https', 'iscsi', 'luks', 'nbd', 'nfs',
2259            'null-aio', 'null-co', 'nvme', 'parallels', 'qcow', 'qcow2', 'qed',
2260            'quorum', 'raw', 'rbd', 'replication', 'sheepdog', 'ssh',
2261            'throttle', 'vdi', 'vhdx', 'vmdk', 'vpc', 'vvfat', 'vxhs' ] }
2262
2263##
2264# @BlockdevOptionsFile:
2265#
2266# Driver specific block device options for the file backend.
2267#
2268# @filename:    path to the image file
2269# @pr-manager:  the id for the object that will handle persistent reservations
2270#               for this device (default: none, forward the commands via SG_IO;
2271#               since 2.11)
2272# @aio:         AIO backend (default: threads) (since: 2.8)
2273# @locking:     whether to enable file locking. If set to 'auto', only enable
2274#               when Open File Descriptor (OFD) locking API is available
2275#               (default: auto, since 2.10)
2276#
2277# Since: 2.9
2278##
2279{ 'struct': 'BlockdevOptionsFile',
2280  'data': { 'filename': 'str',
2281            '*pr-manager': 'str',
2282            '*locking': 'OnOffAuto',
2283            '*aio': 'BlockdevAioOptions' } }
2284
2285##
2286# @BlockdevOptionsNull:
2287#
2288# Driver specific block device options for the null backend.
2289#
2290# @size:    size of the device in bytes.
2291# @latency-ns: emulated latency (in nanoseconds) in processing
2292#              requests. Default to zero which completes requests immediately.
2293#              (Since 2.4)
2294#
2295# Since: 2.9
2296##
2297{ 'struct': 'BlockdevOptionsNull',
2298  'data': { '*size': 'int', '*latency-ns': 'uint64' } }
2299
2300##
2301# @BlockdevOptionsNVMe:
2302#
2303# Driver specific block device options for the NVMe backend.
2304#
2305# @device:    controller address of the NVMe device.
2306# @namespace: namespace number of the device, starting from 1.
2307#
2308# Since: 2.12
2309##
2310{ 'struct': 'BlockdevOptionsNVMe',
2311  'data': { 'device': 'str', 'namespace': 'int' } }
2312
2313##
2314# @BlockdevOptionsVVFAT:
2315#
2316# Driver specific block device options for the vvfat protocol.
2317#
2318# @dir:         directory to be exported as FAT image
2319# @fat-type:    FAT type: 12, 16 or 32
2320# @floppy:      whether to export a floppy image (true) or
2321#               partitioned hard disk (false; default)
2322# @label:       set the volume label, limited to 11 bytes. FAT16 and
2323#               FAT32 traditionally have some restrictions on labels, which are
2324#               ignored by most operating systems. Defaults to "QEMU VVFAT".
2325#               (since 2.4)
2326# @rw:          whether to allow write operations (default: false)
2327#
2328# Since: 2.9
2329##
2330{ 'struct': 'BlockdevOptionsVVFAT',
2331  'data': { 'dir': 'str', '*fat-type': 'int', '*floppy': 'bool',
2332            '*label': 'str', '*rw': 'bool' } }
2333
2334##
2335# @BlockdevOptionsGenericFormat:
2336#
2337# Driver specific block device options for image format that have no option
2338# besides their data source.
2339#
2340# @file:        reference to or definition of the data source block device
2341#
2342# Since: 2.9
2343##
2344{ 'struct': 'BlockdevOptionsGenericFormat',
2345  'data': { 'file': 'BlockdevRef' } }
2346
2347##
2348# @BlockdevOptionsLUKS:
2349#
2350# Driver specific block device options for LUKS.
2351#
2352# @key-secret: the ID of a QCryptoSecret object providing
2353#              the decryption key (since 2.6). Mandatory except when
2354#              doing a metadata-only probe of the image.
2355#
2356# Since: 2.9
2357##
2358{ 'struct': 'BlockdevOptionsLUKS',
2359  'base': 'BlockdevOptionsGenericFormat',
2360  'data': { '*key-secret': 'str' } }
2361
2362
2363##
2364# @BlockdevOptionsGenericCOWFormat:
2365#
2366# Driver specific block device options for image format that have no option
2367# besides their data source and an optional backing file.
2368#
2369# @backing:     reference to or definition of the backing file block
2370#               device, null disables the backing file entirely.
2371#               Defaults to the backing file stored the image file.
2372#
2373# Since: 2.9
2374##
2375{ 'struct': 'BlockdevOptionsGenericCOWFormat',
2376  'base': 'BlockdevOptionsGenericFormat',
2377  'data': { '*backing': 'BlockdevRefOrNull' } }
2378
2379##
2380# @Qcow2OverlapCheckMode:
2381#
2382# General overlap check modes.
2383#
2384# @none:        Do not perform any checks
2385#
2386# @constant:    Perform only checks which can be done in constant time and
2387#               without reading anything from disk
2388#
2389# @cached:      Perform only checks which can be done without reading anything
2390#               from disk
2391#
2392# @all:         Perform all available overlap checks
2393#
2394# Since: 2.9
2395##
2396{ 'enum': 'Qcow2OverlapCheckMode',
2397  'data': [ 'none', 'constant', 'cached', 'all' ] }
2398
2399##
2400# @Qcow2OverlapCheckFlags:
2401#
2402# Structure of flags for each metadata structure. Setting a field to 'true'
2403# makes qemu guard that structure against unintended overwriting. The default
2404# value is chosen according to the template given.
2405#
2406# @template: Specifies a template mode which can be adjusted using the other
2407#            flags, defaults to 'cached'
2408#
2409# Since: 2.9
2410##
2411{ 'struct': 'Qcow2OverlapCheckFlags',
2412  'data': { '*template':       'Qcow2OverlapCheckMode',
2413            '*main-header':    'bool',
2414            '*active-l1':      'bool',
2415            '*active-l2':      'bool',
2416            '*refcount-table': 'bool',
2417            '*refcount-block': 'bool',
2418            '*snapshot-table': 'bool',
2419            '*inactive-l1':    'bool',
2420            '*inactive-l2':    'bool' } }
2421
2422##
2423# @Qcow2OverlapChecks:
2424#
2425# Specifies which metadata structures should be guarded against unintended
2426# overwriting.
2427#
2428# @flags:   set of flags for separate specification of each metadata structure
2429#           type
2430#
2431# @mode:    named mode which chooses a specific set of flags
2432#
2433# Since: 2.9
2434##
2435{ 'alternate': 'Qcow2OverlapChecks',
2436  'data': { 'flags': 'Qcow2OverlapCheckFlags',
2437            'mode':  'Qcow2OverlapCheckMode' } }
2438
2439##
2440# @BlockdevQcowEncryptionFormat:
2441#
2442# @aes: AES-CBC with plain64 initialization vectors
2443#
2444# Since: 2.10
2445##
2446{ 'enum': 'BlockdevQcowEncryptionFormat',
2447  'data': [ 'aes' ] }
2448
2449##
2450# @BlockdevQcowEncryption:
2451#
2452# Since: 2.10
2453##
2454{ 'union': 'BlockdevQcowEncryption',
2455  'base': { 'format': 'BlockdevQcowEncryptionFormat' },
2456  'discriminator': 'format',
2457  'data': { 'aes': 'QCryptoBlockOptionsQCow' } }
2458
2459##
2460# @BlockdevOptionsQcow:
2461#
2462# Driver specific block device options for qcow.
2463#
2464# @encrypt:               Image decryption options. Mandatory for
2465#                         encrypted images, except when doing a metadata-only
2466#                         probe of the image.
2467#
2468# Since: 2.10
2469##
2470{ 'struct': 'BlockdevOptionsQcow',
2471  'base': 'BlockdevOptionsGenericCOWFormat',
2472  'data': { '*encrypt': 'BlockdevQcowEncryption' } }
2473
2474
2475
2476##
2477# @BlockdevQcow2EncryptionFormat:
2478# @aes: AES-CBC with plain64 initialization venctors
2479#
2480# Since: 2.10
2481##
2482{ 'enum': 'BlockdevQcow2EncryptionFormat',
2483  'data': [ 'aes', 'luks' ] }
2484
2485##
2486# @BlockdevQcow2Encryption:
2487#
2488# Since: 2.10
2489##
2490{ 'union': 'BlockdevQcow2Encryption',
2491  'base': { 'format': 'BlockdevQcow2EncryptionFormat' },
2492  'discriminator': 'format',
2493  'data': { 'aes': 'QCryptoBlockOptionsQCow',
2494            'luks': 'QCryptoBlockOptionsLUKS'} }
2495
2496##
2497# @BlockdevOptionsQcow2:
2498#
2499# Driver specific block device options for qcow2.
2500#
2501# @lazy-refcounts:        whether to enable the lazy refcounts
2502#                         feature (default is taken from the image file)
2503#
2504# @pass-discard-request:  whether discard requests to the qcow2
2505#                         device should be forwarded to the data source
2506#
2507# @pass-discard-snapshot: whether discard requests for the data source
2508#                         should be issued when a snapshot operation (e.g.
2509#                         deleting a snapshot) frees clusters in the qcow2 file
2510#
2511# @pass-discard-other:    whether discard requests for the data source
2512#                         should be issued on other occasions where a cluster
2513#                         gets freed
2514#
2515# @overlap-check:         which overlap checks to perform for writes
2516#                         to the image, defaults to 'cached' (since 2.2)
2517#
2518# @cache-size:            the maximum total size of the L2 table and
2519#                         refcount block caches in bytes (since 2.2)
2520#
2521# @l2-cache-size:         the maximum size of the L2 table cache in
2522#                         bytes (since 2.2)
2523#
2524# @l2-cache-entry-size:   the size of each entry in the L2 cache in
2525#                         bytes. It must be a power of two between 512
2526#                         and the cluster size. The default value is
2527#                         the cluster size (since 2.12)
2528#
2529# @refcount-cache-size:   the maximum size of the refcount block cache
2530#                         in bytes (since 2.2)
2531#
2532# @cache-clean-interval:  clean unused entries in the L2 and refcount
2533#                         caches. The interval is in seconds. The default value
2534#                         is 0 and it disables this feature (since 2.5)
2535# @encrypt:               Image decryption options. Mandatory for
2536#                         encrypted images, except when doing a metadata-only
2537#                         probe of the image. (since 2.10)
2538#
2539# Since: 2.9
2540##
2541{ 'struct': 'BlockdevOptionsQcow2',
2542  'base': 'BlockdevOptionsGenericCOWFormat',
2543  'data': { '*lazy-refcounts': 'bool',
2544            '*pass-discard-request': 'bool',
2545            '*pass-discard-snapshot': 'bool',
2546            '*pass-discard-other': 'bool',
2547            '*overlap-check': 'Qcow2OverlapChecks',
2548            '*cache-size': 'int',
2549            '*l2-cache-size': 'int',
2550            '*l2-cache-entry-size': 'int',
2551            '*refcount-cache-size': 'int',
2552            '*cache-clean-interval': 'int',
2553            '*encrypt': 'BlockdevQcow2Encryption' } }
2554
2555##
2556# @BlockdevOptionsSsh:
2557#
2558# @server:              host address
2559#
2560# @path:                path to the image on the host
2561#
2562# @user:                user as which to connect, defaults to current
2563#                       local user name
2564#
2565# TODO: Expose the host_key_check option in QMP
2566#
2567# Since: 2.9
2568##
2569{ 'struct': 'BlockdevOptionsSsh',
2570  'data': { 'server': 'InetSocketAddress',
2571            'path': 'str',
2572            '*user': 'str' } }
2573
2574
2575##
2576# @BlkdebugEvent:
2577#
2578# Trigger events supported by blkdebug.
2579#
2580# @l1_shrink_write_table:      write zeros to the l1 table to shrink image.
2581#                              (since 2.11)
2582#
2583# @l1_shrink_free_l2_clusters: discard the l2 tables. (since 2.11)
2584#
2585# @cor_write: a write due to copy-on-read (since 2.11)
2586#
2587# Since: 2.9
2588##
2589{ 'enum': 'BlkdebugEvent', 'prefix': 'BLKDBG',
2590  'data': [ 'l1_update', 'l1_grow_alloc_table', 'l1_grow_write_table',
2591            'l1_grow_activate_table', 'l2_load', 'l2_update',
2592            'l2_update_compressed', 'l2_alloc_cow_read', 'l2_alloc_write',
2593            'read_aio', 'read_backing_aio', 'read_compressed', 'write_aio',
2594            'write_compressed', 'vmstate_load', 'vmstate_save', 'cow_read',
2595            'cow_write', 'reftable_load', 'reftable_grow', 'reftable_update',
2596            'refblock_load', 'refblock_update', 'refblock_update_part',
2597            'refblock_alloc', 'refblock_alloc_hookup', 'refblock_alloc_write',
2598            'refblock_alloc_write_blocks', 'refblock_alloc_write_table',
2599            'refblock_alloc_switch_table', 'cluster_alloc',
2600            'cluster_alloc_bytes', 'cluster_free', 'flush_to_os',
2601            'flush_to_disk', 'pwritev_rmw_head', 'pwritev_rmw_after_head',
2602            'pwritev_rmw_tail', 'pwritev_rmw_after_tail', 'pwritev',
2603            'pwritev_zero', 'pwritev_done', 'empty_image_prepare',
2604            'l1_shrink_write_table', 'l1_shrink_free_l2_clusters',
2605            'cor_write'] }
2606
2607##
2608# @BlkdebugInjectErrorOptions:
2609#
2610# Describes a single error injection for blkdebug.
2611#
2612# @event:       trigger event
2613#
2614# @state:       the state identifier blkdebug needs to be in to
2615#               actually trigger the event; defaults to "any"
2616#
2617# @errno:       error identifier (errno) to be returned; defaults to
2618#               EIO
2619#
2620# @sector:      specifies the sector index which has to be affected
2621#               in order to actually trigger the event; defaults to "any
2622#               sector"
2623#
2624# @once:        disables further events after this one has been
2625#               triggered; defaults to false
2626#
2627# @immediately: fail immediately; defaults to false
2628#
2629# Since: 2.9
2630##
2631{ 'struct': 'BlkdebugInjectErrorOptions',
2632  'data': { 'event': 'BlkdebugEvent',
2633            '*state': 'int',
2634            '*errno': 'int',
2635            '*sector': 'int',
2636            '*once': 'bool',
2637            '*immediately': 'bool' } }
2638
2639##
2640# @BlkdebugSetStateOptions:
2641#
2642# Describes a single state-change event for blkdebug.
2643#
2644# @event:       trigger event
2645#
2646# @state:       the current state identifier blkdebug needs to be in;
2647#               defaults to "any"
2648#
2649# @new_state:   the state identifier blkdebug is supposed to assume if
2650#               this event is triggered
2651#
2652# Since: 2.9
2653##
2654{ 'struct': 'BlkdebugSetStateOptions',
2655  'data': { 'event': 'BlkdebugEvent',
2656            '*state': 'int',
2657            'new_state': 'int' } }
2658
2659##
2660# @BlockdevOptionsBlkdebug:
2661#
2662# Driver specific block device options for blkdebug.
2663#
2664# @image:           underlying raw block device (or image file)
2665#
2666# @config:          filename of the configuration file
2667#
2668# @align:           required alignment for requests in bytes, must be
2669#                   positive power of 2, or 0 for default
2670#
2671# @max-transfer:    maximum size for I/O transfers in bytes, must be
2672#                   positive multiple of @align and of the underlying
2673#                   file's request alignment (but need not be a power of
2674#                   2), or 0 for default (since 2.10)
2675#
2676# @opt-write-zero:  preferred alignment for write zero requests in bytes,
2677#                   must be positive multiple of @align and of the
2678#                   underlying file's request alignment (but need not be a
2679#                   power of 2), or 0 for default (since 2.10)
2680#
2681# @max-write-zero:  maximum size for write zero requests in bytes, must be
2682#                   positive multiple of @align, of @opt-write-zero, and of
2683#                   the underlying file's request alignment (but need not
2684#                   be a power of 2), or 0 for default (since 2.10)
2685#
2686# @opt-discard:     preferred alignment for discard requests in bytes, must
2687#                   be positive multiple of @align and of the underlying
2688#                   file's request alignment (but need not be a power of
2689#                   2), or 0 for default (since 2.10)
2690#
2691# @max-discard:     maximum size for discard requests in bytes, must be
2692#                   positive multiple of @align, of @opt-discard, and of
2693#                   the underlying file's request alignment (but need not
2694#                   be a power of 2), or 0 for default (since 2.10)
2695#
2696# @inject-error:    array of error injection descriptions
2697#
2698# @set-state:       array of state-change descriptions
2699#
2700# Since: 2.9
2701##
2702{ 'struct': 'BlockdevOptionsBlkdebug',
2703  'data': { 'image': 'BlockdevRef',
2704            '*config': 'str',
2705            '*align': 'int', '*max-transfer': 'int32',
2706            '*opt-write-zero': 'int32', '*max-write-zero': 'int32',
2707            '*opt-discard': 'int32', '*max-discard': 'int32',
2708            '*inject-error': ['BlkdebugInjectErrorOptions'],
2709            '*set-state': ['BlkdebugSetStateOptions'] } }
2710
2711##
2712# @BlockdevOptionsBlkverify:
2713#
2714# Driver specific block device options for blkverify.
2715#
2716# @test:    block device to be tested
2717#
2718# @raw:     raw image used for verification
2719#
2720# Since: 2.9
2721##
2722{ 'struct': 'BlockdevOptionsBlkverify',
2723  'data': { 'test': 'BlockdevRef',
2724            'raw': 'BlockdevRef' } }
2725
2726##
2727# @QuorumReadPattern:
2728#
2729# An enumeration of quorum read patterns.
2730#
2731# @quorum: read all the children and do a quorum vote on reads
2732#
2733# @fifo: read only from the first child that has not failed
2734#
2735# Since: 2.9
2736##
2737{ 'enum': 'QuorumReadPattern', 'data': [ 'quorum', 'fifo' ] }
2738
2739##
2740# @BlockdevOptionsQuorum:
2741#
2742# Driver specific block device options for Quorum
2743#
2744# @blkverify:      true if the driver must print content mismatch
2745#                  set to false by default
2746#
2747# @children:       the children block devices to use
2748#
2749# @vote-threshold: the vote limit under which a read will fail
2750#
2751# @rewrite-corrupted: rewrite corrupted data when quorum is reached
2752#                     (Since 2.1)
2753#
2754# @read-pattern: choose read pattern and set to quorum by default
2755#                (Since 2.2)
2756#
2757# Since: 2.9
2758##
2759{ 'struct': 'BlockdevOptionsQuorum',
2760  'data': { '*blkverify': 'bool',
2761            'children': [ 'BlockdevRef' ],
2762            'vote-threshold': 'int',
2763            '*rewrite-corrupted': 'bool',
2764            '*read-pattern': 'QuorumReadPattern' } }
2765
2766##
2767# @BlockdevOptionsGluster:
2768#
2769# Driver specific block device options for Gluster
2770#
2771# @volume:      name of gluster volume where VM image resides
2772#
2773# @path:        absolute path to image file in gluster volume
2774#
2775# @server:      gluster servers description
2776#
2777# @debug:       libgfapi log level (default '4' which is Error)
2778#               (Since 2.8)
2779#
2780# @logfile:     libgfapi log file (default /dev/stderr) (Since 2.8)
2781#
2782# Since: 2.9
2783##
2784{ 'struct': 'BlockdevOptionsGluster',
2785  'data': { 'volume': 'str',
2786            'path': 'str',
2787            'server': ['SocketAddress'],
2788            '*debug': 'int',
2789            '*logfile': 'str' } }
2790
2791##
2792# @IscsiTransport:
2793#
2794# An enumeration of libiscsi transport types
2795#
2796# Since: 2.9
2797##
2798{ 'enum': 'IscsiTransport',
2799  'data': [ 'tcp', 'iser' ] }
2800
2801##
2802# @IscsiHeaderDigest:
2803#
2804# An enumeration of header digests supported by libiscsi
2805#
2806# Since: 2.9
2807##
2808{ 'enum': 'IscsiHeaderDigest',
2809  'prefix': 'QAPI_ISCSI_HEADER_DIGEST',
2810  'data': [ 'crc32c', 'none', 'crc32c-none', 'none-crc32c' ] }
2811
2812##
2813# @BlockdevOptionsIscsi:
2814#
2815# @transport:       The iscsi transport type
2816#
2817# @portal:          The address of the iscsi portal
2818#
2819# @target:          The target iqn name
2820#
2821# @lun:             LUN to connect to. Defaults to 0.
2822#
2823# @user:            User name to log in with. If omitted, no CHAP
2824#                   authentication is performed.
2825#
2826# @password-secret: The ID of a QCryptoSecret object providing
2827#                   the password for the login. This option is required if
2828#                   @user is specified.
2829#
2830# @initiator-name:  The iqn name we want to identify to the target
2831#                   as. If this option is not specified, an initiator name is
2832#                   generated automatically.
2833#
2834# @header-digest:   The desired header digest. Defaults to
2835#                   none-crc32c.
2836#
2837# @timeout:         Timeout in seconds after which a request will
2838#                   timeout. 0 means no timeout and is the default.
2839#
2840# Driver specific block device options for iscsi
2841#
2842# Since: 2.9
2843##
2844{ 'struct': 'BlockdevOptionsIscsi',
2845  'data': { 'transport': 'IscsiTransport',
2846            'portal': 'str',
2847            'target': 'str',
2848            '*lun': 'int',
2849            '*user': 'str',
2850            '*password-secret': 'str',
2851            '*initiator-name': 'str',
2852            '*header-digest': 'IscsiHeaderDigest',
2853            '*timeout': 'int' } }
2854
2855
2856##
2857# @BlockdevOptionsRbd:
2858#
2859# @pool:               Ceph pool name.
2860#
2861# @image:              Image name in the Ceph pool.
2862#
2863# @conf:               path to Ceph configuration file.  Values
2864#                      in the configuration file will be overridden by
2865#                      options specified via QAPI.
2866#
2867# @snapshot:           Ceph snapshot name.
2868#
2869# @user:               Ceph id name.
2870#
2871# @server:             Monitor host address and port.  This maps
2872#                      to the "mon_host" Ceph option.
2873#
2874# Since: 2.9
2875##
2876{ 'struct': 'BlockdevOptionsRbd',
2877  'data': { 'pool': 'str',
2878            'image': 'str',
2879            '*conf': 'str',
2880            '*snapshot': 'str',
2881            '*user': 'str',
2882            '*server': ['InetSocketAddressBase'] } }
2883
2884##
2885# @BlockdevOptionsSheepdog:
2886#
2887# Driver specific block device options for sheepdog
2888#
2889# @vdi:         Virtual disk image name
2890# @server:      The Sheepdog server to connect to
2891# @snap-id:     Snapshot ID
2892# @tag:         Snapshot tag name
2893#
2894# Only one of @snap-id and @tag may be present.
2895#
2896# Since: 2.9
2897##
2898{ 'struct': 'BlockdevOptionsSheepdog',
2899  'data': { 'server': 'SocketAddress',
2900            'vdi': 'str',
2901            '*snap-id': 'uint32',
2902            '*tag': 'str' } }
2903
2904##
2905# @ReplicationMode:
2906#
2907# An enumeration of replication modes.
2908#
2909# @primary: Primary mode, the vm's state will be sent to secondary QEMU.
2910#
2911# @secondary: Secondary mode, receive the vm's state from primary QEMU.
2912#
2913# Since: 2.9
2914##
2915{ 'enum' : 'ReplicationMode', 'data' : [ 'primary', 'secondary' ] }
2916
2917##
2918# @BlockdevOptionsReplication:
2919#
2920# Driver specific block device options for replication
2921#
2922# @mode: the replication mode
2923#
2924# @top-id: In secondary mode, node name or device ID of the root
2925#          node who owns the replication node chain. Must not be given in
2926#          primary mode.
2927#
2928# Since: 2.9
2929##
2930{ 'struct': 'BlockdevOptionsReplication',
2931  'base': 'BlockdevOptionsGenericFormat',
2932  'data': { 'mode': 'ReplicationMode',
2933            '*top-id': 'str' } }
2934
2935##
2936# @NFSTransport:
2937#
2938# An enumeration of NFS transport types
2939#
2940# @inet:        TCP transport
2941#
2942# Since: 2.9
2943##
2944{ 'enum': 'NFSTransport',
2945  'data': [ 'inet' ] }
2946
2947##
2948# @NFSServer:
2949#
2950# Captures the address of the socket
2951#
2952# @type:        transport type used for NFS (only TCP supported)
2953#
2954# @host:        host address for NFS server
2955#
2956# Since: 2.9
2957##
2958{ 'struct': 'NFSServer',
2959  'data': { 'type': 'NFSTransport',
2960            'host': 'str' } }
2961
2962##
2963# @BlockdevOptionsNfs:
2964#
2965# Driver specific block device option for NFS
2966#
2967# @server:                  host address
2968#
2969# @path:                    path of the image on the host
2970#
2971# @user:                    UID value to use when talking to the
2972#                           server (defaults to 65534 on Windows and getuid()
2973#                           on unix)
2974#
2975# @group:                   GID value to use when talking to the
2976#                           server (defaults to 65534 on Windows and getgid()
2977#                           in unix)
2978#
2979# @tcp-syn-count:           number of SYNs during the session
2980#                           establishment (defaults to libnfs default)
2981#
2982# @readahead-size:          set the readahead size in bytes (defaults
2983#                           to libnfs default)
2984#
2985# @page-cache-size:         set the pagecache size in bytes (defaults
2986#                           to libnfs default)
2987#
2988# @debug:                   set the NFS debug level (max 2) (defaults
2989#                           to libnfs default)
2990#
2991# Since: 2.9
2992##
2993{ 'struct': 'BlockdevOptionsNfs',
2994  'data': { 'server': 'NFSServer',
2995            'path': 'str',
2996            '*user': 'int',
2997            '*group': 'int',
2998            '*tcp-syn-count': 'int',
2999            '*readahead-size': 'int',
3000            '*page-cache-size': 'int',
3001            '*debug': 'int' } }
3002
3003##
3004# @BlockdevOptionsCurlBase:
3005#
3006# Driver specific block device options shared by all protocols supported by the
3007# curl backend.
3008#
3009# @url:                     URL of the image file
3010#
3011# @readahead:               Size of the read-ahead cache; must be a multiple of
3012#                           512 (defaults to 256 kB)
3013#
3014# @timeout:                 Timeout for connections, in seconds (defaults to 5)
3015#
3016# @username:                Username for authentication (defaults to none)
3017#
3018# @password-secret:         ID of a QCryptoSecret object providing a password
3019#                           for authentication (defaults to no password)
3020#
3021# @proxy-username:          Username for proxy authentication (defaults to none)
3022#
3023# @proxy-password-secret:   ID of a QCryptoSecret object providing a password
3024#                           for proxy authentication (defaults to no password)
3025#
3026# Since: 2.9
3027##
3028{ 'struct': 'BlockdevOptionsCurlBase',
3029  'data': { 'url': 'str',
3030            '*readahead': 'int',
3031            '*timeout': 'int',
3032            '*username': 'str',
3033            '*password-secret': 'str',
3034            '*proxy-username': 'str',
3035            '*proxy-password-secret': 'str' } }
3036
3037##
3038# @BlockdevOptionsCurlHttp:
3039#
3040# Driver specific block device options for HTTP connections over the curl
3041# backend.  URLs must start with "http://".
3042#
3043# @cookie:      List of cookies to set; format is
3044#               "name1=content1; name2=content2;" as explained by
3045#               CURLOPT_COOKIE(3). Defaults to no cookies.
3046#
3047# @cookie-secret: ID of a QCryptoSecret object providing the cookie data in a
3048#                 secure way. See @cookie for the format. (since 2.10)
3049#
3050# Since: 2.9
3051##
3052{ 'struct': 'BlockdevOptionsCurlHttp',
3053  'base': 'BlockdevOptionsCurlBase',
3054  'data': { '*cookie': 'str',
3055            '*cookie-secret': 'str'} }
3056
3057##
3058# @BlockdevOptionsCurlHttps:
3059#
3060# Driver specific block device options for HTTPS connections over the curl
3061# backend.  URLs must start with "https://".
3062#
3063# @cookie:      List of cookies to set; format is
3064#               "name1=content1; name2=content2;" as explained by
3065#               CURLOPT_COOKIE(3). Defaults to no cookies.
3066#
3067# @sslverify:   Whether to verify the SSL certificate's validity (defaults to
3068#               true)
3069#
3070# @cookie-secret: ID of a QCryptoSecret object providing the cookie data in a
3071#                 secure way. See @cookie for the format. (since 2.10)
3072#
3073# Since: 2.9
3074##
3075{ 'struct': 'BlockdevOptionsCurlHttps',
3076  'base': 'BlockdevOptionsCurlBase',
3077  'data': { '*cookie': 'str',
3078            '*sslverify': 'bool',
3079            '*cookie-secret': 'str'} }
3080
3081##
3082# @BlockdevOptionsCurlFtp:
3083#
3084# Driver specific block device options for FTP connections over the curl
3085# backend.  URLs must start with "ftp://".
3086#
3087# Since: 2.9
3088##
3089{ 'struct': 'BlockdevOptionsCurlFtp',
3090  'base': 'BlockdevOptionsCurlBase',
3091  'data': { } }
3092
3093##
3094# @BlockdevOptionsCurlFtps:
3095#
3096# Driver specific block device options for FTPS connections over the curl
3097# backend.  URLs must start with "ftps://".
3098#
3099# @sslverify:   Whether to verify the SSL certificate's validity (defaults to
3100#               true)
3101#
3102# Since: 2.9
3103##
3104{ 'struct': 'BlockdevOptionsCurlFtps',
3105  'base': 'BlockdevOptionsCurlBase',
3106  'data': { '*sslverify': 'bool' } }
3107
3108##
3109# @BlockdevOptionsNbd:
3110#
3111# Driver specific block device options for NBD.
3112#
3113# @server:      NBD server address
3114#
3115# @export:      export name
3116#
3117# @tls-creds:   TLS credentials ID
3118#
3119# Since: 2.9
3120##
3121{ 'struct': 'BlockdevOptionsNbd',
3122  'data': { 'server': 'SocketAddress',
3123            '*export': 'str',
3124            '*tls-creds': 'str' } }
3125
3126##
3127# @BlockdevOptionsRaw:
3128#
3129# Driver specific block device options for the raw driver.
3130#
3131# @offset:      position where the block device starts
3132# @size:        the assumed size of the device
3133#
3134# Since: 2.9
3135##
3136{ 'struct': 'BlockdevOptionsRaw',
3137  'base': 'BlockdevOptionsGenericFormat',
3138  'data': { '*offset': 'int', '*size': 'int' } }
3139
3140##
3141# @BlockdevOptionsVxHS:
3142#
3143# Driver specific block device options for VxHS
3144#
3145# @vdisk-id:    UUID of VxHS volume
3146# @server:      vxhs server IP, port
3147# @tls-creds:   TLS credentials ID
3148#
3149# Since: 2.10
3150##
3151{ 'struct': 'BlockdevOptionsVxHS',
3152  'data': { 'vdisk-id': 'str',
3153            'server': 'InetSocketAddressBase',
3154            '*tls-creds': 'str' } }
3155
3156##
3157# @BlockdevOptionsThrottle:
3158#
3159# Driver specific block device options for the throttle driver
3160#
3161# @throttle-group:   the name of the throttle-group object to use. It
3162#                    must already exist.
3163# @file:             reference to or definition of the data source block device
3164# Since: 2.11
3165##
3166{ 'struct': 'BlockdevOptionsThrottle',
3167  'data': { 'throttle-group': 'str',
3168            'file' : 'BlockdevRef'
3169             } }
3170##
3171# @BlockdevOptions:
3172#
3173# Options for creating a block device.  Many options are available for all
3174# block devices, independent of the block driver:
3175#
3176# @driver:        block driver name
3177# @node-name:     the node name of the new node (Since 2.0).
3178#                 This option is required on the top level of blockdev-add.
3179# @discard:       discard-related options (default: ignore)
3180# @cache:         cache-related options
3181# @read-only:     whether the block device should be read-only (default: false).
3182#                 Note that some block drivers support only read-only access,
3183#                 either generally or in certain configurations. In this case,
3184#                 the default value does not work and the option must be
3185#                 specified explicitly.
3186# @detect-zeroes: detect and optimize zero writes (Since 2.1)
3187#                 (default: off)
3188# @force-share:   force share all permission on added nodes.
3189#                 Requires read-only=true. (Since 2.10)
3190#
3191# Remaining options are determined by the block driver.
3192#
3193# Since: 2.9
3194##
3195{ 'union': 'BlockdevOptions',
3196  'base': { 'driver': 'BlockdevDriver',
3197            '*node-name': 'str',
3198            '*discard': 'BlockdevDiscardOptions',
3199            '*cache': 'BlockdevCacheOptions',
3200            '*read-only': 'bool',
3201            '*force-share': 'bool',
3202            '*detect-zeroes': 'BlockdevDetectZeroesOptions' },
3203  'discriminator': 'driver',
3204  'data': {
3205      'blkdebug':   'BlockdevOptionsBlkdebug',
3206      'blkverify':  'BlockdevOptionsBlkverify',
3207      'bochs':      'BlockdevOptionsGenericFormat',
3208      'cloop':      'BlockdevOptionsGenericFormat',
3209      'dmg':        'BlockdevOptionsGenericFormat',
3210      'file':       'BlockdevOptionsFile',
3211      'ftp':        'BlockdevOptionsCurlFtp',
3212      'ftps':       'BlockdevOptionsCurlFtps',
3213      'gluster':    'BlockdevOptionsGluster',
3214      'host_cdrom': 'BlockdevOptionsFile',
3215      'host_device':'BlockdevOptionsFile',
3216      'http':       'BlockdevOptionsCurlHttp',
3217      'https':      'BlockdevOptionsCurlHttps',
3218      'iscsi':      'BlockdevOptionsIscsi',
3219      'luks':       'BlockdevOptionsLUKS',
3220      'nbd':        'BlockdevOptionsNbd',
3221      'nfs':        'BlockdevOptionsNfs',
3222      'null-aio':   'BlockdevOptionsNull',
3223      'null-co':    'BlockdevOptionsNull',
3224      'nvme':       'BlockdevOptionsNVMe',
3225      'parallels':  'BlockdevOptionsGenericFormat',
3226      'qcow2':      'BlockdevOptionsQcow2',
3227      'qcow':       'BlockdevOptionsQcow',
3228      'qed':        'BlockdevOptionsGenericCOWFormat',
3229      'quorum':     'BlockdevOptionsQuorum',
3230      'raw':        'BlockdevOptionsRaw',
3231      'rbd':        'BlockdevOptionsRbd',
3232      'replication':'BlockdevOptionsReplication',
3233      'sheepdog':   'BlockdevOptionsSheepdog',
3234      'ssh':        'BlockdevOptionsSsh',
3235      'throttle':   'BlockdevOptionsThrottle',
3236      'vdi':        'BlockdevOptionsGenericFormat',
3237      'vhdx':       'BlockdevOptionsGenericFormat',
3238      'vmdk':       'BlockdevOptionsGenericCOWFormat',
3239      'vpc':        'BlockdevOptionsGenericFormat',
3240      'vvfat':      'BlockdevOptionsVVFAT',
3241      'vxhs':       'BlockdevOptionsVxHS'
3242  } }
3243
3244##
3245# @BlockdevRef:
3246#
3247# Reference to a block device.
3248#
3249# @definition:      defines a new block device inline
3250# @reference:       references the ID of an existing block device
3251#
3252# Since: 2.9
3253##
3254{ 'alternate': 'BlockdevRef',
3255  'data': { 'definition': 'BlockdevOptions',
3256            'reference': 'str' } }
3257
3258##
3259# @BlockdevRefOrNull:
3260#
3261# Reference to a block device.
3262#
3263# @definition:      defines a new block device inline
3264# @reference:       references the ID of an existing block device.
3265#                   An empty string means that no block device should
3266#                   be referenced.  Deprecated; use null instead.
3267# @null:            No block device should be referenced (since 2.10)
3268#
3269# Since: 2.9
3270##
3271{ 'alternate': 'BlockdevRefOrNull',
3272  'data': { 'definition': 'BlockdevOptions',
3273            'reference': 'str',
3274            'null': 'null' } }
3275
3276##
3277# @blockdev-add:
3278#
3279# Creates a new block device. If the @id option is given at the top level, a
3280# BlockBackend will be created; otherwise, @node-name is mandatory at the top
3281# level and no BlockBackend will be created.
3282#
3283# Since: 2.9
3284#
3285# Example:
3286#
3287# 1.
3288# -> { "execute": "blockdev-add",
3289#      "arguments": {
3290#           "driver": "qcow2",
3291#           "node-name": "test1",
3292#           "file": {
3293#               "driver": "file",
3294#               "filename": "test.qcow2"
3295#            }
3296#       }
3297#     }
3298# <- { "return": {} }
3299#
3300# 2.
3301# -> { "execute": "blockdev-add",
3302#      "arguments": {
3303#           "driver": "qcow2",
3304#           "node-name": "node0",
3305#           "discard": "unmap",
3306#           "cache": {
3307#              "direct": true
3308#            },
3309#            "file": {
3310#              "driver": "file",
3311#              "filename": "/tmp/test.qcow2"
3312#            },
3313#            "backing": {
3314#               "driver": "raw",
3315#               "file": {
3316#                  "driver": "file",
3317#                  "filename": "/dev/fdset/4"
3318#                }
3319#            }
3320#        }
3321#      }
3322#
3323# <- { "return": {} }
3324#
3325##
3326{ 'command': 'blockdev-add', 'data': 'BlockdevOptions', 'boxed': true }
3327
3328##
3329# @blockdev-del:
3330#
3331# Deletes a block device that has been added using blockdev-add.
3332# The command will fail if the node is attached to a device or is
3333# otherwise being used.
3334#
3335# @node-name: Name of the graph node to delete.
3336#
3337# Since: 2.9
3338#
3339# Example:
3340#
3341# -> { "execute": "blockdev-add",
3342#      "arguments": {
3343#           "driver": "qcow2",
3344#           "node-name": "node0",
3345#           "file": {
3346#               "driver": "file",
3347#               "filename": "test.qcow2"
3348#           }
3349#      }
3350#    }
3351# <- { "return": {} }
3352#
3353# -> { "execute": "blockdev-del",
3354#      "arguments": { "node-name": "node0" }
3355#    }
3356# <- { "return": {} }
3357#
3358##
3359{ 'command': 'blockdev-del', 'data': { 'node-name': 'str' } }
3360
3361##
3362# @blockdev-open-tray:
3363#
3364# Opens a block device's tray. If there is a block driver state tree inserted as
3365# a medium, it will become inaccessible to the guest (but it will remain
3366# associated to the block device, so closing the tray will make it accessible
3367# again).
3368#
3369# If the tray was already open before, this will be a no-op.
3370#
3371# Once the tray opens, a DEVICE_TRAY_MOVED event is emitted. There are cases in
3372# which no such event will be generated, these include:
3373# - if the guest has locked the tray, @force is false and the guest does not
3374#   respond to the eject request
3375# - if the BlockBackend denoted by @device does not have a guest device attached
3376#   to it
3377# - if the guest device does not have an actual tray
3378#
3379# @device: Block device name (deprecated, use @id instead)
3380#
3381# @id:     The name or QOM path of the guest device (since: 2.8)
3382#
3383# @force:  if false (the default), an eject request will be sent to
3384#          the guest if it has locked the tray (and the tray will not be opened
3385#          immediately); if true, the tray will be opened regardless of whether
3386#          it is locked
3387#
3388# Since: 2.5
3389#
3390# Example:
3391#
3392# -> { "execute": "blockdev-open-tray",
3393#      "arguments": { "id": "ide0-1-0" } }
3394#
3395# <- { "timestamp": { "seconds": 1418751016,
3396#                     "microseconds": 716996 },
3397#      "event": "DEVICE_TRAY_MOVED",
3398#      "data": { "device": "ide1-cd0",
3399#                "id": "ide0-1-0",
3400#                "tray-open": true } }
3401#
3402# <- { "return": {} }
3403#
3404##
3405{ 'command': 'blockdev-open-tray',
3406  'data': { '*device': 'str',
3407            '*id': 'str',
3408            '*force': 'bool' } }
3409
3410##
3411# @blockdev-close-tray:
3412#
3413# Closes a block device's tray. If there is a block driver state tree associated
3414# with the block device (which is currently ejected), that tree will be loaded
3415# as the medium.
3416#
3417# If the tray was already closed before, this will be a no-op.
3418#
3419# @device:  Block device name (deprecated, use @id instead)
3420#
3421# @id:      The name or QOM path of the guest device (since: 2.8)
3422#
3423# Since: 2.5
3424#
3425# Example:
3426#
3427# -> { "execute": "blockdev-close-tray",
3428#      "arguments": { "id": "ide0-1-0" } }
3429#
3430# <- { "timestamp": { "seconds": 1418751345,
3431#                     "microseconds": 272147 },
3432#      "event": "DEVICE_TRAY_MOVED",
3433#      "data": { "device": "ide1-cd0",
3434#                "id": "ide0-1-0",
3435#                "tray-open": false } }
3436#
3437# <- { "return": {} }
3438#
3439##
3440{ 'command': 'blockdev-close-tray',
3441  'data': { '*device': 'str',
3442            '*id': 'str' } }
3443
3444##
3445# @blockdev-remove-medium:
3446#
3447# Removes a medium (a block driver state tree) from a block device. That block
3448# device's tray must currently be open (unless there is no attached guest
3449# device).
3450#
3451# If the tray is open and there is no medium inserted, this will be a no-op.
3452#
3453# @id:     The name or QOM path of the guest device
3454#
3455# Since: 2.12
3456#
3457# Example:
3458#
3459# -> { "execute": "blockdev-remove-medium",
3460#      "arguments": { "id": "ide0-1-0" } }
3461#
3462# <- { "error": { "class": "GenericError",
3463#                 "desc": "Tray of device 'ide0-1-0' is not open" } }
3464#
3465# -> { "execute": "blockdev-open-tray",
3466#      "arguments": { "id": "ide0-1-0" } }
3467#
3468# <- { "timestamp": { "seconds": 1418751627,
3469#                     "microseconds": 549958 },
3470#      "event": "DEVICE_TRAY_MOVED",
3471#      "data": { "device": "ide1-cd0",
3472#                "id": "ide0-1-0",
3473#                "tray-open": true } }
3474#
3475# <- { "return": {} }
3476#
3477# -> { "execute": "blockdev-remove-medium",
3478#      "arguments": { "id": "ide0-1-0" } }
3479#
3480# <- { "return": {} }
3481#
3482##
3483{ 'command': 'blockdev-remove-medium',
3484  'data': { 'id': 'str' } }
3485
3486##
3487# @blockdev-insert-medium:
3488#
3489# Inserts a medium (a block driver state tree) into a block device. That block
3490# device's tray must currently be open (unless there is no attached guest
3491# device) and there must be no medium inserted already.
3492#
3493# @id:        The name or QOM path of the guest device
3494#
3495# @node-name: name of a node in the block driver state graph
3496#
3497# Since: 2.12
3498#
3499# Example:
3500#
3501# -> { "execute": "blockdev-add",
3502#      "arguments": {
3503#          "node-name": "node0",
3504#          "driver": "raw",
3505#          "file": { "driver": "file",
3506#                    "filename": "fedora.iso" } } }
3507# <- { "return": {} }
3508#
3509# -> { "execute": "blockdev-insert-medium",
3510#      "arguments": { "id": "ide0-1-0",
3511#                     "node-name": "node0" } }
3512#
3513# <- { "return": {} }
3514#
3515##
3516{ 'command': 'blockdev-insert-medium',
3517  'data': { 'id': 'str',
3518            'node-name': 'str'} }
3519
3520
3521##
3522# @BlockdevChangeReadOnlyMode:
3523#
3524# Specifies the new read-only mode of a block device subject to the
3525# @blockdev-change-medium command.
3526#
3527# @retain:      Retains the current read-only mode
3528#
3529# @read-only:   Makes the device read-only
3530#
3531# @read-write:  Makes the device writable
3532#
3533# Since: 2.3
3534#
3535##
3536{ 'enum': 'BlockdevChangeReadOnlyMode',
3537  'data': ['retain', 'read-only', 'read-write'] }
3538
3539
3540##
3541# @blockdev-change-medium:
3542#
3543# Changes the medium inserted into a block device by ejecting the current medium
3544# and loading a new image file which is inserted as the new medium (this command
3545# combines blockdev-open-tray, blockdev-remove-medium, blockdev-insert-medium
3546# and blockdev-close-tray).
3547#
3548# @device:          Block device name (deprecated, use @id instead)
3549#
3550# @id:              The name or QOM path of the guest device
3551#                   (since: 2.8)
3552#
3553# @filename:        filename of the new image to be loaded
3554#
3555# @format:          format to open the new image with (defaults to
3556#                   the probed format)
3557#
3558# @read-only-mode:  change the read-only mode of the device; defaults
3559#                   to 'retain'
3560#
3561# Since: 2.5
3562#
3563# Examples:
3564#
3565# 1. Change a removable medium
3566#
3567# -> { "execute": "blockdev-change-medium",
3568#      "arguments": { "id": "ide0-1-0",
3569#                     "filename": "/srv/images/Fedora-12-x86_64-DVD.iso",
3570#                     "format": "raw" } }
3571# <- { "return": {} }
3572#
3573# 2. Load a read-only medium into a writable drive
3574#
3575# -> { "execute": "blockdev-change-medium",
3576#      "arguments": { "id": "floppyA",
3577#                     "filename": "/srv/images/ro.img",
3578#                     "format": "raw",
3579#                     "read-only-mode": "retain" } }
3580#
3581# <- { "error":
3582#      { "class": "GenericError",
3583#        "desc": "Could not open '/srv/images/ro.img': Permission denied" } }
3584#
3585# -> { "execute": "blockdev-change-medium",
3586#      "arguments": { "id": "floppyA",
3587#                     "filename": "/srv/images/ro.img",
3588#                     "format": "raw",
3589#                     "read-only-mode": "read-only" } }
3590#
3591# <- { "return": {} }
3592#
3593##
3594{ 'command': 'blockdev-change-medium',
3595  'data': { '*device': 'str',
3596            '*id': 'str',
3597            'filename': 'str',
3598            '*format': 'str',
3599            '*read-only-mode': 'BlockdevChangeReadOnlyMode' } }
3600
3601
3602##
3603# @BlockErrorAction:
3604#
3605# An enumeration of action that has been taken when a DISK I/O occurs
3606#
3607# @ignore: error has been ignored
3608#
3609# @report: error has been reported to the device
3610#
3611# @stop: error caused VM to be stopped
3612#
3613# Since: 2.1
3614##
3615{ 'enum': 'BlockErrorAction',
3616  'data': [ 'ignore', 'report', 'stop' ] }
3617
3618
3619##
3620# @BLOCK_IMAGE_CORRUPTED:
3621#
3622# Emitted when a disk image is being marked corrupt. The image can be
3623# identified by its device or node name. The 'device' field is always
3624# present for compatibility reasons, but it can be empty ("") if the
3625# image does not have a device name associated.
3626#
3627# @device: device name. This is always present for compatibility
3628#          reasons, but it can be empty ("") if the image does not
3629#          have a device name associated.
3630#
3631# @node-name: node name (Since: 2.4)
3632#
3633# @msg: informative message for human consumption, such as the kind of
3634#       corruption being detected. It should not be parsed by machine as it is
3635#       not guaranteed to be stable
3636#
3637# @offset: if the corruption resulted from an image access, this is
3638#          the host's access offset into the image
3639#
3640# @size: if the corruption resulted from an image access, this is
3641#        the access size
3642#
3643# @fatal: if set, the image is marked corrupt and therefore unusable after this
3644#        event and must be repaired (Since 2.2; before, every
3645#        BLOCK_IMAGE_CORRUPTED event was fatal)
3646#
3647# Note: If action is "stop", a STOP event will eventually follow the
3648#       BLOCK_IO_ERROR event.
3649#
3650# Example:
3651#
3652# <- { "event": "BLOCK_IMAGE_CORRUPTED",
3653#      "data": { "device": "ide0-hd0", "node-name": "node0",
3654#                "msg": "Prevented active L1 table overwrite", "offset": 196608,
3655#                "size": 65536 },
3656#      "timestamp": { "seconds": 1378126126, "microseconds": 966463 } }
3657#
3658# Since: 1.7
3659##
3660{ 'event': 'BLOCK_IMAGE_CORRUPTED',
3661  'data': { 'device'     : 'str',
3662            '*node-name' : 'str',
3663            'msg'        : 'str',
3664            '*offset'    : 'int',
3665            '*size'      : 'int',
3666            'fatal'      : 'bool' } }
3667
3668##
3669# @BLOCK_IO_ERROR:
3670#
3671# Emitted when a disk I/O error occurs
3672#
3673# @device: device name. This is always present for compatibility
3674#          reasons, but it can be empty ("") if the image does not
3675#          have a device name associated.
3676#
3677# @node-name: node name. Note that errors may be reported for the root node
3678#             that is directly attached to a guest device rather than for the
3679#             node where the error occurred. The node name is not present if
3680#             the drive is empty. (Since: 2.8)
3681#
3682# @operation: I/O operation
3683#
3684# @action: action that has been taken
3685#
3686# @nospace: true if I/O error was caused due to a no-space
3687#           condition. This key is only present if query-block's
3688#           io-status is present, please see query-block documentation
3689#           for more information (since: 2.2)
3690#
3691# @reason: human readable string describing the error cause.
3692#          (This field is a debugging aid for humans, it should not
3693#           be parsed by applications) (since: 2.2)
3694#
3695# Note: If action is "stop", a STOP event will eventually follow the
3696# BLOCK_IO_ERROR event
3697#
3698# Since: 0.13.0
3699#
3700# Example:
3701#
3702# <- { "event": "BLOCK_IO_ERROR",
3703#      "data": { "device": "ide0-hd1",
3704#                "node-name": "#block212",
3705#                "operation": "write",
3706#                "action": "stop" },
3707#      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
3708#
3709##
3710{ 'event': 'BLOCK_IO_ERROR',
3711  'data': { 'device': 'str', '*node-name': 'str',
3712            'operation': 'IoOperationType',
3713            'action': 'BlockErrorAction', '*nospace': 'bool',
3714            'reason': 'str' } }
3715
3716##
3717# @BLOCK_JOB_COMPLETED:
3718#
3719# Emitted when a block job has completed
3720#
3721# @type: job type
3722#
3723# @device: The job identifier. Originally the device name but other
3724#          values are allowed since QEMU 2.7
3725#
3726# @len: maximum progress value
3727#
3728# @offset: current progress value. On success this is equal to len.
3729#          On failure this is less than len
3730#
3731# @speed: rate limit, bytes per second
3732#
3733# @error: error message. Only present on failure. This field
3734#         contains a human-readable error message. There are no semantics
3735#         other than that streaming has failed and clients should not try to
3736#         interpret the error string
3737#
3738# Since: 1.1
3739#
3740# Example:
3741#
3742# <- { "event": "BLOCK_JOB_COMPLETED",
3743#      "data": { "type": "stream", "device": "virtio-disk0",
3744#                "len": 10737418240, "offset": 10737418240,
3745#                "speed": 0 },
3746#      "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
3747#
3748##
3749{ 'event': 'BLOCK_JOB_COMPLETED',
3750  'data': { 'type'  : 'BlockJobType',
3751            'device': 'str',
3752            'len'   : 'int',
3753            'offset': 'int',
3754            'speed' : 'int',
3755            '*error': 'str' } }
3756
3757##
3758# @BLOCK_JOB_CANCELLED:
3759#
3760# Emitted when a block job has been cancelled
3761#
3762# @type: job type
3763#
3764# @device: The job identifier. Originally the device name but other
3765#          values are allowed since QEMU 2.7
3766#
3767# @len: maximum progress value
3768#
3769# @offset: current progress value. On success this is equal to len.
3770#          On failure this is less than len
3771#
3772# @speed: rate limit, bytes per second
3773#
3774# Since: 1.1
3775#
3776# Example:
3777#
3778# <- { "event": "BLOCK_JOB_CANCELLED",
3779#      "data": { "type": "stream", "device": "virtio-disk0",
3780#                "len": 10737418240, "offset": 134217728,
3781#                "speed": 0 },
3782#      "timestamp": { "seconds": 1267061043, "microseconds": 959568 } }
3783#
3784##
3785{ 'event': 'BLOCK_JOB_CANCELLED',
3786  'data': { 'type'  : 'BlockJobType',
3787            'device': 'str',
3788            'len'   : 'int',
3789            'offset': 'int',
3790            'speed' : 'int' } }
3791
3792##
3793# @BLOCK_JOB_ERROR:
3794#
3795# Emitted when a block job encounters an error
3796#
3797# @device: The job identifier. Originally the device name but other
3798#          values are allowed since QEMU 2.7
3799#
3800# @operation: I/O operation
3801#
3802# @action: action that has been taken
3803#
3804# Since: 1.3
3805#
3806# Example:
3807#
3808# <- { "event": "BLOCK_JOB_ERROR",
3809#      "data": { "device": "ide0-hd1",
3810#                "operation": "write",
3811#                "action": "stop" },
3812#      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
3813#
3814##
3815{ 'event': 'BLOCK_JOB_ERROR',
3816  'data': { 'device'   : 'str',
3817            'operation': 'IoOperationType',
3818            'action'   : 'BlockErrorAction' } }
3819
3820##
3821# @BLOCK_JOB_READY:
3822#
3823# Emitted when a block job is ready to complete
3824#
3825# @type: job type
3826#
3827# @device: The job identifier. Originally the device name but other
3828#          values are allowed since QEMU 2.7
3829#
3830# @len: maximum progress value
3831#
3832# @offset: current progress value. On success this is equal to len.
3833#          On failure this is less than len
3834#
3835# @speed: rate limit, bytes per second
3836#
3837# Note: The "ready to complete" status is always reset by a @BLOCK_JOB_ERROR
3838# event
3839#
3840# Since: 1.3
3841#
3842# Example:
3843#
3844# <- { "event": "BLOCK_JOB_READY",
3845#      "data": { "device": "drive0", "type": "mirror", "speed": 0,
3846#                "len": 2097152, "offset": 2097152 }
3847#      "timestamp": { "seconds": 1265044230, "microseconds": 450486 } }
3848#
3849##
3850{ 'event': 'BLOCK_JOB_READY',
3851  'data': { 'type'  : 'BlockJobType',
3852            'device': 'str',
3853            'len'   : 'int',
3854            'offset': 'int',
3855            'speed' : 'int' } }
3856
3857##
3858# @PreallocMode:
3859#
3860# Preallocation mode of QEMU image file
3861#
3862# @off: no preallocation
3863# @metadata: preallocate only for metadata
3864# @falloc: like @full preallocation but allocate disk space by
3865#          posix_fallocate() rather than writing zeros.
3866# @full: preallocate all data by writing zeros to device to ensure disk
3867#        space is really available. @full preallocation also sets up
3868#        metadata correctly.
3869#
3870# Since: 2.2
3871##
3872{ 'enum': 'PreallocMode',
3873  'data': [ 'off', 'metadata', 'falloc', 'full' ] }
3874
3875##
3876# @BLOCK_WRITE_THRESHOLD:
3877#
3878# Emitted when writes on block device reaches or exceeds the
3879# configured write threshold. For thin-provisioned devices, this
3880# means the device should be extended to avoid pausing for
3881# disk exhaustion.
3882# The event is one shot. Once triggered, it needs to be
3883# re-registered with another block-set-write-threshold command.
3884#
3885# @node-name: graph node name on which the threshold was exceeded.
3886#
3887# @amount-exceeded: amount of data which exceeded the threshold, in bytes.
3888#
3889# @write-threshold: last configured threshold, in bytes.
3890#
3891# Since: 2.3
3892##
3893{ 'event': 'BLOCK_WRITE_THRESHOLD',
3894  'data': { 'node-name': 'str',
3895            'amount-exceeded': 'uint64',
3896            'write-threshold': 'uint64' } }
3897
3898##
3899# @block-set-write-threshold:
3900#
3901# Change the write threshold for a block drive. An event will be
3902# delivered if a write to this block drive crosses the configured
3903# threshold.  The threshold is an offset, thus must be
3904# non-negative. Default is no write threshold. Setting the threshold
3905# to zero disables it.
3906#
3907# This is useful to transparently resize thin-provisioned drives without
3908# the guest OS noticing.
3909#
3910# @node-name: graph node name on which the threshold must be set.
3911#
3912# @write-threshold: configured threshold for the block device, bytes.
3913#                   Use 0 to disable the threshold.
3914#
3915# Since: 2.3
3916#
3917# Example:
3918#
3919# -> { "execute": "block-set-write-threshold",
3920#      "arguments": { "node-name": "mydev",
3921#                     "write-threshold": 17179869184 } }
3922# <- { "return": {} }
3923#
3924##
3925{ 'command': 'block-set-write-threshold',
3926  'data': { 'node-name': 'str', 'write-threshold': 'uint64' } }
3927
3928##
3929# @x-blockdev-change:
3930#
3931# Dynamically reconfigure the block driver state graph. It can be used
3932# to add, remove, insert or replace a graph node. Currently only the
3933# Quorum driver implements this feature to add or remove its child. This
3934# is useful to fix a broken quorum child.
3935#
3936# If @node is specified, it will be inserted under @parent. @child
3937# may not be specified in this case. If both @parent and @child are
3938# specified but @node is not, @child will be detached from @parent.
3939#
3940# @parent: the id or name of the parent node.
3941#
3942# @child: the name of a child under the given parent node.
3943#
3944# @node: the name of the node that will be added.
3945#
3946# Note: this command is experimental, and its API is not stable. It
3947# does not support all kinds of operations, all kinds of children, nor
3948# all block drivers.
3949#
3950# FIXME Removing children from a quorum node means introducing gaps in the
3951# child indices. This cannot be represented in the 'children' list of
3952# BlockdevOptionsQuorum, as returned by .bdrv_refresh_filename().
3953#
3954# Warning: The data in a new quorum child MUST be consistent with that of
3955# the rest of the array.
3956#
3957# Since: 2.7
3958#
3959# Example:
3960#
3961# 1. Add a new node to a quorum
3962# -> { "execute": "blockdev-add",
3963#      "arguments": {
3964#          "driver": "raw",
3965#          "node-name": "new_node",
3966#          "file": { "driver": "file",
3967#                    "filename": "test.raw" } } }
3968# <- { "return": {} }
3969# -> { "execute": "x-blockdev-change",
3970#      "arguments": { "parent": "disk1",
3971#                     "node": "new_node" } }
3972# <- { "return": {} }
3973#
3974# 2. Delete a quorum's node
3975# -> { "execute": "x-blockdev-change",
3976#      "arguments": { "parent": "disk1",
3977#                     "child": "children.1" } }
3978# <- { "return": {} }
3979#
3980##
3981{ 'command': 'x-blockdev-change',
3982  'data' : { 'parent': 'str',
3983             '*child': 'str',
3984             '*node': 'str' } }
3985
3986##
3987# @x-blockdev-set-iothread:
3988#
3989# Move @node and its children into the @iothread.  If @iothread is null then
3990# move @node and its children into the main loop.
3991#
3992# The node must not be attached to a BlockBackend.
3993#
3994# @node-name: the name of the block driver node
3995#
3996# @iothread: the name of the IOThread object or null for the main loop
3997#
3998# @force: true if the node and its children should be moved when a BlockBackend
3999#         is already attached
4000#
4001# Note: this command is experimental and intended for test cases that need
4002# control over IOThreads only.
4003#
4004# Since: 2.12
4005#
4006# Example:
4007#
4008# 1. Move a node into an IOThread
4009# -> { "execute": "x-blockdev-set-iothread",
4010#      "arguments": { "node-name": "disk1",
4011#                     "iothread": "iothread0" } }
4012# <- { "return": {} }
4013#
4014# 2. Move a node into the main loop
4015# -> { "execute": "x-blockdev-set-iothread",
4016#      "arguments": { "node-name": "disk1",
4017#                     "iothread": null } }
4018# <- { "return": {} }
4019#
4020##
4021{ 'command': 'x-blockdev-set-iothread',
4022  'data' : { 'node-name': 'str',
4023             'iothread': 'StrOrNull',
4024             '*force': 'bool' } }
4025