Server 2022 boot loops after Hyper-V role installation on Atom processor

Question

Server 2022 boot loops after Hyper-V role installation on Atom processor

Martin Wolter 6

Dear all.

I ran some tests with Server 2022 standard and data center edition on Intel Atom C3000 and found that it gets stuck in a boot loop after installing the Hyper-V role. The old trick from Server 2019 to switch to BIOS mode instead of UEFI doesn't seem to work anymore. This happens independently from

core mode or desktop experience
use windows internal drivers or Intel Chipset / NIC drivers
VT-d / SRIOV enabled or disabled in BIOS (VT-x is enabled of course)

Then I tried using a XEON processor and it worked smoothly at first try. So, I consider the Atom processor to be the problem here.

Any ideas, how to get the Hyper-V role up and running on Denverton?
Thanks for any help.

Martin

Hardware used:

Atom: Supermicro A2SDI-H-TP4F
XEON: Supermicro X10SDV-6C+-TLN4F
64 GB ECC DDR4 RAM
250 GB Samsung EVO SSD

perpetualKid 6 Reputation points

2021-11-02T09:59:41.35+00:00

maybe related issues on an Asrock C3758D4I-4L platform as well: failed upgrade from 2019 in a couple trials, until we disabled the automatic update check during installation. Upgrade went fine thereafter (desktop experience), UEFI, VT-d, SRIOV all enabled, and Hyper-V role installed as well.
However installing Cumulative Updates afterwards (2021-10 for Microsoft server operating system version 21H2 for x64-based Systems (KB5006699)) fails with error 0x800F0923 and ends in a boot loop each time, so we have to use safe mode and roll back.

Other updates (Defender, .NET) install just fine.

Also, while all other hardware runs fine in device manager, now got a problem with "Microsoft Generic IPMI Compliant Device" - device cannot start. (Code 10). The object was not found. Not sure what we are missing, except the direct ink to BMC in Windows Admin Center doesn't show anymore.
Pobably something related to specific chipset and drivers.
RvdH 6 Reputation points

2021-11-02T10:33:47.257+00:00

Yes, i also seem to have the same issue as described by perpetualkid and MartinWolter while trying to enable the Hyper-V role on Windows Server 2022 on a Intel NUC6CAYH with Celeron Processor J3455
This unit previously had Windows Server 2019 on this unit and before that Windows Server 2016 and both worked without issues with Hyper-V role installed

When using the en-us_windows_server_2022_x64_dvd_620d7eac.iso (RTM release) iso I am able to install Hyper-V role, but after installing cumulative updates afterwards it goes into this boot loop as described above, only solution is to start in safe mode and the Hyper-V role installation is rolled back.

Using en-us_windows_server_version_2022_updated_october_2021_x64_dvd_b6e25591.iso i go into this boot loop immediately and again only solution is to start in safe mode and the Hyper-V role installation is rolled back.

VT-d enabled/disabled doesn't seem to make any difference, VT-x is enabled and SRIOV is not available on a NUC6CAYH

The fact it works fine on the RTM release, makes me wonder if some update (for example KB5006699 listed above) breaks something related to the Hyper-V Role?
Please fix this Microsoft!

RvdH 6

I digged in a bit further

Minimum:

1,4 GHz 64-bit processor
Compatible with x64 instruction set
Supports NX and DEP
Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW
Supports Second Level Address Translation (EPT or NPT)

Coreinfo, part of Windows Sysinternals, is a tool you can use to confirm which of these capabilities your CPU has.

CoreInfo excerpt:

Intel(R) Celeron(R) CPU J3455 @ 1.50GHz  
Intel64 Family 6 Model 92 Stepping 9, GenuineIntel  
Microcode signature: 00000046  
VMX       	*	Supports Intel hardware-assisted virtualization  
X64       	*	Supports 64-bit mode  
NX        	*	Supports no-execute page protection  
CX16      	*	Supports CMPXCHG16B instruction  
LAHF-SAHF 	*	Supports LAHF/SAHF instructions in 64-bit mode  
PREFETCHW 	*	Supports PREFETCHW instruction

