Migrate VMWare VM to XCP-ng fails 'Cannot read properties of undefined (reading 'errored')'
-
Having the exact same issue as others. Have upgraded XOA to latest 5.94.2 and gives the 'Cannot read ...' error. If I try with the VM powered on in ESXi I get a different error, '500 Internal Server Error https://xx.xx.xx.xx/folder/W11-23H2-TST1/W11-23H2-TST1-flat.vmdk?dcPath=ha-datacenter&dsName=XXXXX'
I take it this should always be attempted with VM powered off in ESXi? Just for infomration I can complete the import when there are no snapshots and the VM is powered off. This is the only state I have successfully completed an import with.
We're running VMware ESXi, 7.0.3, 22348816 with a local Datastore for the VM storage.
TIA
-
Warm migration is not currently supported with VMFS6.
-
@Danp Thanks, I did wonder as didn't appear I was doing anything wrong following you guides. Any Idea when this is likely to be supported in the future?
-
@fluxtor No, I don't know if/when this functionality will be added.
-
@Danp Got this from a ticket for a similar issue
Migrating from VMFS5 (whatever the underlying storage is) : can do warm and cold migration
Migrating from VMFS6 (whatever the underlying storage is) : can do cold migration
Migrating from NFS datastore : can do warm and cold migration
Migrating from VSAN: will need to download the disk completly and then push it to XCPThe version of the esxi is not relevant as long as its 5+, but ESXI6.5 and following are using VMFS6 by default
Ended up creating an NFS datastore, as it had similar issues even though the datastore was VMFS5
-
Although I didn't encounter your problem, I followed the steps in an article ( sorry fail to post the link) and successfully migrated the virtual machine from VMware to XCP-ng, which was very convenient.
