9p/virtfs share not writable

[rpolyano]

Describe the issue
9p share is not writable.

Configuration

• UTM Version: 4.0.6 (65)
• macOS Version: 12.6
• Mac Chip (Intel, M1, ...): M1

Setup
Guest: Ubuntu Server 22.04

1. Added a VirtFS share of /Users/roman/.../foo in UTM
2. In guest, mounted the share with sudo mount -t 9p -o trans=virtio share /mnt/share -o version=9p2000.L (also tried without -version parameter)
3. ls -l in /mnt/share

ls: test.c: Network dropped connection on reset
ls: makefile: Network dropped connection on reset
total 8
-rw-rw-r-- 1 501 dialout 195 Sep 26 20:59 makefile
-rw-rw-r-- 1 501 dialout 233 Sep 26 21:00 test.c

I know the network dropped bug is already been reported as #4394 but my issue is that trying to modify either of these files, or create new files fails with EACCESS - $ touch test.h --> touch: cannot touch 'test.h': Permission denied

It appears I can make changes as root -$ sudo touch test.h works fine. How can I allow normal user to access the files?

[osy]

Try running sudo chown -R yourusername:yourgroup path/to/share/mount

[rpolyano]

Thank you!

[rpolyano]

Upon further use seems like only the first write works. After that they just hang. I think I'll take the advice I've seen online and give up on 9pfs, it's just not stable enough to work.

[saoj]

@rpolyano What is an alternative to 9pfs?

[sbates130272]

@osy - does your chown solution not create a new problem in that the fileownership on the host filesystem are now set to the uid and gid of the guest account in the VM?

I see exactly the same issue as @rpolyano. We can solve this by using bindfs to re-mount the 9p mount with the desired uid and gid in the guest. Something like

sudo bindfs --map=501/<your guest uid>:@dialout/@<your guest gid> <9p mount point> <desired bindfs mount point>

However it seems to me there must be a way this can be solved via either the call in UTM into qemo -fsdev or in the mount options for the mount command inside the guest. If anyone has any pointers for this I would really appreciate it.

Oh and @osy I think this is an issue rather than a discussion until we root cause a solution....

[osy]

The guest permissions are mapped to host in the file attribute, it does not change the ownership on the host file system. However different guests will see the same permissions.

[sbates130272]

I see that @osy but I also see that new files created by the guest have odd permissions set back on the host. For example if I create a file on the guest called test:

On guest

batesste@bunbeg:~/Projects2$ ls -la test
ls: test: Network dropped connection on reset
-rw-r--r-- 1 batesste batesste 0 Oct  6 19:23 test

On host

batesste@armagh Projects % ls -la@ test
-rw-------@ 1 batesste  staff  0  6 Oct 19:23 test
	com.apple.quarantine	25 
	user.virtfs.gid	4 
	user.virtfs.mode	2 
	user.virtfs.uid	4 

It is annoying that no group or global permissions are set. Any ideas if there is a better set of options in either the QEMU command or the mount command in the host?

[light-idea]

I also ran issues with permissions and solved it by installing bindfs (as above). To get the shared folder to mount every boot, append the following to /etc/fstab:

share	/mnt/macos	9p	trans=virtio,version=9p2000.L,rw,_netdev,nofail	0	0
/mnt/macos    /mnt/share fuse.bindfs map=501/1000:@20/@1000,x-systemd.requires=/mnt/macos 0 0

[sabrehagen]

This comment should be added to the docs: https://docs.getutm.app/guest-support/linux/

[osy]

Done

[mrexodia]

I will try to make a proper guide and add it to the documentation. My goal is to mount my whole macos Home folder and running chown -R is not a good idea in that case. The magic numbers for the user/group id are also not applicable to everyone.

[mrexodia]

I sent a pull request with a better explanation (utmapp/docs.getutm.app#45), thanks to @light-idea for findings the solution with bindfs!