[Solved] VirtualBox 4.3.x not working on OSX 10.9

[jfarr]

I've been using version 4.2.26 for about a year without issues, but need to upgrade now. Problem is that after the upgrade, attempting to start the virtualbox application results in:

Code: Select all

Failed to create the VirtualBox COM object.

The application will now terminate.



Callee RC: NS_ERROR_ABORT (0x80004004)

Attempting to use the command line goes like this:

Code: Select all

Jeff-Farrs-MBP:Dyn-RTD jfarr$ VBoxManage list
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

I've attached a crash report from Library/Logs/DiagnosticReports. The extension was renamed from .crash to .txt to appease the uploader.

Reguarding the min required data for assistance, please understand I can't even start the virtualbox app, much less get a guest running so there is no guest information to post.

If I revert to 4.2.x the issue goes away. I've tried 4.3.2, 4.3.16 and 4.3.12.

This issue has stopped all development for me. Version 4.3+ is needed to resolve this issue (I can post as soon as I'm allowed)


(.... seems the you-are-ell filter doesn't even allow those three letters in sequence? seems harsh)

[loukingjr]

try running the VirtualBox_Uninstall.tool first. Then try reinstalling. If a no go, try repairing disk permissions.

[jfarr]

Fantastic, the Repair Disk Permissions option in Disk Utility seems to have resolved the issue!

Thanks for the help, much appreciated.

[jfarr]

Ugh.. unfortunately the issue has re-appeared. I've tried the same cycles of uninstall/reinstall/downgrade as before, and also the Repair Disk Permissions. To no avail this time

Code: Select all

Jeff-Farrs-MBP:rest_framework jfarr$ vagrant init
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
Jeff-Farrs-MBP:rest_framework jfarr$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["list", "hostonlyifs"]

Stderr: VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

Can someone offer me some info about where to look in logfiles to see the root cause?

Thanks again,
-Jeff

[Perryg]

Vagrant is not supported here and is more than likely what is causing your permission issue.
Seek support from the vagrant folks.

[jfarr]

The error is with VBoxManage:

Code: Select all

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["list", "hostonlyifs"]

Stderr: VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

The same error occurs if I try to run the VirtualBox.app directly

[Perryg]

And what does VBoxManage list hostonlyifs return if run from the terminal? Is the hostonly package installed and running and is the guest configured to use it?

[loukingjr]

The error is with VBoxManage:

The same error occurs if I try to run the VirtualBox.app directly

Your conclusion would hold a lot more weight if there weren't hundreds if not thousands of Mac users running VirtualBox without your error who aren't running Vagrant.

[jfarr]

Running the vboxmanage direct:

Code: Select all

Jeff-Farrs-MBP:django jfarr$ vboxmanage list hostonlyifs
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Unknown exception
VBoxManage: error: /Users/vbox/tinderbox/4.3-mac-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp[534] (nsresult VirtualBox::init())
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component VirtualBox, interface IVirtualBox

Looking into the rest of your questions now.

[loukingjr]

No Vagrant installed…

Code: Select all

Mac-10ddb1bd02d8:~ louis$ vboxmanage list hostonlyifs
Mac-10ddb1bd02d8:~ louis$ 

[jfarr]

I'm aware that this generally works. What I need is information on how to fix this particular situation, thanks.

With vagrant uninstalled, for your edification:

Code: Select all

Jeff-Farrs-MBP:rest_framework jfarr$ vboxmanage list hostonlyifs
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
Jeff-Farrs-MBP:rest_framework jfarr$ vagrant --version
-bash: /usr/bin/vagrant: No such file or directory

[loukingjr]

I'm aware that this generally works. What I need is information on how to fix this particular situation, thanks.

Really. I thought you said the error was with vboxmanage. Vagrant is not supported here.

[jfarr]

Since beating a dead horse is on the menu:

vagrant is now uninstalled from my system by using their uninstall tool. Same results. The issue, by all appearances is with VBoxManage.

Code: Select all

Jeff-Farrs-MBP:rest_framework jfarr$ vboxmanage list hostonlyifs
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.
Jeff-Farrs-MBP:rest_framework jfarr$ vagrant --version
-bash: /usr/bin/vagrant: No such file or directory

[loukingjr]

Did you reboot? I don't know what Vagrant may or may not of done to VirtualBox but I would first just try rebooting. If that doesn't work, uninstall VirtualBox with its uninstall tool, repair disk permissions, reboot, then reinstall VirtualBox.

[jfarr]

There is still some evidence that the issue has something to do with disk permissions, you can see a change in error messages below which shows what happens immediatly after running Repair Disk Permissions (on a fresk virtualbox install).

Not sure why the error is different after the first attempt.

Code: Select all

Jeff-Farrs-MBP:rest_framework jfarr$ vboxmanage list hostonlyifs
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Unknown exception
VBoxManage: error: /Users/vbox/tinderbox/4.3-mac-rel/src/VBox/Main/src-server/VirtualBoxImpl.cpp[534] (nsresult VirtualBox::init())
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component VirtualBox, interface IVirtualBox
Jeff-Farrs-MBP:rest_framework jfarr$ vboxmanage list hostonlyifs
VBoxManage: error: Failed to create the VirtualBox object!
VBoxManage: error: Code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available)
VBoxManage: error: Most likely, the VirtualBox COM server is not running or failed to start.

I'm more than happy to do the dirty work here, but at the moment I don't yet know which logs to look at.


I'll cycle through: clean vbox and vagrant, restart, install vbox and test, repair disk permissions, install vagrant and test now. Will report back.

Per your comments earlier, this setup is working just fine for other team members.. but we've yet to identify what is different about my setup.