Installed all but /home clean -- Virtual Box (vbox) did not install clean

I have a system that was Leap 42.1. Upgraded it to 42.2 by telling it to leave /home alone and format / /var, etc.

Used Yast to get all the needed Repositories.

Checked off Vbox for install.

After boot (since I picked up patches that needed a reboot), I started Vbox and it had problems. Reading various postings, they were typically about, “if you installed the RPM you shouldn’t need to do a make”, etc.

Well, it appears that with the kernel change, the RPM for Virtual Box hasn’t been updated.

Before I go through all the stuff to get the RPM from Oracle, and fight with this for a day or so (just like I had to do with Leap 42.1), any idea when this will get corrected, so that all I need to do is refresh the rpm install? (In this case, I’ve already deleted it with yast).

Hi
Don’t you just need to run the following after kernel changes?


 /etc/init.d/vboxdrv setup

If it gives you a headache and your system CPU supports virtualization, consider switch to kvm…?

Post:

uname -a
zypper se -si kernel virtualbox vbox
zypper lr -d

Before I answer your questions, how about answering mine?

“Before I go through all the stuff to get the RPM from Oracle, and fight with this for a day or so (just like I had to do with Leap 42.1), any idea when this will get corrected, so that all I need to do is refresh the rpm install? (In this case, I’ve already deleted it with yast).”

If this is not going to get fixed anytime soon, how about I consider a switch back to LEAP 42.1 where VBox does work so I don’t have to migrate a guest to another system?

And no vboxdrv setup did not fix it. It only brought up more problems.

Thanks, all of that is just wonderful if I were asking how to diagnose the problem. But, that is not what I was asking.

When, or better, how does one get the rpm fixed so that it installs with LEAP 42.2 and then starts up and runs, with no error messages? After all, 42.2 changed to a newer kernel from 42.1, so the RPM from 42.1 doesn’t just automatically work for 42.2.

And, as I said, I had to go through this with LEAP 42.1, so I think I know how to diagnose this, and run the needed commands.

With others posting (here and other “forums”) about having this problem, I figured asking the question here would get an answer of other than “issue these instructions dummy, because we know you didn’t follow the instructions”.

This behavior is driving people away from Linux as the desktop/host in my not so humble opinion (given that I started using Linux about 2002 in place of Winderz).

And how answering mine?

Virtualbox is running on all openSUSE Distributions without any Problems…

Hi
Because of issues like you have I switched to KVM awhile ago and never looked back, no having to compile anything, nice GUI and command line tools…

If you use the proprietary version, then suggest you take it up with Oracle? Oracle not keeping up with kernel changes, many possible reasons.

If your using the OSS version built on OBS, then a simple solution is to raise a bug report if you think it’s broken…
openSUSE:Submitting bug reports - openSUSE

That is correct, and that’s why you should (or need to) install the 42.2 packages on 42.2.
Virtualbox is included in the distribution.

And the standard 42.2 packages work fine here on two 42.2 systems…

So I dare to say that there is nothing wrong with package, and therefore nothing can be fixed in the package.

You likely have a local installation problem (mixture of incompatible packages?), and you need to fix that locally…
So please answer Sauerland’s questions.

Oh, and you didn’t even mention what error message you get.

This behavior is driving people away from Linux as the desktop/host in my not so humble opinion (given that I started using Linux about 2002 in place of Winderz).

What behavior?
That we try to find out what’s wrong on your system to help you fix it?

Interesting your assertion. But not my experience.

So, I am in the process of re-installing LEAP 42.2 on the machine in question. After that we shall see how things work.


It was suggested that I run KVM. Looked into that, and the ones pushing this actually suggest that one NOT use KVM when running W7 as a guest, but to use vbox instead.

Actually it is you who is making an assertion here.

Everybody else’s experience is different, openSUSE’s virtualbox works fine… :wink:

If you do not want any Help, why do you ask for it?

And the only thing we know is:
It is not working.

You are not willing to give any Information but here on Leap 42.2 it is working.

So it is on you to get it solved, but without any Information it is not possible.

