Can't install and run virtualbox after upgrade from 13.1 to 13.2

English Install/Boot/Login
1

He,

Il upgrade my opensuse version from 13.1 to 13.2 without any problems.
i have already virtualbox nstalled in 13.1. It doesn’t works after upgrade.
So i removed the package and reinstall it. It’s seem that the installation doesn’t works, i have no entries in application launcher.
Here’s the console output, could some one have a solution.

thanks

Elie@linux-ru39:~> sudo zypper in virtualbox
Chargement des données du dépôt…
Lecture des paquets installés…
Résolution des dépendances des paquets…

Les 4 NOUVEAUX paquets suivants vont être installés :
python-virtualbox vboxgtk vboxgtk-lang virtualbox

Les 2 paquets recommandés suivants ont été automatiquement sélectionnés :
vboxgtk vboxgtk-lang

4 paquets à installer.
Taille de téléchargement totale : 12,6 MiB. Déjà en cache : 0 B Après l’opération, 29,3 MiB d’espace disque supplémentaire sera utilisé.
Continuer ? [o/n/? affiche toutes les options] (o): o
Récupération de paquet virtualbox-4.3.18-1.6.x86_64 (1/4), 12,3 MiB ( 28,3 MiB décompressé)
Récupération: virtualbox-4.3.18-1.6.x86_64.rpm …[fait (219,1 KiB/s)]
Récupération de paquet python-virtualbox-4.3.18-1.6.x86_64 (2/4), 318,5 KiB (705,2 KiB décompressé)
Récupération: python-virtualbox-4.3.18-1.6.x86_64.rpm …[fait (181,2 KiB/s)]
Récupération de paquet vboxgtk-0.8.2-6.1.5.noarch (3/4), 53,9 KiB (258,4 KiB décompressé)
Récupération: vboxgtk-0.8.2-6.1.5.noarch.rpm …[fait]
Récupération de paquet vboxgtk-lang-0.8.2-6.1.5.noarch (4/4), 8,6 KiB ( 11,6 KiB décompressé)
Récupération: vboxgtk-lang-0.8.2-6.1.5.noarch.rpm …[fait]
Vérification des conflits de fichiers : …[fait]
(1/4) Installation: virtualbox - 4.3.18-1.6 …[fait]
Sortie rpm supplémentaire:
creating group vboxusers…
setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxSDL to root:vboxusers 4750. (wrong permissions 0750)

(2/4) Installation: python-virtualbox - 4.3.18-1.6 …[fait]
(3/4) Installation: vboxgtk - 0.8.2-6.1.5 …[fait]
(4/4) Installation: vboxgtk-lang - 0.8.2-6.1.5 …[fait]

2

Remove those three packages again and install virtualbox-qt instead, that’s the official GUI.
vboxgtk was some third party GTK frontend, but it hasn’t been changed since 2 years, does not fully support VirtualBox>=4.2, and doesn’t seem to work at all with current python-gtk:
http://bugzilla.opensuse.org/show_bug.cgi?id=902610

And it even has been dropped from the distribution completely recently for exactly those reasons, but it’s still in 13.2.

Again, virtualbox-qt, the Qt4 based official GUI, should work fine, and support all features of course.

3

Thanks for your replies, i remove all the 4 packages and installed
virtualbox virtualbox-qt

But the result is the same, have you an other idea.

Thanks

Récupération de paquet virtualbox-4.3.18-1.6.x86_64 (1/2), 12,3 MiB ( 28,3 MiB décompressé)
Récupération: virtualbox-4.3.18-1.6.x86_64.rpm …[fait (122,8 KiB/s)]
Récupération de paquet virtualbox-qt-4.3.18-1.6.x86_64 (2/2), 3,9 MiB ( 19,6 MiB décompressé)
Récupération: virtualbox-qt-4.3.18-1.6.x86_64.rpm …[fait (170,6 KiB/s)]
Vérification des conflits de fichiers : …[fait]
(1/2) Installation: virtualbox - 4.3.18-1.6 …[fait]
Sortie rpm supplémentaire:
creating group vboxusers…
setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong permissions 0750)
setting /usr/lib/virtualbox/VBoxSDL to root:vboxusers 4750. (wrong permissions 0750)

(2/2) Installation: virtualbox-qt - 4.3.18-1.6 …[fait]
Sortie rpm supplémentaire:
setting /usr/lib/virtualbox/VirtualBox to root:vboxusers 4750. (wrong permissions 0750)

Elie@linux-ru39:~>

4

Well, what is your actual problem?

The missing entry in the application launcher?
Sometimes KDE doesn’t pick up immediately that a new application is installed.
Run “kbuildsycoca4” or logout/login and it should be there.
(although you didn’t tell whether you use KDE or something else…)

Or run “VirtualBox” in a terminal window.

If it still doesn’t work, please describe in more detail what happens, i.e. what do you do to run it, does a window appear, do you get an error message, or what?
Just saying “it doesn’t work” makes it impossible to help.

It works fine here… :wink:

5

I use KDE
There is no entry in the application launcher
When i run virtualbox in a terminal, the virtualbox program start but when i start a Windows 7 VM i get the message

*The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

‘/etc/init.d/vboxdrv setup’

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

*If i do ‘/etc/init.d/vboxdrv setup’ in a terminal i got the message

*Recompiling VirtualBox kernel module, NOT. It has been packaged.
*

6

Again, it should be. In System->Emulators.
If not, try running “kbuildsycoca4” as mentioned, maybe even “kbuildsycoca4 --noincremental” to recreate KDE’s menu cache.
Or logout/login.

When i run virtualbox in a terminal, the virtualbox program start but when i start a Windows 7 VM i get the message

*The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing

‘/etc/init.d/vboxdrv setup’

as root. If it is available in your distribution, you should install the DKMS package first. This package keeps track of Linux kernel changes and recompiles the vboxdrv kernel module if necessary.

Ok. So the kernel module us not found.
Which kernel are you running?

uname -a

Which virtualbox and kernel packages do you have installed exactly now?

rpm -qa | egrep "kernel|virtualbox

If i do ‘/etc/init.d/vboxdrv setup’ in a terminal i got the message

*Recompiling VirtualBox kernel module, NOT. It has been packaged.
*

Yes, the openSUSE packages contain the kernel module pre-compiled, in binary form. No source code. Therefore you cannot re-compile it.

7

Missing a last quote

rpm -qa | egrep "kernel|virtualbox

should be

rpm -qa | egrep "kernel|virtualbox"

or

rpm -qa 'kernel*' '[Vv]irtual[Bb]ox*'
8

Yes, of course. Sorry! :shame:

or

rpm -qa 'kernel*' '[Vv]irtual[Bb]ox*'

Should work as well. But I prefer my version, easier to type I think. :wink:
But I wasn’t thinking that VirtualBox (from virtualbox.org) might be installed as well (I didn’t get that idea when reading the original post).
So probably even better:

rpm -qa | egrep -i "kernel|virtualbox"
9

So probably even better:

rpm -qa | egrep -i "kernel|virtualbox"

Yes that is correct, and more portable too because it use POSIX grep and not jut GNU.
according to

http://pubs.opengroup.org/onlinepubs/009695399/utilities/grep.html

Also i use the ] and globs * but might not work with the C shell family. So in theory your code should work on any Unix shell, but life is full of surprises :).

10

here are the result

Elie@linux-ru39:~> uname -a
Linux linux-ru39.site 3.16.6-2-desktop #1 SMP PREEMPT Mon Oct 20 13:47:22 UTC 2014 (feb42ea) x86_64 x86_64 x86_64 GNU/Linux

Elie@linux-ru39:~> rpm -qa | egrep -i “kernel|virtualbox”
virtualbox-guest-kmp-desktop-4.2.18_k3.11.10_21-2.18.1.x86_64
kernel-desktop-devel-3.16.6-2.1.x86_64
kernel-desktop-3.11.10-21.1.x86_64
virtualbox-guest-x11-4.3.18-1.6.x86_64
kernel-desktop-devel-3.11.10-21.1.x86_64
virtualbox-host-kmp-desktop-4.2.18_k3.11.10_21-2.18.1.x86_64
kernel-syms-3.11.10-21.1.x86_64
virtualbox-guest-kmp-desktop-4.3.18_k3.16.6_2-1.6.x86_64
kernel-desktop-3.16.6-2.1.x86_64
kernel-default-devel-3.16.6-2.1.x86_64
virtualbox-4.3.18-1.6.x86_64
kernel-default-devel-3.11.10-21.1.x86_64
virtualbox-guest-tools-4.3.18-1.6.x86_64
virtualbox-guest-kmp-desktop-4.2.18_k3.11.6_4-2.2.10.x86_64
kernel-source-3.11.10-21.1.noarch
kernel-macros-3.16.6-2.1.noarch
virtualbox-host-kmp-desktop-4.3.18_k3.16.6_2-1.6.x86_64
kernel-xen-devel-3.16.6-2.1.x86_64
kernel-devel-3.11.10-21.1.noarch
virtualbox-qt-4.3.18-1.6.x86_64
kernel-xen-devel-3.11.10-21.1.x86_64
kernel-desktop-3.11.6-4.1.x86_64
kernel-devel-3.16.6-2.1.noarch
kernel-syms-3.16.6-2.1.x86_64
kernel-firmware-20140903git-2.4.noarch
kernel-source-3.16.6-2.1.noarch
Elie@linux-ru39:~>

