Vagrant up didn't work

I'm using Linux Mint 14 x64, and installed Vagrant and VirtualBox, (both from apt-get and the deb from site).

In all the cases I try I get the same error: http://img5.imageshack.us/img5/5143/screenshotlv.png

Any hints?

Sorry You must be a logged in, registered user to answer a question.

Answers

I have also gotten this error. The weird thing is that everything worked fine the first time I went through the steps. I decided to go back and start from scratch, and now cannot get it to work anymore.

I opened up the GUI and tried launching from there, but that also produced an error.

I have also attempted to remove boxes, create new ones, and basically just played around with commands. I even uninstalled Vagrant and reinstalled it. Now I'm just always getting that error.

I'm going to mess around with it and let you know if I come up with anything.

Koji on
In my case I had to enable Intel Virtualization Technology setting in the Gigabyte's MOBO BIOS. It cames disabled by default. But... my vagrant up stopped in another error. I will make another topic for that!
staticdev on
So I may have found a solution. It turns out that in my BIOS there was a setting to allow for a 'Virtual Machine' with my processor settings. It was disabled. I changed it disabled, and now I no longer get the error message. I'm getting some other error message, but at least it seems like progress.
Koji on

Vagrant up didn't work for me either, both on Mint and Windows , the only way was to change the box from precise64 to precise32, and it worked.

mutassem on
I had same issue on mint64 and changing to a precise32 vagrant box worked as well.
Matt Hamada on
Changing to precise32 worked for me! Yes, I have a 32-bit kernel!
raghu on
Maybe you don't have virtualization enabled like the other answer?
Mahmoud Hossam on
Interesting.. just for the sake of curiosity.. which linux distribution do you use? Have you ever installed vagrant via package manager or apt-get?
staticdev on
Strange. I don't know of any reason why the precise64 image wouldn't work.
kennethlove (Staff) on
$ uname -r 3.5.0-17-generic $ uname -m x86_64
staticdev on
I assume you're running a 32bit kernel, then?
kennethlove (Staff) on