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

    Windows 2025 Standard 24H2.11 (iso release of sept 25) crash on reboot with "INACCESSIBLE BOOT DEVICE 0x7B" in XCP 8.2.1 and XCP 8.3

    Scheduled Pinned Locked Moved XCP-ng
    35 Posts 10 Posters 1.6k Views 8 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.
    • D Offline
      dinhngtu Vates 🪐 XCP-ng Team
      last edited by

      The cause has been found, and a fix is under way. Stay tuned.

      F 1 Reply Last reply Reply Quote 1
      • F Offline
        flakpyro @dinhngtu
        last edited by

        @dinhngtu Thats great news!

        1 Reply Last reply Reply Quote 0
        • D Offline
          dinhngtu Vates 🪐 XCP-ng Team
          last edited by dinhngtu

          Hi all, here's a pre-build of the fix for anyone who wants to test (8.3 only):

          wget https://koji.xcp-ng.org/repos/user/8/8.3/xcpng-users.repo -O /etc/yum.repos.d/xcpng-users.repo
          yum update --enablerepo=xcp-ng-ndinh1
          
          F A 2 Replies Last reply Reply Quote 2
          • F Offline
            francesco-maria @dinhngtu
            last edited by

            @dinhngtu will be released also for 8.2.1?

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

              8.2.1 is EOL: https://xcp-ng.org/blog/2025/09/16/xcp-ng-8-2-lts-reached-its-end-of-life/

              F 1 Reply Last reply Reply Quote 0
              • A Offline
                Andrew Top contributor @dinhngtu
                last edited by

                @dinhngtu On a quick test, the ISO boots and installs. When the VM boots from the HD it crashes (and on reboots).

                Updating XCP 8.3 with qemu-4.2.1-5.2.12.2~fixvwc1.1.xcpng8.3.x86_64 solves the issue and the installed windows image boots correctly without any additional changes.

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

                  That's great! \o/

                  1 Reply Last reply Reply Quote 0
                  • F Offline
                    francesco-maria @olivierlambert
                    last edited by

                    @olivierlambert this problem can cause a crash on update of windows 2025 VM on xcp-ng 8.2.1 or remains only a problem for fresh install?

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

                      8.2 is EOL, and also IDK how it's affected by this issue.

                      1 Reply Last reply Reply Quote 0
                      • D Offline
                        dinhngtu Vates 🪐 XCP-ng Team @francesco-maria
                        last edited by

                        @francesco-maria I haven't determined what exact conditions would trigger the issue. It seems to only happen on new installations for now, but it could very well change in the future. Though as long as you keep the Xen drivers installed, things should be OK.

                        F C 2 Replies Last reply Reply Quote 1
                        • F Offline
                          francesco-maria @dinhngtu
                          last edited by

                          @dinhngtu Thanks for info. I config that manual apply of fix solve the problem on my 8.3.
                          I only chance the yum update in yum update --enablerepo=xcp-ng-ndinh1

                          1 Reply Last reply Reply Quote 0
                          • D Offline
                            dinhngtu Vates 🪐 XCP-ng Team
                            last edited by dinhngtu

                            Hello all, the new test build qemu-4.2.1-5.2.12.2~fixvwc2.1.xcpng8.3 is now available.

                            If you have tested the fix before, you can update with this command:

                            yum update --enablerepo=xcp-ng-ndinh1
                            
                            A 1 Reply Last reply Reply Quote 1
                            • A Offline
                              Andrew Top contributor @dinhngtu
                              last edited by

                              @dinhngtu Same results with the updated qemu-4.2.1-5.2.12.2~fixvwc2.1.xcpng8.3.x86_64. The Win2025 VM (without Xen tools) fails to boot correctly using stock XCP 8.3 but starts correctly with the fixvwc patch. (no actual performance or other testing done).

                              1 Reply Last reply Reply Quote 0
                              • C Offline
                                coconutit
                                last edited by

                                @Andrew said in Windows 2025 Standard 24H2.11 (iso release of sept 25) crash on reboot with "INACCESSIBLE BOOT DEVICE 0x7B" in XCP 8.2.1 and XCP 8.3:

                                fixvwc patch

                                Having the same isaue with a new Windows Server 2025 VM , tried to get the updates but it failed also, see attached

                                fcdff538-909b-488c-837c-0898b84ee3b3-image.png

                                D 1 Reply Last reply Reply Quote 0
                                • D Offline
                                  dinhngtu Vates 🪐 XCP-ng Team @coconutit
                                  last edited by

                                  @coconutit Did you run thie command?

                                  wget https://koji.xcp-ng.org/repos/user/8/8.3/xcpng-users.repo -O /etc/yum.repos.d/xcpng-users.repo
                                  
                                  C 1 Reply Last reply Reply Quote 0
                                  • C Offline
                                    coconutit @dinhngtu
                                    last edited by

                                    @dinhngtu
                                    I ran the command you sent but same result trying get the fix . see attached pic.

                                    2c83cc66-154e-483c-b7a8-75209d7c643c-image.png

                                    Thanks for you help, trying to get this server in production.

                                    D 1 Reply Last reply Reply Quote 0
                                    • D Offline
                                      dinhngtu Vates 🪐 XCP-ng Team @coconutit
                                      last edited by

                                      @coconutit I made a mistake with the command, it should be:

                                      yum update --enablerepo=xcp-ng-ndinh1
                                      

                                      (updated up top)

                                      C J 2 Replies Last reply Reply Quote 0
                                      • C Offline
                                        coconutit @dinhngtu
                                        last edited by

                                        @dinhngtu
                                        Yeah!! that was the issue, update applied server booting!! Thanks.

                                        f4e009a8-e85a-40fe-954c-9dfa7798f2c7-image.png

                                        1 Reply Last reply Reply Quote 2
                                        • J Offline
                                          JCS-RVK @dinhngtu
                                          last edited by

                                          @dinhngtu That got my fresh install to boot as well. Thank you!

                                          1 Reply Last reply Reply Quote 2
                                          • C Offline
                                            cg @dinhngtu
                                            last edited by

                                            @dinhngtu I can't say on XCP-ng side, but it's likely linked to:
                                            August patch (and following), as Microsoft changed something to the NVMe stack.

                                            e.g.
                                            https://learn.microsoft.com/en-us/answers/questions/5536733/potential-ssd-detection-bug-in-windows-11-24h2-fol

                                            Google gives a lot about it. It seems that it most likely doesn't kill NVMes but can cause trouble.
                                            We have a few PCs becoming more unstable (BSODs) or even very slow after that upgrae.

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