VMware migration tool: we need your feedback!

florent

@ismo-conguairta said in VMware migration tool: we need your feedback!:

I have two different behaviour on two different XO instances. Each XO instance refers to a different pool (different hosts, same xcp-ng version). In both the instances I try to connect to the same Private Virtual Datacenter based on VMware/vSphere at OVH.

In the first one I get the following error message by using the web UI: "invalid parameters" (take a look at this logfile 2023-02-28T19_25_21.933Z - XO.txt )

In the second one, I get the following error message by using the web UI "404 Not Found https://<vsphere-ip>/folder/<vm-name>/<vm-name>.vmx?dsName=<datastore-name>"

By using the xo-cli I get the "404 Not Found" on both the instances.

Regarding the "404 Not Found", I want to point out that at OVH I have a VMware datacenter (with 2 hosts) and in order to access to the storage I need to specify the parameter dcPath=<datacenter-name>

So the right URL should be https://<vsphere-ip>/folder/<vm-name>/<vm-name>.vmx?dcPath=<datacenter-name>&dsName=<datastore-name>

Simply adding (in a static way) the dcPath specification on line :54 of esxi.mjs file makes it work.

I thought it was constant. I will look into the api to get it, and if not possible expose it in the UI

@Seclusion : noted I will look into theis error message, this one is a first for me

ismo-conguairta

@Seclusion @florent In my case the ESXi version is 7.0.3 (build 20842708) and the vCSA version is 7.0 (build 20845200). The VM I try to migrate is not running on VMware side.
The only difference between the 2 XO instances is that the first one is installed on a PV machine while the second one on a PVHVM machine.

florent

@ismo-conguairta @rajaa-b can you check it, I think the full SR object is sent to the backend when changing the sr from the default one to another , instead of the id

florent

@ismo-conguairta
Can you try this branch : https://github.com/vatesfr/xen-orchestra/pull/6694/files ?

Edit : I can get the dcPath from the esxi api, you can test from the frontend, no need to use the command line

For now you can't change the SR ( changing it will lead to a parameter error)

fbeauchamp opened this pull request in vatesfr/xen-orchestra

closed feat(xo-server): use dcpath in Esxi import #6694

ismo-conguairta

@florent I just checked the branch and I get this error message "404 Not Found https://<vsphere-host>/folder/<vm-name>/<vm-name>.vmx?dcPath=datacenter-61&dsName=<ds-name>"

where datacenter-61 is not the right reference to my datacenter. Please take a look at the following screenshot.

From documentation

dcPath is the inventory path to the Datacenter containing the Datastore.

florent

@ismo-conguairta said in VMware migration tool: we need your feedback!:

inventory path to the Datacenter

