Virtual Box virtualbox-5.0_5.0.26 and higher will not start

[viv]

Running Ubuntu 14.04 Trusty with kernel 3.13.0-92. virtualbox-5.0_5.0.24 is working but when I tried to move to virtualbox-5.0_5.0.26 or virtualbox-5.1_5.1.2 I get an error popup upon startup.
"Failed to create the VirtualBoxClient COM object. The application will now terminate. Callee RC: NS_ERROR_ABORT (0x80004004)" . What's the fix?

[Perryg]

Upgrade gcc and qt to newer versions.

[viv]

I'm already at the latest upgrade level for Ubuntu 14.04.4 LTS - gcc 4.8.4 and qt 5.2.1.You're saying I need to go beyond that if I upgrade Virtual Box to 5.0_5.26 or later? What version of gcc and qt is required?

[Perryg]

I have the following:

• gcc version 4.9.3
  Qt version 5.3.2

[viv]

I moved to Ubuntu 16.04 LTS xenial and still Virtual Box will not run. Tried both 5.1.4 and 5.0.26 and the message is the same. So I am forced to keep using 5.0.24. This OS is using gcc 5.4.0 and qt 5.5.1. Why won't any version higher than 5.0.24 work? What changes went into 5.0.26?

[Perryg]

From a working install, post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

As well as /var/log/vbox-install.log ( as an attachment ) after you try to upgrade and it failed.

[viv]

Attached is the log from a working VM using 5.0.24. I'll need to stop my VMs and try installing 5.0.26 to get the log from a bad install, few minutes.

[viv]

Screenshot from 2016-08-17 14-05-58.png (28.67 KiB) Viewed 7649 times

And the result of installing 5.0.26 is ...

[Perryg]

I just tried this again with Ubuntu 14.04 and 16.04 and it works for me. I looked at your log and can not see a reason why it would not work for you but that leads me to another question. You said you moved to Ubuntu 16.04. How exactly did you do that. Was it a Dist upgrade or a clean install?

[viv]

it was an upgrade. But remember that originally I was at 14.04 LTS and could not move to VB 5.0.26 or beyond either. Here is what dpkg says, maybe the previously installed packages are causing interference?

> dpkg --list | grep VirtualBox
ii unity-scope-virtualbox 0.1+13.10.20130723-0ubuntu1 all VirtualBox scope for Unity
rc virtualbox-4.2 4.2.32-101581~Ubuntu~precise amd64 Oracle VM VirtualBox
rc virtualbox-4.3 4.3.30-101610~Ubuntu~precise amd64 Oracle VM VirtualBox
ii virtualbox-5.0 5.0.26-108824~Ubuntu~trusty amd64 Oracle VM VirtualBox
rc virtualbox-5.1 5.1.4-110228~Ubuntu~xenial amd64 Oracle VM VirtualBox
bob_viveney@shvlhd>

[Perryg]

That was the reason I asked about the move. Upgrading usually will not eliminate the corruption that could be causing your issue. You can try to remove all the older packages apt-get autoclean && apt-get autoremove as well as purging the current install and install again. Purging does not involve nor harm the guests but it never hurts to backup to be safe.

[viv]

autoclean, autoremove, purging, reinstalling ... did not fix the problem. But I did run /usr/lib/virtualbox/VBoxSVC manually and tried starting virtualbox and that caused VBoxSVC to seg fault and I captured a core file. How do I get someone to look at it?

[Perryg]

Best place is bugtracker describing exactly what happened and ask where they want the dump posted.

[viv]

Created ticket #15820.

[UNIXSPOD]

Me too!

I hadn't rebooted for months, and my desktop was getting a bit tweaky, and there were many kernels between where I was and the latest, so I restarted my browser, and vBox, (the two heaviest users of RAM) vBox said it had an upgrade. I figured OK, I would download the upgrade, then reboot my system.

The upgrade was: VirtualBox-5.1-5.1.4_110228_openSUSE132-1.x86_64.rpm
This installed OK, then bailed with a strange undefined symbol error when loading the base library. I tried to load an earlier version i had on hand, 5.0.4 I think. But that just me gave me build errors with the kernel modules. So I tried VMware Player, that also gave me build errors, and demanded I upgrade gcc to 6.1.1, which I did. That too had build errors which I fixed, built the kernel objects, but they wouldn't load.

So I went back to vBox, downloaded the latest OpenSuse 13.1 build: VirtualBox-5.0-5.0.26_108824_openSUSE131-1.x86_64.rpm installed it, it built the binaries with DKMS (a first, normally has to build outside) They all loaded fine, but attempts to bring up the interface resulted in the error:

Code: Select all

Failed to create the VirtualBoxClient COM object.
The application will now terminate.

Callee RC: 
NS_ERROR_ABORT (0x80004004)

Then I came here, saw the requirement for a Qt upgrade, moved from 5.1.1 to 5.4.3, the daily zypper up, gave me another new tool chain, and a new version of vBox: VirtualBox-5.0-5.0.26_108824_openSUSE132-1 which appears to the the OpenSuse 13.2 build of the 13.1 version I already had. It built cleanly:

Code: Select all

Creating group 'vboxusers'. VM users must be member of that group!

No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.

Stopping VirtualBox kernel modules..done
Uninstalling old VirtualBox DKMS kernel modules..done
Trying to register the VirtualBox kernel modules using DKMS..done
Starting VirtualBox kernel modules..done

I still get the same COM object error: NS_ERROR_ABORT (0x80004004)

My environment:

Linux spod 4.7.1-4.g61bf3f1-default #1 SMP PREEMPT Tue Aug 16 14:32:45 UTC 2016 (61bf3f1) x86_64 x86_64 x86_64 GNU/Linux

gcc6-6.1.1+r239476-40.1.x86_64
libqt4-4.8.5-5.17.1.x86_64
libQt5Core5-5.4.2-75.1.x86_64