On Fri, March 2, 2018 2:27 pm, sbore...@gmail.com wrote: > https://www.qubes-os.org/doc/assigning-devices/ > > > and tried enabling 'permissive' mode as described for R3.2 in the above > documentation. However, this per se doesn't work, as the target file > (/sys/bus/pci/drivers/pciback/permissive) > is not writeable, even for root and even when triggered through systemd.
Just tested again on R3.2 and the procedure in the doc works, but only for re-assignable devices (ones using the pciback driver in lspci). Are you sure you were trying to write the correct 0000:<BDF>? When I tried with an un-assignable device, I got: bash: echo: write error: No such device > >> >> And xl dmesg shows: >> >> >> XEN) [VT-D] It's disallowed to assign 0000:00:1a.0 with shared RMRR at >> da8d5000 for Dom5. (XEN) XEN_DOMCTL_assign_device: assign 0000:00:1a.0 >> to dom5 failed (-1) >> > > For the record, xl dmesg is now telling me that > [VT-D] It's risky to assign .. with shared RMRR at .. for Dom4 Setting pci_strictreset to false is what changed this message from "disallowed" to "risky". > what ever that means. > > I don't know which of the options / changes did the trick, but one or > more of the above seems to enable the camera in 'untrusted'. Setting pci_strictreset to false. -- 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/bc6c4fe2cd0600f39143797d52ddfef1.squirrel%40tt3j2x4k5ycaa5zt.onion. For more options, visit https://groups.google.com/d/optout.
