when trying to start VBox 6.1 from Virtualisation repo. Thank you for the links, but two of them are about istalling guest additions (I can’t get to that, because I do not have kernel modules compiled on my host). And the first link relates to some person compiling their kernel without some parameter, that VBox needs. I don’t compile my kernel, I’ve installed it from stable repo.
??
The Virtualbox from the openSUSE repos include kernel modules that are closely matched with the available kernel from that same repo… You can’t use those Virtualbox packages with an arbitrary kernel of your choice.
If you want to use a kernel that’s not from the default repo for your specific version of openSUSE (in other words, you also shouldn’t be using virtualbox packages from 15.2 if you’re running 15.1. If it works, you’re just lucky)
Remove all the openSUSE Virtualbox packages.
Although the Virtualbox documentation says that a new install will always over-write an existing without problems, using the openSUSE packages is likely a scenario not accounted for by the documentation.
Download and install the latest Virtualbox version from the Oracle Virtualbox website. Virtualbox doesn’t keep up with openSUSE versions, install the package for “openSUSE 15.0” https://www.virtualbox.org/wiki/Linux_Downloads
Install pre-requisites for building kernel headers. You can run the following command in an elevated kernel or install the individual packages in YaST Software Manager
I recommend simply “su” and not “su -” in this case because you do <not> want to relogin with a full root environment, it’ll just create complications without any added benefit.
zypper in kernel-devel kernel-default-devel gcc make
Execute the downloaded Oracle Virtualbox package. If you still have your elevated console open, you can run the following after you “change directory” to the directory you’re in. If you are in a “su” console as I recommended, you can simply run the following command which should work without needing to “cd” to the correct directory. The following also assumes you downloaded the Virtualbox file to your logged in ordinary User’s Downloads directory which is default in most DE (modify if needed) and only the one file exists which has a names starting with “VirtualBox”
If you need to specify the exact VirtualBox file, you can remove the trailing asterisk and use the TAB key to autocomplete and select the file.
zypper in ~/Downloads/VirtualBox*
While the file is running, watch for successes and errors that are reported in your console.
When completed, go ahead and try to launch!
At he end I ended up with a frankenstein, but that will have to do.
I have installed VirtualBox from RPM downloaded from VirtualBox website. But It wouldn’t build kernel modules (on a separate note VirtualBox 6.1 from Virtualisation repo files with segmentation fault.).
So then I’ve installed virtualbox-kmp-default from stable kernel repo and now could build kernel modules
If it wouldn’t build, the actual error is important to understand the reason(If your install log file still exists, it may contain that info),
I can only speculate it might have been related to being unable to overwrite a file… I’ve never experienced or heard of a fail due to code, but there is always a first time… But that would more likely happen on TW with its bleeding edge kernels than on a LEAP.
Resolution usually requires purging all Virtualbox files if uninstalling isn’t sufficient.
I’ve described the process a few times in other threads in this Virtualization and the Application forums.
Then, with a truly clean system there is usually no problem installing.
Well…, since this is my work machine and at the moment I need Virtual Box to run MS Office only - I think I’ll stick with what works at the moment. Leap 15.2 should be released in a couple of month and hopefully this will fix all my issues out of he box.
The standard Oracle VirtualBox version 6.0.12 from the standard Leap 15.1 repositories, with the standard default Leap 15.1 Linux Kernel, happily runs the newest Windows 10, without any annoying behaviour – apart from a slow boot.
What’s so special about MS Office that, it needs a special VirtualBox driver?
No, Office does not need a special driver. I need to use “non default” kernel, because I need WiFi drivers that are only available in kernel 5.2 (or 5.4) and above. Because of that - I cannot build kernel modules for Virtual Box 6.0.12
As I’ve posted in a couple other places before now,
kernel 5.6 is a special release because of the flood of new features and capabilities and performance gains.
openSUSE maintainers really, really need to publish official guidance how everyone running any currently supported versions of openSUSE on all platforms can install kernel 5.6.
Awhile back Kernel:Portal was a lot more extensive than it is today… It pointed to support articles, repositories for alternate kernels in various stages of development… But today contains hardly any information other than to explain what the openSUSE kernel is.
Yes,
And that may be the “better” way to install… the RPM is something new, but the .run file is the long time way to install Virtualbox.
Running the file usually doesn’t require the “sh” command, just execute the file…
Current Virtualbox documentation also fully documents this file which is actually a master script that calls several sub-scripts and if one ever has a problem the Virtualbox documentation walks you through running the subscripts individually to identify the problem.
If the file (which is a POSIX sh script) is executable (which is not) then yes you don’t need to add sh to run it, otherwise you will just get an error permission denied.
