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

    "Hardware-assisted virtualization is not enabled on this host" even though platform:exp-nested-hvm=true is set

    Scheduled Pinned Locked Moved XCP-ng
    58 Posts 7 Posters 10.5k 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.
    • stormiS Offline
      stormi Vates 🪐 XCP-ng Team
      last edited by

      There is a downgrade feature on our installation ISOs, that can be used to restore the backup made automatically by the installer when upgrading from 8.2.1 to 8.3 beta/rc.

      1. Make sure you have backups.
      2. This is supposed to be used shortly after the upgrade, because the version of the XAPI database which will be restored will be that of the backup. If you made changes which affected the metadata stored by XAPI, you may end up with a mismatch between what's really on your storage and what XAPI believes is the current state of VMs, storage, etc.
      3. The format for storing UEFI variables for UEFI VMs changed in 8.3 and is not backwards compatible. So UEFI VMs won't start anymore. I'm not sure whether the NVRAM store is converted at upgrade time or only the first time the VMs boot (pinging BenjiReis about this). Anyway, any UEFI VM whose NVRAM store was upgraded to the format used in 8.3 won't boot anymore when started back on 8.2.1. There are solutions, involving wiping the NVRAM store (which is enough for most VMs, but Debian, notably, may need fixing the boot loader afterwards, using a Live media).

      Another option is Warm Migrating VMs from the 8.3 pool to a 8.2.1 pool, using Xen Orchestra, but point 3. above still applies to UEFI VMs.

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

        stormi For Debian UEFI boot failures, which I have, if UEFI boots to a shell, you can load GRUB quickly from the shell and boot Debian then fix it from the OS (without booting an ISO).

        From the UEFI shell use the command: FS0:\EFI\debian\grubx64.efi

        It does not fix anything but lets you start Debian manually.

        You can also copy that command into /boot/efi/startup.nsh or use GRUB to install the standard UEFI boot files that XCP can use for the next boot.

        1 Reply Last reply Reply Quote 1
        • abudefA Offline
          abudef
          last edited by

          To pass the time during a long wait 🙂

          Nested Virtualization (X86) Part I - George Dunlap, Xen Server:
          https://www.youtube.com/watch?v=8jKGYY1Bi_o

          Nested Virtualization (X86) Part II - George Dunlap, Xen Server:
          https://www.youtube.com/watch?v=3MxWvVTmY1s

          X 1 Reply Last reply Reply Quote 0
          • X Offline
            XCP-ng-JustGreat @abudef
            last edited by

            abudef Thank you for providing these links to George Dunlap's Xen Summit nested virtualization talk. It was very informative and also demonstrates a strong commitment to bringing NV to Xen Hypervisor and its derivatives. Particularly in light of Broadcom's acquisition of VMware and the resulting customer exodus, adopting XCP-ng and Vates looks to be an increasingly smart play. I will cross-post the provided links to the big NV thread on here.

            1 Reply Last reply Reply Quote 0
            • X XCP-ng-JustGreat referenced this topic on
            • abudefA Offline
              abudef
              last edited by

              As I'm waiting there, I'm wondering why is implementing nested virtualization so difficult and lengthy in the case of Xen? VMware, H-V, VirtualBox, KVM - they all support it, so I wonder what the reasons might be that Xen still doesn't... 🤔

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

                How many dev dedicated to this task on VMware or HyperV? That's the explanation, it's a question of resources. We are doing our best at Vates to do more and more Xen dev, but ramping up takes time;

                abudefA 1 Reply Last reply Reply Quote 0
                • abudefA Offline
                  abudef @olivierlambert
                  last edited by

                  olivierlambert Well, I guess that too, but I meant something else, whether it might be somehow related to the architecture of individual hypervisors in general, whether simply the way Xen is built is a complication for implementing nested virtualization.

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

                    No especially. Nested is a tricky problem that requires a fair amount of resources to be done correctly, regardless the hypervisor.

                    abudefA 1 Reply Last reply Reply Quote 0
                    • abudefA Offline
                      abudef @olivierlambert
                      last edited by

                      olivierlambert So there are basically no dramatic architectural differences in the individual hypervisors in this regard?

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

                        There is some diff, but not that much between HyperV, ESXi and Xen. However, it's big enough to require a lot of effort to get nested working correctly, one small mistake and your VM is dead.

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