On 11/14/2017 01:33 AM, Michal Kubecek wrote:
On Monday, 13 November 2017 22:41 Stefan Seyfried wrote:
Am 13.11.2017 um 21:03 schrieb Larry Finger:
On 11/13/2017 12:20 PM, Dominique Leuenberger wrote:
In the E-mail with subject "New Tumbleweed snapshot 20171112 released!",> we see the following:
Packages changed: ...
kernel-source (4.13.11 -> 4.13.12)
...
As noted, the kernel after updating will be 4.13.12; however, the VirtualBox kernel modules in the repos are for kernel 4.13.10.
But the weak-modules functionality should catch this, or am I mistaken and this does not work on Factory / Tumbleweed?
I don't think weak-modules can work reliably in Tumbleweed where we make no attempt to preserve kABI. There is always a chance this particular update doesn't break kABI (or at least not the part relevant for virtualbox modules) but in general, you can't rely on that.
Also, a KMP has an explicit dependency on kernel version/release it was built against (no idea if it's the case here).
Michal Kubeček
Michal, Thanks for that information. Yes, the KMP has such a dependency on the kernel version. Would it be a good thing to add a test for the VB KMP to openQA? At least passing the test would provide some assurance that VMs would function after an update. If such a test would be useful, could someone help with the openQA test? It could be as simple as running "modprobe vboxdrv | lsmod | grep vboxdrv" as root and checking for an output that is not empty. Unfortunately, I have no clue on how to write such a test. I have reworked file /sbin/vboxconfig so that it no longer fails if the host source package is for the wrong version. In most cases, that should work. At least a simple script should not kill a local build of the modules. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org