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

    Compatibility Issue Migrating VMs from ESXi 8.03 to XCP-ng 8.3

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    10 Posts 4 Posters 279 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.
    • T Offline
      taghjichte
      last edited by

      Hello

      I have a server running on ESXi 8.03 that hosts two VMs (Windows Server and Linux Ubuntu). Additionally, I have another server running on XCP-ng 8.3.

      I need to migrate the VMs from ESXi to XCP-ng.
      I attempted to export the VMs as OVA files from ESXi and import them into XCP-ng by usine XCP-ng Center, but I encountered an error during the process.

      544363ec-3283-4bd0-a6c2-c20be916840a-Capture d'écran 2025-01-17 115140.png

      After some research, I found that the issue might be related to compatibility with VMDK files and VMware Virtual Hardware version [vmx-21].

      Below is the error log:

      Log file.txt

      Could you provide guidance on how to resolve this compatibility issue or suggest an alternative migration method?

      Thank you,

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

        @taghjichte is there a reason why u do not use the buildin feature of xoa for migration? For us this worked on all our vms.

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

          Hi,

          XCP-ng Center is only community supported (you can open issues in the repo: https://github.com/xcp-ng/xenadmin) but there's no active maintainer in here. As suggested, you should try with Xen Orchestra.

          1 Reply Last reply Reply Quote 0
          • T Offline
            taghjichte
            last edited by

            Hello,

            Thank you for your suggestion to use Xen Orchestra. However, I have the following constraints with my current architecture:

            I have installed a server with XCP-ng and Xen Orchestra in the main datacenter.
            The other servers I want to migrate are located on a remote site connected via a VPN.
            Unfortunately, the VPN connection is unstable and very slow, which makes migration through Xen Orchestra impractical in this scenario.
            This is why I opted for a manual migration process: exporting the VMs as OVA files from ESXi and importing them into XCP-ng using XCP-ng Center.

            8436cce6-6296-4c7e-948e-1581a5c5906f-image.png

            To be transparent, I am new to XCP-ng, and this is my first project with the platform. Could you provide additional guidance on resolving the compatibility issue with the VMDK files or suggest any specific configurations to facilitate this manual migration process?

            Thank you for your support!

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

              @taghjichte Try importing the OVA files using XOA (Import > VM).

              T 1 Reply Last reply Reply Quote 0
              • T Offline
                taghjichte @Danp
                last edited by

                Hi @Danp

                Thank you for your reply. When you mention importing the OVA files using XOA, are you referring to XO Lite or something else?

                I am new to XCP-ng and still learning the platform's terminology and features. Could you please provide more details about the specific tool or method you recommend for this process? Any additional guidance or instructions would be greatly appreciated!

                Thank you for your support!

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

                  @taghjichte XOA stands for xen orchestra appliance (@olivierlambert correct me if i am wrong), this is different then xo lite. U can deploy a xoa instance from xo lite, it gives u a 30 days free trail version. Left u have the import function and choose for vm, there u are able to import an ova file.

                  T 1 Reply Last reply Reply Quote 0
                  • T Offline
                    taghjichte @rtjdamen
                    last edited by

                    @rtjdamen Thank you for the clarification and guidance! I have a question: can I install XOA on each site in my architecture and use it to perform migrations locally? Would this approach work in my scenario where the VPN connection between sites is slow and unstable?

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

                      @taghjichte not shure if i understand correctly but xoa is not intended to run on vmware, not shure if it does but u need to test, i think u can try connecting to your vmware endpoint by using xoa on you xcp side. Unstable will be a problem i guess, slow is just making it to take more time, however these two combined might be a problem, also it depens on how bug your vm is. U can give it a try off course. I think export it on vcenter to ova manual copy and import on xoa side will be more safe and reliable.

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

                        You can deploy multiple XOA if it's your question, one to export in OVA, one to import the OVA.

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