Zane Gray

@n313893254 after posting this bug report on Friday, I did check the spec.template.spec.volumes.persistentVolumeClaim.claimName under the "Edit YAML" for the VM. Here is where things got odd. Sometimes opening the YAML...

I hate to be the "Me too." poster, but I'm having the same issue. I was encouraged enough by https://github.com/harvester/harvester/issues/5143 that I even rebuilt my Harvester cluster on 1.3.1, but...

Just a follow up thought: the VM Import enhancement spec appears to allow for a `path` variable in the CRD: https://github.com/harvester/harvester/blob/master/enhancements/20220726-vm-migration.md The VM that I am attempting to migrate is...

Getting closer! Reading the code at https://github.com/harvester/vm-import-controller/blob/main/pkg/apis/migration.harvesterhci.io/v1beta1/virtualmachines.go, I found that the CRD spec to define the path is `folder`. My CRD now looks like: ``` apiVersion: migration.harvesterhci.io/v1beta1 kind: VirtualMachineImport metadata:...

Final update: I adjusted the metadata -> name value from `struxurewaredcexpert` to `dcexpert`. This overcame the 63 character limit issue. Once I re-applied the CRD, Harvester requested that VCenter power...

One thought: Prior to importing the VM, log into the VM on the source system and install the appropriate Qemu/VirtIO drivers. This "might" allow it to boot after the import....

One other note for anyone who reads this in the future: If your source system is VSphere/VCenter, you may also have to remove the VMWare Tools from the VM prior...

Thanks @schtritoff. I have been using the `-CustomUserDataYamlFile` option for most of my VM deployments on Hyper-V. In fact, it is the main selling point for my using your deployment...

Likely the `test-path` command in this part of the script is what is impacting me:  I wonder if there is a way to allow the `$CustomUserDataYamlFile` to be considered...