<![CDATA[Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined]]>single host XCP-ng 8.2.1 w/ local SR,
XO (ronivay installer)(installed today) , VM on above.
ESXi 8.0u1 (expired trial) all VMs stopped.

Using XO Import from VMware, I sucessfully imported two VMs: a Windows10 VM, and a pfSense VM. I started both and they work.

Next I tried to import a Windows Server 2012R2 (single 60GB disk) from same ESX host. It fails within about five seconds with:

vm.importMultipleFromEsxi
{
  "concurrency": 2,
  "host": "10.16.75.5",
  "network": "eddfca3c-8b32-7cf8-510d-debef0bff592",
  "password": "* obfuscated *",
  "sr": "2a160b8d-11ec-776b-7ce9-0af0ceb540c7",
  "sslVerify": false,
  "stopOnError": true,
  "stopSource": false,
  "template": "b6d0600e-677b-376a-507e-8f9dda9424cb-11c46476-bd5c-4d75-9cf0-57fe55343ba3",
  "user": "root",
  "vms": [
    "3"
  ]
}
{
  "generatedMessage": true,
  "code": "ERR_ASSERTION",
  "operator": "notStrictEqual",
  "succeeded": {},
  "message": "Expected \"actual\" to be strictly unequal to:

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

undefined
    at Esxi.#findDatacenter (file:///opt/xo/xo-builds/xen-orchestra-202406131610/@xen-orchestra/vmware-explorer/esxi.mjs:74:5)
    at Esxi.#download (file:///opt/xo/xo-builds/xen-orchestra-202406131610/@xen-orchestra/vmware-explorer/esxi.mjs:124:56)
    at Esxi.download (file:///opt/xo/xo-builds/xen-orchestra-202406131610/@xen-orchestra/vmware-explorer/esxi.mjs:139:41)
    at Esxi.#inspectVmdk (file:///opt/xo/xo-builds/xen-orchestra-202406131610/@xen-orchestra/vmware-explorer/esxi.mjs:249:21)
    at Esxi.getTransferableVmMetadata (file:///opt/xo/xo-builds/xen-orchestra-202406131610/@xen-orchestra/vmware-explorer/esxi.mjs:351:17)
    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202406131610/@vates/task/index.js:169:22)
    at Task.run (/opt/xo/xo-builds/xen-orchestra-202406131610/@vates/task/index.js:153:20)
    at MigrateVm.migrationfromEsxi (file:///opt/xo/xo-builds/xen-orchestra-202406131610/packages/xo-server/src/xo-mixins/vmware/index.mjs:186:22)
    at file:///opt/xo/xo-builds/xen-orchestra-202406131610/packages/xo-server/src/api/vm.mjs:1480:30
    at Task.runInside (/opt/xo/xo-builds/xen-orchestra-202406131610/@vates/task/index.js:169:22)
    at Task.run (/opt/xo/xo-builds/xen-orchestra-202406131610/@vates/task/index.js:153:20)
    at asyncEach.concurrency.concurrency (file:///opt/xo/xo-builds/xen-orchestra-202406131610/packages/xo-server/src/api/vm.mjs:1478:11)"
}
]]>https://xcp-ng.org/forum/topic/9192/import-from-vmware-err-name-assertionerror-expected-actual-to-be-strictly-unequal-to-undefinedRSS for NodeTue, 09 Jun 2026 02:58:50 GMTFri, 14 Jun 2024 02:04:02 GMT60<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Wed, 25 Feb 2026 13:57:12 GMT]]>@benapetr said in Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined:

Hello, since this never had a clear resolution, here is explanation of the bug and why it happens:

There is a bug in disk iteration in that XO vmware plugin (somewhere in that esxi.mjs I don't remember exact location) - it basically expects that all disks of VM exist in same datastore and if they don't it crashes as the next disk in unexpectedly missing (undefined)

Workaround is rather simple - select the VM in vmware, migrate -> storage, disable DRS (important) and then select any DS that no disks current exist on. If you select and DS that is already used by same VM it will sometimes not get fixed! It also may happen even if VM is "apparently" looking like it's on single DS, even if it reports as such, still try to migrate it to another DS, and disable DRS so that really all files, even meta files are in same directory.

Then run XO import again, it will magically work.

thanks you for the input
we were under the assumption that all the disk of a VM are in the same datastore
the fix should be too hard now that you did the hard work

edit: card created in our backlog, I will take a look after the release to see how hard it is to implement

]]>https://xcp-ng.org/forum/post/102939https://xcp-ng.org/forum/post/102939Wed, 25 Feb 2026 13:57:12 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Wed, 25 Feb 2026 11:56:27 GMT]]>Hello, since this never had a clear resolution, here is explanation of the bug and why it happens:

