On Wednesday, October 25, 2017 at 12:06:21 PM UTC-4, Sonny Horton wrote: > On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote: > > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote: > > > Hardware: Dell Latitude E6420 - i5 > > > 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 > > > > 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' > > > > On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote: > > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote: > > > Hardware: Dell Latitude E6420 - i5 > > > 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 > > > > 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' > > > > On Wednesday, October 25, 2017 at 8:34:04 AM UTC-7, Foppe de Haan wrote: > > On Wednesday, October 25, 2017 at 5:22:13 PM UTC+2, Sonny Horton wrote: > > > Hardware: Dell Latitude E6420 - i5 > > > 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 > > > > 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' > > 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!
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) -- 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/9f13ad94-881e-4ecf-b1aa-98c28f6a1df5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
