PROJECTBLUE

After updating to 6.5.1 from 6.5.0 all of my VM's started to experience stuttering and freezing especially under high load such as gaming. Rolled back to 6.5.0 and everything is fine again.

Sorry to resurrect the thread but I have this card too and I have a question and an issue. Which drivers did you use to install the card within the VM? I'm having an issue where the keyboard and mouse attached to the card occasionally freeze up for a second and I lose all control within the VM. This only seems to happen on games. Do you have any input?

I'm referring to the VBIOS of the graphics card. It's not always necessary to use them but with my system it would get stuck on a black screen if I didn't pass the VBIOS ROM to the GPU's. For me it seems that way. I tried to run it headless on my X99 system (no integrated GPU) but every time I tried to boot the VM that was assigned the GPU in the topmost PCIE slot it would not boot the VM (black screen just like if not passing the VBIOS). I just added an old HD5450 dedicated for the unraid GUI and now I have no issues passing my 290X's to individual VM's.

Let me know how it goes! Do you not have a spare PCIE slot to use for a low powered GPU?

You could try passing the ROM to the graphics card. I had this issue too when I only had 2 GPU's, the first GPU in the system just would not allow me to pass it through no matter what I did. To get both of my 290X's passed through to separate VM's I had to add a 3rd GPU in the slot above both 290X's for unraid to use to let me pass them through. I even tried following a guide to run unraid headless but that didn't help at all.

Try my solution of changing the machine type from i440fx to Q35. I was about to give up on unraid too but now everyhting's working perfectly and I plan to buy the license if it continues to work for the rest of the week. I'm just going to avoid using i440fx as it seems to be for older machine types anyway. Q35 from my understanding has better support for PCIE and emulates more modern hardware. i440fx on the other hand emulates older hardware and was built to support PCI.

I was running i440fx too, I would give it a try! When you next boot after changing the machine type windows will sit at a loading screen for a while saying "getting devices ready" but once that's done it will boot straight to windows and everything will be fine. Mine would be very 50/50 on i440fx - sometimes it would show the red x over the speaker icon and I also had the same issue as you there sometimes too, it would show as working correctly etc - but when I actually tried to use the audio or test the device in windows it either just wouldn't play any sound or windows would claim the device was in use by another program. No amounts of reboots/disabling & enabling the device worked for me. The only thing that worked was uninstall all AMD software, reboot then reinstall it all again. Obviously this wasn't viable for a daily use machine. Next time you shut down the machine change the machine type to Q35 and see if it helps. I have had 0 issues using Q35 for the past 24 hours and I've rebooted the host and the VM multiple times. My sound now works perfectly!

I have the Asus X99-E-WS which uses PLX PEX chips, each PCIE slot/device is in its own IOMMU group.* *Some onboard devices share a group but anything useful like LAN port 2, one of the USB controllers and onboard sound are in their own.

I fixed my issues like yours with temperamental audio by changing the machine type from i440fx to Q35. My HDMI audio now initializes perfectly upon every boot and I no longer have the rex X over the sound icon on the task bar.

Just guessing here... but if KVM works anything like Hyper-V does it's required to use a static amount of memory for the virtual machine when passing through PCI-E devices. Something to do with memory allocation for the hardware.

I've managed to get the sound working reliably, after days of Google searching I stumbled upon a reddit thread with someone who had the same problem. He changed his machine type from i440fx to Q35 and all was good. I did this and now my HDMI audio with the actual AMD audio drivers are working correctly even after VM/Host reboots!

Which version of unraid did you not have issues with? I'm tempted to just roll back to a known working version... Spending 20 odd minutes every time I want to use my computer with suitable audio is a pain to say the least.

That sucks, did it start after a certain Windows update or UnRAID update? The only way I can fix mine is to uninstall the AMD drivers and reinstall them upon every reboot of the VM's/UnRAID. As you can probably tell this is a very frustrating thing to have to do, especially when it's on two VM's at a time. (I use this machine as a dual headed gaming machine)

I have tried this and I can't use the Windows drivers as they only allow Stereo audio. The AMD drivers allow me to use 5.1 channel output to my AV receiver.

Okay the "PCI Device" was the Balloon driver & "PCI Simple Communications Controller" was the serial driver. I don't know why it didn't pick these up when I pointed it at the VirtIO CD (including the individual folders) but at least I know for next time, thanks for the help! My HDMI audio still doesn't start when I first start the VM though... I have to disable the device in device manager then re-enable it for it to work...

Having worked in IT with primarily Windows for a few years now I should have thought of that... I've got too used to Windows being able to just auto install everything driver related these days, plus trying to pick up Linux/UnRAID for the past few days having not used either of them much/at all (except the occasional Linux VM to mess about with) is turning my brain into mush it seems haha. I'll give that a try when I get back home and will update the thread with the outcome, thank you. Oh believe me I know, I made that mistake back in the Windows Vista days. It's like clicking "basic install" on a freeware installer... Never again.

I have, it's always mounted int he VM and I've tried searching manually for drivers both in the root of the CD and each of the subfolders where the .INF files are located. In both cases it doesn't seem to find drivers for these devices.

This seems to be the issue, installed an older driver version using the "clean install" option on the driver installer then rebooted and the sound started working again thank you! Hopefully it will continue working properly when I next reboot the machine. Now to figure out what these unknown PCI devices are in device manager...

I have multiple times, I cannot keep the system running 24/7 due to power costs.

Problem 1: I have recently finished setting up my unraid server with two Windows 10 VM's, everything is working great apart from the following: I have a Radeon 290X passed through to one of my Windows 10 VM's. I use HDMI audio from the 290X to my AV receiver, which worked fine for the first day or so but now it will not "see" that I have the HDMI cable plugged in and will not play sound. (Yes I have checked the cables etc) I have passed through the audio part of my GPU and also tried the MSI audio fix. I have tried changing driver versions which doesn't help. The device shows in device manager and playback devices inside the VM. Any further information required I can supply. Problem 2: Inside device manager there are two devices on both of my VM's with no drivers loaded. These devices are named: "PCI Device" & "PCI Simple Communications Controller" - what are these? I have tried to install drivers of any of my PCI-E devices to these unknown devices but they don't seem to match anything I have passed through. These appear on both of my VM's. Any ideas?