Stupid Hyper-V mistake #1:
Never copy your hyper-V drive, change the drive mapping in the hyper-v administrator, ignore the warning about snapshots, then try to restart your virtual machine. The hyper-v drive contains only the base configuration of the virtual machine (prior to the administration of any snapshots). When you copy the drive, you lose the snapshots and any updates or changes to your virtual machine since the time you took the first snapshot.
If what you're looking for is simply to move/copy your virtual machine, instead of copying the hard drive image, look at "export".
The nice thing about hyper-v versus vmware is that you don't have to worry about driver support (as much). ESXi is supported only on certain hardware platforms. It will work on a lot of unsupported platforms, but isn't it easier to know for sure? If all you're looking for is a development test area, then hyper-v is easy and quick.
Never copy your hyper-V drive, change the drive mapping in the hyper-v administrator, ignore the warning about snapshots, then try to restart your virtual machine. The hyper-v drive contains only the base configuration of the virtual machine (prior to the administration of any snapshots). When you copy the drive, you lose the snapshots and any updates or changes to your virtual machine since the time you took the first snapshot.
If what you're looking for is simply to move/copy your virtual machine, instead of copying the hard drive image, look at "export".
The nice thing about hyper-v versus vmware is that you don't have to worry about driver support (as much). ESXi is supported only on certain hardware platforms. It will work on a lot of unsupported platforms, but isn't it easier to know for sure? If all you're looking for is a development test area, then hyper-v is easy and quick.