1. Forum
  2. Usenet
  3. COMP.OS.LINUX.ADVOCACY

  • Kexec (and HyperV) (was: Re: Dimdows Decay Syndrome Continues)

    From vallor@21:1/5 to ldo@nz.invalid on Sat Feb 8 08:44:20 2025
    XPost: alt.comp.os.windows-11

    On Sat, 8 Feb 2025 06:36:16 -0000 (UTC), Lawrence D'Oliveiro
    <ldo@nz.invalid> wrote in <vo6u10$3ue2q$1@dont-email.me>:

    On Fri, 7 Feb 2025 20:29:39 -0500, CrudeSausage wrote:

    On 2025-02-07 4:34 p.m., Lawrence D'Oliveiro wrote:

    And today, Microsoft’s own experts have no clear idea what Windows is
    doing any more. Why do you think it needs to reboot about five times
    just to do an OS install?

    I have to admit those reboots are a nuisance. Of course, Fedora
    rebooted pretty often too.

    There are ways to minimize that. 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.

    ObWindows: There was a post recently about various virtualization
    solutions. Linux subsystem for Windows now uses HyperV, and I'm
    wondering if there is a native manager that Windows includes for other
    HyperV guests?

    --
    -v System76 Thelio Mega v1.1 x86_64 NVIDIA RTX 3090 Ti
    OS: Linux 6.13.1 Release: Mint 22.1 Mem: 258G
    "These shoes look like Frankenstein's hand-me-downs."

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to vallor on Sat Feb 8 06:41:52 2025
    XPost: alt.comp.os.windows-11

    On Sat, 2/8/2025 3:44 AM, vallor wrote:
    On Sat, 8 Feb 2025 06:36:16 -0000 (UTC), Lawrence D'Oliveiro
    <ldo@nz.invalid> wrote in <vo6u10$3ue2q$1@dont-email.me>:

    On Fri, 7 Feb 2025 20:29:39 -0500, CrudeSausage wrote:

    On 2025-02-07 4:34 p.m., Lawrence D'Oliveiro wrote:

    And today, Microsoft’s own experts have no clear idea what Windows is >>>> doing any more. Why do you think it needs to reboot about five times
    just to do an OS install?

    I have to admit those reboots are a nuisance. Of course, Fedora
    rebooted pretty often too.

    There are ways to minimize that. 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.

    ObWindows: There was a post recently about various virtualization
    solutions. Linux subsystem for Windows now uses HyperV, and I'm
    wondering if there is a native manager that Windows includes for other
    HyperV guests?


    That would be on the Professional SKU, at a minimum.

    [Picture]

    https://i.postimg.cc/NjzsHk9M/Hyper-V-on-parade.gif

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lawrence D'Oliveiro@21:1/5 to vallor on Sat Feb 8 23:42:11 2025
    XPost: alt.comp.os.windows-11

    On 8 Feb 2025 08:44:20 GMT, vallor wrote:

    On Sat, 8 Feb 2025 06:36:16 -0000 (UTC), Lawrence D'Oliveiro
    <ldo@nz.invalid> wrote in <vo6u10$3ue2q$1@dont-email.me>:

    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 <https://manpages.debian.org/kexec_load(2)>:

    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
    <https://manpages.debian.org/reboot(2)> 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).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From vallor@21:1/5 to ldo@nz.invalid on Sun Feb 9 00:25:51 2025
    XPost: alt.comp.os.windows-11

    On Sat, 8 Feb 2025 23:42:11 -0000 (UTC), Lawrence D'Oliveiro
    <ldo@nz.invalid> wrote in <vo8q4j$8tqo$2@dont-email.me>:

    On 8 Feb 2025 08:44:20 GMT, vallor wrote:

    On Sat, 8 Feb 2025 06:36:16 -0000 (UTC), Lawrence D'Oliveiro
    <ldo@nz.invalid> wrote in <vo6u10$3ue2q$1@dont-email.me>:

    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 <https://manpages.debian.org/kexec_load(2)>:

    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 <https://manpages.debian.org/reboot(2)> 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?"

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)