There is a bug in disk iteration in that XO vmware plugin (somewhere in that esxi.mjs I don't remember exact location) - it basically expects that all disks of VM exist in same datastore and if they don't it crashes as the next disk in unexpectedly missing (undefined)

Workaround is rather simple - select the VM in vmware, migrate -> storage, disable DRS (important) and then select any DS that no disks current exist on. If you select and DS that is already used by same VM it will sometimes not get fixed! It also may happen even if VM is "apparently" looking like it's on single DS, even if it reports as such, still try to migrate it to another DS, and disable DRS so that really all files, even meta files are in same directory.

Then run XO import again, it will magically work.

]]>https://xcp-ng.org/forum/post/102938https://xcp-ng.org/forum/post/102938Wed, 25 Feb 2026 11:56:27 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 21 Jun 2024 06:37:51 GMT]]>That's interesting, thanks for the feedback @sshughes and keep us posted!

]]>https://xcp-ng.org/forum/post/79109https://xcp-ng.org/forum/post/79109Fri, 21 Jun 2024 06:37:51 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 21 Jun 2024 00:43:14 GMT]]>@sshughes Pretty certain there is nothing wrong with XO. Seems there is a problem with this VM on ESX. vSphere can perform Export on the other VMs, but not the one in question. Task list says an Export is running, but we never get the prompt to select components for export. Thanks. If I learn any more, will report back.

]]>https://xcp-ng.org/forum/post/79106https://xcp-ng.org/forum/post/79106Fri, 21 Jun 2024 00:43:14 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Thu, 20 Jun 2024 20:17:28 GMT]]>above log entry is result of using XO web UI to import from ESXi and is the 3rd vm we tried to import. The first two imports were successful.
I used ronivay's installer and chose to have xo-server run as non-root user.
Decided to try using xo-cli vm.importFromEsxi.
I SSH to the XO VM as root and figure out how to get xo-cli register to work.
Using parameters displayed in the above log entry I think I was able to properly construct the xo-cli vm.importFromEsxi command as follows:

xo-cli vm.importFromEsxi host=10.16.75.5 user=root password=****** sslVerify=false vm=ParishSVR2 sr=2a160b8d-11ec-776b-7ce9-0af0ceb540c7 network=eddfca3c-8b32-7cf8-510d-debef0bff592 template=b6d0600e-677b-376a-507e-8f9dda9424cb-17a818b5-20a6-4d34-a7ef-320da9ef4c14

The result is a different error. Does this offer any more help as to what went wrong?

