This message was deleted.

If all is well it should start automatically but can take a while as noted at https://docs.harvesterhci.io/v1.4/advanced/addons/vmimport#virtualmachineimport Checking your YAML vs the example I noticed you're missing a '1' after the second 'v1beta' for apiVersion so double check your YAML

Argh, I must have been referring to old docs 😕 - will give that a shot now, thanks for the insight @witty-jelly-95845! One further question, if I may: in terms of the formatting for the source and destination network: should the source also require the name of the dvs in vCenter? I ask, as there are 2 in the datacenter. If so, would it be expected to be formatted as

sourceNetwork: "dvSwitch/dvs_10"

likewise for the destinationNetwork: is the "default" that it refers to the namespace in Harvester, or the name of the cluster network?

This thread is a bit long, but it helped me troubleshoot my first migration: https://github.com/harvester/harvester/issues/5525 IMHO - Unless your VM is highly bespoke with lots of customizations that are not easy to replicate, I would recommend simply rebuilding the VM on Harvester and adjust your DNS/Load Balancer records to shift traffic to the new VM after testing. Dealing with removing the VMWare drivers and adding the VirtIO drivers can be more of a pain than it's worth. Also, take a look at StarWinds v2v converter. Harvester is not (yet) a first class hypervisor within StarWind, but it's useful as an intermediary migration tool. Fair warning: it appears to be "nag ware".