Error encountered during GPU pass-through to Hyper-V due to "Old Style PCI device" issue.
Error encountered during GPU pass-through to Hyper-V due to "Old Style PCI device" issue.
Hi, I need to replace one of my graphics cards (GTX 1650 Super) in a virtual machine running Hyper-V on Ubuntu 20.04 Focal Fossa. I'm trying to set up a pipeline for a self-driving car simulation that requires 3D rendering. I followed the instructions from Microsoft: https://learn.microsoft.com/en-us/window...-using-dda. When I run the check script at https://learn.microsoft.com/en-us/window...assignment, it says my hardware isn't compatible. It mentions "Old -style PCI device, switch port, etc." and says it can't be assigned. I've enabled I/O Modes, ACS, and SR-IoV in BIOS. Some devices appear assignable after the command, but others seem to use the same GPU for pass-through. Are there any remaining BIOS settings I should adjust? Is my chipset simply not supporting discrete device assignment for graphics cards? It's confusing what "old style PCI device" really means. What's the difference between old and new styles? Are there other names for these configurations besides just "old" or "new"? Is this a software or hardware issue? My setup includes: mainboard Asrock Taichi X470, CPU Ryzen 9 3900X, GPU1 RX 5700X (host), installed in bottom PCIE slot; GPU2 GTX 1650 Super (for pass-through), in top PCIE slot with 32GB RAM on Dominator Platinumx 3200MHz. Host system is Windows 11 Pro, guest Ubuntu 20.04. Thanks, Marco.
WSL2 works with Windows 11 and offers strong performance thanks to audio and GPU integration. Nvidia, AMD, and Intel provide support documentation. More details are available on Microsoft's blog about WSL architecture. You can use Ubuntu, Ubuntu 18.04.6 LTS, Ubuntu 20.04.6 LTS, Ubuntu 22.04.2 LTS and other distributions. If you have time and patience, building your own WSL distribution is possible—everything is open-source. I specifically highlight Ubuntu here, as you mentioned. I haven’t used WSL2 with GPU support before. At work, we do use it and it performs well, delivering impressive results. For optimal disk performance, keep your entire project within the WSL environment. You can access your Linux files via File Explorer once it’s installed. From there, you can launch explorer.exe directly from WSL2, opening files as if they were in Windows. You can also run Windows executables from WSL2, which opens natively. The dot at the end lets you open File Explorer in WSL. I’ve created an alias for convenience. For developers, consult your IDE’s documentation on connecting from Windows to WSL2. Many platforms now support this seamlessly, making the experience feel native. Feel free to ask for more details—WSL2 is developing quickly, and recent updates may change guidance. Microsoft is actively improving this feature.