{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/", "slug": "dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count", "url": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/" }, "title": "Select a supported Hyper-V GPU partition count", "summary": "Can administrators choose an arbitrary number of partitions for a GPU?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "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:13:40+00:00", "modified_at": "2026-09-08T18:29:33+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 220, "potentially_affected": "Administrators planning GPU partitioning on Windows Server 2025 Hyper-V hosts.", "dse_recommendation": "Build a placement plan using the counts reported as valid for the installed GPU.", "primary_source": { "name": "Partition and assign GPUs to a virtual machine in Hyper-V", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/partition-assign-vm-gpu", "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 requires Windows Server 2025 on a GPU-partitioning host; the documented clustered live-migration scenario requires Datacenter. The GPU manufacturer defines the valid partition counts, and administrators select from that supported set rather than inventing a count. The Windows Admin Center procedure requires its GPUs extension at version 2.8.0 or later. Microsoft Learn.

\n

Applicability

\n

Identify the actual GPU model, driver, host edition, and management tooling before dividing capacity among guests. Treat a requested number of workloads as a planning input, not evidence that the hardware supports that many partitions. Confirm the source requirements for the intended topology.

\n

DSE recommendation

\n

Build a placement plan using the counts reported as valid for the installed GPU. Have the workload owner describe the expected demand per guest and choose a supported count for an initial trial. Record which guests will receive partitions and how assignments will be reversed. Keep this plan separate from dedicated-device assignment, which addresses a different allocation method.

\n

Verification

\n

Inspect the available counts and resulting partition configuration on each intended host. Confirm the management view recognizes partitioning before assigning a guest. Exercise the representative workload and record its behavior at the chosen partition size; do not present a successful assignment alone as a performance qualification.

\n

Official references

\n

Microsoft Learn: Partition and assign GPUs to a virtual machine in Hyper-V. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft requires Windows Server 2025 on a GPU-partitioning host; the documented clustered live-migration scenario requires Datacenter. The GPU manufacturer defines the valid partition counts, and administrators select from that supported set rather than inventing a count. The Windows Admin Center procedure requires its GPUs extension at version 2.8.0 or later. Microsoft Learn.\nApplicability\nIdentify the actual GPU model, driver, host edition, and management tooling before dividing capacity among guests. Treat a requested number of workloads as a planning input, not evidence that the hardware supports that many partitions. Confirm the source requirements for the intended topology.\nDSE recommendation\nBuild a placement plan using the counts reported as valid for the installed GPU. Have the workload owner describe the expected demand per guest and choose a supported count for an initial trial. Record which guests will receive partitions and how assignments will be reversed. Keep this plan separate from dedicated-device assignment, which addresses a different allocation method.\nVerification\nInspect the available counts and resulting partition configuration on each intended host. Confirm the management view recognizes partitioning before assigning a guest. Exercise the representative workload and record its behavior at the chosen partition size; do not present a successful assignment alone as a performance qualification.\nOfficial references\nMicrosoft Learn: Partition and assign GPUs to a virtual machine in Hyper-V. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft requires Windows Server 2025 on a GPU-partitioning host; the documented clustered live-migration scenario requires Datacenter. The GPU manufacturer defines the valid partition counts, and administrators select from that supported set rather than inventing a count. The Windows Admin Center procedure requires its GPUs extension at version 2.8.0 or later. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/partition-assign-vm-gpu).\n\n## Applicability\n\nIdentify the actual GPU model, driver, host edition, and management tooling before dividing capacity among guests. Treat a requested number of workloads as a planning input, not evidence that the hardware supports that many partitions. Confirm the source requirements for the intended topology.\n\n## DSE recommendation\n\nBuild a placement plan using the counts reported as valid for the installed GPU. Have the workload owner describe the expected demand per guest and choose a supported count for an initial trial. Record which guests will receive partitions and how assignments will be reversed. Keep this plan separate from dedicated-device assignment, which addresses a different allocation method.\n\n## Verification\n\nInspect the available counts and resulting partition configuration on each intended host. Confirm the management view recognizes partitioning before assigning a guest. Exercise the representative workload and record its behavior at the chosen partition size; do not present a successful assignment alone as a performance qualification.\n\n## Official references\n\n[Microsoft Learn: Partition and assign GPUs to a virtual machine in Hyper-V](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/partition-assign-vm-gpu). 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-211-select-a-supported-hyper-v-gpu-partition-count/", "url": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Select a supported Hyper-V GPU partition count", "item": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/", "url": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/", "headline": "Select a supported Hyper-V GPU partition count", "description": "Can administrators choose an arbitrary number of partitions for a GPU?", "abstract": "Can administrators choose an arbitrary number of partitions for a GPU?", "articleBody": "Source facts\nMicrosoft requires Windows Server 2025 on a GPU-partitioning host; the documented clustered live-migration scenario requires Datacenter. The GPU manufacturer defines the valid partition counts, and administrators select from that supported set rather than inventing a count. The Windows Admin Center procedure requires its GPUs extension at version 2.8.0 or later. Microsoft Learn.\nApplicability\nIdentify the actual GPU model, driver, host edition, and management tooling before dividing capacity among guests. Treat a requested number of workloads as a planning input, not evidence that the hardware supports that many partitions. Confirm the source requirements for the intended topology.\nDSE recommendation\nBuild a placement plan using the counts reported as valid for the installed GPU. Have the workload owner describe the expected demand per guest and choose a supported count for an initial trial. Record which guests will receive partitions and how assignments will be reversed. Keep this plan separate from dedicated-device assignment, which addresses a different allocation method.\nVerification\nInspect the available counts and resulting partition configuration on each intended host. Confirm the management view recognizes partitioning before assigning a guest. Exercise the representative workload and record its behavior at the chosen partition size; do not present a successful assignment alone as a performance qualification.\nOfficial references\nMicrosoft Learn: Partition and assign GPUs to a virtual machine in Hyper-V. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:40+00:00", "dateModified": "2026-09-08T18:29:33+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-211-select-a-supported-hyper-v-gpu-partition-count/" }, "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-211-select-a-supported-hyper-v-gpu-partition-count/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Select a supported Hyper-V GPU partition count" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 220, "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": "Partition and assign GPUs to a virtual machine in Hyper-V", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/partition-assign-vm-gpu" } } ] } }