Vagrant：VMware“vmnet”设备无法启动

Question

我刚刚在 Vagrant 中安装了 HashiCorp 的 'vagrant-vmware-fusion' 5.0.4 官方插件。

我正在将 Vagrant 与在 High Sierra 中运行的 VMWare Fusion 10 一起使用。

但是，在vagrant up为 VM执行此操作时，出现错误。

正如错误消息中所建议的那样，我已重新启动，但错误仍在发生。

该怎么办？

$ vagrant up --provider vmware_fusion
Bringing machine 'default' up with 'vmware_fusion' provider...
==> default: Box 'hashicorp/precise64' could not be found. Attempting to find and install...
    default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation
    default: Box Version: >= 0
==> default: Loading metadata for box 'hashicorp/precise64'
    default: URL: https://vagrantcloud.com/hashicorp/precise64
==> default: Adding box 'hashicorp/precise64' (v1.1.0) for provider: vmware_fusion
    default: Downloading: https://vagrantcloud.com/hashicorp/boxes/precise64/versions/1.1.0/providers/vmware_fusion.box
==> default: Successfully added box 'hashicorp/precise64' (v1.1.0) for 'vmware_fusion'!
==> default: Cloning VMware VM: 'hashicorp/precise64'. This can take some time...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Verifying vmnet devices are healthy...
The VMware "vmnet" devices are failing to start. The most common
reason for this is collisions with existing network services. For
example, if a hostonly network space collides with another hostonly
network (such as with VirtualBox), it will fail to start. Likewise,
if forwarded ports collide with other listening ports, it will
fail to start.

Vagrant does its best to fix these issues, but in some cases it
cannot determine the root cause of these failures.

Please verify you have no other colliding network services running.
As a last resort, restarting your computer often fixes this issue.

Answer 1

重新启动几次后，我决定在调用vagrant up命令之前尝试启动“VMware Fusion” 。

它确实有效；vagrant up不会启动 VMWare fusion，因此，您必须运行它vagrant up才能部署 VM。

最终，错误消息可能会更清楚。