LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
LinkBack Search this Thread
Old 10-31-2010, 09:40 PM   #1
tron_thomas
Member
 
Registered: May 2004
Posts: 217

Rep: Reputation: 30
Can't run VirtualBox after Fedora 12 system update


I am running Fedora 12 on an Intel Core 2 Duo system.
I ran a software update which installed a new kernel (2.6.32.23-170.fc12.i686.PAE) along with many other things.
I am now unable to run VirtualBox which I had installed and running successfully before the update.
I tried removing and reinstalling VirtualBox from YUMEX, and rebooting. This did not help.
When I launch VirtualBox from a terminal, it produces the following output:

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

I'm not sure what it is complaining about. The files VirtualBox.so and VBoxVMM.so both exist in the /usr/lib/virtualbox directory.

What can be done to get VirtualBox working again on this system?
 
Old 11-01-2010, 05:57 AM   #2
AlucardZero
Senior Member
 
Registered: May 2006
Location: USA
Distribution: Debian
Posts: 4,570

Rep: Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510Reputation: 510
Recompile the kernel modules. Should be:
Code:
/etc/init.d/vboxdrv setup
 
Old 11-01-2010, 11:51 AM   #3
tron_thomas
Member
 
Registered: May 2004
Posts: 217

Original Poster
Rep: Reputation: 30
The file vboxdrv does not exist in the /etc/init.d directory on my system.
 
Old 11-02-2010, 10:05 AM   #4
mmidgett
LQ Newbie
 
Registered: Aug 2007
Posts: 4

Rep: Reputation: 0
You need to install DKMS, when you do a kernel update it will cause your virtual box to rebuild its drivers. Works like a charm on ubuntu. Not a fedora or redhat fan so I can't help with where to run the setup commands from.
 
Old 11-02-2010, 10:56 AM   #5
tron_thomas
Member
 
Registered: May 2004
Posts: 217

Original Poster
Rep: Reputation: 30
I used YUMEX to install DKMS. The problem still exits.

I can get Virtual Box to launch from the terminal if I use the sudo command to start it with root privileges. I cannot start it normally however.
 
Old 11-03-2010, 08:36 AM   #6
olego
Member
 
Registered: Sep 2008
Location: Kaliningrad, Russia
Distribution: Slackware
Posts: 35

Rep: Reputation: 1
I suppose that you've upgraded glibc to version 2.12.x?

Until Oracle release new version of VirtualBox, please use this solution:

cd /tmp
wget http://www.tux.org/pub/x/ftp.hungry....th-0.13.tar.gz
tar -zxvf chrpath-0.13.tar.gz
cd chrpath-0.13
./configure && make
cd /opt
ln -s VirtualBox V
cd VirtualBox/
/tmp/chrpath-0.13/chrpath -r /opt/V *.so

P.S. I don't use Fedora and I don't know how to prepare correct package. In my Slackware I packaged chrpath and spreaded it along my machines. So I suggest you to prepare native package for your distro.

Last edited by olego; 11-03-2010 at 08:38 AM.
 
Old 11-03-2010, 08:01 PM   #7
tron_thomas
Member
 
Registered: May 2004
Posts: 217

Original Poster
Rep: Reputation: 30
I believe I did update glibc
I don't follow what you are saying in your P.S. olego

What are you trying to say?
 
Old 11-04-2010, 06:34 AM   #8
olego
Member
 
Registered: Sep 2008
Location: Kaliningrad, Russia
Distribution: Slackware
Posts: 35

Rep: Reputation: 1
Quote:
Originally Posted by tron_thomas View Post
I believe I did update glibc
I don't follow what you are saying in your P.S. olego

What are you trying to say?
Apologies for my ugly english. I tried to say that instead of making './configure && make && make install' you'd better use native packaging system and create package for your distro. For example 'chrpath-0.13.rpm'. That I did mean.

But close to the point of topic - was suggested solution helpful to you? On my workstations I use it with success. I found it on one of ubuntu forums, but I lost the link and can't give the reference to the original post.
 
Old 11-04-2010, 06:39 AM   #9
mmidgett
LQ Newbie
 
Registered: Aug 2007
Posts: 4

Rep: Reputation: 0
You also need to make sure you have your kernel sources installed
 
Old 11-04-2010, 08:47 AM   #10
olego
Member
 
Registered: Sep 2008
Location: Kaliningrad, Russia
Distribution: Slackware
Posts: 35

