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

    V2V - Stops at 99%

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    30 Posts 8 Posters 1.2k 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.
    • 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 )

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

                    @florent Oh shoot! So only during the actual vmware import? I guess they're gone now then 😞
                    Sorry I couldn't be of more help!

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

                      @nikade I believe that you can still find the entries in the journalctl output.

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

                        @Danp Yeah? How?
                        Let me know if you want me to grab some logs for you guys, if it's still interesting.

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