Correct to the above: EHCI not xHCI qvm-pci which produced dom0:00_14.0 USB controller: ... - LP USB xHCI Controller sys-usb (no-strict-reset=True) dom0:00_1d.0 USB controller: ... - LP USB EHCI Controller sys-usb (no-strict-reset=True)
Further - I initiated a qvm-start for sys-usb which produced: xl top showed sys-usb as paused for about 60 seconds, then it disappeared from the display. The CLI returned: Start failed: internal error: Unable to reset PCI device 0000:00:14.0: internal error: libxenlight failed to create new domain 'sys-usb' When I execute: qvm-pci attach --persistent -o no-strict-reset=True sys-usb dom0:00_14.0 an error is produced: "'device dom0:00_14.0 of class pci already attached to sys-usb'" Since I don't know if this means the attachment is persistent (it was repeatable after a reboot), I attempted to detached qvm-pci detach sys-usb dom0:00_14.0 qvm-pci detach sys-usb dom0:00_1d.0 Using qvm-pci list, both were gone, no longer listed. So I again performed the attachment as above. Both instances are back in. I do not see any difference from that display. I started up sys-usb from CLI and received the same error about libxenlight failing. -- 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/1b75f23d-25e5-4a81-a364-042705a1971e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
