You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the transition to CentOS Stream 9 as the base image for OKD, we've lost support for newer hardware, since the 5.14 kernel shipped with CentOS 9 is from 2021. In particular, I've got some workloads on my clusters that make use of newer hardware, and the older kernel is unable to properly initialize these devices, which causes the pods to fail. These jobs used to work fine with the FCOS/Fedora kernel.
Would it be possible to either:
a) Pull in a newer/mainline kernel into the SCOS build? There seem to be several options here. I see ELRepo's kernel-ml, the Hyperscale SIG seems to build newer kernel versions, and so does the Kmods SIG.
b) Publish directions on how to build custom images so users can rebuild on their own? I found some directions, but they seem a bit unmaintained and make reference to RH-internal packages and repos which obviously isn't suitable.
The text was updated successfully, but these errors were encountered:
SriRamanujam
changed the title
SCOS build with up-to-date kernel?
SCOS build with more recent kernel?
Feb 23, 2025
With the transition to CentOS Stream 9 as the base image for OKD, we've lost support for newer hardware, since the 5.14 kernel shipped with CentOS 9 is from 2021. In particular, I've got some workloads on my clusters that make use of newer hardware, and the older kernel is unable to properly initialize these devices, which causes the pods to fail. These jobs used to work fine with the FCOS/Fedora kernel.
Would it be possible to either:
a) Pull in a newer/mainline kernel into the SCOS build? There seem to be several options here. I see ELRepo's
kernel-ml
, the Hyperscale SIG seems to build newer kernel versions, and so does the Kmods SIG.b) Publish directions on how to build custom images so users can rebuild on their own? I found some directions, but they seem a bit unmaintained and make reference to RH-internal packages and repos which obviously isn't suitable.
The text was updated successfully, but these errors were encountered: