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

    How to migrate an HPE ROK windows 2019 VM from ESXi to xcp-ng ?

    Scheduled Pinned Locked Moved Migrate to XCP-ng
    hpe rok
    9 Posts 2 Posters 706 Views 2 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
      andyhhlin
      last edited by

      How can I migrate an ESXi VM with the HPE Microsoft Windows 2019 ROK version operating system to an XCP-ng environment?

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

        Hi,

        V2V doesn't work?

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

          Thank you. I will conduct tests after setting up XCP-ng in the client environment. I just wanted to know if anyone else has had this experience?

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

            Hi Sir,
            The XOA had updated to date version , and I got the error message "404 Not Found https://esxi_IP/folder/db/db.vmx?dcPath=folder&dsName=datastore" when migrate from XOA , this site without vcenter . I doubt the parameter dcPath needs to be present , because it's success to download the db.vmx when I browse https://esxi_IP/folder/db/db.vmx?dsName=datastore.
            How to fix it ?

            1 Reply Last reply Reply Quote 0
            • A andyhhlin deleted this topic on
            • olivierlambertO Online
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              404 means the URL cannot be reach from XOA. This error is returned by the HTML destination server, it's not invented or generated by XOA.

              1 Reply Last reply Reply Quote 0
              • A andyhhlin restored this topic on
              • A Offline
                andyhhlin
                last edited by olivierlambert

                Hi,The message as below :

                message: "404 Not Found https://192.168.253.216/folder/web/web.vmx?dcPath=ha-datacenter&dsName=RS2421RP%2B",
                name: "Error",
                stack: "Error: 404 Not Found https://192.168.253.216/folder/web/web.vmx?dcPath=ha-datacenter&dsName=RS2421RP%2B
                    at Esxi.#fetch (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/vmware-explorer/esxi.mjs:106:21)
                    at Esxi.download (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/vmware-explorer/esxi.mjs:139:21)
                    at Esxi.getTransferableVmMetadata (file:///usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/vmware-explorer/esxi.mjs:318:17)
                    at Task.runInside (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:169:22)
                    at Task.run (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:153:20)
                    at MigrateVm.migrationfromEsxi (file:///usr/local/lib/node_modules/xo-server/src/xo-mixins/vmware/index.mjs:187:22)
                    at file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1517:30
                    at Task.runInside (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:169:22)
                    at Task.run (/usr/local/lib/node_modules/xo-server/node_modules/@vates/task/index.js:153:20)
                    at asyncEach.concurrency.concurrency (file:///usr/local/lib/node_modules/xo-server/src/api/vm.mjs:1515:11)"
                }
                

                This infra is just one ESXi 6.7 host without vcenter. The XOA is up to date latest version 5.99. The migration failed for VMs located on storage RS2421RP+, but succeeded for VMs located on another storage datastore1. Could the storage naming be causing this error 404?"
                XoaV2Verror.txt

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

                  It's very likely the name/URL you have provided that is not found on ESXi side

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

                    Could the storage name 'RS2421RP+' be causing this error 404? Should I rename the storage to remove any special characters? or as working on a standalone ESXi host (not under a vCenter), the dcPath might not be required , then how to fix it ?

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

                      That's a possibility. Can you try and report after rename?

                      1 Reply Last reply Reply Quote 0

                      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                      With your input, this post could be even better 💗

                      Register Login
                      • First post
                        Last post