DataHearth Posted August 30, 2020 Share Posted August 30, 2020 Hello there, I'm fairly new UNRAID. I've setup my server 3 days ago with a windows 10 VM (GPU and CPU passthrough). I'm having issue to passed the built in audio controller provided by my motherboard (motherboard: asus z170 pro g => audio controller: Intel 100 Series/C230 Series Chipset Family HD Audio Controller (00:1f.3)). I'm using the GPU's audio controller (NVIDIA GTX1070) and my internal display audio output to plug my speakers. Problem is, after some time or something describe in this thread: UNRAID post . So I've tried another time to add my intel audio controller to my VM. When I tried to start it, I get the error message (attached image). There's no system error Here's the only log happening when trying to launch my VM with the additional Intel audio controller Aug 30 20:48:49 cronos kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Aug 30 20:48:49 cronos kernel: br0: port 2(vnet0) entered blocking state Aug 30 20:48:49 cronos kernel: br0: port 2(vnet0) entered disabled state Aug 30 20:48:49 cronos kernel: device vnet0 entered promiscuous mode Aug 30 20:48:49 cronos kernel: br0: port 2(vnet0) entered blocking state Aug 30 20:48:49 cronos kernel: br0: port 2(vnet0) entered forwarding state Aug 30 20:48:50 cronos kernel: vfio_ecap_init: 0000:01:00.0 hiding ecap 0x19@0x900 Aug 30 20:48:50 cronos kernel: br0: port 2(vnet0) entered disabled state Aug 30 20:48:50 cronos kernel: device vnet0 left promiscuous mode Aug 30 20:48:50 cronos kernel: br0: port 2(vnet0) entered disabled state Aug 30 20:48:51 cronos kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none I've tried to find an answer on unraid forums and google it but I didn't find out any solution . Does anyone has encountered this issue ? Thanks P.S : I've attached my vm's XML below. win10vm.xml Quote Link to comment
eschultz Posted August 31, 2020 Share Posted August 31, 2020 The SMBus most likely is the culprit and has a driver assigned, preventing you from passing through the audio controller (both in the IOMMU group 9). To get around this, you'll need to prevent Unraid from assigning the SMBus driver upon boot by adding "modprobe.blacklist=i2c_i801,i2c_smbus" to your Syslinux configuration append line. Just navigate to this page: https://cronos/Main/Flash?name=flash And modify the green block's append line: Then hit Apply and reboot the Unraid server. Your Windows VM should be able to start after that. Quote Link to comment
DataHearth Posted September 2, 2020 Author Share Posted September 2, 2020 Thank you so much ! That's exactly what was wrong apparently. It even fixed another problem that I was trying to fix (my vms with my nvidia gpu gave me black screen w/ a weird manipulation at the boot of unraid). Thank you ! Quote Link to comment
trevor4n Posted November 15, 2022 Share Posted November 15, 2022 I'm also having issues getting my IOMMU group to appear in windows. Headphones plugged into my line out port aren't discovered. On 8/30/2020 at 9:33 PM, eschultz said: modprobe.blacklist=i2c_i801,i2c_smbus Would those parameters be different with more recent versions of unraid? I tried blacklisting the same thing, and then clearing the power from my system so unraid would let go of my audio device. No luck so far. I do have a few log errors, which I'd be happy to make a separate post about, just figured I'd ping this thread solution for an update! TIA! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.