But as soon as you exit the editor, the mount seems to happen on the guest. (Which is why I prefer the previous mentioned method instead because you are simply giving ownership to your user without any additional alterations). In this case you will need to add your user to the vboxsf group and have access.
On my system it gives the mount point ownership of root and the group of vboxsf (root:vboxsf). or it will create /home/wu-tang/data and mount your share. it will mount your share if the /home/wu-tang/data exists. In the Shared Folders editor I can designate the (host's) share name and I can also give a path for the mount point of directory you wish to use as a mount point on the guest, like /home/wu-tang/data. 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 I mount my shared folder in /etc/fstab like:
0 kommentar(er)
