XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    [RHEL kernel bug] XCP vm fails to boot after newest kernel applied.

    Scheduled Pinned Locked Moved Solved Compute
    49 Posts 12 Posters 2.1k Views 14 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • anthonyperA Offline
      anthonyper Xen Guru
      last edited by

      FYI, there's a patch submitted to linux-stable (6.6 and earlier) but not yet in a stable release:
      https://lore.kernel.org/stable/20250411160833.12944-1-jason.andryuk@amd.com/

      I guess we'll have to wait until this is picked up by Linux, then Red Hat will have to pick that as well.

      1 Reply Last reply Reply Quote 0
      • B Offline
        bberndt @Greg_E
        last edited by

        @Greg_E said in XCP vm fails to boot after newest kernel applied.:

        @bberndt

        Ok, that might explain the difference.

        Would a LEAPP from Rocky 8 up to Alma 9 be possible and solve the issue?

        I did a (not LEAPP, but a migration script from Alama) from Rocky 8 to Alma 8, and it died. None of my Rocky 9's have had a problem so far, and of course end up with a completely different kernel.

        B 1 Reply Last reply Reply Quote 0
        • B Offline
          bufanda @Greg_E
          last edited by bufanda

          @Greg_E They are all running for a while but none where upgrades from RHEL 7 to RHEL 8. I don't do LEAPPs that gives me more often errors than it works. What I did though on one is replacing the System VDI with a newer one, but that was Alma 8 to Alma 9 and that one has no issues.

          1 Reply Last reply Reply Quote 0
          • B Offline
            bufanda @bberndt
            last edited by

            @bberndt you Rocky/Alma 9 will be fine since it's a bug in the kernel for 8 only.

            1 Reply Last reply Reply Quote 1
            • X Offline
              XCP-ng-JustGreat
              last edited by

              This is just a "me too" reply to indicate that I am also experiencing the boot failure immediately after upgrading AlmaLinux 8.10 to the latest kernel 4.18.0-553.50.1. Hopefully, the kernel fix will get integrated soon into the affected and popular RedHat 8 derivatives so that Alma and Rocky 8 et al. can continue to run on our favorite hypervisor. This is a bad one.

              G 1 Reply Last reply Reply Quote 0
              • G Offline
                Greg_E @XCP-ng-JustGreat
                last edited by

                @XCP-ng-JustGreat

                Strange that my fresh Alma 8.10 is still working after updates, makes me think k there is more to this than just the kernel.

                1 Reply Last reply Reply Quote 0
                • X Offline
                  XCP-ng-JustGreat
                  last edited by

                  @Greg_E Wondering what might be the difference? I am using the XenServer Linux tools version 8.4.0-1 and BIOS boot firmware.

                  G 1 Reply Last reply Reply Quote 0
                  • G Offline
                    Greg_E @XCP-ng-JustGreat
                    last edited by

                    @XCP-ng-JustGreat

                    I'm running the same guest tools.

                    Could it be a processor related issue? I'm running AMD v1756b in my lab, haven't had time to try in production that is Intel Silver.

                    B 1 Reply Last reply Reply Quote 0
                    • X Offline
                      XCP-ng-JustGreat
                      last edited by XCP-ng-JustGreat

                      @Greg_E Maybe it only affects Intel? That would be a new wrinkle. Perhaps other AMD users can confirm if the latest AlmaLinux 8 kernel runs fine on their AMD XCP-ng 8.3 hosts? Just read the above referenced RedHat bug report here: https://access.redhat.com/solutions/7116307 Sure enough, it says Xen + Intel in problem description. Check it out.

                      1 Reply Last reply Reply Quote 0
                      • B Offline
                        bufanda @Greg_E
                        last edited by

                        @Greg_E according to the Knowledge base of Redhawks it is den Witz Intel CPUs. So you AMD isn‘t affected

                        1 Reply Last reply Reply Quote 0
                        • P Offline
                          phil
                          last edited by

                          According to https://access.redhat.com/solutions/7116307 the bug is solved, but I don't get newer Kernels on Rocky yet.

                          G 1 Reply Last reply Reply Quote 0
                          • G Offline
                            Greg_E @phil
                            last edited by

                            @phil

                            Sad that even this documentation is locked behind a Redhat account, I can only read part of the problem description. Not going to make an account because it really doesn't affect me right now.

                            B 1 Reply Last reply Reply Quote 0
                            • B Offline
                              bberndt @Greg_E
                              last edited by

                              @Greg_E
                              I made a free account.
                              Resolution
                              The issue has been resolved with the errata: RHBA-2025:4337. Hence, update the kernel to kernel-4.18.0-553.51.1.el8_10 to fix the issue.

                              id assume it arrives soon? I as well, haven't seen it yet.

                              1 Reply Last reply Reply Quote 0
                              • olivierlambertO Online
                                olivierlambert Vates 🪐 Co-Founder CEO
                                last edited by olivierlambert

                                It's now available, yes 🙂 After update, reboot will work

                                edit: ha answered for RH, Alma and Rocky will follow soon I suppose

                                G 1 Reply Last reply Reply Quote 0
                                • G Offline
                                  Greg_E @olivierlambert
                                  last edited by

                                  @olivierlambert

                                  I just updated an Alma 8 and it has the .51 kernel now.

                                  B 1 Reply Last reply Reply Quote 0
                                  • B Offline
                                    bberndt @Greg_E
                                    last edited by

                                    @Greg_E said in XCP vm fails to boot after newest kernel applied.:

                                    @olivierlambert

                                    I just updated an Alma 8 and it has the .51 kernel now.

                                    Tried one of my Rocky's and still .50. I wonder where we can see the status of downstream fixes like that? anyone know? thanks.

                                    G 1 Reply Last reply Reply Quote 0
                                    • G Offline
                                      Greg_E @bberndt
                                      last edited by

                                      @bberndt

                                      This may sound stupid, but here goes...

                                      Does Rocky need to update to .50 before it can update to .51?

                                      I'd guess no, but I've been away from RHEL based stuff since the IBM rug pull. Only coming back because I may need it in the future as I jockey around trying to improve my paycheck.

                                      B 1 Reply Last reply Reply Quote 0
                                      • B Offline
                                        bberndt @Greg_E
                                        last edited by

                                        @Greg_E said in XCP vm fails to boot after newest kernel applied.:

                                        @bberndt

                                        This may sound stupid, but here goes...

                                        Does Rocky need to update to .50 before it can update to .51?

                                        I'd guess no, but I've been away from RHEL based stuff since the IBM rug pull. Only coming back because I may need it in the future as I jockey around trying to improve my paycheck.

                                        https://bugs.rockylinux.org/view.php?id=9307
                                        so, prolly soon-ish.

                                        G 1 Reply Last reply Reply Quote 0
                                        • G Offline
                                          Greg_E @bberndt
                                          last edited by

                                          @bberndt

                                          Alma must have dropped everything to push this out. I wonder what Oracle is doing, guessing they were hit by this too. I'd guess Rocky has this out pretty fast, they know it is important.

                                          1 Reply Last reply Reply Quote 0
                                          • G Offline
                                            glreed735
                                            last edited by

                                            I updated my Redhat 8 instances to the .51 kernel and it's back to working.

                                            The kernel version 4.18.0-553.51.1.el8_10.x86_64 for Red Hat Enterprise Linux 8 was released on April 30, 2025, as part of the bug fix advisory RHBA-2025:4337. ​

                                            This update addresses various issues and includes enhancements to improve system stability and performance. For detailed information about the fixes and improvements in this release, you can refer to the official Red Hat advisory.

                                            B 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post