Bug 318557 – app-emulation/virtualbox-bin - Virtualbox does not start - bin file not found

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Meia Lua 2010-05-05 09:48:08 UTC]

Sucessfully emerged virtualbox-bin and virtualbox-modules but cannot execute any of the virtualbox commands as the binary seems not to be found.
Calling directly the binary with /opt/VirtualBox/VBoxManage produces does not work either.

# VBoxManage 
/opt/bin/VBoxManage: line 87: /opt/VirtualBox/VBoxManage: No such file or directory
/opt/bin/VBoxManage: line 87: /opt/VirtualBox/VBoxManage: Success
# /opt/VirtualBox/VBoxManage 
bash: /opt/VirtualBox/VBoxManage: No such file or directory
# ls -l /opt/VirtualBox/VBoxManage 
-rwxr-x--- 1 root vboxusers 739712 May  5 11:43 /opt/VirtualBox/VBoxManage
# ls -l /opt/bin/VirtualBox 
lrwxrwxrwx 1 root root 23 May  5 11:44 /opt/bin/VirtualBox -> /opt/VirtualBox/VBox.sh
# cat /etc/vbox/vbox.cfg 
INSTALL_DIR=/opt/VirtualBox


Reproducible: Always

Steps to Reproduce:
1. emerge app-emulation/virtualbox-bin-3.0.12 and app-emulation/virtualbox-modules-3.0.12 
2. Set USE flags as follows -headless -vboxwebsrv as mentioned in this thread http://forums.gentoo.org/viewtopic-t-707241.html? 
3. start any VBox** command (e.g. VBoxManage or VBoxHeadless)
/opt/bin/VBoxManage: line 87: /opt/VirtualBox/VBoxManage: No such file or directory
/opt/bin/VBoxManage: line 87: /opt/VirtualBox/VBoxManage: Success



Actual Results:  
# VBoxManage 
/opt/bin/VBoxManage: line 87: /opt/VirtualBox/VBoxManage: No such file or directory
/opt/bin/VBoxManage: line 87: /opt/VirtualBox/VBoxManage: Success


Expected Results:  
VBoxManage should start. Same output when using other VBox** commands like VBoxHeadless or even VBoxManage createvm --name "test" --register

[Comment 1 Meia Lua 2010-05-05 09:52:26 UTC]

Created attachment 230409 [details]
emerge info

[Comment 2 Meia Lua 2010-05-05 09:53:14 UTC]

Created attachment 230411 [details]
strace

[Comment 3 Olivier Galibert 2010-05-05 11:24:00 UTC]

Are you in the vboxusers group? According to the strace some processes seem tp be able to see the executable and others not, which may be a (strange) access rights issue.

[Comment 4 Meia Lua 2010-05-05 11:56:15 UTC]

 
Yes I am:
# id **
gid=1013(svnusers) groups=1013(svnusers),10(wheel),18(audio),100(users),1012(kvm),1020(vboxusers)

Thanks for the hint.

[Comment 5 Meia Lua 2010-05-05 11:59:28 UTC]

I'm running hardened sources. Maybe restrictions linked to this or with PaX?
Here's emerge output at the end of the merge: * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxManage
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxSVC
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxXPCOMIPCD
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxTunctl
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxNetAdpCtl
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxNetDHCP
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxTestOGL
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxSDL
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VBoxHeadless
 * PT PaX marking -m
 *      /var/tmp/portage/app-emulation/virtualbox-bin-3.0.12/image//opt/VirtualBox/VirtualBox
 * 
 * To launch VirtualBox just type: "VirtualBox"
I don't know how Pax works and cannot interprete the above message

[Comment 6 Meia Lua 2010-05-05 20:00:56 UTC]

Following the remark of comment 3 I've checked if there are any problems with text relocations
However everything seems fine:
# scanelf -lpqt returns no broken files.

Anyone had the same issue?

[Comment 7 Andrey Stankov 2010-05-14 15:31:32 UTC]

I have the same problem with starting VBox.
I'm try to reemerge with different USE flag with no success. 
All group/file permissions are ok (I've compare it with the working VBox on other server)
Always have the same error.
Does anyone have a solution?

[Comment 8 Lars Wendler (Polynomial-C) (RETIRED) 2010-06-29 11:58:48 UTC]

Any chance you guys mounted /opt with noexec flag?

[Comment 9 Lars Wendler (Polynomial-C) (RETIRED) 2010-10-20 21:59:03 UTC]

No answer in more than three months --> NEEDINFO