Ok, what I have done is, I’ve gone and deleted Vbox, disabled the local repositories, fixed a few strange problems in an unrelated folder within the /home partition (historical data from an NT 4.0 system that LEAP 42.1 didn’t seem to have a problem with when it was used to back it up to a USB backup drive).

Then I went back into yast under the user’s account (it is my wife’s machine for the work she does) – which required me to give it root access (which I have, she does not), and installed virtualbox.

I attempted to run it. And it failed. Here are the answers to questions asked:

CODE:

ospjbt@linux-z14t:~> uname -a
Linux linux-z14t 4.4.49-16-default #1 SMP Sun Feb 19 17:40:35 UTC 2017 (70e9954) x86_64 x86_64 x86_64 GNU/Linux

CODE:

ospjbt@linux-z14t:~> zypper se -si kernel virtualbox
Loading repository data…
Reading installed packages…

S | Name | Type | Version | Arch | Repository
–±----------------------------±--------±---------------------±-------±----------------------
i | kernel-default | package | 4.4.49-16.1 | x86_64 | Main Update Repository
i | kernel-firmware | package | 20160516git-5.1 | noarch | Main Update Repository
i | virtualbox | package | 5.1.14-9.2 | x86_64 | Main Update Repository
i | virtualbox-host-kmp-default | package | 5.1.14_k4.4.36_8-9.2 | x86_64 | Main Update Repository
i | virtualbox-qt | package | 5.1.14-9.2 | x86_64 | Main Update Repository

ospjbt@linux-z14t:~> zypper lr -d
Repository priorities are without effect. All enabled repositories share the same priority.

| Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service

—±--------------------------------±----------------------------------------±--------±----------±--------±---------±---------±-------------------------------------------------------------------------±-------
1 | VBOX_local | VBOX local | No | ---- | ---- | 99 | plaindir | dir:///home/ospjbt/VirtualBox%20VMs/rpms |
2 | download.nvidia.com-leap | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.nvidia.com/opensuse/leap/42.2 |
3 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/non-oss/ |
4 | download.opensuse.org-non-oss_1 | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.2/non-oss/ |
5 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/leap/42.2/repo/oss/ |
6 | download.opensuse.org-oss_1 | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/42.2/oss |
7 | openSUSE-42.2-0 | openSUSE-42.2-0 | No | ---- | ---- | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-Memorex_MRX-550L_v4_CSAJ5461102279 |
8 | opensuse-guide.org-repo | Libdvdcss Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/openSUSE_Leap_42.2/ |
9 | packman.inode.at-suse | Packman Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://packman.inode.at/suse/openSUSE_Leap_42.2/ |
10 | repo-debug | openSUSE-Leap-42.2-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/42.2/repo/oss/ |
11 | repo-debug-non-oss | openSUSE-Leap-42.2-Debug-Non-Oss | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/debug/distribution/leap/42.2/repo/non-oss/ |
12 | repo-debug-update | openSUSE-Leap-42.2-Update-Debug | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/update/leap/42.2/oss/ |
13 | repo-debug-update-non-oss | openSUSE-Leap-42.2-Update-Debug-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/42.2/non-oss/ |
14 | repo-source | openSUSE-Leap-42.2-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.2/repo/oss/ |
15 | repo-source-non-oss | openSUSE-Leap-42.2-Source-Non-Oss | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/42.2/repo/non-oss/ |

Queried Virtual Box to have it show me what it is:

VirtualBox Graphical User Interface Version 5.1.14_SUSE r112924© 2004-2017 Oracle Corporation (Qt5.6.1)
Copyright © 2017 Oracle Corporation and/or its affiliates. All rights reserved.

Now, upon start of Vbox, this is what happened:

Pushed <Start> button. An attempt at build of the “window” for W7, appears and then immediately dispappears. Then this message shows up (the new error message, which is different from prior attempts):

Failed to open a session for the virtual machine W7 Home Premium.
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}

And this showed up in the log file:

