]> git.proxmox.com Git - mirror_qemu.git/blob - qapi/block-core.json
8411d4f83ac778de4f43f7d6140973409f33bd88
[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 # @BlockdevCacheInfo
190 #
191 # Cache mode information for a block device
192 #
193 # @writeback: true if writeback mode is enabled
194 # @direct: true if the host page cache is bypassed (O_DIRECT)
195 # @no-flush: true if flush requests are ignored for the device
196 #
197 # Since: 2.3
198 ##
199 { 'struct': 'BlockdevCacheInfo',
200 'data': { 'writeback': 'bool',
201 'direct': 'bool',
202 'no-flush': 'bool' } }
203
204 ##
205 # @BlockDeviceInfo:
206 #
207 # Information about the backing device for a block device.
208 #
209 # @file: the filename of the backing device
210 #
211 # @node-name: #optional the name of the block driver node (Since 2.0)
212 #
213 # @ro: true if the backing device was open read-only
214 #
215 # @drv: the name of the block format used to open the backing device. As of
216 # 0.14.0 this can be: 'blkdebug', 'bochs', 'cloop', 'cow', 'dmg',
217 # 'file', 'file', 'ftp', 'ftps', 'host_cdrom', 'host_device',
218 # 'host_floppy', 'http', 'https', 'nbd', 'parallels', 'qcow',
219 # 'qcow2', 'raw', 'tftp', 'vdi', 'vmdk', 'vpc', 'vvfat'
220 # 2.2: 'archipelago' added, 'cow' dropped
221 # 2.3: 'host_floppy' deprecated
222 #
223 # @backing_file: #optional the name of the backing file (for copy-on-write)
224 #
225 # @backing_file_depth: number of files in the backing file chain (since: 1.2)
226 #
227 # @encrypted: true if the backing device is encrypted
228 #
229 # @encryption_key_missing: true if the backing device is encrypted but an
230 # valid encryption key is missing
231 #
232 # @detect_zeroes: detect and optimize zero writes (Since 2.1)
233 #
234 # @bps: total throughput limit in bytes per second is specified
235 #
236 # @bps_rd: read throughput limit in bytes per second is specified
237 #
238 # @bps_wr: write throughput limit in bytes per second is specified
239 #
240 # @iops: total I/O operations per second is specified
241 #
242 # @iops_rd: read I/O operations per second is specified
243 #
244 # @iops_wr: write I/O operations per second is specified
245 #
246 # @image: the info of image used (since: 1.6)
247 #
248 # @bps_max: #optional total max in bytes (Since 1.7)
249 #
250 # @bps_rd_max: #optional read max in bytes (Since 1.7)
251 #
252 # @bps_wr_max: #optional write max in bytes (Since 1.7)
253 #
254 # @iops_max: #optional total I/O operations max (Since 1.7)
255 #
256 # @iops_rd_max: #optional read I/O operations max (Since 1.7)
257 #
258 # @iops_wr_max: #optional write I/O operations max (Since 1.7)
259 #
260 # @iops_size: #optional an I/O size in bytes (Since 1.7)
261 #
262 # @cache: the cache mode used for the block device (since: 2.3)
263 #
264 # @write_threshold: configured write threshold for the device.
265 # 0 if disabled. (Since 2.3)
266 #
267 # Since: 0.14.0
268 #
269 ##
270 { 'struct': 'BlockDeviceInfo',
271 'data': { 'file': 'str', '*node-name': 'str', 'ro': 'bool', 'drv': 'str',
272 '*backing_file': 'str', 'backing_file_depth': 'int',
273 'encrypted': 'bool', 'encryption_key_missing': 'bool',
274 'detect_zeroes': 'BlockdevDetectZeroesOptions',
275 'bps': 'int', 'bps_rd': 'int', 'bps_wr': 'int',
276 'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
277 'image': 'ImageInfo',
278 '*bps_max': 'int', '*bps_rd_max': 'int',
279 '*bps_wr_max': 'int', '*iops_max': 'int',
280 '*iops_rd_max': 'int', '*iops_wr_max': 'int',
281 '*iops_size': 'int', 'cache': 'BlockdevCacheInfo',
282 'write_threshold': 'int' } }
283
284 ##
285 # @BlockDeviceIoStatus:
286 #
287 # An enumeration of block device I/O status.
288 #
289 # @ok: The last I/O operation has succeeded
290 #
291 # @failed: The last I/O operation has failed
292 #
293 # @nospace: The last I/O operation has failed due to a no-space condition
294 #
295 # Since: 1.0
296 ##
297 { 'enum': 'BlockDeviceIoStatus', 'data': [ 'ok', 'failed', 'nospace' ] }
298
299 ##
300 # @BlockDeviceMapEntry:
301 #
302 # Entry in the metadata map of the device (returned by "qemu-img map")
303 #
304 # @start: Offset in the image of the first byte described by this entry
305 # (in bytes)
306 #
307 # @length: Length of the range described by this entry (in bytes)
308 #
309 # @depth: Number of layers (0 = top image, 1 = top image's backing file, etc.)
310 # before reaching one for which the range is allocated. The value is
311 # in the range 0 to the depth of the image chain - 1.
312 #
313 # @zero: the sectors in this range read as zeros
314 #
315 # @data: reading the image will actually read data from a file (in particular,
316 # if @offset is present this means that the sectors are not simply
317 # preallocated, but contain actual data in raw format)
318 #
319 # @offset: if present, the image file stores the data for this range in
320 # raw format at the given offset.
321 #
322 # Since 1.7
323 ##
324 { 'struct': 'BlockDeviceMapEntry',
325 'data': { 'start': 'int', 'length': 'int', 'depth': 'int', 'zero': 'bool',
326 'data': 'bool', '*offset': 'int' } }
327
328 ##
329 # @DirtyBitmapStatus:
330 #
331 # An enumeration of possible states that a dirty bitmap can report to the user.
332 #
333 # @frozen: The bitmap is currently in-use by a backup operation or block job,
334 # and is immutable.
335 #
336 # @disabled: The bitmap is currently in-use by an internal operation and is
337 # read-only. It can still be deleted.
338 #
339 # @active: The bitmap is actively monitoring for new writes, and can be cleared,
340 # deleted, or used for backup operations.
341 #
342 # Since: 2.4
343 ##
344 { 'enum': 'DirtyBitmapStatus',
345 'data': ['active', 'disabled', 'frozen'] }
346
347 ##
348 # @BlockDirtyInfo:
349 #
350 # Block dirty bitmap information.
351 #
352 # @name: #optional the name of the dirty bitmap (Since 2.4)
353 #
354 # @count: number of dirty bytes according to the dirty bitmap
355 #
356 # @granularity: granularity of the dirty bitmap in bytes (since 1.4)
357 #
358 # @status: current status of the dirty bitmap (since 2.4)
359 #
360 # Since: 1.3
361 ##
362 { 'struct': 'BlockDirtyInfo',
363 'data': {'*name': 'str', 'count': 'int', 'granularity': 'uint32',
364 'status': 'DirtyBitmapStatus'} }
365
366 ##
367 # @BlockInfo:
368 #
369 # Block device information. This structure describes a virtual device and
370 # the backing device associated with it.
371 #
372 # @device: The device name associated with the virtual device.
373 #
374 # @type: This field is returned only for compatibility reasons, it should
375 # not be used (always returns 'unknown')
376 #
377 # @removable: True if the device supports removable media.
378 #
379 # @locked: True if the guest has locked this device from having its media
380 # removed
381 #
382 # @tray_open: #optional True if the device has a tray and it is open
383 # (only present if removable is true)
384 #
385 # @dirty-bitmaps: #optional dirty bitmaps information (only present if the
386 # driver has one or more dirty bitmaps) (Since 2.0)
387 #
388 # @io-status: #optional @BlockDeviceIoStatus. Only present if the device
389 # supports it and the VM is configured to stop on errors
390 # (supported device models: virtio-blk, ide, scsi-disk)
391 #
392 # @inserted: #optional @BlockDeviceInfo describing the device if media is
393 # present
394 #
395 # Since: 0.14.0
396 ##
397 { 'struct': 'BlockInfo',
398 'data': {'device': 'str', 'type': 'str', 'removable': 'bool',
399 'locked': 'bool', '*inserted': 'BlockDeviceInfo',
400 '*tray_open': 'bool', '*io-status': 'BlockDeviceIoStatus',
401 '*dirty-bitmaps': ['BlockDirtyInfo'] } }
402
403 ##
404 # @query-block:
405 #
406 # Get a list of BlockInfo for all virtual block devices.
407 #
408 # Returns: a list of @BlockInfo describing each virtual block device
409 #
410 # Since: 0.14.0
411 ##
412 { 'command': 'query-block', 'returns': ['BlockInfo'] }
413
414 ##
415 # @BlockDeviceStats:
416 #
417 # Statistics of a virtual block device or a block backing device.
418 #
419 # @rd_bytes: The number of bytes read by the device.
420 #
421 # @wr_bytes: The number of bytes written by the device.
422 #
423 # @rd_operations: The number of read operations performed by the device.
424 #
425 # @wr_operations: The number of write operations performed by the device.
426 #
427 # @flush_operations: The number of cache flush operations performed by the
428 # device (since 0.15.0)
429 #
430 # @flush_total_time_ns: Total time spend on cache flushes in nano-seconds
431 # (since 0.15.0).
432 #
433 # @wr_total_time_ns: Total time spend on writes in nano-seconds (since 0.15.0).
434 #
435 # @rd_total_time_ns: Total_time_spend on reads in nano-seconds (since 0.15.0).
436 #
437 # @wr_highest_offset: The offset after the greatest byte written to the
438 # device. The intended use of this information is for
439 # growable sparse files (like qcow2) that are used on top
440 # of a physical device.
441 #
442 # @rd_merged: Number of read requests that have been merged into another
443 # request (Since 2.3).
444 #
445 # @wr_merged: Number of write requests that have been merged into another
446 # request (Since 2.3).
447 #
448 # Since: 0.14.0
449 ##
450 { 'struct': 'BlockDeviceStats',
451 'data': {'rd_bytes': 'int', 'wr_bytes': 'int', 'rd_operations': 'int',
452 'wr_operations': 'int', 'flush_operations': 'int',
453 'flush_total_time_ns': 'int', 'wr_total_time_ns': 'int',
454 'rd_total_time_ns': 'int', 'wr_highest_offset': 'int',
455 'rd_merged': 'int', 'wr_merged': 'int' } }
456
457 ##
458 # @BlockStats:
459 #
460 # Statistics of a virtual block device or a block backing device.
461 #
462 # @device: #optional If the stats are for a virtual block device, the name
463 # corresponding to the virtual block device.
464 #
465 # @node-name: #optional The node name of the device. (Since 2.3)
466 #
467 # @stats: A @BlockDeviceStats for the device.
468 #
469 # @parent: #optional This describes the file block device if it has one.
470 #
471 # @backing: #optional This describes the backing block device if it has one.
472 # (Since 2.0)
473 #
474 # Since: 0.14.0
475 ##
476 { 'struct': 'BlockStats',
477 'data': {'*device': 'str', '*node-name': 'str',
478 'stats': 'BlockDeviceStats',
479 '*parent': 'BlockStats',
480 '*backing': 'BlockStats'} }
481
482 ##
483 # @query-blockstats:
484 #
485 # Query the @BlockStats for all virtual block devices.
486 #
487 # @query-nodes: #optional If true, the command will query all the block nodes
488 # that have a node name, in a list which will include "parent"
489 # information, but not "backing".
490 # If false or omitted, the behavior is as before - query all the
491 # device backends, recursively including their "parent" and
492 # "backing". (Since 2.3)
493 #
494 # Returns: A list of @BlockStats for each virtual block devices.
495 #
496 # Since: 0.14.0
497 ##
498 { 'command': 'query-blockstats',
499 'data': { '*query-nodes': 'bool' },
500 'returns': ['BlockStats'] }
501
502 ##
503 # @BlockdevOnError:
504 #
505 # An enumeration of possible behaviors for errors on I/O operations.
506 # The exact meaning depends on whether the I/O was initiated by a guest
507 # or by a block job
508 #
509 # @report: for guest operations, report the error to the guest;
510 # for jobs, cancel the job
511 #
512 # @ignore: ignore the error, only report a QMP event (BLOCK_IO_ERROR
513 # or BLOCK_JOB_ERROR)
514 #
515 # @enospc: same as @stop on ENOSPC, same as @report otherwise.
516 #
517 # @stop: for guest operations, stop the virtual machine;
518 # for jobs, pause the job
519 #
520 # Since: 1.3
521 ##
522 { 'enum': 'BlockdevOnError',
523 'data': ['report', 'ignore', 'enospc', 'stop'] }
524
525 ##
526 # @MirrorSyncMode:
527 #
528 # An enumeration of possible behaviors for the initial synchronization
529 # phase of storage mirroring.
530 #
531 # @top: copies data in the topmost image to the destination
532 #
533 # @full: copies data from all images to the destination
534 #
535 # @none: only copy data written from now on
536 #
537 # @dirty-bitmap: only copy data described by the dirty bitmap. Since: 2.4
538 #
539 # Since: 1.3
540 ##
541 { 'enum': 'MirrorSyncMode',
542 'data': ['top', 'full', 'none', 'dirty-bitmap'] }
543
544 ##
545 # @BlockJobType:
546 #
547 # Type of a block job.
548 #
549 # @commit: block commit job type, see "block-commit"
550 #
551 # @stream: block stream job type, see "block-stream"
552 #
553 # @mirror: drive mirror job type, see "drive-mirror"
554 #
555 # @backup: drive backup job type, see "drive-backup"
556 #
557 # Since: 1.7
558 ##
559 { 'enum': 'BlockJobType',
560 'data': ['commit', 'stream', 'mirror', 'backup'] }
561
562 ##
563 # @BlockJobInfo:
564 #
565 # Information about a long-running block device operation.
566 #
567 # @type: the job type ('stream' for image streaming)
568 #
569 # @device: the block device name
570 #
571 # @len: the maximum progress value
572 #
573 # @busy: false if the job is known to be in a quiescent state, with
574 # no pending I/O. Since 1.3.
575 #
576 # @paused: whether the job is paused or, if @busy is true, will
577 # pause itself as soon as possible. Since 1.3.
578 #
579 # @offset: the current progress value
580 #
581 # @speed: the rate limit, bytes per second
582 #
583 # @io-status: the status of the job (since 1.3)
584 #
585 # @ready: true if the job may be completed (since 2.2)
586 #
587 # Since: 1.1
588 ##
589 { 'struct': 'BlockJobInfo',
590 'data': {'type': 'str', 'device': 'str', 'len': 'int',
591 'offset': 'int', 'busy': 'bool', 'paused': 'bool', 'speed': 'int',
592 'io-status': 'BlockDeviceIoStatus', 'ready': 'bool'} }
593
594 ##
595 # @query-block-jobs:
596 #
597 # Return information about long-running block device operations.
598 #
599 # Returns: a list of @BlockJobInfo for each active block job
600 #
601 # Since: 1.1
602 ##
603 { 'command': 'query-block-jobs', 'returns': ['BlockJobInfo'] }
604
605 ##
606 # @block_passwd:
607 #
608 # This command sets the password of a block device that has not been open
609 # with a password and requires one.
610 #
611 # The two cases where this can happen are a block device is created through
612 # QEMU's initial command line or a block device is changed through the legacy
613 # @change interface.
614 #
615 # In the event that the block device is created through the initial command
616 # line, the VM will start in the stopped state regardless of whether '-S' is
617 # used. The intention is for a management tool to query the block devices to
618 # determine which ones are encrypted, set the passwords with this command, and
619 # then start the guest with the @cont command.
620 #
621 # Either @device or @node-name must be set but not both.
622 #
623 # @device: #optional the name of the block backend device to set the password on
624 #
625 # @node-name: #optional graph node name to set the password on (Since 2.0)
626 #
627 # @password: the password to use for the device
628 #
629 # Returns: nothing on success
630 # If @device is not a valid block device, DeviceNotFound
631 # If @device is not encrypted, DeviceNotEncrypted
632 #
633 # Notes: Not all block formats support encryption and some that do are not
634 # able to validate that a password is correct. Disk corruption may
635 # occur if an invalid password is specified.
636 #
637 # Since: 0.14.0
638 ##
639 { 'command': 'block_passwd', 'data': {'*device': 'str',
640 '*node-name': 'str', 'password': 'str'} }
641
642 ##
643 # @block_resize
644 #
645 # Resize a block image while a guest is running.
646 #
647 # Either @device or @node-name must be set but not both.
648 #
649 # @device: #optional the name of the device to get the image resized
650 #
651 # @node-name: #optional graph node name to get the image resized (Since 2.0)
652 #
653 # @size: new image size in bytes
654 #
655 # Returns: nothing on success
656 # If @device is not a valid block device, DeviceNotFound
657 #
658 # Since: 0.14.0
659 ##
660 { 'command': 'block_resize', 'data': { '*device': 'str',
661 '*node-name': 'str',
662 'size': 'int' }}
663
664 ##
665 # @NewImageMode
666 #
667 # An enumeration that tells QEMU how to set the backing file path in
668 # a new image file.
669 #
670 # @existing: QEMU should look for an existing image file.
671 #
672 # @absolute-paths: QEMU should create a new image with absolute paths
673 # for the backing file. If there is no backing file available, the new
674 # image will not be backed either.
675 #
676 # Since: 1.1
677 ##
678 { 'enum': 'NewImageMode',
679 'data': [ 'existing', 'absolute-paths' ] }
680
681 ##
682 # @BlockdevSnapshot
683 #
684 # Either @device or @node-name must be set but not both.
685 #
686 # @device: #optional the name of the device to generate the snapshot from.
687 #
688 # @node-name: #optional graph node name to generate the snapshot from (Since 2.0)
689 #
690 # @snapshot-file: the target of the new image. A new file will be created.
691 #
692 # @snapshot-node-name: #optional the graph node name of the new image (Since 2.0)
693 #
694 # @format: #optional the format of the snapshot image, default is 'qcow2'.
695 #
696 # @mode: #optional whether and how QEMU should create a new image, default is
697 # 'absolute-paths'.
698 ##
699 { 'struct': 'BlockdevSnapshot',
700 'data': { '*device': 'str', '*node-name': 'str',
701 'snapshot-file': 'str', '*snapshot-node-name': 'str',
702 '*format': 'str', '*mode': 'NewImageMode' } }
703
704 ##
705 # @DriveBackup
706 #
707 # @device: the name of the device which should be copied.
708 #
709 # @target: the target of the new image. If the file exists, or if it
710 # is a device, the existing file/device will be used as the new
711 # destination. If it does not exist, a new file will be created.
712 #
713 # @format: #optional the format of the new destination, default is to
714 # probe if @mode is 'existing', else the format of the source
715 #
716 # @sync: what parts of the disk image should be copied to the destination
717 # (all the disk, only the sectors allocated in the topmost image, from a
718 # dirty bitmap, or only new I/O).
719 #
720 # @mode: #optional whether and how QEMU should create a new image, default is
721 # 'absolute-paths'.
722 #
723 # @speed: #optional the maximum speed, in bytes per second
724 #
725 # @bitmap: #optional the name of dirty bitmap if sync is "dirty-bitmap".
726 # Must be present if sync is "dirty-bitmap", must NOT be present
727 # otherwise. (Since 2.4)
728 #
729 # @on-source-error: #optional the action to take on an error on the source,
730 # default 'report'. 'stop' and 'enospc' can only be used
731 # if the block device supports io-status (see BlockInfo).
732 #
733 # @on-target-error: #optional the action to take on an error on the target,
734 # default 'report' (no limitations, since this applies to
735 # a different block device than @device).
736 #
737 # Note that @on-source-error and @on-target-error only affect background I/O.
738 # If an error occurs during a guest write request, the device's rerror/werror
739 # actions will be used.
740 #
741 # Since: 1.6
742 ##
743 { 'struct': 'DriveBackup',
744 'data': { 'device': 'str', 'target': 'str', '*format': 'str',
745 'sync': 'MirrorSyncMode', '*mode': 'NewImageMode',
746 '*speed': 'int', '*bitmap': 'str',
747 '*on-source-error': 'BlockdevOnError',
748 '*on-target-error': 'BlockdevOnError' } }
749
750 ##
751 # @BlockdevBackup
752 #
753 # @device: the name of the device which should be copied.
754 #
755 # @target: the name of the backup target device.
756 #
757 # @sync: what parts of the disk image should be copied to the destination
758 # (all the disk, only the sectors allocated in the topmost image, or
759 # only new I/O).
760 #
761 # @speed: #optional the maximum speed, in bytes per second. The default is 0,
762 # for unlimited.
763 #
764 # @on-source-error: #optional the action to take on an error on the source,
765 # default 'report'. 'stop' and 'enospc' can only be used
766 # if the block device supports io-status (see BlockInfo).
767 #
768 # @on-target-error: #optional the action to take on an error on the target,
769 # default 'report' (no limitations, since this applies to
770 # a different block device than @device).
771 #
772 # Note that @on-source-error and @on-target-error only affect background I/O.
773 # If an error occurs during a guest write request, the device's rerror/werror
774 # actions will be used.
775 #
776 # Since: 2.3
777 ##
778 { 'struct': 'BlockdevBackup',
779 'data': { 'device': 'str', 'target': 'str',
780 'sync': 'MirrorSyncMode',
781 '*speed': 'int',
782 '*on-source-error': 'BlockdevOnError',
783 '*on-target-error': 'BlockdevOnError' } }
784
785 ##
786 # @blockdev-snapshot-sync
787 #
788 # Generates a synchronous snapshot of a block device.
789 #
790 # For the arguments, see the documentation of BlockdevSnapshot.
791 #
792 # Returns: nothing on success
793 # If @device is not a valid block device, DeviceNotFound
794 #
795 # Since 0.14.0
796 ##
797 { 'command': 'blockdev-snapshot-sync',
798 'data': 'BlockdevSnapshot' }
799
800 ##
801 # @change-backing-file
802 #
803 # Change the backing file in the image file metadata. This does not
804 # cause QEMU to reopen the image file to reparse the backing filename
805 # (it may, however, perform a reopen to change permissions from
806 # r/o -> r/w -> r/o, if needed). The new backing file string is written
807 # into the image file metadata, and the QEMU internal strings are
808 # updated.
809 #
810 # @image-node-name: The name of the block driver state node of the
811 # image to modify.
812 #
813 # @device: The name of the device that owns image-node-name.
814 #
815 # @backing-file: The string to write as the backing file. This
816 # string is not validated, so care should be taken
817 # when specifying the string or the image chain may
818 # not be able to be reopened again.
819 #
820 # Since: 2.1
821 ##
822 { 'command': 'change-backing-file',
823 'data': { 'device': 'str', 'image-node-name': 'str',
824 'backing-file': 'str' } }
825
826 ##
827 # @block-commit
828 #
829 # Live commit of data from overlay image nodes into backing nodes - i.e.,
830 # writes data between 'top' and 'base' into 'base'.
831 #
832 # @device: the name of the device
833 #
834 # @base: #optional The file name of the backing image to write data into.
835 # If not specified, this is the deepest backing image
836 #
837 # @top: #optional The file name of the backing image within the image chain,
838 # which contains the topmost data to be committed down. If
839 # not specified, this is the active layer.
840 #
841 # @backing-file: #optional The backing file string to write into the overlay
842 # image of 'top'. If 'top' is the active layer,
843 # specifying a backing file string is an error. This
844 # filename is not validated.
845 #
846 # If a pathname string is such that it cannot be
847 # resolved by QEMU, that means that subsequent QMP or
848 # HMP commands must use node-names for the image in
849 # question, as filename lookup methods will fail.
850 #
851 # If not specified, QEMU will automatically determine
852 # the backing file string to use, or error out if
853 # there is no obvious choice. Care should be taken
854 # when specifying the string, to specify a valid
855 # filename or protocol.
856 # (Since 2.1)
857 #
858 # If top == base, that is an error.
859 # If top == active, the job will not be completed by itself,
860 # user needs to complete the job with the block-job-complete
861 # command after getting the ready event. (Since 2.0)
862 #
863 # If the base image is smaller than top, then the base image
864 # will be resized to be the same size as top. If top is
865 # smaller than the base image, the base will not be
866 # truncated. If you want the base image size to match the
867 # size of the smaller top, you can safely truncate it
868 # yourself once the commit operation successfully completes.
869 #
870 # @speed: #optional the maximum speed, in bytes per second
871 #
872 # Returns: Nothing on success
873 # If commit or stream is already active on this device, DeviceInUse
874 # If @device does not exist, DeviceNotFound
875 # If image commit is not supported by this device, NotSupported
876 # If @base or @top is invalid, a generic error is returned
877 # If @speed is invalid, InvalidParameter
878 #
879 # Since: 1.3
880 #
881 ##
882 { 'command': 'block-commit',
883 'data': { 'device': 'str', '*base': 'str', '*top': 'str',
884 '*backing-file': 'str', '*speed': 'int' } }
885
886 ##
887 # @drive-backup
888 #
889 # Start a point-in-time copy of a block device to a new destination. The
890 # status of ongoing drive-backup operations can be checked with
891 # query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
892 # The operation can be stopped before it has completed using the
893 # block-job-cancel command.
894 #
895 # For the arguments, see the documentation of DriveBackup.
896 #
897 # Returns: nothing on success
898 # If @device is not a valid block device, DeviceNotFound
899 #
900 # Since 1.6
901 ##
902 { 'command': 'drive-backup', 'data': 'DriveBackup' }
903
904 ##
905 # @blockdev-backup
906 #
907 # Start a point-in-time copy of a block device to a new destination. The
908 # status of ongoing blockdev-backup operations can be checked with
909 # query-block-jobs where the BlockJobInfo.type field has the value 'backup'.
910 # The operation can be stopped before it has completed using the
911 # block-job-cancel command.
912 #
913 # For the arguments, see the documentation of BlockdevBackup.
914 #
915 # Since 2.3
916 ##
917 { 'command': 'blockdev-backup', 'data': 'BlockdevBackup' }
918
919
920 ##
921 # @query-named-block-nodes
922 #
923 # Get the named block driver list
924 #
925 # Returns: the list of BlockDeviceInfo
926 #
927 # Since 2.0
928 ##
929 { 'command': 'query-named-block-nodes', 'returns': [ 'BlockDeviceInfo' ] }
930
931 ##
932 # @drive-mirror
933 #
934 # Start mirroring a block device's writes to a new destination.
935 #
936 # @device: the name of the device whose writes should be mirrored.
937 #
938 # @target: the target of the new image. If the file exists, or if it
939 # is a device, the existing file/device will be used as the new
940 # destination. If it does not exist, a new file will be created.
941 #
942 # @format: #optional the format of the new destination, default is to
943 # probe if @mode is 'existing', else the format of the source
944 #
945 # @node-name: #optional the new block driver state node name in the graph
946 # (Since 2.1)
947 #
948 # @replaces: #optional with sync=full graph node name to be replaced by the new
949 # image when a whole image copy is done. This can be used to repair
950 # broken Quorum files. (Since 2.1)
951 #
952 # @mode: #optional whether and how QEMU should create a new image, default is
953 # 'absolute-paths'.
954 #
955 # @speed: #optional the maximum speed, in bytes per second
956 #
957 # @sync: what parts of the disk image should be copied to the destination
958 # (all the disk, only the sectors allocated in the topmost image, or
959 # only new I/O).
960 #
961 # @granularity: #optional granularity of the dirty bitmap, default is 64K
962 # if the image format doesn't have clusters, 4K if the clusters
963 # are smaller than that, else the cluster size. Must be a
964 # power of 2 between 512 and 64M (since 1.4).
965 #
966 # @buf-size: #optional maximum amount of data in flight from source to
967 # target (since 1.4).
968 #
969 # @on-source-error: #optional the action to take on an error on the source,
970 # default 'report'. 'stop' and 'enospc' can only be used
971 # if the block device supports io-status (see BlockInfo).
972 #
973 # @on-target-error: #optional the action to take on an error on the target,
974 # default 'report' (no limitations, since this applies to
975 # a different block device than @device).
976 #
977 # Returns: nothing on success
978 # If @device is not a valid block device, DeviceNotFound
979 #
980 # Since 1.3
981 ##
982 { 'command': 'drive-mirror',
983 'data': { 'device': 'str', 'target': 'str', '*format': 'str',
984 '*node-name': 'str', '*replaces': 'str',
985 'sync': 'MirrorSyncMode', '*mode': 'NewImageMode',
986 '*speed': 'int', '*granularity': 'uint32',
987 '*buf-size': 'int', '*on-source-error': 'BlockdevOnError',
988 '*on-target-error': 'BlockdevOnError' } }
989
990 ##
991 # @BlockDirtyBitmap
992 #
993 # @node: name of device/node which the bitmap is tracking
994 #
995 # @name: name of the dirty bitmap
996 #
997 # Since 2.4
998 ##
999 { 'struct': 'BlockDirtyBitmap',
1000 'data': { 'node': 'str', 'name': 'str' } }
1001
1002 ##
1003 # @BlockDirtyBitmapAdd
1004 #
1005 # @node: name of device/node which the bitmap is tracking
1006 #
1007 # @name: name of the dirty bitmap
1008 #
1009 # @granularity: #optional the bitmap granularity, default is 64k for
1010 # block-dirty-bitmap-add
1011 #
1012 # Since 2.4
1013 ##
1014 { 'struct': 'BlockDirtyBitmapAdd',
1015 'data': { 'node': 'str', 'name': 'str', '*granularity': 'uint32' } }
1016
1017 ##
1018 # @block-dirty-bitmap-add
1019 #
1020 # Create a dirty bitmap with a name on the node
1021 #
1022 # Returns: nothing on success
1023 # If @node is not a valid block device or node, DeviceNotFound
1024 # If @name is already taken, GenericError with an explanation
1025 #
1026 # Since 2.4
1027 ##
1028 { 'command': 'block-dirty-bitmap-add',
1029 'data': 'BlockDirtyBitmapAdd' }
1030
1031 ##
1032 # @block-dirty-bitmap-remove
1033 #
1034 # Remove a dirty bitmap on the node
1035 #
1036 # Returns: nothing on success
1037 # If @node is not a valid block device or node, DeviceNotFound
1038 # If @name is not found, GenericError with an explanation
1039 # if @name is frozen by an operation, GenericError
1040 #
1041 # Since 2.4
1042 ##
1043 { 'command': 'block-dirty-bitmap-remove',
1044 'data': 'BlockDirtyBitmap' }
1045
1046 ##
1047 # @block-dirty-bitmap-clear
1048 #
1049 # Clear (reset) a dirty bitmap on the device
1050 #
1051 # Returns: nothing on success
1052 # If @node is not a valid block device, DeviceNotFound
1053 # If @name is not found, GenericError with an explanation
1054 #
1055 # Since 2.4
1056 ##
1057 { 'command': 'block-dirty-bitmap-clear',
1058 'data': 'BlockDirtyBitmap' }
1059
1060 ##
1061 # @block_set_io_throttle:
1062 #
1063 # Change I/O throttle limits for a block drive.
1064 #
1065 # @device: The name of the device
1066 #
1067 # @bps: total throughput limit in bytes per second
1068 #
1069 # @bps_rd: read throughput limit in bytes per second
1070 #
1071 # @bps_wr: write throughput limit in bytes per second
1072 #
1073 # @iops: total I/O operations per second
1074 #
1075 # @ops_rd: read I/O operations per second
1076 #
1077 # @iops_wr: write I/O operations per second
1078 #
1079 # @bps_max: #optional total max in bytes (Since 1.7)
1080 #
1081 # @bps_rd_max: #optional read max in bytes (Since 1.7)
1082 #
1083 # @bps_wr_max: #optional write max in bytes (Since 1.7)
1084 #
1085 # @iops_max: #optional total I/O operations max (Since 1.7)
1086 #
1087 # @iops_rd_max: #optional read I/O operations max (Since 1.7)
1088 #
1089 # @iops_wr_max: #optional write I/O operations max (Since 1.7)
1090 #
1091 # @iops_size: #optional an I/O size in bytes (Since 1.7)
1092 #
1093 # Returns: Nothing on success
1094 # If @device is not a valid block device, DeviceNotFound
1095 #
1096 # Since: 1.1
1097 ##
1098 { 'command': 'block_set_io_throttle',
1099 'data': { 'device': 'str', 'bps': 'int', 'bps_rd': 'int', 'bps_wr': 'int',
1100 'iops': 'int', 'iops_rd': 'int', 'iops_wr': 'int',
1101 '*bps_max': 'int', '*bps_rd_max': 'int',
1102 '*bps_wr_max': 'int', '*iops_max': 'int',
1103 '*iops_rd_max': 'int', '*iops_wr_max': 'int',
1104 '*iops_size': 'int' } }
1105
1106 ##
1107 # @block-stream:
1108 #
1109 # Copy data from a backing file into a block device.
1110 #
1111 # The block streaming operation is performed in the background until the entire
1112 # backing file has been copied. This command returns immediately once streaming
1113 # has started. The status of ongoing block streaming operations can be checked
1114 # with query-block-jobs. The operation can be stopped before it has completed
1115 # using the block-job-cancel command.
1116 #
1117 # If a base file is specified then sectors are not copied from that base file and
1118 # its backing chain. When streaming completes the image file will have the base
1119 # file as its backing file. This can be used to stream a subset of the backing
1120 # file chain instead of flattening the entire image.
1121 #
1122 # On successful completion the image file is updated to drop the backing file
1123 # and the BLOCK_JOB_COMPLETED event is emitted.
1124 #
1125 # @device: the device name
1126 #
1127 # @base: #optional the common backing file name
1128 #
1129 # @backing-file: #optional The backing file string to write into the active
1130 # layer. This filename is not validated.
1131 #
1132 # If a pathname string is such that it cannot be
1133 # resolved by QEMU, that means that subsequent QMP or
1134 # HMP commands must use node-names for the image in
1135 # question, as filename lookup methods will fail.
1136 #
1137 # If not specified, QEMU will automatically determine
1138 # the backing file string to use, or error out if there
1139 # is no obvious choice. Care should be taken when
1140 # specifying the string, to specify a valid filename or
1141 # protocol.
1142 # (Since 2.1)
1143 #
1144 # @speed: #optional the maximum speed, in bytes per second
1145 #
1146 # @on-error: #optional the action to take on an error (default report).
1147 # 'stop' and 'enospc' can only be used if the block device
1148 # supports io-status (see BlockInfo). Since 1.3.
1149 #
1150 # Returns: Nothing on success
1151 # If @device does not exist, DeviceNotFound
1152 #
1153 # Since: 1.1
1154 ##
1155 { 'command': 'block-stream',
1156 'data': { 'device': 'str', '*base': 'str', '*backing-file': 'str',
1157 '*speed': 'int', '*on-error': 'BlockdevOnError' } }
1158
1159 ##
1160 # @block-job-set-speed:
1161 #
1162 # Set maximum speed for a background block operation.
1163 #
1164 # This command can only be issued when there is an active block job.
1165 #
1166 # Throttling can be disabled by setting the speed to 0.
1167 #
1168 # @device: the device name
1169 #
1170 # @speed: the maximum speed, in bytes per second, or 0 for unlimited.
1171 # Defaults to 0.
1172 #
1173 # Returns: Nothing on success
1174 # If no background operation is active on this device, DeviceNotActive
1175 #
1176 # Since: 1.1
1177 ##
1178 { 'command': 'block-job-set-speed',
1179 'data': { 'device': 'str', 'speed': 'int' } }
1180
1181 ##
1182 # @block-job-cancel:
1183 #
1184 # Stop an active background block operation.
1185 #
1186 # This command returns immediately after marking the active background block
1187 # operation for cancellation. It is an error to call this command if no
1188 # operation is in progress.
1189 #
1190 # The operation will cancel as soon as possible and then emit the
1191 # BLOCK_JOB_CANCELLED event. Before that happens the job is still visible when
1192 # enumerated using query-block-jobs.
1193 #
1194 # For streaming, the image file retains its backing file unless the streaming
1195 # operation happens to complete just as it is being cancelled. A new streaming
1196 # operation can be started at a later time to finish copying all data from the
1197 # backing file.
1198 #
1199 # @device: the device name
1200 #
1201 # @force: #optional whether to allow cancellation of a paused job (default
1202 # false). Since 1.3.
1203 #
1204 # Returns: Nothing on success
1205 # If no background operation is active on this device, DeviceNotActive
1206 #
1207 # Since: 1.1
1208 ##
1209 { 'command': 'block-job-cancel', 'data': { 'device': 'str', '*force': 'bool' } }
1210
1211 ##
1212 # @block-job-pause:
1213 #
1214 # Pause an active background block operation.
1215 #
1216 # This command returns immediately after marking the active background block
1217 # operation for pausing. It is an error to call this command if no
1218 # operation is in progress. Pausing an already paused job has no cumulative
1219 # effect; a single block-job-resume command will resume the job.
1220 #
1221 # The operation will pause as soon as possible. No event is emitted when
1222 # the operation is actually paused. Cancelling a paused job automatically
1223 # resumes it.
1224 #
1225 # @device: the device name
1226 #
1227 # Returns: Nothing on success
1228 # If no background operation is active on this device, DeviceNotActive
1229 #
1230 # Since: 1.3
1231 ##
1232 { 'command': 'block-job-pause', 'data': { 'device': 'str' } }
1233
1234 ##
1235 # @block-job-resume:
1236 #
1237 # Resume an active background block operation.
1238 #
1239 # This command returns immediately after resuming a paused background block
1240 # operation. It is an error to call this command if no operation is in
1241 # progress. Resuming an already running job is not an error.
1242 #
1243 # This command also clears the error status of the job.
1244 #
1245 # @device: the device name
1246 #
1247 # Returns: Nothing on success
1248 # If no background operation is active on this device, DeviceNotActive
1249 #
1250 # Since: 1.3
1251 ##
1252 { 'command': 'block-job-resume', 'data': { 'device': 'str' } }
1253
1254 ##
1255 # @block-job-complete:
1256 #
1257 # Manually trigger completion of an active background block operation. This
1258 # is supported for drive mirroring, where it also switches the device to
1259 # write to the target path only. The ability to complete is signaled with
1260 # a BLOCK_JOB_READY event.
1261 #
1262 # This command completes an active background block operation synchronously.
1263 # The ordering of this command's return with the BLOCK_JOB_COMPLETED event
1264 # is not defined. Note that if an I/O error occurs during the processing of
1265 # this command: 1) the command itself will fail; 2) the error will be processed
1266 # according to the rerror/werror arguments that were specified when starting
1267 # the operation.
1268 #
1269 # A cancelled or paused job cannot be completed.
1270 #
1271 # @device: the device name
1272 #
1273 # Returns: Nothing on success
1274 # If no background operation is active on this device, DeviceNotActive
1275 #
1276 # Since: 1.3
1277 ##
1278 { 'command': 'block-job-complete', 'data': { 'device': 'str' } }
1279
1280 ##
1281 # @BlockdevDiscardOptions
1282 #
1283 # Determines how to handle discard requests.
1284 #
1285 # @ignore: Ignore the request
1286 # @unmap: Forward as an unmap request
1287 #
1288 # Since: 1.7
1289 ##
1290 { 'enum': 'BlockdevDiscardOptions',
1291 'data': [ 'ignore', 'unmap' ] }
1292
1293 ##
1294 # @BlockdevDetectZeroesOptions
1295 #
1296 # Describes the operation mode for the automatic conversion of plain
1297 # zero writes by the OS to driver specific optimized zero write commands.
1298 #
1299 # @off: Disabled (default)
1300 # @on: Enabled
1301 # @unmap: Enabled and even try to unmap blocks if possible. This requires
1302 # also that @BlockdevDiscardOptions is set to unmap for this device.
1303 #
1304 # Since: 2.1
1305 ##
1306 { 'enum': 'BlockdevDetectZeroesOptions',
1307 'data': [ 'off', 'on', 'unmap' ] }
1308
1309 ##
1310 # @BlockdevAioOptions
1311 #
1312 # Selects the AIO backend to handle I/O requests
1313 #
1314 # @threads: Use qemu's thread pool
1315 # @native: Use native AIO backend (only Linux and Windows)
1316 #
1317 # Since: 1.7
1318 ##
1319 { 'enum': 'BlockdevAioOptions',
1320 'data': [ 'threads', 'native' ] }
1321
1322 ##
1323 # @BlockdevCacheOptions
1324 #
1325 # Includes cache-related options for block devices
1326 #
1327 # @writeback: #optional enables writeback mode for any caches (default: true)
1328 # @direct: #optional enables use of O_DIRECT (bypass the host page cache;
1329 # default: false)
1330 # @no-flush: #optional ignore any flush requests for the device (default:
1331 # false)
1332 #
1333 # Since: 1.7
1334 ##
1335 { 'struct': 'BlockdevCacheOptions',
1336 'data': { '*writeback': 'bool',
1337 '*direct': 'bool',
1338 '*no-flush': 'bool' } }
1339
1340 ##
1341 # @BlockdevDriver
1342 #
1343 # Drivers that are supported in block device operations.
1344 #
1345 # @host_device, @host_cdrom, @host_floppy: Since 2.1
1346 # @host_floppy: deprecated since 2.3
1347 #
1348 # Since: 2.0
1349 ##
1350 { 'enum': 'BlockdevDriver',
1351 'data': [ 'archipelago', 'blkdebug', 'blkverify', 'bochs', 'cloop',
1352 'dmg', 'file', 'ftp', 'ftps', 'host_cdrom', 'host_device',
1353 'host_floppy', 'http', 'https', 'null-aio', 'null-co', 'parallels',
1354 'qcow', 'qcow2', 'qed', 'quorum', 'raw', 'tftp', 'vdi', 'vhdx',
1355 'vmdk', 'vpc', 'vvfat' ] }
1356
1357 ##
1358 # @BlockdevOptionsBase
1359 #
1360 # Options that are available for all block devices, independent of the block
1361 # driver.
1362 #
1363 # @driver: block driver name
1364 # @id: #optional id by which the new block device can be referred to.
1365 # This is a required option on the top level of blockdev-add, and
1366 # currently not allowed on any other level.
1367 # @node-name: #optional the name of a block driver state node (Since 2.0)
1368 # @discard: #optional discard-related options (default: ignore)
1369 # @cache: #optional cache-related options
1370 # @aio: #optional AIO backend (default: threads)
1371 # @rerror: #optional how to handle read errors on the device
1372 # (default: report)
1373 # @werror: #optional how to handle write errors on the device
1374 # (default: enospc)
1375 # @read-only: #optional whether the block device should be read-only
1376 # (default: false)
1377 # @detect-zeroes: #optional detect and optimize zero writes (Since 2.1)
1378 # (default: off)
1379 #
1380 # Since: 1.7
1381 ##
1382 { 'struct': 'BlockdevOptionsBase',
1383 'data': { 'driver': 'BlockdevDriver',
1384 '*id': 'str',
1385 '*node-name': 'str',
1386 '*discard': 'BlockdevDiscardOptions',
1387 '*cache': 'BlockdevCacheOptions',
1388 '*aio': 'BlockdevAioOptions',
1389 '*rerror': 'BlockdevOnError',
1390 '*werror': 'BlockdevOnError',
1391 '*read-only': 'bool',
1392 '*detect-zeroes': 'BlockdevDetectZeroesOptions' } }
1393
1394 ##
1395 # @BlockdevOptionsFile
1396 #
1397 # Driver specific block device options for the file backend and similar
1398 # protocols.
1399 #
1400 # @filename: path to the image file
1401 #
1402 # Since: 1.7
1403 ##
1404 { 'struct': 'BlockdevOptionsFile',
1405 'data': { 'filename': 'str' } }
1406
1407 ##
1408 # @BlockdevOptionsNull
1409 #
1410 # Driver specific block device options for the null backend.
1411 #
1412 # @size: #optional size of the device in bytes.
1413 # @latency-ns: #optional emulated latency (in nanoseconds) in processing
1414 # requests. Default to zero which completes requests immediately.
1415 # (Since 2.4)
1416 #
1417 # Since: 2.2
1418 ##
1419 { 'struct': 'BlockdevOptionsNull',
1420 'data': { '*size': 'int', '*latency-ns': 'uint64' } }
1421
1422 ##
1423 # @BlockdevOptionsVVFAT
1424 #
1425 # Driver specific block device options for the vvfat protocol.
1426 #
1427 # @dir: directory to be exported as FAT image
1428 # @fat-type: #optional FAT type: 12, 16 or 32
1429 # @floppy: #optional whether to export a floppy image (true) or
1430 # partitioned hard disk (false; default)
1431 # @rw: #optional whether to allow write operations (default: false)
1432 #
1433 # Since: 1.7
1434 ##
1435 { 'struct': 'BlockdevOptionsVVFAT',
1436 'data': { 'dir': 'str', '*fat-type': 'int', '*floppy': 'bool',
1437 '*rw': 'bool' } }
1438
1439 ##
1440 # @BlockdevOptionsGenericFormat
1441 #
1442 # Driver specific block device options for image format that have no option
1443 # besides their data source.
1444 #
1445 # @file: reference to or definition of the data source block device
1446 #
1447 # Since: 1.7
1448 ##
1449 { 'struct': 'BlockdevOptionsGenericFormat',
1450 'data': { 'file': 'BlockdevRef' } }
1451
1452 ##
1453 # @BlockdevOptionsGenericCOWFormat
1454 #
1455 # Driver specific block device options for image format that have no option
1456 # besides their data source and an optional backing file.
1457 #
1458 # @backing: #optional reference to or definition of the backing file block
1459 # device (if missing, taken from the image file content). It is
1460 # allowed to pass an empty string here in order to disable the
1461 # default backing file.
1462 #
1463 # Since: 1.7
1464 ##
1465 { 'struct': 'BlockdevOptionsGenericCOWFormat',
1466 'base': 'BlockdevOptionsGenericFormat',
1467 'data': { '*backing': 'BlockdevRef' } }
1468
1469 ##
1470 # @Qcow2OverlapCheckMode
1471 #
1472 # General overlap check modes.
1473 #
1474 # @none: Do not perform any checks
1475 #
1476 # @constant: Perform only checks which can be done in constant time and
1477 # without reading anything from disk
1478 #
1479 # @cached: Perform only checks which can be done without reading anything
1480 # from disk
1481 #
1482 # @all: Perform all available overlap checks
1483 #
1484 # Since: 2.2
1485 ##
1486 { 'enum': 'Qcow2OverlapCheckMode',
1487 'data': [ 'none', 'constant', 'cached', 'all' ] }
1488
1489 ##
1490 # @Qcow2OverlapCheckFlags
1491 #
1492 # Structure of flags for each metadata structure. Setting a field to 'true'
1493 # makes qemu guard that structure against unintended overwriting. The default
1494 # value is chosen according to the template given.
1495 #
1496 # @template: Specifies a template mode which can be adjusted using the other
1497 # flags, defaults to 'cached'
1498 #
1499 # Since: 2.2
1500 ##
1501 { 'struct': 'Qcow2OverlapCheckFlags',
1502 'data': { '*template': 'Qcow2OverlapCheckMode',
1503 '*main-header': 'bool',
1504 '*active-l1': 'bool',
1505 '*active-l2': 'bool',
1506 '*refcount-table': 'bool',
1507 '*refcount-block': 'bool',
1508 '*snapshot-table': 'bool',
1509 '*inactive-l1': 'bool',
1510 '*inactive-l2': 'bool' } }
1511
1512 ##
1513 # @Qcow2OverlapChecks
1514 #
1515 # Specifies which metadata structures should be guarded against unintended
1516 # overwriting.
1517 #
1518 # @flags: set of flags for separate specification of each metadata structure
1519 # type
1520 #
1521 # @mode: named mode which chooses a specific set of flags
1522 #
1523 # Since: 2.2
1524 ##
1525 { 'alternate': 'Qcow2OverlapChecks',
1526 'data': { 'flags': 'Qcow2OverlapCheckFlags',
1527 'mode': 'Qcow2OverlapCheckMode' } }
1528
1529 ##
1530 # @BlockdevOptionsQcow2
1531 #
1532 # Driver specific block device options for qcow2.
1533 #
1534 # @lazy-refcounts: #optional whether to enable the lazy refcounts
1535 # feature (default is taken from the image file)
1536 #
1537 # @pass-discard-request: #optional whether discard requests to the qcow2
1538 # device should be forwarded to the data source
1539 #
1540 # @pass-discard-snapshot: #optional whether discard requests for the data source
1541 # should be issued when a snapshot operation (e.g.
1542 # deleting a snapshot) frees clusters in the qcow2 file
1543 #
1544 # @pass-discard-other: #optional whether discard requests for the data source
1545 # should be issued on other occasions where a cluster
1546 # gets freed
1547 #
1548 # @overlap-check: #optional which overlap checks to perform for writes
1549 # to the image, defaults to 'cached' (since 2.2)
1550 #
1551 # @cache-size: #optional the maximum total size of the L2 table and
1552 # refcount block caches in bytes (since 2.2)
1553 #
1554 # @l2-cache-size: #optional the maximum size of the L2 table cache in
1555 # bytes (since 2.2)
1556 #
1557 # @refcount-cache-size: #optional the maximum size of the refcount block cache
1558 # in bytes (since 2.2)
1559 #
1560 # Since: 1.7
1561 ##
1562 { 'struct': 'BlockdevOptionsQcow2',
1563 'base': 'BlockdevOptionsGenericCOWFormat',
1564 'data': { '*lazy-refcounts': 'bool',
1565 '*pass-discard-request': 'bool',
1566 '*pass-discard-snapshot': 'bool',
1567 '*pass-discard-other': 'bool',
1568 '*overlap-check': 'Qcow2OverlapChecks',
1569 '*cache-size': 'int',
1570 '*l2-cache-size': 'int',
1571 '*refcount-cache-size': 'int' } }
1572
1573
1574 ##
1575 # @BlockdevOptionsArchipelago
1576 #
1577 # Driver specific block device options for Archipelago.
1578 #
1579 # @volume: Name of the Archipelago volume image
1580 #
1581 # @mport: #optional The port number on which mapperd is
1582 # listening. This is optional
1583 # and if not specified, QEMU will make Archipelago
1584 # use the default port (1001).
1585 #
1586 # @vport: #optional The port number on which vlmcd is
1587 # listening. This is optional
1588 # and if not specified, QEMU will make Archipelago
1589 # use the default port (501).
1590 #
1591 # @segment: #optional The name of the shared memory segment
1592 # Archipelago stack is using. This is optional
1593 # and if not specified, QEMU will make Archipelago
1594 # use the default value, 'archipelago'.
1595 # Since: 2.2
1596 ##
1597 { 'struct': 'BlockdevOptionsArchipelago',
1598 'data': { 'volume': 'str',
1599 '*mport': 'int',
1600 '*vport': 'int',
1601 '*segment': 'str' } }
1602
1603
1604 ##
1605 # @BlkdebugEvent
1606 #
1607 # Trigger events supported by blkdebug.
1608 ##
1609 { 'enum': 'BlkdebugEvent',
1610 'data': [ 'l1_update', 'l1_grow.alloc_table', 'l1_grow.write_table',
1611 'l1_grow.activate_table', 'l2_load', 'l2_update',
1612 'l2_update_compressed', 'l2_alloc.cow_read', 'l2_alloc.write',
1613 'read_aio', 'read_backing_aio', 'read_compressed', 'write_aio',
1614 'write_compressed', 'vmstate_load', 'vmstate_save', 'cow_read',
1615 'cow_write', 'reftable_load', 'reftable_grow', 'reftable_update',
1616 'refblock_load', 'refblock_update', 'refblock_update_part',
1617 'refblock_alloc', 'refblock_alloc.hookup', 'refblock_alloc.write',
1618 'refblock_alloc.write_blocks', 'refblock_alloc.write_table',
1619 'refblock_alloc.switch_table', 'cluster_alloc',
1620 'cluster_alloc_bytes', 'cluster_free', 'flush_to_os',
1621 'flush_to_disk', 'pwritev_rmw.head', 'pwritev_rmw.after_head',
1622 'pwritev_rmw.tail', 'pwritev_rmw.after_tail', 'pwritev',
1623 'pwritev_zero', 'pwritev_done', 'empty_image_prepare' ] }
1624
1625 ##
1626 # @BlkdebugInjectErrorOptions
1627 #
1628 # Describes a single error injection for blkdebug.
1629 #
1630 # @event: trigger event
1631 #
1632 # @state: #optional the state identifier blkdebug needs to be in to
1633 # actually trigger the event; defaults to "any"
1634 #
1635 # @errno: #optional error identifier (errno) to be returned; defaults to
1636 # EIO
1637 #
1638 # @sector: #optional specifies the sector index which has to be affected
1639 # in order to actually trigger the event; defaults to "any
1640 # sector"
1641 #
1642 # @once: #optional disables further events after this one has been
1643 # triggered; defaults to false
1644 #
1645 # @immediately: #optional fail immediately; defaults to false
1646 #
1647 # Since: 2.0
1648 ##
1649 { 'struct': 'BlkdebugInjectErrorOptions',
1650 'data': { 'event': 'BlkdebugEvent',
1651 '*state': 'int',
1652 '*errno': 'int',
1653 '*sector': 'int',
1654 '*once': 'bool',
1655 '*immediately': 'bool' } }
1656
1657 ##
1658 # @BlkdebugSetStateOptions
1659 #
1660 # Describes a single state-change event for blkdebug.
1661 #
1662 # @event: trigger event
1663 #
1664 # @state: #optional the current state identifier blkdebug needs to be in;
1665 # defaults to "any"
1666 #
1667 # @new_state: the state identifier blkdebug is supposed to assume if
1668 # this event is triggered
1669 #
1670 # Since: 2.0
1671 ##
1672 { 'struct': 'BlkdebugSetStateOptions',
1673 'data': { 'event': 'BlkdebugEvent',
1674 '*state': 'int',
1675 'new_state': 'int' } }
1676
1677 ##
1678 # @BlockdevOptionsBlkdebug
1679 #
1680 # Driver specific block device options for blkdebug.
1681 #
1682 # @image: underlying raw block device (or image file)
1683 #
1684 # @config: #optional filename of the configuration file
1685 #
1686 # @align: #optional required alignment for requests in bytes
1687 #
1688 # @inject-error: #optional array of error injection descriptions
1689 #
1690 # @set-state: #optional array of state-change descriptions
1691 #
1692 # Since: 2.0
1693 ##
1694 { 'struct': 'BlockdevOptionsBlkdebug',
1695 'data': { 'image': 'BlockdevRef',
1696 '*config': 'str',
1697 '*align': 'int',
1698 '*inject-error': ['BlkdebugInjectErrorOptions'],
1699 '*set-state': ['BlkdebugSetStateOptions'] } }
1700
1701 ##
1702 # @BlockdevOptionsBlkverify
1703 #
1704 # Driver specific block device options for blkverify.
1705 #
1706 # @test: block device to be tested
1707 #
1708 # @raw: raw image used for verification
1709 #
1710 # Since: 2.0
1711 ##
1712 { 'struct': 'BlockdevOptionsBlkverify',
1713 'data': { 'test': 'BlockdevRef',
1714 'raw': 'BlockdevRef' } }
1715
1716 ##
1717 # @QuorumReadPattern
1718 #
1719 # An enumeration of quorum read patterns.
1720 #
1721 # @quorum: read all the children and do a quorum vote on reads
1722 #
1723 # @fifo: read only from the first child that has not failed
1724 #
1725 # Since: 2.2
1726 ##
1727 { 'enum': 'QuorumReadPattern', 'data': [ 'quorum', 'fifo' ] }
1728
1729 ##
1730 # @BlockdevOptionsQuorum
1731 #
1732 # Driver specific block device options for Quorum
1733 #
1734 # @blkverify: #optional true if the driver must print content mismatch
1735 # set to false by default
1736 #
1737 # @children: the children block devices to use
1738 #
1739 # @vote-threshold: the vote limit under which a read will fail
1740 #
1741 # @rewrite-corrupted: #optional rewrite corrupted data when quorum is reached
1742 # (Since 2.1)
1743 #
1744 # @read-pattern: #optional choose read pattern and set to quorum by default
1745 # (Since 2.2)
1746 #
1747 # Since: 2.0
1748 ##
1749 { 'struct': 'BlockdevOptionsQuorum',
1750 'data': { '*blkverify': 'bool',
1751 'children': [ 'BlockdevRef' ],
1752 'vote-threshold': 'int',
1753 '*rewrite-corrupted': 'bool',
1754 '*read-pattern': 'QuorumReadPattern' } }
1755
1756 ##
1757 # @BlockdevOptions
1758 #
1759 # Options for creating a block device.
1760 #
1761 # Since: 1.7
1762 ##
1763 { 'union': 'BlockdevOptions',
1764 'base': 'BlockdevOptionsBase',
1765 'discriminator': 'driver',
1766 'data': {
1767 'archipelago':'BlockdevOptionsArchipelago',
1768 'blkdebug': 'BlockdevOptionsBlkdebug',
1769 'blkverify': 'BlockdevOptionsBlkverify',
1770 'bochs': 'BlockdevOptionsGenericFormat',
1771 'cloop': 'BlockdevOptionsGenericFormat',
1772 'dmg': 'BlockdevOptionsGenericFormat',
1773 'file': 'BlockdevOptionsFile',
1774 'ftp': 'BlockdevOptionsFile',
1775 'ftps': 'BlockdevOptionsFile',
1776 # TODO gluster: Wait for structured options
1777 'host_cdrom': 'BlockdevOptionsFile',
1778 'host_device':'BlockdevOptionsFile',
1779 'host_floppy':'BlockdevOptionsFile',
1780 'http': 'BlockdevOptionsFile',
1781 'https': 'BlockdevOptionsFile',
1782 # TODO iscsi: Wait for structured options
1783 # TODO nbd: Should take InetSocketAddress for 'host'?
1784 # TODO nfs: Wait for structured options
1785 'null-aio': 'BlockdevOptionsNull',
1786 'null-co': 'BlockdevOptionsNull',
1787 'parallels': 'BlockdevOptionsGenericFormat',
1788 'qcow2': 'BlockdevOptionsQcow2',
1789 'qcow': 'BlockdevOptionsGenericCOWFormat',
1790 'qed': 'BlockdevOptionsGenericCOWFormat',
1791 'quorum': 'BlockdevOptionsQuorum',
1792 'raw': 'BlockdevOptionsGenericFormat',
1793 # TODO rbd: Wait for structured options
1794 # TODO sheepdog: Wait for structured options
1795 # TODO ssh: Should take InetSocketAddress for 'host'?
1796 'tftp': 'BlockdevOptionsFile',
1797 'vdi': 'BlockdevOptionsGenericFormat',
1798 'vhdx': 'BlockdevOptionsGenericFormat',
1799 'vmdk': 'BlockdevOptionsGenericCOWFormat',
1800 'vpc': 'BlockdevOptionsGenericFormat',
1801 'vvfat': 'BlockdevOptionsVVFAT'
1802 } }
1803
1804 ##
1805 # @BlockdevRef
1806 #
1807 # Reference to a block device.
1808 #
1809 # @definition: defines a new block device inline
1810 # @reference: references the ID of an existing block device. An
1811 # empty string means that no block device should be
1812 # referenced.
1813 #
1814 # Since: 1.7
1815 ##
1816 { 'alternate': 'BlockdevRef',
1817 'data': { 'definition': 'BlockdevOptions',
1818 'reference': 'str' } }
1819
1820 ##
1821 # @blockdev-add:
1822 #
1823 # Creates a new block device.
1824 #
1825 # This command is still a work in progress. It doesn't support all
1826 # block drivers, it lacks a matching blockdev-del, and more. Stay
1827 # away from it unless you want to help with its development.
1828 #
1829 # @options: block device options for the new device
1830 #
1831 # Since: 1.7
1832 ##
1833 { 'command': 'blockdev-add', 'data': { 'options': 'BlockdevOptions' } }
1834
1835
1836 ##
1837 # @BlockErrorAction
1838 #
1839 # An enumeration of action that has been taken when a DISK I/O occurs
1840 #
1841 # @ignore: error has been ignored
1842 #
1843 # @report: error has been reported to the device
1844 #
1845 # @stop: error caused VM to be stopped
1846 #
1847 # Since: 2.1
1848 ##
1849 { 'enum': 'BlockErrorAction',
1850 'data': [ 'ignore', 'report', 'stop' ] }
1851
1852
1853 ##
1854 # @BLOCK_IMAGE_CORRUPTED
1855 #
1856 # Emitted when a corruption has been detected in a disk image
1857 #
1858 # @device: device name. This is always present for compatibility
1859 # reasons, but it can be empty ("") if the image does not
1860 # have a device name associated.
1861 #
1862 # @node-name: #optional node name (Since: 2.4)
1863 #
1864 # @msg: informative message for human consumption, such as the kind of
1865 # corruption being detected. It should not be parsed by machine as it is
1866 # not guaranteed to be stable
1867 #
1868 # @offset: #optional, if the corruption resulted from an image access, this is
1869 # the host's access offset into the image
1870 #
1871 # @size: #optional, if the corruption resulted from an image access, this is
1872 # the access size
1873 #
1874 # fatal: if set, the image is marked corrupt and therefore unusable after this
1875 # event and must be repaired (Since 2.2; before, every
1876 # BLOCK_IMAGE_CORRUPTED event was fatal)
1877 #
1878 # Since: 1.7
1879 ##
1880 { 'event': 'BLOCK_IMAGE_CORRUPTED',
1881 'data': { 'device' : 'str',
1882 '*node-name' : 'str',
1883 'msg' : 'str',
1884 '*offset' : 'int',
1885 '*size' : 'int',
1886 'fatal' : 'bool' } }
1887
1888 ##
1889 # @BLOCK_IO_ERROR
1890 #
1891 # Emitted when a disk I/O error occurs
1892 #
1893 # @device: device name
1894 #
1895 # @operation: I/O operation
1896 #
1897 # @action: action that has been taken
1898 #
1899 # @nospace: #optional true if I/O error was caused due to a no-space
1900 # condition. This key is only present if query-block's
1901 # io-status is present, please see query-block documentation
1902 # for more information (since: 2.2)
1903 #
1904 # @reason: human readable string describing the error cause.
1905 # (This field is a debugging aid for humans, it should not
1906 # be parsed by applications) (since: 2.2)
1907 #
1908 # Note: If action is "stop", a STOP event will eventually follow the
1909 # BLOCK_IO_ERROR event
1910 #
1911 # Since: 0.13.0
1912 ##
1913 { 'event': 'BLOCK_IO_ERROR',
1914 'data': { 'device': 'str', 'operation': 'IoOperationType',
1915 'action': 'BlockErrorAction', '*nospace': 'bool',
1916 'reason': 'str' } }
1917
1918 ##
1919 # @BLOCK_JOB_COMPLETED
1920 #
1921 # Emitted when a block job has completed
1922 #
1923 # @type: job type
1924 #
1925 # @device: device name
1926 #
1927 # @len: maximum progress value
1928 #
1929 # @offset: current progress value. On success this is equal to len.
1930 # On failure this is less than len
1931 #
1932 # @speed: rate limit, bytes per second
1933 #
1934 # @error: #optional, error message. Only present on failure. This field
1935 # contains a human-readable error message. There are no semantics
1936 # other than that streaming has failed and clients should not try to
1937 # interpret the error string
1938 #
1939 # Since: 1.1
1940 ##
1941 { 'event': 'BLOCK_JOB_COMPLETED',
1942 'data': { 'type' : 'BlockJobType',
1943 'device': 'str',
1944 'len' : 'int',
1945 'offset': 'int',
1946 'speed' : 'int',
1947 '*error': 'str' } }
1948
1949 ##
1950 # @BLOCK_JOB_CANCELLED
1951 #
1952 # Emitted when a block job has been cancelled
1953 #
1954 # @type: job type
1955 #
1956 # @device: device name
1957 #
1958 # @len: maximum progress value
1959 #
1960 # @offset: current progress value. On success this is equal to len.
1961 # On failure this is less than len
1962 #
1963 # @speed: rate limit, bytes per second
1964 #
1965 # Since: 1.1
1966 ##
1967 { 'event': 'BLOCK_JOB_CANCELLED',
1968 'data': { 'type' : 'BlockJobType',
1969 'device': 'str',
1970 'len' : 'int',
1971 'offset': 'int',
1972 'speed' : 'int' } }
1973
1974 ##
1975 # @BLOCK_JOB_ERROR
1976 #
1977 # Emitted when a block job encounters an error
1978 #
1979 # @device: device name
1980 #
1981 # @operation: I/O operation
1982 #
1983 # @action: action that has been taken
1984 #
1985 # Since: 1.3
1986 ##
1987 { 'event': 'BLOCK_JOB_ERROR',
1988 'data': { 'device' : 'str',
1989 'operation': 'IoOperationType',
1990 'action' : 'BlockErrorAction' } }
1991
1992 ##
1993 # @BLOCK_JOB_READY
1994 #
1995 # Emitted when a block job is ready to complete
1996 #
1997 # @type: job type
1998 #
1999 # @device: device name
2000 #
2001 # @len: maximum progress value
2002 #
2003 # @offset: current progress value. On success this is equal to len.
2004 # On failure this is less than len
2005 #
2006 # @speed: rate limit, bytes per second
2007 #
2008 # Note: The "ready to complete" status is always reset by a @BLOCK_JOB_ERROR
2009 # event
2010 #
2011 # Since: 1.3
2012 ##
2013 { 'event': 'BLOCK_JOB_READY',
2014 'data': { 'type' : 'BlockJobType',
2015 'device': 'str',
2016 'len' : 'int',
2017 'offset': 'int',
2018 'speed' : 'int' } }
2019
2020 # @PreallocMode
2021 #
2022 # Preallocation mode of QEMU image file
2023 #
2024 # @off: no preallocation
2025 # @metadata: preallocate only for metadata
2026 # @falloc: like @full preallocation but allocate disk space by
2027 # posix_fallocate() rather than writing zeros.
2028 # @full: preallocate all data by writing zeros to device to ensure disk
2029 # space is really available. @full preallocation also sets up
2030 # metadata correctly.
2031 #
2032 # Since 2.2
2033 ##
2034 { 'enum': 'PreallocMode',
2035 'data': [ 'off', 'metadata', 'falloc', 'full' ] }
2036
2037 ##
2038 # @BLOCK_WRITE_THRESHOLD
2039 #
2040 # Emitted when writes on block device reaches or exceeds the
2041 # configured write threshold. For thin-provisioned devices, this
2042 # means the device should be extended to avoid pausing for
2043 # disk exhaustion.
2044 # The event is one shot. Once triggered, it needs to be
2045 # re-registered with another block-set-threshold command.
2046 #
2047 # @node-name: graph node name on which the threshold was exceeded.
2048 #
2049 # @amount-exceeded: amount of data which exceeded the threshold, in bytes.
2050 #
2051 # @write-threshold: last configured threshold, in bytes.
2052 #
2053 # Since: 2.3
2054 ##
2055 { 'event': 'BLOCK_WRITE_THRESHOLD',
2056 'data': { 'node-name': 'str',
2057 'amount-exceeded': 'uint64',
2058 'write-threshold': 'uint64' } }
2059
2060 ##
2061 # @block-set-write-threshold
2062 #
2063 # Change the write threshold for a block drive. An event will be delivered
2064 # if a write to this block drive crosses the configured threshold.
2065 # This is useful to transparently resize thin-provisioned drives without
2066 # the guest OS noticing.
2067 #
2068 # @node-name: graph node name on which the threshold must be set.
2069 #
2070 # @write-threshold: configured threshold for the block device, bytes.
2071 # Use 0 to disable the threshold.
2072 #
2073 # Since: 2.3
2074 ##
2075 { 'command': 'block-set-write-threshold',
2076 'data': { 'node-name': 'str', 'write-threshold': 'uint64' } }