Closed elimentz closed 6 years ago
Just rolled back to vagrant version 1.9.8, same problem
Hello
Please link a repo where we can clone and vagrant up
otherwise is not easy to repro.
At this moment the error is coming from vmware.
Can you open vmware gui and try to create and boot a vm. ?
Alvaro.
Hi,
@kikitux I get the same error message trying to start the box : puphpet/ubuntu1404-x64
OSX 10.12.6 VMware Fusion 10.0.1 Vagrant 2.0.1 Vagrant plugin vagrant-vmware-fusion 5.0.4
Vagrantfile
Vagrant.configure("2") do |config|
config.vm.provider :vmware_fusion do |vmware, override|
override.vm.box = "puphpet/ubuntu1404-x64"
end
end
vagrant up
Adding vmware.gui = true
in the Vagrantfile makes VMware display the error message : "Cannot find a valid peer process to connect to".
The same setup works with VMware Fusion 8.5.9 so I suspect this is an integration issue with the new VMware Fusion version 10.
Karl
This does not seem to be a Vagrant issue so I'm going to close this issue. Cheers!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Vagrant version
2.0.1
VMWare version:
10.0.1
VMware fusion provider version:
5.0.3
Host operating system
OSX High Sierra
Guest operating system
Ubuntu Xenial 16.04 LTS x64
Vagrantfile
Vagrant file is not going to be much use but I will include it here anyways. I got the vagrant file from Puphpet. I've been using this box for months, never had a problem.
Please note, if you are using Homestead or a different Vagrantfile format, we may be unable to assist with your issue. Try to reproduce the issue using a vanilla Vagrantfile first.
Debug output
Expected behavior
I want to start my vagrant box and log in
Actual behavior
Errors, see debug output
Steps to reproduce
I did a clean install everything: vagrant, VMware, provider - everything. I ran vagrant up and the problem occurred