vmware vm migration error cause ?

[yeopil21]

Environment / VM layout (VMware side)

• i have a VMware VM managed by vCenter.
• The VM uses two virtual disks stored on two different datastores / LUNs:

OS disk: on OS_LUN (500 GB LUN) → a 500 GB VMDK assigned via vCenter

• VMDK file name on that datastore: [hostname]_2.vmdk

DATA disk: on DATA_LUN (1.5 TB LUN) → a 1.5 TB VMDK assigned via vCenter

• On the DATA datastore you see: [hostname].vmdk and [hostname]_1.vmdk

• Target environment (XCP-ng / Xen Orchestra)

• Target platform is XCP-ng, and you are migrating using Xen Orchestra (XO V2V import).

• The migration task shown in XO logs is vm.importMultipleFromEsxi, using:

• host: vCenter IP

• user: vCenter admin account

• sr: target SR UUID in XCP-ng

• network: target network UUID in XCP-ng

• concurrency: 2

Message
Expected "actual" to be strictly unequal to:
undefined

vm.importMultipleFromEsxi

"concurrency": 2,
"host": "Vcenter IP",
"network": "e3461d51-aeeb-2531-eb81-604384f5e86c",
"password": "* obfuscated *",
"sr": "ee70cdc5-70f5-f9eb-3ebd-1815100cbd6a",
"ssIVerify": false,
"stopOnError": true,
"stopSource": true,
"template": "f295540e-6617-1965-2cc1-8b4d36927311-612863ed-900d-456d-b4b7-38b70915fd1f",
"user": "admin",
"vms": [
"vm-21154"

1

}

"generatedMessage": true,
"code": "ERR_ASSERTION",
"operator": "notStrictEqual",
"diff": "simple",
"succeeded": (},
"message": "Expected W"actualW" to be strictly unequal to:

undefined",
"name": "AssertionError",
"stack": "AssertionError [ERR_ASSERTION]: Expected W"actual₩" to be strictly unequal to:

undefined
at Esxi.#findDatacenter (file:///root/xen-orchestra/@xen-orchestra/vmware-explorer/esxi.mjs:88:7)
at Esxi.#download (file:///root/xen-orchestra/@xen-orchestra/vmware-explorer/esxi.mjs:139:56)
at Esxi.download (file:///root/xen-orchestra/@xen-orchestra/vmware-explorer/esxi.mjs:154:41)
at Esxi.#inspectVmdk (file:///root/xen-orchestra/@xen-orchestra/vmware-explorer/esxi.mjs:264:21)
at Esxi.getTransferableVmMetadata (file:///root/xen-orchestra/@xen-orchestra/vmware-explorer/esxi.mjs:367:17)
at Task.runlnside (/root/xen-orchestra/@vates/task/index.js:175:22)
at Task.run (/root/xen-orchestra/@vates/task/index.js:159:20)
at MigrateVm.migrationfromEsxi (file:///root/xen-orchestra/packages/xo-server/src/xo-mixins/vmware/index.mjs:192:22)
at file:///root/xen-orchestra/packages/xo-server/src/api/vm.mjs:1489:30
at Task.runlnside (/root/xen-orchestra/@vates/task/index.js:175:22)
at Task.run (/root/xen-orchestra/@vates/task/index.js:159:20)
at asyncEach.concurrency.concurrency (file:///root/xen-orchestra/packages/xo-server/src/api/vm.mjs:1487:11)"

[olivierlambert]

I edited your post with Markdown code block, it's a lot easier to read. @florent will take a look when he can.

[Pilow]

should you not enter the ESX ip and not the vCenter IP to migrate ?

give it a try

[florent]

@yeopil21 you can target vsphere it should work

The issue here is that XO fail to link one of your datastore to the datacenter

is it XO from source or a XOA ? you should have in your server logs something like can't find datacenter for datastore with the datacenters and the datastore name as detected by XO
are you using an admin account on vsphere or is it a limited one ?