CoreInfo -V excerpt:

Intel(R) Celeron(R) CPU J3455 @ 1.50GHz  
Intel64 Family 6 Model 92 Stepping 9, GenuineIntel  
Microcode signature: 00000046  
VMX       	*	Supports Intel hardware-assisted virtualization  
EPT       	*	Supports Intel extended page tables (SLAT)

looking at the output the Celeron Processor J3455 seems to meet the requirements and should work

perpetualKid 6 Reputation points

2021-11-03T13:41:38.75+00:00

runs fine over here on a J3455 Celeron platform (also Hyper-V enabled) which was upgraded from 2016->2019->2022 out of the RTM Iso en-us_windows_server_2022_x64_dvd_620d7eac.iso and patched all up.
Not sure if KB5006699 is applied, can't find in the update history, and trying to manually apply only gives me a generic "Not applicable" message.
RvdH 6 Reputation points

2021-11-03T17:01:34.007+00:00

If bcdedit contains hypervisorlaunchtype=auto the system boot (loops) directly in recovery mode, with hypervisorlaunchtype=off it boots fine

Really strange....
RvdH 6 Reputation points

2021-11-05T12:49:34.387+00:00

addendum:
I have found out this seem to be related to be able to enable the Core isolation toggle (which is partly based on virtualization as well) on NUC6CAYH (Apollolake)

10.0.20348.169 (RTM) (Clean install)

Install Hyper-V Role Successful
Core isolation toggle Successful

10.0.20348.230 (KB5005575) (Clean install)

Install Hyper-V Role Unsuccessful
Core isolation toggle Unsuccessful

10.0.20348.169 (RTM) (Clean install)

Install Hyper-V Role Successful
Core isolation toggle Successful

10.0.20348.230 (KB5005575) (Update)

We couldn't complete the updates
Undoing changes
Don't turn off you computer
Martin Wolter 6 Reputation points

2021-11-06T16:56:44.237+00:00
I can confirm that Hyper-V works on the RTM version without any updates. But installing any cumulative update leads to the boot loops.

Here is the output of coreinfo -v of the Atom board (after fresh install / without enabling Hyper-V):

Intel(R) Atom(TM) CPU C3958 @ 2.00GHz Intel64 Family 6 Model 95 Stepping 1, GenuineIntel Microcode signature: 00000034 HYPERVISOR - Hypervisor is present VMX * Supports Intel hardware-assisted virtualization EPT * Supports Intel extended page tables (SLAT) URG * Supports Intel unrestricted guest

Does Microsoft actually read this board? And how do we get them to fix this?

Martin Wolter 6

Interestingly, here is the result from coreinfo -v after installing the hyper-v role

Intel(R) Atom(TM) CPU C3958 @ 2.00GHz
Intel64 Family 6 Model 95 Stepping 1, GenuineIntel
Microcode signature: 00000034
HYPERVISOR      *       Hypervisor is present
VMX             -       Supports Intel hardware-assisted virtualization
EPT             -       Supports Intel extended page tables (SLAT)
URG             -       Supports Intel unrestricted guest

Is this on purpose, that everything that was available / supported wihtout hyper-v is now not available / not supported any more?

Martin Wolter 6 Reputation points

2021-11-06T18:20:03.81+00:00

Update: The doesn't seem to be the problem. The result is exactly the same with Server 2016 and Hyper-V running smoothly.
RvdH 6 Reputation points

2021-11-07T08:37:37.92+00:00
Note: Coreinfo must be executed on a system without a hypervisor running for accurate results.

For accurate results about hypervisor capabilities you need to run it without the hypervisor enabled as displayed
Martin Wolter 6 Reputation points

2021-11-07T09:36:00.747+00:00

