First issue:
When converting a VM from ESXi to Hyper V using Microsoft Virtual Machine Converter I select the options to shutdown the guest on the ESXi and start it on the Hyper V hosts. When completed the VM is running on both still and never shut down on the ESXi.
Second issue:
The last VM I have been converting is the same size and spec as 3 others which each took approx. 3 hours. They were held up on Convert Disks for the majority of that and completing each other step fine.
Now this one has completed the other steps in the same timeframe, maybe a bit quicker, but now has been stuck on "Copy disk(s) for over 2 hours, still at only 55%. While it's done this, because it didn't shutdown the ESXi guest once converting the disk to local storage,
I have to cancel the process as changes have been made to that guest in this giant no explanation time. So that's now 5 hours conversion time down the toilet.
I have checked everywhere and can find no explanation for the delay in copying. I've checked the network and disk usage on the conversion machine and host and found no issue, I've checked the IOPS on the SAN it's all stored on, looks like it's not even being used. There's no bottleneck so why did 3 servers all the same go fine (literally the same size HD, the same Application on all, the same exact Specs) then the 4th do this shit?