| View previous topic :: View next topic |
| Author |
Message |
cz0
Apprentice
Joined: 13 Jun 2005
Posts: 280
Location: /earth/russia/moscow
|
 Posted: Wed Oct 07, 2020 10:13 pm Post subject: |
 |
|
| Lori wrote: | | cz0 wrote: | | So, as far as I can see, no source version is working, neither binary.. |
Well, one person on this thread reported a working stable source version (6.0.x), another one a working testing source version (6.1.x). Have you already tried building from source? |
Well, not yet. If I try to update from working 5.2.40 and fail, I will not be able to roll back to any working version as there is no virtualbox-bin anymore. That's what keeping me from trying to build it from sources. In addition to my phobia for any extra dependency packages I got from using Gentoo for 15+ years. |
|
| Back to top |
|
 |
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Thu Oct 08, 2020 12:05 am Post subject: |
|
|
Go from -bin 5.4.0 to source 5.4.0 then keep following the releases forward. Run the iso each time to update the drivers.
Personally I'm unclear if you tried to make a big leap from 5.x bin package to 6.x source in one jump or if you are still on the bin package going from 5 to 6. |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
|
| Back to top |
|
|
mundi
n00b
Joined: 27 Jun 2003
Posts: 60
|
| Posted: Sat Nov 28, 2020 8:00 am Post subject: |
|
|
Hi,
I might have found the solution to our problem, As I commented on the bug (thanks for filing it, btw.):
| Quote: | I solved the issue on the one of my machines that had this problem.
It was a problem with the ownership of the directories where the VirtualBox binaries reside.
The have to belong to root:root
I fixed this with:
# chown root:root /usr
# chown root:root /usr/lib64
# chown root:root /usr/lib64/virtualbox
The binary version used to install in /opt/VirtualBox/ and therefore I did not notice the problem. According to https://www.virtualbox.org/ticket/16759 the parent folders of the virtualbox binaries have to belong to root:root since 5.1.20
Maybe this could be checked by the ebuild? |
Just posting this also here as most people don't search the bugs. |
|
| Back to top |
|
|
Lori
Guru
Joined: 30 Mar 2004
Posts: 338
Location: Barcelona, Spain
|
| Posted: Mon Nov 30, 2020 7:54 pm Post subject: |
|
|
Thanks a lot mundi! As I replied on the bug, I can confirm that the /usr directory permissions were wrong in my case as well, and changing them to root did fix the issue. How did you came across that ticket?
_________________
"The hunt is sweeter then the kill."
Registered Linux User #176911 |
|
| Back to top |
|
|
mundi
n00b
Joined: 27 Jun 2003
Posts: 60
|
| Posted: Mon Nov 30, 2020 10:41 pm Post subject: |
|
|
| Lori wrote: | | Thanks a lot mundi! As I replied on the bug, I can confirm that the /usr directory permissions were wrong in my case as well, and changing them to root did fix the issue. How did you came across that ticket? |
Well,
I ran VBoxHeadless instead of the virtualbox and it gave me:
| Code: | VBoxHeadless: Error -610 in supR3HardenedMainInitRuntime!
VBoxHeadless: dlopen("/usr/lib64/virtualbox/VBoxRT.so",) failed: <NULL> |
Which I found super strange because /usr/lib64/virtualbox/VBoxRT.so existed of course.
So I ran strace VBoxHeadless which gave me https://pastebin.com/zTw3mh3N
I still did not understand that immediately but it gave me the clue that it checks user and group ids and this and some searching the internet for the string "VirtualBox: dlopen("/usr/lib/virtualbox/VBoxRT.so",) failed: <NULL> owner" brings this ticket as the first search result.
So as usual: In the quest of searching for more output, as the VirtualBox log messages are really not helpful even if you compile it with debug flags I tried strace. And the rest was lucky. |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Mon Nov 30, 2020 10:48 pm Post subject: |
|
|
If it's any help:
| Code: | ~ $ ls -l /usr/lib64/virtualbox/VBoxRT.so
-rwxr-x--- 1 root vboxusers 3526520 Oct 20 22:03 /usr/lib64/virtualbox/VBoxRT.so
tony@MSI ~ $ stat /usr/lib64/virtualbox/VBoxRT.so
File: /usr/lib64/virtualbox/VBoxRT.so
Size: 3526520 Blocks: 6888 IO Block: 4096 regular file
Device: 802h/2050d Inode: 23593117 Links: 1
Access: (0750/-rwxr-x---) Uid: ( 0/ root) Gid: ( 304/vboxusers)
Access: 2020-11-27 21:33:05.361644224 -0600
Modify: 2020-10-20 22:03:30.767378563 -0500
Change: 2020-10-20 22:03:57.227378495 -0500
Birth: 2020-10-20 22:03:57.217378495 -0500
|
|
|
| Back to top |
|
|
mundi
n00b
Joined: 27 Jun 2003
Posts: 60
|
| Posted: Mon Nov 30, 2020 10:59 pm Post subject: |
|
|
| Tony0945 wrote: | If it's any help:
| Code: | ~ $ ls -l /usr/lib64/virtualbox/VBoxRT.so
-rwxr-x--- 1 root vboxusers 3526520 Oct 20 22:03 /usr/lib64/virtualbox/VBoxRT.so
|
|
the issue was not the owner of the file but the owner of my /usr directory. It was owned by root:102
| Code: | | drwxrwxr-x 32 root 102 4096 Apr 13 2020 usr |
I don't even have a group 102 so I have no idea how that happend.
But the gentoo installation on this system is really old (initial install release was 1.4) so a lot of stupid stuff might have happened.
The complete path /usr, /usr/lib64, /usr/lib64/virtualbox has to belong to root:root |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Tue Dec 01, 2020 1:46 am Post subject: |
|
|
| Mine's old too. I don't know the initial release number but I cleared out some ancient files from 2004 the other day. It had data for applications that must be gone for ten years now. |
|
| Back to top |
|
|
SoofMan
n00b
Joined: 05 Dec 2008
Posts: 69
|
| Posted: Sat Jan 01, 2022 10:01 pm Post subject: |
|
|
| mundi wrote: |
Hi,
I might have found the solution to our problem, As I commented on the bug (thanks for filing it, btw.):
| Quote: | I solved the issue on the one of my machines that had this problem.
It was a problem with the ownership of the directories where the VirtualBox binaries reside.
The have to belong to root:root
I fixed this with:
# chown root:root /usr
# chown root:root /usr/lib64
# chown root:root /usr/lib64/virtualbox
The binary version used to install in /opt/VirtualBox/ and therefore I did not notice the problem. According to https://www.virtualbox.org/ticket/16759 the parent folders of the virtualbox binaries have to belong to root:root since 5.1.20
Maybe this could be checked by the ebuild? |
Just posting this also here as most people don't search the bugs. |
Holy sh***, this actually solved my problem! All my VMs are working right now!
Many thanks!
Have a tip in Bitcoin Cash (check PM)! |
|
| Back to top |
|
|
|
Desktop Environments
