I have a vmdk file that boots Windows Server 2016 fine in VMware Workstation Player.
I converted the vmdk file to be compatible with ESXi.
I used the command, vmkfstools -i source.vmdk new_esxi_compatible.vmdk -d thin
When I boot the Windows Server 2016 in the ESXi, it goes into "Preparing Automatic Repair", and I can't get it to boot into Windows.
I've tried,
bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd
... but to no avail.
Anything else I can try?
Am is using the vmkfstools correctly?
Try using Vmware V2V Converter as per your requirement.
Regards,
Randhir
Try using Vmware V2V Converter as per your requirement.
Regards,
Randhir
Ah, thanks! I forgot VMware's converter also does V2V. My brain was stuck on it being only used for P2V.
So the converter will convert the vmdk file to a live running ESXi server ...
Is it possible to convert the vmdk file to an ESXi-compatible vmdk file, without needing a running ESXi server?
I would then manually move the ESXi-compatible vmdk file to the ESXi server myself at a later time.
So the converter will convert the vmdk file to a live running ESXi server ...
yes , Once you use Converter to move VM on esxi . Your disk will be vmdk.
Is it possible to convert the vmdk file to an ESXi-compatible vmdk file, without needing a running ESXi server?
No, you have to select your ESXI host name when you are going to covert VM on esxi .
I would then manually move the ESXi-compatible vmdk file to the ESXi server myself at a later time.
No, It will create VMDK file along with other supported file . you no need to move any file manually.
Regards,
Randhir
If you found my answers useful please consider marking them as Correct OR Helpful
VMware Converter worked. I was concerned it would take too long, converting and transferring over the network, to the ESXi server.
It showed it would take 5-6 hours to complete, but it only took 1-2 hours.