[Leap 15.4] Virtualbox vboxconfig file missing
I'm using openSUSE Leap 15.4 Beta I have installed Virtualbox, added myself to the vboxusers group, and can start Virtualbox. It sees my VMs, but won't start them, telling me to run # /sbin/vboxconfig first. But this command is not found, and I can confirm that there is not a file called vboxconfig in /sbin Any suggestions, please? Bob -- Bob Williams
My answer to this and other security issues with vbox in suse is to use/install from the vBox project repositories. Additional benefit is that with the Oracle vBox additions USB works. If you want to go by that route: sudo zypper addrepo http://download.virtualbox.org/virtualbox/rpm/opensuse/15.0/ x86_64/ virtualbox sudo zypper refesh sudo zypper remove virtualbox sudo zypper install VirtualBox-6.1 If you need vBox additions: 1. download the additions from: https://download.virtualbox.org/virtualbox/*/*.vbox-extpack 2. become root by: su (will not work with sudo) 3. as root install the additions: virtualbox ......vbox-extpack 4. exit from su 5. run virtualbox ans normal user This setup rebuilds vBox kernel module(s) when you run zypper update automagically. I rarely have issues with it. Users needs to be members of vboxusers group as you have already discovered Note: Updates to minor versions such as current 6.1.32 works as expected with zypper update. When there are new 6.2, 6.3, .... 7.x major versions. You might want to uninstall VirtualBox-6.1 and install whatever the newer version is All that said - if not for legacy VMs, KVM + qemu is better choice for new VMs. KVM is faster, maintained, part of Linux kernel, better in many ways, IMHO. Most importantly, it is properly GNU licensed and true open source, free (as in freedom) project. Best luck, Tomas On Fri, 2022-04-01 at 15:24 +0000, Bob Williams wrote:
I'm using openSUSE Leap 15.4 Beta
I have installed Virtualbox, added myself to the vboxusers group, and can start Virtualbox. It sees my VMs, but won't start them, telling me to run # /sbin/vboxconfig first. But this command is not found, and I can confirm that there is not a file called vboxconfig in /sbin
Any suggestions, please?
Bob
-- Bob Williams
On Fri, 01 Apr 2022 11:58:18 -0400 TomasK wrote:
My answer to this and other security issues with vbox in suse is to use/install from the vBox project repositories. Additional benefit is that with the Oracle vBox additions USB works.
If you want to go by that route: sudo zypper addrepo http://download.virtualbox.org/virtualbox/rpm/opensuse/15.0/ x86_64/ virtualbox sudo zypper refesh sudo zypper remove virtualbox sudo zypper install VirtualBox-6.1
If you need vBox additions: 1. download the additions from: https://download.virtualbox.org/virtualbox/*/*.vbox-extpack 2. become root by: su (will not work with sudo) 3. as root install the additions: virtualbox ......vbox-extpack 4. exit from su 5. run virtualbox ans normal user This setup rebuilds vBox kernel module(s) when you run zypper update automagically. I rarely have issues with it. Users needs to be members of vboxusers group as you have already discovered
Note: Updates to minor versions such as current 6.1.32 works as expected with zypper update. When there are new 6.2, 6.3, .... 7.x major versions. You might want to uninstall VirtualBox-6.1 and install whatever the newer version is
All that said - if not for legacy VMs, KVM + qemu is better choice for new VMs. KVM is faster, maintained, part of Linux kernel, better in many ways, IMHO. Most importantly, it is properly GNU licensed and true open source, free (as in freedom) project.
Best luck, Tomas
On Fri, 2022-04-01 at 15:24 +0000, Bob Williams wrote:
I'm using openSUSE Leap 15.4 Beta
I have installed Virtualbox, added myself to the vboxusers group, and can start Virtualbox. It sees my VMs, but won't start them, telling me to run # /sbin/vboxconfig first. But this command is not found, and I can confirm that there is not a file called vboxconfig in /sbin
Any suggestions, please?
Bob
-- Bob Williams
Tomas, Thank you for this very detailed and helpful reply. As a start I have installed the KVM pattern; now looking to see how to use it. If I don't get on with it, I shall follow your suggestion of reinstalling Virtualbox from the virtualbox repository. Kind regards Bob -- Bob Williams
participants (2)
-
Bob Williams
-
TomasK