{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/", "slug": "dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm", "url": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/" }, "title": "Identify the physical GPU before assigning it to a standalone VM", "summary": "What evidence is needed before assigning an entire graphics device through Hyper-V DDA?", "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:14:11+00:00", "modified_at": "2026-09-08T18:26:32+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 2, "word_count": 224, "potentially_affected": "Administrators assigning graphics devices to VMs on standalone Hyper-V hosts.", "dse_recommendation": "Run the documented hardware survey in the approved assessment environment and review the result with the hardware owner.", "primary_source": { "name": "Deploy graphics devices by using Discrete Device Assignment", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Deploying-graphics-devices-using-dda", "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 Discrete Device Assignment as passing a whole PCIe device to a VM on a standalone, nonclustered Hyper-V host. The device location path identifies the hardware for host dismount and mount operations. A vendor-supplied mitigation driver is separate from the guest device driver and, when provided, should be installed before the device is dismounted from the host. Microsoft Learn.

\n

Applicability

\n

Confirm that the intended deployment is standalone rather than clustered. Identify the server, VM, physical adapter, and vendor guidance before choosing the device. Keep full-device assignment distinct from GPU partitioning and from clustered VM GPU support.

\n

DSE recommendation

\n

Run the documented hardware survey in the approved assessment environment and review the result with the hardware owner. Record the device location path against the physical inventory, then have a second operator verify the match. Resolve the vendor mitigation-driver decision before planning the host change. Document the intended guest driver and a procedure for returning the device to host use.

\n

Verification

\n

During the controlled pilot, verify that the intended device is assigned to the intended VM and that the guest reports the expected hardware. Exercise the required graphics workload and record actual results. Confirm the planned removal and return path in the test environment before assigning additional devices.

\n

Official references

\n

Microsoft Learn: Deploy graphics devices by using Discrete Device Assignment. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft documents Discrete Device Assignment as passing a whole PCIe device to a VM on a standalone, nonclustered Hyper-V host. The device location path identifies the hardware for host dismount and mount operations. A vendor-supplied mitigation driver is separate from the guest device driver and, when provided, should be installed before the device is dismounted from the host. Microsoft Learn.\nApplicability\nConfirm that the intended deployment is standalone rather than clustered. Identify the server, VM, physical adapter, and vendor guidance before choosing the device. Keep full-device assignment distinct from GPU partitioning and from clustered VM GPU support.\nDSE recommendation\nRun the documented hardware survey in the approved assessment environment and review the result with the hardware owner. Record the device location path against the physical inventory, then have a second operator verify the match. Resolve the vendor mitigation-driver decision before planning the host change. Document the intended guest driver and a procedure for returning the device to host use.\nVerification\nDuring the controlled pilot, verify that the intended device is assigned to the intended VM and that the guest reports the expected hardware. Exercise the required graphics workload and record actual results. Confirm the planned removal and return path in the test environment before assigning additional devices.\nOfficial references\nMicrosoft Learn: Deploy graphics devices by using Discrete Device Assignment. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft documents Discrete Device Assignment as passing a whole PCIe device to a VM on a standalone, nonclustered Hyper-V host. The device location path identifies the hardware for host dismount and mount operations. A vendor-supplied mitigation driver is separate from the guest device driver and, when provided, should be installed before the device is dismounted from the host. [Microsoft Learn](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Deploying-graphics-devices-using-dda).\n\n## Applicability\n\nConfirm that the intended deployment is standalone rather than clustered. Identify the server, VM, physical adapter, and vendor guidance before choosing the device. Keep full-device assignment distinct from GPU partitioning and from clustered VM GPU support.\n\n## DSE recommendation\n\nRun the documented hardware survey in the approved assessment environment and review the result with the hardware owner. Record the device location path against the physical inventory, then have a second operator verify the match. Resolve the vendor mitigation-driver decision before planning the host change. Document the intended guest driver and a procedure for returning the device to host use.\n\n## Verification\n\nDuring the controlled pilot, verify that the intended device is assigned to the intended VM and that the guest reports the expected hardware. Exercise the required graphics workload and record actual results. Confirm the planned removal and return path in the test environment before assigning additional devices.\n\n## Official references\n\n[Microsoft Learn: Deploy graphics devices by using Discrete Device Assignment](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Deploying-graphics-devices-using-dda). 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-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/", "url": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Identify the physical GPU before assigning it to a standalone VM", "item": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/", "url": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/", "headline": "Identify the physical GPU before assigning it to a standalone VM", "description": "What evidence is needed before assigning an entire graphics device through Hyper-V DDA?", "abstract": "What evidence is needed before assigning an entire graphics device through Hyper-V DDA?", "articleBody": "Source facts\nMicrosoft documents Discrete Device Assignment as passing a whole PCIe device to a VM on a standalone, nonclustered Hyper-V host. The device location path identifies the hardware for host dismount and mount operations. A vendor-supplied mitigation driver is separate from the guest device driver and, when provided, should be installed before the device is dismounted from the host. Microsoft Learn.\nApplicability\nConfirm that the intended deployment is standalone rather than clustered. Identify the server, VM, physical adapter, and vendor guidance before choosing the device. Keep full-device assignment distinct from GPU partitioning and from clustered VM GPU support.\nDSE recommendation\nRun the documented hardware survey in the approved assessment environment and review the result with the hardware owner. Record the device location path against the physical inventory, then have a second operator verify the match. Resolve the vendor mitigation-driver decision before planning the host change. Document the intended guest driver and a procedure for returning the device to host use.\nVerification\nDuring the controlled pilot, verify that the intended device is assigned to the intended VM and that the guest reports the expected hardware. Exercise the required graphics workload and record actual results. Confirm the planned removal and return path in the test environment before assigning additional devices.\nOfficial references\nMicrosoft Learn: Deploy graphics devices by using Discrete Device Assignment. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:11+00:00", "dateModified": "2026-09-08T18:26:32+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/" }, "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-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/#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": "Identify the physical GPU before assigning it to a standalone VM" }, "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": 224, "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": "Deploy graphics devices by using Discrete Device Assignment", "url": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Deploying-graphics-devices-using-dda" } } ] } }