

File created in shared_folder actually resides in /media/sf_shared_folder. The above command will create a shared_folder directory under the user’s home. ln -s /media/sf_shared_folder /home/ /shared_folder You can create a soft link that points to /media/sf_shared_folder. Now you can access the /media/sf_shared_folder directory. Log out of the current session and log back in. Open up a terminal in the guest machine and enter the following command. So what we need to now is add your user to vboxsf group. By default, only root and members of the vboxsf group have read and write access to this directory. In /media/ directory of the Linux guest, you will find a new directory called sf_shared_folder if the shared folder name on the host is shared_folder. Check Auto-mount to auto-mount the shared folder when the guest OS boots up. You can check Read-only to let your guest have read access but no write permission to the shared folder on the host machine.

Then in the Folder Path field, select a folder on your host machine.

Then click on the add button to add a shared folder. In the Virtualbox Manager window, right-click on your guest machine and select Settings.

I suppose I should also ask: any chance Norton on the Windows system is interfering? Yet "touch" and "vi" allow me to write files in the share folder which Windows can then see. Very curiously, "ln -s" fails with "read-only file system". One more strange fact: "cp" to the share folder fails. I know it doesn't make sense but it's true. There's something different about what "cp" and "mv" do versus "touch" and "vi". It's NOT a simple matter of write protection / read only. Let me suggest considering for a moment how I can succeed at "touch" and "vi", creating new files in the shared folder from the Ubuntu guest session, but failing at "cp" and "mv". Either VirtualBox manager shared folder declaration OR terminal session "mount" but not both. I am assuming one or the other but not both. That also returns "no such file or directory".Ĭlarification: when using "mount" from terminal session, I presume you do NOT want a shared folder declared from the VirtualBox Manager, correct?
