-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 14.0.1 - Errors with newest integration tools #1115
Comments
Nothing we can do but wait for Parallels to offer a patch/fix, I backed off 14 for the last release because it broke all the drivers. |
There is a workaround: Parallels/vagrant-parallels#325 (comment) I've made a patch for bento (adapted from vagrant-parallels, see https://github.com/Parallels/vagrant-parallels/blob/master/lib/vagrant-parallels/guest_cap/linux/mount_parallels_shared_folder.rb#L103): diff --git a/_common/parallels.sh b/_common/parallels.sh
index 16b3644..7ce801f 100644
--- a/_common/parallels.sh
+++ b/_common/parallels.sh
@@ -20,5 +20,16 @@ parallels-iso|parallels-pvm)
umount /tmp/parallels;
rm -rf /tmp/parallels;
rm -f $HOME_DIR/*.iso;
+
+ # Parallels Tools for Linux includes native auto-mount script,
+ # which causes losing some of Vagrant-relative shared folders.
+ # So, we should disable this behavior.
+ # https://github.com/chef/bento/issues/1115
+ auto_mount_script='/usr/bin/prlfsmountd'
+ if [ -f "${auto_mount_script}" ]; then
+ echo -e '#!/bin/sh\n'\
+ '# Shared folders auto-mount is disabled by Vagrant ' \
+ > "${auto_mount_script}"
+ fi
;;
esac I can send a PR if you are ok to accept it. |
@max-arnold please do submit the PR - I'm currently out for a family thing but I'll review and merge later this week if it's viable. |
This is fixed as per above - images will be released early next week ideally. |
Version:
Latest bento commit (below), Vagrant 2.1.5
edab452
Environment: [Details about the environment such as the Operating System, cookbook details, etc...]
Parallels 14.0.1
Scenario:
When I build Bento locally (the published boxes work fine), and I use the latest integration tools from parallels, I get the below error on some of my machines on boot. This doesn't happen with the current published box (v201808.24.0), that uses an old version of parallels tools.
This issue does not happen with Parallels 13.
Any way I can help troubleshoot this?
The text was updated successfully, but these errors were encountered: