Problems getting USB to work on a mac

Discussions about using Mac OS X guests (on Apple hardware) in VirtualBox.
Post Reply
fustbariclation
Posts: 14
Joined: 21. Feb 2013, 10:09

Problems getting USB to work on a mac

Post by fustbariclation »

I'm trying to get this board to work. This is the output from VboxManage list usbhost

UUID: 4a19ca14-47b9-4328-ac11-b1d1341aca99
VendorId: 0x0483 (0483)
ProductId: 0x374b (374B)
Revision: 1.0 (0100)
Port: 4
USB version/speed: 0/Full
Manufacturer: STMicroelectronics
Product: STM32 STLink
SerialNumber: 066CFF575256867067061620
Address: p=0x374b;v=0x0483;s=0x0000450b6bb20617;l=0x14400000
Current State: Unavailable

I've tried applying the useful information I found here:

https://davidoluwatimi.wordpress.com/20 ... sb-access/

I've reduce the number of CPUs to 1, and made sure the right extensions are installed. I've also unplugged and re-plugged the device.

All I see on the linux end is:

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I've configured the Virtualbox ports to:

- Enable the USB Controller
- USB 2.0 (EHCI) Controller
- USB Device Filters -- STMicroelectronics STM32 STLink [0100]

I've also tried, on that filter, setting 'Remote: to 'Any'' and Port to 003.

I'd be delighted by any suggestions about how to get it working!
socratis
Site Moderator
Posts: 27330
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Problems getting USB to work on a mac

Post by socratis »

The article that you linked to has several major errors:
  1. You do NOT need the guest additions for USB support. Just the ExtPack.
  2. You do NOT need to lower your vCPUs to 1. It works fine with multiple vCPUs. There was a bug (#7462), but it was fixed 3 years ago.
  3. You do NOT need to create a blank USB filter. This has the potential to capture every USB device in your system, including your Bluetooth mouse and keyboard. You don't want to do that.
I had to post the above in red text so that people won't make the mistake of following an erroneous article. Hopefully.

In order to better understand the problem you need to submit some more information. Please read the following: Minimum information needed for assistance. For the VM log file ("VBox.log.zip"), here's what you do:
  1. Start the VM. Not from a saved or suspended state. Clean start.
  2. Take the steps required to generate/observe the error.
  3. Shut down the VM. Not suspended, not paused. Shut down.
  4. Right-click on the VM in the VirtualBox Manager.
  5. Select "Show Log..."
  6. Save it (just the first log, VBox.log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).
Post also the output of the following commands:
   VBoxManage list usbhost
   VBoxManage showvminfo "Your_Virtual_Machine_Name"
Please enclose the output in the

Code: Select all

 tag. It makes it easier to read.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Post Reply