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

    Imported VM Starts but Does Not Initialize the Display

    Scheduled Pinned Locked Moved Solved Xen Orchestra
    51 Posts 8 Posters 3.4k Views 7 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.
    • K Online
      kagbasi-ngc
      last edited by

      Quick update to the situation.

      I imported the VM to another XCP-ng host I run at my church (rebuilt with v8.3) and the VM started up without any issues. So looks like the issue in my home lab may be related to nested-virtualization (although not sure exactly what).

      If someone has any ideas that would be awesome, cos I'd love to be able to experiment in a virtualized environment.

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

        Are you sure you are booting in the same mode than the original platform? (BIOS or UEFI)

        K 1 Reply Last reply Reply Quote 0
        • K Online
          kagbasi-ngc @olivierlambert
          last edited by

          @olivierlambert Yes sir, both are configured to boot UEFI. I didn't make any changes.

          I did notice, however, that in my virtualized environment (the one where I'm having the problem), the VM doesn't show the button to copy the secure boot certificates to the VM. See screenshots below.

          PHYSICAL ENVIRONMENT (Where the VM boots successfully😞
          Screenshot 2024-12-10 083318.png

          VIRTUALIZED ENVIRONMENT (Where the VM fails to boot😞
          Screenshot 2024-12-10 083346.png

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

            @stormi does this ring a bell?

            1 Reply Last reply Reply Quote 0
            • K kagbasi-ngc marked this topic as a question on
            • stormiS Offline
              stormi Vates 🪐 XCP-ng Team
              last edited by

              Regarding the "Copy the pool's default UEFI certificates to the VM" button, I believe it is only displayed if the pool was setup for Secure Boot first. However, an imported VM comes with its own certificates, so if it was booting up correctly with Secure Boot enforced before the export, it should still do so after an import, regardless of the pool state.

              Does it boot if you set Secure Boot to not enforced? I don't think it will, be let's try anyway.

              K 1 Reply Last reply Reply Quote 0
              • K Online
                kagbasi-ngc @stormi
                last edited by

                @stormi I turned off Secure Boot and it's the same result. VM starts (according to the log) but doesn't proceed to POST.

                stormiS 1 Reply Last reply Reply Quote 0
                • stormiS Offline
                  stormi Vates 🪐 XCP-ng Team @kagbasi-ngc
                  last edited by

                  @kagbasi-ngc So I believe this has more to do with nested virtualization. Does the XCP-ng VM have all the required virtualization capabilities?

                  K 1 Reply Last reply Reply Quote 0
                  • K Online
                    kagbasi-ngc @stormi
                    last edited by

                    @stormi Sorry for the delayed response. Yes, the XCP-ng VM has all the virtualization capabilities (as recommended in this guide- https://docs.xcp-ng.org/guides/xcpng-in-a-vm/). See screenshot below.

                    Screenshot 2024-12-10 141443.png

                    DanpD 1 Reply Last reply Reply Quote 0
                    • DanpD Offline
                      Danp Pro Support Team @kagbasi-ngc
                      last edited by

                      @kagbasi-ngc Maybe this? https://docs.xcp-ng.org/releases/release-8-3/#nested-virtualization-though-not-on-purpose

                      K stormiS 2 Replies Last reply Reply Quote 0
                      • K Online
                        kagbasi-ngc @Danp
                        last edited by

                        @Danp Well, that certainly puts a nail in this coffin...lol. Thanks for sharing, I'll stop testing then.

                        @olivierlambert should we leave this thread as unsolved until such time as nested virtualization is functional again within the codebase?

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

                          Can you try with XCP-ng 8.2?

                          K 1 Reply Last reply Reply Quote 0
                          • stormiS Offline
                            stormi Vates 🪐 XCP-ng Team @Danp
                            last edited by

                            @Danp This is about hypervisors nested inside XCP-ng 8.3, but here as I understood it it was XCP-ng nested inside another hypervisor, so in theory it should not be related.

                            1 Reply Last reply Reply Quote 1
                            • K Online
                              kagbasi-ngc @olivierlambert
                              last edited by kagbasi-ngc

                              @olivierlambert So I managed to whip up a v8.2.1 instance and attempted to import the VM, but the import wouldn't start. I simply get the message in the top-right - "Starting import" - then it would go away.

                              I couldn't find any errors on the host logs, but I found this error within XO itself (i.e., Settings > Logs) :

                              Screenshot 2024-12-11 025730.png

                              My takeaway from this is that I cannot export a VM from a newer host and import it into an older one.

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

                                Note: you cannot import a VM from a more recent XCP-ng to an older one (the opposite works though)

                                K 1 Reply Last reply Reply Quote 0
                                • K Online
                                  kagbasi-ngc @olivierlambert
                                  last edited by

                                  @olivierlambert Hmm, so why would you encourage me to try it, if you knew it wouldn't work....lol. 😕

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

                                    I encouraged you to test if nested XCP-ng 8.2 worked better than 8.3, that's it.

                                    K 1 Reply Last reply Reply Quote 0
                                    • K Online
                                      kagbasi-ngc @olivierlambert
                                      last edited by

                                      @olivierlambert Okay, so I'm at fault for reading too much into your guidance, eh? Okay.

                                      In that case then, I think we'd already established that nested virtualization works - because I have been able to add an SR, create VMs, add VDIs, etc., in the nested virtualization environment on 8.3. The only thing that was failing for me, which is the primary reason for standing it up, is the import of a VM.

                                      So is it safe to say this is not likely an issue with nested virtualization but with something else in the codebase that's preventing the imported VM from successfully initializing the display when in UEFI mode?

                                      stormiS 1 Reply Last reply Reply Quote 0
                                      • stormiS Offline
                                        stormi Vates 🪐 XCP-ng Team @kagbasi-ngc
                                        last edited by

                                        @kagbasi-ngc I'd check the output of xl dmesg and the contents of /var/log/daemon.log and /var/log/xensource.log after trying to start the VM.

                                        K 1 Reply Last reply Reply Quote 0
                                        • K Online
                                          kagbasi-ngc @stormi
                                          last edited by

                                          @stormi @olivierlambert

                                          As requested, please find the outputs of the logs:

                                          • Output of xl dmesg - https://gist.github.com/kismetgerald/403edf28d5fd358722d2bc36b52f38f1
                                          • Output of /var/log/daemon.log - https://gist.github.com/kismetgerald/8965863047eee26b815dcfcfe4faabae
                                          • Output of /var/log/xensource.log - https://gist.github.com/kismetgerald/4ed62e999d9920d697f06c8e42de9873

                                          For time reference, I started the VM at approximately Dec 12 05:08 - don't recall the precise second. If I can provide other logs, please let me know.

                                          stormiS 1 Reply Last reply Reply Quote 0
                                          • stormiS Offline
                                            stormi Vates 🪐 XCP-ng Team @kagbasi-ngc
                                            last edited by

                                            @kagbasi-ngc I was inviting you to have a look first, but I'll try to give it a look. Still, try to find something relevant in them, it's a good troubleshooting exercise.

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