I have got the highest respect for Hyper-V. It’s simple to use I don’t need to learn any new interface (it’s just another mmc snap-in) in which to mange the virtual world. However when someone asks me if they can install other roles alongside hyper-V in production I say “Oi mate NO don’t do it”.
The problem here is that it is possible to do this with Hyper-V, for example to run SQL Server alongside hyper-v in the host operating system. It’s not a FAQ but do get asked about the advisability of this by customers and I have seen internal threads asking the same thing. Rather than ask why this a bad idea let me debunk some “myths” about why people think it is a good idea:
In fact the only reason I put applications alongside hyper-V is for ease of use and a better experience when I am showing how infrastructure stuff works in my demo environment. So I have Office installed on the base OS along with on using hyper-V for demos.
If I was putting a virtual machine infrastructure into production, I would use the free Hyper-V Server in as the host operating system and remotely manage this with server manager or System Center on a client machine, as this is lightweight and secure and still easy to manage.
Well said Andrew!
This is a helpful post. Can you provide any benchmarks or citations that support your claim?