{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/", "slug": "dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts", "url": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/" }, "title": "Keep GPU resource-pool names consistent across clustered DDA hosts", "summary": "How should clustered GPU assignment be represented across Hyper-V nodes?", "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:21+00:00", "modified_at": "2026-09-08T18:29:34+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 225, "potentially_affected": "Administrators assigning dedicated GPUs to clustered VMs using DDA.", "dse_recommendation": "Create a per-node GPU inventory linked to the intended shared pool name and VM assignments.", "primary_source": { "name": "Use GPUs with Discrete Device Assignment in clustered VMs on Windows Server and Azure Local", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm", "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 documents dedicating physical GPUs to clustered VMs through DDA as distinct from GPU partitioning. The cluster uses a GPU resource pool to determine placement of VMs assigned to that pool. The PowerShell procedure creates a pool on each server and requires the same pool name on every server. Microsoft Learn.

\n

Applicability

\n

Confirm the supported cluster, GPU, and VM requirements in the current source before preparing pools. Inventory the available hardware on each intended node. Keep a matching pool label separate from proof that every node has suitable hardware and capacity.

\n

DSE recommendation

\n

Create a per-node GPU inventory linked to the intended shared pool name and VM assignments. Have the hardware and virtualization owners review the mapping together. Preserve the host device state and the VM preparation settings before the pilot. Define where the VM should be allowed to start or move and which observed condition will block placement.

\n

Verification

\n

Inspect pool names and membership on every intended host, then assign a representative prepared VM. Verify its actual GPU and workload behavior on the permitted placement paths. Exercise the agreed failover scenario and record the selected node and hardware. Resolve inconsistent names, missing devices, or unexpected placement before assigning more workloads.

\n

Official references

\n

Microsoft Learn: Use GPUs with Discrete Device Assignment in clustered VMs on Windows Server and Azure Local. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft documents dedicating physical GPUs to clustered VMs through DDA as distinct from GPU partitioning. The cluster uses a GPU resource pool to determine placement of VMs assigned to that pool. The PowerShell procedure creates a pool on each server and requires the same pool name on every server. Microsoft Learn.\nApplicability\nConfirm the supported cluster, GPU, and VM requirements in the current source before preparing pools. Inventory the available hardware on each intended node. Keep a matching pool label separate from proof that every node has suitable hardware and capacity.\nDSE recommendation\nCreate a per-node GPU inventory linked to the intended shared pool name and VM assignments. Have the hardware and virtualization owners review the mapping together. Preserve the host device state and the VM preparation settings before the pilot. Define where the VM should be allowed to start or move and which observed condition will block placement.\nVerification\nInspect pool names and membership on every intended host, then assign a representative prepared VM. Verify its actual GPU and workload behavior on the permitted placement paths. Exercise the agreed failover scenario and record the selected node and hardware. Resolve inconsistent names, missing devices, or unexpected placement before assigning more workloads.\nOfficial references\nMicrosoft Learn: Use GPUs with Discrete Device Assignment in clustered VMs on Windows Server and Azure Local. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft documents dedicating physical GPUs to clustered VMs through DDA as distinct from GPU partitioning. The cluster uses a GPU resource pool to determine placement of VMs assigned to that pool. The PowerShell procedure creates a pool on each server and requires the same pool name on every server. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm).\n\n## Applicability\n\nConfirm the supported cluster, GPU, and VM requirements in the current source before preparing pools. Inventory the available hardware on each intended node. Keep a matching pool label separate from proof that every node has suitable hardware and capacity.\n\n## DSE recommendation\n\nCreate a per-node GPU inventory linked to the intended shared pool name and VM assignments. Have the hardware and virtualization owners review the mapping together. Preserve the host device state and the VM preparation settings before the pilot. Define where the VM should be allowed to start or move and which observed condition will block placement.\n\n## Verification\n\nInspect pool names and membership on every intended host, then assign a representative prepared VM. Verify its actual GPU and workload behavior on the permitted placement paths. Exercise the agreed failover scenario and record the selected node and hardware. Resolve inconsistent names, missing devices, or unexpected placement before assigning more workloads.\n\n## Official references\n\n[Microsoft Learn: Use GPUs with Discrete Device Assignment in clustered VMs on Windows Server and Azure Local](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm). 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-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/", "url": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Keep GPU resource-pool names consistent across clustered DDA hosts", "item": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/", "url": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/", "headline": "Keep GPU resource-pool names consistent across clustered DDA hosts", "description": "How should clustered GPU assignment be represented across Hyper-V nodes?", "abstract": "How should clustered GPU assignment be represented across Hyper-V nodes?", "articleBody": "Source facts\nMicrosoft documents dedicating physical GPUs to clustered VMs through DDA as distinct from GPU partitioning. The cluster uses a GPU resource pool to determine placement of VMs assigned to that pool. The PowerShell procedure creates a pool on each server and requires the same pool name on every server. Microsoft Learn.\nApplicability\nConfirm the supported cluster, GPU, and VM requirements in the current source before preparing pools. Inventory the available hardware on each intended node. Keep a matching pool label separate from proof that every node has suitable hardware and capacity.\nDSE recommendation\nCreate a per-node GPU inventory linked to the intended shared pool name and VM assignments. Have the hardware and virtualization owners review the mapping together. Preserve the host device state and the VM preparation settings before the pilot. Define where the VM should be allowed to start or move and which observed condition will block placement.\nVerification\nInspect pool names and membership on every intended host, then assign a representative prepared VM. Verify its actual GPU and workload behavior on the permitted placement paths. Exercise the agreed failover scenario and record the selected node and hardware. Resolve inconsistent names, missing devices, or unexpected placement before assigning more workloads.\nOfficial references\nMicrosoft Learn: Use GPUs with Discrete Device Assignment in clustered VMs on Windows Server and Azure Local. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:13:21+00:00", "dateModified": "2026-09-08T18:29:34+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/" }, "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-230-keep-gpu-resource-pool-names-consistent-across-clustered-dda-hosts/#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": "Keep GPU resource-pool names consistent across clustered DDA hosts" }, "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": 225, "timeRequired": "PT2M", "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": "Use GPUs with Discrete Device Assignment in clustered VMs on Windows Server and Azure Local", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/use-gpu-with-clustered-vm" } } ] } }