http://bugzilla.opensuse.org/show_bug.cgi?id=1178360 http://bugzilla.opensuse.org/show_bug.cgi?id=1178360#c47 --- Comment #47 from Larry Finger <Larry.Finger@gmail.com> --- (In reply to Stefan Hundhammer from comment #42)

virtualbox-kmp-default rebuilds the kernel module in its post-install script (and recreates the initrd with dracut). Is it possible or plausible that in certain situations it does that with the wrong kernel headers or something like that? Using the ones of the currently running kernel rather than the one that is also being installed in the same "zypper dup" run?

If you build a kernel module with the wrong headers, the resulting code will simply not load, thus your supposition is wrong!

Is it plausible that this might be only a missing dependency in the virtualbox .spec file; or a post-install script being executed at an inappropriate time, before the complete upgrade process is complete?

The VirtualBox modules do not need to be in the initrd as they are not loaded until the file system is up and running. Nonetheless, the install system puts them in initrd. The spec process is rather complicated; however, I think it is doing the right thing otherwise. -- You are receiving this mail because: You are the assignee for the bug.