Kexec is fine but I think the NMBL folk (https://fizuxchyk.wordpress.com/2024/06/13/nmbl-we-dont-need...) found that some hardware doesn't really like being initialized by the kernel twice (or by two different kernels if you prefer). This hardware or the drivers is written to assume that the kernel only boots once between resets.
Im not sure about initializing twice problem, sounds more like FUD to me. it is possible to leave computer as is for next kernel even with "whole memory allocation intact". maybe problem for "soft restart", but not for using linux as bootloader providing NVME boot capability usecase.
you can literally tell linux kernel - make my cpu XYZ look like cpu ABC... and everything works fine. [this was possible even before AI chatbots were a thing (ai joke sorry)]
Comments
You can boot an OS on NVME drive from another bootloader on a USB drive.
I have been using CloverBootloader for years.
https://github.com/CloverHackyColor/CloverBootloader
or KEXEC from linux kernel.
Kexec is fine but I think the NMBL folk (https://fizuxchyk.wordpress.com/2024/06/13/nmbl-we-dont-need...) found that some hardware doesn't really like being initialized by the kernel twice (or by two different kernels if you prefer). This hardware or the drivers is written to assume that the kernel only boots once between resets.
Kexec is amazing when this doesn't happen to you
How Clover deals with that ?
Im not sure about initializing twice problem, sounds more like FUD to me. it is possible to leave computer as is for next kernel even with "whole memory allocation intact". maybe problem for "soft restart", but not for using linux as bootloader providing NVME boot capability usecase.
you can literally tell linux kernel - make my cpu XYZ look like cpu ABC... and everything works fine. [this was possible even before AI chatbots were a thing (ai joke sorry)]