Commit ae110dc5 authored by Brian Turek's avatar Brian Turek Committed by Jano Tomko
Browse files

qemu: add docs for 'fmode' and 'dmode' options

Adds documentation for QEMU 9pfs 'fmode' and 'dmode' options.
Signed-off-by: Brian Turek's avatarBrian Turek <>
Signed-off-by: Jano Tomko's avatarJán Tomko <>
Reviewed-by: Jano Tomko's avatarJán Tomko <>
parent 1d9b4a96
Pipeline #211813407 passed with stages
in 27 minutes and 54 seconds
......@@ -3062,6 +3062,12 @@ A directory on the host that can be accessed directly from the guest.
<target dir='/import/from/host'/>
<filesystem type='mount' accessmode='mapped' fmode='644' dmode='755'>
<driver type='path'/>
<source dir='/export/to/guest'/>
<target dir='/import/from/host'/>
<filesystem type='file' accessmode='passthrough'>
<driver type='loop' format='raw'/>
<source file='/export/to/guest.img'/>
......@@ -3140,6 +3146,13 @@ A directory on the host that can be accessed directly from the guest.
"virtio-non-transitional", or "virtio". See `Virtio transitional
devices <#elementsVirtioTransitional>`__ for more details.
The filesystem element has optional attributes ``fmode`` and ``dmode``.
These two attributes control the creation mode for files and directories
when used with the ``mapped`` value for ``accessmode`` (:since:`since 6.10.0,
requires QEMU 2.10` ). If not specified, QEMU creates files with mode
``600`` and directories with mode ``700``. The setuid, setgid, and sticky
bit are unsupported.
The filesystem element has an optional attribute ``multidevs`` which
specifies how to deal with a filesystem export containing more than one
device, in order to avoid file ID collisions on guest when using 9pfs (
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment