After a kernel upgrade vboxdrv is not starting anymore.
my current Kernel version is:
Linux delta 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
systemctel status vboxdrv gives the following output:
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded.
vboxdrv.service - LSB: VirtualBox Linux module
Loaded: loaded (/etc/init.d/vboxdrv)
Active: active (exited) since So 2015-08-23 20:35:23 CEST; 2min 16s ago
Process: 10470 ExecStop=/etc/init.d/vboxdrv stop (code=exited, status=0/SUCCESS)
Process: 10498 ExecStart=/etc/init.d/vboxdrv start (code=exited, status=0/SUCCESS)
In /var/log/messages I see no relevant errors:
2015-08-23T20:35:23.234293+02:00 delta kernel: 1875.226748] VBoxPciLinuxLinuxUnload
2015-08-23T20:35:23.266792+02:00 delta vboxdrv[10470]: Stopping VirtualBox kernel modules…done
2015-08-23T20:35:23.471320+02:00 delta kernel: 1875.464235] vboxdrv: Found 2 processor cores
2015-08-23T20:35:23.490069+02:00 delta kernel: 1875.482491] vboxdrv: TSC mode is Invariant, tentative frequency 1497829076 Hz
2015-08-23T20:35:23.490100+02:00 delta kernel: 1875.482498] vboxdrv: Successfully loaded version 5.0.2_SUSE (interface 0x00230003)
2015-08-23T20:35:23.695946+02:00 delta kernel: 1875.689478] VBoxNetFlt: Successfully started.
2015-08-23T20:35:23.700994+02:00 delta kernel: 1875he.694050] VBoxNetAdp: Successfully started.
2015-08-23T20:35:23.704156+02:00 delta kernel: 1875.697792] VBoxPciLinuxInit
2015-08-23T20:35:23.704178+02:00 delta kernel: 1875.697808] vboxpci: IOMMU not found (not registered)
2015-08-23T20:35:23.711260+02:00 delta vboxdrv[10498]: Starting VirtualBox kernel modules…done
The current installed RPMs are:
virtualbox-host-kmp-desktop-5.0.2_k3.16.7_24-178.d_l_ocaml.1.x86_64
virtualbox-websrv-5.0.2-178.d_l_ocaml.1.x86_64
virtualbox-5.0.2-178.d_l_ocaml.1.x86_64
virtualbox-guest-kmp-desktop-5.0.2_k3.16.7_24-178.d_l_ocaml.1.x86_64
Where can I try searching, what the error is, when I can’t see any error message at all?
What I already did:
- reboot system
- uninstall virtualbox
- install fresh virtualbox 5.0.2 from the virtualization repository
- reboot system again
Nothing really helped. What can I do more to find the error?
Best regards
Werner
Why are you booting that old kernel?
Boot the latest one that you installed as update.
systemctel status vboxdrv gives the following output:
VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded.
vboxdrv.service - LSB: VirtualBox Linux module
Loaded: loaded (/etc/init.d/vboxdrv)
Active: active (exited) since So 2015-08-23 20:35:23 CEST; 2min 16s ago
Process: 10470 ExecStop=/etc/init.d/vboxdrv stop (code=exited, status=0/SUCCESS)
Process: 10498 ExecStart=/etc/init.d/vboxdrv start (code=exited, status=0/SUCCESS)
I see nothing wrong here.
The kernel modules do seem to be loaded correctly.
Why do you think they aren’t?
Also the /var/log/messages shows that they are loaded.
The current installed RPMs are:
virtualbox-host-kmp-desktop-5.0.2_k3.16.7_24-178.d_l_ocaml.1.x86_64
virtualbox-websrv-5.0.2-178.d_l_ocaml.1.x86_64
virtualbox-5.0.2-178.d_l_ocaml.1.x86_64
virtualbox-guest-kmp-desktop-5.0.2_k3.16.7_24-178.d_l_ocaml.1.x86_64
Are that all?
Please post the output of:
rpm -qa | egrep -i "vbox|virtualbox"
Oh, I missed that one. I was used to the fact in older distributions, that the newest kernel was always choosen first.
Now this one is running:
Linux delta 3.16.7-24-desktop #1 SMP PREEMPT Mon Aug 3 14:37:06 UTC 2015 (ec183cc) x86_64 x86_64 x86_64 GNU/Linux
Please post the output of:
Voilà, yes that’s all because I completely removed virtualbox and then reinstalled it to see, if the installation itself is intact.
virtualbox-host-kmp-desktop-5.0.2_k3.16.7_24-178.d_l_ocaml.1.x86_64
virtualbox-websrv-5.0.2-178.d_l_ocaml.1.x86_64
virtualbox-5.0.2-178.d_l_ocaml.1.x86_64
virtualbox-guest-kmp-desktop-5.0.2_k3.16.7_24-178.d_l_ocaml.1.x86_64
Best regards
Werner
Now the virtualbox is running again. So it seems, it was the old kernel.
Thanks a lot for this important hint.
Normally it should be, yes, unless you configure another one to be booted by default in YaST->System->Boot Loader.
What bootloader are you actually using?
Is it configured correctly in /etc/sysconfig/bootloader?
grep LOADER_TYPE /etc/sysconfig/bootloader
If not, the boot menu won’t be updated correctly on kernel updates.
Voilà, yes that’s all because I completely removed virtualbox and then reinstalled it to see, if the installation itself is intact.
virtualbox-host-kmp-desktop-5.0.2_k3.16.7_24-178.d_l_ocaml.1.x86_64
virtualbox-websrv-5.0.2-178.d_l_ocaml.1.x86_64
virtualbox-5.0.2-178.d_l_ocaml.1.x86_64
virtualbox-guest-kmp-desktop-5.0.2_k3.16.7_24-178.d_l_ocaml.1.x86_64
OK.
So you don’t seem to use any GUI frontend? You are only using the Web Frontend, right?
Otherwise you should have virtualbox-qt installed as well.