VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib64/virtualbox/VirtualBox.so",) failed: VBoxVMM.so: cannot open shar

VirtualBox OSE 3.2.10 Bug修复

fraannk

于 2010-11-30 15:58:00 发布

阅读量4.9k

点赞数

CC 4.0 BY-SA版权

文章标签： components file testing object

本文链接：https://blog.youkuaiyun.com/frank2336/article/details/6045686

本文记录了在 Fedora 14 中 VirtualBox-OSE-3.2.10-1.fc14.x86_64 版本遇到的一个问题及其解决办法。该问题是由于缺少必要的共享对象文件导致 VirtualBox 启动失败。通过创建指向 /usr/lib64/virtualbox 的符号链接到 /lib64 目录下，可以绕过此问题。

http://comments.gmane.org/gmane.linux.redhat.fedora.rpmfusion.devel/8527 https://bugzilla.rpmfusion.org/show_bug.cgi?id=1465

https://bugzilla.rpmfusion.org/show_bug.cgi?id=1465

in updates testing I found 
VirtualBox-OSE-3.2.10-1.fc14.x86_64

which have same problem of this bug and same work around 

# find /usr/lib64/virtualbox/ -name /*.so -exec ln -s -t /lib64 '{}' ';'

[frank@apollo virtualbox]$ VirtualBox

VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib64/virtualbox/VirtualBox.so",) failed: VBoxVMM.so: cannot open shared object file: No such file or directory

[frank@apollo components]$ su -c "find /usr/lib64/virtualbox/ -name /*.so -exec ln -s -t /lib64 '{}' ';'"

Password:

ln: creating symbolic link `/lib64/VBoxREM.so': File exists

ln: creating symbolic link `/lib64/VBoxVMM.so': File exists

ln: creating symbolic link `/lib64/VBoxDDU.so': File exists

ln: creating symbolic link `/lib64/VBoxXPCOM.so': File exists

ln: creating symbolic link `/lib64/VBoxRT.so': File exists

[frank@apollo components]$ VirtualBox