[***PSA*** Do not update your BIOS on Ryzen, pass through will not work.]

8 hours ago, david279 said:

There is a bug with the latest ryzen bios that kills pass through right now. Hope newer bios revisions will fix it but there is a patch the fixes the issue but you will need to patch the unRAID kernel for that. Best bet is to revert to a older bios.

Thanks for the information. I attempted to do that but my motherboard doesn’t like it. I have since assumed that was the case and gave up on trying to resurrect my project.

[***PSA*** Do not update your BIOS on Ryzen, pass through will not work.]

I made the mistake of updating the BIOS on my X370 Ryzen board, which completely killed my VM project. Here was my little predicament:

 

I recently updated my BIOS, which changed all of the PCIe device IDs. (i.e. 29:00.0 -> 0a:00.0) Unraid went nuts, and I eventually resorted to starting completely from scratch. I created 2 fresh Windows 10 VMs using VNC, which worked. When I went to pass through my RX 580 to a VM, it starts but then pauses itself. Attempting to resume it results in this error:

internal error: unable to execute QEMU command 'cont': Resetting the Virtual Machine is required

I force stop the VM and attempting to start it again results in this error:

internal error: Unknown PCI header type '127'

I receive the same errors when trying to pass through my RX 570 to the other VM, and they will not do anything until the system is rebooted. 

 

However, my cheap Nvidia GT 710 will pass through and run the VM for a few minutes before giving me a black screen with just the cursor. Attached are my diagnostics.

 

Motherboard: ASUS Crosshair VI Hero (Wi-Fi AC)

CPU: AMD Ryzen 7 1700

RAM: 32GB DDR4-2400MHz
GPUs:

- Nvidia Geforce GT 710

- AMD RX 570 (primary)

- AMD RX 580

 

Any ideas as to what is wrong with the new BIOS?

diagnostics-20190615-1715.zip

[Unraid Virtual Machines: Adobe Creative Cloud, Thin Clients, & Remote Teams]

On 5/26/2019 at 12:33 PM, cypres0099 said:

Thanks for the info @Ep1cPl4yz

 

Scenario 2

 

I guess I don't totally understand the details of how thin clients work. I figured they were just displaying frames rendered from the server onto the workstation monitor. I was figuring wifi would be enough to do that. Is it regular use that would cause the problems over wifi or is it the video editing and things like that?

If you have a recent Wi-Fi router close to where you plan to place your thin clients, you may be able to get away with using 5GHz Wi-Fi for the thin clients, but connecting an UnRAID box to Wi-Fi is never a good idea.

[unraid gpu passthrough on laptop]

1 hour ago, jonp said:

 

Meaning the laptop screen itself won't display anything?

Whatever is using the integrated graphics will probably show up on the built-in display. An external display may be required to see the output of the dedicated GPU.

[unraid gpu passthrough on laptop]

I have had success with passing the primary GPU and a secondary one in a desktop and then switching using OS settings. Install your OS using VNC then pass through both GPUs to the same VM and see what happens. You may need to attach an external display to a video output port for it to work.

[Unraid Virtual Machines: Adobe Creative Cloud, Thin Clients, & Remote Teams]

Scenario 1, hence the name, is pretty basic and can easily be done with the correct hardware. A three-monitor setup is easy if there are enough video outputs on your GPU. Yes, it would function almost identically to a standalone desktop with similar specs. It would not interfere with dockers provided that there are enough resources left over for Unraid to use for them.

 

Scenario 2 is feasible with the correct hardware. Just make sure there is a solid Ethernet connection between the server and thin clients. Look into using Thunderbolt to connect a dock to the server, such as this one from Elgato. Same as above otherwise.

 

Scenario 3 is completely out of the question unless you have an insanely fast internet connection for the server, and a pretty decent one for the remote clients. Chances are your ISP does not sell a fast enough internet connection to support multiple remote users simultaneously. It would probably be cheaper to build and send each of your team members a new mid-range system than to pay for an insanely fast internet connection every month.