| commit | 094138d09e78443a4b6ec9532398e0ae98323319 | |
| author | Kevin Wolf <kwolf@redhat.com> | |
| Wed, 6 Jul 2016 12:15:51 +0000 (6 14:15 +0200) | ||
| committer | Kevin Wolf <kwolf@redhat.com> | |
| Mon, 5 Sep 2016 17:06:47 +0000 (5 19:06 +0200) | ||
| tree | 5f372f724c09f98c7509be9b144c85cf572966de | treesnapshot (tar.gz zip) |
| parent | cd7fca952ce8456955f7f4e11df9ced14204c2f1 | commitdiff |
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>
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>
| blockdev-nbd.c | diffblobblamehistory | |
| qapi/block.json | diffblobblamehistory |