VirtualBox 2.1.2 Failed to create COM object + compile issue

[Grogan]

Hello

I'm using VirtualBox-2.1.2-41885-Linux_x86.run

Version 2.1.0 worked perfectly (and still does if I go back to it)

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 can't seem to figure this one out. I've deleted /etc/vbox and ~/.VirtualBox and I've deleted everything VirtualBox related from /tmp

---------------------------------------------------------------

Also, an unrelated problem compiling the modules. After the install, there are some symlinks in the src/vboxdrv and src/vboxnetflt source directories that prevent the compile operation from even starting. It just says "nothing to be done for all" if I do it manually. It says nothing if invoked through the installer. It just instantly shows that the modules compiled successfully. It had me chasing my tail. It wasn't until I upgraded my kernel and the old modules were gone that I realized they weren't compiling.

Removing /opt/VirtualBox-2.1.2/src/vboxdrv/vboxdrv and opt/VirtualBox-2.1.2/src/vboxnetflt/vboxnetflt symlinks allows the modules to compile normally, with make all in the src directory, and /etc/init.d/vboxdrv setup

The links just point back to the source directories:

lrwxrwxrwx 1 root root 33 Jan 22 21:27 vboxdrv -> /opt/VirtualBox-2.1.2/src/vboxdrv

lrwxrwxrwx 1 root root 36 Jan 22 21:27 vboxnetflt -> /opt/VirtualBox-2.1.2/src/vboxnetflt

----------------------------------------------------

But that ain't my problem, the modules compile and load correctly after removing those links. I'm not sure if that's "Bug Report" material or not so I'm just mentioning it here.

My problem is that I can't start the VirtualBox GUI because of the COM object error.

I would be grateful for any assistance here. My OS is a home built Linux from Scratch type system, and I'm currently using Linux 2.6.28.1 (was using 2.6.26.8 previously but that wasn't working either)

[bjlockie]

I have the same error "Callee RC: NS_ERROR_ABORT (0x80004004)".
I upgraded from 2.0.6 and I have kernel 2.6.28.1

[bjlockie]

Do you have x86_64 too?
I did strace and it is trying to load open("/opt/VirtualBox-2.1.2/tls/x86_64/libpthread.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
among other errors.
I have no "/opt/VirtualBox-2.1.2/tls" directory.

[bjlockie]

I ran VBoxSVC and VirtualBox:

./VBoxSVC
*********************************************
Sun xVM VirtualBox XPCOM Server Version 2.1.2
(C) 2008-2009 Sun Microsystems, Inc.
All rights reserved.

Starting event loop....
[press Ctrl-C to quit]
process 4251: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
D-Bus not built with -rdynamic so unable to print a backtrace
Aborted

So that doesn't help.

[Grogan]

No, I'm just running this on Linux x86

I have not made any further progress on this problem. I thought it might have been because I didn't have dbus, but I've since compiled, configured and started dbus (and dbus-glib while I was at it) and I still have the exact same error with VirtualBox.

I'm beginning to think this version is just a lost cause and I'll go back to version 2.1.0 which works perfectly for me.

[tpistor]

I have two opensuse 10.3 64-bit systems - a laptop and a desktop.

On laptop, virtualbox 2.1.2 is working.
On desktop, virtualbox 2.1.2 is not working with the following error:

VirtualBox Command Line Management Interface Version 2.1.2
(C) 2005-2009 Sun Microsystems, Inc.
All rights reserved.

[!] Failed to create the VirtualBox object!
[!] Primary RC = NS_ERROR_ABORT (0x80004004) - Operation aborted
[!] Most likely, the VirtualBox COM server is not running or failed to start.

So...I have proof that it works on opensuse 10.3, 64-bit - I just can't figure out why it works on one machine and not the other. I'm open to suggestions about looking at differences between the two systems.

[Grogan]

It's got to be something we're missing, or something that's different. It's obviously not happening to everyone, though we are not alone. There's at least one other forum thread with this same error here too.

I'm about to build a new compiler (c++ libraries come from gcc) and toolchain, and glibc with newer kernel headers and stuff. I think I'll get my system up to a more modern level and possibly might have better luck running binary software packages like this.

That may not solve this problem, but I'm having another problem even with VirtualBox 2.1.0. It crashes when trying to open certain browse dialogs (glibc's gconv related error) and I have to use VBoxManage to perform a few configuration operations.

[Grogan]

I'm about to build a new compiler (c++ libraries come from gcc) and toolchain, and glibc with newer kernel headers and stuff. I think I'll get my system up to a more modern level and possibly might have better luck running binary software packages like this.

That may not solve this problem, but I'm having another problem even with VirtualBox 2.1.0. It crashes when trying to open certain browse dialogs (glibc's gconv related error) and I have to use VBoxManage to perform a few configuration operations.

Well, a new glibc build and friends solved the browse dialog crash with VirtualBox 2.1.0, but as expected I still have the XPCOM error with VirtualBox 2.1.2. Oh well, at least I can browse for virtual disks and ISO images with Virtual Box 2.1.0 now.

[hoganx]

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.

[Grogan]

Ahh, thank you, that's something else to try. I don't have Hal. I can do that also (I've set up dbus and that didn't help). I've been happily using VirtualBox 2.1.0 though.

Shame though... I don't otherwise use dbus/hal. I'm from the old school. You want something to work, you create device nodes for it and load kernel modules. It has no choice but to work, and stays working.

I won't get a chance to try it for a few days, but it sounds like that will be the answer. It makes sense.

[phestar]

Good luck Grogan, I have the same problem (see http://forums.virtualbox.org/viewtopic.php?t=13633) but I'm running dbus in my system and VBox only works if I STOP dbus before starting VBox.

[hoganx]

I`ve tried to stop DBus and it works on my system too. So VBox 2.12 doesn`t work only when DBus is started and HAL isn`t.

[Grogan]

I saw that, but I didn't have dbus at all initially and I had the error. That would be quite odd if dbus needs to be installed and stopped as opposed to not installed. If it was a shared library thing (not everyone even has dbus compiled with shared library support) you'd think it would complain on the console about a missing library.

When I get to it (hopefully I can find some time tomorrow), perhaps I'll try that first before setting up Hal just to see.

I really appreciate you guys chiming in here,.

[drescherjm]

I have the same issue under 64 bit gentoo with the puel version and 2.1.2. 2.1.0 works without this problem.

Edit: It works after dbus is stopped.

[drescherjm]

I`ve tried to stop DBus and it works on my system too. So VBox 2.12 doesn`t work only when DBus is started and HAL isn`t.

Thanks, that was the key for me. When I added hal to my startup and rebooted all was well.