I noticed significant performance issues after upgrading to Maveric ks.. That is when I decided to try out Oracle Virtualbox.. More importantly some of the devops I was trying such as Vagrant and Docker did have readily available VMs for Virtualbox. But for security reasons (see above) this is disabled by default. Hey there, @Jakobud.I'm actually the one that came up with the solution you are currently using, and here is what I've been doing: I just comment this line out on the initial vagrant up, and I uncomment it for the rest of the time I'm using the machine.It's obviously far from ideal, but it works with little effort as long as you don't need to rebuild your machine all the time. The fix to prevent dangerous symlinks from the guest is very complicated, therefore we decided to not allow any guest to create any symlink to work around the security problem. So let's say that alice is a user on machine "darkstar" at 192.168.1.1. Dismiss Join GitHub today.
VBoxManage setextradata VM_NAME VBoxInternal2/SharedFoldersEnableSymlinksCreate 1 Then your guest will be able to create symlinks again. Then let's say that that NFS has been configured on darkstar to share out a certain directory, and allow connections from everything in the range 192.168.1.1 through 192.168.1.255. GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together. When building OpenCV-3.1.0 in Ubuntu 14.04 installed inside VirtualBox 5.0.16 (in Win7 host), I encountered the following error: cmake_symlink_library: System Error: Read-only file system Both the OpenCV source folder and build folder locate in a shared folder that resides outside the VirtualBox’s virtual hard disk (in my Win7 host drive). If you have not added virtualbox commands to your path, either do so or run VBoxManage from the folder where it is located. I have been using VMWare Fusion on my MBP for a while. Replace VM_name with the name of the virtual machine, and the name of shared_folder with the name of the shared folder in the settings of your virtual machine, Right click on your command prompt and “Run as Administrator” (or whatever program you’re using to make those symlinks needs to be run as adminstrator). This is fine: Vagrant guests can access the entire host filesystem.