If we have a look at how Microsoft Hyper-V and VMware ESXi work, we see many differences in terms of architecture. However, most virtualization administrators aren't aware of these differences. In fact, many of them don't really know how Hyper-V hypervisor works on the host operating system.
A very common misunderstanding about Microsoft Hyper-V is that since Windows operating system is required to install Hyper-V, it operates on the host OS instead of directly on the hardwar
It is important to bear in mind that once the Hyper-V role is enabled through the server administrator, the code of the hypervisor is already configured to start in the space of Windows kernel. Components that operate in the kernel space always have direct access to the hardware, and the same happens with Hyper-V. On the other hand, VMware ESXi uses a completely different approach. The ESXi hypervisor works as an independent ISO file, being a Linux kernel OS.
Both Hyper-V and ESXi are type 1 hypervisors. This means that they run directly on the hardware and their designs can be classified as microkernelizados or monolithic. The unique design differences between these two hypervisors are the location of device drivers and control function.
Learn all the details reading the full article: How the Hyper-V architecture differs from VMware ESXi