Thank for you feedback and direct honesty, I guess you really don't like ESX :-P
But I agree with you on many of the issues you point out. Quality of the software, the website, their product naming/branding.
Management tool....I don't agree so much.Try to connect Hyper-V manager to a HyperV server (non-desktop version of course) not joined to the domain....that's take a lot of work!
I think the ESXi did a pretty good job with the Web client, and I like you can SSH to your ESX server....you can't do that to you Hyper-V. You can use PowerShell, but I still prefer my putty and WinSCP :-)
Unfortunately I need USB passthrough, that's why I consider ESXi.
I think you can get summon the biggest differences between the two:
- Hyper-V runs on almost any hardware and you can keep current with the software without changing you hardware for quite a long time
- ESXi is quite pesky at the hardware it runs on - and you can be quite assured, that the newest version of ESXi will not run on any server older than 3 years. That is the biggest disadvantage of ESXi in my opinion
- Hyper-V is very pesky at the VM Guest software you are running under its hypervisor and if you need a graphical console other than RDP on your VM guest, the graphic is really bad - further there is no real support for USB (pass-through) devices. That are the biggest disadvantages of Hyper-V in my opinion.
- ESXi supports a multitude of VM Guest software and you can even run quite old guests easily, it has a really good graphics performance and it does support USB-passthrough for almost all available USB devices
- Hyper-V is Windows, so you can use a multitude of software for all sorts of jobs to be done including management of the hypervisor, but the included management tools are quite limited in my view
- ESXi is quite proprietary, so the software options you can run on your server are quite limited, but the included management tools (if you are using Vcenter server) have much more possibilities (they are only horribly slow, if you look e.g. on the webclient)
The rest is of importance only for very specific or big environments IMO.
I don't agree with the comment about ESXi not running on server hardware older than 3 years. We are typically refreshing hardware every 3 to 4 years but some of that always trickles down to TEST/DEV and it's all still listed on the HCL and supported. Granted at some point it's going to fall off the HCL for the latest version of the hypervisor but your usually on hardware that is over 5 years old at least by that point.
And to Mrgrouchy, you work for Microsoft I assume right? So much false information spewed in that only ever post from you. Sigh....
In my environment I have both Hyper-V 2012R2 and Vmware 5.x to latest 6.5 , each have 3 hosts running total 25 VMs serving all kind of applications (SQL, Firewall, RSA...). They are up for more than two year now. I do support on my own learning mostly on YouTube and google search. I do have backup system using Arcronis, or do manual backup provided by the product. Both conversion tool from Microsoft and VMware are not perfect, I found it work most for me when I perform conversion make sure to stop all application services, batch processes, and do not start the new VM after conversion to allow you to check the settings of the new VMs. Also I found that VMware did not work well with application using hardware dongle key.
when you perform P2V make sure your DNS settings and domain name are correct.
I read all comparing information on both product mostly online and do my own research, take notes on problem or errors from others that do the installation or conversion, and just pick one that work good for my environment regarding to operating system (windows or Unix), licensing, in my case my company mostly on Windows environment but I do have a few applications do not support Hyper-v at that time that why I ended up have both VMware and Hyper-V They both are good, I have not had a failure VM before, I did test restore VM on the same host or to different host on both product and it works very well. I will plan to convert the host to Hyper-V 2016 in the future.
Just my 2 cents, and sorry English is not my main language.