Ticket #10958 (new defect)

Opened 4 years ago

Last modified 2 years ago

Windows guest does not recognized Broadcom 5880 smart card reader

Reported by: armillz Owned by:
Priority: major Component: USB
Version: VirtualBox 4.2.0 Keywords: smart card
Cc: Guest type: Windows
Host type: Windows


I have a Dell Latitude E6520 with a built in Broadcom 5880 smart card reader that refuses to work inside my Windows Guest OS. Some relevant notes:

  • the 5880 reader works fine on my host system.
  • if I plug in an external USB smart card reader (SCR3310), that works fine inside the guest OS
  • the built in 5880 reader works fine in a guest if I use VMware.

Virtual box will allow me to connect the 5880 from the USB devices menu. It then indicates a lot of flashing red/green lights on the USB icon, but my smart card software inside the guest (ActivClient) does not recognize that a reader is present. Inserting/removing the card has no effect.

My configuration:

  • Windows 7 64-bit Professional on the host, 8GB RAM
  • Windows 2008 R2 64-bit as the guest, 3.5GB RAM

I just updated to VirtualBox 4.2 but have tried this on a bunch of previous 4.0 and 4.1 versions. I was hoping this would eventually be fixed. My googling through the community indicates that others have had this problem and it has never been solved.

Any idea how to make this work or whether it will be fixed?

Change History

comment:1 Changed 4 years ago by Hachiman

Could you please attach your log file?

comment:2 Changed 4 years ago by AllTheVbox!

It's been a perennial pain trying to get VirtualBox to properly recognize integrated Broadcom 5880 Smart Card readers on Dell laptops (in my case using an Ubuntu 11.04 host and Windows guest), even when the card reader checks out fine under on the host and you pass the device through exclusively to the guest. Worse yet, as of my installation of a Windows 7 guest, I can't even get my trusty SCR3310 reader to work on the guest OS. :(

I know virtual machines can handle this hardware - see VMWare - and this is a well known problem for VirtualBox, so I'm at a loss as to why crickets chirp whenever a user submits one of these tickets. Will someone at Oracle please, PLEASE at least acknowledge that this is a problem, explain why it's happening, and provide a sense of whether there is a technical approach to fix it in a future release?


Version 4, edited 4 years ago by AllTheVbox! (previous) (next) (diff)

comment:3 Changed 4 years ago by ubeinges

I've got the same problem with a Windows XP SP3 guest. The error remains the same throughout all versions of VB 4.1.x and 4.2.x I tried. The same card reader works fine with the same guest installation when I use it in VMware player. So this must be a Virtualbox issue.

Could you please fix this!

comment:4 Changed 4 years ago by ubeinges

Tested today with brandnew version 4.2.2. Issue is still present.

comment:5 Changed 4 years ago by MatNe

Still the same problem - please fix it, I need the smartcard driver in Virtualbox too.

Last edited 4 years ago by MatNe (previous) (diff)

comment:6 Changed 3 years ago by mobbingmaster

Still the same problem! Please fix it - this is currently the only reason why we still need the VMWare Player - all other VMs are running under VirtualBox.

comment:7 Changed 3 years ago by Jon Roach

I have the same problem with a Dell E6400 internal reader. VMWare Player can pass the Broadcomm card reader through with no problem, so why can't VirtualBox? VB has been dogged by this particular problem for years, and I'm starting to think it will never be fixed.

Please fix it: I'm dying to get rid of VMWare Player, but am currently stuck with it because the Smart Card is a critical part of the remote access solution for our company and VirtualBox just can't support it. Yet.

I'm running 64-bit Ubuntu 12.04 LTS with a 64-bit Windows 7 Pro guest.

Last edited 3 years ago by Jon Roach (previous) (diff)

comment:8 Changed 2 years ago by slowhog

Sam problem here. Tried enable/disable EHCI, tried filter(and not) the device.

Host is Arch Linux, guest is Windows XP SP3.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use