-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parallels 10 & 1.2.2, Failed to mount folders #135
Comments
You have set unsupported mount options to the It is working fine with previous provider version because there was another approach for synced folders. So, having the latest provider version (>= 1.2.0), I suggest you to use this configuration section to define synced folder: config.vm.provider "parallels" do |v, override|
override.vm.synced_folder "<path_on_your_host>", "/var/www/html", mount_options: ["share"]
end
P.s. I defiantly should fill the documentation with all mount options supported by |
ah, I didn't realise those were virtual box specific. Thanks, that works now! |
Mount options "dmode" and "fmode" are unavailable for "prl_fs" filesystem. Use mount option "share", which provides liberal access permissions to shared folders. Related issue: Parallels/vagrant-parallels#135
Thanks @legal90. Your example override works great. For those coming along in the wake (like myself), note that "config" is misspelled as "convig" in the current example. No biggie, just make sure to change to the correct spelling or there'll be a big ugly stack output waiting for you when you run your Vagrantfile ;) |
Oops, Sorry for that mistake 😦 |
no problem. thanks! |
I got around this by manually reinstalling the Parallels Tools for Linux as indicated in https://download.parallels.com/desktop/v12/docs/en_US/Parallels%20Desktop%20User%27s%20Guide/32791.htm |
I have just upgraded to parallels 10 and the plugin to 1.2.2. The VMs don't start anymore. It did install Parallels Tools and reboot the vm before getting this error:
I also tried 1.2.0 with parallels 9 & 10, and im getting the same error with a slightly different message ("vboxsf" instead of "prl_fs").
I have got it working for now, running version 1.1.0 of the plugin with parallels 9 & 10.
Any idea what might be causing this issue?
(Using ubuntu 14.04 (https://vagrantcloud.com/parallels/ubuntu-14.04))
The text was updated successfully, but these errors were encountered: