Guys, When testing with kimchi nfs feature, I filed two issues related to nfs image permission problem: 1. volume creation failure: Because of storage pool permission is not configured to make write permission.(https://github.com/kimchi-project/kimchi/issues/261) 2. vm with volume cannot be started: Root users are mapped to nobody, so img it created cannot be accessed by libvirt-qemu(on ubuntu) user.(https://github.com/kimchi-project/kimchi/issues/267) After discussed with Mark Wu, we would like to propose the following to resolve these two problem: 1. To allow creation: export with all_squash(gid = kimchi_guid) and group allow write permission. Also with planned nfs-pool prevalidation (a timeout try mount in a process), we can check if the gid and permission is right. This will save us from future trouble. 2. To allow qemu process(started by libvirt) to access img, we add uid ('qemu' under fedora and 'libvirt-qemu' under ubuntu) which running qemu process to 'kimchi' group to allow the write access of the img. I am also investigating other possibilities like using storage pool permissions and so on. Welcome thoughts on it! -- project-kimchi mailing list <project-kimchi(a)googlegroups.com&gt; https://groups.google.com/forum/#!forum/project-kimchi --- You received this message because you are subscribed to the Google Groups "project-kimchi" group. To unsubscribe from this group and stop receiving emails from it, send an email to project-kimchi+unsubscribe(a)googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.