diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2016-07-06 14:15:51 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2016-09-05 19:06:47 +0200 |
| commit | 094138d09e78443a4b6ec9532398e0ae98323319 (patch) | |
| tree | 5f372f724c09f98c7509be9b144c85cf572966de /qapi/block.json | |
| parent | cd7fca952ce8456955f7f4e11df9ced14204c2f1 (diff) | |
nbd-server: Allow node name for nbd-server-add
There is no reason why an NBD server couldn't be started for any node,
even if it's not on the top level. This converts nbd-server-add to
accept a node-name.
Note that there is a semantic difference between using a BlockBackend
name and the node name of its root: In the former case, the NBD server
is closed on eject; in the latter case, the NBD server doesn't drop its
reference and keeps the image file open this way.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'qapi/block.json')
| -rw-r--r-- | qapi/block.json | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/qapi/block.json b/qapi/block.json index db05169187..8b08bd2fd0 100644 --- a/qapi/block.json +++ b/qapi/block.json @@ -161,9 +161,9 @@ ## # @nbd-server-add: # -# Export a device to QEMU's embedded NBD server. +# Export a block node to QEMU's embedded NBD server. # -# @device: Block device to be exported +# @device: The device name or node name of the node to be exported # # @writable: Whether clients should be able to write to the device via the # NBD connection (default false). #optional |