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

    VMware import 404 error

    Scheduled Pinned Locked Moved Xen Orchestra
    27 Posts 4 Posters 1.7k Views 4 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

      🍾 😄

      1 Reply Last reply Reply Quote 0
      • S Offline
        sunwriter @florent
        last edited by

        @florent Thank you! Looking forward to migrating more VM's.

        1 Reply Last reply Reply Quote 1
        • S Offline
          s3b
          last edited by

          Hi,
          i try to migrate vm from VMWARE esxi / vsphere 7.0.3 , i use the XO from source : xo-server 5.110.1 and xo-web 5.112.1 , commit : 5a2c3 .
          VM halted or up same problem : "message": "404 Not Found https://xxxx/folder/baldr1-test_1/baldr1-test.vmx?dc=xxx&dsName=xxx" .
          Any suggestions ? thanks ,
          Seb .

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

            Are you sure about the DC Name? 404 means we can't find the file with the URL we build.

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

              @s3b can you go to the datastore explorer of your esxi, download the baldr1-test.vmx file with your browser and compare the url with the one on 404 ?

              S 1 Reply Last reply Reply Quote 1
              • S Offline
                s3b @florent
                last edited by

                @florent @olivierlambert thanks for your fast reply , the url is different when i try to download the file :
                https://esx4.xxx.local/folder/baldr1-test_1/baldr1-test.vmx?dcPath=ha-datacenter&dsName=import-proxmox&enc=std

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

                  @s3b we made a typo while cleaning code before merging , it is fixed on this branch fix_dcpath and, hopefully, it will be merged soon
                  The PR is here : https://github.com/vatesfr/xen-orchestra/pull/6729/files

                  fbeauchamp opened this pull request in vatesfr/xen-orchestra

                  closed fix(vmware-explorer): fix dcPath parameter #6729

                  S 1 Reply Last reply Reply Quote 1
                  • S Offline
                    s3b @florent
                    last edited by

                    @florent said in VMware import 404 error:

                    fix_dcpath

                    great job @florent 😄 , it works well now, just 2 things I don't run xo as root so I had errors on thick storage with vgchange rights so I used thin storage, and I had a problem with the TLS connection because I use a self-signed certificate for xo-server so I had to add in my systemd orchestra service:
                    Environment=NODE_TLS_REJECT_UNAUTHORIZED=0 and
                    then it worked very well.
                    One thing that confused me a bit is that there was no progress bar on the import page but it is clearly visible on the tasks page. Thank you again for the responsiveness and efficiency.👍

                    florentF 1 Reply Last reply Reply Quote 2
                    • florentF Offline
                      florent Vates 🪐 XO Team @s3b
                      last edited by

                      @s3b the progress bar is on our roadmap , it will be even more needed when handling multiple import in parallel

                      S 2 Replies Last reply Reply Quote 1
                      • S Offline
                        s3b @florent
                        last edited by

                        @florent great ! 👍

                        1 Reply Last reply Reply Quote 0
                        • S Offline
                          s3b @florent
                          last edited by

                          @florent false joy , i have a problem now with another VM , this vm is on same place as baldr1-test , error :

                          message": "404 Not Found https://10.30.xx.xx/folder/undefined?dcPath=Webxxx&dsName=undefined",
                          

                          th Vm is baldr2-test , the dsName should be the same but is undefined .

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

                            @s3b dsName should be the datastore

                            what is the datastore name ? Are the vmx and vmdk files on the same one ? what is fileName of this disk in the vmx file ?

                            S 1 Reply Last reply Reply Quote 0
                            • S Offline
                              s3b @florent
                              last edited by

                              @florent the dsNAme is import-proxmox like for baldr1-test.
                              There is no .vmx so i think i have to delete from inventory the VM and recreate the vm and attach the disk . For now there is just 2 files :
                              [import-proxmox] baldr2-test/baldr2-test-import-ctk.vmdk
                              and
                              [import-proxmox] baldr2-test/baldr2-test-import.vmdk

                              .

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

                                @s3b The vmx file is mandatory for the import, I didn't know that it was not for running on an esxi

                                Recreating it should solve the problem, I will improve our error handling on this case

                                S 1 Reply Last reply Reply Quote 0
                                • S Offline
                                  s3b @florent
                                  last edited by

                                  @florent , delete vm from inventory , recreate the vm , move disk from old folder to new folder and then attach the disk to vm works fine 😄

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

                                    @s3b I am more a XCP guy 😇

                                    S 1 Reply Last reply Reply Quote 0
                                    • S Offline
                                      s3b @florent
                                      last edited by

                                      @florent 👍

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