Rep: Reputation: 1
Quote:
Originally Posted by mmidgett View Post
You also need to make sure you have your kernel sources installed
Topic starter said that he removed and installed vbox after kernel/glibc upgrade. So I suppose that he has kernel headers installed. The main reason for error message "VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: VBoxVMM.so: cannot open shared object file: No such file or directory" is glibc 2.12.

This info I've found on the glibc changelog
Quote:
Patched "dynamic linker expands $ORIGIN in setuid library search path".
This security issue allows a local attacker to gain root if they can create
a hard link to a setuid root binary.
So, I suggested a solution:

Quote:
cd /tmp
wget http://www.tux.org/pub/x/ftp.hungry....th-0.13.tar.gz
tar -zxvf chrpath-0.13.tar.gz
cd chrpath-0.13
./configure && make
cd /opt
ln -s /usr/lib/virtualbox V
cd V/
/tmp/chrpath-0.13/chrpath -r /opt/V *.so
It works for me and for other people. But instead of 'make install' chrpath into the system, I suggested to create the valid package. I can provide the Slackbuild script for Slackware-based systems but I'm not familiar with Redhat and Debian based systems and couldn't help with packaging.

I corrected paths, because the standard installation path is '/opt', but topicstarter has '/usr/lib/virtualbox'.

Last edited by olego; 11-04-2010 at 08:51 AM.
 
Old 11-04-2010, 08:02 PM   #11
tron_thomas
Member
 
Registered: May 2004
Posts: 217

Original Poster
Rep: Reputation: 30
Okay I think I follow what you are saying. Fedora uses YUM (Yellowdog Updater, Modified) for package management. I use a graphical program called YUMEX, and I was able to install the chrpath package.

I'm not sure why you are suggest to create a symbolic to virtualbox in the /opt directory. What is the reason for doing this?
Why wouldn't someone just run the chrpath command where virtualbox is installed already?
 
Old 11-05-2010, 07:05 AM   #12
olego
Member
 
Registered: Sep 2008
Location: Kaliningrad, Russia
Distribution: Slackware
Posts: 35

Rep: Reputation: 1
Quote:
Originally Posted by tron_thomas View Post
I'm not sure why you are suggest to create a symbolic to virtualbox in the /opt directory. What is the reason for doing this?
Why wouldn't someone just run the chrpath command where virtualbox is installed already?
/usr/lib/virtualbox/VirtualBox is a SUID root executable.
It wants to dlopen VirtualBox.so.
VirtualBox.so depends on finding VBoxVMM.so in the same directory. It has
RPATH: [$ORIGIN].

This possible vulnerability was corrected in the recent glibc. Because of the RPATH value is pretty short, we can't change it to "/usr/lib/virtualbox/", so we should change it to a short path. '/opt/V' is not worse than any other short path.

BTW I suggest you to search through FC repos, may be you'll find there new version of VirtualBox. As I heard FC14 has corrected VBox in its repo which supports glibc 2.12.

And sorry again for my English. It's not my mother language.

Last edited by olego; 11-05-2010 at 07:10 AM.
 
Old 11-09-2010, 11:42 AM   #13
tron_thomas
Member
 
Registered: May 2004
Posts: 217

Original Poster
Rep: Reputation: 30
I update my system every week, which is most likely how I ended up with the version of glibc that broke VirtualBox.

I update this last weekend and no changes to VirtualBox were available.

I don't understand the issue with short path lengths and RPATH. What is the reason the paths need to be short?
 
Old 11-09-2010, 03:42 PM   #14
John VV
Guru
 
Registered: Aug 2005
Posts: 12,108

Rep: Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591Reputation: 1591
tron_thomas
i would start testing fedora 14 on that vm system
fedora 12 hits END of LIFE in about 2 weeks
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
VirtualBox , after Fedora 12 update tor.ment0r Linux - Virtualization and Cloud 2 02-03-2010 09:35 AM
Fedora 9 Update System Issue, Can anyone help? CoppeRaven Fedora 4 10-05-2008 07:45 PM
After Fedora Update System will not start carlos_duran Linux - Newbie 2 09-01-2008 02:38 PM
Fedora 9 Update System Issue captainxark Fedora 9 08-09-2008 09:57 PM
Update overdose? No executable run, system dead. b0uncer Zenwalk 6 12-01-2006 02:35 PM


All times are GMT -5. The time now is 02:13 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration