Vagrant up stuck on network setup with VMware provider on macOS 11

Hi there,

I am having issues setting up a very basic Vagrant box with VMware provider (Fusion 12) on macOS 11.

This happens when not specifying any network settings at all:

Vagrantfile:

Vagrant.configure(“2”) do |config|
config.vm.box = “centos/7”
end

vagrant up --provider=vmware_desktop
Bringing machine ‘default’ up with ‘vmware_desktop’ provider…
==> default: Cloning VMware VM: ‘centos/7’. This can take some time…
==> default: Checking if box ‘centos/7’ version ‘2004.01’ is up to date…
==> default: Verifying vmnet devices are healthy…
==> default: Preparing network adapters…
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING:
WARNING: ethernet0.pcislotnumber = “32”
WARNING:
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING:
WARNING: Vagrant.configure(2) do |config|
WARNING: config.vm.provider :vmware_desktop do |vmware|
WARNING: vmware.vmx[“ethernet0.pcislotnumber”] = “32”
WARNING: end
WARNING: end
WARNING:
WARNING: For more information: https://www.vagrantup.com/docs/vmware/boxes.html#vmx-allowlisting
==> default: Starting the VMware VM…
==> default: Waiting for the VM to receive an address…

Here it’s stuck

This happens when specifying a private network:

Vagrantfile:

Vagrant.configure(“2”) do |config|
config.vm.box = “centos/7”
config.vm.network “private_network”, ip: “192.168.33.20”
end

vagrant up --provider=vmware_desktop
Bringing machine ‘default’ up with ‘vmware_desktop’ provider…
==> default: Cloning VMware VM: ‘centos/7’. This can take some time…
==> default: Checking if box ‘centos/7’ version ‘2004.01’ is up to date…
==> default: Verifying vmnet devices are healthy…
Vagrant failed to create a new VMware networking device. The following
error message was generated while attempting to create a new device:
Failed to create new device
Please resolve any problems reported in the error message above and
try again.

Any help is much appreciated!

I confirm, I have exactly the same issue, MacOS Big Sur Beta 10 + Fusion 12 Pro + latest version Vagrant.

I experience the same issue, which is a shame since I discovered this issue just after upgrading VMWare and the vagrant vmware provider (and discovering this upgrade requires a paid upgrade…).
My configuration:
MacOS Catalina + Fusion 12 Pro + latest version of vagrant.

Any chance that we see at least a workaround for this issue?