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

    VMware migration tool: we need your feedback!

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    298 Posts 33 Posters 160.8k 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.
    • R
      Riven
      last edited by

      Any plans to check how many vNICs there are and allow us to map each one correctly.

      All of our vmware VMs have multiple vNICs and are in different port-groups.

      Its not a major hassle to change them post-migration - just a nice-to-have.

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

        You mean to map each VIF to each Network of your choice?

        R 1 Reply Last reply Reply Quote 0
        • R
          Riven @olivierlambert
          last edited by

          @olivierlambert - Yes, so when we do a V2V there is only 1 VIF listed to put the migrated VIFs in to, even if the VM has 5 VIFs

          Is it possible to query each vmx and allow us to select a 'network' for each VIF that it has?

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

            Question for @florent

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

              @Riven said in VMware migration tool: we need your feedback!:

              @olivierlambert - Yes, so when we do a V2V there is only 1 VIF listed to put the migrated VIFs in to, even if the VM has 5 VIFs

              Is it possible to query each vmx and allow us to select a 'network' for each VIF that it has?

              not for now

              1 Reply Last reply Reply Quote 0
              • R
                rtjdamen @olivierlambert
                last edited by

                @olivierlambert I wanted to comment on this topic, we have migrated around 450 vms in 3 months using this feature, it really was a game changer and without it we were never able to make the step to XCP-NG. during the migration process we saw the feature being improved, overall speed and reliability were great. Compliments on this feature and i think it will help a lot of future customers migrating to XCP-NG.

                1 Reply Last reply Reply Quote 1
                • T
                  tcp_len
                  last edited by olivierlambert

                  Migration fails, here is the raw log;

                  {
                    "id": "0lxdi3kqv",
                    "properties": {
                      "name": "importing vms 14",
                      "userId": "9045a9e7-f9b2-44fd-81e9-02c1ea88b37b",
                      "total": 1,
                      "done": 0,
                      "progress": 0
                    },
                    "start": 1718297723335,
                    "status": "interrupted",
                    "updatedAt": 1718298405138,
                    "tasks": [
                      {
                        "id": "c3bsox2ydxp",
                        "properties": {
                          "name": "importing vm 14"
                        },
                        "start": 1718297723339,
                        "status": "pending",
                        "tasks": [
                          {
                            "id": "lvtzb0k3sc9",
                            "properties": {
                              "name": "connecting to 10.x.x.12"
                            },
                            "start": 1718297723341,
                            "status": "success",
                            "end": 1718297723756,
                            "result": {
                              "_events": {},
                              "_eventsCount": 0
                            }
                          },
                          {
                            "id": "n6tsha4ebu",
                            "properties": {
                              "name": "get metadata of 14"
                            },
                            "start": 1718297723756,
                            "status": "pending"
                          }
                        ]
                      }
                    ]
                  }
                  
                  DanpD 1 Reply Last reply Reply Quote 0
                  • DanpD
                    Danp Vates 🪐 Pro Support Team @tcp_len
                    last edited by

                    @tcp_len We recently released a Vmware migration checklist that you can view here -- https://help.vates.tech/kb/en-us/37/133

                    Frankly, that log doesn't give us much to go on so you will need to provide more details if you want further assistance, ie:

                    • ESXi version
                    • Type of datastore
                    • Version of XOA or current commit if using XO from sources
                    • XCP host version; fully patched?
                    • Warm or cold migration?
                    • Does the VM have any snapshots?
                    • etc
                    T 1 Reply Last reply Reply Quote 1
                    • T
                      tcp_len @Danp
                      last edited by

                      @Danp

                      1. ESXI version 6.5
                      2. Data Store - VMFS5
                      3. XOA f7220852-f0c4-4319-874d-f45b20ce911b-image.png
                      4. XCP - Welcome To XCP-Ng 8.2.1
                      5. Cold Migraration
                      6. No Snapshots

                      From the checklist posted, I should uninstall the Vmware tools before I attempt migration as well as run #yum update on the XCP host.

                      1 Reply Last reply Reply Quote 0
                      • A
                        andyh
                        last edited by andyh

                        Could anyone explain what we should be setting for 'Original Template' in the Import VM screen ?

                        Selecting a template appears to create a new empty VM with no apparent attempt to perform the migration.

                        Capture.JPG

                        Using Xen Orchestra from Sources (commit 636c8) against an ESXi 5.1 host, via an nginx reverse proxy (to work around legacy ciphers).

                        DanpD 1 Reply Last reply Reply Quote 0
                        • DanpD
                          Danp Vates 🪐 Pro Support Team @andyh
                          last edited by

                          @andyh This is intended for you to select the template that best represents the source VM. If you are migrating a Debian VM, then pick the Debian option that best matches the source VM.

                          I'm unsure about compatibility with an ESXi version that one. Do you get any error messages or have you checked the XO logs?

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

                            @Danp No error messages and nothing in either Settings - Logs or via the CLI (journalctl)

                            It could be due to the age of the ESXi host or the fact I am using a reverse SSL proxy to cope with the legacy ciphers.

                            I'll look to export the VMs as OVA's and import that way.

                            A 1 Reply Last reply Reply Quote 0
                            • P
                              probain
                              last edited by

                              The address field doesn't trim trailing whitespace. Not a big deal breaker. But it did take me a couple of minutes until I found out why my copy/paste address was giving me errors

                              1 Reply Last reply Reply Quote 0
                              • A
                                andyh @andyh
                                last edited by

                                @danp
                                I was having a similar issue with OVA imports (using Chrome), tried a different browser (Firefox) and was able to import the OVA.

                                Went back to the reverse proxy and tried in Firefox, I currently have two VMs importing directly from VMware 😀

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