VMware EVC (Enhanced VMotion Compatibility) enable VMware VMotion across CPU generations
Everyone who had been using VMware for a while, would appreciate VMware VMotion. Actually VMware VMotion have always been a distinguished feature of VMware ESX servers. Despite of VMotion has always been a great feature, people using it at earlier stages used to have a tough time when having to use it across different CPU generation. That meant companies had to actually put similar hardware server in the same cluster, to guarantee that VMotion work smoothly. This was not possible at all the time, and was a tough call for implementers as they had to cheat masking manually in order to avoid VMotion not accepting to run between different CPU genrations.




i need to build a 2 server cluster to host a frontend virtual machine.
the virtual machine should run on 1 node(most powerful) and in case of hardware/software failure run on 2 node (less powerful only for services availability, reliability)
should i use vmware or hyper-v for best costs/Reliability ratio?
thanks in advance.
As reliability go I would say VMware can beat hyper-V at any time, specially they have been out there for a lot longer & running in many production environment. I know many members of our team will argue on this, but if you come to me I would always implement VMware over Hyper-V when a critical application is involved.