Oracle VM VirtualBox: Ticket #1347: USB device reported working, but no communicationhttps://www.virtualbox.org/ticket/1347
<p>
I would like to report a USB device that appears as working in the guest OS, but programs cannot communicate with it.
I am using Vista 64-bit with XP 32-bit in <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a>. The main reason for using virtualization is the unavailability of a 64-bit driver for a reprogrammable USB FPGA board. This little board can be programmed using a utility (Adept Suite) of the manufacturer (Digilent). I added a USB filter for this device in <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> and it got detected in the guest OS and installed the correct driver for it. It appears as enabled and working in Device Manager. The utility can also detect the board and its ID. However, when it tries to communicate with it (Initialize Chain) it fails. I can confirm that this same setup with another virtualization software works and the utility can communicate to the board.
I would gladly provide any kind of dump, log or other debug data for investigation.
</p>
en-usOracle VM VirtualBox/graphics/vbox_logo2_gradient.pnghttps://www.virtualbox.org/ticket/1347
Trac 0.12cornbreadWed, 02 Apr 2008 14:15:34 GMThttps://www.virtualbox.org/ticket/1347#comment:1
https://www.virtualbox.org/ticket/1347#comment:1
<p>
Same deal I have. Bug <a class="new ticket" href="https://www.virtualbox.org/ticket/1051" title="defect: Usb Device not working all other devices work. (new)">#1051</a>. I talked to the devs on irc and they said don't hold your breath on usb working on my device any time soon.
</p>
Ticketsandervl73Fri, 02 May 2008 20:43:16 GMTstatus changed; resolution sethttps://www.virtualbox.org/ticket/1347#comment:2
https://www.virtualbox.org/ticket/1347#comment:2
<ul>
<li><strong>status</strong>
changed from <em>new</em> to <em>closed</em>
</li>
<li><strong>resolution</strong>
set to <em>fixed</em>
</li>
</ul>
<p>
Try again with 1.6.0 and report back if it's still relevant. Thanks.
</p>
TicketmludwigSat, 03 May 2008 15:10:48 GMTstatus changed; resolution deletedhttps://www.virtualbox.org/ticket/1347#comment:3
https://www.virtualbox.org/ticket/1347#comment:3
<ul>
<li><strong>status</strong>
changed from <em>closed</em> to <em>reopened</em>
</li>
<li><strong>resolution</strong>
<em>fixed</em> deleted
</li>
</ul>
<p>
I set up a new 32-bit XP SP3 VM in 1.6.0 and I got the same result, it appears working, but communication fails. Activating USB devices in the VM also fails sometimes with no error message ie. clicking on a device on the USB list does nothing.
Other times I get a crash on the host:
Product
Sun xVM <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> Interface
</p>
<p>
Problem
Stopped working
</p>
<p>
Date
2008.05.03. 4:03
</p>
<p>
Status
Not Reported
</p>
<p>
Problem signature
Problem Event Name: APPCRASH
Application Name: VBoxSVC.exe
Application Version: 1.0.0.1
Application Timestamp: 4818d40b
Fault Module Name: VBoxDDU.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4818d31d
Exception Code: c0000005
Exception Offset: 00000000000196e4
OS Version: 6.0.6001.2.1.0.256.6
Locale ID: 1038
Additional Information 1: 80ad
Additional Information 2: 922c9c6d5745beeb98fd45a7b83b0223
Additional Information 3: 5cb6
Additional Information 4: 57cd1eed70ec2a428d77631cff6b5e38
</p>
<p>
The problem seems not limited to my FPGA board, but also a "Mass storage device" (USB external hard drive).
Let me know, if you need other debug data.
</p>
TicketfrankWed, 09 Jul 2008 20:23:14 GMTcomponent changedhttps://www.virtualbox.org/ticket/1347#comment:4
https://www.virtualbox.org/ticket/1347#comment:4
<ul>
<li><strong>component</strong>
changed from <em>other</em> to <em>USB</em>
</li>
</ul>
TicketmludwigTue, 16 Sep 2008 20:19:20 GMThttps://www.virtualbox.org/ticket/1347#comment:5
https://www.virtualbox.org/ticket/1347#comment:5
<p>
Just confirming that the the same issue is experienced in <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> 2.0.2 and it is consistent with other user reports of not all USB working.
</p>
TicketZhekaSFri, 14 Aug 2009 17:02:59 GMThttps://www.virtualbox.org/ticket/1347#comment:6
https://www.virtualbox.org/ticket/1347#comment:6
<p>
Same issue in <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> 3.0.4 (and older). No progress since 2.0.1 .
</p>
TicketmichaelFri, 14 Aug 2009 21:57:53 GMThttps://www.virtualbox.org/ticket/1347#comment:7
https://www.virtualbox.org/ticket/1347#comment:7
<p>
Unfortunately, there will probably always be a number of unsupported USB devices in <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a>, since every device has a few quirks of its own, to which <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> has to be adjusted. That said, <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> USB support is being worked on continuously, and it is always worth checking whether new versions make unsupported devices work.
</p>
TicketxobyWed, 12 May 2010 14:17:33 GMThttps://www.virtualbox.org/ticket/1347#comment:8
https://www.virtualbox.org/ticket/1347#comment:8
<p>
The problem is still present with <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> v3.1.8 (tested with Digilent Adept, Basys 2 board, a linux 64 bits host and a Windows XP guest).
</p>
TicketcgrecoFri, 28 May 2010 17:24:42 GMThttps://www.virtualbox.org/ticket/1347#comment:9
https://www.virtualbox.org/ticket/1347#comment:9
<p>
Communication problem persists with <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> 3.2.0, Digilent Adept 2-3-0, Basys2 board, Debian linux 64 bit (lenny) host and Window 7 Enterprise guest. Board recognized but cannot initialize. Apparently, reading from device is functional but cannot write to the device.
</p>
TicketjwcxzWed, 25 Aug 2010 21:17:58 GMThttps://www.virtualbox.org/ticket/1347#comment:10
https://www.virtualbox.org/ticket/1347#comment:10
<p>
Issue still exists with 3.2.8. Same behavior as above. Arch Linux, Kernel 2.6.35.3, Digilent Adept 2.4 with Nexys2 board on a Windows XP guest.
</p>
TicketerhardmWed, 23 Feb 2011 17:57:18 GMThttps://www.virtualbox.org/ticket/1347#comment:11
https://www.virtualbox.org/ticket/1347#comment:11
<p>
The same problem exist in version 4.0.4 <a class="missing changeset" title="No changeset 70112 in the repository">r70112</a>
</p>
TicketandreweffTue, 12 Jul 2011 16:51:11 GMThttps://www.virtualbox.org/ticket/1347#comment:12
https://www.virtualbox.org/ticket/1347#comment:12
<p>
This problem persists in version 4.0.10 with Arch Linux kernel 2.6.39 as the host and windows 7 32 bit as the guest.
</p>
TicketfrankThu, 14 Jul 2011 11:52:49 GMThttps://www.virtualbox.org/ticket/1347#comment:13
https://www.virtualbox.org/ticket/1347#comment:13
<p>
andreweff, which package did you use? The official package from our website or an Arch Linux package?
</p>
TicketandreweffThu, 14 Jul 2011 12:34:40 GMThttps://www.virtualbox.org/ticket/1347#comment:14
https://www.virtualbox.org/ticket/1347#comment:14
<p>
I used this package: <a class="ext-link" href="http://www.archlinux.org/packages/community/x86_64/virtualbox/"><span class="icon"> </span>http://www.archlinux.org/packages/community/x86_64/virtualbox/</a>
I could try the package from the website but I'd imagine that the arch package is based on it.
</p>
TicketfrankThu, 14 Jul 2011 13:24:30 GMThttps://www.virtualbox.org/ticket/1347#comment:15
https://www.virtualbox.org/ticket/1347#comment:15
<p>
That's easy to find out if you attach a VBox.log file from such a VM session to this ticket.
</p>
TicketandreweffThu, 14 Jul 2011 13:50:35 GMTattachment sethttps://www.virtualbox.org/ticket/1347
https://www.virtualbox.org/ticket/1347
<ul>
<li><strong>attachment</strong>
set to <em>Logs.tar.gz</em>
</li>
</ul>
<p>
Several Logs in which this problem occurs.
</p>
TicketfrankThu, 14 Jul 2011 14:00:40 GMThttps://www.virtualbox.org/ticket/1347#comment:16
https://www.virtualbox.org/ticket/1347#comment:16
<p>
In that case the case is clear. The Arch Linux guys use the official source code for compiling their own package. For proper USB 2.0 support, the extension pack is required but due to a bug this does not help for VBox 4.0.10. I'm quite sure that your problems result from this bug. That bug will be fixed in the next maintenance release.
</p>
TicketandreweffThu, 14 Jul 2011 14:07:14 GMThttps://www.virtualbox.org/ticket/1347#comment:17
https://www.virtualbox.org/ticket/1347#comment:17
<p>
I think I have the extension pack installed as well. Does this bug mean that this issue will occur even with the extension pack? If I am somehow able to rollback to a version that doesn't have this bug should it work? What is the latest version that doesn't have this bug?
</p>
<p>
arch extension package: <a class="ext-link" href="http://aur.archlinux.org/packages.php?ID=44761"><span class="icon"> </span>http://aur.archlinux.org/packages.php?ID=44761</a>
</p>
TicketfrankThu, 14 Jul 2011 14:17:07 GMThttps://www.virtualbox.org/ticket/1347#comment:18
https://www.virtualbox.org/ticket/1347#comment:18
<p>
The Arch extension pack is just the official extension pack from the VirtualBox download site. Yes, even if the extension pack is installed you wouldn't be able to enable USB 2.0 devices. Either install the official package (the universal.run package in your case) or install any 3.2.x package.
</p>
TicketvollkornWed, 26 Oct 2011 10:28:29 GMThttps://www.virtualbox.org/ticket/1347#comment:19
https://www.virtualbox.org/ticket/1347#comment:19
<p>
Same problem with 4.1.4. I'm using Max OS X 10.7.2 as host and Windows XP SP3 as guest. Digilents Adept is able to identify the device (Basys 2) but when I try to connect it reports "Initialization failed. Check connection and try again". Would be great if the bug gets fixed in near future :)
</p>
TicketrafoakwaSat, 01 Feb 2014 17:30:20 GMThttps://www.virtualbox.org/ticket/1347#comment:20
https://www.virtualbox.org/ticket/1347#comment:20
<p>
Same problem persists using MAC OS 10.9.1 as host and Windows 7 as guest on VB 4.3.2. A fix would be very much appreciated. Thanks.
</p>
TicketkulpWed, 20 Aug 2014 01:55:59 GMThttps://www.virtualbox.org/ticket/1347#comment:21
https://www.virtualbox.org/ticket/1347#comment:21
<p>
There is a workaround. I had this problem with Mac OS X 10.9.4 as the host and Debian with kernel 2.6.32-5-amd64 as the guest. I found that uninstalling the Oracle Extension pack (EHCI host) and using the default <a class="wiki" href="https://www.virtualbox.org/wiki/VirtualBox">VirtualBox</a> USB 1.1 support causes my flashing of my Digilent Nexys3 board to work properly.
</p>
<p>
This is not an option for many people, but it does demonstrate that there is the possibility of getting it to work, so perhaps someone sufficiently motivated would like to explore the reason it works with USB 1.1 and not USB 2.0 (but since the Oracle extension pack is binary-only, that means it would have to be Oracle ... somehow this seems unlikely.)
</p>
Ticket