No longer able to connect controller over usb from Mac OS after updating to OS 15.0 (Mac OS Sequoia)

Submitted by geoff.stafford… on #1

When I attempt to connect my controller to my virtual machine, it shows that the controller is connected to the server, but I am unable to actually connect the controller to the VM, even though it is set to auto use this device. My Mac is on OS 15.0 (newest update) with the newest version of Virtual Here (just downloaded from the site today) 4.6.8.

Submitted by Michael on Thu, 2024/09/19 - 18:52

#2

What is the setup exactly? You are using the controller via virtualhere into the server which runs a VM which you are then trying to redirect again into the VM?

 

Submitted by geoff.stafford… on Thu, 2024/09/19 - 21:23

#3

I have the VirtualHere server installed and licensed on my mac mini, I then have the client software installed on a windows 11 VM. I connect to the VM over Moonlight, and use VirtualHere to connect the USB devices. 

Submitted by Michael on Thu, 2024/09/19 - 21:30

#4

On the MacOS, bring up the VirtualHere server dialog click Settings->View Log. Does that show any errors?

Submitted by geoff.stafford… on Thu, 2024/09/19 - 22:05

#5

Here are the logs related to the controller. It almost seems like the new Mac OS update won't let Virtual Here bind the USB device:

Thu Sep 19 08:01:57 2024 LOG_INFO    Found Full speed device [045e:028e] 'ZhiXu, Controller' at address 34672640
Thu Sep 19 08:02:17 2024 LOG_INFO    10.99.2.112 connected as connection 1 (Standard TCP)
Thu Sep 19 08:02:18 2024 LOG_INFO    Device busy cannot be seized, trying again in 1 sec
Thu Sep 19 08:02:19 2024 LOG_ERR     captureDevicePrepare: USBDeviceOpenSeize error kIOReturnExclusiveAccess (exclusive access) at 4295088064
Thu Sep 19 08:02:19 2024 LOG_ERR     Error binding device 34672640 [045e:028e] to connection 1, BIND_ERROR
Thu Sep 19 08:02:21 2024 LOG_INFO    Device busy cannot be seized, trying again in 1 sec
Thu Sep 19 08:02:22 2024 LOG_ERR     captureDevicePrepare: USBDeviceOpenSeize error kIOReturnExclusiveAccess (exclusive access) at 4295088064

 

Submitted by geoff.stafford… on Sat, 2024/09/21 - 23:11

#7

You're a rockstar. That fixed the issue! Thanks as always for your quick assistance!