Mac OS X: Must run VirtualBox at least once before running `vagrant up` about vagrant HOT 7 CLOSED

Great idea! I didn't even know this happened since this situation has never occurred to me, but now that its brought up it makes sense =] I'll work on this soon and update this issue once it has been fixed.

from vagrant.

Give a useful error if the VirtualBox.xml is not found [closed by 723c36c]

from vagrant.

mscottford,

This has been implemented in the latest commit here: http://github.com/mitchellh/vagrant/commit/723c36cb1d460647fb92fa61f5a7f537776af0d1

Mitchell

from vagrant.

Hi Mitchell,

You, sir, are incredibly efficient!

Thanks,
-Scott

from vagrant.

I'm still seeing the same thing, though launching VirtualBox didn't fix it. Every time I run 'vagrant up' it creates a whole new VM (which works if I start it manually in VB), but still gives the same error.

from vagrant.

marcus,

So vagrant up for you is actually creating the VM properly, and not giving the above error? If so, what actually is giving an error and what exactly is that error?

Mitchell

from vagrant.

No, it was creating the VM in VB (but didn't start it), then dying with the errror given here. This has gone away now the other problem I had is fixed - running it not in my home dir did not cause this error - perhaps not a coincidence?

from vagrant.