Lines Matching full:node

66   is a block node definition. See the :manpage:`qemu(1)` manual page for a
67   description of block node properties and the :manpage:`qemu-block-drivers(7)`
78 .. option:: --export [type=]nbd,id=<id>,node-name=<node-name>[,name=<export-name>][,writable=on|off…
79 …--export [type=]vhost-user-blk,id=<id>,node-name=<node-name>,addr.type=unix,addr.path=<socket-path…
80 …--export [type=]vhost-user-blk,id=<id>,node-name=<node-name>,addr.type=fd,addr.str=<fd>[,writable=…
81 …--export [type=]fuse,id=<id>,node-name=<node-name>,mountpoint=<file>[,growable=on|off][,writable=o…
82 …--export [type=]vduse-blk,id=<id>,node-name=<node-name>,name=<vduse-name>[,writable=on|off][,num-q…
84   is a block export definition. ``node-name`` is the block node that should be
90   ``node-name``). ``bitmap`` is the name of a dirty bitmap reachable from the
91   block node, so the NBD client can use NBD_OPT_SET_META_CONTEXT with the
102   on which to export the given block node. That file will not be changed, it
103   will just appear to have the block node's content while the export is active
109   block node to fit.  The ``allow-other`` option controls whether users other
236       --blockdev driver=file,node-name=disk,filename=disk.img \
238       --export type=nbd,id=export,node-name=disk,writable=on
244       --blockdev driver=file,node-name=file,filename=disk.qcow2 \
245       --blockdev driver=qcow2,node-name=qcow2,file=file \
246 …--export type=vhost-user-blk,id=export,addr.type=unix,addr.path=vhost-user-blk.sock,node-name=qcow2
252       --blockdev driver=file,node-name=file,filename=disk.qcow2 \
253       --blockdev driver=qcow2,node-name=qcow2,file=file \
254       --export type=fuse,id=export,node-name=qcow2,mountpoint=disk.qcow2,writable=on