# Identify the physical GPU before assigning it to a standalone VM

> What evidence is needed before assigning an entire graphics device through Hyper-V DDA?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:14:11+00:00
- Modified: 2026-09-08T18:26:32+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

What evidence is needed before assigning an entire graphics device through Hyper-V DDA?

## 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.

## Article

## Source facts

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](https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Deploying-graphics-devices-using-dda).

## Applicability

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.

## DSE recommendation

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.

## Verification

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.

## Official references

[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.

## Primary reference

- Name: Deploy graphics devices by using Discrete Device Assignment
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Deploying-graphics-devices-using-dda
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Identify the physical GPU before assigning it to a standalone VM,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-180-identify-the-physical-gpu-before-assigning-it-to-a-standalone-vm/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.