]> git.proxmox.com Git - mirror_qemu.git/blob - qapi/block-core.json
qapi: Correct the name of the iops_rd parameter
[mirror_qemu.git] / qapi / block-core.json
1 # -*- Mode: Python -*-
2 #
3 # QAPI block core definitions (vm unrelated)
4
5 # QAPI common definitions
6 { 'include': 'common.json' }
7
8 ##
9 # @SnapshotInfo
10 #
11 # @id: unique snapshot id
12 #
13 # @name: user chosen name
14 #
15 # @vm-state-size: size of the VM state
16 #
17 # @date-sec: UTC date of the snapshot in seconds
18 #
19 # @date-nsec: fractional part in nano seconds to be used with date-sec
20 #
21 # @vm-clock-sec: VM clock relative to boot in seconds
22 #
23 # @vm-clock-nsec: fractional part in nano seconds to be used with vm-clock-sec
24 #
25 # Since: 1.3
26 #
27 ##
28
29 { 'struct': 'SnapshotInfo',
30 'data': { 'id': 'str', 'name': 'str', 'vm-state-size': 'int',
31 'date-sec': 'int', 'date-nsec': 'int',
32 'vm-clock-sec': 'int', 'vm-clock-nsec': 'int' } }
33
34 ##
35 # @ImageInfoSpecificQCow2:
36 #
37 # @compat: compatibility level
38 #
39 # @lazy-refcounts: #optional on or off; only valid for compat >= 1.1
40 #
41 # @corrupt: #optional true if the image has been marked corrupt; only valid for
42 # compat >= 1.1 (since 2.2)
43 #
44 # @refcount-bits: width of a refcount entry in bits (since 2.3)
45 #
46 # Since: 1.7
47 ##
48 { 'struct': 'ImageInfoSpecificQCow2',
49 'data': {
50 'compat': 'str',
51 '*lazy-refcounts': 'bool',
52 '*corrupt': 'bool',
53 'refcount-bits': 'int'
54 } }
55
56 ##
57 # @ImageInfoSpecificVmdk:
58 #
59 # @create-type: The create type of VMDK image
60 #
61 # @cid: Content id of image
62 #
63 # @parent-cid: Parent VMDK image's cid
64 #
65 # @extents: List of extent files
66 #
67 # Since: 1.7
68 ##
69 { 'struct': 'ImageInfoSpecificVmdk',
70 'data': {
71 'create-type': 'str',
72 'cid': 'int',
73 'parent-cid': 'int',
74 'extents': ['ImageInfo']
75 } }
76
77 ##
78 # @ImageInfoSpecific:
79 #
80 # A discriminated record of image format specific information structures.
81 #
82 # Since: 1.7
83 ##
84
85 { 'union': 'ImageInfoSpecific',
86 'data': {
87 'qcow2': 'ImageInfoSpecificQCow2',
88 'vmdk': 'ImageInfoSpecificVmdk'
89 } }
90
91 ##
92 # @ImageInfo:
93 #
94 # Information about a QEMU image file
95 #
96 # @filename: name of the image file
97 #
98 # @format: format of the image file
99 #
100 # @virtual-size: maximum capacity in bytes of the image
101 #
102 # @actual-size: #optional actual size on disk in bytes of the image
103 #
104 # @dirty-flag: #optional true if image is not cleanly closed
105 #
106 # @cluster-size: #optional size of a cluster in bytes
107 #
108 # @encrypted: #optional true if the image is encrypted
109 #
110 # @compressed: #optional true if the image is compressed (Since 1.7)
111 #
112 # @backing-filename: #optional name of the backing file
113 #
114 # @full-backing-filename: #optional full path of the backing file
115 #
116 # @backing-filename-format: #optional the format of the backing file
117 #
118 # @snapshots: #optional list of VM snapshots
119 #
120 # @backing-image: #optional info of the backing image (since 1.6)
121 #
122 # @format-specific: #optional structure supplying additional format-specific
123 # information (since 1.7)
124 #
125 # Since: 1.3
126 #
127 ##
128
129 { 'struct': 'ImageInfo',
130 'data': {'filename': 'str', 'format': 'str', '*dirty-flag': 'bool',
131 '*actual-size': 'int', 'virtual-size': 'int',
132 '*cluster-size': 'int', '*encrypted': 'bool', '*compressed': 'bool',
133 '*backing-filename': 'str', '*full-backing-filename': 'str',
134 '*backing-filename-format': 'str', '*snapshots': ['SnapshotInfo'],
135 '*backing-image': 'ImageInfo',
136 '*format-specific': 'ImageInfoSpecific' } }
137
138 ##
139 # @ImageCheck:
140 #
141 # Information about a QEMU image file check
142 #
143 # @filename: name of the image file checked
144 #
145 # @format: format of the image file checked
146 #
147 # @check-errors: number of unexpected errors occurred during check
148 #
149 # @image-end-offset: #optional offset (in bytes) where the image ends, this
150 # field is present if the driver for the image format
151 # supports it
152 #
153 # @corruptions: #optional number of corruptions found during the check if any
154 #
155 # @leaks: #optional number of leaks found during the check if any
156 #
157 # @corruptions-fixed: #optional number of corruptions fixed during the check
158 # if any
159 #
160 # @leaks-fixed: #optional number of leaks fixed during the check if any
161 #
162 # @total-clusters: #optional total number of clusters, this field is present
163 # if the driver for the image format supports it
164 #
165 # @allocated-clusters: #optional total number of allocated clusters, this
166 # field is present if the driver for the image format
167 # supports it
168 #
169 # @fragmented-clusters: #optional total number of fragmented clusters, this
170 # field is present if the driver for the image format
171 # supports it
172 #
173 # @compressed-clusters: #optional total number of compressed clusters, this
174 # field is present if the driver for the image format
175 # supports it
176 #
177 # Since: 1.4
178 #
179 ##
180
181 { 'struct': 'ImageCheck',
182 'data': {'filename': 'str', 'format': 'str', 'check-errors': 'int',
183 '*image-end-offset': 'int', '*corruptions': 'int', '*leaks': 'int',
184 '*corruptions-fixed': 'int', '*leaks-fixed': 'int',
185 '*total-clusters': 'int', '*allocated-clusters': 'int',
186 '*fragmented-clusters': 'int', '*compressed-clusters': 'int' } }
187
188 ##
189 # @MapEntry:
190 #
191 # Mapping information from a virtual block range to a host file range
192 #
193 # @start: the start byte of the mapped virtual range
194 #
195 # @length: the number of bytes of the mapped virtual range
196 #
197 # @data: whether the mapped range has data
198 #
199 # @zero: whether the virtual blocks are zeroed
200 #
201 # @depth: the depth of the mapping
202 #
203 # @offset: #optional the offset in file that the virtual sectors are mapped to
204 #
205 # @filename: #optional filename that is referred to by @offset
206 #
207 # Since: 2.6
208 #
209 ##
210 { 'struct': 'MapEntry',
211 'data': {'start': 'int', 'length': 'int', 'data': 'bool',
212 'zero': 'bool', 'depth': 'int', '*offset': 'int',
213 '*filename': 'str' } }
214
215 ##
216 # @BlockdevCacheInfo
217 #
218 # Cache mode information for a block device
219 #
220 # @writeback: true if writeback mode is enabled
221 # @direct: true if the host page cache is bypassed (O_DIRECT)
222 # @no-flush: true if flush requests are ignored for the device
223 #
224 # Since: 2.3
225 ##
226 { 'struct': 'BlockdevCacheInfo',
227 'data': { 'writeback': 'bool',
228 'direct': 'bool',
229 'no-flush': 'bool' } }
230
231 ##
232 # @BlockDeviceInfo:
233 #
234 # Information about the backing device for a block device.
235 #
236 # @file: the filename of the backing device
237 #
238 # @node-name: #optional the name of the block driver node (Since 2.0)
239 #
240 # @ro: true if the backing device was open read-only
241 #
242 # @drv: the name of the block format used to open the backing device. As of
243 # 0.14.0 this can be: 'blkdebug', 'bochs', 'cloop', 'cow', 'dmg',
244 # 'file', 'file', 'ftp', 'ftps', 'host_cdrom', 'host_device',
245 # 'http', 'https', 'nbd', 'parallels', 'qcow',
246 # 'qcow2', 'raw', 'tftp', 'vdi', 'vmdk', 'vpc', 'vvfat'
247 # 2.2: 'archipelago' added, 'cow' dropped
248 # 2.3: 'host_floppy' deprecated
249 # 2.5: 'host_floppy' dropped
250 #
251 # @backing_file: #optional the name of the backing file (for copy-on-write)
252 #
253 # @backing_file_depth: number of files in the backing file chain (since: 1.2)
254 #
255 # @encrypted: true if the backing device is encrypted
256 #
257 # @encryption_key_missing: true if the backing device is encrypted but an
258 # valid encryption key is missing
259 #
260 # @detect_zeroes: detect and optimize zero writes (Since 2.1)
261 #
262 # @bps: total throughput limit in bytes per second is specified
263 #
264 # @bps_rd: read throughput limit in bytes per second is specified
265 #
266 # @bps_wr: write throughput limit in bytes per second is specified
267 #
268 # @iops: total I/O operations per second is specified
269 #
270 # @iops_rd: read I/O operations per second is specified
271 #
272 # @iops_wr: write I/O operations per second is specified
273 #
274 # @image: the info of image used (since: 1.6)
275 #
276 # @bps_max: #optional total throughput limit during bursts,
277 # in bytes (Since 1.7)
278 #
279 # @bps_rd_max: #optional read throughput limit during bursts,
280 # in bytes (Since 1.7)
281 #
282 # @bps_wr_max: #optional write throughput limit during bursts,
283 # in bytes (Since 1.7)
284 #
285 # @iops_max: #optional total I/O operations per second during bursts,
286 # in bytes (Since 1.7)
287 #
288 # @iops_rd_max: #optional read I/O operations per second during bursts,
289 # in bytes (Since 1.7)
290 #
291 # @iops_wr_max: #optional write I/O operations per second during bursts,
292 # in bytes (Since 1.7)
293 #
294 # @bps_max_length: #optional maximum length of the @bps_max burst
295 # period, in seconds. (Since 2.6)
296 #
297 # @bps_rd_max_length: #optional maximum length of the @bps_rd_max
298 # burst period, in seconds. (Since 2.6)
299 #
300 # @bps_wr_max_length: #optional maximum length of the @bps_wr_max
301 # burst period, in seconds. (Since 2.6)
302 #
303 # @iops_max_length: #optional maximum length of the @iops burst
304 # period, in seconds. (Since 2.6)
305 #
306 # @iops_rd_max_length: #optional maximum length of the @iops_rd_max
307 # burst period, in seconds. (Since 2.6)
308 #
309 # @iops_wr_max_length: #optional maximum length of the @iops_wr_max
310 # burst period, in seconds. (Since 2.6)
311 #
312 # @iops_size: #optional an I/O size in bytes (Since 1.7)
313 #
314 # @group: #optional throttle group name (Since 2.4)
315 #
316 # @cache: the cache mode used for the block device (since: 2.3)
317 #
318 # @write_threshold: configured write threshold for the device.
319 # 0 if disabled. (Since 2.3)
320 #
321 # Since: 0.14.0
322 #
323 ##
324 { 'struct': 'BlockDeviceInfo',
325 'data': { 'file': 'str', '*node-name': 'str', 'ro': 'bool', 'drv': 'str',
326 '*backing_file': 'str', 'backing_file_depth': 'int',
327 'encrypted': 'bool', 'encryption_key_missing': 'bool',
328 'detect_zeroes': 'BlockdevDetectZeroesOptions',
329 'bps': 'int', 'bps_rd': 'int', 'bps_wr': 'int',
330 'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
331 'image': 'ImageInfo',
332 '*bps_max': 'int', '*bps_rd_max': 'int',
333 '*bps_wr_max': 'int', '*iops_max': 'int',
334 '*iops_rd_max': 'int', '*iops_wr_max': 'int',
335 '*bps_max_length': 'int', '*bps_rd_max_length': 'int',
336 '*bps_wr_max_length': 'int', '*iops_max_length': 'int',
337 '*iops_rd_max_length': 'int', '*iops_wr_max_length': 'int',
338 '*iops_size': 'int', '*group': 'str', 'cache': 'BlockdevCacheInfo',
339 'write_threshold': 'int' } }
340
341 ##
342 # @BlockDeviceIoStatus:
343 #
344 # An enumeration of block device I/O status.
345 #
346 # @ok: The last I/O operation has succeeded
347 #
348 # @failed: The last I/O operation has failed
349 #
350 # @nospace: The last I/O operation has failed due to a no-space condition
351 #
352 # Since: 1.0
353 ##
354 { 'enum': 'BlockDeviceIoStatus', 'data': [ 'ok', 'failed', 'nospace' ] }
355
356 ##
357 # @BlockDeviceMapEntry:
358 #
359 # Entry in the metadata map of the device (returned by "qemu-img map")
360 #
361 # @start: Offset in the image of the first byte described by this entry
362 # (in bytes)
363 #
364 # @length: Length of the range described by this entry (in bytes)
365 #
366 # @depth: Number of layers (0 = top image, 1 = top image's backing file, etc.)
367 # before reaching one for which the range is allocated. The value is
368 # in the range 0 to the depth of the image chain - 1.
369 #
370 # @zero: the sectors in this range read as zeros
371 #
372 # @data: reading the image will actually read data from a file (in particular,
373 # if @offset is present this means that the sectors are not simply
374 # preallocated, but contain actual data in raw format)
375 #
376 # @offset: if present, the image file stores the data for this range in
377 # raw format at the given offset.
378 #
379 # Since 1.7
380 ##
381 { 'struct': 'BlockDeviceMapEntry',
382 'data': { 'start': 'int', 'length': 'int', 'depth': 'int', 'zero': 'bool',
383 'data': 'bool', '*offset': 'int' } }
384
385 ##
386 # @DirtyBitmapStatus:
387 #
388 # An enumeration of possible states that a dirty bitmap can report to the user.
389 #
390 # @frozen: The bitmap is currently in-use by a backup operation or block job,
391 # and is immutable.
392 #
393 # @disabled: The bitmap is currently in-use by an internal operation and is
394 # read-only. It can still be deleted.
395 #
396 # @active: The bitmap is actively monitoring for new writes, and can be cleared,
397 # deleted, or used for backup operations.
398 #
399 # Since: 2.4
400 ##
401 { 'enum': 'DirtyBitmapStatus',
402 'data': ['active', 'disabled', 'frozen'] }
403
404 ##
405 # @BlockDirtyInfo:
406 #
407 # Block dirty bitmap information.
408 #
409 # @name: #optional the name of the dirty bitmap (Since 2.4)
410 #
411 # @count: number of dirty bytes according to the dirty bitmap
412 #
413 # @granularity: granularity of the dirty bitmap in bytes (since 1.4)
414 #
415 # @status: current status of the dirty bitmap (since 2.4)
416 #
417 # Since: 1.3
418 ##
419 { 'struct': 'BlockDirtyInfo',
420 'data': {'*name': 'str', 'count': 'int', 'granularity': 'uint32',
421 'status': 'DirtyBitmapStatus'} }
422
423 ##
424 # @BlockInfo:
425 #
426 # Block device information. This structure describes a virtual device and
427 # the backing device associated with it.
428 #
429 # @device: The device name associated with the virtual device.
430 #
431 # @type: This field is returned only for compatibility reasons, it should
432 # not be used (always returns 'unknown')
433 #
434 # @removable: True if the device supports removable media.
435 #
436 # @locked: True if the guest has locked this device from having its media
437 # removed
438 #
439 # @tray_open: #optional True if the device's tray is open
440 # (only present if it has a tray)
441 #
442 # @dirty-bitmaps: #optional dirty bitmaps information (only present if the
443 # driver has one or more dirty bitmaps) (Since 2.0)
444 #
445 # @io-status: #optional @BlockDeviceIoStatus. Only present if the device
446 # supports it and the VM is configured to stop on errors
447 # (supported device models: virtio-blk, ide, scsi-disk)
448 #
449 # @inserted: #optional @BlockDeviceInfo describing the device if media is
450 # present
451 #
452 # Since: 0.14.0
453 ##
454 { 'struct': 'BlockInfo',
455 'data': {'device': 'str', 'type': 'str', 'removable': 'bool',
456 'locked': 'bool', '*inserted': 'BlockDeviceInfo',
457 '*tray_open': 'bool', '*io-status': 'BlockDeviceIoStatus',
458 '*dirty-bitmaps': ['BlockDirtyInfo'] } }
459
460 ##
461 # @query-block:
462 #
463 # Get a list of BlockInfo for all virtual block devices.
464 #
465 # Returns: a list of @BlockInfo describing each virtual block device
466 #
467 # Since: 0.14.0
468 ##
469 { 'command': 'query-block', 'returns': ['BlockInfo'] }
470
471
472 ##
473 # @BlockDeviceTimedStats:
474 #
475 # Statistics of a block device during a given interval of time.
476 #
477 # @interval_length: Interval used for calculating the statistics,
478 # in seconds.
479 #
480 # @min_rd_latency_ns: Minimum latency of read operations in the
481 # defined interval, in nanoseconds.
482 #
483 # @min_wr_latency_ns: Minimum latency of write operations in the
484 # defined interval, in nanoseconds.
485 #
486 # @min_flush_latency_ns: Minimum latency of flush operations in the
487 # defined interval, in nanoseconds.
488 #
489 # @max_rd_latency_ns: Maximum latency of read operations in the
490 # defined interval, in nanoseconds.
491 #
492 # @max_wr_latency_ns: Maximum latency of write operations in the
493 # defined interval, in nanoseconds.
494 #
495 # @max_flush_latency_ns: Maximum latency of flush operations in the
496 # defined interval, in nanoseconds.
497 #
498 # @avg_rd_latency_ns: Average latency of read operations in the
499 # defined interval, in nanoseconds.
500 #
501 # @avg_wr_latency_ns: Average latency of write operations in the
502 # defined interval, in nanoseconds.
503 #
504 # @avg_flush_latency_ns: Average latency of flush operations in the
505 # defined interval, in nanoseconds.
506 #
507 # @avg_rd_queue_depth: Average number of pending read operations
508 # in the defined interval.
509 #
510 # @avg_wr_queue_depth: Average number of pending write operations
511 # in the defined interval.
512 #
513 # Since: 2.5
514 ##
515
516 { 'struct': 'BlockDeviceTimedStats',
517 'data': { 'interval_length': 'int', 'min_rd_latency_ns': 'int',
518 'max_rd_latency_ns': 'int', 'avg_rd_latency_ns': 'int',
519 'min_wr_latency_ns': 'int', 'max_wr_latency_ns': 'int',
520 'avg_wr_latency_ns': 'int', 'min_flush_latency_ns': 'int',
521 'max_flush_latency_ns': 'int', 'avg_flush_latency_ns': 'int',
522 'avg_rd_queue_depth': 'number', 'avg_wr_queue_depth': 'number' } }
523
524 ##
525 # @BlockDeviceStats:
526 #
527 # Statistics of a virtual block device or a block backing device.
528 #
529 # @rd_bytes: The number of bytes read by the device.
530 #
531 # @wr_bytes: The number of bytes written by the device.
532 #
533 # @rd_operations: The number of read operations performed by the device.
534 #
535 # @wr_operations: The number of write operations performed by the device.
536 #
537 # @flush_operations: The number of cache flush operations performed by the
538 # device (since 0.15.0)
539 #
540 # @flush_total_time_ns: Total time spend on cache flushes in nano-seconds
541 # (since 0.15.0).
542 #
543 # @wr_total_time_ns: Total time spend on writes in nano-seconds (since 0.15.0).
544 #
545 # @rd_total_time_ns: Total_time_spend on reads in nano-seconds (since 0.15.0).
546 #
547 # @wr_highest_offset: The offset after the greatest byte written to the
548 # device. The intended use of this information is for
549 # growable sparse files (like qcow2) that are used on top
550 # of a physical device.
551 #
552 # @rd_merged: Number of read requests that have been merged into another
553 # request (Since 2.3).
554 #
555 # @wr_merged: Number of write requests that have been merged into another
556 # request (Since 2.3).
557 #
558 # @idle_time_ns: #optional Time since the last I/O operation, in
559 # nanoseconds. If the field is absent it means that
560 # there haven't been any operations yet (Since 2.5).
561 #
562 # @failed_rd_operations: The number of failed read operations
563 # performed by the device (Since 2.5)
564 #
565 # @failed_wr_operations: The number of failed write operations
566 # performed by the device (Since 2.5)
567 #
568 # @failed_flush_operations: The number of failed flush operations
569 # performed by the device (Since 2.5)
570 #
571 # @invalid_rd_operations: The number of invalid read operations
572 # performed by the device (Since 2.5)
573 #
574 # @invalid_wr_operations: The number of invalid write operations
575 # performed by the device (Since 2.5)
576 #
577 # @invalid_flush_operations: The number of invalid flush operations
578 # performed by the device (Since 2.5)
579 #
580 # @account_invalid: Whether invalid operations are included in the
581 # last access statistics (Since 2.5)
582 #
583 # @account_failed: Whether failed operations are included in the
584 # latency and last access statistics (Since 2.5)
585 #
586 # @timed_stats: Statistics specific to the set of previously defined
587 # intervals of time (Since 2.5)
588 #
589 # Since: 0.14.0
590 ##
591 { 'struct': 'BlockDeviceStats',
592 'data': {'rd_bytes': 'int', 'wr_bytes': 'int', 'rd_operations': 'int',
593 'wr_operations': 'int', 'flush_operations': 'int',
594 'flush_total_time_ns': 'int', 'wr_total_time_ns': 'int',
595 'rd_total_time_ns': 'int', 'wr_highest_offset': 'int',
596 'rd_merged': 'int', 'wr_merged': 'int', '*idle_time_ns': 'int',
597 'failed_rd_operations': 'int', 'failed_wr_operations': 'int',
598 'failed_flush_operations': 'int', 'invalid_rd_operations': 'int',
599 'invalid_wr_operations': 'int', 'invalid_flush_operations': 'int',
600 'account_invalid': 'bool', 'account_failed': 'bool',
601 'timed_stats': ['BlockDeviceTimedStats'] } }
602
603 ##
604 # @BlockStats:
605 #
606 # Statistics of a virtual block device or a block backing device.
607 #
608 # @device: #optional If the stats are for a virtual block device, the name
609 # corresponding to the virtual block device.
610 #
611 # @node-name: #optional The node name of the device. (Since 2.3)
612 #
613 # @stats: A @BlockDeviceStats for the device.
614 #
615 # @parent: #optional This describes the file block device if it has one.
616 #
617 # @backing: #optional This describes the backing block device if it has one.
618 # (Since 2.0)
619 #
620 # Since: 0.14.0
621 ##
622 { 'struct': 'BlockStats',
623 'data': {'*device': 'str', '*node-name': 'str',
624 'stats': 'BlockDeviceStats',
625 '*parent': 'BlockStats',
626 '*backing': 'BlockStats'} }
627
628 ##
629 # @query-blockstats:
630 #
631 # Query the @BlockStats for all virtual block devices.
632 #
633 # @query-nodes: #optional If true, the command will query all the block nodes
634 # that have a node name, in a list which will include "parent"
635 # information, but not "backing".
636 # If false or omitted, the behavior is as before - query all the
637 # device backends, recursively including their "parent" and
638 # "backing". (Since 2.3)
639 #
640 # Returns: A list of @BlockStats for each virtual block devices.
641 #
642 # Since: 0.14.0
643 ##
644 { 'command': 'query-blockstats',
645 'data': { '*query-nodes': 'bool' },
646 'returns': ['BlockStats'] }
647
648 ##
649 # @BlockdevOnError:
650 #
651 # An enumeration of possible behaviors for errors on I/O operations.
652 # The exact meaning depends on whether the I/O was initiated by a guest
653 # or by a block job
654 #
655 # @report: for guest operations, report the error to the guest;
656 # for jobs, cancel the job
657 #
658 # @ignore: ignore the error, only report a QMP event (BLOCK_IO_ERROR
659 # or BLOCK_JOB_ERROR)
660 #
661 # @enospc: same as @stop on ENOSPC, same as @report otherwise.
662 #
663 # @stop: for guest operations, stop the virtual machine;
664 # for jobs, pause the job
665 #
666 # Since: 1.3
667 ##
668 { 'enum': 'BlockdevOnError',
669 'data': ['report', 'ignore', 'enospc', 'stop'] }
670
671 ##
672 # @MirrorSyncMode:
673 #
674 # An enumeration of possible behaviors for the initial synchronization
675 # phase of storage mirroring.
676 #
677 # @top: copies data in the topmost image to the destination
678 #
679 # @full: copies data from all images to the destination
680 #
681 # @none: only copy data written from now on
682 #
683 # @incremental: only copy data described by the dirty bitmap. Since: 2.4
684 #
685 # Since: 1.3
686 ##
687 { 'enum': 'MirrorSyncMode',
688 'data': ['top', 'full', 'none', 'incremental'] }
689
690 ##
691 # @BlockJobType:
692 #
693 # Type of a block job.
694 #
695 # @commit: block commit job type, see "block-commit"
696 #
697 # @stream: block stream job type, see "block-stream"
698 #
699 # @mirror: drive mirror job type, see "drive-mirror"
700 #
701 # @backup: drive backup job type, see "drive-backup"
702 #
703 # Since: 1.7
704 ##
705 { 'enum': 'BlockJobType',
706 'data': ['commit', 'stream', 'mirror', 'backup'] }
707
708 ##
709 # @BlockJobInfo:
710 #
711 # Information about a long-running block device operation.
712 #
713 # @type: the job type ('stream' for image streaming)
714 #
715 # @device: the block device name
716 #
717 # @len: the maximum progress value
718 #
719 # @busy: false if the job is known to be in a quiescent state, with
720 # no pending I/O. Since 1.3.
721 #
722 # @paused: whether the job is paused or, if @busy is true, will
723 # pause itself as soon as possible. Since 1.3.
724 #
725 # @offset: the current progress value
726 #
727 # @speed: the rate limit, bytes per second
728 #
729 # @io-status: the status of the job (since 1.3)
730 #
731 # @ready: true if the job may be completed (since 2.2)
732 #
733 # Since: 1.1
734 ##
735 { 'struct': 'BlockJobInfo',
736 'data': {'type': 'str', 'device': 'str', 'len': 'int',
737 'offset': 'int', 'busy': 'bool', 'paused': 'bool', 'speed': 'int',
738 'io-status': 'BlockDeviceIoStatus', 'ready': 'bool'} }
739
740 ##
741 # @query-block-jobs:
742 #
743 # Return information about long-running block device operations.
744 #
745 # Returns: a list of @BlockJobInfo for each active block job
746 #
747 # Since: 1.1
748 ##
749 { 'command': 'query-block-jobs', 'returns': ['BlockJobInfo'] }
750
751 ##
752 # @block_passwd:
753 #
754 # This command sets the password of a block device that has not been open
755 # with a password and requires one.
756 #
757 # The two cases where this can happen are a block device is created through
758 # QEMU's initial command line or a block device is changed through the legacy
759 # @change interface.
760 #
761 # In the event that the block device is created through the initial command
762 # line, the VM will start in the stopped state regardless of whether '-S' is
763 # used. The intention is for a management tool to query the block devices to
764 # determine which ones are encrypted, set the passwords with this command, and
765 # then start the guest with the @cont command.
766 #
767 # Either @device or @node-name must be set but not both.
768 #
769 # @device: #optional the name of the block backend device to set the password on
770 #
771 # @node-name: #optional graph node name to set the password on (Since 2.0)
772 #
773 # @password: the password to use for the device
774 #
775 # Returns: nothing on success
776 # If @device is not a valid block device, DeviceNotFound
777 # If @device is not encrypted, DeviceNotEncrypted
778 #
779 # Notes: Not all block formats support encryption and some that do are not
780 # able to validate that a password is correct. Disk corruption may
781 # occur if an invalid password is specified.
782 #
783 # Since: 0.14.0
784 ##
785 { 'command': 'block_passwd', 'data': {'*device': 'str',
786 '*node-name': 'str', 'password': 'str'} }
787
788 ##
789 # @block_resize
790 #
791 # Resize a block image while a guest is running.
792 #
793 # Either @device or @node-name must be set but not both.
794 #
795 # @device: #optional the name of the device to get the image resized
796 #
797 # @node-name: #optional graph node name to get the image resized (Since 2.0)
798 #
799 # @size: new image size in bytes
800 #
801 # Returns: nothing on success
802 # If @device is not a valid block device, DeviceNotFound
803 #
804 # Since: 0.14.0
805 ##
806 { 'command': 'block_resize', 'data': { '*device': 'str',
807 '*node-name': 'str',
808 'size': 'int' }}
809
810 ##
811 # @NewImageMode
812 #
813 # An enumeration that tells QEMU how to set the backing file path in
814 # a new image file.
815 #
816 # @existing: QEMU should look for an existing image file.
817 #
818 # @absolute-paths: QEMU should create a new image with absolute paths
819 # for the backing file. If there is no backing file available, the new
820 # image will not be backed either.
821 #
822 # Since: 1.1
823 ##
824 { 'enum': 'NewImageMode',
825 'data': [ 'existing', 'absolute-paths' ] }
826
827 ##
828 # @BlockdevSnapshotSync
829 #
830 # Either @device or @node-name must be set but not both.
831 #
832 # @device: #optional the name of the device to generate the snapshot from.
833 #
834 # @node-name: #optional graph node name to generate the snapshot from (Since 2.0)
835 #
836 # @snapshot-file: the target of the new image. A new file will be created.
837 #
838 # @snapshot-node-name: #optional the graph node name of the new image (Since 2.0)
839 #
840 # @format: #optional the format of the snapshot image, default is 'qcow2'.
841 #
842 # @mode: #optional whether and how QEMU should create a new image, default is
843 # 'absolute-paths'.
844 ##
845 { 'struct': 'BlockdevSnapshotSync',
846 'data': { '*device': 'str', '*node-name': 'str',
847 'snapshot-file': 'str', '*snapshot-node-name': 'str',
848 '*format': 'str', '*mode': 'NewImageMode' } }
849
850 ##
851 # @BlockdevSnapshot
852 #
853 # @node: device or node name that will have a snapshot created.
854 #
855 # @overlay: reference to the existing block device that will become
856 # the overlay of @node, as part of creating the snapshot.
857 # It must not have a current backing file (this can be
858 # achieved by passing "backing": "" to blockdev-add).
859 #
860 # Since 2.5
861 ##
862 { 'struct': 'BlockdevSnapshot',
863 'data': { 'node': 'str', 'overlay': 'str' } }
864
865 ##
866 # @DriveBackup
867 #
868 # @device: the name of the device which should be copied.
869 #
870 # @target: the target of the new image. If the file exists, or if it
871 # is a device, the existing file/device will be used as the new
872 # destination. If it does not exist, a new file will be created.
873 #
874 # @format: #optional the format of the new destination, default is to
875 # probe if @mode is 'existing', else the format of the source
876 #
877 # @sync: what parts of the disk image should be copied to the destination
878 # (all the disk, only the sectors allocated in the topmost image, from a
879 # dirty bitmap, or only new I/O).
880 #
881 # @mode: #optional whether and how QEMU should create a new image, default is
882 # 'absolute-paths'.
883 #
884 # @speed: #optional the maximum speed, in bytes per second
885 #
886 # @bitmap: #optional the name of dirty bitmap if sync is "incremental".
887 # Must be present if sync is "incremental", must NOT be present
888 # otherwise. (Since 2.4)
889 #
890 # @on-source-error: #optional the action to take on an error on the source,
891 # default 'report'. 'stop' and 'enospc' can only be used
892 # if the block device supports io-status (see BlockInfo).
893 #
894 # @on-target-error: #optional the action to take on an error on the target,
895 # default 'report' (no limitations, since this applies to
896 # a different block device than @device).
897 #
898 # Note that @on-source-error and @on-target-error only affect background I/O.
899 # If an error occurs during a guest write request, the device's rerror/werror
900 # actions will be used.
901 #
902 # Since: 1.6
903 ##
904 { 'struct': 'DriveBackup',
905 'data': { 'device': 'str', 'target': 'str', '*format': 'str',
906 'sync': 'MirrorSyncMode', '*mode': 'NewImageMode',
907 '*speed': 'int', '*bitmap': 'str',
908 '*on-source-error': 'BlockdevOnError',
909 '*on-target-error': 'BlockdevOnError' } }
910
911 ##
912 # @BlockdevBackup
913 #
914 # @device: the name of the device which should be copied.
915 #
916 # @target: the name of the backup target device.
917 #
918 # @sync: what parts of the disk image should be copied to the destination
919 # (all the disk, only the sectors allocated in the topmost image, or
920 # only new I/O).
921 #
922 # @speed: #optional the maximum speed, in bytes per second. The default is 0,
923 # for unlimited.
924 #
925 # @on-source-error: #optional the action to take on an error on the source,
926 # default 'report'. 'stop' and 'enospc' can only be used
927 # if the block device supports io-status (see BlockInfo).
928 #
929 # @on-target-error: #optional the action to take on an error on the target,
930 # default 'report' (no limitations, since this applies to
931 # a different block device than @device).
932 #
933 # Note that @on-source-error and @on-target-error only affect background I/O.
934 # If an error occurs during a guest write request, the device's rerror/werror
935 # actions will be used.
936 #
937 # Since: 2.3
938 ##
939 { 'struct': 'BlockdevBackup',
940 'data': { 'device': 'str', 'target': 'str',
941 'sync': 'MirrorSyncMode',
942 '*speed': 'int',
943 '*on-source-error': 'BlockdevOnError',
944 '*on-target-error': 'BlockdevOnError' } }
945
946 ##
947 # @blockdev-snapshot-sync
948 #
949 # Generates a synchronous snapshot of a block device.
950 #
951 # For the arguments, see the documentation of BlockdevSnapshotSync.
952 #
953 # Returns: nothing on success
954 # If @device is not a valid block device, DeviceNotFound
955 #
956 # Since 0.14.0
957 ##
958 { 'command': 'blockdev-snapshot-sync',
959 'data': 'BlockdevSnapshotSync' }
960
961
962 ##
963 # @blockdev-snapshot
964 #
965 # Generates a snapshot of a block device.
966 #
967 # For the arguments, see the documentation of BlockdevSnapshot.
968 #
969 # Since 2.5
970 ##
971 { 'command': 'blockdev-snapshot',
972 'data': 'BlockdevSnapshot' }
973
974 ##
975 # @change-backing-file
976 #
977 # Change the backing file in the image file metadata. This does not
978 # cause QEMU to reopen the image file to reparse the backing filename
979 # (it may, however, perform a reopen to change permissions from
980 # r/o -> r/w -> r/o, if needed). The new backing file string is written
981 # into the image file metadata, and the QEMU internal strings are
982 # updated.
983 #
984 # @image-node-name: The name of the block driver state node of the
985 # image to modify.
986 #
987 # @device: The name of the device that owns image-node-name.
988 #
989 # @backing-file: The string to write as the backing file. This
990 # string is not validated, so care should be taken
991 # when specifying the string or the image chain may
992 # not be able to be reopened again.
993 #
994 # Since: 2.1
995 ##
996 { 'command': 'change-backing-file',
997 'data': { 'device': 'str', 'image-node-name': 'str',
998 'backing-file': 'str' } }
999
1000 ##
1001 # @block-commit
1002 #
1003 # Live commit of data from overlay image nodes into backing nodes - i.e.,
1004 # writes data between 'top' and 'base' into 'base'.
1005 #
1006 # @device: the name of the device
1007 #
1008 # @base: #optional The file name of the backing image to write data into.
1009 # If not specified, this is the deepest backing image
1010 #
1011 # @top: #optional The file name of the backing image within the image chain,
1012 # which contains the topmost data to be committed down. If
1013 # not specified, this is the active layer.
1014 #
1015 # @backing-file: #optional The backing file string to write into the overlay
1016 # image of 'top'. If 'top' is the active layer,
1017 # specifying a backing file string is an error. This
1018 # filename is not validated.
1019 #
1020 # If a pathname string is such that it cannot be
1021 # resolved by QEMU, that means that subsequent QMP or
1022 # HMP commands must use node-names for the image in
1023 # question, as filename lookup methods will fail.
1024 #
1025 # If not specified, QEMU will automatically determine
1026 # the backing file string to use, or error out if
1027 # there is no obvious choice. Care should be taken
1028 # when specifying the string, to specify a valid
1029 # filename or protocol.
1030 # (Since 2.1)
1031 #
1032 # If top == base, that is an error.
1033 # If top == active, the job will not be completed by itself,
1034 # user needs to complete the job with the block-job-complete
1035 # command after getting the ready event. (Since 2.0)
1036 #
1037 # If the base image is smaller than top, then the base image
1038 # will be resized to be the same size as top. If top is
1039 # smaller than the base image, the base will not be
1040 # truncated. If you want the base image size to match the
1041 # size of the smaller top, you can safely truncate it
1042 # yourself once the commit operation successfully completes.
1043 #
1044 # @speed: #optional the maximum speed, in bytes per second
1045 #
1046 # Returns: Nothing on success
1047 # If commit or stream is already active on this device, DeviceInUse
1048 # If @device does not exist, DeviceNotFound
1049 # If image commit is not supported by this device, NotSupported
1050 # If @base or @top is invalid, a generic error is returned
1051 # If @speed is invalid, InvalidParameter
1052 #
1053 # Since: 1.3
1054 #
1055 ##
1056 { 'command': 'block-commit',
1057 'data': { 'device': 'str', '*base': 'str', '*top': 'str',
1058 '*backing-file': 'str', '*speed': 'int' } }
1059
1060 ##
1061 # @drive-backup
1062 #
1063 # Start a point-in-time copy of a block device to a new destination. The
1064 # status of ongoing drive-backup operations can be checked with
1065 # query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1066 # The operation can be stopped before it has completed using the
1067 # block-job-cancel command.
1068 #
1069 # For the arguments, see the documentation of DriveBackup.
1070 #
1071 # Returns: nothing on success
1072 # If @device is not a valid block device, DeviceNotFound
1073 #
1074 # Since 1.6
1075 ##
1076 { 'command': 'drive-backup', 'data': 'DriveBackup' }
1077
1078 ##
1079 # @blockdev-backup
1080 #
1081 # Start a point-in-time copy of a block device to a new destination. The
1082 # status of ongoing blockdev-backup operations can be checked with
1083 # query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
1084 # The operation can be stopped before it has completed using the
1085 # block-job-cancel command.
1086 #
1087 # For the arguments, see the documentation of BlockdevBackup.
1088 #
1089 # Since 2.3
1090 ##
1091 { 'command': 'blockdev-backup', 'data': 'BlockdevBackup' }
1092
1093
1094 ##
1095 # @query-named-block-nodes
1096 #
1097 # Get the named block driver list
1098 #
1099 # Returns: the list of BlockDeviceInfo
1100 #
1101 # Since 2.0
1102 ##
1103 { 'command': 'query-named-block-nodes', 'returns': [ 'BlockDeviceInfo' ] }
1104
1105 ##
1106 # @drive-mirror
1107 #
1108 # Start mirroring a block device's writes to a new destination.
1109 #
1110 # @device: the name of the device whose writes should be mirrored.
1111 #
1112 # @target: the target of the new image. If the file exists, or if it
1113 # is a device, the existing file/device will be used as the new
1114 # destination. If it does not exist, a new file will be created.
1115 #
1116 # @format: #optional the format of the new destination, default is to
1117 # probe if @mode is 'existing', else the format of the source
1118 #
1119 # @node-name: #optional the new block driver state node name in the graph
1120 # (Since 2.1)
1121 #
1122 # @replaces: #optional with sync=full graph node name to be replaced by the new
1123 # image when a whole image copy is done. This can be used to repair
1124 # broken Quorum files. (Since 2.1)
1125 #
1126 # @mode: #optional whether and how QEMU should create a new image, default is
1127 # 'absolute-paths'.
1128 #
1129 # @speed: #optional the maximum speed, in bytes per second
1130 #
1131 # @sync: what parts of the disk image should be copied to the destination
1132 # (all the disk, only the sectors allocated in the topmost image, or
1133 # only new I/O).
1134 #
1135 # @granularity: #optional granularity of the dirty bitmap, default is 64K
1136 # if the image format doesn't have clusters, 4K if the clusters
1137 # are smaller than that, else the cluster size. Must be a
1138 # power of 2 between 512 and 64M (since 1.4).
1139 #
1140 # @buf-size: #optional maximum amount of data in flight from source to
1141 # target (since 1.4).
1142 #
1143 # @on-source-error: #optional the action to take on an error on the source,
1144 # default 'report'. 'stop' and 'enospc' can only be used
1145 # if the block device supports io-status (see BlockInfo).
1146 #
1147 # @on-target-error: #optional the action to take on an error on the target,
1148 # default 'report' (no limitations, since this applies to
1149 # a different block device than @device).
1150 # @unmap: #optional Whether to try to unmap target sectors where source has
1151 # only zero. If true, and target unallocated sectors will read as zero,
1152 # target image sectors will be unmapped; otherwise, zeroes will be
1153 # written. Both will result in identical contents.
1154 # Default is true. (Since 2.4)
1155 #
1156 # Returns: nothing on success
1157 # If @device is not a valid block device, DeviceNotFound
1158 #
1159 # Since 1.3
1160 ##
1161 { 'command': 'drive-mirror',
1162 'data': { 'device': 'str', 'target': 'str', '*format': 'str',
1163 '*node-name': 'str', '*replaces': 'str',
1164 'sync': 'MirrorSyncMode', '*mode': 'NewImageMode',
1165 '*speed': 'int', '*granularity': 'uint32',
1166 '*buf-size': 'int', '*on-source-error': 'BlockdevOnError',
1167 '*on-target-error': 'BlockdevOnError',
1168 '*unmap': 'bool' } }
1169
1170 ##
1171 # @BlockDirtyBitmap
1172 #
1173 # @node: name of device/node which the bitmap is tracking
1174 #
1175 # @name: name of the dirty bitmap
1176 #
1177 # Since 2.4
1178 ##
1179 { 'struct': 'BlockDirtyBitmap',
1180 'data': { 'node': 'str', 'name': 'str' } }
1181
1182 ##
1183 # @BlockDirtyBitmapAdd
1184 #
1185 # @node: name of device/node which the bitmap is tracking
1186 #
1187 # @name: name of the dirty bitmap
1188 #
1189 # @granularity: #optional the bitmap granularity, default is 64k for
1190 # block-dirty-bitmap-add
1191 #
1192 # Since 2.4
1193 ##
1194 { 'struct': 'BlockDirtyBitmapAdd',
1195 'data': { 'node': 'str', 'name': 'str', '*granularity': 'uint32' } }
1196
1197 ##
1198 # @block-dirty-bitmap-add
1199 #
1200 # Create a dirty bitmap with a name on the node
1201 #
1202 # Returns: nothing on success
1203 # If @node is not a valid block device or node, DeviceNotFound
1204 # If @name is already taken, GenericError with an explanation
1205 #
1206 # Since 2.4
1207 ##
1208 { 'command': 'block-dirty-bitmap-add',
1209 'data': 'BlockDirtyBitmapAdd' }
1210
1211 ##
1212 # @block-dirty-bitmap-remove
1213 #
1214 # Remove a dirty bitmap on the node
1215 #
1216 # Returns: nothing on success
1217 # If @node is not a valid block device or node, DeviceNotFound
1218 # If @name is not found, GenericError with an explanation
1219 # if @name is frozen by an operation, GenericError
1220 #
1221 # Since 2.4
1222 ##
1223 { 'command': 'block-dirty-bitmap-remove',
1224 'data': 'BlockDirtyBitmap' }
1225
1226 ##
1227 # @block-dirty-bitmap-clear
1228 #
1229 # Clear (reset) a dirty bitmap on the device
1230 #
1231 # Returns: nothing on success
1232 # If @node is not a valid block device, DeviceNotFound
1233 # If @name is not found, GenericError with an explanation
1234 #
1235 # Since 2.4
1236 ##
1237 { 'command': 'block-dirty-bitmap-clear',
1238 'data': 'BlockDirtyBitmap' }
1239
1240 ##
1241 # @blockdev-mirror
1242 #
1243 # Start mirroring a block device's writes to a new destination.
1244 #
1245 # @device: the name of the device whose writes should be mirrored.
1246 #
1247 # @target: the id or node-name of the block device to mirror to. This mustn't be
1248 # attached to guest.
1249 #
1250 # @replaces: #optional with sync=full graph node name to be replaced by the new
1251 # image when a whole image copy is done. This can be used to repair
1252 # broken Quorum files.
1253 #
1254 # @speed: #optional the maximum speed, in bytes per second
1255 #
1256 # @sync: what parts of the disk image should be copied to the destination
1257 # (all the disk, only the sectors allocated in the topmost image, or
1258 # only new I/O).
1259 #
1260 # @granularity: #optional granularity of the dirty bitmap, default is 64K
1261 # if the image format doesn't have clusters, 4K if the clusters
1262 # are smaller than that, else the cluster size. Must be a
1263 # power of 2 between 512 and 64M
1264 #
1265 # @buf-size: #optional maximum amount of data in flight from source to
1266 # target
1267 #
1268 # @on-source-error: #optional the action to take on an error on the source,
1269 # default 'report'. 'stop' and 'enospc' can only be used
1270 # if the block device supports io-status (see BlockInfo).
1271 #
1272 # @on-target-error: #optional the action to take on an error on the target,
1273 # default 'report' (no limitations, since this applies to
1274 # a different block device than @device).
1275 #
1276 # Returns: nothing on success.
1277 #
1278 # Since 2.6
1279 ##
1280 { 'command': 'blockdev-mirror',
1281 'data': { 'device': 'str', 'target': 'str',
1282 '*replaces': 'str',
1283 'sync': 'MirrorSyncMode',
1284 '*speed': 'int', '*granularity': 'uint32',
1285 '*buf-size': 'int', '*on-source-error': 'BlockdevOnError',
1286 '*on-target-error': 'BlockdevOnError' } }
1287
1288 ##
1289 # @block_set_io_throttle:
1290 #
1291 # Change I/O throttle limits for a block drive.
1292 #
1293 # Since QEMU 2.4, each device with I/O limits is member of a throttle
1294 # group.
1295 #
1296 # If two or more devices are members of the same group, the limits
1297 # will apply to the combined I/O of the whole group in a round-robin
1298 # fashion. Therefore, setting new I/O limits to a device will affect
1299 # the whole group.
1300 #
1301 # The name of the group can be specified using the 'group' parameter.
1302 # If the parameter is unset, it is assumed to be the current group of
1303 # that device. If it's not in any group yet, the name of the device
1304 # will be used as the name for its group.
1305 #
1306 # The 'group' parameter can also be used to move a device to a
1307 # different group. In this case the limits specified in the parameters
1308 # will be applied to the new group only.
1309 #
1310 # I/O limits can be disabled by setting all of them to 0. In this case
1311 # the device will be removed from its group and the rest of its
1312 # members will not be affected. The 'group' parameter is ignored.
1313 #
1314 # @device: The name of the device
1315 #
1316 # @bps: total throughput limit in bytes per second
1317 #
1318 # @bps_rd: read throughput limit in bytes per second
1319 #
1320 # @bps_wr: write throughput limit in bytes per second
1321 #
1322 # @iops: total I/O operations per second
1323 #
1324 # @iops_rd: read I/O operations per second
1325 #
1326 # @iops_wr: write I/O operations per second
1327 #
1328 # @bps_max: #optional total throughput limit during bursts,
1329 # in bytes (Since 1.7)
1330 #
1331 # @bps_rd_max: #optional read throughput limit during bursts,
1332 # in bytes (Since 1.7)
1333 #
1334 # @bps_wr_max: #optional write throughput limit during bursts,
1335 # in bytes (Since 1.7)
1336 #
1337 # @iops_max: #optional total I/O operations per second during bursts,
1338 # in bytes (Since 1.7)
1339 #
1340 # @iops_rd_max: #optional read I/O operations per second during bursts,
1341 # in bytes (Since 1.7)
1342 #
1343 # @iops_wr_max: #optional write I/O operations per second during bursts,
1344 # in bytes (Since 1.7)
1345 #
1346 # @bps_max_length: #optional maximum length of the @bps_max burst
1347 # period, in seconds. It must only
1348 # be set if @bps_max is set as well.
1349 # Defaults to 1. (Since 2.6)
1350 #
1351 # @bps_rd_max_length: #optional maximum length of the @bps_rd_max
1352 # burst period, in seconds. It must only
1353 # be set if @bps_rd_max is set as well.
1354 # Defaults to 1. (Since 2.6)
1355 #
1356 # @bps_wr_max_length: #optional maximum length of the @bps_wr_max
1357 # burst period, in seconds. It must only
1358 # be set if @bps_wr_max is set as well.
1359 # Defaults to 1. (Since 2.6)
1360 #
1361 # @iops_max_length: #optional maximum length of the @iops burst
1362 # period, in seconds. It must only
1363 # be set if @iops_max is set as well.
1364 # Defaults to 1. (Since 2.6)
1365 #
1366 # @iops_rd_max_length: #optional maximum length of the @iops_rd_max
1367 # burst period, in seconds. It must only
1368 # be set if @iops_rd_max is set as well.
1369 # Defaults to 1. (Since 2.6)
1370 #
1371 # @iops_wr_max_length: #optional maximum length of the @iops_wr_max
1372 # burst period, in seconds. It must only
1373 # be set if @iops_wr_max is set as well.
1374 # Defaults to 1. (Since 2.6)
1375 #
1376 # @iops_size: #optional an I/O size in bytes (Since 1.7)
1377 #
1378 # @group: #optional throttle group name (Since 2.4)
1379 #
1380 # Returns: Nothing on success
1381 # If @device is not a valid block device, DeviceNotFound
1382 #
1383 # Since: 1.1
1384 ##
1385 { 'command': 'block_set_io_throttle',
1386 'data': { 'device': 'str', 'bps': 'int', 'bps_rd': 'int', 'bps_wr': 'int',
1387 'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
1388 '*bps_max': 'int', '*bps_rd_max': 'int',
1389 '*bps_wr_max': 'int', '*iops_max': 'int',
1390 '*iops_rd_max': 'int', '*iops_wr_max': 'int',
1391 '*bps_max_length': 'int', '*bps_rd_max_length': 'int',
1392 '*bps_wr_max_length': 'int', '*iops_max_length': 'int',
1393 '*iops_rd_max_length': 'int', '*iops_wr_max_length': 'int',
1394 '*iops_size': 'int', '*group': 'str' } }
1395
1396 ##
1397 # @block-stream:
1398 #
1399 # Copy data from a backing file into a block device.
1400 #
1401 # The block streaming operation is performed in the background until the entire
1402 # backing file has been copied. This command returns immediately once streaming
1403 # has started. The status of ongoing block streaming operations can be checked
1404 # with query-block-jobs. The operation can be stopped before it has completed
1405 # using the block-job-cancel command.
1406 #
1407 # If a base file is specified then sectors are not copied from that base file and
1408 # its backing chain. When streaming completes the image file will have the base
1409 # file as its backing file. This can be used to stream a subset of the backing
1410 # file chain instead of flattening the entire image.
1411 #
1412 # On successful completion the image file is updated to drop the backing file
1413 # and the BLOCK_JOB_COMPLETED event is emitted.
1414 #
1415 # @device: the device name
1416 #
1417 # @base: #optional the common backing file name
1418 #
1419 # @backing-file: #optional The backing file string to write into the active
1420 # layer. This filename is not validated.
1421 #
1422 # If a pathname string is such that it cannot be
1423 # resolved by QEMU, that means that subsequent QMP or
1424 # HMP commands must use node-names for the image in
1425 # question, as filename lookup methods will fail.
1426 #
1427 # If not specified, QEMU will automatically determine
1428 # the backing file string to use, or error out if there
1429 # is no obvious choice. Care should be taken when
1430 # specifying the string, to specify a valid filename or
1431 # protocol.
1432 # (Since 2.1)
1433 #
1434 # @speed: #optional the maximum speed, in bytes per second
1435 #
1436 # @on-error: #optional the action to take on an error (default report).
1437 # 'stop' and 'enospc' can only be used if the block device
1438 # supports io-status (see BlockInfo). Since 1.3.
1439 #
1440 # Returns: Nothing on success
1441 # If @device does not exist, DeviceNotFound
1442 #
1443 # Since: 1.1
1444 ##
1445 { 'command': 'block-stream',
1446 'data': { 'device': 'str', '*base': 'str', '*backing-file': 'str',
1447 '*speed': 'int', '*on-error': 'BlockdevOnError' } }
1448
1449 ##
1450 # @block-job-set-speed:
1451 #
1452 # Set maximum speed for a background block operation.
1453 #
1454 # This command can only be issued when there is an active block job.
1455 #
1456 # Throttling can be disabled by setting the speed to 0.
1457 #
1458 # @device: the device name
1459 #
1460 # @speed: the maximum speed, in bytes per second, or 0 for unlimited.
1461 # Defaults to 0.
1462 #
1463 # Returns: Nothing on success
1464 # If no background operation is active on this device, DeviceNotActive
1465 #
1466 # Since: 1.1
1467 ##
1468 { 'command': 'block-job-set-speed',
1469 'data': { 'device': 'str', 'speed': 'int' } }
1470
1471 ##
1472 # @block-job-cancel:
1473 #
1474 # Stop an active background block operation.
1475 #
1476 # This command returns immediately after marking the active background block
1477 # operation for cancellation. It is an error to call this command if no
1478 # operation is in progress.
1479 #
1480 # The operation will cancel as soon as possible and then emit the
1481 # BLOCK_JOB_CANCELLED event. Before that happens the job is still visible when
1482 # enumerated using query-block-jobs.
1483 #
1484 # For streaming, the image file retains its backing file unless the streaming
1485 # operation happens to complete just as it is being cancelled. A new streaming
1486 # operation can be started at a later time to finish copying all data from the
1487 # backing file.
1488 #
1489 # @device: the device name
1490 #
1491 # @force: #optional whether to allow cancellation of a paused job (default
1492 # false). Since 1.3.
1493 #
1494 # Returns: Nothing on success
1495 # If no background operation is active on this device, DeviceNotActive
1496 #
1497 # Since: 1.1
1498 ##
1499 { 'command': 'block-job-cancel', 'data': { 'device': 'str', '*force': 'bool' } }
1500
1501 ##
1502 # @block-job-pause:
1503 #
1504 # Pause an active background block operation.
1505 #
1506 # This command returns immediately after marking the active background block
1507 # operation for pausing. It is an error to call this command if no
1508 # operation is in progress. Pausing an already paused job has no cumulative
1509 # effect; a single block-job-resume command will resume the job.
1510 #
1511 # The operation will pause as soon as possible. No event is emitted when
1512 # the operation is actually paused. Cancelling a paused job automatically
1513 # resumes it.
1514 #
1515 # @device: the device name
1516 #
1517 # Returns: Nothing on success
1518 # If no background operation is active on this device, DeviceNotActive
1519 #
1520 # Since: 1.3
1521 ##
1522 { 'command': 'block-job-pause', 'data': { 'device': 'str' } }
1523
1524 ##
1525 # @block-job-resume:
1526 #
1527 # Resume an active background block operation.
1528 #
1529 # This command returns immediately after resuming a paused background block
1530 # operation. It is an error to call this command if no operation is in
1531 # progress. Resuming an already running job is not an error.
1532 #
1533 # This command also clears the error status of the job.
1534 #
1535 # @device: the device name
1536 #
1537 # Returns: Nothing on success
1538 # If no background operation is active on this device, DeviceNotActive
1539 #
1540 # Since: 1.3
1541 ##
1542 { 'command': 'block-job-resume', 'data': { 'device': 'str' } }
1543
1544 ##
1545 # @block-job-complete:
1546 #
1547 # Manually trigger completion of an active background block operation. This
1548 # is supported for drive mirroring, where it also switches the device to
1549 # write to the target path only. The ability to complete is signaled with
1550 # a BLOCK_JOB_READY event.
1551 #
1552 # This command completes an active background block operation synchronously.
1553 # The ordering of this command's return with the BLOCK_JOB_COMPLETED event
1554 # is not defined. Note that if an I/O error occurs during the processing of
1555 # this command: 1) the command itself will fail; 2) the error will be processed
1556 # according to the rerror/werror arguments that were specified when starting
1557 # the operation.
1558 #
1559 # A cancelled or paused job cannot be completed.
1560 #
1561 # @device: the device name
1562 #
1563 # Returns: Nothing on success
1564 # If no background operation is active on this device, DeviceNotActive
1565 #
1566 # Since: 1.3
1567 ##
1568 { 'command': 'block-job-complete', 'data': { 'device': 'str' } }
1569
1570 ##
1571 # @BlockdevDiscardOptions
1572 #
1573 # Determines how to handle discard requests.
1574 #
1575 # @ignore: Ignore the request
1576 # @unmap: Forward as an unmap request
1577 #
1578 # Since: 1.7
1579 ##
1580 { 'enum': 'BlockdevDiscardOptions',
1581 'data': [ 'ignore', 'unmap' ] }
1582
1583 ##
1584 # @BlockdevDetectZeroesOptions
1585 #
1586 # Describes the operation mode for the automatic conversion of plain
1587 # zero writes by the OS to driver specific optimized zero write commands.
1588 #
1589 # @off: Disabled (default)
1590 # @on: Enabled
1591 # @unmap: Enabled and even try to unmap blocks if possible. This requires
1592 # also that @BlockdevDiscardOptions is set to unmap for this device.
1593 #
1594 # Since: 2.1
1595 ##
1596 { 'enum': 'BlockdevDetectZeroesOptions',
1597 'data': [ 'off', 'on', 'unmap' ] }
1598
1599 ##
1600 # @BlockdevAioOptions
1601 #
1602 # Selects the AIO backend to handle I/O requests
1603 #
1604 # @threads: Use qemu's thread pool
1605 # @native: Use native AIO backend (only Linux and Windows)
1606 #
1607 # Since: 1.7
1608 ##
1609 { 'enum': 'BlockdevAioOptions',
1610 'data': [ 'threads', 'native' ] }
1611
1612 ##
1613 # @BlockdevCacheOptions
1614 #
1615 # Includes cache-related options for block devices
1616 #
1617 # @writeback: #optional enables writeback mode for any caches (default: true)
1618 # @direct: #optional enables use of O_DIRECT (bypass the host page cache;
1619 # default: false)
1620 # @no-flush: #optional ignore any flush requests for the device (default:
1621 # false)
1622 #
1623 # Since: 1.7
1624 ##
1625 { 'struct': 'BlockdevCacheOptions',
1626 'data': { '*writeback': 'bool',
1627 '*direct': 'bool',
1628 '*no-flush': 'bool' } }
1629
1630 ##
1631 # @BlockdevDriver
1632 #
1633 # Drivers that are supported in block device operations.
1634 #
1635 # @host_device, @host_cdrom: Since 2.1
1636 #
1637 # Since: 2.0
1638 ##
1639 { 'enum': 'BlockdevDriver',
1640 'data': [ 'archipelago', 'blkdebug', 'blkverify', 'bochs', 'cloop',
1641 'dmg', 'file', 'ftp', 'ftps', 'host_cdrom', 'host_device',
1642 'http', 'https', 'null-aio', 'null-co', 'parallels',
1643 'qcow', 'qcow2', 'qed', 'quorum', 'raw', 'tftp', 'vdi', 'vhdx',
1644 'vmdk', 'vpc', 'vvfat' ] }
1645
1646 ##
1647 # @BlockdevOptionsBase
1648 #
1649 # Options that are available for all block devices, independent of the block
1650 # driver.
1651 #
1652 # @driver: block driver name
1653 # @id: #optional id by which the new block device can be referred to.
1654 # This option is only allowed on the top level of blockdev-add.
1655 # A BlockBackend will be created by blockdev-add if and only if
1656 # this option is given.
1657 # @node-name: #optional the name of a block driver state node (Since 2.0).
1658 # This option is required on the top level of blockdev-add if
1659 # the @id option is not given there.
1660 # @discard: #optional discard-related options (default: ignore)
1661 # @cache: #optional cache-related options
1662 # @aio: #optional AIO backend (default: threads)
1663 # @rerror: #optional how to handle read errors on the device
1664 # (default: report)
1665 # @werror: #optional how to handle write errors on the device
1666 # (default: enospc)
1667 # @read-only: #optional whether the block device should be read-only
1668 # (default: false)
1669 # @stats-account-invalid: #optional whether to include invalid
1670 # operations when computing last access statistics
1671 # (default: true) (Since 2.5)
1672 # @stats-account-failed: #optional whether to include failed
1673 # operations when computing latency and last
1674 # access statistics (default: true) (Since 2.5)
1675 # @stats-intervals: #optional list of intervals for collecting I/O
1676 # statistics, in seconds (default: none) (Since 2.5)
1677 # @detect-zeroes: #optional detect and optimize zero writes (Since 2.1)
1678 # (default: off)
1679 #
1680 # Since: 1.7
1681 ##
1682 { 'struct': 'BlockdevOptionsBase',
1683 'data': { 'driver': 'BlockdevDriver',
1684 '*id': 'str',
1685 '*node-name': 'str',
1686 '*discard': 'BlockdevDiscardOptions',
1687 '*cache': 'BlockdevCacheOptions',
1688 '*aio': 'BlockdevAioOptions',
1689 '*rerror': 'BlockdevOnError',
1690 '*werror': 'BlockdevOnError',
1691 '*read-only': 'bool',
1692 '*stats-account-invalid': 'bool',
1693 '*stats-account-failed': 'bool',
1694 '*stats-intervals': ['int'],
1695 '*detect-zeroes': 'BlockdevDetectZeroesOptions' } }
1696
1697 ##
1698 # @BlockdevOptionsFile
1699 #
1700 # Driver specific block device options for the file backend and similar
1701 # protocols.
1702 #
1703 # @filename: path to the image file
1704 #
1705 # Since: 1.7
1706 ##
1707 { 'struct': 'BlockdevOptionsFile',
1708 'data': { 'filename': 'str' } }
1709
1710 ##
1711 # @BlockdevOptionsNull
1712 #
1713 # Driver specific block device options for the null backend.
1714 #
1715 # @size: #optional size of the device in bytes.
1716 # @latency-ns: #optional emulated latency (in nanoseconds) in processing
1717 # requests. Default to zero which completes requests immediately.
1718 # (Since 2.4)
1719 #
1720 # Since: 2.2
1721 ##
1722 { 'struct': 'BlockdevOptionsNull',
1723 'data': { '*size': 'int', '*latency-ns': 'uint64' } }
1724
1725 ##
1726 # @BlockdevOptionsVVFAT
1727 #
1728 # Driver specific block device options for the vvfat protocol.
1729 #
1730 # @dir: directory to be exported as FAT image
1731 # @fat-type: #optional FAT type: 12, 16 or 32
1732 # @floppy: #optional whether to export a floppy image (true) or
1733 # partitioned hard disk (false; default)
1734 # @label: #optional set the volume label, limited to 11 bytes. FAT16 and
1735 # FAT32 traditionally have some restrictions on labels, which are
1736 # ignored by most operating systems. Defaults to "QEMU VVFAT".
1737 # (since 2.4)
1738 # @rw: #optional whether to allow write operations (default: false)
1739 #
1740 # Since: 1.7
1741 ##
1742 { 'struct': 'BlockdevOptionsVVFAT',
1743 'data': { 'dir': 'str', '*fat-type': 'int', '*floppy': 'bool',
1744 '*label': 'str', '*rw': 'bool' } }
1745
1746 ##
1747 # @BlockdevOptionsGenericFormat
1748 #
1749 # Driver specific block device options for image format that have no option
1750 # besides their data source.
1751 #
1752 # @file: reference to or definition of the data source block device
1753 #
1754 # Since: 1.7
1755 ##
1756 { 'struct': 'BlockdevOptionsGenericFormat',
1757 'data': { 'file': 'BlockdevRef' } }
1758
1759 ##
1760 # @BlockdevOptionsGenericCOWFormat
1761 #
1762 # Driver specific block device options for image format that have no option
1763 # besides their data source and an optional backing file.
1764 #
1765 # @backing: #optional reference to or definition of the backing file block
1766 # device (if missing, taken from the image file content). It is
1767 # allowed to pass an empty string here in order to disable the
1768 # default backing file.
1769 #
1770 # Since: 1.7
1771 ##
1772 { 'struct': 'BlockdevOptionsGenericCOWFormat',
1773 'base': 'BlockdevOptionsGenericFormat',
1774 'data': { '*backing': 'BlockdevRef' } }
1775
1776 ##
1777 # @Qcow2OverlapCheckMode
1778 #
1779 # General overlap check modes.
1780 #
1781 # @none: Do not perform any checks
1782 #
1783 # @constant: Perform only checks which can be done in constant time and
1784 # without reading anything from disk
1785 #
1786 # @cached: Perform only checks which can be done without reading anything
1787 # from disk
1788 #
1789 # @all: Perform all available overlap checks
1790 #
1791 # Since: 2.2
1792 ##
1793 { 'enum': 'Qcow2OverlapCheckMode',
1794 'data': [ 'none', 'constant', 'cached', 'all' ] }
1795
1796 ##
1797 # @Qcow2OverlapCheckFlags
1798 #
1799 # Structure of flags for each metadata structure. Setting a field to 'true'
1800 # makes qemu guard that structure against unintended overwriting. The default
1801 # value is chosen according to the template given.
1802 #
1803 # @template: Specifies a template mode which can be adjusted using the other
1804 # flags, defaults to 'cached'
1805 #
1806 # Since: 2.2
1807 ##
1808 { 'struct': 'Qcow2OverlapCheckFlags',
1809 'data': { '*template': 'Qcow2OverlapCheckMode',
1810 '*main-header': 'bool',
1811 '*active-l1': 'bool',
1812 '*active-l2': 'bool',
1813 '*refcount-table': 'bool',
1814 '*refcount-block': 'bool',
1815 '*snapshot-table': 'bool',
1816 '*inactive-l1': 'bool',
1817 '*inactive-l2': 'bool' } }
1818
1819 ##
1820 # @Qcow2OverlapChecks
1821 #
1822 # Specifies which metadata structures should be guarded against unintended
1823 # overwriting.
1824 #
1825 # @flags: set of flags for separate specification of each metadata structure
1826 # type
1827 #
1828 # @mode: named mode which chooses a specific set of flags
1829 #
1830 # Since: 2.2
1831 ##
1832 { 'alternate': 'Qcow2OverlapChecks',
1833 'data': { 'flags': 'Qcow2OverlapCheckFlags',
1834 'mode': 'Qcow2OverlapCheckMode' } }
1835
1836 ##
1837 # @BlockdevOptionsQcow2
1838 #
1839 # Driver specific block device options for qcow2.
1840 #
1841 # @lazy-refcounts: #optional whether to enable the lazy refcounts
1842 # feature (default is taken from the image file)
1843 #
1844 # @pass-discard-request: #optional whether discard requests to the qcow2
1845 # device should be forwarded to the data source
1846 #
1847 # @pass-discard-snapshot: #optional whether discard requests for the data source
1848 # should be issued when a snapshot operation (e.g.
1849 # deleting a snapshot) frees clusters in the qcow2 file
1850 #
1851 # @pass-discard-other: #optional whether discard requests for the data source
1852 # should be issued on other occasions where a cluster
1853 # gets freed
1854 #
1855 # @overlap-check: #optional which overlap checks to perform for writes
1856 # to the image, defaults to 'cached' (since 2.2)
1857 #
1858 # @cache-size: #optional the maximum total size of the L2 table and
1859 # refcount block caches in bytes (since 2.2)
1860 #
1861 # @l2-cache-size: #optional the maximum size of the L2 table cache in
1862 # bytes (since 2.2)
1863 #
1864 # @refcount-cache-size: #optional the maximum size of the refcount block cache
1865 # in bytes (since 2.2)
1866 #
1867 # @cache-clean-interval: #optional clean unused entries in the L2 and refcount
1868 # caches. The interval is in seconds. The default value
1869 # is 0 and it disables this feature (since 2.5)
1870 #
1871 # Since: 1.7
1872 ##
1873 { 'struct': 'BlockdevOptionsQcow2',
1874 'base': 'BlockdevOptionsGenericCOWFormat',
1875 'data': { '*lazy-refcounts': 'bool',
1876 '*pass-discard-request': 'bool',
1877 '*pass-discard-snapshot': 'bool',
1878 '*pass-discard-other': 'bool',
1879 '*overlap-check': 'Qcow2OverlapChecks',
1880 '*cache-size': 'int',
1881 '*l2-cache-size': 'int',
1882 '*refcount-cache-size': 'int',
1883 '*cache-clean-interval': 'int' } }
1884
1885
1886 ##
1887 # @BlockdevOptionsArchipelago
1888 #
1889 # Driver specific block device options for Archipelago.
1890 #
1891 # @volume: Name of the Archipelago volume image
1892 #
1893 # @mport: #optional The port number on which mapperd is
1894 # listening. This is optional
1895 # and if not specified, QEMU will make Archipelago
1896 # use the default port (1001).
1897 #
1898 # @vport: #optional The port number on which vlmcd is
1899 # listening. This is optional
1900 # and if not specified, QEMU will make Archipelago
1901 # use the default port (501).
1902 #
1903 # @segment: #optional The name of the shared memory segment
1904 # Archipelago stack is using. This is optional
1905 # and if not specified, QEMU will make Archipelago
1906 # use the default value, 'archipelago'.
1907 # Since: 2.2
1908 ##
1909 { 'struct': 'BlockdevOptionsArchipelago',
1910 'data': { 'volume': 'str',
1911 '*mport': 'int',
1912 '*vport': 'int',
1913 '*segment': 'str' } }
1914
1915
1916 ##
1917 # @BlkdebugEvent
1918 #
1919 # Trigger events supported by blkdebug.
1920 #
1921 # Since: 2.0
1922 ##
1923 { 'enum': 'BlkdebugEvent', 'prefix': 'BLKDBG',
1924 'data': [ 'l1_update', 'l1_grow_alloc_table', 'l1_grow_write_table',
1925 'l1_grow_activate_table', 'l2_load', 'l2_update',
1926 'l2_update_compressed', 'l2_alloc_cow_read', 'l2_alloc_write',
1927 'read_aio', 'read_backing_aio', 'read_compressed', 'write_aio',
1928 'write_compressed', 'vmstate_load', 'vmstate_save', 'cow_read',
1929 'cow_write', 'reftable_load', 'reftable_grow', 'reftable_update',
1930 'refblock_load', 'refblock_update', 'refblock_update_part',
1931 'refblock_alloc', 'refblock_alloc_hookup', 'refblock_alloc_write',
1932 'refblock_alloc_write_blocks', 'refblock_alloc_write_table',
1933 'refblock_alloc_switch_table', 'cluster_alloc',
1934 'cluster_alloc_bytes', 'cluster_free', 'flush_to_os',
1935 'flush_to_disk', 'pwritev_rmw_head', 'pwritev_rmw_after_head',
1936 'pwritev_rmw_tail', 'pwritev_rmw_after_tail', 'pwritev',
1937 'pwritev_zero', 'pwritev_done', 'empty_image_prepare' ] }
1938
1939 ##
1940 # @BlkdebugInjectErrorOptions
1941 #
1942 # Describes a single error injection for blkdebug.
1943 #
1944 # @event: trigger event
1945 #
1946 # @state: #optional the state identifier blkdebug needs to be in to
1947 # actually trigger the event; defaults to "any"
1948 #
1949 # @errno: #optional error identifier (errno) to be returned; defaults to
1950 # EIO
1951 #
1952 # @sector: #optional specifies the sector index which has to be affected
1953 # in order to actually trigger the event; defaults to "any
1954 # sector"
1955 #
1956 # @once: #optional disables further events after this one has been
1957 # triggered; defaults to false
1958 #
1959 # @immediately: #optional fail immediately; defaults to false
1960 #
1961 # Since: 2.0
1962 ##
1963 { 'struct': 'BlkdebugInjectErrorOptions',
1964 'data': { 'event': 'BlkdebugEvent',
1965 '*state': 'int',
1966 '*errno': 'int',
1967 '*sector': 'int',
1968 '*once': 'bool',
1969 '*immediately': 'bool' } }
1970
1971 ##
1972 # @BlkdebugSetStateOptions
1973 #
1974 # Describes a single state-change event for blkdebug.
1975 #
1976 # @event: trigger event
1977 #
1978 # @state: #optional the current state identifier blkdebug needs to be in;
1979 # defaults to "any"
1980 #
1981 # @new_state: the state identifier blkdebug is supposed to assume if
1982 # this event is triggered
1983 #
1984 # Since: 2.0
1985 ##
1986 { 'struct': 'BlkdebugSetStateOptions',
1987 'data': { 'event': 'BlkdebugEvent',
1988 '*state': 'int',
1989 'new_state': 'int' } }
1990
1991 ##
1992 # @BlockdevOptionsBlkdebug
1993 #
1994 # Driver specific block device options for blkdebug.
1995 #
1996 # @image: underlying raw block device (or image file)
1997 #
1998 # @config: #optional filename of the configuration file
1999 #
2000 # @align: #optional required alignment for requests in bytes
2001 #
2002 # @inject-error: #optional array of error injection descriptions
2003 #
2004 # @set-state: #optional array of state-change descriptions
2005 #
2006 # Since: 2.0
2007 ##
2008 { 'struct': 'BlockdevOptionsBlkdebug',
2009 'data': { 'image': 'BlockdevRef',
2010 '*config': 'str',
2011 '*align': 'int',
2012 '*inject-error': ['BlkdebugInjectErrorOptions'],
2013 '*set-state': ['BlkdebugSetStateOptions'] } }
2014
2015 ##
2016 # @BlockdevOptionsBlkverify
2017 #
2018 # Driver specific block device options for blkverify.
2019 #
2020 # @test: block device to be tested
2021 #
2022 # @raw: raw image used for verification
2023 #
2024 # Since: 2.0
2025 ##
2026 { 'struct': 'BlockdevOptionsBlkverify',
2027 'data': { 'test': 'BlockdevRef',
2028 'raw': 'BlockdevRef' } }
2029
2030 ##
2031 # @QuorumReadPattern
2032 #
2033 # An enumeration of quorum read patterns.
2034 #
2035 # @quorum: read all the children and do a quorum vote on reads
2036 #
2037 # @fifo: read only from the first child that has not failed
2038 #
2039 # Since: 2.2
2040 ##
2041 { 'enum': 'QuorumReadPattern', 'data': [ 'quorum', 'fifo' ] }
2042
2043 ##
2044 # @BlockdevOptionsQuorum
2045 #
2046 # Driver specific block device options for Quorum
2047 #
2048 # @blkverify: #optional true if the driver must print content mismatch
2049 # set to false by default
2050 #
2051 # @children: the children block devices to use
2052 #
2053 # @vote-threshold: the vote limit under which a read will fail
2054 #
2055 # @rewrite-corrupted: #optional rewrite corrupted data when quorum is reached
2056 # (Since 2.1)
2057 #
2058 # @read-pattern: #optional choose read pattern and set to quorum by default
2059 # (Since 2.2)
2060 #
2061 # Since: 2.0
2062 ##
2063 { 'struct': 'BlockdevOptionsQuorum',
2064 'data': { '*blkverify': 'bool',
2065 'children': [ 'BlockdevRef' ],
2066 'vote-threshold': 'int',
2067 '*rewrite-corrupted': 'bool',
2068 '*read-pattern': 'QuorumReadPattern' } }
2069
2070 ##
2071 # @BlockdevOptions
2072 #
2073 # Options for creating a block device.
2074 #
2075 # Since: 1.7
2076 ##
2077 { 'union': 'BlockdevOptions',
2078 'base': 'BlockdevOptionsBase',
2079 'discriminator': 'driver',
2080 'data': {
2081 'archipelago':'BlockdevOptionsArchipelago',
2082 'blkdebug': 'BlockdevOptionsBlkdebug',
2083 'blkverify': 'BlockdevOptionsBlkverify',
2084 'bochs': 'BlockdevOptionsGenericFormat',
2085 'cloop': 'BlockdevOptionsGenericFormat',
2086 'dmg': 'BlockdevOptionsGenericFormat',
2087 'file': 'BlockdevOptionsFile',
2088 'ftp': 'BlockdevOptionsFile',
2089 'ftps': 'BlockdevOptionsFile',
2090 # TODO gluster: Wait for structured options
2091 'host_cdrom': 'BlockdevOptionsFile',
2092 'host_device':'BlockdevOptionsFile',
2093 'http': 'BlockdevOptionsFile',
2094 'https': 'BlockdevOptionsFile',
2095 # TODO iscsi: Wait for structured options
2096 # TODO nbd: Should take InetSocketAddress for 'host'?
2097 # TODO nfs: Wait for structured options
2098 'null-aio': 'BlockdevOptionsNull',
2099 'null-co': 'BlockdevOptionsNull',
2100 'parallels': 'BlockdevOptionsGenericFormat',
2101 'qcow2': 'BlockdevOptionsQcow2',
2102 'qcow': 'BlockdevOptionsGenericCOWFormat',
2103 'qed': 'BlockdevOptionsGenericCOWFormat',
2104 'quorum': 'BlockdevOptionsQuorum',
2105 'raw': 'BlockdevOptionsGenericFormat',
2106 # TODO rbd: Wait for structured options
2107 # TODO sheepdog: Wait for structured options
2108 # TODO ssh: Should take InetSocketAddress for 'host'?
2109 'tftp': 'BlockdevOptionsFile',
2110 'vdi': 'BlockdevOptionsGenericFormat',
2111 'vhdx': 'BlockdevOptionsGenericFormat',
2112 'vmdk': 'BlockdevOptionsGenericCOWFormat',
2113 'vpc': 'BlockdevOptionsGenericFormat',
2114 'vvfat': 'BlockdevOptionsVVFAT'
2115 } }
2116
2117 ##
2118 # @BlockdevRef
2119 #
2120 # Reference to a block device.
2121 #
2122 # @definition: defines a new block device inline
2123 # @reference: references the ID of an existing block device. An
2124 # empty string means that no block device should be
2125 # referenced.
2126 #
2127 # Since: 1.7
2128 ##
2129 { 'alternate': 'BlockdevRef',
2130 'data': { 'definition': 'BlockdevOptions',
2131 'reference': 'str' } }
2132
2133 ##
2134 # @blockdev-add:
2135 #
2136 # Creates a new block device. If the @id option is given at the top level, a
2137 # BlockBackend will be created; otherwise, @node-name is mandatory at the top
2138 # level and no BlockBackend will be created.
2139 #
2140 # This command is still a work in progress. It doesn't support all
2141 # block drivers among other things. Stay away from it unless you want
2142 # to help with its development.
2143 #
2144 # @options: block device options for the new device
2145 #
2146 # Since: 1.7
2147 ##
2148 { 'command': 'blockdev-add', 'data': { 'options': 'BlockdevOptions' } }
2149
2150 ##
2151 # @x-blockdev-del:
2152 #
2153 # Deletes a block device that has been added using blockdev-add.
2154 # The selected device can be either a block backend or a graph node.
2155 #
2156 # In the former case the backend will be destroyed, along with its
2157 # inserted medium if there's any. The command will fail if the backend
2158 # or its medium are in use.
2159 #
2160 # In the latter case the node will be destroyed. The command will fail
2161 # if the node is attached to a block backend or is otherwise being
2162 # used.
2163 #
2164 # One of @id or @node-name must be specified, but not both.
2165 #
2166 # This command is still a work in progress and is considered
2167 # experimental. Stay away from it unless you want to help with its
2168 # development.
2169 #
2170 # @id: #optional Name of the block backend device to delete.
2171 #
2172 # @node-name: #optional Name of the graph node to delete.
2173 #
2174 # Since: 2.5
2175 ##
2176 { 'command': 'x-blockdev-del', 'data': { '*id': 'str', '*node-name': 'str' } }
2177
2178 ##
2179 # @blockdev-open-tray:
2180 #
2181 # Opens a block device's tray. If there is a block driver state tree inserted as
2182 # a medium, it will become inaccessible to the guest (but it will remain
2183 # associated to the block device, so closing the tray will make it accessible
2184 # again).
2185 #
2186 # If the tray was already open before, this will be a no-op.
2187 #
2188 # Once the tray opens, a DEVICE_TRAY_MOVED event is emitted. There are cases in
2189 # which no such event will be generated, these include:
2190 # - if the guest has locked the tray, @force is false and the guest does not
2191 # respond to the eject request
2192 # - if the BlockBackend denoted by @device does not have a guest device attached
2193 # to it
2194 # - if the guest device does not have an actual tray
2195 #
2196 # @device: block device name
2197 #
2198 # @force: #optional if false (the default), an eject request will be sent to
2199 # the guest if it has locked the tray (and the tray will not be opened
2200 # immediately); if true, the tray will be opened regardless of whether
2201 # it is locked
2202 #
2203 # Since: 2.5
2204 ##
2205 { 'command': 'blockdev-open-tray',
2206 'data': { 'device': 'str',
2207 '*force': 'bool' } }
2208
2209 ##
2210 # @blockdev-close-tray:
2211 #
2212 # Closes a block device's tray. If there is a block driver state tree associated
2213 # with the block device (which is currently ejected), that tree will be loaded
2214 # as the medium.
2215 #
2216 # If the tray was already closed before, this will be a no-op.
2217 #
2218 # @device: block device name
2219 #
2220 # Since: 2.5
2221 ##
2222 { 'command': 'blockdev-close-tray',
2223 'data': { 'device': 'str' } }
2224
2225 ##
2226 # @x-blockdev-remove-medium:
2227 #
2228 # Removes a medium (a block driver state tree) from a block device. That block
2229 # device's tray must currently be open (unless there is no attached guest
2230 # device).
2231 #
2232 # If the tray is open and there is no medium inserted, this will be a no-op.
2233 #
2234 # This command is still a work in progress and is considered experimental.
2235 # Stay away from it unless you want to help with its development.
2236 #
2237 # @device: block device name
2238 #
2239 # Since: 2.5
2240 ##
2241 { 'command': 'x-blockdev-remove-medium',
2242 'data': { 'device': 'str' } }
2243
2244 ##
2245 # @x-blockdev-insert-medium:
2246 #
2247 # Inserts a medium (a block driver state tree) into a block device. That block
2248 # device's tray must currently be open (unless there is no attached guest
2249 # device) and there must be no medium inserted already.
2250 #
2251 # This command is still a work in progress and is considered experimental.
2252 # Stay away from it unless you want to help with its development.
2253 #
2254 # @device: block device name
2255 #
2256 # @node-name: name of a node in the block driver state graph
2257 #
2258 # Since: 2.5
2259 ##
2260 { 'command': 'x-blockdev-insert-medium',
2261 'data': { 'device': 'str',
2262 'node-name': 'str'} }
2263
2264
2265 ##
2266 # @BlockdevChangeReadOnlyMode:
2267 #
2268 # Specifies the new read-only mode of a block device subject to the
2269 # @blockdev-change-medium command.
2270 #
2271 # @retain: Retains the current read-only mode
2272 #
2273 # @read-only: Makes the device read-only
2274 #
2275 # @read-write: Makes the device writable
2276 #
2277 # Since: 2.3
2278 ##
2279 { 'enum': 'BlockdevChangeReadOnlyMode',
2280 'data': ['retain', 'read-only', 'read-write'] }
2281
2282
2283 ##
2284 # @blockdev-change-medium:
2285 #
2286 # Changes the medium inserted into a block device by ejecting the current medium
2287 # and loading a new image file which is inserted as the new medium (this command
2288 # combines blockdev-open-tray, x-blockdev-remove-medium,
2289 # x-blockdev-insert-medium and blockdev-close-tray).
2290 #
2291 # @device: block device name
2292 #
2293 # @filename: filename of the new image to be loaded
2294 #
2295 # @format: #optional, format to open the new image with (defaults to
2296 # the probed format)
2297 #
2298 # @read-only-mode: #optional, change the read-only mode of the device; defaults
2299 # to 'retain'
2300 #
2301 # Since: 2.5
2302 ##
2303 { 'command': 'blockdev-change-medium',
2304 'data': { 'device': 'str',
2305 'filename': 'str',
2306 '*format': 'str',
2307 '*read-only-mode': 'BlockdevChangeReadOnlyMode' } }
2308
2309
2310 ##
2311 # @BlockErrorAction
2312 #
2313 # An enumeration of action that has been taken when a DISK I/O occurs
2314 #
2315 # @ignore: error has been ignored
2316 #
2317 # @report: error has been reported to the device
2318 #
2319 # @stop: error caused VM to be stopped
2320 #
2321 # Since: 2.1
2322 ##
2323 { 'enum': 'BlockErrorAction',
2324 'data': [ 'ignore', 'report', 'stop' ] }
2325
2326
2327 ##
2328 # @BLOCK_IMAGE_CORRUPTED
2329 #
2330 # Emitted when a corruption has been detected in a disk image
2331 #
2332 # @device: device name. This is always present for compatibility
2333 # reasons, but it can be empty ("") if the image does not
2334 # have a device name associated.
2335 #
2336 # @node-name: #optional node name (Since: 2.4)
2337 #
2338 # @msg: informative message for human consumption, such as the kind of
2339 # corruption being detected. It should not be parsed by machine as it is
2340 # not guaranteed to be stable
2341 #
2342 # @offset: #optional, if the corruption resulted from an image access, this is
2343 # the host's access offset into the image
2344 #
2345 # @size: #optional, if the corruption resulted from an image access, this is
2346 # the access size
2347 #
2348 # fatal: if set, the image is marked corrupt and therefore unusable after this
2349 # event and must be repaired (Since 2.2; before, every
2350 # BLOCK_IMAGE_CORRUPTED event was fatal)
2351 #
2352 # Since: 1.7
2353 ##
2354 { 'event': 'BLOCK_IMAGE_CORRUPTED',
2355 'data': { 'device' : 'str',
2356 '*node-name' : 'str',
2357 'msg' : 'str',
2358 '*offset' : 'int',
2359 '*size' : 'int',
2360 'fatal' : 'bool' } }
2361
2362 ##
2363 # @BLOCK_IO_ERROR
2364 #
2365 # Emitted when a disk I/O error occurs
2366 #
2367 # @device: device name
2368 #
2369 # @operation: I/O operation
2370 #
2371 # @action: action that has been taken
2372 #
2373 # @nospace: #optional true if I/O error was caused due to a no-space
2374 # condition. This key is only present if query-block's
2375 # io-status is present, please see query-block documentation
2376 # for more information (since: 2.2)
2377 #
2378 # @reason: human readable string describing the error cause.
2379 # (This field is a debugging aid for humans, it should not
2380 # be parsed by applications) (since: 2.2)
2381 #
2382 # Note: If action is "stop", a STOP event will eventually follow the
2383 # BLOCK_IO_ERROR event
2384 #
2385 # Since: 0.13.0
2386 ##
2387 { 'event': 'BLOCK_IO_ERROR',
2388 'data': { 'device': 'str', 'operation': 'IoOperationType',
2389 'action': 'BlockErrorAction', '*nospace': 'bool',
2390 'reason': 'str' } }
2391
2392 ##
2393 # @BLOCK_JOB_COMPLETED
2394 #
2395 # Emitted when a block job has completed
2396 #
2397 # @type: job type
2398 #
2399 # @device: device name
2400 #
2401 # @len: maximum progress value
2402 #
2403 # @offset: current progress value. On success this is equal to len.
2404 # On failure this is less than len
2405 #
2406 # @speed: rate limit, bytes per second
2407 #
2408 # @error: #optional, error message. Only present on failure. This field
2409 # contains a human-readable error message. There are no semantics
2410 # other than that streaming has failed and clients should not try to
2411 # interpret the error string
2412 #
2413 # Since: 1.1
2414 ##
2415 { 'event': 'BLOCK_JOB_COMPLETED',
2416 'data': { 'type' : 'BlockJobType',
2417 'device': 'str',
2418 'len' : 'int',
2419 'offset': 'int',
2420 'speed' : 'int',
2421 '*error': 'str' } }
2422
2423 ##
2424 # @BLOCK_JOB_CANCELLED
2425 #
2426 # Emitted when a block job has been cancelled
2427 #
2428 # @type: job type
2429 #
2430 # @device: device name
2431 #
2432 # @len: maximum progress value
2433 #
2434 # @offset: current progress value. On success this is equal to len.
2435 # On failure this is less than len
2436 #
2437 # @speed: rate limit, bytes per second
2438 #
2439 # Since: 1.1
2440 ##
2441 { 'event': 'BLOCK_JOB_CANCELLED',
2442 'data': { 'type' : 'BlockJobType',
2443 'device': 'str',
2444 'len' : 'int',
2445 'offset': 'int',
2446 'speed' : 'int' } }
2447
2448 ##
2449 # @BLOCK_JOB_ERROR
2450 #
2451 # Emitted when a block job encounters an error
2452 #
2453 # @device: device name
2454 #
2455 # @operation: I/O operation
2456 #
2457 # @action: action that has been taken
2458 #
2459 # Since: 1.3
2460 ##
2461 { 'event': 'BLOCK_JOB_ERROR',
2462 'data': { 'device' : 'str',
2463 'operation': 'IoOperationType',
2464 'action' : 'BlockErrorAction' } }
2465
2466 ##
2467 # @BLOCK_JOB_READY
2468 #
2469 # Emitted when a block job is ready to complete
2470 #
2471 # @type: job type
2472 #
2473 # @device: device name
2474 #
2475 # @len: maximum progress value
2476 #
2477 # @offset: current progress value. On success this is equal to len.
2478 # On failure this is less than len
2479 #
2480 # @speed: rate limit, bytes per second
2481 #
2482 # Note: The "ready to complete" status is always reset by a @BLOCK_JOB_ERROR
2483 # event
2484 #
2485 # Since: 1.3
2486 ##
2487 { 'event': 'BLOCK_JOB_READY',
2488 'data': { 'type' : 'BlockJobType',
2489 'device': 'str',
2490 'len' : 'int',
2491 'offset': 'int',
2492 'speed' : 'int' } }
2493
2494 # @PreallocMode
2495 #
2496 # Preallocation mode of QEMU image file
2497 #
2498 # @off: no preallocation
2499 # @metadata: preallocate only for metadata
2500 # @falloc: like @full preallocation but allocate disk space by
2501 # posix_fallocate() rather than writing zeros.
2502 # @full: preallocate all data by writing zeros to device to ensure disk
2503 # space is really available. @full preallocation also sets up
2504 # metadata correctly.
2505 #
2506 # Since 2.2
2507 ##
2508 { 'enum': 'PreallocMode',
2509 'data': [ 'off', 'metadata', 'falloc', 'full' ] }
2510
2511 ##
2512 # @BLOCK_WRITE_THRESHOLD
2513 #
2514 # Emitted when writes on block device reaches or exceeds the
2515 # configured write threshold. For thin-provisioned devices, this
2516 # means the device should be extended to avoid pausing for
2517 # disk exhaustion.
2518 # The event is one shot. Once triggered, it needs to be
2519 # re-registered with another block-set-threshold command.
2520 #
2521 # @node-name: graph node name on which the threshold was exceeded.
2522 #
2523 # @amount-exceeded: amount of data which exceeded the threshold, in bytes.
2524 #
2525 # @write-threshold: last configured threshold, in bytes.
2526 #
2527 # Since: 2.3
2528 ##
2529 { 'event': 'BLOCK_WRITE_THRESHOLD',
2530 'data': { 'node-name': 'str',
2531 'amount-exceeded': 'uint64',
2532 'write-threshold': 'uint64' } }
2533
2534 ##
2535 # @block-set-write-threshold
2536 #
2537 # Change the write threshold for a block drive. An event will be delivered
2538 # if a write to this block drive crosses the configured threshold.
2539 # This is useful to transparently resize thin-provisioned drives without
2540 # the guest OS noticing.
2541 #
2542 # @node-name: graph node name on which the threshold must be set.
2543 #
2544 # @write-threshold: configured threshold for the block device, bytes.
2545 # Use 0 to disable the threshold.
2546 #
2547 # Since: 2.3
2548 ##
2549 { 'command': 'block-set-write-threshold',
2550 'data': { 'node-name': 'str', 'write-threshold': 'uint64' } }