00:00:11.018867 VM: fHMEnabled=true (configured) fRecompileUser=false fRecompileSupervisor=false
00:00:11.018869 VM: fRawRing1Enabled=false CSAM=true PATM=true
00:00:11.019021 VMSetError: /home/abuild/rpmbuild/BUILD/VirtualBox-5.1.14/src/VBox/VMM/VMMR3/HM.cpp(716) int HMR3Init(PVM); rc=VERR_SVM_DISABLED
00:00:11.019035 VMSetError: AMD-V is disabled in the BIOS (or by the host OS)
00:00:11.027796 crCtlSubmit failed (rc=VERR_NOT_SUPPORTED)
00:00:11.144621 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED)}, preserve=false aResultDetail=0
00:00:11.144793 Console: Machine state changed to ‘PoweredOff’
00:00:11.210060 Power up failed (vrc=VERR_SVM_DISABLED, rc=NS_ERROR_FAILURE (0X80004005))
00:00:11.504991 GUI: UIMachineViewScale::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:11.505033 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={02326f63-bcb3-4481-96e0-30d1c2ee97f6} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:11.505080 GUI: Aborting startup due to power up progress issue detected…

Again, this was working with Leap 42.1 just before I updated to 42.2.

Running on a AMD or Intel processor???

Did it change???

BTW runs fine here on an AMD FX chip

AMD-V

And no, the mother board/CPU didn’t change. All I did was upgrade the O/S to LEAP 42.2, by telling the install to ignore /home (mirrored raid) and had it format all the other partitions and then install. Then reconnected when I [re]created the userids.

Recommend this thread “reset,” restating some facts so that there is some common understanding…

First,
I understand that you had LEAP 42.1 installed, and you had Virtualbox installed.
Then, you did what you describe as an “upgrade” but really isn’t. When you reformatted your non-home partitions, you really created a new install re-using your /home partition, but everything else is brand new, not an upgrade. This probably wasn’t necessary, especially for the relatively minor upgrade from 42.1 to 42.2.

So, you really do need to do some checks to make sure your <new install> is working properly… It wouldn’t be a good idea to install apps and do any modifications to your system until you’ve verified to your own satisfaction that your 42.2 is rock solid. And, this should be done <without> installing any new applications like Virtualbox. And, be aware that a new Virtualbox install won’t necessarily automatically be able to run Guests created when your system was 42.1.

Now,
Once you’re satisfied with your LEAP 42.2 basic functionality, only then you should start making decisions about apps like Virtualbox. Virtualbox can be installed one of two ways from the openSUSE repos or from virtualbox.org (generally referred to as Oracle Virtualbox because the packages come from Oracle, not openSUSE). When you say you “Checked off Vbox for install” that would mean that you are installing the openSUSE packages and not packages from Oracle, so <on a new system> you should not need to run vboxdrv… Your problem is something else. As is always the case, when you don’t post exactly your command and the errors that result, people are guessing and perhaps not accurately.

The SDB for installing Virtualbox from the openSUSE repos
https://en.opensuse.org/SDB:VirtualBox_Installation

Should you decide to install Oracle Virtualbox instead, then you should disregard the instructions installing and running Virtualbox from the openSUSE repos, your procedure will be different.

TSU

AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).

Is it disabled in the Bios (I think no) but is it disabled in the Settings of the Machine?

Yes,
And, in particular this can and will happen if you flash upgrade the BIOS, all BIOS settings would then return to default undoing changes like whether virtualization is supported.

TSU

lscpu | grep Virt

Returns this:

Virtualization AMD-V

Now, is Linux saying it has it turned on, or is Linux saying that it is turned on in the Bios?

At any rate, I opened a bug report on this and that was the last thing they asked me for.

You can also enable/disable that Setting in the Settings of your Win7 Maschine:
http://openmafia.org/~osf/Screenshots/Auswahl_172.jpg

There was a bug found in the build:

I have verified the problem. There is something wrong with OBS (openSUSE Build
Service). When the standard kernel for Leap42.2 was upgraded from 4.4.36 to
4.4.49, an automatic rebuild of VirtualBox should have been triggered, but it
was not. Thus, your system (and mine) were left with a module that does not
match the running kernel.

When I try to manually trigger an update at OBS, I get an error message. I have
sent E-mail to the Factory mailing list to get an explanation and/or fix.

Seems I was correct in my hypothesis – something is wrong with the rpm.