[Bug 862766] New: VirtualBox lacks vboxdrv.ko following update to kernel-default-devel-3.11.10-7.1.x86_64.rpm
https://bugzilla.novell.com/show_bug.cgi?id=862766 https://bugzilla.novell.com/show_bug.cgi?id=862766#c0 Summary: VirtualBox lacks vboxdrv.ko following update to kernel-default-devel-3.11.10-7.1.x86_64.rpm Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: Markus.Kuhn@cl.cam.ac.uk QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 I yesterday ran "zypper update", which updated my kernel kernel-desktop|3.11.10-7.1|x86_64: /var/log/zypp/history: 2014-02-06 23:03:09|install|kernel-desktop|3.11.10-7.1|x86_64||repo-update|d4b38d39499b32730cd3f0ea68e7febd69fc329d231b25d6c04ab8b9333e505a| 2014-02-06 23:03:11|install|kernel-devel|3.11.10-7.1|noarch||repo-update|b2e9350f32495d6991e511a963b95d54c1ab013b0d12dfa8f2490d932026aeaf| 2014-02-06 23:03:12|install|kernel-docs|3.11.10-7.3|noarch||repo-update|614249f76a975dc4d13dda36758982a13696c98b0f5e528fb5797554367150a5| Since then, VirtualBox has been complaining Kernel driver not installed (rc=-1908) 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. I couldn't find anything with "zypper search dkms", so I assume vboxdrv.ko is supposed to come prepackaged with openSUSE, and indeed there is # rpm -ql virtualbox-host-kmp-desktop /lib/modules/3.7.10-1.11-desktop /lib/modules/3.7.10-1.11-desktop/updates /lib/modules/3.7.10-1.11-desktop/updates/vboxdrv.ko /lib/modules/3.7.10-1.11-desktop/updates/vboxnetadp.ko /lib/modules/3.7.10-1.11-desktop/updates/vboxnetflt.ko /lib/modules/3.7.10-1.11-desktop/updates/vboxpci.ko /lib/modules/3.11.6-4-desktop /lib/modules/3.11.6-4-desktop/updates /lib/modules/3.11.6-4-desktop/updates/vboxdrv.ko /lib/modules/3.11.6-4-desktop/updates/vboxnetadp.ko /lib/modules/3.11.6-4-desktop/updates/vboxnetflt.ko /lib/modules/3.11.6-4-desktop/updates/vboxpci.ko But those are still the kernel modules for the previous kernel version 3.11.6! It seems that openSUSE updated the kernel yesterday to 3.11.10-7, but forgot to update virtualbox-host-kmp-desktop at the same time, and therefore there is now no vboxdrv.ko matching the current kernel available. I've tried to load the available old driver with /sbin/insmod /lib/modules/3.11.6-4-desktop/updates/vboxdrv.ko But that just results in the error message Failed to open a session for the virtual machine Stackato-v3.0.1. Failed to open/create the internal network 'HostInterfaceNetworking-eth0' (VERR_SUPDRV_COMPONENT_NOT_FOUND). Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND). One of the kernel modules was not successfully loaded. Make sure that no kernel modules from an older version of VirtualBox exist. Then try to recompile and reload the kernel modules by executing '/etc/init.d/vboxdrv setup' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND). Could you please recompile virtualbox-host-kmp-desktop for the current kernel and push it out as an update? Reproducible: Always Steps to Reproduce: 1. Run "zypper update" to get latest kernel 3.11.10-7.1 2. Run VirtualBox and start a virtual machine with bridge configuration. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c1
Johannes Weberhofer
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c2
--- Comment #2 from Markus Kuhn
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c3
David Kerkhof
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c4
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c5
--- Comment #5 from David Kerkhof
The following NEW packages are going to be installed: kernel-desktop [....] This is different from what I am used to see in case of a kernel update where
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c6
Yarny Yarny
S | Name | Type | Version | Arch | Repository --+----------------------+------------+-------------+--------+------------ i | kernel-desktop | package | 3.11.10-7.1 | i686 | suse-update i | kernel-desktop | package | 3.11.6-4.1 | i686 | suse-oss | kernel-desktop | srcpackage | 3.11.10-7.1 | noarch | suse-update | kernel-desktop-base | package | 3.11.10-7.1 | i686 | suse-update | kernel-desktop-base | package | 3.11.6-4.1 | i686 | suse-oss | kernel-desktop-devel | package | 3.11.10-7.1 | i686 | suse-update | kernel-desktop-devel | package | 3.11.6-4.1 | i686 | suse-oss
On a side note: systemd doesn't see the failure of vboxdrv.service:
vboxdrv.service - LSB: VirtualBox Linux module Loaded: loaded (/etc/init.d/vboxdrv) Active: active (exited) since Sun 2014-02-09 08:54:00 CET; 13min ago Process: 1067 ExecStart=/etc/init.d/vboxdrv start (code=exited, status=0/SUCCESS)
Feb 09 08:54:00 XXX systemd[1]: Starting LSB: VirtualBox Linux module... Feb 09 08:54:00 XXX vboxdrv[1067]: Starting VirtualBox kernel modules..failed Feb 09 08:54:00 XXX vboxdrv[1067]: (modprobe vboxdrv failed. Please use 'dmesg' to Feb 09 08:54:00 XXX systemd[1]: Started LSB: VirtualBox Linux module. Should this be reported as a separate bug?
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c7
--- Comment #7 from Markus Kuhn
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c8
--- Comment #8 from Yarny Yarny
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c9
Wolfgang Bauer
our kmp concept should reuse the old driver also for the newer kernel.
that it does not work seems to point to a flaw within the kmp handling scripts , e.g. weak-updates etc.
I don't think it's a problem with the kmp handling scripts, as it worked fine with the nvidia driver RPMs here, which use the same mechanism AFAIK. And even if you create the link manually and load the kernel module, bridged networking does not work as reported in comment#2 (I could 100% reliably reproduce this here on two different systems). So the kernel module as packaged (compiled against kernel 3.11.6) seems to be incompatible with kernel 3.11.10. Maybe that's the reason why the symlink doesn't get created by the scripts in the first place? Btw, virtualbox from the Virtualization repo works fine, this does contain a kmp package for 3.11.10 (and a newer virtualbox version of course). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c10
Marcus Meissner
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c11
--- Comment #11 from Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c12
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c13
Luigi baldoni
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c14
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c15
--- Comment #15 from Luigi baldoni
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c16
--- Comment #16 from Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c17
Luigi baldoni
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c18
--- Comment #18 from Markus Kuhn
https://bugzilla.novell.com/show_bug.cgi?id=862766
https://bugzilla.novell.com/show_bug.cgi?id=862766#c19
--- Comment #19 from Benjamin Brunner
participants (1)
-
bugzilla_noreply@novell.com