Ticket #8506 (closed defect: obsolete)

Opened 8 years ago

Last modified 3 years ago

Win7 (x86) Guest Aborts On Ubuntu Host (x86) if Logitech Pro 9000 USB Camera Connected

Reported by: prynhart Owned by:
Component: USB Version: VirtualBox 4.0.4
Keywords: Logitech, USB, Aborted Cc:
Guest type: Windows Host type: Linux

Description (last modified by frank) (diff)

Symptom: Win7 (x86) Guest Aborts On Ubuntu Host (x86) if Logitech Pro 9000 USB Camera Connected

Steps to Reproduce:

  1. Clean Install of Ubuntu 10.04 or above as a Host
  2. Install VirtualBox 4.04
  3. Create and Install a Windows 7 VM
  4. Connect a Logitech Pro 9000 Camera (identified as "Unknown device 046D:0990 [0008]" by VB) to the host
  5. Attempt to connect the USB device to the VM. The VM will exit immediately and enter into the State "Aborted".


  1. I have reproduced this fault on more than one Ubuntu based Host.
  2. The relevant output of "VBoxManage list usbhost" is:

UUID: 73b26267-f686-4623-895b-d2db4e816d2c VendorId: 0x046d (046D) ProductId: 0x0990 (0990) Revision: 0.8 (0008) SerialNumber: 7A2B4C54 Address: sysfs:/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-5//device:/dev/vboxusb/002/014 Current State: Busy

I have captured a Core Dump as per which is attached along with the VB log.


VBox.log Download (46.7 KB) - added by prynhart 8 years ago.
VB Log

Change History

comment:1 Changed 8 years ago by prynhart

The GZipped core dump exceeds the maximum file size permitted for upload. I have uploaded the file to:

If someone could please let me know when I can remove this file this would be appreciated.



Changed 8 years ago by prynhart

VB Log

comment:2 Changed 8 years ago by prynhart

Unfortunately some of the line breaks haven't pasted correctly in the original post :-(

comment:3 Changed 8 years ago by frank

Thanks for the core dump. We are investigating...

comment:4 Changed 8 years ago by frank

I've analyzed your core dump. The cause of the crash is not yet clear. Could you install  this test build? This is a debug build which will run notably slower but it also contains a lot of sanity checks, maybe some assertion is triggered. If you can reproduce the crash, I would be interested in the core dump again.

No worry about your VMs, you can just safely install this debug build, do some checks and re-install VirtualBox 4.0.4.

To start the VM, please do the following:

  • make sure that no VBoxSVC daemon is running
  • start the VM with
    export VBOX_ASSERT=none
    VirtualBox -startvm VM_NAME
    where you replace VM_NAME with the name of the VM to start. This version will also create several log files in the local directory, make them available as well.

Thank you!

comment:5 Changed 8 years ago by frank

Did you find any time to install that debug build?

comment:6 Changed 8 years ago by prynhart

Hi Frank,

Thank you for looking into this issue. Since I filed the bug report, I've actually changed jobs :-) I was having the problem on my work computer and managed to replicate it on another box also. I don't currently have a Ubuntu box handy, but will try to arrange one within the next few days for testing. If you would be able to leave the bug report open until that time that would be appreciated.

Many Thanks,


comment:7 Changed 8 years ago by prynhart

Hi Frank,

Apologies for the delay. I'm now setup and ready to test. However, the link above (containing the debug build) now appears to be broken, i.e.:

# wget --2011-04-24 19:36:12-- Resolving Connecting to||:80... connected. HTTP request sent, awaiting response... 404 Not Found 2011-04-24 19:36:13 ERROR 404: Not Found.

I'm presuming that a newer debug version has been built ? If so, is there any chance that you could please post an updated link. (Listing of the directory contents @ appears to be disabled.)



comment:8 Changed 8 years ago by frank

Please could you just install VBox 4.0.6 and check if this release fixed your problem? Make sure that the current user is member of the vboxusers group (this was sometimes not necessary with VBox 4.0.4).

comment:9 Changed 8 years ago by prynhart

I did try setting up a new test environment as per the bug report (i.e. 32 bit Linux host - 32 bit Windows VM). Specs of the host: 3 GHz P4 with 2 GB Ram - Guest has 1 GB ram allocated.

I'm not able to reproduce the crash, but haven't been successful in getting the camera to work either. The VM turns to "treacle" as soon as I connect the camera which is listed as "Unknown Device 046D:0990 [0007]" as before. By treacle, I mean that the machine runs so incredibly slowly that even just moving the mouse over the Windows Start Orb & clicking once will take more than 5 minutes for the Start Menu to pop up. (With the camera disconnected the response time is a few seconds.) Unfortunately I can't start device manager etc to investigate the state of drivers. The guest isn't in a crashed state but is unusable. Hmmmm....


comment:10 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use