{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/", "slug": "dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum", "url": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/" }, "title": "Separate Hyper-V startup memory from the post-start minimum", "summary": "Which memory floor applies while a Dynamic Memory VM starts and after it is running?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:14:16+00:00", "modified_at": "2026-09-08T18:26:31+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 196, "potentially_affected": "Administrators configuring Hyper-V Dynamic Memory for supported guest workloads.", "dse_recommendation": "Ask the workload owner to define both a successful restart and acceptable steady-state operation.", "primary_source": { "name": "Dynamic Memory for Hyper-V Virtual Machines", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/dynamic-memory", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

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

", "content_text": "Source facts\nMicrosoft 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.\nApplicability\nIdentify 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.\nDSE recommendation\nAsk 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.\nVerification\nObserve 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.\nOfficial references\nMicrosoft Learn: Dynamic Memory for Hyper-V Virtual Machines. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft 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](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/dynamic-memory).\n\n## Applicability\n\nIdentify 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.\n\n## DSE recommendation\n\nAsk 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.\n\n## Verification\n\nObserve 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.\n\n## Official references\n\n[Microsoft Learn: Dynamic Memory for Hyper-V Virtual Machines](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/dynamic-memory). Source reviewed September 8, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/", "url": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Separate Hyper-V startup memory from the post-start minimum", "item": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/", "url": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/", "headline": "Separate Hyper-V startup memory from the post-start minimum", "description": "Which memory floor applies while a Dynamic Memory VM starts and after it is running?", "abstract": "Which memory floor applies while a Dynamic Memory VM starts and after it is running?", "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nIdentify 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.\nDSE recommendation\nAsk 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.\nVerification\nObserve 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.\nOfficial references\nMicrosoft Learn: Dynamic Memory for Hyper-V Virtual Machines. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:16+00:00", "dateModified": "2026-09-08T18:26:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-175-separate-hyper-v-startup-memory-from-the-post-start-minimum/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Separate Hyper-V startup memory from the post-start minimum" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 196, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Dynamic Memory for Hyper-V Virtual Machines", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/dynamic-memory" } } ] } }