A função Hyper-V no Windows 10 Pro é diferente da função no Windows Server?

Question

Pelo que entendi, quando você ativa a função Hyper-V no Server 2008 e acima, ela virtualizará o próprio SO do servidor para ser executado sobre o Hyper-V.

Fonte:

• link

• O Hyper-V parece rodar sobre o SO host, então por que ele é considerado um hipervisor nativo (tipo-1)?

Quando eu habilito a função Hyper-V no Win 10 Pro, acontece a mesma coisa?

    

Answer 1

Em ambos os casos (versões do Windows servidor e não-servidor), o hyper-v é instalado como um hypervisor tipo 1 entre o hardware e o sistema operacional host; Portanto, nesse sentido, o sistema operacional host é convertido em uma máquina virtual.

No entanto, existem diferenças na implementação entre as versões de servidor e não-servidor:

Differences between Hyper-V on Windows and Hyper-V on Windows Server

There are some features that work differently in Hyper-V on Windows than they do in Hyper-V running on Windows Server.

The memory management model is different for Hyper-V on Windows. On a server, Hyper-V memory is managed with the assumption that only the virtual machines are running on the server. In Hyper-V on Windows, memory is managed with the expectation that most client machines are running software on host in addition to running virtual machines. For example, a developer might be running Visual Studio as well as several virtual machines on the same computer.

Hyper-V features available in Windows Server only

There are some features included in Hyper-V on Windows Server that are not included in Hyper-V on Windows. These include:

Virtualizing GPUs using RemoteFX
Live migration of virtual machines from one host to another
Hyper-V Replica
Virtual Fiber Channel
SR-IOV networking
Shared .VHDX

Limitations

Using virtualization does have limitations. Features or applications that depend on specific hardware will not work well in a virtual machine. For example, games or applications that require processing with GPUs might not work well. Also, applications relying on sub-10ms timers such as live music mixing applications or high precision times could have issues running in a virtual machine.

In addition, if you have Hyper-V enabled, those latency-sensitive, high-precision applications may also have issues running in the host. This is because with virtualization enabled, the host OS also runs on top of the Hyper-V virtualization layer, just as guest operating systems do. However, unlike guests, the host OS is special in that it has direct access to all the hardware, which means that applications with special hardware requirements can still run without issues in the host OS.