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

    UEFI guests not loading console

    Scheduled Pinned Locked Moved Unsolved Management
    20 Posts 5 Posters 1.3k Views 5 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.
    • planedropP Offline
      planedrop Top contributor @Mefosheez
      last edited by

      @Mefosheez Hmmm ok, yeah I would check a few of the logs on XCP-ng itself. https://docs.xcp-ng.org/troubleshooting/log-files/

      Also, has this host been rebooted fairly recently?

      MefosheezM 1 Reply Last reply Reply Quote 0
      • MefosheezM Offline
        Mefosheez @planedrop
        last edited by Mefosheez

        @planedrop notworking-uefi-new.txt working-bios-exisitng.txt

        yes i bounced the other day for testing purposes. no different results.

        attached is a tail on daemon.log

        this, is it enforcing something it should not?

        Dec 9 12:13:32 xcp-r630 varstored-17[1574285]: initialize_settings: Secure boot enable: false
        Dec 9 12:13:32 xcp-r630 varstored-17[1574285]: initialize_settings: Authenticated variables: enforcing

        and this, are the interesting bits. does it not see available memory?

        Dec 9 12:13:33 xcp-r630 qemu-dm-17[1574330]: Detected Xen version 4.17
        Dec 9 12:13:44 xcp-r630 qemu-dm-17[1574330]: AllocatePages failed: No 0x10400 Pages is available.
        Dec 9 12:13:44 xcp-r630 qemu-dm-17[1574330]: There is only left 0x3929 pages memory resource to be allocated.
        Dec 9 12:13:44 xcp-r630 qemu-dm-17[1574330]: ERROR: Out of aligned pages
        Dec 9 12:13:44 xcp-r630 qemu-dm-17[1574330]: ASSERT /builddir/build/BUILD/edk2-20220801/MdeModulePkg/Core/DxeIplPeim/X64/VirtualMemory.c(814): BigPageAddress != 0

        Thanks for the assist.

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

          Those error messages doesn't look good. Any idea @TeddyAstie ?

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

            @Mefosheez Looks like a OVMF bug to me (issue with PML5e ?).

            What CPU are you using ?

            MefosheezM 2 Replies Last reply Reply Quote 0
            • MefosheezM Offline
              Mefosheez @TeddyAstie
              last edited by

              @TeddyAstie intel e5-2680
              Screenshot 2024-12-10 at 8.03.07 AM.png

              If it is useful for troubleshooting I have a different host in the pool with an i7-3770 I could try and deploy this on.

              Thanks.

              TeddyAstieT planedropP 2 Replies Last reply Reply Quote 0
              • TeddyAstieT Offline
                TeddyAstie Vates 🪐 XCP-ng Team Xen Guru @Mefosheez
                last edited by

                @Mefosheez So it is not concerned with (potential) PML5e issues.

                Have you tried rebooting the host ?

                MefosheezM 1 Reply Last reply Reply Quote 0
                • planedropP Offline
                  planedrop Top contributor @Mefosheez
                  last edited by

                  @Mefosheez I would try it on that other host you have and see if you run into the same issues, just for good measure.

                  Are they managed by the same XO? Maybe you can just migrate it to the other host so it's the exact same VM.

                  MefosheezM 1 Reply Last reply Reply Quote 0
                  • MefosheezM Offline
                    Mefosheez @TeddyAstie
                    last edited by

                    @TeddyAstie I did a reboot but not change.

                    @planedrop They are and I will do it this afternoon.

                    Thanks.

                    1 Reply Last reply Reply Quote 0
                    • MefosheezM Offline
                      Mefosheez @planedrop
                      last edited by

                      @planedrop I found a sec to do this now. the host works as expected, the log is attached for boot. newhost-working.txt

                      So the the page allocation errors on the other host (lower level than I get normally) look to be uefi and qemu related. and the PML5e (found a white paper on it) seems to correlate as well. @TeddyAstie is there a reason you feel it is no longer relevant based on this chipset (e5-2680 v3)?

                      Thanks!

                      MefosheezM 1 Reply Last reply Reply Quote 0
                      • MefosheezM Offline
                        Mefosheez @Mefosheez
                        last edited by

                        @Mefosheez said in UEFI guests not loading console:

                        @planedrop I found a sec to do this now. the host works as expected, the log is attached for boot. newhost-working.txt

                        So the the page allocation errors on the other host (lower level than I get normally) look to be uefi and qemu related. and the PML5e (found a white paper on it) seems to correlate as well. @TeddyAstie is there a reason you feel it is no longer relevant based on this chipset (e5-2680 v3)?

                        Thanks!

                        wanted to add that the initial migration failed with a "network required" error when moving from pool-wide eth3 to pool-wide eth0. I removed the existing vif (eth3), ran migrate, and then created a new vif (eth0)

                        1 Reply Last reply Reply Quote 0
                        • MefosheezM Offline
                          Mefosheez @TeddyAstie
                          last edited by

                          @TeddyAstie Wanted to follow up and see if you had any insight on this pages error? I can confirm on a different host the VM will boot, I migrated it (live) back to the original host and it worked fine also, until I restarted it and then it failed the same way on boot up. same errors. thanks.

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

                            @Mefosheez

                            The only experience that I have is Server 2025 Eval with an older Xeon, vtpm, vsecure boot, vuefi and no problems with default configuration using win2022 template and turning on the above mentioned settings.

                            The only real difference is that I always uncheck automatic boot during creation, go into advanced and change the Intel NIC, save and then initial boot.

                            I mention that all of the settings are virtual because my old servers do not support hardware uefi or hardware tpm 2.0 so all of that must be synthetic for my lab.

                            I'm also using up to date XCP 8.3 with this VM.

                            MefosheezM 1 Reply Last reply Reply Quote 0
                            • MefosheezM Mefosheez referenced this topic on
                            • MefosheezM Offline
                              Mefosheez @Greg_E
                              last edited by

                              @Greg_E thanks for the feedback. I am stuck on this one. is either host or chipset specific and I don't have another e5-2680 v3 to test with. found another post on here around the same time frame that has this same error on boot. hope its not a broader issue.

                              https://xcp-ng.org/forum/topic/10075/imported-vm-starts-but-does-not-initialize-the-display

                              1 Reply Last reply Reply Quote 0
                              • MefosheezM Mefosheez referenced this topic on
                              • MefosheezM Mefosheez marked this topic as a question on
                              • First post
                                Last post