✖ JsonRpcError: can't get config of object ParishSVR2 (Type: VirtualMachine)
    at Peer._callee$ (/opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/json-rpc-peer/dist/index.js:139:44)
    at tryCatch (/opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:45:16)
    at Generator.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:133:17)
    at Generator.next (/opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/@babel/runtime/helpers/regeneratorRuntime.js:74:21)
    at asyncGeneratorStep (/opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/@babel/runtime/helpers/asyncToGenerator.js:3:24)
    at _next (/opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/@babel/runtime/helpers/asyncToGenerator.js:22:9)
    at /opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/@babel/runtime/helpers/asyncToGenerator.js:27:7
    at new Promise (<anonymous>)
    at Peer.<anonymous> (/opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/@babel/runtime/helpers/asyncToGenerator.js:19:12)
    at Peer.exec (/opt/xo/xo-builds/xen-orchestra-202406131610/node_modules/json-rpc-peer/dist/index.js:182:20) {
  code: -32000,
  data: {
    message: "can't get config of object ParishSVR2 (Type: VirtualMachine)",
    name: 'Error',
    stack: "Error: can't get config of object ParishSVR2 (Type: VirtualMachine)\n" +
      '    at Esxi.fetchProperty (file:///opt/xo/xo-builds/xen-orchestra-202406131610/@xen-orchestra/vmware-explorer/esxi.mjs:447:13)\n' +
      '    at processTicksAndRejections (node:internal/process/task_queues:95:5)',
    succeeded: {}
  }
}
]]>https://xcp-ng.org/forum/post/79090https://xcp-ng.org/forum/post/79090Thu, 20 Jun 2024 20:17:28 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 14 Jun 2024 10:34:42 GMT]]>@ph7 said in Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined:

Shoundnt node.js be 18 ?

FYI, that is no longer required.

]]>https://xcp-ng.org/forum/post/78705https://xcp-ng.org/forum/post/78705Fri, 14 Jun 2024 10:34:42 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 14 Jun 2024 07:07:02 GMT]]>@ph7 I also have version 20, but no problem importing from VMware 🤔

74ce8389-8fbd-4d37-bf73-fa2c9d63bfdb-obrazek.png

]]>https://xcp-ng.org/forum/post/78702https://xcp-ng.org/forum/post/78702Fri, 14 Jun 2024 07:07:02 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 14 Jun 2024 07:02:19 GMT]]>@sshughes
Shoundnt node.js be 18 ?

]]>https://xcp-ng.org/forum/post/78701https://xcp-ng.org/forum/post/78701Fri, 14 Jun 2024 07:02:19 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 14 Jun 2024 02:52:34 GMT]]>@sshughes Hmmm, that's frustrating. If I remember correctly, that is a Python error. It might be something with the Python script itself. Is the VM off when you're trying to import it? It shouldn't matter, but just something to try.

]]>https://xcp-ng.org/forum/post/78694https://xcp-ng.org/forum/post/78694Fri, 14 Jun 2024 02:52:34 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 14 Jun 2024 02:35:42 GMT]]>@sshughes also ran apt-get update apt-get upgrade, but again... I installed this VM less than 12 hours ago, so nothing new.

]]>https://xcp-ng.org/forum/post/78692https://xcp-ng.org/forum/post/78692Fri, 14 Jun 2024 02:35:42 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 14 Jun 2024 02:33:39 GMT]]>@Nick-085
Just did. Reports nothing new.
Import fails with same error.

[info] Checking current node.js version

[ok] node.js version already on 20, checking updates

[info] Fetching Xen Orchestra source code

[info] Creating install directory: /opt/xo/xo-builds/xen-orchestra-202406132228

[info] No changes to Xen Orchestra since previous install. Skipping build. Use the --force to update anyway.
[info] Cleaning up install directory: /opt/xo/xo-builds/xen-orchestra-202406132228
]]>https://xcp-ng.org/forum/post/78691https://xcp-ng.org/forum/post/78691Fri, 14 Jun 2024 02:33:39 GMT<![CDATA[Reply to Import from VMware err: name: AssertionError: Expected "actual" to be strictly unequal to: undefined on Fri, 14 Jun 2024 02:22:25 GMT]]>@sshughes Can/have you run updates on the XO VM itself, then run the XOInstaller script to check for XO updates? That's what fixes issues for me most of the time.

]]>https://xcp-ng.org/forum/post/78690https://xcp-ng.org/forum/post/78690Fri, 14 Jun 2024 02:22:25 GMT