I updated to use another property (from https://developer.vmware.com/apis/196/vsphere/doc/vim.Datacenter.html ) is it better ? on our lab, theses properties have the same value

ismo-conguairta

@florent I have just checked and your last update works like a charm. Great!

Touille

Hi folks,

I have an error when importing from VMware

I'm using XO from sources :

commit number : ea2c6
Hypervisor : Xcp-ng 8.2.1
node : 18.14.2

When I go on import and "from VMware", I put my ESX credentials, check "skip SSL", I do see the list of my VMs from my ESX. I select everything that needed and when I import, I have an error, doesn't matter which option I select or if the VM is running Windows or Linux. Also my ESX are running vmware 5.5.0

Here is the log and screenshot :

vm.importFromEsxi
{
  "host": "IP MASKED",
  "network": "6277d50c-5d2e-e896-864a-5afcc009ad51",
  "password": "* obfuscated *",
  "sr": {
    "type": "SR",
    "content_type": "user",
    "physical_usage": 33929035776,
    "allocationStrategy": "thin",
    "current_operations": {},
    "inMaintenanceMode": false,
    "name_description": "VM",
    "name_label": "NFS",
    "size": 12884899659776,
    "shared": true,
    "SR_type": "nfs",
    "tags": [],
    "usage": 289910292480,
    "VDIs": [
      "afef80db-c923-4248-b731-4d1712f02db1",
      "42fc30c3-4d8f-4126-bb78-fd4a8285b03a",
      "b286ad66-3d19-4984-aa80-840d93c72cf0",
      "03869f0c-1a02-4e32-9932-4e221e534eb0",
      "d17a4e5e-7276-4ef2-84f4-4766c4ad471e"
    ],
    "other_config": {
      "auto-scan": "true"
    },
    "sm_config": {},
    "$container": "3eb75cbb-0cc2-3c90-e63e-ae6da1ef9417",
    "$PBDs": [
      "90204213-cbec-5194-439d-ab795a0fe4b8",
      "2c8adf39-d2a9-8dd5-568d-872fcc04de54"
    ],
    "id": "cecb563f-f745-3ed6-1f64-85de34dfbbd5",
    "uuid": "cecb563f-f745-3ed6-1f64-85de34dfbbd5",
    "$pool": "3eb75cbb-0cc2-3c90-e63e-ae6da1ef9417",
    "$poolId": "3eb75cbb-0cc2-3c90-e63e-ae6da1ef9417",
    "_xapiRef": "OpaqueRef:04f1c17c-357e-428c-bbbe-2a558cd7238a"
  },
  "sslVerify": false,
  "stopSource": false,
  "thin": false,
  "user": "root",
  "vm": "109"
}
{
  "code": 10,
  "data": {
    "errors": [
      {
        "instancePath": "/sr",
        "schemaPath": "#/properties/sr/type",
        "keyword": "type",
        "params": {
          "type": "string"
        },
        "message": "must be string"
      }
    ]
  },
  "message": "invalid parameters",
  "name": "XoError",
  "stack": "XoError: invalid parameters
    at Module.invalidParameters (/opt/xo/xo-builds/xen-orchestra-202303011617/packages/xo-common/api-errors.js:26:11)
    at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202303011617/packages/xo-server/src/xo-mixins/api.mjs:65:20)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202303011617/packages/xo-server/src/xo-mixins/api.mjs:390:19)"
}

ismo-conguairta

@Touille As @florent said in a previous message probably the full SR object is sent to the backend instead of its id. This happens when you change the destination SR from the default one to another. You can try to proceed with the export on the default SR.

Take a look at this branch: https://github.com/vatesfr/xen-orchestra/pull/6696/files
It seems to fix the error.

Rajaa-BARHTAOUI opened this pull request in vatesfr/xen-orchestra

closed fix(xo-web/import/vmware): fix invalid params #6696

olivierlambert

It's even merged in master (few seconds ago)

Touille

Hi @ismo-conguairta.
As you and Florent said, before the update, when I tried to import to another SR than the default one, it wouldn't work.

Since the update an hour ago, it's fixed I've just imported a VM from VMware to any SR I want

thank you!!

planedrop

It may have already been mentioned in here more recently, but I still think some kind of system to select specific VHDs from the ESXi box would be super nice.

Sometimes one may only need to move the data of specific VHDs (excluding say logging or other temporary data style VHDs) and this would greatly speed up migrations.

It would also help in the event someone has VHDs that are larger than 2TiB, since you'd be able to only move the smaller ones and find an alternate solution for the larger than 2TiB VHDs.

Just a thought though; this tool is still amazing and has helped me start migrations!

olivierlambert

@planedrop the issue is that we are about to add multi-VM migration, so it will be a bit harder to make individual choices per disk. However, we could always create a convention based on a tag/name of the disk to ignore it, what do you think?

planedrop

@olivierlambert I think a tag or name based exclusion would be a great idea! Helps in the more niche use cases where not all drives have to be moved.

As an example use case, I have a VM I am going to migrate sometime in the next few weeks, but I only need it's C drive (the other drives are for logging, etc... and are more than 2TiB anyway). Right now I plan to export the VMDK and try importing it but I've had mixed results with that working correctly in the past, whereas this new V2V migration tool has been super reliable so far, so I'd have more confidence in it working (not to mention it's less work haha).

olivierlambert

In VMware, can you easily tag a VM disk?

planedrop

@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?

olivierlambert

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

planedrop

@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:

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!

olivierlambert

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

planedrop

@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?