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