Path: ...!3.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.karotte.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: vallor Newsgroups: comp.os.linux.advocacy,alt.comp.os.windows-11 Subject: Re: Kexec (and HyperV) (was: Re: Dimdows Decay Syndrome Continues) Date: 9 Feb 2025 00:25:51 GMT Lines: 35 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 X-Trace: individual.net ra57poVTydPLnNLF3IEkZwtKE3gbgTBKcrxqBBX+3e1fexqJr4 Cancel-Lock: sha1:Fw52sK05jXUeYpjZnOixGS0qPGE= sha256:eo0ZHZrdZunsy6kbiCS+VpJ/tTzA3QAAn7Bpedn+Jbw= X-Face: +McU)#<-H?9lTb(Th!zR`EpVrp<0)1p5CmPu.kOscy8LRp_\u`:tW;dxPo./(fCl CaKku`)]}.V/"6rISCIDP` User-Agent: Pan/0.161 (Hmm3; cd378e06; Linux-6.13.1) Bytes: 2487 On Sat, 8 Feb 2025 23:42:11 -0000 (UTC), Lawrence D'Oliveiro wrote in : > 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). I don't see your point. (That's what I said.) It doesn't load "without disturbing the userland"... -- -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti OS: Linux 6.13.1 Release: Mint 22.1 Mem: 258G "Why is "easy listening" so hard to listen to?"