none
Win Server 2016 v1709 - Element not found when starting VMs with passthrough GPUs RRS feed

  • Question

  • This configuration worked under Windows Server 2016 v1607.  GPU01 is being passed through to VM01, GPU02 is being passed through to VM02.  Oddly enough, I am able to pass through the HDMI audio component without any issues, but if the GPU itself is assigned, the VMs issue the following error when trying to start.

    Virtual Pci Express Port (Instance ID 9EA1922C-4417-4057-91C3-CF95E1D7F092): Failed to Power on with Error 'Element
    not found.'.
    'VM01' failed to start. (Virtual machine ID 89D10D4E-00E5-4E4C-977B-048C7201EDA7)
    'VM01' Virtual Pci Express Port (Instance ID 9EA1922C-4417-4057-91C3-CF95E1D7F092): Failed to Power on with Error
    'Element not found.' (0x80070490). (Virtual machine ID 89D10D4E-00E5-4E4C-977B-048C7201EDA7)
    Could not allocate the PCI Express device with the Plug and Play Device Instance path
    'PCIP\VEN_1002&DEV_67DF&SUBSYS_04B01043&REV_CF\4&10A35DAE&0&0010' because it is already in use by another VM.

    Now the "already in use by another VM" is misleading, because I've triple checked that they are not assigned to other VMs, and it appears that this message appears for other errors where passthrough is not working as well.  Any thoughts on this?

    Sunday, February 4, 2018 8:52 PM

All replies

  • Hello,

    Please make sure that the GPUs are DDA capable. You can run the following script for checking it.

    https://github.com/MicrosoftDocs/Virtualization-Documentation/tree/master/hyperv-samples/benarm-powershell/DDA

    Additionally, the following blog article is a good resource for configuring DDA with GPU.

    https://blog.workinghardinit.work/2016/04/11/discrete-device-assignment-in-windows-server-2016-hyper-v/

    Best regards,

    Andy Liu 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, February 5, 2018 7:55 AM
  • The script returns the following message, but it's important to note that the passthrough was working until I installed v1709.  There must be a difference between how passthrough worked in v1607 and v1709.

    Traffic from this device may be redirected to other devices in the system.  Not assignable.

    Monday, February 5, 2018 8:49 AM
  • Hello,

    actually, I've the same issue, with Windows 2019 (1809), same style of error message, but only different IDs. (VEN 1002 (ATI/AMD), DEV 6985 (Radeon Pro WX 3100))

    My Mainboard does DDA, as there was no issues with Windows 2016.

    (it's even the same effect, where I cannot pass the GPU itself, but the Audio part can be passed over)

    Vulpes

    Sunday, January 27, 2019 7:36 PM
  • Same for me using a pny Quadro P4000. Have you been able to resolve this issue?
    Saturday, February 16, 2019 5:29 PM
  • Hello,

    actually, I've the same issue, with Windows 2019 (1809), same style of error message, but only different IDs. (VEN 1002 (ATI/AMD), DEV 6985 (Radeon Pro WX 3100))

    My Mainboard does DDA, as there was no issues with Windows 2016.

    (it's even the same effect, where I cannot pass the GPU itself, but the Audio part can be passed over)

    Vulpes

    Same Here. 

    Server 2019 Std. - AMD Radeon RX550

    as soon as i passthrough the gpu the vm will not start - "already used by another vm" - what is absolutly not the case.

    Best

    Stefan

    • Edited by St.Benner Monday, February 18, 2019 9:25 PM
    Monday, February 18, 2019 6:23 PM
  • Did someone found a solution? still searching and my server 2019 is still without gpu power :(

    best

    Stefan

    Friday, February 22, 2019 1:36 PM
  • Still no solution, I'm about to give up any hope for an update to solve this. I think I may switch to esxi or something. I have projects still on hold after losing passthru ability on my WX7100 GPU from the 2016 to 2019 upgrade I foolishly applied to my host many months ago.

    Friday, April 5, 2019 12:43 AM
  • tried it aigan with the latest patchlevel... still not working. What is needed that MS takes care?
    Friday, June 7, 2019 9:45 PM
  • Still broken on 2019.
    Friday, July 12, 2019 12:22 PM
  • i am about to give up. it is a shame. especialy for small business customers... seems like no one from MS takes care of this and it is something that "works as desinged"...
    Sunday, September 15, 2019 8:26 PM
  • I've been trying for way too long now to pass a Quadro P2200, thought it was the card but NVidia says the Quadro 2000+ should be able to be DDA.

    Looking at this post I think I'm getting the same "Object Not Found" error message others are getting when trying to start the VM.

    Has anybody found a solution to this issue.

    Thanks.

    Thursday, October 3, 2019 12:57 PM
  • Hey ptola,

    until now we did not find a solution. i think we also tried with server 2019 but i am not quite sure about that.

    it is a shame to be honest...

    Friday, October 11, 2019 9:46 PM
  • Tried with esxi 6.7, everything worked fine, was able to pass the GPU without any problems.

    A friend of mine told me today that he had been successful in doing it, but he lost his powershell scripts, so I tried again and after a couple of hours of setting everything up, Fail! still not working.

    This is very frustrating.

    Thursday, October 17, 2019 1:34 AM
  • I've been trying for way too long now to pass a Quadro P2200, thought it was the card but NVidia says the Quadro 2000+ should be able to be DDA.

    Looking at this post I think I'm getting the same "Object Not Found" error message others are getting when trying to start the VM.

    Has anybody found a solution to this issue.

    Thanks.

    I have a Quadro K2200 that was passing through without issue in Server 2016.  Now in 2019 I get the same errors.

    Aside from the OS difference I did install datacenter core instead of datacenter desktop.  I'm not sure if this is an issue.

    I also have not installed the Video drivers on the host this time around.

    I do plan on giving it another go with a Desktop version of the OS.  But I really see no reason why that would make a difference at this time.


    Please remember to mark my replies as answers if they help

    Sunday, October 20, 2019 10:37 PM
  • I do plan on giving it another go with a Desktop version of the OS.  But I really see no reason why that would make a difference at this time.

    I Have now had a chance to install Server 2019 Desktop Experience and it exhibits the same issue as with Server 2019 core. 

    On the Actual How to Page someone does make mention that it worked for them with Server Core 1903.  I may attempt that route and see how it goes.

    https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/deploying-graphics-devices-using-dda


    Please remember to mark my replies as answers if they help

    Sunday, November 10, 2019 10:12 PM