virtual box no longer starts after latest updates [Solved]

[gallienus]

After the latest group of updates virtual box no longer starts. I'm using the 64-bit version of the 2.6.34 kernel and version 3.2.10 of virtualbox. When I try to start virtualbox from the command prompt I get this

Code: Select all

darkmessiah@sabayon ~ $ VirtualBox
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/opt/VirtualBox/VirtualBox.so",) failed: VBoxVMM.so: cannot open shared object file: No such file or directory


I checked the file is there of course. And I'm using the correct kernel modules for virtualbox and I load the virtual box drivers with sudo modprobe vboxdrv. As far as I know this is the only program that's been affected.

You'll have to take "the latest group of updates" with a grain of salt. Before I rebooted sabayon tonight my computer had been up and running for 17 days. So it could be the latest updates or any that have happened in the last 17 days. Up until tonight's reboot virtualbox has been running fine.

After some searching I found this....http://www.salixos.org/forum/viewtopic.php?f=24&t=1447
Would something similar work with sabayon?

[joost]

I think you are correct.

http://www.virtualbox.org/ticket/7623

Because of a security issue we had to update glibc.
I can reproduce the problem on my system here.

[joost]

virtualbox-bin-3.2.10-r1 will be in Entropy soon.

[gallienus]

Wooohooo! The virtualbox-bin-3.2.10-r1 update solved the problem. I just downloaded it and virtual box started up and ran fine.