diff options
author | Roman Bogorodskiy <bogorodskiy@gmail.com> | 2020-10-07 20:07:04 +0400 |
---|---|---|
committer | Roman Bogorodskiy <bogorodskiy@gmail.com> | 2020-10-09 18:46:04 +0400 |
commit | 7382a7c2bef9d0f74a364a13b8b4ec8c08ffd1e5 (patch) | |
tree | a9b72f3b7921bdd89690d8ba86fe9ca1cc2fa802 /src/libvirt_private.syms | |
parent | 7c878cf9a73ee6f6fecbc17eff1b2a46cfc007fa (diff) | |
download | libvirt-7382a7c2bef9d0f74a364a13b8b4ec8c08ffd1e5.tar.gz |
bhyve: implement virtio-9p support
Recently virtio-9p support was added to bhyve.
On the host side it looks this way:
bhyve .... -s 25:0,virtio-9p,sharename=/path/to/shared/dir
It could also have ",ro" suffix to make share read-only.
In the Linux guest, this share is mounted with:
mount -t 9p sharename /mnt/sharename
In the guest user will see the same permissions and ownership
information for this directory as on the host. No uid/gid remapping is
supported, so those could resolve to wrong user or group names.
The same applies to the other side: chowning/chmodding in the guest will
set specified ownership and permissions on the host.
In libvirt domain XML it's modeled using the 'filesystem' element:
<filesystem type='mount'>
<source dir='/path/to/shared/dir'/>
<target dir='sharename'/>
</filesystem>
Optional 'readonly' sub-element enables read-only mode.
Signed-off-by: Roman Bogorodskiy <bogorodskiy@gmail.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
Diffstat (limited to 'src/libvirt_private.syms')
-rw-r--r-- | src/libvirt_private.syms | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/libvirt_private.syms b/src/libvirt_private.syms index 152083d220..d773aee571 100644 --- a/src/libvirt_private.syms +++ b/src/libvirt_private.syms @@ -402,6 +402,7 @@ virDomainDiskSourceFormat; virDomainDiskTranslateSourcePool; virDomainFeatureTypeFromString; virDomainFeatureTypeToString; +virDomainFSAccessModeTypeToString; virDomainFSCacheModeTypeToString; virDomainFSDefFree; virDomainFSDefNew; |