![]() x86/split lock detection: #AC: CPU 5/KVM/107893 took a split_lock trap at address: 0x754c6793 usb 3-3.2: USB disconnect, device number 7 sd 8:0:0:0: Write cache: disabled, read cache: enabled, doesn't support DPO or FUA usb 4-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-2.4: New USB device found, idVendor=0b95, idProduct=1790, bcdDevice= 2.00 sd 8:0:0:0: Attached scsi generic sg0 type 0 scsi 8:0:0:0: Direct-Access SanDisk Extreme 0001 PQ: 0 ANSI: 6 usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15 xhci_hcd 0000:08:00.0: Host supports USB 3.0 SuperSpeed ![]() xhci_hcd 0000:08:00.0: new USB bus registered, assigned bus number 4 xhci_hcd 0000:08:00.0: new USB bus registered, assigned bus number 3 xhci_hcd 0000:08:00.0: xHCI Host Controller It looks fine in lspci -nnv at this point: Then the controller can not be passed-through to any VM anymore. However, if I passthrough it to a macOS 10.13 VM, it works fine the first time the VM starts until the macOS is shutdown or rebooted. No driver blacklist or vfio related modprobe conf modification is needed and it just works. I can reboot the windows VM as many times as I want and the controller just keep working correctly and fluently, and can even be "removed and rescanned" to be used in Proxmox VE host to connect USB storage devices to the host - I can put the controller anywhere (used inside VM or by host) at anytime as I want and switch it back and forth without any error. It works perfect when passthoughed to a Windows 11 vm, all the functions including USB 2.0 and 3.0 works like a charm. I thought a seperate USB controller connected through PCI-e would help so I bought a FL1100 PCI-e 1x USB controller with 4 USB type-A ports. Once the VM was shutdown or rebooted, the USB 3.0 would no longer work until I reboot the host. But USB 3.0 could only work on the first boot of any VM with the controller passthroughed. ![]() Actually I could passthrough the intel USB controller and use it with all basic USB 2.0 functions work as expected. My PC has a B660 chipset and there is only one Intel USB controller which is in the same IOMMU group as System RAM and lacks available reset mechanism. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |