Vagrant on Mac OS X can't start

[Larry Zhao]

Guys,

I am just trying out Vagrant with virtual box on my Mac OSX Mountain Lion.

I installed the latest VirtualBox 4.3.0 and installed the latest Vagrant V2 and trying to fire up a Ubuntu precise 32 like the Getting Started Doc said, but I got this:

○ → vagrant up
/Applications/Vagrant/embedded/gems/gems/vagrant-1.3.5/lib/vagrant/util/which.rb:32: warning: Insecure world writable dir /Applications in PATH, mode 040777
Bringing machine 'default' up with 'virtualbox' provider...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

I tried it with VirtualBox GUI on and got this in the log:

VirtualBox VM 4.3.0 r89960 darwin.amd64 (Oct 15 2013 12:50:16) release log
00:00:00.965199 Log opened 2013-10-21T16:04:26.347891000Z
00:00:00.965200 Build Type: release
00:00:00.965214 OS Product: Darwin
00:00:00.965219 OS Release: 12.5.0
00:00:00.965222 OS Version: Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64
00:00:00.965341 DMI Product Name: MacBookPro8,1
00:00:00.965405 DMI Product Version: 1.0
00:00:00.965412 Host RAM: 8192MB total, 3548MB available
00:00:00.965413 Executable: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM
00:00:00.965414 Process ID: 13789
00:00:00.965415 Package type: DARWIN_64BITS_GENERIC
00:00:00.967191 Installed Extension Packs:
00:00:00.967199   None installed!
00:00:00.969694 pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_SUPLIB_WORLD_WRITABLE szErr="World writable: '/Applications'"
00:00:00.969716 VMSetError: /Users/vbox/tinderbox/4.3-mac-rel/src/VBox/VMM/VMMR3/VM.cpp(594) int vmR3CreateU(UVM*, uint32_t, int (*)(UVM*, VM*, void*), void*); rc=VERR_SUPLIB_WORLD_WRITABLE
00:00:00.969722 VMSetError: Failed to load VMMR0.r0
00:00:00.969848 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={Failed to load VMMR0.r0 (VERR_SUPLIB_WORLD_WRITABLE)}, preserve=false
00:00:00.972185 Power up failed (vrc=VERR_SUPLIB_WORLD_WRITABLE, rc=NS_ERROR_FAILURE (0X80004005))
00:00:01.407388 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={8ab7c520-2442-4b66-8d74-4ff1e195d2b6} aComponent={Console} aText={The object is not ready}, preserve=false

I've tried a lot of things but still can't get it up. What's the problem of my setup?

[Mitchell Hashimoto]

This looks like an issue with VirtualBox. Try to start the VM without
Vagrant, using only VirtualBox, and report a bug to the VirtualBox
folks.

Best,
Mitchell

> --
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Larry Zhao]

Hi, Mitchell,

I tried to start the image just from VBox, without Vagrant. But the error from the log is the same.

Yes, I am gonna open an issue to VBox, but does it work if I use an older version of VBox?

Thank you very much.

[Larry Zhao]

Hi, Guys, 

With the help of guys form VirtualBox, I found that it's my own problem. Permission of my /Application was drwxrwxrwx+ ,  that was a problem for the virtualbox because the /Application directory's permission is too wide. So after `chmod o-w /Application`, it's running now.

Sorry for the bothering to everyone.

[ss...@talenttech.com]

I have the same issue and fixed by doing chmod o-w /Applications. Thanks!

[Meir]

My thank you as well here added!