Hyper V freezes

[fordy1765]

Hi,

    I have a Proliant DL380 G10 server with server 2022 installed. Everything works fine until I install the HyperV role. On rebooting it just hangs almost as soon as it's finished posting. If I disable HyperV in the BIOS it will boot but obviously HyperV wont start. I have tried numerous settings to no avail. I have installed the latest SPP, tried server 2019 and 2025, I've also tried ESXi 7.03 which purple screens as soon as you try to create a VM. It has been back and they have, apparently, replaced the mainboard and processors. The storage controller has also been replaced (HPE Smart Array P408i-a SR Gen10). There are no errors at all on booting. I've wasted days on this and I'm just about at the end of my tether.

Any ideas?

Thanks

Graeme

[Suman_1978]

Hi,

Please see if these documents help you.
https://support.hpe.com/hpesc/public/docDisplay?docId=sf000080049en_us

https://www.hpe.com/psnow/doc/a50003760enw
Page#7, Note It is advised that Secured-core be configured in the BIOS before OS installation and that Secured-core be configured (through registry keys or Windows Admin Center) before roles such as Hyper-V are added.

Thank You!
I work with HPE but opinions expressed here are mine.

[fordy1765]

Hi,

    Many thanks for taking the time to reply. I am looking into this but don't see the option to enable secured-core in the BIOS. Also when going to Device security >> Core isolation >> Turned on Firmware protection isn't available only Memory Integrity . Is there something that I am missing? The OS is 2022 Std btw. The processors are Intel(R) Xeon(R) Platinum 8160 CPU.

Cheers

Graeme

[fordy1765]

@Suman_1978 Further to the fact that Firmware Protection is not available as an option when I enable memory integrity it crashes immediately after posting which is exactly what happens when I install the hyperv role. Maybe this is enabled when installing the role., hence the same result??? When I reset the server it will boot but memory integrity is disabled again. 

This leads me to thinking that something is not configured  in the BIOS. I can see no option for secure-core support in BIOS or in Device Security.