Cannot Open USB Device Error Message 2021 M1 Pro MacBook Pro #3375
Comments
|
Thank your for providing the debug log and crash log. Generally, UTM is able to pass through USB devices to emulated guests. Regarding the USB error: in your VM config, USB 3.0 support is enabled in the Sharing tab (this is the default setting). Please uncheck USB 3.0 (XHCI) support and try again. (I can tell because Regarding the crash: does the VM crash immediately after the error in your screenshot? For developers, here is an excerpt from the translated crash report. Full Translated Crash Report |
|
Hello,
Thanks for responding. This error occurs with and without USB 3.0 enabled in settings. Here is screenshot attached with USB legacy 2.0 only.
… On Dec 9, 2021, at 6:22 AM, CONATH ***@***.***> wrote:
Thank your for providing the debug log and crash log. Generally, UTM is able to pass through USB devices to emulated guests.
Regarding the USB error: in your VM config, USB 3.0 support is enabled in the Sharing tab (this is the default setting). Please uncheck USB 3.0 (XHCI) support and try again. (I can tell because -device nec-usb-xhci,id=usb-controller-0 is in the debug log.)
Regarding the crash: does the VM crash immediately after the error in your screenshot?
For developers, here is an excerpt from the translated crash report.
Process: QEMULauncher [14979]
Path: /Applications/UTM.app/Contents/XPCServices/QEMUHelper.xpc/Contents/MacOS/QEMULauncher.app/Contents/MacOS/QEMULauncher
Identifier: com.utmapp.QEMULauncher
Version: 2.4.1 (40)
Code Type: ARM-64 (Native)
Parent Process: QEMUHelper [5833]
Responsible: UTM [5606]
User ID: 501
Date/Time: 2021-12-09 00:34:34.2731 -0500
OS Version: macOS 12.0.1 (21A559)
Report Version: 12
Anonymous UUID: 11940037-F7AA-8236-A18B-AE114BBACF71
Sleep/Wake UUID: F785C8EE-501F-4958-A85D-FC68A860E9F8
Time Awake Since Boot: 160000 seconds
Time Since Wake: 29869 seconds
System Integrity Protection: enabled
Crashed Thread: 8
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
[…]
Thread 8 Crashed:
0 libsystem_kernel.dylib 0x1a56cd9b8 __pthread_kill + 8
1 libsystem_pthread.dylib 0x1a570115c pthread_kill + 288
2 libsystem_c.dylib 0x1a563e314 abort + 164
3 qemu-x86_64-softmmu 0x105fe4c1c 0x105fd0000 + 85020
4 qemu-x86_64-softmmu 0x106121f70 process_queued_cpu_work + 208
5 qemu-x86_64-softmmu 0x106120d4c 0x105fd0000 + 1379660
6 qemu-x86_64-softmmu 0x1064cc438 0x105fd0000 + 5227576
7 libsystem_pthread.dylib 0x1a57014ec _pthread_start + 148
8 libsystem_pthread.dylib 0x1a56fc2d0 thread_start + 8
Full Translated Crash Report
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#3375 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACD6LBEK4PLUKIICWP6JL73UQCGPRANCNFSM5JVTKHSA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
|
Sorry, the attachment won't work via email. Please open the GitHub issue page and add the file in the comment field. When does the crash happen? Is it right after the error message? |
|
Sorry about that. Here is the updated screenshot. The crash does not happen after the error. The crash is isolated issue as it is random and I provided because the template for posting asked for debug and crash logs. |
|
Thanks. The template is somewhat confusing I suppose; the crash log is only needed if the problem you are reporting is a crash. Unfortunately there is not much info for me to go off off here other than the error -99. Maybe we can get more detail from the macOS Console app. Here's the steps to get additional info via Console app:
Thank you in advance! |
|
Two errors notable in this log. First error: seems like UTM is not properly signed, might not have the necessary entitlements for USB passthrough.
How did you install UTM? Second error: USB device already in use The system error The VM starts at this point in the log: Anyway, it seems like the USB device is already used by another application. To resolve both errors, I would try the following steps:
|
|
Followed your instructions below. Reinstalled app, restarted Mac, and confirmed connect to VM. Still receive the same error. |
|
@MAPE15 I would like to try to reproduce this error so we can get closer to finding the underlying issue and fixing it. To do this I will need the config.plist from your VM, please (get it by ctrl-clicking the VM in UTM, select Show in Finder, ctrl-click the Additionally, if you can, please send the technical specifications of the USB device you are attempting to connect (model number, manual, etc.), as well as the way you are connecting it to your Mac (e. g. which adapter used incl. model). Finally, it might be useful to get a screenshot of how the macOS System Information app sees your USB device. To get this:
Thank you! |
|
My 2c is that USB support is shoddy and will continue to be shoddy until Apple provides capture APIs that allow for device reset. Right now we have to wait for the kernel to try to configure the device and fail and pass it to the capture application (UTM) to take over. Many devices don't like that and will not behave properly. |
|
A recent experience: Just yesterday I had trouble working with a USB to IDE adapter with UTM. The adapter is a cheap device and had trouble with working on the macOS. Connecting it to UTM was an additional struggle with lots of retries and a crash in the usb library. |
|
So what do you guys recommend we do to get things working? @conath you are a developer of UTM right? |
|
I am not a low-level developer capable of fixing this, and osy is more knowledgeable on these topics. As osy has pointed out it is not in the scope of the UTM project to fix this right now. What you could try (and this is really just a weird trick more than an actual solution) is re-connecting the device quickly to your Mac and very quickly click to connect it to the VM when the UTM alert appears. That could work around the "already in use" error. I really don't know if it would work for your specific device, though. |
|
Yeah I agree. It would not work with my specific device. |
|
I had this problem before and i managed by installing USB drivers for the usb ports , it worked for me. |
Hi, I still got the same issue. Where did you get the USB drivers? |
|
Same here when mounting a Samsung 2TB T7 external HDD (the small blue one). Using UTM 4.4.4 on macOS Sonoma 14.0 on Macbook Pro M1 14". 
|
I have tried mounting my radar detector that uses USB 2.0 which UTM can see but cannot mount into the emulated x86/x64 versions of Windows XP, 7, and 11 ARM. I believe that the issue is that it does not detect any emulated versions of USB 3.0 drivers. UTM can see the device but when trying to mount it, I receive an error message from UTM. I wanted to ask the developers to help me retrieve any kind of logs to see why it is having an error and see if we can make it compatible with these emulated x86/x64 Windows VMs. I tested to ensure it was not my device but connecting it to an Intel based PC and it worked fine.
UTM Version: 2.4.1(40)
OS Version: 12.0.1 macOS Monterey
Intel or Apple Silicon? Apple Silicon M1 Pro
Crash log
QEMULauncher-2021-12-09-003436.txt
Debug log
debug.log
Please let me know if you can assist me with this issue or if I need to provide you anything else to help troubleshoot and resolve this issue. FYI, I also tried this on Parallels and it would not work either.
Thank You!
The text was updated successfully, but these errors were encountered: