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>
This commit is contained in:
Kevin Wolf 2016-07-06 14:15:51 +02:00
parent cd7fca952c
commit 094138d09e
2 changed files with 11 additions and 14 deletions

View file

@ -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