Yes, of course you're right with this.
The important point is, that the Atom CPU fulfills the Hyper-V requirements prior to enabling the role, but then doesn't work with Hyper-V installed.
RvdH 6 Reputation points

2021-11-07T13:28:32.4+00:00

I get exactly the same as you, only difference mine is equipped with a Celeron Processor J3455
But this is extra confusing as perpetualKid said he got it working without issues on Celeron Processor J3455 platform, what the hell?

Because of that, big chance it is not the processor that is the issue, but maybe a missing UEFI variable?
Martin Wolter 6 Reputation points

2021-11-08T07:33:32.64+00:00
It worked using the RTM version which means one of the following

After the update, Microsoft requests additional information from UEFI/BIOS which was not necessary initially or in Server 2016 / 2019

Microsoft made mistakes in the update

Microsoft added additional features which now block operation

So, I cleary see the fault on Microsoft's side here.
BTW: The newest BIOS version is installed (rev. 1.5 on the Atom board). Still not working.
Martin Wolter 6 Reputation points

2021-12-21T11:59:02.913+00:00

Still no change with CU 12-2021.
Probably, I need to wait until the next functional update.
Dave Boulden 6 Reputation points

2022-01-07T19:57:53.15+00:00

I am also experiencing this incredibly frustrating issue on my SuperMicro A2SDi-16C-HLN4F Intel C3955 equipped board withy a new installation of Win Server 2022 Standard. It is also preventing me from running Docker Desktop on the machine.
RvdH 6 Reputation points

2022-07-23T09:52:48.853+00:00

Is this finally fixed?
I gave it another go today, and as it seems so far the hyper-v role now install without issues... Windows Defender Core isolation toggle seems to work as well
Dave Boulden 6 Reputation points

2022-07-23T10:42:08.16+00:00

I certainly hope so, I'll give it a go myself and see if it is.
Dave Boulden 6 Reputation points

2022-07-23T14:23:36.417+00:00

That's confirmed, I now have Hyper-V running on my C3955 based server running Win Server 2022 Standard.
perpetualKid 6 Reputation points

2022-07-23T18:38:57.307+00:00

confirmed on Atom C3758 as well!

1 answer

Your answer

perpetualKid 6 Reputation points

2021-11-02T09:59:41.35+00:00

maybe related issues on an Asrock C3758D4I-4L platform as well: failed upgrade from 2019 in a couple trials, until we disabled the automatic update check during installation. Upgrade went fine thereafter (desktop experience), UEFI, VT-d, SRIOV all enabled, and Hyper-V role installed as well.
However installing Cumulative Updates afterwards (2021-10 for Microsoft server operating system version 21H2 for x64-based Systems (KB5006699)) fails with error 0x800F0923 and ends in a boot loop each time, so we have to use safe mode and roll back.

Other updates (Defender, .NET) install just fine.

Also, while all other hardware runs fine in device manager, now got a problem with "Microsoft Generic IPMI Compliant Device" - device cannot start. (Code 10). The object was not found. Not sure what we are missing, except the direct ink to BMC in Windows Admin Center doesn't show anymore.
Pobably something related to specific chipset and drivers.
RvdH 6 Reputation points

2021-11-02T10:33:47.257+00:00

Yes, i also seem to have the same issue as described by perpetualkid and MartinWolter while trying to enable the Hyper-V role on Windows Server 2022 on a Intel NUC6CAYH with Celeron Processor J3455
This unit previously had Windows Server 2019 on this unit and before that Windows Server 2016 and both worked without issues with Hyper-V role installed

When using the en-us_windows_server_2022_x64_dvd_620d7eac.iso (RTM release) iso I am able to install Hyper-V role, but after installing cumulative updates afterwards it goes into this boot loop as described above, only solution is to start in safe mode and the Hyper-V role installation is rolled back.

