1st Add the repo
Start Yast > Repositories > add .> Use URL > copy & paste that link > give it a name > accept > Trust the key & close
Next:
In Yast > Software Management > search for “virtualbox”
select it > it should also select the correct kernel module for you; but, I check in a terminal with "uname -a
in the right smaller window > click Versions > tick the 5.1.10-253-1 set of rpms
I did vbox
vbox- guest icons
vbox-host-kmp-default – this is the kernel module to check; 4.4.27-2-default is where I’m at now
Vbox-qt
Accept
When it is all done, I reboot to load the new kernel modules
Now, we have to do one more thing:
Start Yast > Security & Users > Users & Group Mngt > select your user name > edit > Details & over on the right tick “vboxusers”
OK out of Yast
Reboot
start Vbox and go through the setup; I used a dynamic disk so it grows only as I fill it
you can read the vbox help; they have a forum
you can download the additions when you have the OS installed; I installed them from safe mode, F8 at boot, in win7
It’s so cool that Opensuse is finally to the point where I can use VMs on my laptop. I use Win7 routinely for software not available on Linux, but mostly I use straight Opensuse (13.2x64). I’m following cybersecurity blogs and was looking at Qubes. That looks good, but it’s just a distro that forces you to use Xen. Let me get this straight - you always use VNC to access virtual machines when running the Xen opensuse kernel? It’s nice that Virtualbox takes care of all this machine-access part for you. But I think Xen might be a little more secure than Virtualbox, or at least, that’s the inference I see on various security pages.
Well,
Virtualbox is a bit less secure I’m sure because those compromises were made to make the app more User-friendly.
But, If better security is desired, it shouldn’t be too hard to Google some discussions on the topic and make the necessary modifications.
Virtualbox is also intended for Desktop app use, and I doubt encouraged to be used for Production use.