VERR_SHARING_VIOLATION (0x80004005) when attaching USB Storage directly to Vbox 7.0.4 VMs

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
Glenn Fawcett
Posts: 1
Joined: 28. Dec 2023, 23:57

VERR_SHARING_VIOLATION (0x80004005) when attaching USB Storage directly to Vbox 7.0.4 VMs

Post by Glenn Fawcett »

This is more complicated that it appears. I have two virtual serial port adapters where one works and the other doesn't: a Prolific serial chip inside an ICP-DAS CAN adapter and CANable slcan firmware within a CANable adapter. When plugged into MacOS Ventura 13.6.3 (22G436), the Prolific interface creates /dev/tty.usbserial-1410 and the CANable adapter creates /dev/tty.usbmodem14101 -- this may be a clue.

Both devices can be used as serial ports, in an identical way, under MacOS. However, the Prolific device can be connected to VirtualBox (running Windows 10) but the CANable device gives the VERR_SHARING_VIOLATION. This is perfectly repeatable. Filters have no effect.

Prolific (this one works)
USB-Serial Controller D:
Product ID: 0x2303
Vendor ID: 0x067b (Prolific Technology, Inc.)
Version: 4.00
Speed: Up to 12 Mb/s
Manufacturer: Prolific Technology Inc.
Location ID: 0x14100000 / 1
Current Available (mA): 500
Current Required (mA): 100
Extra Operating Current (mA): 0
Makes:
/dev/cu.usbserial-1410
/dev/tty.usbserial-1410

CANable slcan 6/29/2023 (this one does not work)
CANable 9fddea4 github [dot] com/normaldotcom/canable-fw.git:
Product ID: 0x60c4
Vendor ID: 0xad50
Version: 2.00
Serial Number: 003B003E5457530120383638
Speed: Up to 12 Mb/s
Manufacturer: Protofusion Labs
Location ID: 0x14100000 / 1
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0
Makes:
/dev/cu.usbmodem14101
/dev/tty.usbmodem14101
Post Reply