1
00:00:00,840 --> 00:00:03,500
Hyper‑V hypervisor scheduler types.

2
00:00:03,500 --> 00:00:03,810
Well,

3
00:00:03,810 --> 00:00:07,780
what we're talking about here first of all is a scheduler determines how the

4
00:00:07,780 --> 00:00:13,830
Hyper‑V host assigns work across guest virtual CPUs. And the way it normally

5
00:00:13,830 --> 00:00:20,520
works is that virtual machine virtual processors. Now LP refers to a logical CPU

6
00:00:20,520 --> 00:00:23,130
core on the hardware host machine. You know,

7
00:00:23,130 --> 00:00:27,220
you may have a physical CPU that has two or four logical cores

8
00:00:27,220 --> 00:00:30,300
on it, and then with or without CPU groups,

9
00:00:30,300 --> 00:00:34,680
you're giving CPU access to your virtual machines, and those virtual machines

10
00:00:34,680 --> 00:00:40,720
have one or more virtual processor cores, right? And normally your VM virtual

11
00:00:40,720 --> 00:00:46,380
processors run 1:1 with a host's logical processor, but you can, as an

12
00:00:46,380 --> 00:00:51,220
administrator, control guest VM access to use any of the host's logical

13
00:00:51,220 --> 00:00:56,210
processors. There's a few types of scheduler that you can configure. The default

14
00:00:56,210 --> 00:01:00,950
is the classic scheduler, and this is just what Microsoft defines as fair share,

15
00:01:00,950 --> 00:01:03,030
round‑robin CPU scheduling,

16
00:01:03,030 --> 00:01:07,510
just what you would get as if the VMware a physical box,

17
00:01:07,510 --> 00:01:10,360
how it would schedule work across its tasks.

18
00:01:10,360 --> 00:01:14,870
Next, we have the core scheduler, and this would be used for a higher

19
00:01:14,870 --> 00:01:20,290
security orientation. This allows you to constrain guest virtual

20
00:01:20,290 --> 00:01:24,660
processor cores to physical cores that provide strong isolation. So you

21
00:01:24,660 --> 00:01:29,990
might have one VM attached to one processor core, another VM attached to

22
00:01:29,990 --> 00:01:35,270
another core, and this is to prevent bleeding, data leakage, across those

23
00:01:35,270 --> 00:01:40,130
cores where you have a need, a greater need, to provide strong CPU and

24
00:01:40,130 --> 00:01:41,510
data isolation.

25
00:01:41,510 --> 00:01:45,690
Lastly, there is the root scheduler, and this is the default mode that's

26
00:01:45,690 --> 00:01:50,140
used in Windows client; that is Windows 10 Hyper‑V, Windows 11 Hyper‑V.

27
00:01:50,140 --> 00:01:54,950
This is using the built‑in what's called NT scheduler, just the operating

28
00:01:54,950 --> 00:01:58,740
system scheduler, where the hypervisor hands over control of the

29
00:01:58,740 --> 00:02:00,550
scheduling to the operating system.

30
00:02:00,550 --> 00:02:05,320
So the root scheduler in client Hyper‑V, Hyper‑V doesn't do anything as

31
00:02:05,320 --> 00:02:14,000
far as scheduling work across the VM virtual processors. It just basically punts it to the host operating system.