Setting Minimum memory size causes driver locked RAM

Apps and Virtualization
,
1

When running a Windows 11 VM, if I set the Minimum Memory size to 4Gib and Memory size to 16Gib, RAM usage sits at around 90% (12GB used), and RAMMap shows it’s due to a driver lock. When the system needs to use more than 4 GB of ram, it does free up some from the driver lock, but it still runs like crap, and causes apps to crash.

As soon as a remove the Minimum Memory size and reboot, it runs fine, and the ram is released.

Threadripper 2950X
64Gb RAM

Hyper-V Enlightenments enabled
CPU Mode: Host Passthrough
Disk: AHCI mode
NIC: VirtIO mode

I’ve installed the VirtIO drivers, as well as the VM tools, as per the proxmox VirtIO drivers page.

Any suggestions?

2

This is how memory “ballooning” works.

The VM appears to be allocated the full amount of memory, the balloon is inflated to take away the “unused” portion, thus forcing the VM to page out / discard other allocated memory portions.

Personally, I found it unstable and would not recommend.