![Vagrant:VMware“vmnet”设备无法启动](https://linux22.com/image/128808/Vagrant%EF%BC%9AVMware%E2%80%9Cvmnet%E2%80%9D%E8%AE%BE%E5%A4%87%E6%97%A0%E6%B3%95%E5%90%AF%E5%8A%A8.png)
我刚刚在 Vagrant 中安装了来自 HashiCorp 的“vagrant-vmware-fusion”5.0.4 官方插件。
我正在使用 Vagrant 和在 High Sierra 中运行的 VMWare Fusion 10。
但是,在vagrant up
为虚拟机执行此操作时,我遇到了错误。
根据错误消息中的建议,我已重新启动,但错误仍然发生。
该怎么办?
$ 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.
答案1
重新启动几次后,我决定在调用该vagrant up
命令之前启动“VMware Fusion”试试运气。
它确实有效;vagrant up
不会启动 VMWare fusion,因此,您必须运行它才能vagrant up
部署虚拟机。
最终,错误消息可能会更加清晰。
答案2
对我来说,在 OSX Catalina(在 2018 年的 mac-mini 上)上,这是一个完全不同的解决方案:
进入“系统偏好设置”->“安全和隐私”->“完整磁盘访问”并选中 VMWare Fusion 复选框后,问题就消失了。
做完这个 vagrant up 工作就顺利了。为了完整起见,这一切都发生在 Vagrant VMWare Utility v1.0.18 w/VMware Fusion 12.1.0 Pro 上。
奇怪的是,在不同的 Mac(也是 Catalina,但 2017 Macbook Pro)上,我不必这样做,而且我从未遇到过这个问题。
答案3
答案4
我遇到了这个错误消息。我有另一个正在运行的暂停的 VMware fusion VM。我关闭了暂停的虚拟机,再次执行“vagrant up”。 vagrant 会话已经过去了错误消息。