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.
    • abudefA Online
      abudef @abudef
      last edited by abudef

      But I have a suspicion that it hasn't worked since the last or second to last batch of updates for XCP-ng, that it worked before.

      I can confirm this; on another lab I updated XCP-ng with the last fifty or so updates from the end of April, and nested XCP-ng also appears to have virtualization support not enabled...

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

        You mean 8.2 or 8.3?

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

          I use version 8.3.

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

            That might be interesting to check if it works with the same context on 8.2

            1 Reply Last reply Reply Quote 0
            • abudefA Online
              abudef
              last edited by

              Nested virtualization seems to work correctly in version 8.2.1 with the latest updates (native host).

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

                Nested virtualization seems to work correctly in version 8.2.1 with the latest updates (native host).

                On the contrary; the problem is related to virtualized XCP-ng version 8.3 with the latest updates, not to the native host.

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

                  Nested virtualization seems to work correctly in version 8.2.1 with the latest updates (native host).

                  On the contrary; the problem is related to virtualized XCP-ng version 8.3 with the latest updates, not to the native host.

                  The combination (8.3latest(8.x)) does not work either. Nested virtualization simply doesn't work if 8.3 is either a native host, a virtualized host, or both.

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

                    And 8.3 with Xen 4.13 instead of 4.17?

                    1 Reply Last reply Reply Quote 0
                    • abudefA Online
                      abudef
                      last edited by

                      Well, it seems that the problem is caused by Xen 4.17...

                      1 Reply Last reply Reply Quote 0
                      • abudefA Online
                        abudef
                        last edited by

                        I temporarily moved the entire XCP-ng lab to ESXi. I need a few different hosts for scenario testing, migration and backup testing, XO proxies testing etc. and of course I can't dedicate a hw server for each of them in the lab. Please let me know when the nested virtualization support will be operational again on version 8.3.

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

                          Well, you are the first to report this regression, so we'll need time to reproduce and investigate.

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

                            Add stormi so we create a card internally.

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

                              Noted! If this happens on our hardware too, this will be very annoying for our own virtual XCP-ng that we use all the time for development and testing.

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

                                olivierlambert Thank you very much for the impeccable support and fast communication 👍

                                I tested again today and the problem is always on the host side, regardless of the type of guest. This corrects some of my hasty information above.

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

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

                                  I tested again today and the problem is always on the host side, regardless of the type of guest. This corrects some of my hasty information above.

                                  What do you mean? Can you give examples?

                                  abudefA 1 Reply Last reply Reply Quote 0
                                  • abudefA Online
                                    abudef @stormi
                                    last edited by

                                    stormi If the host is on version 8.3 with Xen 4.17, nested virtualization does not work on any guest. If version 8.3 with Xen 4.17 is on a guest, but the host is running version 8.2.1 or an out-of-date 8.3 (Xen 4.13), it doesn't matter and nested guest virtualization works.

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

                                      abudef In the second case, do you mean there's:

                                      8.2.1 host running a nested 8.3 (Xen 4.17) VM running itself a Nested XCP-ng? (so nested inside nested)

                                      abudefA 1 Reply Last reply Reply Quote 0
                                      • abudefA Online
                                        abudef @stormi
                                        last edited by

                                        stormi That's not quite what I meant. The point is that if the host is 8.3/4.17, then virtualization is not working on its guest and therefore no other nested guest can be started on this guest. And actually, yes, if 8.3/4.17 appears somewhere in the cascade of nested hosts, then nested virtualization will no longer work on its guest.

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

                                          abudef Can you try this on a shutdown VM:

                                          1. Disable nested from the VM/Advanced tab
                                          2. xe vm-param-set platform:nested_virt=true uuid=<VM UUID>
                                          3. Start the VM
                                          abudefA 1 Reply Last reply Reply Quote 0
                                          • olivierlambertO Online
                                            olivierlambert Vates 🪐 Co-Founder CEO
                                            last edited by

                                            It seems we also need to modify some other bits, stand by.

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