Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.os.linux.advocacy,alt.comp.os.windows-11 Subject: Re: Kexec (and HyperV) (was: Re: Dimdows Decay Syndrome Continues) Date: Sat, 8 Feb 2025 23:42:11 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: References: <9pdtpjdb64l7nitvc1vrdh4dqmank92caq@4ax.com> <4iJnP.222162$HO1.112840@fx14.iad> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sun, 09 Feb 2025 00:42:11 +0100 (CET) Injection-Info: dont-email.me; posting-host="91af83d9754a40698e08cc58e36c2bf7"; logging-data="292696"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19f31e9qni6vKmuOPsc/lTo" User-Agent: Pan/0.161 (Chasiv Yar; ) Cancel-Lock: sha1:uRUico/iiRHttsz0KOMGRH+Vlxk= Bytes: 2103 On 8 Feb 2025 08:44:20 GMT, vallor wrote: > On Sat, 8 Feb 2025 06:36:16 -0000 (UTC), Lawrence D'Oliveiro > wrote in : > >> Doesn’t RHEL support kexec, which >> allows the old Linux kernel to pass control to the new one without >> actually disrupting the userland? > > You're thinking of live kernel patching. kexec_load(2) load a kernel > that you can have execute if the current kernel crashes. You do this > for debugging, usually. Bit more than that : The kexec_load() system call loads a new kernel that can be executed later by reboot(2). And one of the functions of the latter is: LINUX_REBOOT_CMD_KEXEC (RB_KEXEC, 0x45584543, since Linux 2.6.13). Execute a kernel that has been loaded earlier with kexec_load(2).