Using en-us_windows_server_version_2022_updated_october_2021_x64_dvd_b6e25591.iso i go into this boot loop immediately and again only solution is to start in safe mode and the Hyper-V role installation is rolled back.

VT-d enabled/disabled doesn't seem to make any difference, VT-x is enabled and SRIOV is not available on a NUC6CAYH

The fact it works fine on the RTM release, makes me wonder if some update (for example KB5006699 listed above) breaks something related to the Hyper-V Role?
Please fix this Microsoft!
RvdH 6 Reputation points

2021-11-03T12:00:44.07+00:00

I digged in a bit further

Minimum:

1,4 GHz 64-bit processor
Compatible with x64 instruction set
Supports NX and DEP
Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW
Supports Second Level Address Translation (EPT or NPT)

Coreinfo, part of Windows Sysinternals, is a tool you can use to confirm which of these capabilities your CPU has.

CoreInfo excerpt:

Intel(R) Celeron(R) CPU J3455 @ 1.50GHz Intel64 Family 6 Model 92 Stepping 9, GenuineIntel Microcode signature: 00000046 VMX * Supports Intel hardware-assisted virtualization X64 * Supports 64-bit mode NX * Supports no-execute page protection CX16 * Supports CMPXCHG16B instruction LAHF-SAHF * Supports LAHF/SAHF instructions in 64-bit mode PREFETCHW * Supports PREFETCHW instruction

CoreInfo -V excerpt:

Intel(R) Celeron(R) CPU J3455 @ 1.50GHz Intel64 Family 6 Model 92 Stepping 9, GenuineIntel Microcode signature: 00000046 VMX * Supports Intel hardware-assisted virtualization EPT * Supports Intel extended page tables (SLAT)

looking at the output the Celeron Processor J3455 seems to meet the requirements and should work
perpetualKid 6 Reputation points

2021-11-03T13:41:38.75+00:00

runs fine over here on a J3455 Celeron platform (also Hyper-V enabled) which was upgraded from 2016->2019->2022 out of the RTM Iso en-us_windows_server_2022_x64_dvd_620d7eac.iso and patched all up.
Not sure if KB5006699 is applied, can't find in the update history, and trying to manually apply only gives me a generic "Not applicable" message.
RvdH 6 Reputation points

2021-11-03T17:01:34.007+00:00

If bcdedit contains hypervisorlaunchtype=auto the system boot (loops) directly in recovery mode, with hypervisorlaunchtype=off it boots fine

Really strange....
RvdH 6 Reputation points

2021-11-05T12:49:34.387+00:00

addendum:
I have found out this seem to be related to be able to enable the Core isolation toggle (which is partly based on virtualization as well) on NUC6CAYH (Apollolake)

10.0.20348.169 (RTM) (Clean install)

Install Hyper-V Role Successful
Core isolation toggle Successful

10.0.20348.230 (KB5005575) (Clean install)

Install Hyper-V Role Unsuccessful
Core isolation toggle Unsuccessful

10.0.20348.169 (RTM) (Clean install)

Install Hyper-V Role Successful
Core isolation toggle Successful

10.0.20348.230 (KB5005575) (Update)

We couldn't complete the updates
Undoing changes
Don't turn off you computer
Martin Wolter 6 Reputation points

2021-11-06T16:56:44.237+00:00

I can confirm that Hyper-V works on the RTM version without any updates. But installing any cumulative update leads to the boot loops.

Here is the output of coreinfo -v of the Atom board (after fresh install / without enabling Hyper-V):

Intel(R) Atom(TM) CPU C3958 @ 2.00GHz Intel64 Family 6 Model 95 Stepping 1, GenuineIntel Microcode signature: 00000034 HYPERVISOR - Hypervisor is present VMX * Supports Intel hardware-assisted virtualization EPT * Supports Intel extended page tables (SLAT) URG * Supports Intel unrestricted guest

Does Microsoft actually read this board? And how do we get them to fix this?
Martin Wolter 6 Reputation points

