I had been running SLED12 SP3 with Vbox. Ran W7 as a guest just fine. Ok, long story very short: I got forced into having to get a new Mobo and CPU. This forced me into going to SLED15 to overcome all the EUFI problems.
So now I have this system running SLED15, and it boots just fine (as opposed to the rigmarole I was doing with the install CD and having to get to “more” and then select load linux…).
I have installed VBox using Yast and repos from OPENsuse on SLED15 – I didn’t see anything that provided Vbox with SLED15 repos.
The problem I am running into, regardless of the level of Vbox is there is a missing requirement.
It wants Libvpx.so.1 .
Perhaps I am using the wrong repo?
And the Oracle page that I wound up on, while doing a search for a fix to this problem, indicates that I also have to get some extension package, but I can’t seem to find it for SUSE. I can find it for a few other distros…
Anyone got some idea of how to get Vbox working?
I don’t think KVM is a solution until I can export the W7 system from Vbox, apparently by using Vbox to do the export. Well, once I get that fixed, then why go to KVM?
Hi
I’m guessing it’s part of the guest additions, did you install that
package?
Well, using KVM will negate the issue of compiled modules and breakages
with kernel updates. If your hardware/cpu supports virtualization, then
can’t beat KVM IMHO, plus it won’t taint the kernel, so if you have
issues at least it won’t be rejected if you create a bug report etc.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Ok, back to this (another problem had this one on hold – video display issues).
I now have this system running SLED 12 SP4, and I pulled in the repositories needed from LEAP 15…
At this point after installing VirtualBox (VBox), I tried to start it and it failed asking for a command to be issued, which asked for zypper to be run…
All of that seemed to work, and now I am back to a problem I’ve seen before but don’t remember how I fixed it the last time.
[QUOTEFailed to open a session for the virtual machine W7Premium.
AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}][/QUOTE]
I really do not think I have turned off AMD-V in the BIOS.
But, I’ll be back with an answer to that… (rebooting) – because I can’t remember the command to query this from within SLED…
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
[QUOTE=malcolmlewis;55986]Hi
From Linux to check it’s enabled;
egrep "vmx|svm" /proc/cpuinfo
In your case should be svm.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]
Long story very short. I’ve had a run of bad motherboards and work issues along with and issues with the new type of BIOS…
Have an ASUS board and went into the bios and finally found the way to set virtualization on.
I now have VirtualBox running but I can’t get the guest tools. The level of VBox and the tools do not match.
But I finally have it installed and running (actually have W10 running).
