What you should do to create files from within the running guest system in the mounted shared folder are these steps : The root cause is that the guest system is running as libvirt-qemu user. Unix & Linux - KVM / QEMU / Virt-Manager : How can I store files in the mounted shared folder
It was possible to read files but I was not allowed to write files to the shared source path folder. I once had a very similar problem, providing read-write access to the shared folder. This makes a passthrough-like mode usable for people who run the hypervisor as non-root. Similar to 'passthrough', the exception is that failure of privileged operations like 'chown' are ignored. This mode is generally a bit slower than passthrough. If your host system supports ACLs, this mode will also allow proper ACL support in the guest. The advantage is that file attributes and permissions are "mapped" for the guest so that they are independent changes elsewhere (as long as the files stay accessible). This means you need to make sure that files on the hypervisor are accessible to the QEMU process (username libvirt-qemu on my setup). The source is accessed with the permissions of the hypervisor (QEMU process). Beware that changes to permissions/ownership will affect all guests using that filesystem. This is the default accessmode if one is not specified. The source is accessed with the permissions of the user inside the guest. Currently this only works with type='mount' for the QEMU/KVM driver. The filesystem block has an optional attribute accessmode which specifies the security mode for accessing the source (since 0.8.5). The best docs I have found regarding the modes is from the libvirt docs:
To understand this, it's important to remember that the virtualised file system needs to manage permissions of files and they may not be the same in the host as they are in the guest. There are important implications for permission mapping. Share modes define how the virtualised (p9fs) file system is presented to the guest machine.
0 kommentar(er)