2021-11-06T18:00:42.443+00:00

Interestingly, here is the result from coreinfo -v after installing the hyper-v role

Intel(R) Atom(TM) CPU C3958 @ 2.00GHz Intel64 Family 6 Model 95 Stepping 1, GenuineIntel Microcode signature: 00000034 HYPERVISOR * Hypervisor is present VMX - Supports Intel hardware-assisted virtualization EPT - Supports Intel extended page tables (SLAT) URG - Supports Intel unrestricted guest

Is this on purpose, that everything that was available / supported wihtout hyper-v is now not available / not supported any more?
Martin Wolter 6 Reputation points

2021-11-06T18:20:03.81+00:00

Update: The doesn't seem to be the problem. The result is exactly the same with Server 2016 and Hyper-V running smoothly.
RvdH 6 Reputation points

2021-11-07T08:37:37.92+00:00

Note: Coreinfo must be executed on a system without a hypervisor running for accurate results.

For accurate results about hypervisor capabilities you need to run it without the hypervisor enabled as displayed
Martin Wolter 6 Reputation points

2021-11-07T09:36:00.747+00:00

Yes, of course you're right with this.
The important point is, that the Atom CPU fulfills the Hyper-V requirements prior to enabling the role, but then doesn't work with Hyper-V installed.
RvdH 6 Reputation points

2021-11-07T13:28:32.4+00:00

I get exactly the same as you, only difference mine is equipped with a Celeron Processor J3455
But this is extra confusing as perpetualKid said he got it working without issues on Celeron Processor J3455 platform, what the hell?

Because of that, big chance it is not the processor that is the issue, but maybe a missing UEFI variable?
Martin Wolter 6 Reputation points

2021-11-08T07:33:32.64+00:00

It worked using the RTM version which means one of the following

After the update, Microsoft requests additional information from UEFI/BIOS which was not necessary initially or in Server 2016 / 2019

Microsoft made mistakes in the update

Microsoft added additional features which now block operation

So, I cleary see the fault on Microsoft's side here.
BTW: The newest BIOS version is installed (rev. 1.5 on the Atom board). Still not working.
Martin Wolter 6 Reputation points

2021-12-21T11:59:02.913+00:00

Still no change with CU 12-2021.
Probably, I need to wait until the next functional update.
Dave Boulden 6 Reputation points

2022-01-07T19:57:53.15+00:00

I am also experiencing this incredibly frustrating issue on my SuperMicro A2SDi-16C-HLN4F Intel C3955 equipped board withy a new installation of Win Server 2022 Standard. It is also preventing me from running Docker Desktop on the machine.
RvdH 6 Reputation points

2022-07-23T09:52:48.853+00:00

Is this finally fixed?
I gave it another go today, and as it seems so far the hyper-v role now install without issues... Windows Defender Core isolation toggle seems to work as well
Dave Boulden 6 Reputation points

2022-07-23T10:42:08.16+00:00

I certainly hope so, I'll give it a go myself and see if it is.
Dave Boulden 6 Reputation points

2022-07-23T14:23:36.417+00:00

That's confirmed, I now have Hyper-V running on my C3955 based server running Win Server 2022 Standard.
perpetualKid 6 Reputation points

2022-07-23T18:38:57.307+00:00

confirmed on Atom C3758 as well!

Answer 1

Anonymous

I'd start by checking here and with manufacturer about support for Server 2022.
https://www.windowsservercatalog.com/

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

Martin Wolter 6 Reputation points

2021-11-07T10:00:44.607+00:00

Neither Atom C39XX nor XEON D15XX are on the list. At least D15XX works anyway.
On the other hand Atom C33XX is on the list which has the same properties but less cores / computational power. Sounds inconsistent to me or the list is simply incomplete.

Share via

Server 2022 boot loops after Hyper-V role installation on Atom processor

1 answer

Your answer