11

*Again, it should be. In System->Emulators.
If not, try running “kbuildsycoca4” as mentioned, maybe even “kbuildsycoca4 --noincremental” to recreate KDE’s menu cache.
Or logout/login.
*
Do nothing better, no entry in Emulators, enven if you try to search “virtualbox” in application launcher, no result.

12

First of all, you do not need all those virtualbox-guest packages on the host!
They are useless on the host, they contain the guest additions as the name implies. You only need to install them in the guest if you are running openSUSE as guest (but they should be installed automatically in this case).

The other virtualbox packages actually do look ok.
But you still have the kernel modules from version 4.2.18 installed as well. Shouldn’t normally be a problem, but maybe that’s what causes your problem.
So please remove all virtualbox packages, and then only install the 3 necessary ones, i.e. virtualbox, virtualbox-qt, and virtualbox-host-kmp-desktop

sudo zypper rm virtualbox*
sudo zypper in virtualbox virtualbox-qt virtualbox-host-kmp-desktop

It should work then.

No idea why the entry doesn’t show up in the menu, but maybe this will get fixed as well by the reinstall.

Another side-note:
I see kernel-desktop 3 times in your list: 3.16.6 (i.e. the one from 13.2), 3.11.10-21 (the latest 13.1 one) and 3.11.6 (the one 13.1 shipped with).
Normally only the latest two kernels are kept, so you shouldn’t actually have 3.11.6.
I’d suggest to try removing it manually. Maybe it is required by some old KMP package you have installed, which might also cause problems.

sudo zypper rm kernel-desktop-3.11.6
13

I am following this case because I have the same problem.

De-installing and re-installing virtualbox as indicated has not solved it for me, unfortunately.

I am still asked to vboxdrv setup, and that gives only the same error message as for everyone else.

Any other ideas?

14

Which one? The one from openSUSE, or the one from Oracle?

If you are using the one from Oracle, you have to run “/etc/init.d/vboxdrv setup” after every kernel update (and after a distribution upgrade as well obviously).
Unless you do that automatically via dkms.

I am still asked to vboxdrv setup, and that gives only the same error message as for everyone else.

Everyone else? I don’t get that error message, it worked just fine here imediately after the upgrade to 13.2 without having to do anything special… :wink:

Please post a list of all your installed virtualbox and kernel packages:

rpm -qa | egrep -i "virtualbox|kernel"

And the output of “uname -a”, to be sure.

15

Thanks for the quick reaction.

I am using the one from opensuse, as it has worked very well in the past.

Doing “/etc/init.d/vboxdrv setup” gives me the famous error message “Recompiling VirtualBox kernel module, NOT. It has been packaged.” which is of no help whatsoever.

uname -a gives me

Linux wolfgang-lt 3.16.6-2-desktop #1 SMP PREEMPT Mon Oct 20 13:47:22 UTC 2014 (feb42ea) x86_64 x86_64 x86_64 GNU/Linux

rpm -qa | egrep -i “virtualbox|kernel” gives me

kernel-source-3.11.10-21.1.noarch
kernel-default-devel-3.16.6-2.1.x86_64
kernel-macros-3.16.6-2.1.noarch
kernel-desktop-3.16.6-2.1.x86_64
kernel-devel-3.11.10-21.1.noarch
kernel-desktop-devel-3.11.10-21.1.x86_64
virtualbox-host-kmp-default-4.3.18_k3.16.6_2-123.1.x86_64
virtualbox-qt-4.3.18-123.1.x86_64
kernel-default-3.16.6-2.1.x86_64
kernel-xen-devel-3.11.10-21.1.x86_64
kernel-source-3.16.6-2.1.noarch
kernel-default-devel-3.11.10-21.1.x86_64
kernel-firmware-20140903git-2.4.noarch
kernel-devel-3.16.6-2.1.noarch
kernel-desktop-devel-3.16.6-2.1.x86_64
virtualbox-guest-kmp-default-4.3.18_k3.16.6_2-123.1.x86_64
virtualbox-host-kmp-desktop-4.3.18_k3.16.6_2-123.1.x86_64
kernel-default-3.11.10-21.1.x86_64
kernel-syms-3.16.6-2.1.x86_64
kernel-desktop-3.11.10-21.1.x86_64
kernel-xen-devel-3.16.6-2.1.x86_64
virtualbox-4.3.18-123.1.x86_64
virtualbox-guest-kmp-desktop-4.3.18_k3.16.6_2-123.1.x86_64
kernel-syms-3.11.10-21.1.x86_64

I am really stuck, I am afraid…

16

Yes, and it still does.

