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

    Issues with warm migration from ESXi 8.0.2

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    10 Posts 4 Posters 806 Views
    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
      kebabdjur
      last edited by

      Hi!

      We're having issues migrating from ESXi 8.0.2 getting the following error:

      Can't import delta of a running VM without its parent vdi

      We're using XO built from sources, latest commit. We also tried using XOA and this instead gave the following error:

      Cannot destructure property 'vdi' of 'vhds[userdevice]' as it is undefined.

      The migration tool just throws the error and then shuts down the target VM on the ESXi host.

      We've tried the following things:

      • Migrate to local storage
      • Migrate to NFS storage
      • Move VM:s to a different storage in ESXi (Local, NFS and FC-connected SAN)
      • VM:s created from template and fresh installs
      • VM:s with and without VMWare Tools installed
      • VM:s with varying levels of "Hardware compatibility"
      • Connecting the migration tool to vcenter
      • Connecting the migration tool to esxi host

      We need to be able to do warm migrations as we have a bunch of customer servers that "can't" be shutdown for any extended period of time.

      Any help would be greatly appreciated!

      If it helps I've attached a copy of the full error log from XO.
      migration-error.txt

      D 2 Replies Last reply Reply Quote 0
      • D
        DustinB @kebabdjur
        last edited by

        @kebabdjur what level of licensing is installed on for each ESXi system? Is this vSphere or straight ESXi?

        • vSphere is a work in progress and doesn't currently work
        • You must have licensing (beyond free and essentials) to perform a warm migration
        • You must perform this on a per host basis (not vSphere)
        1 Reply Last reply Reply Quote 0
        • D
          DustinB @kebabdjur
          last edited by

          @kebabdjur in the logs "connecting to VCENTER-SERVER"

          Assuming you're trying to bulk migrate from vSphere vCenter, isn't supported and is a work in progress.

          Try migrating from a individual ESXi host, assuming again you're licensed for it.

          K 1 Reply Last reply Reply Quote 0
          • K
            kebabdjur @DustinB
            last edited by

            @DustinB

            Hi!

            Thanks for quick reply!

            As stated in orginal post, the issue comes regardless if we're connecting to VCenter or straight to the ESXi host(s), the sample error just happened to be from one of the attempts to the vcenter server.

            The machines are licensed with vSphere 8 Enterprise Plus via VSPP.

            We've also attempted from free versions of ESXi 7 and ESXi8, but like you said, it's not working from free license versions since they lack some features such as power down vm.

            Attaching log from attempt when connecting straight to an ESXi-host.

            migration-error2.txt

            D 1 Reply Last reply Reply Quote 0
            • D
              DustinB @kebabdjur
              last edited by

              @kebabdjur does this VM have any snapshots on ESXi?

              That may cause issues.

              K 1 Reply Last reply Reply Quote 0
              • K
                kebabdjur @DustinB
                last edited by

                @DustinB

                No snapshots, issue even comes up if we create a brand new server from scratch.

                Also tried updating to latest commit but made no difference.

                Offline migration works like a charm and it finds the files as expected, but it would be great if we could get warm migration working. Those 7 weeks until April 30th feel very short right now.

                D 1 Reply Last reply Reply Quote 0
                • D
                  DustinB @kebabdjur
                  last edited by

                  @kebabdjur What is vSphere/ESXi reporting regarding this operation? Any logs they can provide?

                  1 Reply Last reply Reply Quote 0
                  • J
                    john.c
                    last edited by john.c

                    @kebabdjur What VMFS is your ESXi 8.0.2 reporting on your hosts for the datastore(s)?

                    If it is VMFS5 or lower then currently it won't be holding up your warm migration. However if it is reporting VMFS6 or higher then it will hold up (prevent) your warm migration as this version isn't currently supported.

                    The Vates employee @Danp is currently handling another warm migration issue on an earlier version of ESXi than your one (version 7.0.0). The user with the issue, have the necessary features in the VMware ESXi licenses which they are using on their hosts. However unfortunately their datastore(s) are formatted for VMFS6 rather than the currently supported VMFS5 or lower. Support for VMFS6 is being worked on but Danp doesn't know when it will be released.

                    Also there may be other issues in effect (possibly different APIs), which Vate's developers are investigating. So if there's different APIs in VMware ESXi version 7.0.0, then there's a possibility for it to also be present in VMware ESXi version 8.0.0.

                    https://xcp-ng.org/forum/post/73330

                    K 1 Reply Last reply Reply Quote 0
                    • K
                      kebabdjur @john.c
                      last edited by

                      @john-c @DustinB

                      Hi!

                      We have now tried changing one of the storages to VMFS5 but the issue persists. Same goes for if the VM is on NFS 4.1.

                      I've managed to get some logs from the ESXi host, hoping any of them will be of use. Like before I've replaced IP:s and VLAN names.

                      cfw12-vm-boot-log.txt
                      cfw12-vm-tansferattempt-esxi-log.txt
                      cfw12-xoappliance-vmfs5-error.txt
                      cfw12-xosrc01-vmfs5-error.txt
                      esx-hostd-log.txt

                      Like the other guy said, anything we can do to help please let us know. If that means access, testing, moving to any of the paid plans, we just want this working.

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

                        Adding @florent in the loop

                        1 Reply Last reply Reply Quote 0
                        • J john.c referenced this topic on
                        • First post
                          Last post