Hyper-V Server 2016 as Bare Metal Hypervisor or Not ?

Question

Hey community. I was hoping for some clarification. I am use to working with VMWare ESXi VSphere for hypervisors. So I have been labbing for my MCSA and I notice alot of the context of MCSA material describes installing an instance of Windows Server 2016, and then turning that into a Hyper-V Server. What I did was I installed Hyper-V Server 2016 on my ProLiant. Is there any reason why I would not want to do this ? I had to reference alot of white papers, manuals, eventually blogs, and I think a youtube video or two before I could manage it from my remote PC. It involved adding the target computer via power shell, customizing the hosts file, adding the server within the PC's computer configuration I forget what exactly. I also had to disable the firewall on the Hyper-V Server 2016 before the Hyper-V Server 2016 hosted on the ProLiant started appearing in my Hyper-V Manager from my Windows 10 Pro machine.

However I was listening to this gentleman's youtube video.

https://www.youtube.com/watch?v=CdJJ4jiYx0Q

and he explains that Hyper-V Server is meant to be installed as a bare metal Hypervisor which is what I did do but because i was accustomed to working with VMWare SAN's that are the same way where you install the Hypervisor on the host machine and start spinning up virtual machines. However I noticed i got some updates on the Hyper-V-Server 2016 the other day and not all of them wanted to install ... I believe some of the updates were for Windows so it went into this infinity loop patching process. However this experience coupled with the literature that I am reading that explains many scenarios of an instance of Windows Server being installed first followed by turning the box into a Hyper V Host but after an installation of Windows Server ?

What's the final word on this ? I already have like 8 VM's on my machine. I just didn't want to run into an unforeseen issue later on.

Anyone know what's up with this my fellow community members ? Your expertise is much appreciated.

Answer 1

Not sure what the question is? Yes windows hyper-v is a type one hypervisor.
https://learn.microsoft.com/en-us/windows-server/administration/performance-tuning/role/hyper-v-server/architecture

--please don't forget to Accept as answer if the reply is helpful--

Answer 2

Hi，

1. Hyper V server is a stand-alone product that contains only the Windows hypervisor, a Windows Server driver model, and virtualization components. It provides a simple and reliable virtualization solution to help you improve your server utilization and reduce costs.

Windows server with Hyper V role is an entire System with Hyper V role installed.

https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/hyper-v-server-2016

2. Below is an article about how to get start with Hyper V server 2016, for your reference:

https://www.techrepublic.com/article/getting-started-with-microsoft-hyper-v-server-2016/

Thanks for your time!
Best Regards,
Anne

-----------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.