VMware Converter 3 can clone source images containing these operating systems, but the destination virtual machine may or may not work without additional configuration after import. In particular, if the source image contains unsupported hardware, you might need to modify the configuration of the destination.
I understand the converters from VMware have improved by leaps and bounds over what it was in version 3, but theres still a reasonable amount of security in P2Ving a box while its completely down with no running services whatsoever.
DiskHandleWrapper,87 DiskLib_Open failed on vpxa-nfc VMFS _015 VM01/VM01.vmdk@esx01:902!52 f1 8e a1 39 1c c1 f8-9c d4 05 71 1a 4f ae c6 with error NBD_ERR_NETWORK _CONNECT. imageProcessingTaskImpl,552 BlockLevelCloning:task21: Image processing task has failed with MethodFault:Exception: sysimage.
Fifth issue, vCenter integration. Its not exactly shocking that it didnt work with vCenter, but I was hopeful. The converter would go through and recognize everything out of vCenter, but then ran into a bunch of issues as soon as the clone actually starts.
Can import as well as create Virtual Appliances in Open Virtual Machine Format (OVF) version 0.9 Can remove all System Restore checkpoints in the target virtual machine when doing volume-based cloning. Provides full support for Microsoft Vista 32-bit and 64-bit operating systems.
It took me literally 15 minutes from the point of hitting a button to boot to disc to the point of accepting the EULA. Third issue, drivers. I was lucky enough for the internal NICs to be found but the add-on NICs were not.
Hot cloning with VMware Converter can be tricky, but this tip offers a step-by-step tutorial to help with your hot or cold physical-to-virtual (P2V) migration.
VMware Converter 5 - available, it s a standalone product, not integrated into vCenter, can be used and isntalled on client PC to convert physical to virtual.