View Single Post
Old 25. Mar 2010, 01:45 AM   #5 (permalink)
Senior Member
freedog96150's Avatar
Join Date: Jan 2010
Location: Not Vegas
Posts: 111

Hyper-V was designed to be a bare-metal Hypervisor. It was never intended to be any kind of a server other than a virtual host ready to accept guest OS's. Yes there are basic networking functions, storage management functions, and Active Directory type functions, but this is more to allow you to get the Host onto your existing network so that you can manage it with client tools from a remote workstation.

MS has provided a very nice set of GUI tools that you would load onto any XPSP3 or higher client that takes all the command-line aspects out of the picture.

The reason MS is providing this for free is to jump into the virtual ring with the likes of VMWare EXSi, Citrix XenServer and other bare-metal hypervisors, all who give you their hypervisors and some basic tools for free.

For anyone who is struggling with the bare-metal hypervisor terminology, here is a quick explanation. Like any regular OS, a Hypervisor loads straight to the hard drive (hence bare metal) FIRST. You can then load all your Guest OS's on top of that host OS. This differs from a traditional virtual server setup that normally consists of a host OS (either Linux or Windows), the virtual software/drivers, and then the guest OS. As you can see, there is an extra layer involved.

There are pros and cons to each setup, all of which can be debated in the usual "holy war" manner that geeks tends to utilize to express their irrational and undying loyalty to a single technology.
freedog96150 is offline   Reply With Quote