A 1st look at Discrete Device Assignment in Hyper-V

Let’s take a 1st look at Discrete Device Assignment in Hyper-V

Discrete Device Assignment (DDA) is the ability to take suitable PCI Express devices in a server and pass them through directly to a virtual machine.

This sounds a lot like SR-IOV that we got in Windows 2012  It might also make you think of virtual Fibre Channel in a VM where you get access to the FC HBA on the host. The concept is similar as in that it giving the physical capabilities to a virtual machine.

But this is about Windows Server 2016 new capability which takes all this a lot further. The biggest use case for this seems to be GPUs and NVMe disks. In environment where absolute speed matters the gains by doing DDA are worth the effort. Especially when this works well with live migrations (not yet as far as I can see right now, and it’s probably quite a challenge).

There a great series of blog post on DDA

Microsoft also has a survey script available to find potential DDA devices on your hosts. It will reporting on which of them meet the criteria for passing them through to a VM.


That script is a very nice educational tool by the way. When I look at one of my servers I find that I have a couple of devices that are potential candidates:

So I’m looking at the Mellanox NICs. I wondered if this is the first step to RDMA in the guest. Probably not. The way I’m seeing the network stack evolve in Windows 2016 that’s the place where that will be handled.


And the Nvidia GRID K1 –  one of the poster childs of DDA and needed to compete in the high end VDI market


And yes the Emulex FC HBAs in the server. This is interesting and I’m curious about the vFC/DDA with FC story. But I have no further info on this. vFC is still there in W2K16 and I don’t think this DDA will replace it.


And finally it showed me the PERC controller as a potential candidate. Now trying to get a PERC 730 exposed to a VM with DDA sounds like and experiment I might just spend some evening hours one just to see where it leads. But only NVMe is supported. But hey a boy can play right?


So we have some lab work to do and we’ll see where we end up when we get TPv5 in our hands. What I also really need to get my hands on are some NVMe disks Smile But soon I’ll publish my findings on configuring this with an NVIDIA GRID K1 GPU.

6 thoughts on “A 1st look at Discrete Device Assignment in Hyper-V

  1. Pingback: Setting up Discrete Device Assignment with a GPU - Working Hard In IT

  2. Can this function be used on Windows 10 Hyper-V host? I really want to install iTunes on a VM and makes my iPhone sync in it, I don’t like iTunes install in a physical machine

    • Just install iTunes in a VM and hookup your smartphone over USB over ethernet. This only works on servers with very specific supported hardware for specific use cases. I’m sure some googling will turn up some ideas for that.

  3. Would this also work with FC HBA cards with a Quantum Scalar i40 tape unit? The tape drives are LTO4 HP drives.

    • I actually messed around a bit with RDMA NICs to try it bu that didn’t work out. A wireless NIC worked once in testing. Haven’t done a FC HBA. You might get it to work if the firmware/driver don’t block it but it’s way deep in unsupported territory so perhaps for some test/dev but I’d stay away from it in production.

Leave a Reply, get the discussion going, share and learn with your peers.

This site uses Akismet to reduce spam. Learn how your comment data is processed.