virtualbox-kmp updates for patched kernel packages
Hi, do you know the reason why openSUSE doesn't provide pre-compiled virtualbox-kmp packages which are version compatible with the updated kernel packages? I think this is only a matter of triggering the rebuild of virtualbox:kmp when there is a new kernel package available. Thanks Markus
05.12.2020 18:45, Markus Kolb пишет:
Hi,
do you know the reason why openSUSE doesn't provide pre-compiled virtualbox-kmp packages which are version compatible with the updated kernel packages?
Without knowing openSUSE distribution and release this question is meaningless.
I think this is only a matter of triggering the rebuild of virtualbox:kmp when there is a new kernel package available.
a) virtualbox:kmp repository is not provided by "openSUSE" b) you could volunteer to do it - trigger rebuild when there is a new kernel package available
Am 05.12.2020 17:16, schrieb Andrei Borzenkov:
05.12.2020 18:45, Markus Kolb пишет:
Hi,
do you know the reason why openSUSE doesn't provide pre-compiled virtualbox-kmp packages which are version compatible with the updated kernel packages?
Without knowing openSUSE distribution and release this question is meaningless.
Friendly philosophy. A question is meaningless... Maybe just don't answer if you are not interested to answer questions!
I think this is only a matter of triggering the rebuild of virtualbox:kmp when there is a new kernel package available.
a) virtualbox:kmp repository is not provided by "openSUSE"
I've never talked about any repository, but the virtualbox-kmp packages... http://download.opensuse.org/distribution/leap/15.2/repo/oss/x86_64/virtualb... The newest update is from September http://download.opensuse.org/update/leap/15.2/oss/x86_64/virtualbox-kmp-defa... In the meantime there were 4 other kernel updates. Now at kernel-default-5.3.18-lp152.54.1.x86_64.rpm So not provided by openSUSE? Go home!
06.12.2020 01:35, Markus Kolb пишет:
Am 05.12.2020 17:16, schrieb Andrei Borzenkov:
05.12.2020 18:45, Markus Kolb пишет:
Hi,
do you know the reason why openSUSE doesn't provide pre-compiled virtualbox-kmp packages which are version compatible with the updated kernel packages?
Without knowing openSUSE distribution and release this question is meaningless.
Friendly philosophy. A question is meaningless... Maybe just don't answer if you are not interested to answer questions!
I think this is only a matter of triggering the rebuild of virtualbox:kmp when there is a new kernel package available.
a) virtualbox:kmp repository is not provided by "openSUSE"
I've never talked about any repository, but the virtualbox-kmp packages...
http://download.opensuse.org/distribution/leap/15.2/repo/oss/x86_64/virtualb...
The newest update is from September http://download.opensuse.org/update/leap/15.2/oss/x86_64/virtualbox-kmp-defa...
In the meantime there were 4 other kernel updates. Now at kernel-default-5.3.18-lp152.54.1.x86_64.rpm
So not provided by openSUSE? Go home!
openSUSE Leap version does not change kernel ABI during its lifetime. Module built for some kernel version shuold work for any future kernel update and does not require rebuild against newer kernels. If you observe that module stopped working after kernel update, this is bug that must be reported.
Am 06.12.2020 07:53, schrieb Andrei Borzenkov:
openSUSE Leap version does not change kernel ABI during its lifetime. Module built for some kernel version shuold work for any future kernel update and does not require rebuild against newer kernels. If you observe that module stopped working after kernel update, this is bug that must be reported.
It's no problem of ABI compatibility. Kernel updates are versioned differently to be able to install multiple versions at the same time and boot them. For this every other package providing kernel modules needs to honor the different kernel module path location (aka. /lib/modules/<VERSION>) after kernel updates. As far as I know this was and is always handled by providing a new matching package, which installs its modules in the correct path. But this is missed for virtualbox modules the last 4 times. Maybe the original "meaningless" question makes now sense for you and it is the only question I'd like to have an answer for.
06.12.2020 13:00, Markus Kolb пишет:
Am 06.12.2020 07:53, schrieb Andrei Borzenkov:
openSUSE Leap version does not change kernel ABI during its lifetime. Module built for some kernel version shuold work for any future kernel update and does not require rebuild against newer kernels. If you observe that module stopped working after kernel update, this is bug that must be reported.
It's no problem of ABI compatibility. Kernel updates are versioned differently to be able to install multiple versions at the same time and boot them. For this every other package providing kernel modules needs to honor the different kernel module path location (aka. /lib/modules/<VERSION>) after kernel updates. As far as I know this was and is always handled by providing a new matching package, which installs its modules in the correct path. But this is missed for virtualbox modules the last 4 times.
And virtualbox stopped working?
Maybe the original "meaningless" question makes now sense for you and it is the only question I'd like to have an answer for.
I answered this already - KMP built for earlier kernel version is continued to be used for kernel updates.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2020-12-06 at 11:00 +0100, Markus Kolb wrote:
Am 06.12.2020 07:53, schrieb Andrei Borzenkov:
openSUSE Leap version does not change kernel ABI during its lifetime. Module built for some kernel version shuold work for any future kernel update and does not require rebuild against newer kernels. If you observe that module stopped working after kernel update, this is bug that must be reported.
It's no problem of ABI compatibility. Kernel updates are versioned differently to be able to install multiple versions at the same time and boot them. For this every other package providing kernel modules needs to honor the different kernel module path location (aka. /lib/modules/<VERSION>) after kernel updates. As far as I know this was and is always handled by providing a new matching package, which installs its modules in the correct path. But this is missed for virtualbox modules the last 4 times.
No, it is handled via "weak updates". I don't have 15.2, but look: cer@Telcontar:~> l /lib/modules/ total 36 drwxr-xr-x 9 root root 4096 Nov 27 13:58 ./ drwxr-xr-x 11 root root 4096 Nov 27 13:25 ../ drwxr-xr-x 2 root root 4096 Apr 1 2019 4.12.14-lp150.11-default/ drwxr-xr-x 2 root root 4096 Jun 2 2019 4.12.14-lp151.24-default/ drwxr-xr-x 2 root root 4096 Mar 22 2020 4.12.14-lp151.27-default/ drwxr-xr-x 3 root root 4096 Sep 29 2019 4.12.14-lp151.28.10-default/ drwxr-xr-x 3 root root 4096 Nov 10 13:05 4.12.14-lp151.28.67-default/ drwxr-xr-x 5 root root 4096 Nov 13 15:29 4.12.14-lp151.28.79-default/ drwxr-xr-x 5 root root 4096 Nov 27 13:29 4.12.14-lp151.28.83-default/ cer@Telcontar:~> l /lib/modules/4.12.14-lp151.28.83-default/ total 4632 drwxr-xr-x 5 root root 4096 Nov 27 13:29 ./ drwxr-xr-x 9 root root 4096 Nov 27 13:58 ../ lrwxrwxrwx 1 root root 53 Nov 24 08:57 build -> /usr/src/linux-4.12.14-lp151.28.83-obj/x86_64/default/ drwxr-xr-x 13 root root 4096 Nov 27 13:25 kernel/ - -rw-r--r-- 1 root root 1147090 Nov 27 13:25 modules.alias - -rw-r--r-- 1 root root 1114054 Nov 27 13:25 modules.alias.bin - -rw-r--r-- 1 root root 5716 Nov 24 08:56 modules.builtin - -rw-r--r-- 1 root root 7341 Nov 27 13:25 modules.builtin.bin - -rw-r--r-- 1 root root 419848 Nov 27 13:25 modules.dep - -rw-r--r-- 1 root root 597146 Nov 27 13:25 modules.dep.bin - -rw-r--r-- 1 root root 401 Nov 27 13:25 modules.devname - -rw-r--r-- 1 root root 766 Nov 24 08:57 modules.fips - -rw-r--r-- 1 root root 156666 Nov 24 08:56 modules.order - -rw-r--r-- 1 root root 605 Nov 27 13:25 modules.softdep - -rw-r--r-- 1 root root 562712 Nov 27 13:25 modules.symbols - -rw-r--r-- 1 root root 681717 Nov 27 13:25 modules.symbols.bin lrwxrwxrwx 1 root root 34 Nov 24 08:57 source -> /usr/src/linux-4.12.14-lp151.28.83/ drwxr-xr-x 2 root root 4096 Nov 27 13:25 vdso/ drwxr-xr-x 3 root root 4096 Nov 27 13:25 weak-updates/ cer@Telcontar:~> cer@Telcontar:~> l /lib/modules/4.12.14-lp151.28.83-default/weak-updates/ total 12 drwxr-xr-x 3 root root 4096 Nov 27 13:25 ./ drwxr-xr-x 5 root root 4096 Nov 27 13:29 ../ drwxr-xr-x 2 root root 4096 Nov 27 13:25 extra/ cer@Telcontar:~> l /lib/modules/4.12.14-lp151.28.83-default/weak-updates/extra/ total 16 drwxr-xr-x 2 root root 4096 Nov 27 13:25 ./ drwxr-xr-x 3 root root 4096 Nov 27 13:25 ../ lrwxrwxrwx 1 root root 57 Nov 27 13:25 vboxdrv.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxdrv.ko lrwxrwxrwx 1 root root 59 Nov 27 13:25 vboxguest.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxguest.ko lrwxrwxrwx 1 root root 60 Nov 27 13:25 vboxnetadp.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxnetadp.ko lrwxrwxrwx 1 root root 60 Nov 27 13:25 vboxnetflt.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxnetflt.ko lrwxrwxrwx 1 root root 57 Nov 27 13:25 vboxpci.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxpci.ko lrwxrwxrwx 1 root root 56 Nov 27 13:25 vboxsf.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxsf.ko lrwxrwxrwx 1 root root 59 Nov 27 13:25 vboxvideo.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxvideo.ko cer@Telcontar:~> That's how the the virtualbox modules are linked kernel update after kernel update. The same modules created for 4.12.14-lp151.28.67-default/ are used in 4.12.14-lp151.28.83-default/.
Maybe the original "meaningless" question makes now sense for you and it is the only question I'd like to have an answer for.
You failed to mention 15.2 and exact links to the packages in your first post. His question was relevant, yours was not clear :-) - -- Cheers, Carlos E. R. (from openSUSE 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCX8zP0Rwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV2KQAni9sARj7W02lMwMFftOH 91M8JG0eAJ99D4xwftPduSY5oyOJPi3c0D+1mQ== =5yxn -----END PGP SIGNATURE-----
Am 06.12.2020 13:34, schrieb Carlos E. R.:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [...]
No, it is handled via "weak updates".
I don't have 15.2, but look:
[...]
cer@Telcontar:~> l /lib/modules/4.12.14-lp151.28.83-default/weak-updates/extra/ total 16 drwxr-xr-x 2 root root 4096 Nov 27 13:25 ./ drwxr-xr-x 3 root root 4096 Nov 27 13:25 ../ lrwxrwxrwx 1 root root 57 Nov 27 13:25 vboxdrv.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxdrv.ko lrwxrwxrwx 1 root root 59 Nov 27 13:25 vboxguest.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxguest.ko lrwxrwxrwx 1 root root 60 Nov 27 13:25 vboxnetadp.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxnetadp.ko lrwxrwxrwx 1 root root 60 Nov 27 13:25 vboxnetflt.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxnetflt.ko lrwxrwxrwx 1 root root 57 Nov 27 13:25 vboxpci.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxpci.ko lrwxrwxrwx 1 root root 56 Nov 27 13:25 vboxsf.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxsf.ko lrwxrwxrwx 1 root root 59 Nov 27 13:25 vboxvideo.ko -> /lib/modules/4.12.14-lp151.28.67-default/extra/vboxvideo.ko cer@Telcontar:~>
That's how the the virtualbox modules are linked kernel update after kernel update. The same modules created for 4.12.14-lp151.28.67-default/ are used in 4.12.14-lp151.28.83-default/.
Ok. Thanks a lot, Carlos. This is something I didn't remember. But somehow it has not worked in the meantime nevertheless. I had installed some kernels out of the row, also without module support, for debugging a kernel bug. Maybe this is the cause for stopping generating these links in the right place?! At the moment after reinstalling the original virtualbox-kmp package the links are in place. I'll have an eye on this with the next kernel update.
On 12/6/20 10:39 AM, Markus Kolb wrote:
Ok. Thanks a lot, Carlos. This is something I didn't remember. But somehow it has not worked in the meantime nevertheless. I had installed some kernels out of the row, also without module support, for debugging a kernel bug. Maybe this is the cause for stopping generating these links in the right place?! At the moment after reinstalling the original virtualbox-kmp package the links are in place. I'll have an eye on this with the next kernel update.
I had had problems with the pre-compiled modules during the vbox 5.2, 6.0 and 6.1 branch transitions. I finally just installed to rpms from Oracle and let dkms rebuild the modules on each kernel update. Not a big deal at all. -- David C. Rankin, J.D.,P.E.
participants (4)
-
Andrei Borzenkov -
Carlos E. R. -
David C. Rankin -
Markus Kolb