VirtualBox 2.1.2 Failed to create COM object + compile issue

[drescherjm]

Now after starting hal and rebooting this has caused me several unexpected problems. From a keyboard mapping problem to a serious problem with hdparm setting drives to power down. It looks like I will be running without hal...

[Grogan]

Yep, by golly it's working now.

I found that BOTH dbus and HAL needed to be installed, but it will work with neither of them running. I first tried it with dbus-daemon stopped (before going through all the bullshit of preparing my system for HAL) but VirtualBox 2.1.2 was still throwing the same error.

After installing HAL, I tried VirtualBox 2.1.2 while dbus was running, and it would not start (same error). I killed dbus-daemon and it works now.

So I'll just take all that stuff out of the runlevels. It can sit there unused just as dependencies as long as VirtualBox works.

Thanks guys, I really appreciate the help. I'd have not guessed this stuff because it was not complaining about missing dependencies in the usual manner. (and 2.1.0 worked without them being installed)

[qu1j0t3]

Hello

I've upgraded, I've installed fresh. Same problem. When I go to run VirtualBox I get a dialog:

Failed to Create the VirtualBox COM Object

Callee RC:
NS_ERROR_ABORT (0x80004004)

I had the same problem on my Arch Linux with VirtualBox 2.12. Running hal deamon solves it.

I'd like to confirm that this solves the problem on my Gentoo (x86) as well:

Code: Select all

deepthought ~ # /etc/init.d/hald start
 * Starting Hardware Abstraction Layer daemon ...                         [ ok ]
deepthought ~ # rc-update add hald default
 * hald added to runlevel default

VB 2.1.2 then starts normally.

[nahun]

Installing hal now, but just stopping dbus worked for me too. I came by this thread from Google, so thanks everyone. Hopefully others will see this too and it'll help them.