Closed AdrianFretwell closed 2 years ago
Thanks a lot for your feedback!
For future reference, forum thread about USB passthrough issues: https://xcp-ng.org/forum/topic/266/usb-passthrough-test-reports-in-7-5rc1
Saved my day, altough I m testing USB performance using USB DVBT keys.
Is this bug still present in XCP-ng 8.2? We could probably contribute a fix upstream if it is.
I'm having this issue in XCP-ng 8,2
However, it only happens once I try to pass through a GPU. If I have only USB, all is fine, but as soon as I also attempt to passthrough a PCI-E GPU the USB starts throwing this error. As if this was a combination of both type of passthrough used simultaneously that is causing the issue.
Further account of this behavior (in version 8.1) here => https://forum.level1techs.com/t/xcp-pci-passthrough-usb-passthrough-does-not-work-together/162110
Thanks for your report. This does not seem to be the same issue as that from the original poster though. Could you open a new one?
I am still facing the same issue. USB dongle passthrough attempts give this same error. (And I am also passing through a GPU as mentioned)
Updated packages addressing this issue are available for testing on XCP-ng 8.2: https://xcp-ng.org/forum/post/41480
The update with the fix is now released to every XCP-ng 8.2 user: https://xcp-ng.org/blog/2021/12/08/december-2021-xcp-ng-updates/
After attaching a USB device to a VM using the procedure detailed here https://github.com/xcp-ng/xcp/wiki/USB-Pass-Through. I see the following error when trying to start the VM:
[root@ahf-test1 ~]# xe vm-start uuid=03c084c3-6165-25a8-d983-3cd5b11816a0
It looks like /opt/xensource/libexec/usb_reset.py is being passed the -r argument but no value for it. I assume RESET_ONLY is a constant.
I have found a work around for this but it is not a solution.
I have modified /opt/xensource/libexec/usb_reset.py to add a default for the -r argument if non is supplied: Before:
After:
The underlying problem must be with whatever code calls usb_reset.py, but I can't work out where it is called from when a VM with USB is started.
Kind regards, Adrian.