Separate Hyper-V startup memory from the post-start minimum

Source facts

Microsoft distinguishes the memory allocated at startup from the minimum allocation used after startup. The post-start minimum permits Hyper-V to reclaim memory that is no longer needed after the guest’s startup phase. Hyper-V also monitors the host operating system’s runtime health when deciding how much memory it can safely allocate to VMs. Microsoft documentation.

Applicability

Identify the guest release, application support requirements, current startup and minimum values, host memory, and expected concurrent VMs. Review all Dynamic Memory settings together before changing a single number.

DSE recommendation

Ask the workload owner to define both a successful restart and acceptable steady-state operation. Record startup memory and the post-start minimum as separate decisions. Choose a representative application load and a restart sequence that includes the other VMs expected to be active on the host.

Verification

Observe guest startup, application readiness, and memory allocation as the workload settles. Repeat under the approved concurrent-host load and compare results with the two memory decisions. Preserve a failed restart or unacceptable steady-state response as a finding rather than treating consolidation density as the only acceptance measure.

Official references

Microsoft Learn: Dynamic Memory for Hyper-V Virtual Machines. Source reviewed September 8, 2026.