R4rc2 fresh install - sys-net won't start with PCI USB controllers attached.
Sonny Horton
BRCM on-board WiFi disabled in BIOS
VT-x and VT-d properly enabled in BIOS
Machine worked great with R3.2, including USB WiFi using Edimax/Realtek
Symptoms:
USB WiFi adapters (tried two) not properly detected during install
Attempting to start sys-net qube with either PCI USB controller attached results in error: "Start failed: internal error: libxenlight failed to create new domain 'sys-net'"
Actions taken:
Removed both PCI USB controllers from sys-net and sys-net will then start. Tried adding them back singly (there are two) and sys-net will not start.
My issue appears to be closely related to this: https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot
The last several lines of my output of xl dmesg is identical to that noted on the FAQ page linked above, but adds more lines showing failure to attach either of the two controllers to a number of xen domains.
However, the FAQ says it is likely a USB3.0 issue, but this machine does not have USB3.0 and note that the controllers worked fine in R3.2.
I have not tried this solution: "qvm-prefs usbVM -s pci_strictreset false" as my error message is different and, as noted above, these USB controllers worked fine in R3.2. I also don't want to open up additional risks.
Thanks in advance for any assistance. I am *somewhat* new to Qubes, but love it.
Sonny Horton
Foppe de Haan
please disconnect them from the usbVM, then start the VM, and (re)attach them using 'qvm-pci a usbVM -o no-strict-reset=true --persistent dom0:0x_yy.z'
Sonny Horton
Thank you for the fast response.
Apologies to the list for not quoting in my original reply.
I seem to need some help with the syntax of the device ID at the end of the command.
lspci shows me IDs of 00:1a.0 and 00:1d.0 for the controllers, but the qvm-pci command doesn't accept that ID prefaced with dom0: (i.e.: dom0:00:1a.0)... I get the error "qvm-pci: error: backend vm 'dom0' doesn't expose device '00:1a.0'".
I am sure I am misunderstanding something.
Thanks again for the help!
da...@darcybrown.com
I am having the same trouble on a Purism Librem 13v2. Fresh install, selected to use usb inside sys-net option during install.
I tried detaching USB and it will start up, then re-attaching however fails with the same error in the journalctl, with a stack trace.
(Sonny systax should have underscore in it: dom0:00_1a.0 -- running qvm-pci with no args lists them as they should be used)
Sonny Horton
I will mark this as complete. In my searching for syntax clues (sorry I missed the underscore), the output of qvm-pci ls told me what I needed. I was able to attach one of the controllers, but the other gives an empty response from qubesd. I'm going to see if I have the right controller for my USB WiFi and proceed from there. Thanks again!
SH
Sonny Horton
Thanks - our posts crossed in the air, but I did find my syntax issue. Feel free to mark uncomplete for your own purposes. I have a separate issue now with one of my USB controllers and will raise that as a separate topic.
SH