Re: [vagrant-up] Vagrant upgrade 1.0.5 to 1.2.2 - result in I can not start my vm's anymore

[Dominic Lüchinger]

Dear Geff

On 09/06/13 23:59, Geff wrote:

> after upgrading Vagrant 1.0.5 to 1.2.2 on Mac 10.8.4 I can't start my
> VM's anymore.
>
> I had just ran the vm in 1.0.5 and successfully stopped it with vagrant
> halt.
> I had virtualBox 4.1.22 running whilst upgrading, no machines was running.
>
> After the upgrade I get this error in all the VM's:
> "$ vagrant up
> Bringing machine 'default' up with 'virtualbox' provider...
> There are errors in the configuration of this machine. Please fix
> the following errors and try again:
>
> vm:
> * The box 'lucid32' could not be found."
> (box name varies of course)
>
> Anyone have any idea how I can get the machines working again?
> (preferably as they are, since I'm developing my support for doing this
> from config only and hence they boxes are not quite automagically built
> yet.)
>
> The id in the old .vagrant matches the id in the new
> .vagrant/machines/default/virtualbox/id and they match the machine id in
> the virtual box machine.

Take a look at:
https://github.com/mitchellh/vagrant/issues/1691
It might be related to your problem.

Kind regards

Dominic

[Geff]

Hei Dominic,

thanks for pointing me in this direction and thanks to Mitchell Hashimoto for the fix.

I now can boot two of the machines so looks like this fixed it.

Back to me now to fix the failing chef processing :-(

regards

Geff