On Thu, 2023-08-10 at 21:36 +0000, 51li...@ileg.al wrote: > Its interesting, since my amd legion is testing machine, i never use > sys-usb, and yeah i found that usb passthrough lead system to reboot. > can you provide a more detail about step by step what have you done ? >
At install time untick the 'sysusb' creation, and then create sysusb by hand and attach just 1 USB controller at a time (following the instructions here https://www.qubes-os.org/doc/usb-qubes/#how-to-create-a-usb-qube-for-use-with-a-usb-keyboard) Another way to find out which device is causing the system to poweroff is to use any other VM (e.g. 'personal'), change it to HVM, and go to the devices tab in settings and try passing through one controller at a time, and make a note which one worked and which one didn't. If it works, power off the VM, remove the device from it and try the other ones in turn. If the machine gets instantly powered off instead then make a note about the broken device. I'll write some step-by-step examples once I got it working a bit more reliably, but for now the next device that is misbehaving sometimes is the network card: 0e:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter Sometimes it just keeps printing messages that it is waiting after FLR, and the boot doesn't actually finish (or maybe I didn't wait long enough, I gave up after half a minute after it has printed a few retry messages about FLR). Other times it works reliably (it seems to misbehave if I boot into Qubes directly after the machine has been powered off, but seems to work if I first boot into native Fedora and then reboot into Qubes). Best regards, --Edwin -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bc0382033f36b0bc7ed70d6cd3bc17cb7d6383de.camel%40etorok.net.