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

    V2V - Stops at 99%

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    27 Posts 8 Posters 1.1k 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.
    • nikadeN Offline
      nikade Top contributor
      last edited by nikade

      I'm seeing something similar, not sure if its the same issue, but mine stops at 95% and just hangs there:

      [12:18 sto-xcp1 ~]# xe task-list
      uuid ( RO) : c1056d36-b195-056a-4121-e82d7fc851fb
      name-label ( RO): [XO] Importing content into VDI [ESXI]DEBIAN 12 fiona.iextreme.org-flat.vmdk on SR Local storage
      name-description ( RO):
      status ( RO): pending
      progress ( RO): 0.950

      The nbdkit debug-log can be found here:
      https://mirror2.iextreme.org/temp/stderr

      Edit: some additional info

      Xen Orchestra, commit 1640a
      Master, commit 1640a

      1 Reply Last reply Reply Quote 0
      • V Offline
        Vanny 3rd party vendor
        last edited by

        Did you solve the problem?

        If you are looking for another migration solution, you can also try Vinchin Backup & Recovery, which migrates VMware to XCP-ng by restoring VMware VM to XCP-ng host.

        florentF 1 Reply Last reply Reply Quote 0
        • florentF Offline
          florent Vates 🪐 XO Team @Vanny
          last edited by florent

          @Vanny we are still working on the issue which seems to be partly due to the new V2V code, and partly to qcow2 supports.

          Note that the v2v tool is a convenient tool, but there are a lot of good tools out there, and some may better fit your needs after testing.

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

            FYI, Vanny is a representative from Vinchin 😉

            1 Reply Last reply Reply Quote 1
            • nikadeN Offline
              nikade Top contributor
              last edited by

              Got most of them working, except 2 of the bigger ones.

              florentF 1 Reply Last reply Reply Quote 1
              • florentF Offline
                florent Vates 🪐 XO Team @nikade
                last edited by

                @nikade we'll got them ( on monday )
                could you remind me the exact size of the disks ? to check for an alignment issue

                nikadeN 1 Reply Last reply Reply Quote 0
                • nikadeN Offline
                  nikade Top contributor @florent
                  last edited by nikade

                  @florent it was 2 windows vm's, both with 100gb but not even 50% filled.

                  Edit: All Linux VM's worked tho.

                  florentF 1 Reply Last reply Reply Quote 1
                  • florentF Offline
                    florent Vates 🪐 XO Team @nikade
                    last edited by

                    @nikade TBF I was expecting from multi TB VM imported through qcow2

                    nikadeN 1 Reply Last reply Reply Quote 0
                    • nikadeN Offline
                      nikade Top contributor @florent
                      last edited by

                      @florent Sorry to dissapoint you 😉
                      Can you remind me where the vmware-import logs are stored on the XO machine? I can see if I still have them for you, it could be an alignment issue.

                      florentF 1 Reply Last reply Reply Quote 0
                      • florentF Offline
                        florent Vates 🪐 XO Team @nikade
                        last edited by

                        @nikade this is a good news : that will be easier to test and debug.

                        during an import you should have a nbdkit logs of ${diskPath} are in ${tmpDir} where diskPath is the datastore/diskname.vmdk and tmpDir is something like /tmp/xo-serverXXXX

                        the logs are in a stderr file in $tmpDir ( they can be quite big )

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