[SOLVED] virtiofs directory mapping does not mount exec in guest vm

3

3xogenic

New Member
Jun 20, 2024
3
0
1
Hi everyone,

I'm trying out a virtiofs directory mapping from a mounted HDD ("Vapordisk") to a guest VM (cachyos) and despite being mounted and read-writeable in the guest VM, I cannot get the drive mounted exec. My ultimate goal is to mount this virtiofs mapping in Steam on the cachyos VM as file storage. Steam sees the folder, but provides the error "Steam library folder is not executable."

virtiofs entry in VM conf:
virtiofs0: Vapordisk,cache=never,direct-io=1,expose-acl=1

/etc/fstab in guest:
Vapordisk /mnt/vapordisk virtiofs defaults,noatime,nofail 0 0

running mount | grep Vapordisk on the guest provides:
Vapordisk on /mnt/vapordisk type virtiofs (rw,noatime)

ls -l /mntin PVE shows 777 permissions and nobody:nogroup ownership on the drive as well as the /vapordisk mountpoint.
ls -l on both the root of the disk as well as child folders on the disk show 777 permissions and nobodyownership.

FWIW, I'm unsure if this is hurting anything since I can see and modify the drive in the guest already, but lsmod | grep virtiofs shows nothing after a modprobe virtiofs.
Another FWIW, this disk is mounted in an OpenMediaVault VM as well as a mountpoint in an LXC with no problems.

At this point I'm unsure what else it could be. I have all permissions and ownership wide open, to my knowledge I have my virtiofs mapping and fstab configured correctly. Is there something I'm missing? Is my config incorrect or is there something I'm not understanding here?

Thanks for any help.

EDIT: More importantly I'm trying to determine if this is a PVE issue, a CachyOS issue, or even a Steam issue for all I know. Obviously CachyOS and Steam are out of the scope of the forum, but it's still hard to tell at this point.
 
Last edited:
"not executable" could refer to the access mode (the executable bit) of a directory as well (see `man chmod`).
 
mfederanko said:
Maybe check the correct casing of you "steamapps" folder, as described in https://wiki.archlinux.org/title/St...folder_because_of_missing_execute_permissions
Click to expand...

This was it, there was not a "steamapps" folder inside the target. I do wish Steam would change the error message to something more descriptive there, I went on a wild goose chase in the total opposite direction for a whole day thinking it was a permissions thing. I'm just glad it wasn't a PVE issue.

Appreciate your superior googling and your time sir.
 
You must log in or register to reply here.
Top Bottom
Back