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

    VMware migration tool: we need your feedback!

    News
    27
    273
    8.0k
    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
      olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
      last edited by

      In VMware, can you easily tag a VM disk?

      planedropP 1 Reply Last reply Reply Quote 0
      • planedropP
        planedrop @olivierlambert
        last edited by

        @olivierlambert I don't think there are tags for them, per-se but you can rename a VMDK file to whatever you want within vCenter. Maybe just looking at the name of the VMDK files and allowing someone to enter ones to exclude would work?

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

          Sure, I just need to know what's the easiest way to do this in VMware, since I don't know it at all 🙂

          planedropP 1 Reply Last reply Reply Quote 0
          • planedropP
            planedrop @olivierlambert
            last edited by

            @olivierlambert Totally understand.

            I think going based on the name of the disk would be the best option.

            For example, on a test VM I have, the disks all show up like this:
            b6cb6358-8dc2-4961-ba18-e6e3ecdd4eec-image.png

            And I can rename them if need be.

            Does the current V2V tool just look for .vmdk files and then migrate those?

            I guess what I'm thinking is like something that says "exclude the below disks" and then has a list system where you can enter the disk name as it shows up here in ESXi so that it ignores those disks?

            I'm not sure how complex this would be though so just throwing out suggestions haha!

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

              I would prefer something that's not configured in XO but a convention on the VMware side so it can scale during one import on tons of VMs

              planedropP 1 Reply Last reply Reply Quote 0
              • planedropP
                planedrop @olivierlambert
                last edited by

                @olivierlambert I see, this makes sense.

                Maybe a naming convention can be used and then users can rename their VMDK files to something specific that is ignored?

                Like say you have Ubuntu1.vmdk, Ubuntu2.vmdk, Ubuntu3.vmdk and someone only wants Ubuntu1.vmdk, they could rename Ubuntu2 and 3 ones to ignore1.vmdk and ignore2.vmdk?

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

                  Frankly IDK, and I'd like more input from VMware users to make a decision based on multiple opinions 🙂

                  planedropP 1 Reply Last reply Reply Quote 0
                  • planedropP
                    planedrop @olivierlambert
                    last edited by

                    @olivierlambert I agree, would be good to hear from more people. We only run a handful of VMs on VMware so I may not be the best person to give detailed feedback.

                    1 Reply Last reply Reply Quote 0
                    • chrispro-21C
                      chrispro-21 @brezlord
                      last edited by

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

                      TypeError

                      I got something similar on the latest build of XO.
                      System: ESXi 6.7.0 Update 3 (Build 15160138)

                      vm.importFromEsxi
                      {
                        "host": "10.20.0.105",
                        "network": "1816a2e5-562a-4559-531d-6b59f8ec1a5c",
                        "password": "* obfuscated *",
                        "sr": "eb23cb22-5b8c-9641-b801-c86397e05520",
                        "sslVerify": false,
                        "stopSource": true,
                        "thin": false,
                        "user": "root",
                        "vm": "9"
                      }
                      {
                        "message": "Cannot read properties of undefined (reading 'stream')",
                        "name": "TypeError",
                        "stack": "TypeError: Cannot read properties of undefined (reading 'stream')
                          at file:///home/node/xen-orchestra/packages/xo-server/src/xo-mixins/migrate-vm.mjs:272:30
                          at Task.runInside (/home/node/xen-orchestra/@vates/task/index.js:158:22)
                          at Task.run (/home/node/xen-orchestra/@vates/task/index.js:137:20)"
                      }
                      
                      florentF 1 Reply Last reply Reply Quote 0
                      • florentF
                        florent Vates 🪐 XO Team 🔭 @chrispro-21
                        last edited by

                        @chrispro-21 we're not able to import VM with snapshots from esxi 6.5+ , for now

                        At least the next release will be able to ignore them or give a meaningfull error, if we have not finished the implementation of sesparse reading ( the disk snapshot format for esxi 6.5+)

                        A 1 Reply Last reply Reply Quote 0
                        • A
                          alexredston @florent
                          last edited by olivierlambert

                          Hi @florent I'm getting the same on ESXi 6.7 - have tried migrating the disk storage within VMWare first to see if it updated. Looking forwards to testing this new feature as soon as disk format sorted - in the mean time will look for a workaround.

                          vm.importFromEsxi
                          {
                            "host": "172.29.49.11",
                            "network": "b4d861c9-a735-b21c-6f58-655911cf8fb2",
                            "password": "* obfuscated *",
                            "sr": "1216d3f2-a60d-e68b-ea93-0b1b594a53cb",
                            "sslVerify": true,
                            "stopSource": false,
                            "thin": false,
                            "user": "administrator@blue.local",
                            "vm": "vm-4292"
                          }
                          {
                            "message": "sesparse Vmdk reading is not functionnal yet gbr-stf-blue-dc/gbr-stf-blue-dc-000001-sesparse.vmdk",
                            "name": "Error",
                            "stack": "Error: sesparse Vmdk reading is not functionnal yet gbr-stf-blue-dc/gbr-stf-blue-dc-000001-sesparse.vmdk
                              at openDeltaVmdkasVhd (file:///opt/xo/xo-builds/xen-orchestra-202303171405/@xen-orchestra/vmware-explorer/openDeltaVmdkAsVhd.mjs:7:11)
                              at file:///opt/xo/xo-builds/xen-orchestra-202303171405/packages/xo-server/src/xo-mixins/migrate-vm.mjs:267:27
                              at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202303171405/@vates/task/index.js:158:22)
                              at Task.run (/opt/xo/xo-builds/xen-orchestra-202303171405/@vates/task/index.js:137:20)"
                          }
                          
                          1 Reply Last reply Reply Quote 0
                          • olivierlambertO
                            olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                            last edited by

                            @alexredston you can workaround it by stopping the VM and that will work 🙂

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

                              @olivierlambert Thanks - already underway.

                              3 hours elapsed, 3 hours to go 80GB thick provisioned primary domain controller, unfortunately it was on a slow network card 1G, averaging about 42 MB per second during the transfer. Will try the next one on 10G and will see what the speed is like.

                              RAID 1 on old server to RAID10 ADM triple mirrored and striped.

                              R 1 Reply Last reply Reply Quote 0
                              • olivierlambertO
                                olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                                last edited by

                                Select thin on the XO V2V tool, that might be faster in the end. Patience is key 🙂

                                A 1 Reply Last reply Reply Quote 0
                                • R
                                  rochemike @alexredston
                                  last edited by

                                  @alexredston I don't know what "old server" means to you, but 42MB/se could be ~320Mbps which would be about the maximum on a SCSI bus. If I'm right and it's Ultra2 SCSI, there's little that you'll be able to speed up by increasing available network bandwidth.

                                  https://en.wikipedia.org/wiki/Parallel_SCSI#:~:text=At 10 MHz with a,rate of 640 MB%2Fs.

                                  Mike

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

                                    @rochemike SSD - so should go a little faster.

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

                                      @olivierlambert Trying another VM now - Linux this time, on ESXi it is 500GB thin provisioned with about 100GB in use - transfer died at around 20 hours + on thick, seemed to get nowhere on thin, but I'm not sure where to get error message to see what happened - just going to try again now after bringing XO up to date with master. Will try thin.

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

                                        @rochemike it did get there in the end - one down 28 to go

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

                                          \o/

                                          Next release will have multi-VM import 🙂

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

                                            @olivierlambert yes
                                            and the multi import will runVM two by two

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