Ray Joseph wrote on 4/28/19 5:21 AM:
jrsm, Thank you, that was a lot of info. This took me to here: https://www.qubes-os.org/doc/usb-qubes/ From which as root, I executed: qubesctl state.sls qvm.sys-usb 4 succeeded and 1 failed. In sequence: ID: hide-usb-from-dom0-legacy Function: file.append Name: /etc/default/grub ... This one succeeded ID: grub2-mkconfig -o /boot/grub2/grub.cfg Function: cmd.run Result: True Comment: State was not run because none of the onchanges reqs changed Changes: ... This one succeeded ID: sys-net-usb Function: qvm.prefs Name: sys-net Result: False Comment: The following requisition were not found: require: sls: qvm.sys-net Changes: ... This one failed Then there were two other successes for: ID: qubes-input-proxy ID: sys-usb-input-proxy That was the complete emission. I guess the failure signal was the 'Result: False" and all the text was in red. I have checked the terms in the emission but was not able to find anything that looked relevant. It is not clear why sys-net was addressed in the usb process. But I do recall that a usb controller was installed in the sys-net but no wifi. While I have read some about the possibility of using sys-net for usb functions, I don't recall any reference to the installation doing that. Any suggestions?
If you aren't using a USB keyboard, creating your own sys-usb is simple. Create an AppVM, disable networking, and assign your USB controllers to it. If you are using a USB keyboard, refer to that same document. It can be tricky.
-- 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/618b2ac0-9cd4-3c56-c74f-e61dbfe5d6a0%40danwin1210.me. For more options, visit https://groups.google.com/d/optout.
