View previous topic :: View next topic |
Author |
Message |
ndbg2 n00b
Joined: 13 Apr 2010 Posts: 20 Location: Germany
|
Posted: Mon Nov 08, 2010 11:36 am Post subject: [SOLVED] Virtualbox-bin does not start after -uDN world |
|
|
Hi everybody,
again I experienced some curious behaviour of virtualbox-bin-3.1.8.
A couple of days I was working with vbox-3.1.8 and a WinXP Guest. While it was running I installed some packages like
nvidia-settings
nvidia-drivers
x86info.
I did an emerge -uDN world as well. A day later, after a shutdown, I tried to start it again by clicking on the icon. Vbox seems to start at first, but the initial window, where you choose your guest-systems doesn´t even show up.
I have really no idea where to look at.
What I did so far:
reemerged all vbox related packages (bin, modules, additions, input, video) --> same problem.
unmerged nvidia-* and x86info. --> same problem.
So it actually must have something to do with the full update. But I really cannot remember, what packes have been updatet....
Any ideas?? I would appreciate any hint... _________________ Desktop - AMD FX-6300 - 3.5GHz - 8GB RAM - KDE 5
Last edited by ndbg2 on Tue Nov 09, 2010 9:04 pm; edited 1 time in total |
|
Back to top |
|
|
Ahenobarbi Retired Dev
Joined: 02 Apr 2009 Posts: 345 Location: Warsaw, PL
|
Posted: Mon Nov 08, 2010 1:31 pm Post subject: |
|
|
Did you try revdep-rebuild? |
|
Back to top |
|
|
ndbg2 n00b
Joined: 13 Apr 2010 Posts: 20 Location: Germany
|
Posted: Mon Nov 08, 2010 3:03 pm Post subject: |
|
|
Hi Ahenobarbi,
as far as I remember, I did. But I will do it again this evening.
Is it possible to find out, what packages have been installed shortly? _________________ Desktop - AMD FX-6300 - 3.5GHz - 8GB RAM - KDE 5 |
|
Back to top |
|
|
Section_8 l33t
Joined: 22 May 2004 Posts: 627
|
Posted: Mon Nov 08, 2010 3:53 pm Post subject: |
|
|
Is it possible that your world update emerged a new gentoo-sources with the symlink use flag, and updated the /usr/src/linux symlink? Then, even if you didn't install the new kernel, the re-emerge of virtlualbox-modules built them against the wrong kernel. |
|
Back to top |
|
|
tomtom69 Apprentice
Joined: 09 Nov 2010 Posts: 245 Location: Bavaria
|
Posted: Tue Nov 09, 2010 9:37 am Post subject: Re: Virtualbox-bin does not start after -uDN world |
|
|
Hello,
ndbg2 wrote: |
So it actually must have something to do with the full update. But I really cannot remember, what packes have been updatet....
|
I had the same problem here. It was related to the glibc update that fixed a bug with shared libraries.
Symptom: When you start Virtualbox from the console, you can see that the file VBoxVMM.so can not be found.
What helped was a hack that generates links in the lib64 folder to the virtualbox shared libraries:
# find /opt/virtualbox/ -name \*.so -exec ln -s -t /lib64 '{}' ';'
# find /opt/virtualbox/ -name \*.so.4 -exec ln -s -t /lib64 '{}' ';'
(based on: https://bugzilla.rpmfusion.org/show_bug.cgi?id=1465)
tomtom69 |
|
Back to top |
|
|
ndbg2 n00b
Joined: 13 Apr 2010 Posts: 20 Location: Germany
|
Posted: Tue Nov 09, 2010 9:01 pm Post subject: [SOLVED] Virtualbox-bin does not start after -uDN world |
|
|
PERFECT!!!
Thanks a lot tomtom69. It works again.
The glibc update was it.
Ahenobarbi: revdep-rebuild said that all is consistant
Section_8: The symlink looked allright.
Anyway, it was an option. Thanks a lot. _________________ Desktop - AMD FX-6300 - 3.5GHz - 8GB RAM - KDE 5 |
|
Back to top |
|
|
static_k n00b
Joined: 10 Oct 2005 Posts: 73 Location: NY
|
Posted: Fri Nov 12, 2010 12:35 pm Post subject: Re: Virtualbox-bin does not start after -uDN world |
|
|
tomtom69 wrote: | Hello,
ndbg2 wrote: |
So it actually must have something to do with the full update. But I really cannot remember, what packes have been updatet....
|
I had the same problem here. It was related to the glibc update that fixed a bug with shared libraries.
Symptom: When you start Virtualbox from the console, you can see that the file VBoxVMM.so can not be found.
What helped was a hack that generates links in the lib64 folder to the virtualbox shared libraries:
# find /opt/virtualbox/ -name \*.so -exec ln -s -t /lib64 '{}' ';'
# find /opt/virtualbox/ -name \*.so.4 -exec ln -s -t /lib64 '{}' ';'
(based on: https://bugzilla.rpmfusion.org/show_bug.cgi?id=1465)
tomtom69 |
Thanks tomtom69! That worked for me as well. I had the same issue where VirtualBox would run fine as root but not as user. |
|
Back to top |
|
|
Princess Nell l33t
Joined: 15 Apr 2005 Posts: 916
|
Posted: Sat Nov 13, 2010 11:31 am Post subject: |
|
|
I forgot the reference, but this is fixed in 3.2.10. I unmasked it and it works perfectly well (-r1). |
|
Back to top |
|
|
travonz n00b
Joined: 20 Jan 2005 Posts: 17
|
Posted: Mon Dec 06, 2010 2:30 pm Post subject: |
|
|
Hello,
I also solved this problem by upgrading to the lastest 3.2.10 (not r1) version which work well. |
|
Back to top |
|
|
|