Updating from Server 2022 to Server 2025 fails due to limited RAM about mslab HOT 3 OPEN

My investigation found that the update failed because the in-place upgrade is failing to allocate a large enough block of RAM (about 500MB) to set up the ramdisk needed to do the upgrade.

Setting the minimum RAM for the VM to 2048 MB solved the problem.

This is consistent with the minimum RAM documented here:
https://learn.microsoft.com/en-us/windows-server/get-started/hardware-requirements?tabs=cpu

from mslab.

Appreciate your investigation and all the time spent! the specific one to change is the startup RAM from 512MB to 2048 MB (or 2GB). I will try out if this also works with startup RAM of 1GB and if there is any change between 2019 > 2022 IPU behaviour and 2022 > 2025 IPU behaviour.

from mslab.

Checking with mslab24.04, the startup ram and minimum RAM is ok for the hydrated Domain Controller.
@jaromirk I would like to suggest to review the 3_Deploy.ps1 to raise the bar for additional VMs by default.

If not specified in Labconfig, it defaults to 512 MB which is too low for Windows Server with Desktop Experience.
2048 MB is required to avoid issues.

I have no tried if 512MB is enough for Core. Adding the distinguished Edition Core or GUI into the code would require "loosy" checks on the filename of the parentdisk specified in labconfig. This could be prone for failures if users choose different naming for parent files.

MemoryStartupBytes= 512MB; # Startup memory size

proposed fix:
#590

Reference, see information box:
https://learn.microsoft.com/en-us/windows-server/get-started/hardware-requirements?tabs=ram

Thank you for your investigation and assistance @michbern-ms!

from mslab.