
Virtualbox wanted you to be able to effectively do the same thing in its GUI, and for the most part you can. The auto option ensures mounting on startup. Those are the id of my user.Īfter that, you should be able to mount the drive by typing sudo mount -a. most importantly the uid=1000 and the gid=1000. Mine is called sharedsfname.Īdding a line (above) to /etc/fstab, designating the share sharedsfsname, the mount point /files, and the filesystem type vboxsf, along with some options.

you can also get this name from sudo VBoxControl sharedfolder list on the guest. Using the shared folder name (NOT THE AUTO-NAME mount point, created by virtualbox?: sf_XXXXXXXX), This is the name that you designated in the virtualbox GUI on the host(it also gets auto-created but it is an editable field in the Shared Folders editor). I am creating my own folder on my guest called /files. I am creating my shared folder and checking 'make permanent' (always clicking OK, to accept the changes) I have a linux on linux setup though, so I am not sure about the effects with a Windows host. Without it I have the same issue that you are experiencing. The uid/gid=userid option is the key in my case. Sharedsfname /files vboxsf rw,noexec,auto,nouser,uid=1000,gid=1000 0 0 avamk Posts: 29 Joined: 7.I mount my shared folder in /etc/fstab like: How can I troubleshoot these problems? Thank you. Sometimes, a seemingly random assortment of files and folders inside the share would show up as belonging to nobody:nobody, and I can access them even with the `sudo` command. Strangely, if I use the `nano` editor from the terminal, I can edit and write to the same file just fine.Ģ. By using the `ls -lh` command in a terminal, I see that the files and folders in the share are owned by root:vboxsf with read and write privileges to the root user and the vboxsf group. In Visual Studio Code, the error is simply permission denied.

For example, if I use Gnome's text editor to open, edit, and try to save a pure text file in the share, I get a "file busy" error.

I often can't save my changes to files I edit in those shares. I added my virtual machine user to the vboxsf group and I can see and open files in those two shares from the virtual machine.ġ. Through that I have a Red Hat Enterprise Linux 8.1 virtual machine (with guest additions 6.1.4) with two shared folders with "Access" set to full and auto-mount enabled. I have Virtualbox 6.1.4 on a Windows 10 guest both fully updated.
