Share via

Hyper-V Dynamic memory fails when you have Memory Integrity on

Theo Verweij 1 Reputation point
2022-11-30T17:39:40.847+00:00

On a Windows 2019 Server with Hyper-V on, I am running a Windows 2019 Server.

The VM has Memory Integrity on and, because Memory Integrity is a Virtualization technology, I also switched on nested Virtualization.

In the VM, the following Event is logged:
Source: Hyper-V-Guest-Drivers
Event ID: 5
Message: The dynamic memory driver failed because a nested instance of Hyper-V was detected.

I know you can not use Dynamic Memory with a nested HyperV server, but I don't think that the VBS should block the use of Dynamic Memory.

The most strange thing is that with multiple VM's, all configured the same, only a few give this message; all others are working fine with VBS and Dynamic Memory.

Is it a bug that Dynamic Memory won't (always) work with VBS security on the VM or is there somewhere a setting that enables this configuration?

Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,749 questions
Windows Server Security
Windows Server Security
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Security: The precautions taken to guard against crime, attack, sabotage, espionage, or another threat.
1,859 questions

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.