Hyper‑V hypervisor scheduler types.
Well,
what we're talking about here first of all is a scheduler determines how the
Hyper‑V host assigns work across guest virtual CPUs. And the way it normally
works is that virtual machine virtual processors. Now LP refers to a logical CPU
core on the hardware host machine. You know,
you may have a physical CPU that has two or four logical cores
on it, and then with or without CPU groups,
you're giving CPU access to your virtual machines, and those virtual machines
have one or more virtual processor cores, right? And normally your VM virtual
processors run 1:1 with a host's logical processor, but you can, as an
administrator, control guest VM access to use any of the host's logical
processors. There's a few types of scheduler that you can configure. The default
is the classic scheduler, and this is just what Microsoft defines as fair share,
round‑robin CPU scheduling,
just what you would get as if the VMware a physical box,
how it would schedule work across its tasks.
Next, we have the core scheduler, and this would be used for a higher
security orientation. This allows you to constrain guest virtual
processor cores to physical cores that provide strong isolation. So you
might have one VM attached to one processor core, another VM attached to
another core, and this is to prevent bleeding, data leakage, across those
cores where you have a need, a greater need, to provide strong CPU and
data isolation.
Lastly, there is the root scheduler, and this is the default mode that's
used in Windows client; that is Windows 10 Hyper‑V, Windows 11 Hyper‑V.
This is using the built‑in what's called NT scheduler, just the operating
system scheduler, where the hypervisor hands over control of the
scheduling to the operating system.
So the root scheduler in client Hyper‑V, Hyper‑V doesn't do anything as
far as scheduling work across the VM virtual processors. It just basically punts it to the host operating system.