Bugzilla – Bug 1212191
Virtualbox links broken
Last modified: 2023-06-17 16:55:27 UTC
Created attachment 867491 [details] links broken Hello, there are son link broken in /usr/lib/virtualbox, looks like are not created using absolute path, that will be the correct way to create symbolic links.
This is what is supposed to be links and owned by vboxusers the file sizes are correct. LLR1:/usr/lib/virtualbox # ll | egrep "^lr|-rws|vboxusers" -rwsr-x--- 1 root vboxusers 137464 May 22 06:32 VBoxHeadless -rwsr-x--- 1 root vboxusers 31056 May 22 06:32 VBoxNetAdpCtl -rwsr-x--- 1 root vboxusers 137464 May 22 06:32 VBoxNetDHCP -rwsr-x--- 1 root vboxusers 137464 May 22 06:32 VBoxNetNAT -rwxr-xr-x 1 root vboxusers 10488 May 22 06:32 VBoxPermissionMessage -rwxr-xr-x 1 root vboxusers 10480 May 22 06:32 VBoxSUIDMessage -rwxr-xr-x 1 root vboxusers 10480 May 22 06:32 VBoxUSB_DevRules lrwxrwxrwx 1 root root 12 May 22 06:32 VirtualBox -> VirtualBoxVM -rwxr-xr-x 1 root vboxusers 3037680 May 22 06:32 VirtualBox6 -rwsr-x--- 1 root vboxusers 137464 May 22 06:32 VirtualBoxVM LLR1:/usr/lib/virtualbox # These work correctly from Oracle and in Tumbleweed and Leap 15.4 and 15.5. If this is what you have it is correct.
Those links are red because those files are SUID as shown by the rws privileges for the owner. These are normal, just have the same color as a broken link.
ok, thanks I created this because when trying to create a machine using VirtualBox the PC froze and i tough was for this.
At what stage did the PC freeze?
(In reply to Larry Finger from comment #4) > At what stage did the PC freeze? creating the new machine, sometimes pop up the progress bar and stay there, and sometimes when press finish, the pop-up won't show and the pc freeze, have to use REISUB
What does 'hwinfo --cpu' show for any one of your CPUs. If it is an Intel from generation 11+ and you are running kernel 6.3.6 in the host, then you have run into the IBT problem. See https://forums.opensuse.org/t/virtualbox-fails-to-start-on-newest-cpus-with-6-3-6-kernel-how-to-fix-until-oracle-finds-a-fix/166879 for a workaround.
(In reply to Larry Finger from comment #6) > What does 'hwinfo --cpu' show for any one of your CPUs. If it is an Intel > from generation 11+ and you are running kernel 6.3.6 in the host, then you > have run into the IBT problem. See > https://forums.opensuse.org/t/virtualbox-fails-to-start-on-newest-cpus-with- > 6-3-6-kernel-how-to-fix-until-oracle-finds-a-fix/166879 > for a workaround. thanks a lot this solve the issue.
*** This bug has been marked as a duplicate of bug 1212209 ***