Recently I had to fix my Leap 15.0 because I had accidentally installed some tumbleweed repos (via a one click install). I successfully got things up and running by using a bootable USB and running and upgrade. Everything is working great except the Virtualbox. Here is what I remember about the chain of events:
When I tried to run it at first, it suggested I run /sbin/vboxconfig. That produced an error message something like host “kernel driver” not installed. I figured the software got erased with my OS fix and so I went to YAST and downloaded virtualbox there. But then I realized it was a different version than I had previously installed. It was 5.2, but I had 5.2.18.
I deleted that and found a tutorial for downloading on Opensuse using the CL. At that point I downloaded the 5.2.18 version successfully. But when I went to install it, there was an error:
setting /usr/lib/virtualbox/VBoxNetNAT to root:vboxusers 4750. (wrong permissions 0755)
setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong permissions 0750)
Then I rebooted the computer, hoping that it just needed that, but the problem is still there. Now I get this error:
The desktop entry file
file:///root/.local/share/plasma_icons/virtualbox.desktop
is not valid.
I’m hoping to fix this without erasing the whole VM, if possible. But whatever it takes, I’m game for it.
Am guessing your installed Virtualbox kernel modules are still the ones built for your Tumbleweed kernel.
Should be fixable by re-installing however you installed before…
If you installed from the OSS, then you should execute a “force install” to force a downgrade, ie
zypper in -f virtualbox
If you’re instead installing by downloading from the Oracle Virtualbox site,
Then I assume that simply re-running the install should fix your problem, again if you are prompted to downgrade, then do so… do not keep anything from before.
If you have problems, post again with as much detail as possible about any error that displays or the installation log file.
I don’t remember how I installed the original VM, that was over a year ago. But with this recent problem, I installed (and then later deleted) it all through Yast. But that didn’t fix it. I was suspicious that the 5.2.24 package it chooses was not compatible with the 5.2.18 version that is originally on the computer. So that is why I deleted it, and then installed the 5.2.18 via the konsole. But that was not successful, because of the permissions problem ( I posted the code in the first post).
Ok. So I just ran the command you suggested and it installed the 5.2.24 package, with some problems. Here is the info:
3 new packages to install.
Overall download size: 20.0 MiB. Already cached: 0 B. After the operation, additional 65.1 MiB will be used.
Continue? [y/n/...? shows all options] (y): y
Retrieving package virtualbox-host-kmp-default-5.2.24_k4.12.14_lp150.12.61-lp150.4.33.1.x86_64
(1/3), 305.4 KiB (816.3 KiB unpacked)
Retrieving: virtualbox-host-kmp-default-5.2.24_k4.12.14_lp150.12.61-lp150.4.33.1.x86_64.rpm ........[done (11.8 KiB/s)]
Retrieving package virtualbox-5.2.24-lp150.4.33.1.x86_64 (2/3), 11.7 MiB ( 35.8 MiB unpacked)
Retrieving: virtualbox-5.2.24-lp150.4.33.1.x86_64.rpm ...............................................[done (3.3 MiB/s)]
Retrieving package virtualbox-qt-5.2.24-lp150.4.33.1.x86_64 (3/3), 8.0 MiB ( 28.6 MiB unpacked)
Retrieving: virtualbox-qt-5.2.24-lp150.4.33.1.x86_64.rpm ............................................[done (3.3 MiB/s)]
Checking for file conflicts: ....................................................................................[done]
(1/3) Installing: virtualbox-host-kmp-default-5.2.24_k4.12.14_lp150.12.61-lp150.4.33.1.x86_64 ...................[done]
(2/3) Installing: virtualbox-5.2.24-lp150.4.33.1.x86_64 .........................................................[done]
Additional rpm output:
setting /usr/lib/virtualbox/VBoxNetNAT to root:vboxusers 4750. (wrong permissions 0755)
setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong permissions 0750)
(3/3) Installing: virtualbox-qt-5.2.24-lp150.4.33.1.x86_64 ......................................................[done]
Additional rpm output:
setting /usr/lib/virtualbox/VirtualBox to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxSDL to root:vboxusers 4750. (wrong permissions 0750)
When I attempt to start virtualbox, here is the error message:
The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing
'/sbin/vboxconfig'
as root.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
First
Ha e you tried to run “/etc/vboxconfig” as described?
If that doesn’t work, then uninstall virtualbox with the following command
jzypper rm "virtualbox*"
Then you should verify the results, I recommend using the “locate” command instead of the “find” command because locate is blindingly fast so is worth the extra time to install. If you want to use the locate utility you have to install it which is part of the mlocate package
zypper in mlocate
by default the locate database updates its database of files in your system every 24 hrs, but we don’t want to wait until tomorrow to run it so update the database immediately with the following command in an elevated console
updatedb
Now you can “locate” any files on your system, and if you want to look for files in a specific place(we won’t do that here because we want to find files anywhere on your system), just include the path in your search, eg
locate virtualbox
locate vbox
Since you’re trying to cpurge your system of all old virtualbox files so you can re-install virtualbox completely clean, you can delete practically anything you find assuming you hadn’t modified your old virtualbox radically in some strange way which you’d want to preserve. The only exception might be if you named your Guest VM with virtualbox or vbox in its name… IMO most people wouldn’t do that, but take a moment to think about that before you start deleting files manually.
Remove all the files you found using the “locate” command (or any other command you might have used like find) by command line
rm* file_name*
If you wish, you can “update the locate database” again and re-run locate to verify the files are removed,
Then re-install virtualbox using YaST or zypper.
Ok. Here is an update. I followed all the steps you suggested, except did not remove all the virtualbox files. I’m guessing that will remove the entire prior system. Is that true? If so, are there any other ideas before doing that. I install a Windows 10 and they always give me trouble when I try to validate it.
Anyways, if I have to start from scratch, that’s fine. But I felt it was good for you to have a look at the list of files and make sure they all should get deleted. Here is the results of that last work:
The point is to first remove as much of the virtualbox application as possible using the package manage, ie by using zypper or YaST.
Then, inspect what remains using locate.
Whatever you still see in your system using locate should be mostly User configuration settings, but there might be more that is preventing a truly complete removal so that a new install won’t use anything from your failed TW experience.
From what you posted,
You listed a number of files which should have been removed by package uninstall, which is minimally helpful…Because all you’re listing is what you’d expect in a full install.
The list of files I posted was what remained after removing the virtualbox application using zypper. When I search through YaST it doesn’t show and vbox applications installed either. So apparently the uninstall procedure left a lot of files on the computer.
Are you suggesting I manually erase all? If so, no problem. Since there are so many files, would it be more efficient to just navigate to those folders and delete them? As opposed to doing it one file at a time in konsole.
Also, I want to make sure I understand the consequences of this. I will completely lose my old Windows 10 OS that I had there. True?
Yes, remove the folder (recursively to include contents).
Will not affect your Virtualbox guests,
The critical infomration about each Guest is in the folder containing he disk file, plus the Guest configuration file and misc other files.
I’m a little nervous about deleting all of those files. Let me check before doing so. For example, do I want to keep any that say “guest” anywhere? Like these:
Delete the above files.
In particular, the file ending in “.ko” is likely the one giving you the most problems.
Do not delete the files below, those are related to your Guests
Although it probably won’t make much difference, delete those files related to the extension pack, they will be re-installed when VBox is re-installed.
I removed the suggested files. Then installed Vbox 5.2 via YaST and restarted. I received the error this error:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing
'/sbin/vboxconfig'
as root.
If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
I ran the sbin command and got this:
linux-vqod:~ # /sbin/vboxconfig
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-default-devel kernel-default-devel-5.1.7-1
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-default-devel kernel-default-devel-5.1.7-1
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
I then attempted to install the headers after reading a tutorial. It suggested I go into YaST, then Software Management, then click on Patterns and select Base Development, C/C++ and Linux Kernel Development. Then a restart, but the same error messages are given both by Vbox and in the Konsole when I retry the sbin command.
I started to look into the EFI secure boot suggestion. Could this be the fix? What do you think?
The kernel development pattern won’t build kernel modules (which are kernel add-ons), it’s for building the core parts of the kernel (eg initramfs).
The required packages for building kernel modules in general can be installed with the following command (assuming you’re running the default kernel)
zypper in gcc make kernel-devel kernel-default-devel
After that, you should be able to successfully install.
Bad news. The problem is still there. I ran the code and it did find another package to install. But when I attempt to start up the Vbox, I get the same error message. I ran the sbin command again, but get the same error message.
linux-vqod:~ # /sbin/vboxconfig
Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-default-devel kernel-default-devel-5.1.7-1
This system is currently not set up to build kernel modules.
Please install the Linux kernel "header" files matching the current kernel
for adding new hardware support to the system.
The distribution packages containing the headers are probably:
kernel-default-devel kernel-default-devel-5.1.7-1
There were problems setting up VirtualBox. To re-start the set-up process, run
/sbin/vboxconfig
as root. If your system is using EFI Secure Boot you may need to sign the
kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
them. Please see your Linux system's documentation for more information.
I checked and do have EFI secure boot enabled.
Do you have any other ideas?
By the thanks for being patient with me. I’m looking forward to announce a success soon :).
The most common ;cause for failure even after adding the appropriate kernel headers and and compiler is that your kernel and kernel-devel packages are out of sync. This often happens when for instance you’re currently adding packages not all at once, and it’s always good practice to update your system prior to installing new packages.
Update your system with the following which should re-sync package versions (all latest) and try installing Virtualbox again
The current Leap 15.0 Oracle VirtualBox version is 5.2.24
[quote=“rgietzen”]
setting /usr/lib/virtualbox/VBoxNetNAT to root:vboxusers 4750. (wrong permissions 0755)
setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong permissions 0750)
This ain’t an error.
It’s information that the openSUSE package sets the permissions to something other than what Oracle believes they should be.
You’re running the VirtualBox VMs from the user “root”?? !!!
[HR][/HR]Please be aware that, there’s a magic Oracle VirtualBox CLI tool: “VBoxManage”
Please post the following Terminal outputs:
“VBoxManage list extpacks
” - “VBoxManage list --long vms
”
Examples are as follows (my VirtualBox VMs run from a “normal” user – not “root” … ):
> VBoxManage list extpacks
Extension Packs: 1
Pack no. 0: Oracle VM VirtualBox Extension Pack
Version: 5.2.24
Revision: 128163
Edition:
Description: USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
VRDE Module: VBoxVRDP
Usable: true
Why unusable:
>
> VBoxManage list --long vms
Name: XXX
Groups: /
Guest OS: Windows 10 (64-bit)
UUID: 18dd02ad-3ede-4c7a-bb61-427cde005a3f
Config file: /homeXX/User-VMs/XXX/XXX/XXX.vbox
Snapshot folder: /homeXX/User-VMs/XXX/XXX/Snapshots
Log folder: /homeXX/User-VMs/XXX/XXX/Logs
Hardware UUID: 18dd02ad-3ede-4c7a-bb61-427cde005a3f
Memory size: 5120MB
Page Fusion: off
VRAM size: 256MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 4
PAE: on
Long Mode: on
Triple Fault Reset: off
APIC: on
X2APIC: off
.
.
.
.
USB Device Filters:
<none>
Bandwidth groups: <none>
Shared folders:
Name: 'tmp', Host path: '/homeXX/User-VMs/XXX/tmp' (machine mapping), writable
Name: 'WindowsSicherungen', Host path: '/homeXX/User-VMs/XXX/WindowsSicherungen' (machine mapping), writable
Capturing: not active
Capture audio: not active
Capture screens: 0
Capture file: /homeXX/User-VMs/XXX/XXX/XXX.webm
Capture dimensions: 1024x768
Capture rate: 512 kbps
Capture FPS: 25
Capture options: ac_enabled=false
Description:
Windows 10.
Sigma PhotoPro.
Silkypix (Pentax).
Guest:
Configured memory balloon size: 0 MB
>
[HR][/HR]As an aside, please be aware that, when you upgrade from Leap 15.0 to Leap 15.1, you may, possibly, experience some pain with the VirtualBox upgrade from V5 to V6:
The upgrade doesn’t handle the VirtualBox Extension Pack upgrade in a pleasant fashion.
One has to use the VirtualBox CLI Manager (VBoxManage) to remove the 5.22 or 5.24 Extension Pack and then install the correct V6 Extension Pack …
[quote="“dcurtisfra,post:17,topic:136777”]
The current Leap 15.0 Oracle VirtualBox version is 5.2.24
Thanks for offering to help. Yes, I use root as my user desktop. I am aware of the all the warnings and accept responsibility.
Here are the outputs:
VBoxManage list extpacks
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.1.7-1-default) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.
Extension Packs: 0
linux-vqod:~ # VBoxManage list --long vms
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.1.7-1-default) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.
Name: Windows 10
Groups: /
Guest OS: Windows 10 (64-bit)
UUID: bb24902d-cefe-4211-83ea-71f4abc72108
Config file: /home/VirtualBox VMs/Windows 10/Windows 10.vbox
Snapshot folder: /home/VirtualBox VMs/Windows 10/Snapshots
Log folder: /home/VirtualBox VMs/Windows 10/Logs
Hardware UUID: bb24902d-cefe-4211-83ea-71f4abc72108
Memory size: 4423MB
Page Fusion: off
VRAM size: 128MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
PAE: off
Long Mode: on
Triple Fault Reset: off
APIC: on
X2APIC: off
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: on
BIOS APIC mode: APIC
Time offset: 0ms
RTC: local time
Hardw. virt.ext: on
Nested Paging: on
Large Pages: off
VT-x VPID: on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: HyperV
State: powered off (since 2019-06-07T00:01:57.000000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0): SATA
Storage Controller Type (0): IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 30
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
SATA (0, 0): /home/VirtualBox VMs/Windows 10/Windows 10.vdi (UUID: ad6e0c5b-8131-46fa-bcf1-31f016fe2036)
SATA (1, 0): /root/.config/VirtualBox/VBoxGuestAdditions_5.2.18.iso (UUID: a6487b11-36ca-4193-b286-60434bdfb618)
NIC 1: MAC: 0800274BF083, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
UART 3: disabled
UART 4: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: ALSA, Controller: HDA, Codec: STAC9221)
Audio playback: disabled
Audio capture: enabled
Clipboard Mode: HostToGuest
Drag and drop Mode: disabled
VRDE: disabled
USB: disabled
EHCI: disabled
XHCI: enabled
USB Device Filters:
<none>
Bandwidth groups: <none>
Shared folders:
Name: 'VM_Shared_Folder', Host path: '/home/Documents/VM Shared Folder' (machine mapping), writable
Capturing: not active
Capture audio: not active
Capture screens: 0
Capture file: /home/VirtualBox VMs/Windows 10/Windows 10.webm
Capture dimensions: 1024x768
Capture rate: 512 kbps
Capture FPS: 25
Capture options: ac_enabled=false
Guest:
Configured memory balloon size: 0 MB