Hyper-V… 2 Months Later

I have to say this so far… I will not be giving any of my influence to my immediate boss or other co-workers (or even anyone on the interwebs) to use Hyper-V 2012, or any other version in a production environment for a few reasons:

1. Linux Guests

Obviously I am a Linux enthusiast. I don’t believe that it is right for everyone, but I do believe in it, and I do believe that it is a very solid server platform. That being said, Microsoft has not accepted this fact quite yet. Integration with a Linux guest under Hyper-V is flaky at best. I have had more kernel panics using stock CentOS than I ever have on any other hypervisor, or even physical machines. This is with their integration software installed as well. I do not use Debian / Ubuntu as production machines, so I can’t speak for those, but Red Hat / Oracle / CentOS may be “officially supported”, but they do not work nearly up to snuff. I honestly have been afraid to update some of the servers I put on our Hyper-V server for that reason.

2. Cannot hot-add hardware

And by hardware, I don’t mean hot adding a CPU or a gig of memory… In VMware this is a given – sometimes you need to hot add a NIC or a hard drive. This is not the case in Hyper-V – and if it is it is buried somewhere deep in there.

3.  Runs on top of Windows

This could be a pro or a con.

Anyway, there are far more things to mention, but the Linux Kernel Panics are happening far too often for me to endorse this as an acceptable alternative for VMware – you might as well just run Virtual Box on the machine and share the machines through RDP – I think that would be a more stable solution than Hyper-V.