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
    28 Posts 7 Posters 509 Views 6 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.
    • 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 Offline
        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 Offline
            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 Offline
                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 1 Reply 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

                      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=v8.3-u-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
                        • First post
                          Last post