can't start my VM on Vagrant 1.5.1

[alexeyOnGitHub]

Windows 7 64bit.

I have a VM created with Vagrant 1.4. I downloaded Vagrant 1.5.1 today and tried bringing the machine up with it (tried up/halt/reload) :

$~/vagrant (master)
$ vagrant reload
c:/Vagrant/embedded/lib/ruby/2.0.0/rubygems/version.rb:191:in initialize': Malformed version number string virtualbox (ArgumentError) from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/box_collection.rb:273:innew'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/box_collection.rb:273:in block (2 levels) in find' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/box_collection.rb:270:inmap'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/box_collection.rb:270:in block in find' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/box_collection.rb:416:inblock in with_collection_lock'
from c:/Vagrant/embedded/lib/ruby/2.0.0/monitor.rb:211:in mon_synchronize' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/box_collection.rb:415:inwith_collection_lock'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/box_collection.rb:263:in find' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/vagrantfile.rb:147:inblock in machine_config'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/vagrantfile.rb:180:in call' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/vagrantfile.rb:180:inmachine_config'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/vagrantfile.rb:45:in machine' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/environment.rb:416:inmachine'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/plugin/v2/command.rb:142:in block in with_target_vms' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/plugin/v2/command.rb:175:incall'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/plugin/v2/command.rb:175:in block in with_target_vms' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/plugin/v2/command.rb:174:inmap'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/plugin/v2/command.rb:174:in with_target_vms' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/plugins/commands/reload/command.rb:36:inexecute'
from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/cli.rb:42:in execute' from c:/Vagrant/embedded/gems/gems/vagrant-1.5.1/lib/vagrant/environment.rb:248:incli'
from c:/Vagrant/bin/../embedded/gems/gems/vagrant-1.5.1/bin/vagrant:158:in `

'

[mitchellh]

The upgrade didn't suceed for some reason:

echo "1.1" > ~/.vagrant.d/setup_version

Run vagrant again

[alexeyOnGitHub]

that helped, thank you.

$ echo "1.1" > ~/.vagrant.d/setup_version

$~/portals/tools/vagrant (master)
$ vagrant reload
Vagrant is upgrading some internal state for the latest version.
Please do not quit Vagrant at this time. While upgrading, Vagrant
will need to copy all your boxes, so it will use a considerable
amount of disk space. After it is done upgrading, the temporary disk
space will be freed.
==> default: Attempting graceful shutdown of VM...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 80 => 9099 (adapter 1)

[allaire]

I had the same issue, I would love to have some explanation on this @mitchellh ! Should we nuke that file when installing a new version?

I normally delete the content of ~/.vagrant.d/gems directory and ~/.vagrant.d/plugins.json when upgrading to a major version.

[wvega]

I upgraded from Vagrant 1.4.? to Vagrant 1.5.2 yesterday and found the same problem. @mitchellh instruction fixed it for me.

The content of the setup_version filter after the upgrade and before using @mitchellh instruction was:

$ cat ~/.vagrant.d/setup_version
1.5

When I read "The upgrade didn't succeed for some reason" in Mitchell's comment I was hoping to find a value lower than 1.1 in my setup_version but found 1.5 instead. Is that ok or could be a problem with the installer?

[peoplemerge]

Very helpful, fixed my issue with the same name. Thanks!

[ammmze]

I tried deleting ~/.vagrant.d/gems, ~/.vagrant.d/plugins.json and ~/.vagrant.d/setup_verion with no luck. However killing the entire ~/.vagrant.d directory did work, though i'm sure it was over the top.

[kevinmeredith]

+1 for @ammmze's solution - rm -rf ~/.vagrant.d.

Note that you'll have to download your boxes again. Sparing the directory containing the boxes is probably a good idea.

[drpebcak]

Also you'll have to install plugins again.

[tehranian]

FWIW - Just hit this upgrading my Mac from 1.4.3 to 1.5.4.

[lsaffie]

I upgraded to 1.6.3 and had this same issue.
echo "1.1" > ~/.vagrant.d/setup_version
did it for me. I never tried rm -rf ~/.vagrant.d but I'm sure that would've also worked based on everyones's experience.

Thanks

[vinyar]

I hit this from 1.3.5 to 1.6.3. I tried setting the file to 1.6, but got an error from Vagrant about new version being installed and a request to reinstall vagrant (which I did). Also, 1.6.3 didn't see any of my boxes with 'vagrant box list' so I rm -ef .vagrant.d which seemed to fix the issue.

[dergachev]

Same story as @lsaffie

After upgrading from 1.4 to 1.6.3, I got this error and the following seems to have fixed it:

echo "1.1" > ~/.vagrant.d/setup_version

[dalareo]

+1 rm -rf ~/.vagrant.d

[jopo79]

Thanks it works.
rm -rf ~/.vagrant.d

[emimarz]

+1 rm -rf ~/.vagrant.d

[lvillasica]

💯 👍 rm -rf ~/.vagrant.d

[ghost]

This is not a solution. I have 22 vagrant boxes built and defined, and (re)building 340gb of boxes I have spent months and months building and refining because some install/upgrade error cannot be fixed is totally uncalled for. Even the thought of having to export/reinstall/import them is seriously out of line!

[kwilczynski]

I have the same problem and nothing seem to be able to resolve it. The box is built with Packer (which should be irrelevant). I can list boxes with vagrant box list but any other command like e.g., vagrant up or vagrant status would fail with the aforementioned version. Prior to upgrading to latest release of Vagrant everything was working fine.

Update: I even tried the popular boxes by Chef from https://github.com/chef/bento, and the same issue.

[adioe3]

What worked for me was making sure the Vagrantfile has the box name instead od ., try changing this line:

  config.vm.box = "."

to your box name, for example:

  config.vm.box = "centos/7"

You can find out the box name with vagrant box list:

$ vagrant box list
centos/7 (virtualbox, 1804.02)

[ghost]

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.