An unexpected error occurred while loading the Vagrant VMware provider #3299

Closed
ubermuda opened this Issue Mar 24, 2014 · 9 comments

Projects

None yet

8 participants

@ubermuda

I just upgraded to Vagrant 1.5.1, and first command I run (vagrant destroy) gives me this:

An unexpected error occurred while loading the Vagrant VMware
provider. Please contact support with the following
error code: '7'.
Vagrant failed to initialize at a very early stage:

The plugins failed to load properly. The error message given is
shown below.

exit

Here's a gist of the run with VAGRANT_LOG=debug: https://gist.github.com/ubermuda/d0e8944390614d212ed4

@bartmcleod

Same problem here. I thought it was caused by migrating my MacBook. Any invocation of the vagrant command yields this error. Also vagrant 1.5.1

@mitchellh
Owner

I'm unsure what is causing this, but I've heard that nuking the home directory ~/.vagrant.d fixes things. You can save your boxes by preserving ~/.vagrant.d/boxes

@mitchellh mitchellh closed this Apr 2, 2014
@ubermuda
ubermuda commented Apr 2, 2014

Actually I reverted to vagrant 1.4.3, upgraded my plugins and re-upgraded to 1.5.1, and it worked.

@jeffbrabant

I upgraded to 1.5.3 on windows and I had this problem. I previously had the workstation plugin installed, but rerunning that command solved the issue.

vagrant plugin install vagrant-vmware-workstation

@bartmcleod

This worked for me too initiale, but with version 1.5.3 vagrant up with the vmware box gives me ruby errors complaining about the version. I also upgraded the plugin, uninstalled and re-installed it. Doesn't help. As far as I'm concerned 1.5.3. with the VMware provider is broken.

@jweir
jweir commented May 6, 2014

Just got this error when upgrading from 1.5 to 1.6

rm -rf ~/.vagrant.d/plugins.json

And I was able to move on. Then Vagrant ran an upgrade script.

FYI the only plugin I have installed is the vmware_fusion provider

@rwellens
rwellens commented May 7, 2014

I have just re-install my vmware Provider

vagrant plugin install vagrant-vmware-fusion

@AlexSatrapa

I had this error when upgrading from Vagrant 1.5 to 1.6.5 as well.

I removed the ~/.vagrant.d/plugins.json file and ran vagrant plugin install vagrant-vmware-fusion and everything is back to normal.

@PortNumber53

rm ~/.vagrant.d/plugins.json worked for me too, didn't have to do any plugin install

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment