A Webmin module for KernelCare would be nice, too. All it would minimally need to do would be defer non-critical kernel updates for a few days (which is what I basically do manually). It could also do more; but since the goal is to avoid reboots due to kernel updates, that would minimally be enough.
I think you have an opportunity to influence these decisions I for one will be very interested in which direction you go or show support for. After getting so much help from you and the rest of the team here over the years, I respect and value your opinion very much on these matters.
For me personally I basically want the equivalent of what we always had with CentOS - a reliable, secure, production-ready distro.
Stream does sound a little bit interesting, as the only thing I wished with CentOS in the past is that it wasn’t so behind in terms of packages - so maybe this could be a good thing and I’m certainly keeping my options open - but as soon as I start experiencing issues with it, or begin to hear that lots of others are, I will be looking to move to something else (such as Debian or Rocky Linux).
That would be pretty tough to pull off for CL because it’s pretty highly-customized, as is Virtualmin.
On the other hand, it would be in both companies’ interests; so I can’t imagine Igor turning down a request by Virtualmin for a few free licenses (nor vice-versa) to see if they could make it work. But Igor’s guys are probably working full-time on Lenix, and our guys are overworked as it is.
By the way, KernelCare works just fine in Virt without an official module. I basically just ignore non-critical kernel updates until they get live-patched, which can take a few hours to a few days. By “non-critical,” I mean not security-related, and not correcting some bug that I’ve actually been experiencing.
Occasionally, the KernelCare patches actually happen before the official kernel updates, in which case I don’t even get the update notification. But a module would still be nice to have.
Here are few things people should know about CentOS Linux Stream:
Stream is NOT clone I used, and kernel will never be as stable as RHEL cloned kernel,
EPEL will not be complied against Stream but against RHEL packages
ElRepo 3rd party drivers will NEVER be compiled against Stream kernels but against RHEL kernels. If you have (hardware) system that needs drivers not in a RHEL kernel, you can loose connection or storage link after reboot.
At some points in time new Stream kernels will come at such a fast pace that driver builders will not be able to keep up
With possible frequent changes in kABI curremt kmod/weak update driver/module model will not be applicable to Stream like it is to CentOS Linux.