5 # == Block device exports
8 { 'include': 'sockets.json' }
9 { 'include': 'block-core.json' }
14 # Keep this type consistent with the nbd-server-start arguments. The
15 # only intended difference is using SocketAddress instead of
16 # SocketAddressLegacy.
18 # @addr: Address on which to listen.
20 # @tls-creds: ID of the TLS credentials object (since 2.6).
22 # @tls-authz: ID of the QAuthZ authorization object used to validate
23 # the client's x509 distinguished name. This object is is only
24 # resolved at time of use, so can be deleted and recreated on the
25 # fly while the NBD server is active. If missing, it will default
26 # to denying access (since 4.0).
28 # @max-connections: The maximum number of connections to allow at the
29 # same time, 0 for unlimited. Setting this to 1 also stops the
30 # server from advertising multiple client support (since 5.2;
35 { 'struct': 'NbdServerOptions',
36 'data': { 'addr': 'SocketAddress',
39 '*max-connections': 'uint32' } }
44 # Start an NBD server listening on the given host and port. Block
45 # devices can then be exported using @nbd-server-add. The NBD server
46 # will present them as named exports; for example, another QEMU
47 # instance could refer to them as "nbd:HOST:PORT:exportname=NAME".
49 # Keep this type consistent with the NbdServerOptions type. The only
50 # intended difference is using SocketAddressLegacy instead of
53 # @addr: Address on which to listen.
55 # @tls-creds: ID of the TLS credentials object (since 2.6).
57 # @tls-authz: ID of the QAuthZ authorization object used to validate
58 # the client's x509 distinguished name. This object is is only
59 # resolved at time of use, so can be deleted and recreated on the
60 # fly while the NBD server is active. If missing, it will default
61 # to denying access (since 4.0).
63 # @max-connections: The maximum number of connections to allow at the
64 # same time, 0 for unlimited. Setting this to 1 also stops the
65 # server from advertising multiple client support (since 5.2;
68 # Returns: error if the server is already running.
72 { 'command': 'nbd-server-start',
73 'data': { 'addr': 'SocketAddressLegacy',
76 '*max-connections': 'uint32' },
77 'allow-preconfig': true }
80 # @BlockExportOptionsNbdBase:
82 # An NBD block export (common options shared between nbd-server-add
83 # and the NBD branch of block-export-add).
85 # @name: Export name. If unspecified, the @device parameter is used
86 # as the export name. (Since 2.12)
88 # @description: Free-form description of the export, up to 4096 bytes.
93 { 'struct': 'BlockExportOptionsNbdBase',
94 'data': { '*name': 'str', '*description': 'str' } }
97 # @BlockExportOptionsNbd:
99 # An NBD block export (distinct options used in the NBD branch of
102 # @bitmaps: Also export each of the named dirty bitmaps reachable from
103 # @device, so the NBD client can use NBD_OPT_SET_META_CONTEXT with
104 # the metadata context name "qemu:dirty-bitmap:BITMAP" to inspect
105 # each bitmap. Since 7.1 bitmap may be specified by node/name
108 # @allocation-depth: Also export the allocation depth map for @device,
109 # so the NBD client can use NBD_OPT_SET_META_CONTEXT with the
110 # metadata context name "qemu:allocation-depth" to inspect
111 # allocation details. (since 5.2)
115 { 'struct': 'BlockExportOptionsNbd',
116 'base': 'BlockExportOptionsNbdBase',
117 'data': { '*bitmaps': ['BlockDirtyBitmapOrStr'],
118 '*allocation-depth': 'bool' } }
121 # @BlockExportOptionsVhostUserBlk:
123 # A vhost-user-blk block export.
125 # @addr: The vhost-user socket on which to listen. Both 'unix' and
126 # 'fd' SocketAddress types are supported. Passed fds must be UNIX
129 # @logical-block-size: Logical block size in bytes. Defaults to 512
132 # @num-queues: Number of request virtqueues. Must be greater than 0.
137 { 'struct': 'BlockExportOptionsVhostUserBlk',
138 'data': { 'addr': 'SocketAddress',
139 '*logical-block-size': 'size',
140 '*num-queues': 'uint16'} }
143 # @FuseExportAllowOther:
145 # Possible allow_other modes for FUSE exports.
147 # @off: Do not pass allow_other as a mount option.
149 # @on: Pass allow_other as a mount option.
151 # @auto: Try mounting with allow_other first, and if that fails, retry
152 # without allow_other.
156 { 'enum': 'FuseExportAllowOther',
157 'data': ['off', 'on', 'auto'] }
160 # @BlockExportOptionsFuse:
162 # Options for exporting a block graph node on some (file) mountpoint
165 # @mountpoint: Path on which to export the block device via FUSE. This
166 # must point to an existing regular file.
168 # @growable: Whether writes beyond the EOF should grow the block node
169 # accordingly. (default: false)
171 # @allow-other: If this is off, only qemu's user is allowed access to
172 # this export. That cannot be changed even with chmod or chown.
173 # Enabling this option will allow other users access to the export
174 # with the FUSE mount option "allow_other". Note that using
175 # allow_other as a non-root user requires user_allow_other to be
176 # enabled in the global fuse.conf configuration file. In auto
177 # mode (the default), the FUSE export driver will first attempt to
178 # mount the export with allow_other, and if that fails, try again
179 # without. (since 6.1; default: auto)
183 { 'struct': 'BlockExportOptionsFuse',
184 'data': { 'mountpoint': 'str',
186 '*allow-other': 'FuseExportAllowOther' },
187 'if': 'CONFIG_FUSE' }
190 # @BlockExportOptionsVduseBlk:
192 # A vduse-blk block export.
194 # @name: the name of VDUSE device (must be unique across the host).
196 # @num-queues: the number of virtqueues. Defaults to 1.
198 # @queue-size: the size of virtqueue. Defaults to 256.
200 # @logical-block-size: Logical block size in bytes. Range [512,
201 # PAGE_SIZE] and must be power of 2. Defaults to 512 bytes.
203 # @serial: the serial number of virtio block device. Defaults to
208 { 'struct': 'BlockExportOptionsVduseBlk',
209 'data': { 'name': 'str',
210 '*num-queues': 'uint16',
211 '*queue-size': 'uint16',
212 '*logical-block-size': 'size',
216 # @NbdServerAddOptions:
218 # An NBD block export, per legacy nbd-server-add command.
220 # @device: The device name or node name of the node to be exported
222 # @writable: Whether clients should be able to write to the device via
223 # the NBD connection (default false).
225 # @bitmap: Also export a single dirty bitmap reachable from @device,
226 # so the NBD client can use NBD_OPT_SET_META_CONTEXT with the
227 # metadata context name "qemu:dirty-bitmap:BITMAP" to inspect the
228 # bitmap (since 4.0).
232 { 'struct': 'NbdServerAddOptions',
233 'base': 'BlockExportOptionsNbdBase',
234 'data': { 'device': 'str',
235 '*writable': 'bool', '*bitmap': 'str' } }
240 # Export a block node to QEMU's embedded NBD server.
242 # The export name will be used as the id for the resulting block
247 # @deprecated: This command is deprecated. Use @block-export-add
250 # Returns: error if the server is not running, or export with the same
251 # name already exists.
255 { 'command': 'nbd-server-add',
256 'data': 'NbdServerAddOptions', 'boxed': true, 'features': ['deprecated'],
257 'allow-preconfig': true }
260 # @BlockExportRemoveMode:
262 # Mode for removing a block export.
264 # @safe: Remove export if there are no existing connections, fail
267 # @hard: Drop all connections immediately and remove export.
269 # Potential additional modes to be added in the future:
271 # hide: Just hide export from new clients, leave existing connections
272 # as is. Remove export after all clients are disconnected.
274 # soft: Hide export from new clients, answer with ESHUTDOWN for all
275 # further requests from existing clients.
279 {'enum': 'BlockExportRemoveMode', 'data': ['safe', 'hard']}
282 # @nbd-server-remove:
284 # Remove NBD export by name.
286 # @name: Block export id.
288 # @mode: Mode of command operation. See @BlockExportRemoveMode
289 # description. Default is 'safe'.
293 # @deprecated: This command is deprecated. Use @block-export-del
298 # - the server is not running
299 # - export is not found
300 # - mode is 'safe' and there are existing connections
304 { 'command': 'nbd-server-remove',
305 'data': {'name': 'str', '*mode': 'BlockExportRemoveMode'},
306 'features': ['deprecated'],
307 'allow-preconfig': true }
312 # Stop QEMU's embedded NBD server, and unregister all devices
313 # previously added via @nbd-server-add.
317 { 'command': 'nbd-server-stop',
318 'allow-preconfig': true }
323 # An enumeration of block export types
327 # @vhost-user-blk: vhost-user-blk export (since 5.2)
329 # @fuse: FUSE export (since: 6.0)
331 # @vduse-blk: vduse-blk export (since 7.1)
335 { 'enum': 'BlockExportType',
337 { 'name': 'vhost-user-blk',
338 'if': 'CONFIG_VHOST_USER_BLK_SERVER' },
339 { 'name': 'fuse', 'if': 'CONFIG_FUSE' },
340 { 'name': 'vduse-blk', 'if': 'CONFIG_VDUSE_BLK_EXPORT' } ] }
343 # @BlockExportOptions:
345 # Describes a block export, i.e. how single node should be exported on
346 # an external interface.
348 # @id: A unique identifier for the block export (across all export
351 # @node-name: The node name of the block node to be exported
354 # @writable: True if clients should be able to write to the export
357 # @writethrough: If true, caches are flushed after every write request
358 # to the export before completion is signalled. (since: 5.2;
361 # @iothread: The name of the iothread object where the export will
362 # run. The default is to use the thread currently associated with
363 # the block node. (since: 5.2)
365 # @fixed-iothread: True prevents the block node from being moved to
366 # another thread while the export is active. If true and
367 # @iothread is given, export creation fails if the block node
368 # cannot be moved to the iothread. The default is false.
373 { 'union': 'BlockExportOptions',
374 'base': { 'type': 'BlockExportType',
376 '*fixed-iothread': 'bool',
380 '*writethrough': 'bool' },
381 'discriminator': 'type',
383 'nbd': 'BlockExportOptionsNbd',
384 'vhost-user-blk': { 'type': 'BlockExportOptionsVhostUserBlk',
385 'if': 'CONFIG_VHOST_USER_BLK_SERVER' },
386 'fuse': { 'type': 'BlockExportOptionsFuse',
387 'if': 'CONFIG_FUSE' },
388 'vduse-blk': { 'type': 'BlockExportOptionsVduseBlk',
389 'if': 'CONFIG_VDUSE_BLK_EXPORT' }
395 # Creates a new block export.
399 { 'command': 'block-export-add',
400 'data': 'BlockExportOptions', 'boxed': true,
401 'allow-preconfig': true }
406 # Request to remove a block export. This drops the user's reference
407 # to the export, but the export may still stay around after this
408 # command returns until the shutdown of the export has completed.
410 # @id: Block export id.
412 # @mode: Mode of command operation. See @BlockExportRemoveMode
413 # description. Default is 'safe'.
415 # Returns: Error if the export is not found or @mode is 'safe' and the
416 # export is still in use (e.g. by existing client connections)
420 { 'command': 'block-export-del',
421 'data': { 'id': 'str', '*mode': 'BlockExportRemoveMode' },
422 'allow-preconfig': true }
425 # @BLOCK_EXPORT_DELETED:
427 # Emitted when a block export is removed and its id can be reused.
429 # @id: Block export id.
433 { 'event': 'BLOCK_EXPORT_DELETED',
434 'data': { 'id': 'str' } }
439 # Information about a single block export.
441 # @id: The unique identifier for the block export
443 # @type: The block export type
445 # @node-name: The node name of the block node that is exported
447 # @shutting-down: True if the export is shutting down (e.g. after a
448 # block-export-del command, but before the shutdown has completed)
452 { 'struct': 'BlockExportInfo',
453 'data': { 'id': 'str',
454 'type': 'BlockExportType',
456 'shutting-down': 'bool' } }
459 # @query-block-exports:
461 # Returns: A list of BlockExportInfo describing all block exports
465 { 'command': 'query-block-exports', 'returns': ['BlockExportInfo'],
466 'allow-preconfig': true }