On Thu, January 18, 2018 1:17 am, Marek Marczykowski-Górecki wrote: > On Thu, Jan 18, 2018 at 01:05:46AM +0000, mossy-nw wrote: >>> On Wed, Jan 17, 2018 at 11:54:23PM +0000, mossy-nw wrote:
>>>> Has anyone using Qubes R4.0 been able to resolve any issues (e.g. >>>> with wifi) by setting PCI permissive mode? (as described in:) >>> >>>> https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-iss >>>> ues > I assume this is after enabling permissive mode, right? > Simon, is setting permissive mode in dom0 enough? Or maybe qemu in > stubdomain perform some additional filtering? Per device permissive mode is broken in 4.0. I was trying to figure out where exactly while troubleshooting my Atheros card. I found where the init script in the stubdomain reads the device values from xenstore, but I couldn't find anywhere that actually added per device permissive entries to xenstore (whereas I did find where msitranslate and power_mgmt got set). For my troubleshooting, I set the init script to default to permissive=true which results in every device being added as permissive but it didn't help my Atheros case anyways. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/381cd456cabaaaba83b17dfc7ac94fd6.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
