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

    Cannot Install Windows 10 in New VM

    Scheduled Pinned Locked Moved Compute
    19 Posts 6 Posters 286 Views 4 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 @mickwilli
      last edited by

      @mickwilli Could you provide the host hardware configuration and ISO being used?

      M 1 Reply Last reply Reply Quote 0
      • M Offline
        mickwilli @dinhngtu
        last edited by

        @dinhngtu can you please explain what you mean and exactly what information you’re asking for?

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

          @mickwilli What host hardware do you have and which ISO did you use for the Windows installation? I assume you used the default Windows 10 template?

          M 1 Reply Last reply Reply Quote 0
          • M Offline
            mickwilli @dinhngtu
            last edited by

            @dinhngtu the host is a Dell Precision T3610 workstation with Intel Xeon processor and 120GB RAM. I used the default Windows 10 (64bit) template. The ISO was built with the Microsoft Windows 10 media creator about a month ago and it successfully installed a VirtualBox VM. The ISO is located on a NFS SR.

            1 Reply Last reply Reply Quote 0
            • A Offline
              acebmxer
              last edited by

              is the vm set to bios, uefi? is secure boot enabled in the vm?

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

                Also what Xeon model exactly?

                M 1 Reply Last reply Reply Quote 0
                • M Offline
                  mickwilli @acebmxer
                  last edited by

                  @acebmxer it is UEFI, and I’ve tried with and without secure boot enabled.

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    mickwilli @olivierlambert
                    last edited by

                    @olivierlambert it is a “ Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz”

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

                      Could you provide a crash dump?

                      M 1 Reply Last reply Reply Quote 0
                      • M Offline
                        mickwilli @dinhngtu
                        last edited by

                        @dinhngtu given it’s trying to boot from the installer, where would it save the crash dump to?

                        D 2 Replies Last reply Reply Quote 0
                        • D Offline
                          dinhngtu Vates 🪐 XCP-ng Team @mickwilli
                          last edited by

                          @mickwilli Forget that, I just realized E5-2660 v2 is way too old for Windows 10. See the supported processors.

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

                            @dinhngtu Win10 on XCP 8.3 with E5-2600v2 works just fine for me...

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

                              @Andrew Still, having an unsupported CPU makes it somewhat difficult to troubleshoot the issue, especially when it's a recent ISO. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED is sometimes associated with execution of unsupported instructions (though I don't know if that's the case here). For instance, there's a poke-of-death on some newer Intel CPUs related to the Architectural LBR feature (https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#windows-bug-check-0x3b-system_service_exception-on-systems-with-newer-intel-cpus).

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

                                @mickwilli Do you know how to create custom Windows PE ISOs? It might be possible to put the boot kernel in the ISO into debugging mode, then using the Connecting to guests using serial console guide to collect a crash analysis.

                                M 1 Reply Last reply Reply Quote 0
                                • M Offline
                                  mickwilli @dinhngtu
                                  last edited by

                                  @dinhngtu sorry, I don't know how to do that offhand. If you point me in the direction of some instructions, I'm happy to give it a go.

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

                                    @mickwilli You can extract the ISO, run the following command:

                                    bcdedit /store <extracted ISO path>\Boot\BCD /set debug on
                                    bcdedit /store <extracted ISO path>\Boot\BCD /dbgsettings serial debugport:1 baudrate:115200
                                    

                                    Then repack the ISO.

                                    You can also create a new ISO using this guide: https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-create-usb-bootable-drive then run the two commands above on media\Boot\BCD before you run MakeWinPEMedia.

                                    M 1 Reply Last reply Reply Quote 0
                                    • M Offline
                                      mickwilli @dinhngtu
                                      last edited by

                                      @dinhngtu Thanks. I'll try and give that a go in the next few days and will report back.

                                      Note that I have Windows 10 1803 installed without any issues. Trying to update to 22H2 fails with the same blue screen error as you'd expect. Sadly, no crash dump as it seems to fail very early in the boot process.

                                      TeddyAstieT 1 Reply Last reply Reply Quote 0
                                      • TeddyAstieT Offline
                                        TeddyAstie Vates 🪐 XCP-ng Team Xen Guru @mickwilli
                                        last edited by

                                        @mickwilli said in Cannot Install Windows 10 in New VM:

                                        @dinhngtu Thanks. I'll try and give that a go in the next few days and will report back.

                                        Note that I have Windows 10 1803 installed without any issues. Trying to update to 22H2 fails with the same blue screen error as you'd expect. Sadly, no crash dump as it seems to fail very early in the boot process.

                                        Do you get any additional BSOD details in xl dmesg ?

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