Doing “/etc/init.d/vboxdrv setup” gives me the famous error message “Recompiling VirtualBox kernel module, NOT. It has been packaged.” which is of no help whatsoever.

Of course.
The openSUSE package doesn’t contain any source code, so you cannot compile the module. It contains the kernel module in pre-compiled form, as binary, and that only matches one particular kernel. That’s why there is more than one virtualbox-host-kmp package.

rpm -qa | egrep -i “virtualbox|kernel” gives me:

First of all, you don’t need the virtualbox-guest-kmp packages on the host. But that won’t cause a problem.

Then, why do you have both kernel-default and kernel-desktop installed? That’s unnecessary IMHO. You could remove one (kernel-default, I’d suggest) and the corresponding kmp packages.

I don’t see anything inherently wrong with your packages though. Maybe something went wrong with the installation? (some weird installation/deinstallation order might have removed the kernel module file)
Try to reinstall the particular kmp for the current kernel:

sudo zypper in -f virtualbox-host-kmp-desktop

If that doesn’t help, try to remove all virtualbox packages, and only install the necessary ones as I wrote in a previous post already:

sudo zypper rm virtualbox*
sudo zypper in virtualbox virtualbox-qt virtualbox-host-kmp-desktop

And check that the kernel module is actually being loaded during boot:

systemctl status vboxdrv
chkconfig vboxdrv
17

Thanks again.

“systemctl status vboxdrv” gives me

vboxdrv.service - LSB: VirtualBox Linux module
Loaded: loaded (/etc/init.d/vboxdrv)
Active: inactive (dead)

Does that give a hint on anything?

18

It seems to be impossible to stop zypper from installing them…

I can do that, but again, almost any default operation of zypper seems to put them back…

In terms of “weirdness”, I am using qt5 and plasma5, but virtualbox DID work with these conditions during the last week or two.

tried that already, following your earlier recommendations…

19

No. That just says that it is not started.
What does “chkconfig vboxdrv” say?

Yeah, right.
Apparently kmp packages automatically supplement the main package, so they are effectively recommended by virtualbox, even the guest-kmp. :
Anyway, as mentioned they are not causing a problem.

I can do that, but again, almost any default operation of zypper seems to put them back…

That should not happen.
Unless you have anything else installed that requires or recommends kernel-default.

In terms of “weirdness”, I am using qt5 and plasma5, but virtualbox DID work with these conditions during the last week or two.

Well, qt5 and plasma5 should have no influence on the virtualbox kernel module. qt5 is even a requirement on 13.2, as YaST is using it.

tried that already, following your earlier recommendations…

Before or after you posted your package list?

I would suggest the following:

  • remove kernel-default and all dependencies:
sudo zypper rm kernel-default
  • remove all virtualbox packages:
sudo zypper rm virtualbox*
  • install the correct ones again:
sudo zypper in virtualbox virtualbox-qt virtualbox-host-kmp-desktop

If it still doesn’t work then, try to load the kernel module manually:

sudo /sbin/modprobe -v vboxdrv

And post the output of “dmesg|tail” afterwards.

And check that the kernel modules actually exist in the right place:

ls -l /lib/modules/3.16.6-2-desktop/updates
20

did all that, with no positive effect

Now THAT one solved it. What do we learn from that?

247.950246] Bluetooth: L2CAP socket layer initialized
247.950257] Bluetooth: SCO socket layer initialized
247.951726] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
247.951729] Bluetooth: BNEP filters: protocol multicast
247.951735] Bluetooth: BNEP socket layer initialized
1201.932990] capability: warning: `VirtualBox’ uses 32-bit capabilities (legacy support in use)
9137.630146] vboxdrv: Found 4 processor cores.
9137.630354] vboxdrv: fAsync=0 offMin=0x208 offMax=0x2a85
9137.630451] vboxdrv: TSC mode is ‘synchronous’, kernel timer mode is ‘normal’.
9137.630454] vboxdrv: Successfully loaded version 4.3.18_OSE (interface 0x001a0008).

total 1132
-rw-r–r-- 1 root root 548592 Nov 3 09:29 vboxdrv.ko
-rw-r–r-- 1 root root 415704 Nov 3 09:29 vboxguest.ko
-rw-r–r-- 1 root root 16128 Nov 3 09:29 vboxnetadp.ko
-rw-r–r-- 1 root root 41664 Nov 3 09:29 vboxnetflt.ko
-rw-r–r-- 1 root root 39264 Nov 3 09:29 vboxpci.ko
-rw-r–r-- 1 root root 79080 Nov 3 09:29 vboxsf.ko
-rw-r–r-- 1 root root 7256 Nov 3 09:29 vboxvideo.ko

Not sure what the conclusion from this is, but I am glad that I have my vbox back!