virtual: 0.896
architecture: 0.799
files: 0.765
device: 0.759
network: 0.746
performance: 0.698
ppc: 0.682
graphic: 0.581
hypervisor: 0.576
VMM: 0.567
kernel: 0.564
socket: 0.541
vnc: 0.539
mistranslation: 0.539
register: 0.535
semantic: 0.524
arm: 0.516
PID: 0.496
user-level: 0.481
KVM: 0.479
permissions: 0.472
peripherals: 0.395
risc-v: 0.392
boot: 0.368
TCG: 0.336
i386: 0.334
x86: 0.319
debug: 0.278
assembly: 0.213

native libgfapi  glusterfs support for virtio 9p filesystem passthrough

I can add block devices on glusterfs natively to my virtual machines since qemu 1.3 
I would like to see the same feature for virtio 9p filesystems added on my VM. 

Accessing a filesystem mounted on the Metal is my favorite solution for storage that is to be shared between more than one VM. But because my VMs are not running as root, they are not able to passthrough userids and gids to gluster-fuse. uid mapping is also not possible because no xattr support. 

So all I can do is either setting up seperate NFS Servers to bring the Filesystem in via Network, or to start qemu as root or to add fuse_xattr on top of glusterfs_fuse. I do expect however that the fastest and most relieable solution is to make something like this possible: 

-fsdev local,id=test_dev,path=gluster://this.node/test_mount,security_model=passthrough -device virtio-9p-pci,fsdev=test_dev,mount_tag=test_mount

regards 

    Hans

There are currently no plans to implement a GlusterFS fs driver backend for 9pfs in QEMU.

Right now the status of 9p in QEMU is "odd fixes", which means there are currently no paid developers maintaining 9p, nor do current 9p maintainers have sufficient time to work on it on a daily basis. New 9p features for that reason are only likely to appear if there is an effort for the feature coming from outside.

As xattrs are apparently not available with GlusterFS yet, you might want to try security_model=mapped-file with 9p as workaround instead:
https://wiki.qemu.org/Documentation/9psetup



Ok, then let's mark this ticket as WONTFIX since nobody will be working on it in the near future.