I have a machine with Leap 15.6 and a bunch of guests running 7.1 right now
I will be trying to build Tumbleweed and Leap versions tonight.
Linux guest work fine in 7.1 - Windows guests when 7.1 guest additions are install cannot use NAT for networks any more - Bridged works fine.
Will keep you updated - the Oracle virtualization repo has to have the %releasever changed to 15.5 to install it in 15.6 - I have a bugzilla with Oracle for that.
Leap guest that want to use their guest additions need to install kernel-source and kernel-syms for their guest additions to install.
They do not support Tumbleweed or Slowroll hosts or guests.
There are some issues with 7.1.0 - here are the game stoppers:
Windows NAT does not work - only Bridge network
Windows shares folders do not work
Windows mouse does not release - have to use right-ctrl to change windows
No sound on any guests Linux or Windows
Reports of failed save state and re start not working.
I am waiting for fixes before getting 7.1.0 out for openSUSE.
I suspect that we will wait for 7.1.2 to fix these problems
If anyone wants the Tumbleweed/Slowroll rpms for 7.0.1 leave me a PM
I have it working - If you do not install the 7.1.0 guest additions to Windows guests and keep the 7.0.18 or 7.0.20 guests - everything seems to work except for NAT.
Is it normal for new VirtualBox updates to appear late in the openSUSE repo?
It may sound silly but not having the latest VirtualBox is the reason I went back to an Arch based distro yesterday from Tumbleweed. I dual boot Windows and Linux on my system and I need to access VirtualBox from both OS but the older version cannot open VMs that was opened with the new version. I tried downloading the openSUSE’s rpm file from VBox website, but it didn’t work. So, I’m curious to know why Arch repo got it quickly while openSUSE hasn’t yet.
I have slowroll and tumbleweed built with 7.1 - the /usr/share/virtualbox/*.iso has to be delete as it did not build (I needed some windows code) but “Insert Guest Additions” will download the good file from Oracle. This is not signed but built the way Oracle showed me to test on Tumbleweed.
I could not figure out how to build it in OBS which is needed to get it into the openSUSE repositories. The Oracle build is rather simple and takes 20 minutes on a i712700T system with nvme drives.
You can download it from here for the next 7 days.
You can sign it to make it secure - It will add a MOK to the BIOS to allow secure boot
Here is a signing directory to used after you installing the rpm file and before the reboot.
You have to accept the MOK into the BIOS and secure boot will work as expected.
Link to the MOK signing for VirtualBox kernel modules:
Thanks again for sharing this. But honestly, it’s too much trouble for me as I’m relatively new in the Linux world. For the time being I’ll just stick to using the Arch based distro I’m using at the moment and will come back to Tumblweed in the future.
@SeriousHoax As a new user, then I would suggest looking at the default virtual machine tools… qemu/libvirt etc… Then of course there is always distrobox…
@malcolmlewis Thanks for the suggestion. Actually, as I said, I interchange between Windows and Linux on my dual boot system regularly and need to run the same VMs on both OS. So, using the same Virtual Machine app is my preference. Linux distros work very well in Virtual Box in both windows and Linux host while for Windows as a guest os, VMWare is far superior but terrible for Linux guests in my experience.
Oh wait, after writing what I wrote above I decided to search qemu on google before commenting and I see that qemu is available for Windows also? Okay that makes things interesting. I’ll have to check it out.
@malcolmlewis Nice. I’m in the process of checking it out.
Yeah, this kernel module integration is quite an issue as I’m starting to understand. I guess for that reason I can’t expect to install VirtualBox in Arch Distrobox and have it work on Tumbleweed as it requires kernel module integration. Is that correct? (I also use secure boot).
@malcolmlewis I guess you mean Windows as a Guest OS in qemu in your openSUSE system. I was talking about installing qemu on Windows and running VMs on that.
@larryr Hi! I decided to try installing Vbox from your rpm and sign in. I’m testing it in a VM first. I installed the rpm and now want to sign by the mok you provided. I see that you also put a script in it for signing. But how do I use the script? This is what I’m getting when I run it.
“Usage: sign_kmp.sh Path of directory containing modules”
Can you help?
If I remember correctly it is a single line - the script is needed to build a MOK key but there is one included here is how I did it
execute this for easy signing and generate new signature keys (you get a new MOK each time)
./sign_kmp.sh /lib/modules/$(uname -r)/misc/
or do this for no new MOK key (in the same directory as sign_kmp.sh which does this:
I’m on a desktop though…
Let me see how qemu performs on a Windows system.