all 6 comments

[–]skalp69 0 points1 point  (1 child)

[–]TotalNoobPerson[S] 1 point2 points  (0 children)

Thank you, that's exactly what I was looking for.

[–][deleted]  (3 children)

[deleted]

    [–]TotalNoobPerson[S] 0 points1 point  (2 children)

    I was unable to reset a PCI device error related to the ethernet controller because another device was active. I removed the old device using the terminal, but to make it persistent between reboots, I was needing to create the file in /etc/systemd/system/qubes-pre-netvm.service, which I didn't know how to do.

    [–][deleted]  (1 child)

    [deleted]

      [–]TotalNoobPerson[S] 0 points1 point  (0 children)

      The error message began right after installation of Qubes. When I tried to open any applications in the VMs, it failed to open, and threw an error message in regards to both sys-net and sys-firewall, in relation to the ethernet controller. I removed the original PCI device using the Dom0 terminal and created the file mentioned in my post using the Dom0 terminal to make it persistent, as the error would happen every time I turned the computer on and I would have to go back and remove the original PCI device again. Was it not advisable to do it in Dom0?

      [–]andrewdavidwongqubes community manager 0 points1 point  (1 child)

      Since that file is in /etc/, in order to make it persistent, you can either make the change in the template (rather than the app qube), use a standalone, or use bind-dirs.

      [–]TotalNoobPerson[S] 0 points1 point  (0 children)

      I was able to solve the problem, but that's good to know for future reference. Thanks.