Dear Linuxers, I've the same problem the original op raised and more than a month later this is still unsolved (at least on my machine).
I've installed: - dkms-2.1.0.1-1.fc12.noarch - VirtualBox-OSE-3.2.6-2.fc13.x86_64 - kmod-VirtualBox-OSE-3.2.6-1.fc13.9.x86_64
still a FC13 with the repo Steven's suggested but yum says that nothing needs to be updated and still VirtualBox silently quit with the VBoxVMM.so missing message.
Any idea?
Walter
On Fri, 29 Oct 2010, Steven Stern wrote:
On 10/29/2010 01:36 PM, Tod Thomas wrote:
The full messages is:
VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: VBoxVMM.so: cannot open shared object file: No such file or directory
The VBoxVMM.so file is in the same directory as the VirtualBox.so file. Also:
ldd /usr/lib/virtualbox/VirtualBox.so linux-gate.so.1 => (0x00bec000) libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00110000) libGL.so.1 => /usr/lib/libGL.so.1 (0x00961000) VBoxVMM.so => /usr/lib/virtualbox/VBoxVMM.so (0xb7625000)...
shows its in the correct dir.
This thread suggests it has something to do with glibc: https://bugzilla.redhat.com/show_bug.cgi?id=645500
This thread suggests it has been fixed: https://bugzilla.rpmfusion.org/show_bug.cgi?id=1465
If all of this information is correct will it soon become part of the FC13 yum update stream?
Thanks - Tod
I strongly recommend installing Virtual Box from the repo at VirtualBox.org. Scroll down a bit on http://www.virtualbox.org/wiki/Linux_Downloads to find instructions for installing the repo. After that, "yum update" keeps things in line.