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

    XOA 5.110 - Import from VMWare shows "vddk:" without ok or checkmark status

    Scheduled Pinned Locked Moved Xen Orchestra
    17 Posts 4 Posters 411 Views 3 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.
    • A Offline
      Andrw0830 @Danp
      last edited by

      @Danp It's ESXi 6.7.0 Update 3. I do notice a speed improvement when importing the VMs when they are powered off, just the disks won't import when the VM is on.

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

        @Andrw0830 Did you take a snapshot prior attempting the warm migration?

        A 1 Reply Last reply Reply Quote 0
        • A Offline
          Andrw0830 @Danp
          last edited by

          @Danp Thanks for the suggestion as that was it.

          Since warm migration wouldn't work before, I've completely forgot a snapshot was needed before trying the import.

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

            Is it clear in our doc @Danp to make a snapshot on the VM we want to live migrate, and ourselves? (ie it's not done via the V2V automatically?)

            M DanpD 2 Replies Last reply Reply Quote 0
            • M Offline
              MajorP93 @olivierlambert
              last edited by MajorP93

              @olivierlambert said in XOA 5.110 - Import from VMWare shows "vddk:" without ok or checkmark status:

              Is it clear in our doc @Danp to make a snapshot on the VM we want to live migrate, and ourselves? (ie it's not done via the V2V automatically?)

              I was also performing tests with the new V2V VDDK feature and noticed that it is required to manually create snapshots on VMWare side.

              I was wondering: is there any particular reason that V2V is not creating the snapshots automatically?

              I think if it would create the snapshots automatically it would be a great improvement and make the feature more intuitive to use.

              Another thing that I noticed:
              after successful migration by V2V VDDK tool the resulting VM on XCP-ng side has 2 snapshots:
              48d6a3ba-154d-422c-a5d7-7caf7fe5a69c-grafik.png
              Are they required? Can they be deleted automatically by V2V feature?

              In the old V2V implementation (without VDDK) I did not have these snapshots after successful migration.

              Anyways: thank you so much for this great product, I am currently preparing the migration of our internal infrastructure from VMWare to the Vates stack and am feeling great so far about the product and the community!

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

                @MajorP93 said in XOA 5.110 - Import from VMWare shows "vddk:" without ok or checkmark status:

                I was wondering: is there any particular reason that V2V is not creating the snapshots automatically?

                I agree, question for @florent

                edit: and about the snapshots on destination too, I wonder if it's normal 🙂

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

                  @olivierlambert said in XOA 5.110 - Import from VMWare shows "vddk:" without ok or checkmark status:

                  Is it clear in our doc @Danp to make a snapshot on the VM we want to live migrate, and ourselves? (ie it's not done via the V2V automatically?)

                  I believe so, although I know that @florent stated that they need to be updated.

                  @MajorP93 said in XOA 5.110 - Import from VMWare shows "vddk:" without ok or checkmark status:

                  after successful migration by V2V VDDK tool the resulting VM on XCP-ng side has 2 snapshots:
                  Are they required? Can they be deleted automatically by V2V feature?

                  IDK if this will be more automated in the future, but you can easily remove these snapshots following the V2V migration.

                  1 Reply Last reply Reply Quote 0
                  • A Offline
                    Andrw0830
                    last edited by Andrw0830

                    Ok so wanted to post an update.

                    With a snapshot created, importing from VMWare will allow the snapshot disks to be imported, but once that's done, the source VM never shuts down and the import process just hangs (have to eventually just stop the task from XOA). Within ESXI, the tasks shows whenever XOA reached out with the last task name of "Nfc Get Vm Files" listed (see image). Is there a reason why creating the VM and inputting the snapshot disks work, but nothing happens afterwards? I've even tried to re-create a Debian version of my XOA just in case maybe building the nbdkit and libnbd manually on my Ubuntu XOA caused the issue, but the Debian version has the same issue including the vddk not showing a green checkmark with an ok status at the top. Someone with a working import, can they confirm if the VDDK is supposed to show an 'ok' status or is it fine with the blank status after the ':'? I've downloaded the "VMware-vix-disklib-9.0.0.0.24742305.x86_64.tar.gz" and dragged it into the XOA window and clicked on the button to import it so that should work.

                    XOA-Import-From-VMWare-Recent-Tasks.jpg

                    M 1 Reply Last reply Reply Quote 0
                    • M Offline
                      MajorP93 @Andrw0830
                      last edited by MajorP93

                      @Andrw0830 For me V2V also shows a blank status for VDDK and I am using version 9.0 of the .tar.gz aswell.
                      Import of VMs from ESXi works fine and VM get’s shut down on the ESXi side automatically. I do have the little quirks mentioned before though.

                      A 1 Reply Last reply Reply Quote 0
                      • A Offline
                        Andrw0830 @MajorP93
                        last edited by Andrw0830

                        @MajorP93

                        @MajorP93 said in XOA 5.110 - Import from VMWare shows "vddk:" without ok or checkmark status:

                        @Andrw0830 For me V2V also shows a blank status for VDDK and I am using version 9.0 of the .tar.gz aswell.
                        Import of VMs from ESXi works fine and VM get’s shut down on the ESXi side automatically. I do have the little quirks mentioned before though.

                        Thanks for the information. Do you use ESXi Free or paid license? Just wondering if it's paid then that might be why as I've heard before that ESXi free starting with 6.7, didn't allow warm migration and I remember trying to use Starwind's V2V converter a year ago and it wouldn't work with ESXi 6.7 with the free license installed. That was to import an image into VMWare not to export one so not sure if the license limitation would still effect that.

                        M 1 Reply Last reply Reply Quote 0
                        • M Offline
                          MajorP93 @Andrw0830
                          last edited by

                          @Andrw0830 I am using paid version of ESXi / vSphere.
                          The free version of ESXi has so many limitations that I consider it pretty much unusable / only usable for very limited basic tests.
                          It would not suprise me if your issue is due to the license limitations within ESXi.

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