utmapp / utmapp/UTM

Cannot connect ANY usb to VM

Open
#6,672 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Swift
Stars
35.5k
Forks
1.8k
Avg merge
5d 5h
Merged PRs (30d)
7

Description

Describe the issue
No USB device connects to ANY vm, be it windows 7/8/10/11 arm/x64/x86 or any linux platform.

see below for exact error in debug log highlighted and screen recording attached. Please not i have tried a USB smartcard, USB flashdrive, an iphone, a USB keyboard (i know it works without needing to attach to the vm, for testing purposes). To note, i have tried a 3in 1 usbc to usb adapter and also a straight usb-C to usb adapter.

https://github.com/user-attachments/assets/a6b9a3b1-7cab-4235-a3e3-51c1fbce6890
I would appreciate any help, unsure if this an ios issue or an ipad M2 issue as i cant seem to get anyone who has my set up to try and replicate.

Configuration (required) UTM-HV

UTM Version: 4.5.4
OS Version: 16.6.1
Device Model: Ipad Pro M2
Is it jailbroken (name jailbreak used)? N/A
How did you install UTM? Trollstore2 - Jit enabled
Debug log

debug.log

}
No symbol named '' found in system symbol set
libusb: warning [darwin_detach_kernel_driver] IOServiceAuthorize: unknown error (0xe00002c7)
2024-09-10 15:58:55,552 CRITICAL GSpice-usbredirhost: could not claim interface 0 (configuration 1): LIBUSB_ERROR_ACCESS
2024-09-10 16:58:55.552 UTM[553:169855] [QEMULogging(0x28097d000)] 2024-09-10 15:58:55,552 CRITICAL GSpice-usbredirhost: could not claim interface 0 (configuration 1): LIBUSB_ERROR_ACCESS
mouseDidStopBeingCurrent: 0x281e55180
2024-09-10 16:58:55.991 UTM[553:166695] [QEMULogging(0x28097d000)] mouseDidStopBeingCurrent: 0x281e55180
mouseDidBecomeCurrent: 0x281e5a560
2024-09-10 16:58:55.991 UTM[553:166695] [QEMULogging(0x28097d000)] mouseDidBecomeCurrent: 0x281e5a560
Debug JSON send -> {
arguments = {
"command-line" = "delvm suspend";

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.