Actually, using type: "vmware_desktop" or "vmware_fusion" results in:

`block in synced_folders': Internal error. Report this as a bug. Invalid: 
vmware_desktop (RuntimeError)

which is the same message as when specifying random text for the type, so I 
believe vmware is the correct value. I'm not sure why it doesn't work 
though. Here is my Vagrantfile:

Vagrant.configure("2") do |config| = "centos/7"

  # Disable the default rsync sync method:
  config.vm.synced_folder "./", "/vagrant", id: "vagrant-root", disabled: 
  # This just enables the folder using rsync again:
  config.vm.synced_folder "./", "/vagrant"
  # This (exporting a different location in the guest) syncs the folder 
using VMware:
  config.vm.synced_folder "./", "/vagrant2"
  config.ssh.insert_key = false

On Monday, September 19, 2016 at 1:27:51 PM UTC+8, Michael Vermaes wrote:
> When setting up the CentOS 7 box from 
> with the VMware Fusion 
> provider, /vagrant is always shared using the rsync method. Is there a way 
> to override this using the Vagrantfile? I've tried the following:
> - Setting different values for the 'type' of the synced_folder, such as 
> vmware/vmware_fusion/vmware_desktop, but this generates an error on reload:
> ...
> ==> default: Verifying vmnet devices are healthy...
> .../.vagrant.d/gems/gems/vagrant-vmware-fusion-4.0.11/lib/vagrant-vmware-fusion/synced_folder.rb:10:in
> `usable?': wrong number of arguments (2 for 1) (ArgumentError)
> ...
> - Setting the folder with id: "vagrant-root" to disabled, and then 
> redefining it on a new line. This is ignored, and rsync is still used.
> - Defining a second synced_folder with a different guest path (/vagrant2). 
> This works.
> Given the last point, I believe VMware Tools are set up correctly. The 
> Tools were configured by installing open-vm-tools from CentOS 
> repositorities and then adding the tools from the Fusion iso to get shared 
> folder support.
> Other version details:
> - OS X 10.11.6
> - VMware Fusion 8.5 (same behaviour with 8.1.1)
> - Vagrant 1.8.5
> - vagrant-vmware-fusion 4.0.11
> Thanks for any suggestions anyone can provide.

This mailing list is governed under the HashiCorp Community Guidelines - Behavior in violation of 
those guidelines may result in your removal from this mailing list.

GitHub Issues:
IRC: #vagrant on Freenode
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To view this discussion on the web visit
For more options, visit

Reply via email to