VMWare Fusion & HGFS kernel module not found

[radeksimko]

If I want to bring up a halted VM with a VMWare Fusion provider and forget about specifying the --provider option, Vagrant apparently detect the provider, but it doesn't start the VM correctly anyway:

radeksimko@my-mac:personal-mac $ vagrant up
Bringing machine 'default' up with 'vmware_fusion' provider...
==> default: Verifying vmnet devices are healthy...
==> default: Preparing network adapters...
==> default: Starting the VMware VM...
==> default: Waiting for the VM to finish booting...
==> default: The machine is booted and ready!
==> default: Forwarding ports...
    default: -- 22 => 2222
==> default: Configuring network adapters within the VM...
==> default: Waiting for HGFS kernel module to load...
The HGFS kernel module was not found on the running virtual machine.
This must be installed for shared folders to work properly. Please
install the VMware tools within the guest and try again. Note that
the VMware tools installation will succeed even if HGFS fails
to properly install. Carefully read the output of the VMware tools
installation to verify the HGFS kernel modules were installed properly.

If I halt the machine and bring it up again with vagrant up --provider=vmware_fusion, everything (HGFS) works well again.

I haven't dived into the code yet, but it looks like some parts of Vagrant can detect the provider and react accordingly and some not.

[mitchellh]

The detection is very simple:

lsmod | grep -i hgfs

The HGFS module in VMware is flaky and very often doesn't come up cleanly on first boot depending on how the system is configured. I've reported this to VMware but haven't heard back yet. Ultimately, not an issue that Vagrant can help with yet as far as I know. Sorry!