﻿ticket,summary,version,host,created,modified,_changetime,_description,_reporter
21312,USB Device unknown,VirtualBox-7.0.4,Linux,2022-11-25T05:53:03Z,2022-12-13T15:33:13Z,2022-12-13T15:33:13Z,"Windows7 x64 is installed on the guest system, after applying the VirtualBox 7.0.x update, there were problems with the USB device enumerator. If the memory on the guest system is less than 2068Mb, then everything works (found out experimentally). If you set more memory (2068Mb or more), then when connecting USB devices (barcode scanner, smartphone, etc.), error Code 43 occurs and the device manager identifies the equipment as USB/Unknown.",CrayZD
21218,USB drives do not connect to Virtualbox 7.0.2 under macOS host,VirtualBox-7.0.2,Mac OS X,2022-10-29T22:53:41Z,2023-01-18T18:59:17Z,2023-01-18T18:59:17Z,"Attempting to attach a USB drive from the host os (macOS) to the guest (Lubuntu) fails, even when drives are unmounted on the host, and an appropriate USB filter has been defined. Errors as follows:


{{{
Failed to attach the USB device SanDisk Cruzer [0100] to the virtual machine Lubuntu 2.
Failed to create a proxy device for the USB device. (Error: VERR_SHARING_VIOLATION).
}}}

Log attached.

{{{
Failed to attach the USB device SanDisk Cruzer [0100] to the virtual machine Lubuntu 2.
Could not find a USB device with uuid {}.
Callee RC:
NS_ERROR_FAILURE (0X80004005)
}}}


",ianr77
21436,Coral USB EdgeTPU runs high then disappear from host,VirtualBox-6.1.42,Mac OS X,2023-01-27T12:34:35Z,2023-01-27T12:34:35Z,2023-01-27T12:34:35Z,"Running on MacPro 4,1 with macOS 10.13.x (High Sierra) and have 3 machines running. Google Coral should be running in the 10-40ms range with 5-6 cameras. 

Machine 1 - Home-assistant runs perfect.
 Tried adding Frigate add-on with Coral TPU USB runs high inference >300ms and then disappears from virtual machine and sometimes disconnects from host. Tried different port and a powered USB hub. Always the same results after a while. Upon advice from Frigate NVR developers, moved to separate machine. 

Machine 2 - runs Ubuntu perfectly. 

Machine 3 - running Frigate NVR stand-alone on Debian guest
Same as above. Runs high at first (100ms) and then goes higher >300ms and disconnects from guest but not from host. 

Why does the Coral run so high and why does it disconnect? 
                  ",Frank61
19515,Virtualbox disconnects USB drives without first unmounting them,VirtualBox 6.1.6,Mac OS X,2020-04-20T10:40:02Z,2020-12-31T23:22:43Z,2020-12-31T23:22:43Z,"I'm using a macOS 10.15.4 host with Virtualbox 6.1.6 with a Windows 7 guest. If I select a USB drive already mounted on the host to connect to the guest from the machine USB menu the drive gets suddenly disconnected without first unmounting it thus causing filesystem inconsistencies and data loss. The same thing happens with linux guests.

I'd happily attach a log but I'm afraid of losing data on my USB backup hard drive so I hope this is alright.

Thanks in advance.",gio91ber
19426,USB-to-Ethernet crash with Ubuntu guest and Windows 10 host,VirtualBox 6.1.4,Windows,2020-03-23T22:58:21Z,2020-03-24T01:41:52Z,2020-03-24T01:41:52Z,"Hi,

I'm passing a USB 3.0 USB-to-Ethernet adapter to a Ubuntu 18.04 VM running on a Windows 10 host. After a few seconds of high bandwidth data transfer, the xhci driver in the guest crashes with the following output in dmesg:

{{{
[ 2556.648728] xhci_hcd 0000:00:0c.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 4 comp_code 13
[ 2556.648734] xhci_hcd 0000:00:0c.0: Looking for event-dma 00000000381ff450 trb-start 00000000381ff300 trb-end 00000000381ff300 seg-start 00000000381ff000 seg-end 00000000381ffff0
}}}

The bug happens whether or not I have the guest additions installed. I've tested that this bug does NOT occur when using the same adapter on either a native Windows 10 or Ubuntu machine. I also tried updating the kernel and drivers in the guest VM to the latest version but the bug still occurs. The bug also seems to happen with a variety of USB 3.0 USB-to-Ethernet adapters.

Notably the bug seems to happen on several Dell laptops (Dell Precision 5520). I tested the same setup on an HP laptop with an Ubuntu host but the issue did not appear.",xynith
19413,Silent fail of inotify_add_watch,VirtualBox 6.1.4,Linux,2020-03-18T10:13:21Z,2020-03-18T10:13:21Z,2020-03-18T10:13:21Z,"To watch new USB devices, ''VBoxSVC'' use ''inotify_add_watch'' on ''/dev/vboxusb''. If ''inotify_add_watch'' fails, USB redirection will silently fail (no log nor warnings).

''inotify_add_watch'' may fail if the limit of watches is already reached. The limit is quite low on a default stable debian install (8192) and several modern text editors use a lot of watches to... watch directories and subdirectories.

Step to reproduce the problem:
1] make sure that VBoxSVC isn't running
2] check that the limit is not too high ''cat /proc/sys/fs/inotify/max_user_watches'', if it is, just temporarily decrease it: ''echo 1000 | sudo tee /proc/sys/fs/inotify/max_user_watches''
3] drain all the watches (for example by executing ''inotifywatch -r'' on a folder with a lot of subfolders.
4] run ''VBoxSVC'', you may ''strace'' it to make sure that ''inotify_add_watch'' fails
5] run ''VBoxManage list usbhost''
6] observe that ''inotify_add_watch'' fails in ''VBoxSVC'' and that ''VBoxManage list usbhost'' returns nothing.
7] [optionnal] use this script to check who's using all the watches: https://raw.githubusercontent.com/fatso83/dotfiles/master/utils/scripts/inotify-consumers

''VBoxSVC'' should return an error that ''VBoxManage list usbhost'' and VirtualBox gui client could display to easily diagnose the problem and maybe hint on a solution (kill the process using all the watches or increase the limit).

There may be other use of ''inotify_add_watch'' in the VBox codebase and there may be other code path to check (for example, there is also a restriction on the number of inotify **instances**, cf. ''/proc/sys/fs/inotify/max_user_instances'', that may cause ''inotify_init'' to fail). ",elvanderb
21225,USB,VirtualBox 6.1.38,Linux,2022-10-31T19:56:56Z,2022-11-04T12:30:09Z,2022-11-04T12:30:09Z,"USB is shown as working just fine when defining the Guest VM xppro
however, when xppro is run and accessing Devises the USB section is grayed out.

Running Linux Mint 20 Ulyssa",buz
21118,USB isochronous transfers cause problems under OS/2 guest,VirtualBox 6.1.38,Windows,2022-10-03T07:04:10Z,2022-10-03T07:15:20Z,2022-10-03T07:15:20Z,"Host: Windows 11, guest: OS/2

If I try to play sounds via a USB connected audio 1.0 or audio 2.0 sound device, the sound always is extremely choppy.
This directly relates to ticket #18947, but this time I selected ""USB"" as the component instead of ""Audio"" because this clearly is a USB issue with isochronous transfers.
If needed, I could provide tracing information from the guest USB audio driver or I could provide additional analysis if requested (thinking about the ""samples per microframe"" value that the USB audio 2.0 device reports back on its ""sync isochronous in"" endpoint).",lerdmann
21339,"USB Filter PortNumber field formatting for ports higher than 9 => fixed in SVN/next 7.0.x,6.1.x maintenance",VirtualBox 6.1.36,Windows,2022-12-14T20:31:59Z,2022-12-19T08:54:13Z,2022-12-19T08:54:13Z,"Inability to insert a PortNumber higher than 9, the ""Port"" field of the USB Filter only accepts numeric characters, this makes the insertion of port numbers higher than 9 not possible, considering that this field reads hexadecimal inputs, the insertion of a port number like 13(000d) not possible.
As a workaround, manual input of the hex value in the .vbox file of the guest works.

For further information: https://forums.virtualbox.org/viewtopic.php?f=6&t=108063",fantinel
21019,VirtualBox 6.1.34a causing BSOD when plugging in ST-LINK/V2,VirtualBox 6.1.34,Windows,2022-07-10T02:56:55Z,2022-07-10T03:06:11Z,2022-07-10T03:06:11Z,"Hello, I am attempting to connect an LPC1114 to an Ubuntu 18.04.6 VM running on VirtualBox 6.1.34a via an ST-LINK/V2. Shortly after connecting the device and adding it to the Ubuntu VM, my personal machine experienced a BSOD which threw PNP_DETECTED_FATAL_ERROR (ca). 

This BSOD recurred 2 more times, only when VirtualBox was running and the device was plugged in simultaneously, the BSOD did not occur when either event happened individually.

Taking a look at the minidump, it seems IoGetDevicePropertyData and VBoxUSBMon have something to do with it. Attached are the relevant minidump and VM log.",camcom
20819,Upgrading to 6.1.32 Failed due to USB permissions...,VirtualBox 6.1.32,Windows,2022-02-09T20:30:28Z,2022-02-09T20:30:28Z,2022-02-09T20:30:28Z,"Going trough the regular standard VirtualBox upgrade noticed upgrade to 6.1.32 failed and succeed in two different computers.

My work computer which is secured and by AD blocked the usage of USB due to Data Security requirements, failed to start after install the upgrade to 6.1.32.

However at home computer doing the exactly same upgrade, succeed because there was not constrain about the USB Security at home and not ruled by Windows AD Group Policy filtering USB.

Just like to report, being more agnostic and less intrusive will allow the usage and embracement of VirtualBox more widely.

Thank you for this fantastic product. please keep doing the great work.

Best Regards Dinooz ",Dinooz
20725,VirtualBox OHCI-controller randomly skips sending URBs to the host,VirtualBox 6.1.30,all,2021-12-14T13:35:43Z,2022-04-06T09:23:41Z,2022-04-06T09:23:41Z,"Hello!

I have noticed some problems with USB 1.1 devices under VirtualBox.

First, I noticed that when I work with smart cards on VMs, sending some random APDU commands fails. For the test, I generate and destroy key pairs in a loop. I looked at the libccidand libusb log and found that at some point sending of the command gets stuck and fails when send operation timeout exceeds:
{{{
00000003 sending: 00 40 05 80 71 00 00 00 B4
00000005 -> 000000 6F 09 00 00 00 00 8E 00 00 00 00 40 05 80 71 00 00 00 B4
[133.818293] [00029ac3] libusb: debug [libusb_submit_transfer] transfer 0x7f04880010d8
[133.818297] [00029ac3] libusb: debug [add_to_flying_list] arm timer for timeout in 5000ms (first in line)
[133.818302] [00029ac3] libusb: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 19
[133.818479] [00029ac3] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[133.818486] [00029ac3] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
[138.818506] [00029ac3] libusb: debug [usbi_wait_for_events] poll() returned 1
[138.818545] [00029ac3] libusb: debug [libusb_cancel_transfer] transfer 0x7f04880010d8
[138.835720] [00029ac3] libusb: debug [arm_timer_for_next_timeout] no timeouts, disarming timer
[138.835771] [00029ac3] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[138.835775] [00029ac3] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
[138.835781] [00029ac3] libusb: debug [usbi_wait_for_events] poll() returned 1
[138.835787] [00029ac3] libusb: debug [reap_for_handle] urb type=3 status=-2 transferred=0
[138.835790] [00029ac3] libusb: debug [handle_bulk_completion] handling completion status -2 of bulk urb 1/1
[138.835792] [00029ac3] libusb: debug [handle_bulk_completion] abnormal reap: urb status -2
[138.835794] [00029ac3] libusb: debug [handle_bulk_completion] abnormal reap: last URB handled, reporting
[138.835797] [00029ac3] libusb: debug [usbi_handle_transfer_cancellation] detected timeout cancellation
[138.835799] [00029ac3] libusb: debug [arm_timer_for_next_timeout] no timeouts, disarming timer
[138.835802] [00029ac3] libusb: debug [usbi_handle_transfer_completion] transfer 0x7f04880010d8 has callback 0x7f049c94c850
[138.835804] [00029ac3] libusb: debug [sync_transfer_cb] actual_length=0
[138.835807] [00029ac3] libusb: debug [libusb_free_transfer] transfer 0x7f04880010d8
05017523 ccid_usb.c:857:WriteUSB() write failed (2/17): -7 LIBUSB_ERROR_TIMEOUT
00000004 openct/proto-t1.c:215:t1_transceive() fatal: transmit/receive failed
00000012 ifdhandler.c:1821:IFDHICCPresence() usb:072f/90cc:libudev:0:/dev/bus/usb/002/017 (lun: 0)
00000027 -> 000000 65 00 00 00 00 00 8F 00 00 00
[138.835862] [000299fb] libusb: debug [libusb_submit_transfer] transfer 0x7f04900013f8
[138.835865] [000299fb] libusb: debug [add_to_flying_list] arm timer for timeout in 5000ms (first in line)
[138.835870] [000299fb] libusb: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 10
[138.835901] [000299fb] libusb: debug [libusb_handle_events_timeout_completed] doing our own event handling
[138.835904] [000299fb] libusb: debug [usbi_wait_for_events] poll() 3 fds with timeout in 60000ms
00000057 SW:
00000002 ifdwrapper.c:543:IFDTransmit() Card not transacted: 612
00000002 winscard.c:1620:SCardTransmit() Card not transacted: 0x80100016
}}}

After, I decided to look at the usbmon log (at the virtual machine) and found that sending of some URBs fail with -2 callback status:
{{{
ffff9e538d484e40 2827121885 S Bo:2:017:2 -115 19 = 6f090000 00008d00 00000000 05804000 0000c5
ffff9e538d484e40 2827124488 C Bo:2:017:2 0 19 >
ffff9e538d484e40 2827124733 S Bi:2:017:2 -115 65556 <
ffff9e538d484e40 2827128522 C Bi:2:017:2 0 16 = 80060000 00008d00 00000000 02900092
ffff9e538d484e40 2827180820 S Bo:2:017:2 -115 19 = 6f090000 00008e00 00000040 05807100 0000b4
ffff9e538d484e40 2832198155 C Bo:2:017:2 -2 0
ffff9e538d484e40 2832198387 S Bo:2:017:2 -115 10 = 65000000 00008f00 0000
ffff9e538d484e40 2832219064 C Bo:2:017:2 0 10 >
ffff9e538d484e40 2832219163 S Bi:2:017:2 -115 10 <
}}}

To make sure that the problem is not caused by a small timeout (libccid uses 5 second timeout), I disabled it. After that sending failed URBs gets stuck forever and usbmon log looks like this:
{{{
ffff9e538d484e40 2827121885 S Bo:2:017:2 -115 19 = 6f090000 00008d00 00000000 05804000 0000c5
ffff9e538d484e40 2827124488 C Bo:2:017:2 0 19 >
ffff9e538d484e40 2827124733 S Bi:2:017:2 -115 65556 <
ffff9e538d484e40 2827128522 C Bi:2:017:2 0 16 = 80060000 00008d00 00000000 02900092
ffff9e538d484e40 2827180820 S Bo:2:017:2 -115 19 = 6f090000 00008e00 00000040 05807100 0000b4
}}}

I decided to look at usbmon log of the host machine and found that the failed URBs aren't sent at all, and the log looks like this:
{{{
ffff9e538d484e40 2827121885 S Bo:2:017:2 -115 19 = 6f090000 00008d00 00000000 05804000 0000c5
ffff9e538d484e40 2827124488 C Bo:2:017:2 0 19 >
ffff9e538d484e40 2827124733 S Bi:2:017:2 -115 65556 <
ffff9e538d484e40 2827128522 C Bi:2:017:2 0 16 = 80060000 00008d00 00000000 02900092
}}}

Also, I found how to get usbmon log of an emulated root hub controller. Failed commands don't appear there too.

I decided that maybe there is a problem with OHCI controller emulation. During debugging I noticed that after failure HeadP and TailP of Bulk List ED (Endpoint Description) are set and aren't equal, but the OHCI controller doesn't process it, because BLF (Bulk List Filled) status is not set.

After discovering the problem, I found there is some problem with cache. To prove it I added logging of bulk_head, status at the beginning of the StartFrame function and before calling the ServiceBulkList function. I also added logging of cached and real values of TailP and HeadP at the ServiceBulkList function.

Extra log patch:
{{{
diff --git a/src/VBox/Devices/USB/DevOHCI.cpp b/src/VBox/Devices/USB/DevOHCI.cpp
index 45b23dd9..713a84a5 100644                                                                                                                                                                               	 
--- a/src/VBox/Devices/USB/DevOHCI.cpp
+++ b/src/VBox/Devices/USB/DevOHCI.cpp
@@ -1564,6 +1564,14 @@ DECLINLINE(void) ohciR3ReadEd(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd)
 #endif
 }
 
+/**
+ * Reads an OHCIED without caching.
+ */
+DECLINLINE(void) ohciR3ReadEdWithoutCaching(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd)
+{
+	ohciR3GetDWords(pDevIns, EdAddr, (uint32_t *)pEd, sizeof(*pEd) >> 2);
+}
+
 /**
  * Reads an OHCITD.
  */
@@ -3746,12 +3754,18 @@ static void ohciR3ServiceBulkList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThis
     	&& (cIterations-- > 0))
 	{
     	OHCIED Ed;
+    	OHCIED RealEd;
 
     	/* Bail if previous processing ended up in the unrecoverable error state. */
     	if (pThis->intr_status & OHCI_INTR_UNRECOVERABLE_ERROR)
         	break;
 
+
     	ohciR3ReadEd(pDevIns, EdAddr, &Ed);
+    	ohciR3ReadEdWithoutCaching(pDevIns, EdAddr, &RealEd);
+   	if (Ed.TailP != RealEd.TailP || Ed.HeadP != RealEd.HeadP)
+       	Log((""Cached and real Ed mismatch: EdAddr: 0x%x. Ed.HeadP: cached=0x%x real=0x%x. Ed.TailP: cached=0x%x real=0x%x\n"", EdAddr, Ed.HeadP, RealEd.HeadP, Ed.TailP, RealEd.TailP));
+
     	Assert(!(Ed.hwinfo & ED_HWINFO_ISO)); /* the guest is screwing us */
     	if (ohciR3IsEdReady(&Ed))
     	{
@@ -4286,6 +4300,8 @@ static void ohciR3StartOfFrame(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThisCC)
 	/*
  	* Bulk EPs.
  	*/
+
+	Log((""StartOfFrame: Bulk head: 0x%x. Status: 0x%x\n"", pThis->bulk_head, pThis->status));
 	if (	(pThis->ctl & OHCI_CTL_BLE)
     	&&  (pThis->status & OHCI_STATUS_BLF))
     	ohciR3ServiceBulkList(pDevIns, pThis, pThisCC);
@@ -4350,6 +4366,8 @@ static DECLCALLBACK(bool) ohciR3StartFrame(PVUSBIROOTHUBPORT pInterface, uint32_
 
 	ohciR3Lock(pThisCC);
 
+	Log((""StartFrame: Bulk head: 0x%x. Status: 0x%x\n"", pThis->bulk_head, pThis->status));
+
 	/* Reset idle detection flag */
 	pThis->fIdle = true;
}}}

I got the following logs:
1. usbmon_token.log -- usbmon log on the VM
2. vb_token.log -- VirtualBox log with enabled dev_ohci (lvl 2, 3, 4) logging

As you can see cached and real value of TailP are mismatched before data interchange stuck. Also, BLF status is set before reading mismatched cache:
{{{
StartFrame: Bulk head: 0x349d1150. Status: 0x0
ohciR3ReadTd(,0x349d3120,): R=1 DP=2 DI=0 T=0 EC=0 CC=0xf CBP=0x02f72000 NextTD=0x349d30c0 BE=0x02f72007 UNK=0x0
ohciR3ReadTd(,0x349d3120,): R=1 DP=2 DI=0 T=0 EC=0 CC=0xf CBP=0x02f72000 NextTD=0x349d30c0 BE=0x02f72007 UNK=0x0
ohciR3ReadTd(,0x349d3120,): R=1 DP=2 DI=0 T=0 EC=0 CC=0xf CBP=0x02f72000 NextTD=0x349d30c0 BE=0x02f72007 UNK=0x0
ohciR3ReadTd(,0x349d3120,): R=1 DP=2 DI=0 T=0 EC=0 CC=0xf CBP=0x02f72000 NextTD=0x349d30c0 BE=0x02f72007 UNK=0x0
ohci: Updating HCCA on frame 0x3c4d
StartOfFrame: Bulk head: 0x349d1150. Status: 0x4
Cached and real Ed mismatch: EdAddr: 0x349d1150. Ed.HeadP: cached=0x349d31e0 real=0x349d31e0. Ed.TailP: cached=0x349d31e0 real=0x349d3300
ohciR3StartOfFrame: HcCommandStatus=0x00000000: HCR=0 CLF=0 *BLF=0 OCR=0 SOC=0
*FLUSH*
HcBulkHeadED_w(0x349d1150) - old=0x349d11c0 new=0x349d1150
HcBulkCurrentED_w(0x00000000) - old=0x00000000 new=0x00000000
HcControl_w(0x000002af) => CBSR=3 PLE=1 IE=1 CLE=0 *BLE=1 HCFS=0x2 IR=0 RWC=1 RWE=0
HcCommandStatus_w(0x00000004) => HCR=0 CLF=0 *BLF=1 OCR=0 SOC=0
*END*
}}}

I tried to describe the condition which leads to stuck. I think the following happens:
1. HC enters the StartFrame function;
2. HC updates cache;
3. HCD fills TD list and sets HeadP and TailP for Bulk List;
4. HCD sets Bulk List pointer via registers;
5. HCD set BLF status;
6. HC sees that BLF status is set and enters the ServiceBulkList function;
7. HC reads old cached values of HeadP and TailP functions and sees that the TD list is not ready. Therefore it unchecks BLF status.
8. HC enters the StartFrame again at the next iteration. It sees that BLF status is unchecked and doesn't process the Bulk List (but cached values of TailP and TailP are already equal).
9. HCD waits for the Bulk List will be serviced.


I think about some solutions for this problem:
1. Set the invalidate cache flag inside some register setter functions and invalidate cache inside R3 if it's set. But it may lead to a decrease in performance.
2. Disable caching at all. It decreases performance too, but helps to avoid headaches.
3. Avoid some symptoms of the problem. If cached EDs are not ready, but the corresponding status is set, then check ED directly from memory. It's probably a bad solution, because there are some cases where cached ED is ready, but real is not. Nevertheless, it may be better for performance.

I wrote a patch for the last solution and it helped me (it's draft):
{{{
diff --git a/src/VBox/Devices/USB/DevOHCI.cpp b/src/VBox/Devices/USB/DevOHCI.cpp
index 45b23dd9..e34c0ebb 100644
--- a/src/VBox/Devices/USB/DevOHCI.cpp
+++ b/src/VBox/Devices/USB/DevOHCI.cpp
@@ -1550,20 +1550,25 @@ DECLINLINE(void) ohciR3CacheTdUpdate(POHCICC pThisCC, RTGCPHYS32 TdAddr, PCOHCIT
 /**
  * Reads an OHCIED.
  */
-DECLINLINE(void) ohciR3ReadEd(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd)
+DECLINLINE(void) ohciR3ReadEdEx(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd, bool cached)
 {
 # ifdef VBOX_WITH_OHCI_PHYS_READ_STATS
 	physReadStatsUpdateDesc(&g_PhysReadState.ed, EdAddr);
 	physReadStatsUpdateDesc(&g_PhysReadState.all, EdAddr);
 # endif
 #ifdef VBOX_WITH_OHCI_PHYS_READ_CACHE
-	POHCICC pThisCC = PDMDEVINS_2_DATA_CC(pDevIns, POHCICC);
-	ohciR3PhysReadCacheRead(pDevIns, &pThisCC->CacheED, EdAddr, pEd, sizeof(*pEd));
+	if (cached) {
+    	POHCICC pThisCC = PDMDEVINS_2_DATA_CC(pDevIns, POHCICC);
+    	ohciR3PhysReadCacheRead(pDevIns, &pThisCC->CacheED, EdAddr, pEd, sizeof(*pEd));
+	}
 #else
 	ohciR3GetDWords(pDevIns, EdAddr, (uint32_t *)pEd, sizeof(*pEd) >> 2);
 #endif
 }
 
+#define ohciR3ReadEd(pDevIns, EdAddr, pEd) \
+ 	ohciR3ReadEdEx(pDevIns, EdAddr, pEd, 1)
+
 /**
  * Reads an OHCITD.
  */
@@ -3701,6 +3706,31 @@ DECLINLINE(bool) ohciR3IsEdReady(PCOHCIED pEd)
      	&& !(pEd->hwinfo & ED_HWINFO_SKIP);
 }
 
+/**
+ * Tries to get ready an OHCIED from cache and on fail dirrectly from memory.
+ */
+DECLINLINE(bool) ohciR3TryReadReadyEd(PPDMDEVINS pDevIns, uint32_t EdAddr, POHCIED pEd)
+{
+#ifdef VBOX_WITH_OHCI_PHYS_READ_CACHE
+	ohciR3ReadEdEx(pDevIns, EdAddr, pEd, 1);
+	if (ohciR3IsEdReady(pEd))
+    	return true;
+#endif
+
+	ohciR3ReadEdEx(pDevIns, EdAddr, pEd, 0);
+	if (ohciR3IsEdReady(pEd)) {
+#ifdef VBOX_WITH_OHCI_PHYS_READ_CACHE
+    // Cache contains old page. Invalidate it.
+    	POHCICC pThisCC = PDMDEVINS_2_DATA_CC(pDevIns, POHCICC);
+    	ohciR3PhysReadCacheInvalidate(&pThisCC->CacheED);
+    	ohciR3PhysReadCacheInvalidate(&pThisCC->CacheTD);
+#endif
+    return true;
+	}
+
+	return false;
+}
+
 
 /**
  * Checks if an endpoint has TDs queued (not necessarily ready to have them processed).
@@ -3751,9 +3781,9 @@ static void ohciR3ServiceBulkList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThis
     	if (pThis->intr_status & OHCI_INTR_UNRECOVERABLE_ERROR)
         	break;
 
-    	ohciR3ReadEd(pDevIns, EdAddr, &Ed);
+    	bool ready = ohciR3TryReadReadyEd(pDevIns, EdAddr, &Ed);
     	Assert(!(Ed.hwinfo & ED_HWINFO_ISO)); /* the guest is screwing us */
-    	if (ohciR3IsEdReady(&Ed))
+    	if (ready)
     	{
         	pThis->status |= OHCI_STATUS_BLF;
         	pThis->fBulkNeedsCleaning = true;
@@ -3909,9 +3939,9 @@ static void ohciR3ServiceCtrlList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThis
     	if (pThis->intr_status & OHCI_INTR_UNRECOVERABLE_ERROR)
         	break;
 
-    	ohciR3ReadEd(pDevIns, EdAddr, &Ed);
+    	bool ready = ohciR3TryReadReadyEd(pDevIns, EdAddr, &Ed);
     	Assert(!(Ed.hwinfo & ED_HWINFO_ISO)); /* the guest is screwing us */
-    	if (ohciR3IsEdReady(&Ed))
+    	if (ready)
     	{
 # if 1
         	/*
@@ -3928,8 +3958,7 @@ static void ohciR3ServiceCtrlList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC pThis
                 	pThis->status |= OHCI_STATUS_CLF;
                 	break;
             	}
-            	ohciR3ReadEd(pDevIns, EdAddr, &Ed); /* It might have been updated on URB completion. */
-        	} while (ohciR3IsEdReady(&Ed));
+        	} while (ohciR3TryReadReadyEd(pDevIns, EdAddr, &Ed));
 # else
         	/* Simplistic, for debugging. */
         	ohciR3ServiceHeadTd(pThis, VUSBXFERTYPE_CTRL, &Ed, EdAddr, ""Control"");
@@ -3991,8 +4020,7 @@ static void ohciR3ServicePeriodicList(PPDMDEVINS pDevIns, POHCI pThis, POHCICC p
     	if (pThis->intr_status & OHCI_INTR_UNRECOVERABLE_ERROR)
         	break;
 
-    	ohciR3ReadEd(pDevIns, EdAddr, &Ed);
-    	if (ohciR3IsEdReady(&Ed))
+    	if (ohciR3TryReadReadyEd(pDevIns, EdAddr, &Ed))
     	{
         	/*
          	* ""There is no separate head pointer of isochronous transfers. The first
}}}

I admit that you may have no USB 1.1 smart card to reproduce the bug. So, I found how to reproduce the bug via USB 1.1 flash drive (or via any other flash drive connected via USB 1.1 hub).

I wrote a test thatmounts and unmounts a flash drive in a loop, and noticed that sometimes the execution of these operations takes a lot of time.

test.sh:
{{{
i=0
while true
do
    i=$(($i+1))
    echo ""Iteration $i""
    date +""%T""
    mount /dev/sdb1 /media/kek || break
    umount /dev/sdb1 || break
done
}}}

output:
{{{
Iteration 1
18:06:49
Iteration 2
18:06:51
Iteration 3
18:07:26
Iteration 4
18:07:28
Iteration 5
18:07:30
}}}

Inside the OHCI log I found the same problem as for a smart card:
usbmon_falsh.log -- usbmon log for looped mount and unmount
vb_flash.log -- VirtualBox output

What do you think about that? May you confirm the bug? Will it be fixed?

Also, I found some problems with EHCI controller emulation, but will write about that in another bug.

Waiting for your response!
Thanks!",lo1ol
20774,CP2102 USB to UART Bridge Ctrl - USB Device Connection Echec (0x80004005),VirtualBox 6.1.30,Windows,2022-01-16T18:45:44Z,2022-01-16T21:38:14Z,2022-01-16T21:38:14Z,"The Silicon Labs CP2102 USB to UART Bridge Controller doesn't work as expected.

Host : Windows 10
Guest : Windows XP SP3",ManWithNoName
20762,VM crash after KVMS switch,VirtualBox 6.1.30,Linux,2022-01-07T02:17:10Z,2022-01-07T02:17:10Z,2022-01-07T02:17:10Z,"See [https://forums.virtualbox.org/viewtopic.php?f=7&t=104891&sid=51cd5f0216603e8bec8562fd1da4b3bc] for more information.

Environment:

I have multiple PCs connected by a keyboard-video-mouse-switch (KVMS, to clearly distinguish from kvm, the kernel virtualization subsystem).  The KVMS is a FJGear USB2.0 HDMI KVM model FJ-401HUA.  I will refer to these PCs as A, B, and C.  All 3 boxes are hosting Devuan Beowulf, and all VMs running on all boxes are running Devuan Beowulf Ascii, Beowulf, or Chimaera under virtualbox 6.1.30.  All hosts are running the latest virtualbox extensions, and guests are running the latest virtualbox guest additions.

Description of the Problem:

The problem is that switching between two of these boxes causes a VM running USB 3 to crash.  After an initial switch from A to B and back to A, one VM running USB 3 on A had crashed.  In one instance, switching a second time after this from A to B and back to A, all but one VM running USB 3 had crashed and even a VM running USB 2 had also crashed.  

Detail:

I run virtualbox on PCs A and B.   I use PC A for most of my regular activities; B and C are ""test"" boxes.  However, despite B being a testbox, I do have the VMs on B networked together with some of the VMs on A.  The 3 PCs are networked through an electronic ethernet switch.

The KVMS does work, although there is a bit of a wait for the video to re-sync after a switch.   The KVMS is capable up to 1920x1080, which matches my monitor's resolution.   Normally, I don't notice any peculiar behavior related to using the manual buttons on the face of the unit.  There are some messages logged after each switch, but they have never caused an issue until I changed the VM (the one that crashed) to USB 3.

I have attached the log for the crashed VM (see above link).  These logs were created by saving them from the log dialog box in the virtualbox GUI.  I have not modified them other than to obfuscate private information.  The logs are cut short for some reason, but it is NOT related to the obfuscation script.  I can save the logs again, from the GUI again, and the same results occur.   The line counts of the log files match before and after obfuscation.


",Harry M
20696,Port Change Detect (PCD) bit not set on port change interrupt (xHCI),VirtualBox 6.1.30,Mac OS X,2021-11-28T00:23:46Z,2021-12-01T20:01:54Z,2021-12-01T20:01:54Z,"The XHCI emulation fails to set the Port Change Detect (PCD) bit (bit 4) in the USB 
Status Register on a port change interrupt as described in the ""eXtensible Host Controller 
Interface for Universal Serial Bus (xHCI) Requirements Specification May 2019 Revision 
1.2"" section 5.4.2.

When real hardware generates a port change interrupt the Port Change Detect (PCD) bit 
is always set. In the VirtualBox VM, when a port change interrupt occurs, the USB Status 
Register only contains the Event Interrupt (EINT) bit set, and not the Port Change Detect 
(PCD) bit. This does not match the way real hardware works.

This (obviously) affects all guest OSes, and is not limited to specific ones.

I have not tested this on other host platforms.",Lewis Rosenthal
20652,USB passthrough fails for Linux hosts and Windows VM with 6.1.28,VirtualBox 6.1.28,Linux,2021-11-08T03:45:07Z,2021-11-23T05:01:03Z,2021-11-23T05:01:03Z,"With version 6.1.28 running on a Linux Host and a Windows 7 or 10 guest, some USB passthrough operations fail.

This was first reported at https://bugzilla.opensuse.org/show_bug.cgi?id=1192338 where the reporter noted that he could not attach an iPhone to iTunes through his Windows 10 VM on an openSUSE Leap 15.3 host. He also notes that when the VM is closed, there is no power on the USB port until he reboots.

I further tested using an RTL8188EUS Wifi dongle passed through to a Windows 7 or 10 guest from an openSUSE Tumbleweed host. In this case, the Windows software creates a network device, but is unable to complete setting it up. This operation worked with 6.1.26.

I tested my setup using the Oracle binary RPM for openSUSE Leap 15. It had the same problem.",Larry Finger
20532,BSOD when un-plugging USB device with Windows 10 Host and Windows 7 Guest (VM On),VirtualBox 6.1.26,Windows,2021-09-02T15:52:06Z,2021-09-02T15:52:06Z,2021-09-02T15:52:06Z,"Host : Microsoft Windows [version 10.0.19042.1165]
Guest : Windows 7

step 1 : (OK)
- run the guest VM
- plug USB devices

step 2a : (OK)
- switch off the VM
- un-plug USB devices

step 2b : (HOST BSOD and reset)
- un-plug USB devices while VM is still running

",ManWithNoName
20530,Request Ability To Share Smartcard With Host and Guest,VirtualBox 6.1.26,other,2021-08-31T15:09:38Z,2021-08-31T15:09:38Z,2021-08-31T15:09:38Z,"Currently, VMWare Player is the only known software that allows the ability to share the USB smartcard reader with the host while still allowing the guest to read the smartcard. Virtualbox takes the smartcard away from the host and only allows the guest to see it when you attempt to activate the smartcard reader on the guest. With certain Windows security settings enabled, this effectively causes the host to immediately lock the screen, preventing the user from doing anything. I request to add this feature that has been long-supported in VMWare Player where the Host and Guest are able to share a connected smartcard.",Capt_Ahab
20506,Attaching Yubikey USB device to VM causes Guest VM to Crash within Seconds,VirtualBox 6.1.26,Mac OS X,2021-08-18T20:19:16Z,2021-08-19T08:31:39Z,2021-08-19T08:31:39Z,"Host OS: macOS 11.5.1
Guest OS: Ubuntu 20.04.2.0 x64 with Guest Additions installed
VBox: 6.1.26

Within the Guest OS, when accessing a website that uses FIDO/U2F authentication with a Yubikey USB device, I attached the Yubikey to my host machine and then used the Devices | USB menu to pass through the Yubikey USB device to the Guest machine.  The device worked properly and authentication with the website succeeded within the guest.  However within a few seconds (perhaps 5 seconds) the guest VM process crashed and macOS displayed a ""Problem Report for VirtualBox VM"" dump report window with stack traces (see attachment).  I repeated this three times and each time the crash occurred.  On the third time, after successfully passing through and authenticating with the Yubikey USB device, I quickly accessed the Devices menu to detach the Yubikey USB device, which detachment appeared to succeed (the checkmark next to it was removed), however, again, a few seconds later the guest VM process crashed.  ",OtterFlip
20442,XHCI has wrong PCI config space and runtime register settings,VirtualBox 6.1.22,Windows,2021-06-30T21:17:30Z,2021-07-05T07:24:04Z,2021-07-05T07:24:04Z,"host: Win-10, guest: OS/2

These PCI config space registers contain incorrect values (without being touched by any driver):
SBRN: is=0x20 should be=0x30 (only allowed value)
FLADJ: is=0x00 should be=0x20 (default value)

Additionally, runtime register MFINDEX is upcounting and wrapping even though the operational USBCMD register does not have the ""R/S"" bit set (""run"").

This is according to XHCI spec. I am not enough of a virtual machine expert to know if it is the USB HW that is not working according to spec or if it is the virtualization.

I have tried to get XHCI working with the corresponding XHCI driver (for OS/2) but it would not work. Not sure if that's the HW/virtualization or the HC driver doing the wrong thing.",lerdmann
20376,USB Moxa UPort1150l device cannot start Code 10,VirtualBox 6.1.22,Windows,2021-05-24T11:44:18Z,2021-05-24T11:44:18Z,2021-05-24T11:44:18Z,"Hello!

'''Hardware and hosts:[[BR]]'''

Dell Precision 7520 Windows 10 company based 20H2 (year ago some older version)[[BR]]

Virtual Windows 7 - all updates[[BR]]


I have found that about a year ago my Uport was working fine with Win7. After a update VM and extensions it stopped working. Now I have tested also this with new fresh Win7 installation and same problem exist.

In device manager the device status is ""This device cannot start. (Code 10)"". If I try to use some other driver from Moxa like Uport 1150 then result is same.",Vahelduvool
20352,[Guest - windows 7] Cannot detect Qualcomm MMC Storage USB device,VirtualBox 6.1.22,Windows,2021-05-09T22:30:33Z,2021-05-09T22:30:33Z,2021-05-09T22:30:33Z,"*This is a CRITICAL issue related to Android embeded development on Windows guest machine;[[BR]]
Universal Qualcomm USB Driver: [https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/] [[BR]]
Steps to reproduce:
1. Access Edl mode on a Qualcomm-insided Android device (by ADB, test point on board, etc ...) [[BR]]
2. Open Device management on Windows guest OS and check detected usb passthrought devices; [[BR]]
Results:
1. Only host machine detects successfully Qualcomm MMC USB Storage device, we can check in Disk Management programme, it shows all related partitions on on-board MMC storage; [[BR]]
2. Guest machine can NOT detect Qualcomm MMC USB Storage device and all related MMC partitions; [[BR]]

Expectations:
The guest machine should detects Qualcomm MMC USB Storage device and all related MMC partitions [[BR]]

Screenshots: [https://drive.google.com/drive/folders/1MKIm7xnrIDJ0BfPKRLfOJzZmK3z61DGk?usp=sharing]
References:
1. https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ [Adb commandline approach]
2. http://andrux-and-me.blogspot.com/2015/09/bringing-lg-g2-back-from-dead.html [Onboard test point approach]
Thanks team,",Kelvin
19321,"VM crashes often on USB unplug/replug, also out of blue sky",VirtualBox 6.1.2,Linux,2020-02-19T13:14:15Z,2020-03-03T13:35:46Z,2020-03-03T13:35:46Z,"Hi,
this looks like a regression in 6.1.2 and 6.0.16 since I cannot duplicate with 6.0.14.
The VM simply disappears from the screen. Sometimes with no visible reason, but every few USB unplug/replug cycles. I found the USB part since I write some code that communicates to a USB device (CDC-ACM aka ComPort emulation). One of the actions does cause the device to reboot (on purpose).

Other times it sits in the background and when I want to open the VM window again, it is gone. Then sometimes it crashes immediately at start or shortly after. A host reboot brings it back to work (until it crashes randomly again).
Host and guest are running with latest updates.
H: Ubuntu 18.04, 5.3.0-40-generic
G: Win10-64, 19H2 (but also showed at 19h1)

I have not seen a crash with Linux guests, but do not use them often right now.

In the logs I did not find useful hints, I hope you do. Let me know when I can help with debugging.

There is a thread in the forum:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=96829&p=470373#p470373]
",ucrasher2
19240,"windows CE handheld will not connect VirtualBox 6.1, MacOS X host, Windows 7 SP1 guest",VirtualBox 6.1.2,Mac OS X,2020-01-17T19:28:06Z,2020-01-17T19:28:06Z,2020-01-17T19:28:06Z,"This is identical to bug report #12489 that has been closed as obsolete.

I've been using Parallels but didn't  want to continue to upgrade to keep up with MacOS so thought I'd try virtualBox.  This all works fine on Parallels up to and including their current version.  

when I try to connect my Windows CE handheld to the system I get an error that the Microsoft USBSync did not install properly and that the device is not connected.  Also an error from the driver status that the ""device cannot start (code 10)""


Same install of Windows 7 from the same CD and the same downloaded Microsoft Windows Mobile Device Center/drivers on Parallels works fine.
",billj
20118,Failed to create a proxy device for the USB device.,VirtualBox 6.1.16,other,2021-01-08T21:16:33Z,2021-01-08T21:16:33Z,2021-01-08T21:16:33Z,"Hello,

after upgrading to 6.1.16 from 6.0.x USB mounting is not working anymore. The upgrade coincides with Mac OS upgrade to Big Sur version, after which my VirtualBox 6.0 stopped working. Now after upgrade to 6.1.16 I get the following message when trying to connect USB Storage 2.0 and 3.0 to any guest OS:


{{{
00:01:24.433251 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to create a proxy device for the USB device. (Error: VERR_PDM_NO_USB_PORTS)}, preserve=false aResultDetail=-2861
}}}

I have also installed Extensions pack matching 6.1.16 version. Do you know what might be causing the issue?

Thanks!
Dragan

",Dragan
20110,Virtualbox looses track of USB SSD,VirtualBox 6.1.16,Windows,2020-12-31T06:45:36Z,2020-12-31T06:45:36Z,2020-12-31T06:45:36Z,"I've encountered a big glitch. If I create a virtual machine with no virtual drive, and then use a USB filter to attach a USB SSD (WD Passport if it matters) to the virtual machine, then it will find that drive no problem for ONLY the first powercycle. Rebooting without powering down the machine makes no difference. But if you power the machine down (not save state, actually set the machine as turned off), then try to turn it on again, it won't find the SSD. It boots into the EFI shell, and the EFI shell reports no file systems, or it reports the Optical Disc file system if there is one. But it doesn't see the USB drive. The only way I've been able to fix this is to completely delete the machine and re-create from scratch. That's annoying and stupid!
",TheStudent
20018,BSOD when plugging (any) USB device to Windows 10 computer even when no VM is on,VirtualBox 6.1.16,Windows,2020-11-05T07:36:22Z,2020-11-05T07:36:22Z,2020-11-05T07:36:22Z,"For my windows laptop this issue occurs for at least couple of newest builds of VirtualBox 6.1.x versions. The issue haven't occurred on version 6.0.24 for me.

Every time I connect any USB device to my laptop AFTER starting VBox (but not necessarily any VMs) BSOD occurs.

VBoxUSBMon.sys seems to cause PNP_DETECTED_FATAL_ERROR.

Some of my colleagues are suffering from same issue.


Windows 10 Enterprise, 2004, 19041.572",SamuelH
19993,USB MIDI on Windows 2000 SP4,VirtualBox 6.1.14,Linux,2020-10-22T18:20:52Z,2020-10-22T18:20:52Z,2020-10-22T18:20:52Z,"Hello All,

when I connect YAMAHA MIDI Keyboard to Windows 2000 host via USB the system crashes during the PnP phase. When it enters the:

""Found New Hardware - USB Audio Device"" the BSOD appears with:

STOP 0x0000001E ...
KMODE_EXCEPTION_NOT_HANDLED
Address BCEA7A90 base at BCEA3000, DateStamp 3803cad4 - usbaudio.sys
... etc.

I tried almost everything from switching to USB 1.0, changing the Sound Card to SoundBlaster etc.
The Host is Debian 10 (buster) the version of VirtualBox is 6.1.14.

I updated the VirtualBox Guest Add-ons to latest version. Turned off VT-x all leads to BSOD.

Thanks in advance",unun
19977,USB3 UASP SATA SSD support,VirtualBox 6.1.14,Windows,2020-10-17T17:43:27Z,2020-10-17T17:43:27Z,2020-10-17T17:43:27Z,"Hi,

I connected my Usb 3 Sata Ssd Mx500 to the host. I can see UASP is supported and enabled in CrystalDisk Info, in Windows 10. However, it is not in the guest (same OS). I have of course installed Virtualbox extension pack.

The difference in speed is high: with CrystalDiskMark, I have around 320MB/s in guest and 450MB/s in host.

Workaround:
Mount the drive in guest. The benchmark shows similar result that in host.

This is a good improvement I think, but no a priority.

Env: Windows 10 in host/guest
Virtualbox 6.1.14 with guest additions in guest + extension pack.",myroad
19951,Can't boot from bootable USB and install window on freshly created Windows VM,VirtualBox 6.1.14,Linux,2020-10-09T17:22:31Z,2020-10-09T17:22:31Z,2020-10-09T17:22:31Z,"1. I wasted an hour of my life downloading and creating an installable USB drive with Windows 10, using Microsoft's official tool.
2. In Virtual Box on a Linux host, I created a VM, chose Windows as the machine type, enabled the USB controller,
3. Then I plugged the physical Windows bootable USB drive into the host's physical USB port, and added that device to the VM
4. I powered on the VM and I was asked to choose whether to boot from a physical optical drive on the host, an ISO image simulating an optical drive, and I don't remember what other options, but there was no option to boot from the USB drive.

I should have that option. Now I have to start over and download a DVD ISO image and use that.",php4fan
19933,Issues due to lost USB packets (control and bulk type transfers),VirtualBox 6.1.14,Linux,2020-10-02T23:46:30Z,2020-10-02T23:48:14Z,2020-10-02T23:48:14Z,"Hi all,

I'm using the latest VirtualBox version under Kubuntu 18.04 LTS. I'm having errors when testing a software I've made in a VM running the same OS, but it makes no difference on other VMs running other Linux distributions. However, my software doesn't have issues when it is running on my native machine, no VMs involved. I even tested this on a different machine, and no issues whatsoever even after a few hours.

The history here is that this software controls a USB switcher, monitoring it continuously, ever 200ms (but that can be changed in the options). The USB switcher itself is based on the CP2130 from Silicon Labs. The software has all the kinks ironed, but it fails on a VirtualBox VM, which should not happen. This also happens, seemingly, irregardless of the version of VBox I have installed. I've recently updated to the latest version from the VirtualBox repository, but saw no differences. In fact, I've seen it fail catastrophically and even causing the device to reset (the software forces a reset if more than 10 errors occur) quite rapidly. More frequently, errors are due to lost control transfers, but can happen with bulk transfers as well.

To sort this out, I've decided to run traces with Wireshark, simultaneoulsy inside and outside the VM, monitoring the same connections essentially. I can conclude that there were some lost packets because I've seen errors reporting inside the VM pertaining to packets that simply were not matched to any packets caught outside the VM, which might mean that the request packet never went outside the VM to the USB host, and due to timeout, it generated a ENOENT response inside the VM, but not outside. I must add that responses that exceed 100ms are ruled out the the application.

I have the images proving the issue, the screenshots highlighting some of the packets and the traces taken inside and outside the VM.

Kind regards, Samuel Lourenço",bloguetronica
19946,interrupt transfers stop working,VirtualBox 6.1.10,Linux,2020-10-07T12:04:10Z,2020-10-12T06:01:20Z,2020-10-12T06:01:20Z,"After forwarding a SCM Microsystems, Inc. SCR331 SmartCard Reader USB device to the guest, it can at first be used normally. If it isn't used for a few seconds (no cards are inserted or removed, no interrupt responses are sent), interrupt handling stops working for the device. The reader can still be accessed (for example, if a card is inserted certutil can still read it), but further interrupts don't reach the guest (if no card was inserted, newly inserted cards are not noticed).

Running wireshark on both host and guest shows that on both host and guest an interrupt in request is sent out and after 5 seconds a response from the device is received. After that, the guest has no further traffic, but on the host, a SET FEATURE request is sent and a response received.

I have also seen this problem on an older modified virtualbox verion 5.1.38. I was unable to use wireshark in this configuration, but observed that in qemu-usb in file hcd-xhci.c, in function xhci_process_comands, in a switch on TBRType type, it falls into CR_STOP_ENDPOINT.",Cochimetl
19794,Windows 10 Blue Screen when USB device is disconectec runnning only VBox application,VirtualBox 6.1.10,all,2020-08-05T14:33:28Z,2020-08-05T15:21:34Z,2020-08-05T15:21:34Z,"Hi all,

The issue happens all the time, the only that you need is open virtualbox, is not necessary to run a guest virtual machine:

Open Virtual box
Disconnect a USB keyboard or Mouse (some times blue screen come here), if not,
Connect a USB keyboard or Mouse, here comes the blue screen.

If you open the VirtualBox application and close and disconnect and connect a USB Keyboard or mouse, the doesn't happens.

I'm ussing the VirtualBox 6.1.12-139181, I uninstall and install 6.1.0-135406 and the issue is there, also on 6.1.10-138449",Andres Marin
19775,Bluetooth device failed to pass through VM - MacOS,VirtualBox 6.1.10,Mac OS X,2020-07-28T16:22:43Z,2020-07-29T22:10:39Z,2020-07-29T22:10:39Z,"When I want to use my internal bluetooth in the VM, VBox reports that it failed to attach. However, in VBoxManage, it reports that the device is available. I have requested help in the [https://forums.virtualbox.org/viewtopic.php?f=8&t=99203 Forum], but the issue was not solved. Also, when attempting to connect the device, this error shows in the console (but not the logs):

{{{
014435.208921 VBoxSVC@(null): IOUSBUserClientLegacy::start: missing entitlement com.apple.bluetooth.control
}}}

Steps Taken:
1. Start VBox
2. Launch VM.
3. Try to connect to Bluetooth on the fly.

or 
1. Start VBox
2. Set USB filter.
3. Launch VM.
",JP3
19714,USB Port filter should use Linux USB bus id instead of a random number,VirtualBox 6.1.10,Linux,2020-07-10T22:18:01Z,2020-07-14T09:15:33Z,2020-07-14T09:15:33Z,"On Linux the ""port"" field in the ""USB Filter"" should ideally use the physical bus id instead of a random number.[[BR]]
In my use case I'd like to create an USB filter limited to a specific physical USB port. If the user e.g. puts some random USB memory stick into this specific physical USB port, it should show up in the VM. For that it would be necessary to have a USB filter which can refer to a unique ""port"", which the current implementation can not guarantee.[[BR]]
[[BR]]
E.g. currently I see this on my machine:[[BR]]
{{{
UUID:               9b7430c2-c602-49d8-84e9-ffbb3a22bce0
VendorId:           0x04d9 (04D9)
ProductId:          0x1133 (1133)
Revision:           2.16 (0216)
Port:               1
USB version/speed:  1/Low
Manufacturer:       Holtek Semiconductor, Inc.
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2//device:/dev/vboxusb/003/002
Current State:      Busy

UUID:               191cbe8f-442d-4f5e-9552-c0b0cd7bf119
VendorId:           0x046a (046A)
ProductId:          0x0023 (0023)
Revision:           0.50 (0050)
Port:               1
USB version/speed:  2/Low
Manufacturer:       Cherry GmbH
Product:            CyMotion Master Linux Keyboard G230
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-2//device:/dev/vboxusb/002/002
Current State:      Busy
}}}

As you can see in the example above, both USB ports have ""Port: 1"" and thus they are not uniquely identifyable. So it would be more useful to instead refer the ""Port"" field to ""3-2"" for the first entry, and to ""2-2"" in the second entry (see the ""Address"" field).
",Helge Deller
19219,Serial port access via USB dropping lots of data...,VirtualBox 6.1.0,Windows,2020-01-12T12:51:34Z,2020-01-15T04:44:08Z,2020-01-15T04:44:08Z,"Receiving data from a serial uart device seems to drop lots of data.

* Host: Windows 10 with VirtualBox 6.1 with extension pack
* Guest: Xubuntu 18.04 with guest additions
* FTDI serial USB module connected to USB port and passed through to Xubuntu
* FPGA connected to the FTDI module sending serial data at 115200 baud. The data is sent in 64-byte chunks, one chunk per second (it's a test project and that's just what I've selected for testing).

I'm finding that:

* Xubuntu on a real machine - works fine.
* Xubuntu in a VirtualBox VM - fails.

Under VirtualBox, I get maybe 16 bytes out of every 64 byte chunk and occasional data corruption (as in bytes that I know aren't being transmitted showing up).

The commands I'm using the dump the serial port are:

$ sudo ssty -F /dev/ttyACM1 115200 raw -echo
$ sudo xxd /dev/ttyACM1

Attached screen shot shows correct serial dump (under windows), on the right, the messed up data via VirtualBox.

VirtualBox Log also attached",toptensoftware
19187,"USB crashes VBox 6.0, 6.1",VirtualBox 6.1.0,Windows,2019-12-26T20:40:28Z,2020-01-13T12:15:06Z,2020-01-13T12:15:06Z,"When enabling USB filter for:
 Busch-Jaeger Elektro GmbH KNX-USB Interface (Flush mounted) [0101]
 vendor id 145c
 product id 1330
 revision 0101
on host W7 home premium sp1, guest W7 home premium sp1, with vbox 6.0, and latest 6.1. Vbox 6.1 at least sends application error message: ""the guest machine crashes with instruction at 0xdd0069fe referenced memory at 0x00000146. The memory could not be read."" whereas vbox 6.0 was simply aborting the guest machine without message.

It worked in Vbox 5.2.2 with same host, guest Windows XP.

",Yves P
18736,attach two similar usb device always fail,VirtualBox 6.0.8,Windows,2019-07-02T10:55:38Z,2019-07-05T12:10:22Z,2019-07-05T12:10:22Z,"Hi,
I want to attach two generic usb card reader, there is 3 problems :
- I can't differenciate which card in the menu (peripheral -> usb show me the same device twice)
- attaching the first device work, the second always fail
- once an attachement fail, the device will always be listed in peripheral -> usb, ejecting the device still show it, pluging the device again will create a new entry, trying to attach the device again will fail and so on...",JLM
18652,Reiner SCT CyberJack USB no longer works (reset full speed usb device ...),VirtualBox 6.0.8,Linux,2019-05-16T18:04:22Z,2019-05-31T07:57:06Z,2019-05-31T07:57:06Z,"Since Virtualbox 6.0.6 it appears that the Reiner SCT CyberJack Standard Chipcard reader (USB) can no longer be used from within a Windows VM.

Card reader is detected ok by Linux
[  611.544511] usb 1-7: new full-speed USB device number 5 using xhci_hcd
[  611.879182] usb 1-7: New USB device found, idVendor=0c4b, idProduct=0500, bcdDevice= 0.01
[  611.879185] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  611.879187] usb 1-7: Product: cyberJack RFID standard
[  611.879188] usb 1-7: Manufacturer: REINER SCT
[  611.879189] usb 1-7: SerialNumber: 5287xxxxxx

After launching a Windows 10 VM (USB device connected automatically to VM) countless messages of type
[  612.661394] usb 1-7: reset full-speed USB device number 5 using xhci_hcd

and the CyberJack driver within the VM cannot access the chipcard reader.

*Additional info*
Symptom: The reader does not seem to accept the card if plugged in",Jörg Skottke
18664,Reset of USB device causes failure to attach,VirtualBox 6.0.8,Linux,2019-05-21T11:28:08Z,2019-05-21T11:28:08Z,2019-05-21T11:28:08Z,"For some time now we have been able to test our USB3 machine vision cameras in a Windows VM but a recent change to VirtualBox has introduced a device reset during the attach process. 
The cameras we use are designed for continuous running in a factory and so the reset being issued is causing them to go through a full reset to ensure that they can be recovered in a fault case. This means that they are disconnecting from the host causing VirtualBox to lose track and fail to attach them to the guest. 
If I set a USB filter it gets stuck in a loop of constantly resetting the device and failing to attach it.

Is it possible to configure VirtualBox to disable the new device reset feature either globally or for a specific device?",Dan
18630,Using dd to write to SD Card in a USB SD Card device results in an error,VirtualBox 6.0.6,Mac OS X,2019-05-08T21:50:53Z,2019-05-09T00:54:35Z,2019-05-09T00:54:35Z,"NOTE: This may be a duplicate of ticket #17020. That issue appears to be the exact same problem and is not resolved.

On VirtualBox Version 6.0.6 r130049 (Qt5.6.3), using dd to write to SD Card using an external USB SD Card device has an error.

""dd: error writing '/dev/sde': No space left on device""

I am using a process I have previously used through VirtualBox and an external USB-A SD Card device to write to our stocked SD Cards. For simplicity, I used the same image that previously worked.

The host MacOS 10.14.4 has no issues with the exact same command.
NOTE: On host MacOS, may use ""brew install pv iozone""

Using ""iozone"", I established the max ""write"" speed at 7 MiB/s to our in stock, SanDisk Edge 16GB Micro SD HC 1 ""4"". We've been using these same SD Cards for years.


USB-C SD Card device on host MacOS completes correctly, at about 2.7MiB/s. I validated this SD Card on target hardware and it is correct.
{{{
bzcat 07626-38_sandisk-1.1.1-smc-2.8.0-with-ADCP.img.bz2 |  pv --size 15931539456 | sudo dd of=/dev/rdisk2 bs=512 conv=noerror,sync
[=================================================================================================================================================================>] 100%            
31116288+0 records in
31116288+0 records out
15931539456 bytes transferred in 5748.904531 secs (2771230 bytes/sec)
}}}


USB-C SD Card device on VirtualBox Ubuntu 16 error at this repeatable number of records out. Note the speed is too fast for this device.
{{{
bzcat myDisk.img.bz2 | pv --size 15931539456 | sudo dd of=/dev/sde bs=512 conv=noerror,sync
dd: error writing '/dev/sde': No space left on device===========================>                                                                                                                                                               ] 25% ETA 0:07:00
8131777+0 records in
8131776+0 records out
4163469312 bytes (4.2 GB, 3.9 GiB) copied, 142.747 s, 29.2 MB/s
3.88GiB 0:02:22 [27.8MiB/s] [=====================================================>                                                                                                                                                             ] 26%      
}}}



USB-A SD Card device on VirtualBox Ubuntu 16 also failed.
NOTE: This process and this exact USB-A SD Card device worked on some older version of VirtualBox, but unknown what that was because I did that about a year ago.
{{{
bzcat myDisk.img.bz2 | pv --size 15931539456 | sudo dd of=/dev/sdi bs=512 conv=noerror,sync
dd: error writing '/dev/sdi': Input/output error============================================================================================================================================>                                                   ] 76% ETA 0:20:48
23878697+0 records in
23878696+0 records out
12225892352 bytes (12 GB, 11 GiB) copied, 4279.2 s, 2.9 MB/s
11.4GiB 1:11:19 [2.72MiB/s] [===============================================================================================================================================================>                                                   ] 76%      
}}}


After powering off the VM and starting it again, using the USB-C SD Card device fails in a different way. Write speed is reasonable, but still has an error.
{{{
bzcat myDisk.img.bz2 | pv --size 15931539456 | sudo dd of=/dev/sde bs=512 conv=noerror,sync
dd: error writing '/dev/sde': No space left on device============================================================================================================================================================>                              ] 86% ETA 0:05:01
406158+80035 records in
486192+0 records out
15931539456 bytes (16 GB, 15 GiB) copied, 2192.37 s, 7.3 MB/s
12.9GiB 0:36:32 [6.03MiB/s] [======================================================================================================================================================================================>                            ] 87%   
}}}",Andrew Trapani
20635,The USB device disappears from the host but doesn't appear on the guest,VirtualBox 6.0.4,Windows,2021-10-25T10:41:25Z,2021-10-25T10:41:25Z,2021-10-25T10:41:25Z,,LAWGR
18417,USB thumb drive is persistent.  It does not disappear while removed,VirtualBox 6.0.4,Windows,2019-02-06T17:34:03Z,2019-02-06T17:34:03Z,2019-02-06T17:34:03Z,"SanDisk drive showed correctly in Devices, and was gone when I removed the drive.  That was then!  

Now, it does not disappear when removed, and in fact shows twice when I again install it.

Underlying Windows 10 device does come and go as expected.

Comment: is there a way to refresh devices (USB devices)?",Derick Moore
18413,All VM guests stuck (black screen) and can't be killed - after a USB filter is set,VirtualBox 6.0.4,Linux,2019-02-05T17:00:11Z,2019-02-05T17:00:11Z,2019-02-05T17:00:11Z,"HOST: Linux Mint 19.1/Cinnamon + VirtualBox 5.2.24 first, then 6.0.4
GUESTS: Windows 10 Home, Windows 7 Prof, both worked fine until

I SET a new USB FILTER for Win10 (I am in the vboxusers group)
and then I started Win10 : just a black screen appeared, nothing else.
I could nor stop it, neither kill it from a terminal. Then I even had my Linux host to force to stop with the power button, too.

TESTS
1. After a new Linux host start I started Vbox again (now without any modification) and then Win7 guest. Same result as above.

2. I deleted completely VirtualBox 5.2.24 with all its files, even the VM-s from my laptop, (they were exported not long ago to an external drive). Then I installed VirtualBox 6.0.4 and its Extension Pack, and imported my 2 Windows VMs. They both worked fine again. I installed the apropriate GuestAdditions in both. Still ok. I could work with them well. 
Then I added myself to the vboxusers, rebooted Linux and started VirtualBox again. I set a new USB filter for Win10 and started it. Black screen again which could not be killed, and Linux could not be stopped. 

3. After a new start I tested my Win7 guest as well, neither works it any more. Black screen, stuck, Lx can't be stopped.

I think some Vbox configuration goes bad... I use Vbox since many years, and I do not rememeber similar problem. In a formerly Vbox version I could set USB filters, however I do not remeber the version number unfortunately. Anyhow, I appreciate Vbox very much, it is an excellent work. 

",JBM
19296,No USB devices available to Win7/Win10 guests on Linux host [VBox 6.0.16],VirtualBox 6.0.16,Linux,2020-02-08T15:47:58Z,2020-12-10T17:45:16Z,2020-12-10T17:45:16Z,"Under VirtualBox 6.0.14-133895, right-clicking on the USB icon on the VBox window status displays a menu showing a list of the USB interfaces/devices available on the host. Each entry in the list has a checkbox which can be used to assign the USB device to the Guest OS.

However, after upgrading to Version 6.0.16-135674 of VirtualBox, right-clicking on the USB icon does not show the list of USB interfaces/devices - instead it shows a menu list with the only entry of ""USB Settings..."" and a greyed-out entry stating ""No USB Devices Connected""

Although I discovered this issue when running Windows 7 and Windows 10 guest VMs, the same issue also arose when running an Ubuntu 16.04.6 guest VM too.

I have attached the following files:
- a screenshot of a Win10 guest VM, showing the the USB device statuses when running under VBox 6.0.14-133895
- a screenshot of a Win10 guest VM, showing the the USB device statuses when running under VBox 6.0.16-135674
- a zipped copy of the VM log for the Win10 guest, runing under VBox 6.0.16-135674.

My host system is a Lenovo Thinkpad E590 laptop with Intel Core i5-8265U CPU & 8Gb RAM, running Ubuntu 16.04.6.

I originally raised this as an issue on the forum, at [https://forums.virtualbox.org/viewtopic.php?f=7&t=96663&p=469555#p469555]",thoikix
19143,usb busy with previous request,VirtualBox 6.0.14,other,2019-12-10T22:05:30Z,2019-12-14T22:49:29Z,2019-12-14T22:49:29Z,"i have installed the extension pack, i still get the issue, i could not find vboxusb.inf i found vboxusb.sy i could not find uppperfilters on my windows registry.",foreign
19054,No USB Device on Windows 7 guest,VirtualBox 6.0.14,Windows,2019-10-31T14:02:05Z,2019-10-31T16:15:06Z,2019-10-31T16:15:06Z,"Host Win10 (64bit)
Guest Win7 (64bit)

After upgrading to 6.0.14 there is no USB device shown anymore in USB List. ",cyberoner
18947,usb audio is extremely choppy,VirtualBox 6.0.12,Windows,2019-09-19T18:21:53Z,2019-09-24T06:09:08Z,2019-09-24T06:09:08Z,"Guest: OS/2

In principle, usb audio does work under OS/2 but the sound is extremely choppy. I am using a USB 1.x sound device (compatible with usb audio standard 1.0). With older versions of VirtualBox, this problem did not exist but the guest was more unstable (guest crashed).",lerdmann
18883,Issue with USB joystick SPEEDLINK COMPETITION PRO,VirtualBox 6.0.10,Windows,2019-08-30T10:29:38Z,2019-09-29T15:23:00Z,2019-09-29T15:23:00Z,"Issue when arcade joystick Speedlink Competition Pro is inserted: when VBox GUI is running ('''don't need to start a VM''') this device switches erroneously from
SPEEDLINK COMPETITION PRO (VID_0738&PID_2217)
into
Game Controller for Android (VID_0079&PID_181C).

The same issue was already fixed by SDL author blacklisting the device from HID enumeration, so I hope you can do the same to solve this problem forcing me to unplug the device every time:
https://hg.libsdl.org/SDL/rev/64d32e614d64 ",hexaae
18772,USB flash drive selection / addition causing crash or on removal,VirtualBox 6.0.10,Windows,2019-07-18T16:34:37Z,2019-07-18T16:34:37Z,2019-07-18T16:34:37Z,"Intermittent, but fails enough to be extremely troublesome.",xlar54
17799,USB Webcams are Not Working in Windows Guest (w. Extension Pack & Guest Additions),VirtualBox 5.2.8,Windows,2018-06-03T22:13:44Z,2018-06-21T05:24:35Z,2018-06-21T05:24:35Z,"I am trying to get my webcam, Microsoft LifeCam (USB), to work in a Windows 7 (64 bit) Guest on Windows 7 (64 bit) Host.


The camera works fine in the Host using two different applications:
1. Microsoft LifeCam software
2. Portable Webcam (http://sourceforge.net/p/portablewebcam)

I am currently using VirtualBox 5.2.8 w. Guest Edition and Extension Pack. I select the WebCam under devices (and not in USB devices). The camera is recognized in Device manager. However, the Camera is not working;
1. Microsoft LifeCam software: ""No Camera found""
2. Portable Webcam: Camera light turns on then off. I just get a white screen

I can use the camera in the Host, using either application, even when virtual box is running with the camera attached to the Guest (Should that work? I had expected the Guest to take ownership of the camera).

I also tried Logitech C270 Webcam and I have the same problem. 

Please help, I have spent several months on this using different guests and versions of VirtualBox.
Thank you in advance!

p.s. 
1. The cameras works fine in VMware virtual machines and Windows 7 Host/Guests.
2. I posted this previously in the forum but got no response (https://forums.virtualbox.org/viewtopic.php?f=6&t=87569)",ppan
17607,5.2.8 Has Issues Passing Though USB Devices Consistently,VirtualBox 5.2.8,Linux,2018-03-08T14:27:46Z,2018-03-08T14:27:46Z,2018-03-08T14:27:46Z,"I use USB passthrough often, and after updating to the newest version, the passthrough was working maybe 1 of 10 tries. Currently, I am trying to passthrough USB to Serial cables. Downgrading to 5.2.6 has solved these issues. ",SheepyBloke
17533,USB3.1 USB stick fails to enumerate,VirtualBox 5.2.6,Windows,2018-02-08T12:37:24Z,2019-01-29T15:19:48Z,2019-01-29T15:19:48Z,"Host: W10 LTSB (64bit)
Guest: Linux (64bit)
VB Version: 5.2.6 r120293 (Qt5.6.2)

I've recently purchased another one of these sticks (Verbatim Go V3 MAX). The old ones (read out as USB3.0) work just fine.

This one however shows up as USB3.1 (booting linux on physical machine). The stick works just fine on W10 / linux, as long as I don't use a VM.

Disabling USB3 in the VM ""helps"", but USB2 speeds are just 5MB/s.",robert spitzenpfeil
17602,"USB passthrough problem, when flashing embedded system using PSOC Creator.",VirtualBox 5.2.6,Linux,2018-03-07T10:07:56Z,2018-04-30T14:42:56Z,2018-04-30T14:42:56Z,"I have a problem with PSOC Creator. I'm using usb passthrough to pass cypress development board to Windows 10 on virtual machine. 

My host machine is Arch Linux. I've set up usb filter, and device is correctly recognized on guest machine, but when i try to program the board or connect debugger, PSOC Creator application hangs until i disconnect and reconnect usb cable. Then this error shows up: ""There was an error while programming the device: failed to reacquire the device.""

Trying several times, sometimes it works, sometimes it gets stuck and I need to reconnect device. But most of the time it doesn't work.

I have disabled auto suspend for this device.

If you need some extra information about the system please tell me, I will try to provide them.",morali
17508,USB Passthrough Keyboard sometimes does not detect keystrokes,VirtualBox 5.2.6,Windows,2018-01-29T09:14:54Z,2018-01-29T14:07:24Z,2018-01-29T14:07:24Z,"Hi there!

I use Virtualbox on Windows 10 and have a Ubuntu 16 VM. I attach a seperate USB keyboard and mouse to the host and pass them through to the VM. This is pretty nice because with additional screen where the VM is in fullscreen mode, its almost like having two fully operational computers.

Everything works fine with the rather old version 5.0.8 r103449 of VB. I noticed that with later versions it happens that sometimes keystrokes get lost / do not get detected in the VM, especially when typing fast. The latest version I tried and I can still reproduce that behavior is 5.2.6 r120293 (Qt5.6.2). I always have the guest utilities updated and installed but they seem to have no effect here.

I really would appreciate you guys looking into that issue and fixing it, it worked in the past so maybe it's an small and easy fix. Unfortunately it's what keeps me from updating to later VB version.

Thank you and best regards,
Nils",Nils Koenig
17471,"regression 5.2.2 -> 5.2.4, USB stopped work with TomTom Go",VirtualBox 5.2.4,Linux,2018-01-17T23:42:55Z,2018-06-20T23:01:34Z,2018-06-20T23:01:34Z,"Moving from 5.2.2 to 5.2.4 TomTom My Drive software is unable to connect to my TomTom.
TomTom Go software seems to see the TomTom device but it can't connect to it anymore.

Virtualbox was working fine with 5.2.2.

USB is configured as 2.0. Host is Debian running kernel 4.14.7, guest is Windows 7.

Still not working with 5.2.6.



thanks",IvanSB
18660,"The moment the USB is connected to the host OS, the guest OS being started takes away all USB control regardless of the USB setting",VirtualBox 5.2.30,Windows,2019-05-20T01:39:53Z,2019-05-23T09:01:44Z,2019-05-23T09:01:44Z,"The moment the USB is connected to the host OS, the guest OS being started takes away all USB control regardless of the USB setting",0o0o
18591,USBIP from/to NAS Sinology not working any more,VirtualBox 5.2.28,Linux,2019-04-21T17:22:35Z,2020-01-13T12:17:10Z,2020-01-13T12:17:10Z,"Hi,
I've using Oracle VirtualBox on Linux Mint 18.04 host for over a year, to run a Windows XP printing through USBIP on a 3D printer plugged onto a Synology 216j with VirtualHere USBIP server.

Everything worked fine until Version 5.2.26 r128414 (Qt5.6.1).

After upgrading to 5.2.28, my XP could still see USBIP ports but the Up! 3D application under XP could not see the printer as connected.

After upgrading to virtualbox 6.0, the VM could not see the USBIP port.

Coming back to 5.2.26 make it work again.

Best regards,
Jean-Marc",Jean-Marc au Boulot
18176,USB resets and hangs during high I/O,VirtualBox 5.2.22,Mac OS X,2018-12-10T22:06:28Z,2022-12-03T15:52:56Z,2022-12-03T15:52:56Z,"Experiencing USB reset and hangs on Virtualbox 5.2.22 on Macbook Pro 2017 10.13.6, on Oracle Linux 7.5 and Ubuntu 18.04 VMs.  I'm able to replicate the problem, very quickly, by running the following:
{{{
$ sudo dd if=/dev/zero of=./testfile status=progress bs=1024k
639631360 bytes (640 MB) copied, 5.448752 s, 117 MB/s
}}}
It starts out pretty fast, but once the reset occurs, the speeds taper down to < 50MB/s.  The OL system log shows the resets and I/O errors as:
{{{
Dec 10 15:55:28 jdnissen-lobi7 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
Dec 10 15:55:38 jdnissen-lobi7 kernel: usb 2-1: reset SuperSpeed USB device number 2 using xhci_hcd
Dec 10 15:55:44 jdnissen-lobi7 systemd: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 1858 (cma)
Dec 10 15:55:44 jdnissen-lobi7 systemd: Mounting Arbitrary Executable File Formats File System...
Dec 10 15:55:45 jdnissen-lobi7 systemd: Mounted Arbitrary Executable File Formats File System.
Dec 10 15:55:46 jdnissen-lobi7 kernel: EXT4-fs (dm-3): Delayed block allocation failed for inode 12 at logical offset 546816 with max blocks 2048 with error 5
Dec 10 15:55:46 jdnissen-lobi7 kernel: EXT4-fs (dm-3): This should not happen!! Data will be lost
Dec 10 15:55:46 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:55:51 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:55:57 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:01 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:07 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:12 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:17 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:22 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:27 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
Dec 10 15:56:32 jdnissen-lobi7 kernel: JBD2: Detected IO errors while flushing file data on dm-3-8
}}}
I've attempted to workaround this with the new test build 6.0.0 RC1, and it didn't help.  OL and Ubuntu updates don't help, either.

It's happening on two different USB drives:  Seagate 2TB and Western Digital 2TB.  The seagate is formatted as NTFS and the WD is Linux EXT4.  

In addition, I can attach the drives to an old laptop running bare-metal OL7.2, and it works just fine...no resets, hangs, or slow I/Os, during the 'dd' (or file copies).

I work for Oracle, and this problem is preventing me from being able to copy large patch bundles, used during customer installs.


",Jimson
18162,Linux guest cannot perform large USB requests,VirtualBox 5.2.22,Mac OS X,2018-12-01T19:30:17Z,2018-12-01T19:30:17Z,2018-12-01T19:30:17Z,"I have a Starlight Express Trius SX-56 astrophotography camera. This camera performs image transfers as single USB bulk transfers. Due to the large sensor size, these transfers are 32MB in size. While this is larger than the default memory size for usbfs in the kernel (16MB), by writing a larger number to /sys/module/usbcore/parameters/usbfs_memory_mb, this limit can easily be extended. However, that does not make the camera work in a VirtualBox virtual machine. It turns out that the 32MB request formulated in the guest arrives as a 5MB request in the host (tested on MacOS mojave, USB packets inspected with Wireshark on MacOS host and Linux guest). The camera cannot handle this short request and locks up.",Andreas Müller
18144,VBoxManage list usbhost fails to correctly identify USB Reader,VirtualBox 5.2.22,Linux,2018-11-22T08:38:36Z,2018-11-30T00:34:21Z,2018-11-30T00:34:21Z,"Here is the output of various commands that might be useful. My report and comments are disclosed below.

{{{
$ uname -a
Linux wangwq-mint 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux
}}}


{{{
$ sudo lsusb -vv -d 0000:a180
[sudo] wangwq 的密码：

Bus 001 Device 008: ID 0000:a180  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0000 
  idProduct          0xa180 
  bcdDevice            1.00
  iManufacturer           1 NARI
  iProduct                2 Sgchip Smart Card Reader
  iSerial                 0 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          338
    bNumInterfaces          4
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              200mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              3 Sgchip Dual Reader ICC 
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       4800
        dwMaxiumumClock      8000
        bNumClockSupported      0
        dwDataRate          10752 bps
        dwMaxDataRate      412903 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             254
        dwSyncProtocols  00000007  2-wire 3-wire I2C
        dwMechanical     00000000 
        dwFeatures       000207B2
          Auto configuration based on ATR
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          CCID can set ICC in clock stop mode
          NAD value other than 0x00 accepted
          Auto IFSD exchange
          Short APDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              4 Sgchip Dual Reader PICC
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V 
        dwProtocols             2  T=1
        dwDefaultClock       4000
        dwMaxiumumClock      4000
        bNumClockSupported      0
        dwDataRate          10752 bps
        dwMaxDataRate      250000 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             256
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       00020040
          Auto parameter negotation made by CCID
          Short APDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse      00
        bClassEnvelope         00
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              5 Sgchip Dual Reader SAM 
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         2  3.0V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       3580
        dwMaxiumumClock     14320
        bNumClockSupported      0
        dwDataRate           9600 bps
        dwMaxDataRate     2703401 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             252
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       000100BA
          Auto configuration based on ATR
          Auto voltage selection
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               2
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0 
      bInterfaceProtocol      0 
      iInterface              6 Sgchip Dual Reader SAM2
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.10  (Warning: Only accurate for version 1.0)
        nMaxSlotIndex           0
        bVoltageSupport         2  3.0V 
        dwProtocols             3  T=0 T=1
        dwDefaultClock       3580
        dwMaxiumumClock     14320
        bNumClockSupported      0
        dwDataRate           9600 bps
        dwMaxDataRate     2703401 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             252
        dwSyncProtocols  00000000 
        dwMechanical     00000000 
        dwFeatures       000100BA
          Auto configuration based on ATR
          Auto voltage selection
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse    echo
        bClassEnvelope       echo
        wlcdLayout           none
        bPINSupport             0 
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x07  EP 7 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
}}}


{{{
$ sudo VBoxManage list -l usbhost
Host USB Devices:

UUID:               4a8de244-7a20-4628-b37b-ccf8dc8d5eb3
VendorId:           0x147e (147E)
ProductId:          0x1002 (1002)
Revision:           0.72 (0072)
Port:               2
USB version/speed:  1/Full
Manufacturer:       UPEK
Product:            TouchStrip Fingerprint Sensor      
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3//device:/dev/vboxusb/001/004
Current State:      Captured

UUID:               2d39f89a-f8da-491e-8fdd-83194944aaf9
VendorId:           0x093a (093A)
ProductId:          0x2510 (2510)
Revision:           1.0 (0100)
Port:               1
USB version/speed:  1/Low
Manufacturer:       PixArt
Product:            USB Optical Mouse
Address:            sysfs:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-2//device:/dev/vboxusb/003/002
Current State:      Busy

UUID:               38696f50-c6ad-4b9c-8953-48d5beda95bd
VendorId:           0x04f2 (04F2)
ProductId:          0xb2ea (B2EA)
Revision:           5.24 (0524)
Port:               5
USB version/speed:  2/High
Manufacturer:       Chicony Electronics Co., Ltd.
Product:            Integrated Camera
Address:            sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6//device:/dev/vboxusb/001/006
Current State:      Busy

}}}


{{{
$ dmesg
...
[13121.127104] usb 1-1.2: new full-speed USB device number 8 using ehci-pci
[13121.243283] usb 1-1.2: New USB device found, idVendor=0000, idProduct=a180
[13121.243287] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[13121.243290] usb 1-1.2: Product: Sgchip Smart Card Reader
[13121.243292] usb 1-1.2: Manufacturer: NARI

}}}


I have properly working Virtualbox and full list of USB devices available inside Windows guest OS. The problem I face is that a specific USB serial device 0000:a180 is not properly exposed by ""VBoxManage list -l usbhost"" and respectively not properly passed-through to Windows guest. All other devices are properly passed-through.

",XiaoQ
18059,Upgrade to 5.2.20 breaks usb passthrough,VirtualBox 5.2.20,Windows,2018-10-18T09:21:20Z,2018-11-05T15:10:52Z,2018-11-05T15:10:52Z,"Host : Windows 10 Enterprise 1607

Upgraded Virtualbox to 5.2.20 from 5.2.18 with extension pack and USB passthrough does not detect any connected devices. Downgrading Extension pack to 5.2.18 does not resolve the issue, downgrading Virtualbox to 5.2.18 solves it.

I can upgrade again to collect any logs you want to help you solving this bug

Regards",3mptyy
18015,A forwarded Dectel CI692 doesn't work if the controller is USB 2.0,VirtualBox 5.2.18,all,2018-09-27T14:30:26Z,2018-09-27T14:30:26Z,2018-09-27T14:30:26Z,"When I use USB forwarding and a virtual USB 2.0 controller to attach a Dectel CI692 smart card reader to a CentOS 7.5 guest, attempts to use the smart card fail, with an error that traces back to ""libusb_error_timeout"" from PC/SC on the guest. The problem seems specific to this narrow configuration. Here's what I've discovered by testing various combinations of things:

* The problem occurs on both a 2017 MacBook Pro running High Sierra and a Dell OptiPlex 7050 running CentOS 7.5 as the hosts.
* The problem occurs whether the real USB port on the host is USB 2.0 or USB 3.0.
* The problem doesn't occur if I use a virtual USB 1.1 controller or a virtual USB 3.0 controller. For now, this is my workaround.
* The problem only occurs with certain smart card readers. When I tried it with an HID Omnikey smart card reader instead, it worked fine.
* The problem doesn't occur if I use the reader in a real USB 2.0 port with CentOS 7.5 on bare metal.
* The problem doesn't occur if I just run ""pcsc_scan""; it sees the smart card fine. The problem only occurs when I try to use the keys on it, such as by running ""ssh-keygen -D /usr/lib64/pkcs11/libcoolkeypk11.so"".

Steps to reproduce:

* Install CentOS 7.5 in a guest
* Set the guest to use a USB 2.0 controller, and forward the Dectel CI692 to it
* Insert a smart card into the Dectel CI692
* Install the packages ""epel-release"", ""pcsc-tools"", and ""coolkey"" in the guest
* Run ""ssh-keygen -D /usr/lib64/pkcs11/libcoolkeypk11.so"" in the guest

Expected result: the public keys from the smart card should be printed.
Actual result: the command fails with the message ""cannot read public key from pkcs11"".

Attached are two logs: one with a USB 1.1 controller, where the command works correctly, and one with a USB 2.0 controller, where the problem occurs. Both logs were saved immediately after running the ssh-keygen command.",jsible
17907,"Mouse pointer icon frozen, mouse clicks working when USB2 enabled in Win10 VM",VirtualBox 5.2.16,Windows,2018-08-01T19:59:31Z,2018-08-01T23:00:57Z,2018-08-01T23:00:57Z,"1. hp Zbook STudio G3 laptop, 16GB RAM, I7-6700HQ CPU @2.6GHz
2. Windows 10 Enterprise, 64-bit OS, x64-based processor
3. Logitech wireless mouse and keyboard, M510.
3. VirtualBox-5.2.16-123759-Win.exe
4. Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack

Problem Description:

Installed VirtualBox-5.2.16-123759-Win.exe.  
Downloaded Windows 10 trial to create a Windows 10 VM with.
Used without issue for several days.  Mouse and keyboard working fine.

Installed VirtualBox guest additions.  
Settings->UserInterface->Devices checked Insert Guest Additions CD Image.
Started VM.
Ran the installer, VBoxWindowsAdditions-amd64. rebooted.
Mouse and keyboard still working fine.

Needed access to usb2 devices.
shutdown vm.
USB2 & 3 could not be enabled. Instructions said to install extension pack.
downloaded Oracle_VM_VirtualBox_Extension_Pack-5.2.16.vbox-extpack and installed.
Enabled USB2:  Settings->USB.  Added USB devices, Intel Corp. [0001], Logitech USB Receiver [1203] 
Usb2 & usb3 could now be enabled in Settings.
start vm.

As soon as Windows initial screen appears, mouse pointer icon appears frozen.
The wait cursor (round circle) is showing and changing.
moving the mouse makes the mouse cursor blink but the actual cursor does not change position.
as you physically move the mouse, You can see different areas of the windows screen responding as 
an ""invisible"" mouse cursor passes over them.
clicking the mouse brings up the mouse dialog menus. 
The host computer has no mouse capability.
If I don't login and enter windows, and I stay on the login screen, I can use the tab key to move over and select 
shutdown.
As soon as the VM shuts down, I have control over the mouse again.

While VM is shutdown, I can go back to settings, delete the USB devices I added for USB 2.
when vm is restarted, I can move mouse.

I also tried a wired HP usb mouse.  Same behavior.

I tried going to logitech site for updates for mouse driver.  Did not find anything.
Since the HP wired mouse has the exact same behavior, I don't think it is Logitech related.",inxe
17806,Error 0x80070057 usb,VirtualBox 5.2.12,Windows,2018-06-06T14:36:57Z,2018-06-11T16:30:57Z,2018-06-11T16:30:57Z,"Hola, cree una maquina virtual w10, el SO donde esta instalado virtualbox es w7. y no logro utilizar un pendrive, probé varios.",woltsp
17723,VirtualBox cannot catch USB devices if RemoteFX USB Redirection enabled,VirtualBox 5.2.10,Windows,2018-05-01T19:59:38Z,2018-05-10T19:19:25Z,2018-05-10T19:19:25Z,"Host: Windows 7 SP1 Pro 64 bit. VirtualBox Version 5.2.10 r122406
Guest: Mageia Linux 6 with kernel 4.14.30
The guest additions have been installed 

I had to enable RemoteFX USB Redirection on my Windows 7 Laptop using Group Policy Editor (Enabled for Administrator and User). This feature is necessary in order to redirect ""other"" devices like Dongles etc. to a remote computer using Microsoft RDP protocol version 8.0.
But if this feature is enabled VirtualBox is not able to catch any USB device, neither a simple mass storage device like an USB stick nor a camera...
The first try to connect doesn't show anything, the second try results in an error ""USB device is busy with a previous request""

I tested this on Windows 7 SP1 Pro 64 bit host with a Mageia Linux 6 Guest and with a Knoppix Live ISO (Guest).
When disabling RemoteFX USB Redirection on the host again, everything works as expected.

How to reproduce:
1. Open Group Policy Editor (gpedit.msc) from the command line and 
2. navigate to: Computer Configuration \ Administrative Templates \ Windows Components \ Remote Desktop Services \ Remote Desktop  Connection Client \  RemoteFX USB Device Redirection \ Allow RDP redirection of other supported RemoteFX USB devices from this computer
3. Set to Enabled and the rights to Administrator and User
4. Run gpupdate /force from an elevated command prompt or better do a reboot of the host as advised within the description
5. Connect a simple USB Stick to Windows host
6. Start a virtual machine within VirtualBox and try to catch this USB stick within the Guest
7. The USB device will not be connected. A second try will result in the error: ""USB device is busy with a previous request""

Related tickets: There may be some parallels to Ticket #13513 but the setting is little bit different. Host is a native computer (not a guest somewhere) and Windows 7 itself is not connected via RDP.

Expected behaviour: The setting of ""RemoteFX USB Redirection"" should not have any impact on the USB driver used within VirtualBox

--> maybe it would be helpful to ad this setting to ""USB basics and troubleshooting"" within the VirtualBox forum as it took me hours to narrow this bug down
",spuch
16173,USB3 Passthrough Fails w/ VLI USB3 Controller,VirtualBox 5.1.8,Windows,2016-11-09T13:38:39Z,2016-11-09T13:38:39Z,2016-11-09T13:38:39Z,"I've been unable to get USB 3.0 or 2.0 devices to attach to VMs on a machine I've added a VLI-based PCIe USB 3.0 card to. It shows up as ""captured"" in the devices menu, but never appears in the VM. The device is also not replaced with the passthrough driver on the host. I've reason to believe this is related to the VLI chipset the card uses as USB 2.0 devices attached to the Intel chipset's USB 2.0 controller work just fine. The same VMs are able to have devices passed through to them properly on a machine that uses Intel's USB 3.0 controller. I've tested this with an external USB 3.0 hard drive (ASMedia controller) and two flash drives. (Sandisk Ultra and a Silicon Power.)",Ziginox
16094,Blue Screen of computer when plugging in USB drive,VirtualBox 5.1.8,Windows,2016-10-20T15:34:04Z,2016-10-20T15:34:04Z,2016-10-20T15:34:04Z,"If I have any virtual box related program running, whether it is the manager or VM if I plug in a certain USB drive it will blue screen the machine.  The usb drive is an Apricorn Aegis Secure Key: [https://www.cdw.com/shop/products/Apricorn-Aegis-Secure-Key-16-GB-USB-2.0/2544731.aspx?cm_cat=GoogleBase&cm_ite=2544731&cm_pla=NA-NA-APR_DR&cm_ven=acquirgy&ef_id=VoqpAAAAAM2hNEIN:20161020153038:s&gclid=CjwKEAjw1qHABRDU9qaXs4rtiS0SJADNzJiskwfgwH9FOtljO4nsvRtWsa6-g1FSC16RwESXdPa8DhoCVqvw_wcB&s_kwcid=AL!4223!3!61836302419!!!g!18283950120!].  I can get around it by not using the drive when I am using the VM, but if I accidently forget for any reason, it will immediately blue screen my computer as soon as it is plugged in.",jammer2000b
16032,VirtualBox not compatible with USBPcap and similar,VirtualBox 5.1.6,Windows,2016-10-05T12:38:38Z,2019-09-12T00:10:55Z,2019-09-12T00:10:55Z,"Hello,

* Issue:

current versions of VirtualBox are not compatible with USBPcap on Windows (e.g. Windows 8.1 or Windows 10).

* Description

USBPcap provides USB traffic recording functionality by injecting itself into the USB stack (see http://desowin.org/usbpcap/block_diagram.html) in a way currently incompatible with the way VirtualBox does something similar.

* Experienced behavior

Host USB device is unavailable (""busy"") for attachment to Virtual Machine with USBPcap installed and active. USBPcap can be installed as (optional but default) component of WireShark.

* Expected behavior

VirtualBox forwards the USB device in a defined manner, i.e. either with all USB traffic happening inside the VM visible to USBPcap, or with all USB traffic inside the VM circumventing USBPcap

* Why shouldn't this be fixed by USBPcap?

There are multiple software packages providing similar or identical USB sniffing capability in a similar or near identical functionality, addressing this in all of them with special code instead of handling this properly at the virtualization layer (already deeply involving itself with the system) seems odd.",berlincount
15927,USB Wifi Dongle drops connection after short period,VirtualBox 5.1.6,Mac OS X,2016-09-13T23:52:22Z,2017-12-12T19:08:52Z,2017-12-12T19:08:52Z,"Trying to use a [https://www.thinkpenguin.com/gnu-linux/penguin-wireless-n-usb-adapter-gnu-linux-tpe-n150usb Think Penguin TPE-N150USB] USB WIFI adapter in close proximity to my router.

The guest VM will recognize and use the adapter just fine. I can usually connect to my wifi, but the connection drops after 5-10 seconds (usually as soon as I try to access any over it). Subsequent attempts to connect to any WIFI connection will fail. Result is the same for any network I try to connect to, and on several different linux's, though primarily with fully up-to-date Ubuntu 16.04 ( Kernel 4.4 and 4.6 for grins and giggles). USB 2 and USB 3 both yield the same result.

I have ruled out a problem dongle since if I boot natively into the same version of linux, the wifi connection works flawlessly. 

My  problem seems unrelated to [https://www.virtualbox.org/ticket/9511 Ticket #9511] since my drivers load properly. 

Not sure if its helpful, but I have a [https://forums.virtualbox.org/viewtopic.php?f=8&t=79442 Forum Post here] with more info. Forum Moderator says he doesn't experience a similar issue with Linux Host, so perhaps the problem is specific only to Mac hardware?

(VirtualBox version 5.1.6 w/ latest Extension Pack and Guest Additions)

Please let me know if there is any further information I can provide, or any troubleshooting I should attempt. 

",Briantb
16076,Ubuntu 16.04.1 VM slow after copying data to external USB drive (irq 20: nobody cared),VirtualBox 5.1.6,Mac OS X,2016-10-17T20:49:27Z,2017-05-23T09:32:29Z,2017-05-23T09:32:29Z,"When I copy a lot of data to an external Western Digital passport drive (USB3) either using rsync or just drag and drop in a Ubuntu 16.04.1 Desktop VM now and then the desktop slows down to a crawl and stays like this even if I cancel the rsync. The dataset is a lot of 30-40MB files (rsync), or ~8 of 4-5G files (drag and drop). It does not always occur, but when I check dmesg -w I do see ""irq 20: nobody cared"" followed by a call trace. Reboot of the VM fixes this, until it happens again.",John Bokma
16022,"""VBoxManage list usbhost"" misidentifies ""USB version/speed""",VirtualBox 5.1.6,Mac OS X,2016-10-03T18:29:37Z,2016-10-03T18:29:37Z,2016-10-03T18:29:37Z,"The output in the ""VBoxManage list usbhost"" has one line for ""USB version/speed"". This comes up always as ""'''0'''/Low"", ""'''0'''/High"", ""'''0'''/Full"" or ""'''0'''/Super"". On other hosts the information with the same devices comes up correctly. Sometimes the __same device__ will be identified as ""'''0/Low'''"" on an OSX host and ""'''1/Full'''"" on a Windows host.

For background on this, please see: https://forums.virtualbox.org/viewtopic.php?f=1&t=80008",Socratis
15936,5.1.6 segfault in VBoxDD.so on USB unplug,VirtualBox 5.1.6,Linux,2016-09-15T15:51:39Z,2016-09-22T17:40:27Z,2016-09-22T17:40:27Z,"Hi,
the VM window just disappears.
It does not happen every time. As matter of fact I was working several days now with many USB unplug events. This time I captured logs.

{{{
04:11:12.098613 VUSB: Detached '00007fe874d5be50[proxy 0c2e:096a]' from port 1
04:11:12.098710 AssertLogRel /home/vbox/vbox-5.1.6/src/VBox/VMM/VMMR3/TM.cpp(1727) int TMR3TimerDestroy(PTMTIMER): <NULL>
}}}

and syslog

{{{
Sep 15 17:14:41 don kernel: [27511.485796] USBDevIo--1[19180]: segfault at e8 ip 00007fe89133910a sp 00007fe85557ae90 error 4
Sep 15 17:14:41 don kernel: [27511.485802] EhciFramer[14246]: segfault at f0 ip 00007fe891335ca0 sp 00007fe85600eb50 error 4 in VBoxDD.so[7fe89127a000+28e000]
Sep 15 17:14:41 don kernel: [27511.485808]  in VBoxDD.so[7fe89127a000+28e000]
}}}

 I can also share the Ubuntu crash report with the devs; but do not want to see it in the public. I this also 9MB.

And I can provide the USB device if that makes a difference (I live close to Endersbach).

Here is the link to the forum post:
[https://forums.virtualbox.org/viewtopic.php?f=7&t=79708&p=372643#p372643]
(there is also wrote about another crash, but I think the two are unrelated).

",ucrasher2
15851,"Can't use an USB device in Windows 10 guest: ""is in use by someone else""",VirtualBox 5.1.4,Mac OS X,2016-08-23T17:50:11Z,2017-03-18T18:45:01Z,2017-03-18T18:45:01Z,"I'm running Windows 10 guest on OS X El Capitan host.

I can't ever pass USB smart cart reader to the guest using the status bar icon because of the following error:

{{{
Failed to attach the USB device SCM Microsystems Inc. SCR3310 v2.0 USB SC Reader [0204] to the virtual machine Boot Camp.

USB device 'SCM Microsystems Inc. SCR3310 v2.0 USB SC Reader' with UUID {34262c72-da4e-4d08-99ff-ca2bee575214} is in use by someone else.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: HostUSBDeviceWrap
Interface: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Callee: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

The USB device in question is not really in use other than being plugged in.

Things I tried so far:
1. Create and use an USB filter
2. Switch between USB 2 and USB 3 in VM settings.

This is a critical issue for me, because I need to use VPN for work and I can't use the host VPN either because of VM crash in NAT mode (a separate issue).",DKroot
15901,Copyig files over USB hangs with USB 3 support,VirtualBox 5.1.4,Windows,2016-09-08T05:40:42Z,2016-10-28T13:16:58Z,2016-10-28T13:16:58Z,"Windows 7 host. 

I copied files from my Kubuntu 16.04.1 to an external tablet via adb push. 

The file I copied is roughly 600 MB. The file takes about 3 minutes to copy from Windows, in VirtualBox Linux Guest the file is still stuck copying after 12 hours. 

I started experiencing this problem since USB 3 support was introduced with VirtualBox 5.0. I do not have this problem with USB 2 enabled. 

My USB port is the following:
Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller

I had the problem driver version 1.0.4.225 then upgraded to 1.0.10.255, but had the same problem. 

The external device I am copying to is a Texas Instrument Blaze Tablet. 
",nopaste
17177,Loss of usb device after live snapshot or snapshot restore,VirtualBox 5.1.30,Linux,2017-10-18T09:32:09Z,2017-10-24T15:20:39Z,2017-10-24T15:20:39Z,"{{{
Host OS: Solus 3 (linux)
Guest OS: Solus 3
Solus kernel: 4.13.5-24.current
VirtualBox Build: 5.1.30r118389
Extension pack installed
USB 2.0 selected
}}}

* USB gamepad shared with the guest.
* Cold boot.
* Play a game using gamepad (e.g. supertux 2)
* Take a live snapshot.
* Gamepad no longer working.
* Restore snapshot.
* Gamepad not working.
* Reboot = gamepad working again.

",romulous75
17126,keyboard mouse not functional on host after dock(or unplug/plug mouse/kb),VirtualBox 5.1.28,Mac OS X,2017-09-30T06:08:18Z,2017-09-30T17:24:00Z,2017-09-30T17:24:00Z,"Steps to reproduce:

1. Host has usb mouse plugged in.
2. Run VBox. Start VM.
3. Notice mouse still works on host.
4. Unplug, replug mouse
5. Notice Mouse is now not functional on host.
6. Notice Mouse is now grabbed by Virtualbox and passed to VM, though no filter exists.
Note mouse/keyboard grabbed with no filter or even when filter is created and disabled.

Expected behavior:
5. Mouse not grabbed by Vbox unless filter is created and enabled.

This is greatly undesirable for docking scenarios.  If vitualbox is running and laptop is undocked/docked.  Mouse/keyboard are not functional.  Only apparent workaround is open up laptop use touchpad to manually disable grabbed mouse/keyboard or save and re-run VM.

Reproduces on 5.1.28, 5.1.29 r118065, and previous versions.",donemo
17020,dd on USB drive results in Input/output error,VirtualBox 5.1.26,Windows,2017-08-17T22:04:47Z,2017-12-12T10:11:41Z,2017-12-12T10:11:41Z,"Since version 5.1.22 and probably earlier I cannot write images to my USB SD card adapter anymore. Especially when writing larger images such as 4 GB of Raspbian I see the following error after some minutes:

{{{
debianguest:~$ time sudo dd if=/dev/loop0p2 |pv -s 4300M |sudo dd of=/dev/sdc2
dd: writing to '/dev/sdc2': Input/output error                ] 34% ETA 0:17:38
3068849+0 records in
3068848+0 records out
1571250176 bytes (1.6 GB, 1.5 GiB) copied, 567.657 s, 2.8 MB/s
1.46GiB 0:09:27 [2.64MiB/s] [==========>                      ] 34%            

real    9m27.844s
user    0m5.073s
sys     0m43.153s
}}}

Something with the USB driver seems to be broken on Windows 10 hosts. It used to work correctly with earlier versions.

This is an update of bug #17019 with corrected fields.
",Frank Breitling
18393,USB3 drive not recognized when connected to USB3 port,VirtualBox 5.1.24,Windows,2019-01-30T18:09:24Z,2019-01-30T18:12:30Z,2019-01-30T18:12:30Z,"I have a Windows7 host w/ Debian8 guest on VirtualBox 5.2.8.  WD Elements 2TB disk (https://smile.amazon.com/gp/product/B00D0L5BH8/) and Thinkpad E560 laptop (https://smile.amazon.com/Lenovo-ThinkPad-20EV002JUS-15-6-Inch-Processor/)

The disk connected into any usb3 port on the laptop.  It is recognized and works fine under the Windows host.  Once I connect the disk to the virtualbox guest, windows correctly stops seeing it and the guest shows:

{{{
[ 1786.262759] usb 1-2: new high-speed USB device number 7 using xhci_hcd
[ 1786.486278] usb 1-2: device descriptor read/64, error 18
[ 1786.775519] usb 1-2: device descriptor read/64, error 18
[ 1787.063049] usb 1-2: new high-speed USB device number 8 using xhci_hcd
[ 1787.247705] usb 1-2: device descriptor read/64, error 18
[ 1787.535498] usb 1-2: device descriptor read/64, error 18
[ 1787.818462] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[ 1787.835491] usb 1-2: Invalid ep0 maxpacket: 9
[ 1788.018588] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[ 1788.035487] usb 1-2: Invalid ep0 maxpacket: 9
[ 1788.036814] usb usb1-port2: unable to enumerate USB device
}}}

''virtualbox list usbhost'' when the device '''is not''' connected to the virtualbox guest:
{{{
UUID:               91f87b8b-5c6c-4318-b582-48e82af85f67
VendorId:           0x1058 (1058)
ProductId:          0x25a2 (25A2)
Revision:           16.33 (1633)
Port:               15
USB version/speed:  3/Super
Manufacturer:       Western Digital
Product:            Elements 25A2
SerialNumber:       575853314539373957304D4D
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0008
Current State:      Busy
}}}

.. and ''virtualbox list usbhost'' when the device '''is''' connected to the virtualbox guest:
{{{
UUID:               d4973955-0c60-418e-bd19-29d060869977
VendorId:           0x1058 (1058)
ProductId:          0x25a2 (25A2)
Revision:           16.33 (1633)
Port:               15
USB version/speed:  3/High
Manufacturer:       Western Digital
Product:            Elements 25A2
SerialNumber:       575853314539373957304D4D
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0009
Current State:      Unavailable
}}}

the device does not show up in /dev/sd* at all and ''lsusb'' does not show the device

the guest is configured for USB3 in virtualbox settings and the guest does have the usb3 drivers loaded.

when I use a USB2 extension cable between the disk and the laptop, the device works in the virtualbox guest.


see for discussion: https://forums.virtualbox.org/viewtopic.php?f=6&t=82474",jkister
17387,USB Dongle not recognized correctly,VirtualBox 5.1.22,Windows,2017-12-21T13:56:46Z,2017-12-21T13:56:46Z,2017-12-21T13:56:46Z,"Host: Windows 10 Pro x64
Client: Ubuntu 16 LTS
VirtualBox: 5.1.22r115126 with ExtensionPack

Synopsis:
An USB-Dongle (Dinkey Pro Lite Mini) is plugged in and gets not recognized correctly from the VirtualBox.
I have to disable/enable this ""Human Interface Dongle / USB Input Device"" from the device manager (or replug it) once after starting the VB. This is an issue only with the Windows 10 OS.
The same setup (dongle, VB) on Windows 7 is working perfectly.

Attacments:
logs.zip: Logs from Machine => Show Log...
usbhost1.log: usb host list after virtual box start
usbhost2.log: usb host list disable/enable the specified USB Input Device
01.jpg: Screenshot after virtual box start
02.jpg: Screenshot disable/enable the specified USB Input Device

The correctly attached device name is ""OEM HID Dongle [0106]"". If the Dongle is recognized correctly as OEM HID Dongle the serial number is attached correctly.
",igm
17370,Unknown USB device detected,VirtualBox 5.1.22,Windows,2017-12-14T10:57:05Z,2017-12-14T21:27:57Z,2017-12-14T21:27:57Z,"00:00:00.054173 USB: Unknown USB device detected (idVendor: 0x096e, idProduct: 0x0007). Please, report the idVendor and idProduct to virtualbox.org.

It's enough for ""report""?",igm
16880,USBPROXY Getting USB descriptor failed with error 31,VirtualBox 5.1.22,Windows,2017-07-06T16:30:28Z,2017-11-06T04:07:05Z,2017-11-06T04:07:05Z,"I cannot use the USB extension pack anymore. It was working fine a few weeks ago but now I get this error whenever I try to add a USB device (from the host) to the guest machine:

USBPROXY Getting USB descriptor failed with error 31

The USB device disappears from the host but dooes not appear on the guest. I tried to downgrade to older versions of VirtualBox but it does not work.

The USB devices are working fine on the host.

Both host and guest run Windows 10 X64 Creator Update.",M.
16850,No Connection to Mobile Phone with MTP via USB,VirtualBox 5.1.22,Windows,2017-06-21T17:09:56Z,2017-10-20T07:30:48Z,2017-10-20T07:30:48Z,"
== My configuration: ==

My Host-OS is Windows 8.1 and my VirtualBox is V5.1.22r115126 including its extension pack and installed USB-controller.
  

== The problem: ==

While my Samsung Galaxy Note 4 (SM-N910F) with Android 6.0.1 perfectly connects through USB with MTP to any native installed Mint or Ubuntu Linux OS, it does not connect to any Mint or Ubuntu if it runs virtual under VB. The file browser of the guest system shows the mobile phone but doesn't show any files. It further appears to hang. All other USB devices work well.

The phone is automatically detected as follows:
Name:         SAMSUNG_Android[0400]
Manufacturer: 04e8
Product ID:   6860
Revision no:  0400
Manufacturer: SAMSUNG
Product:      SAMSUNG_Android
Serial No.:   55xxxx7b
Port:         
Remote:       No
 
Special observation:
Two virtual Guest-OS (both MINT) were running. After I tried to connect my mobile phone without success to one Guest-OS, I shut the Guest-OS down and suddenly found that the phone was connected to the remaining Guest-OS as MTP-device and showed all directories and files as it should be and everything worked fine.


== Conclusion: ==

VB has a bug in handling USB MTP devices or certain USB MTP devices (like my Samsung Galaxy Note 4).

I would be grateful if you could provide a solution or if you book and confirm this as a VB bug.

Didi

  
",Didi
16776,use of USB Audio device in guest trap the host on exiting VM,VirtualBox 5.1.22,Windows,2017-05-21T17:05:21Z,2017-05-21T17:05:21Z,2017-05-21T17:05:21Z,"Host: Windows 7, 32-bit
Guest: OS/2

When I use an USB Audio device (I have not tested any other isochronous
device) in the guest and if I subsequently end the VM,
a trap will happen inside VirtualBox, see attached screenshot.
Ejecting the USB Audio device in the guest before exiting the VM makes
no difference.
Using the very same USB Driver stack under an native OS/2 Installation
does not exhibit any trap.",lerdmann
16765,Virtualbox crashes whit device in DFU mode attached to USB,VirtualBox 5.1.22,Linux,2017-05-17T23:12:20Z,2017-05-17T23:19:19Z,2017-05-17T23:19:19Z,"I work with a device that needs to be rebooted in DFU mode in order to be updated. This device is already connected to the VM with JTAG and UART connections through USB connectors. So far so good, I can see the devices, read data on serial port, list the devices using lsusb, udev rules are properly applied, everything works fine. My problem happens when I reboot the device and remove the jumper that puts the device in DFU mode. As soon as the device boots the VM freezes and goes to an Aborted state. 

I'm using Virtualbox + vagrant but I was also able to reproduce this issue using a pure Virtualbox machine. Issue is also reproducible with older versions of Virtualbox. Host runs on Ubuntu 14.04 and guests are Ubuntu 14.04 and Ubuntu 16.04.

I went through tutorials and forums posts trying to get it to work but I was not able to find a solution and I really need it working as it is a blocker to use virtual machines on my environment. 

Attached are Virtualbox log and core dump.   ",carlosavj
16828,Unknown USB device detected,VirtualBox 5.1.20,Windows,2017-06-13T17:43:23Z,2017-06-14T16:14:45Z,2017-06-14T16:14:45Z,"There is a line in my VBoxSVC.log that says:
00:00:00.546001          USB: Unknown USB device detected (idVendor: 0x8087, idProduct: 0x07da). Please, report the idVendor and idProduct to virtualbox.org.

So, I am reporting it.",RayH
15709,mouse does not work anymore when newer VB starts a VM,VirtualBox 5.1.2,Windows,2016-07-29T06:45:17Z,2016-08-11T13:50:02Z,2016-08-11T13:50:02Z,"mouse is frozen when newer VirtualBox (5.024, 5,026, 5.1.2) starts a VM with 4.3.32 everything is fine.
I use a mircosoft touch mouse with.",xdk
16620,Crash when removing USB device,VirtualBox 5.1.18,Windows,2017-03-29T16:07:08Z,2017-03-29T16:07:08Z,2017-03-29T16:07:08Z,"I have a USB Wi-Fi dongle which I occasionally use from my virtual Linux guest (besides an ordinary Ethernet connection via the Windows host). I got into the habit of removing it virtually (i.e making it invisible to the guest via the VirtualBox pop-up menu → Devices → USB, then unchecking the relevant device) before saving the state of the virtual machine, because if I don’t do that I occasionally get my Linux guest’s system log spammed with error messages when I restore the virtual machine.

In 5.0.32 (and at least a couple of earlier versions) it worked without a hitch, but in 5.1.18 the guest crashes when I do it. Specifically, I get a Windows pop-up (and an entry in Windows application log) with a message like this:
>  VirtualBox.exe - Application Error : The instruction at 0x00007FFD56EA7D70 referenced memory at 0x00000000000000E8. The memory could not be read.

If I do not close the pop-up, the virtual machine crashes soon anyway. In one case, it crashed when I tried to save its state; in another, it crashed as soon as I tried to sync the filesystem in the Linux guest (via the sync command).

As the bug is a deal-breaker to me, I have returned to 5.0.32.

Host: Windows 10 Pro 64-bit[[br]]
Guest: Ubuntu 14.04.5 LTS 64-bit with Guest Additions installed",mgrzegor
16618,USB Device Filter ASK ME WHAT TO DO,VirtualBox 5.1.18,all,2017-03-29T04:31:25Z,2017-03-29T12:21:46Z,2017-03-29T12:21:46Z,"Currently you need to set up a device filter for each USB device that you want to connect to VM instead of Host device.

It would be great if you could have a filter called ASK ME WHAT TO DO WHEN USB DEVICE IS CONNECTED

When this filter is enabled, and any USB device is plugged in, then a popup window would say ""Would you like to connect to Host computer or to VM #1 (or VM #2 or VM #3)""

Basically its a popup that asks where you to connect the newly plugged in USB device. This would eliminate the need of having to create seperate filters for new USB device you want to connect to a VM. It would also make it easier to move the device between VM and Host.
",jshrek
16466,VB 5.1.14 (linux host / win7 guest) fails concurrent audio/video input from integrated USB device (Logitech C920 webcam); separate devices work OK,VirtualBox 5.1.14,Linux,2017-02-08T16:04:46Z,2020-04-23T20:46:18Z,2020-04-23T20:46:18Z,"I've a desktop with VB 5.1.14 installed
{{{
	VBoxManage --version
		5.1.14r112924
}}}
and running
{{{
	VBoxManage list runningvms
		""Win7_64"" {71...e9}
}}}
on linux/64 host
{{{
	VBoxManage list hostinfo
		Host Information:

		Host time: 2017-02-08T15:13:41.459000000Z
		Processor online count: 4
		Processor count: 4
		Processor online core count: 4
		Processor core count: 4
		Processor supports HW virtualization: yes
		Processor supports PAE: yes
		Processor supports long mode: yes
		Processor supports nested paging: yes
		Processor#0 speed: 3010 MHz
		Processor#0 description: AMD Phenom(tm) II X4 945 Processor
		Processor#1 speed: 3010 MHz
		Processor#1 description: AMD Phenom(tm) II X4 945 Processor
		Processor#2 speed: 3010 MHz
		Processor#2 description: AMD Phenom(tm) II X4 945 Processor
		Processor#3 speed: 3010 MHz
		Processor#3 description: AMD Phenom(tm) II X4 945 Processor
		Memory size: 16030 MByte
		Memory available: 2423 MByte
		Operating system: Linux
		Operating system version: 4.9.8-2.gaf90696-default
}}}
with up-to-date extpack installed
{{{
	VBoxManage list extpacks
		Extension Packs: 1
		Pack no. 0:   Oracle VM VirtualBox Extension Pack
		Version:      5.1.14
		Revision:     112924
		Edition:
		Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk
		VRDE Module:  VBoxVRDP
		Usable:       true
		Why unusable:
}}}
The host runs PulseAudio.

I have two devices attached and functional in the host, an integrated (audio + video) webcam, and a standalone microphone
{{{
	lsusb | egrep -i ""Logitech|Telex""
		Bus 001 Device 011: ID 046d:082d Logitech, Inc. HD Pro Webcam C920
		Bus 001 Device 010: ID 0562:0002 Telex Communications, Inc. Telex Microphone

	hwinfo --usb
		...
		11: USB 00.1: 0000 Unclassified device
		  [Created at usb.122]
		  Unique ID: xnLL.dxozCEIXKDA
		  Parent ID: k4bc.029GFTetOb3
		  SysFS ID: /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-4/1-4:1.1
		  SysFS BusID: 1-4:1.1
		  Hardware Class: unknown
		  Model: ""Logitech HD Pro Webcam C920""
		  Hotplug: USB
		  Vendor: usb 0x046d ""Logitech, Inc.""
		  Device: usb 0x082d ""HD Pro Webcam C920""
		  Revision: ""0.11""
		  Serial ID: ""60F274DF""
		  Driver: ""uvcvideo""
		  Driver Modules: ""uvcvideo""
		  Speed: 480 Mbps
		  Module Alias: ""usb:v046Dp082Dd0011dcEFdsc02dp01ic0Eisc02ip00in01""
		  Config Status: cfg=new, avail=yes, need=no, active=unknown
		  Attached to: #24 (Hub)

		12: USB 00.0: 0401 Multimedia audio controller
		  [Created at usb.122]
		  Unique ID: cLrx.qTkEoUPZciD
		  Parent ID: k4bc.029GFTetOb3
		  SysFS ID: /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-2/1-2:1.0
		  SysFS BusID: 1-2:1.0
		  Hardware Class: sound
		  Model: ""Telex Microphone""
		  Hotplug: USB
		  Vendor: usb 0x0562 ""Telex Communications, Inc.""
		  Device: usb 0x0002 ""Telex Microphone""
		  Revision: ""1.00""
		  Serial ID: ""XXXXX""
		  Driver: ""snd-usb-audio""
		  Driver Modules: ""snd_usb_audio""
		  Speed: 12 Mbps
		  Module Alias: ""usb:v0562p0002d0100dc00dsc00dp00ic01isc01ip00in00""
		  Driver Info #0:
		    Driver Status: snd_usb_audio is active
		    Driver Activation Cmd: ""modprobe snd_usb_audio""
		  Config Status: cfg=new, avail=yes, need=no, active=unknown
		  Attached to: #24 (Hub)
		...
}}}
In the host, under PulseAudio routing, the webcam &/or the standalone mic can be used by linux native apps separately &/or concurrently.  No issues.

In VB, Audio settings are set to
{{{
	Audio
		HostDriver: PulseAudio
		Constroller: Intel HD Audio
}}}
The VM sees the mic & webcam on the host as
{{{
	VBoxManage list usbhost
		...
		UUID:               24651a23-221b-45e4-bddf-00bbfc1ce03a
		VendorId:           0x0562 (0562)
		ProductId:          0x0002 (0002)
		Revision:           1.0 (0100)
		Port:               1
		USB version/speed:  1/Full
		Manufacturer:       Telex Communications, Inc.
		Product:            Telex USB microphone
		SerialNumber:       XXXXX
		Address:            sysfs:/sys/devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-2//device:/dev/vboxusb/001/010
		Current State:      Captured
		...
		UUID:               272cd013-38e7-4515-af01-9c8f2aebbbd0
		VendorId:           0x046d (046D)
		ProductId:          0x082d (082D)
		Revision:           0.17 (0017)
		Port:               3
		USB version/speed:  2/High
		Manufacturer:       Logitech, Inc.
		Product:            HD Pro Webcam C920
		SerialNumber:       60F274DF
		Address:            sysfs:/sys/devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb1/1-4//device:/dev/vboxusb/001/011
		Current State:      Busy
}}}
The VM runs Win7/64 with SP1 + latest ConvenienceRollup & all updates.


I'm attempting to get the VM to use ONLY the Logitech C920, for BOTH audio / video input source.

'''[CASE_1]'''

device selection state @ VM 'Devices'
{{{
	Devices
		USB
			[ ] Telex Communications, Inc. Telex USB microphone [0100]
			[ ] Logitech, Inc. HD Pro Webcam C920 [0011]
		Webcams
			[X] HD Pro Webcam C920
}}}
MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
@ Microsoft Setup Wizard

there is NO detected audio input at all.


'''[CASE_2]'''

changing device selection state @ VM 'Devices' to
{{{
	Devices
		USB
			[X] Telex Communications, Inc. Telex USB microphone [0100]
			[ ] Logitech, Inc. HD Pro Webcam C920 [0011]
		Webcams
			[X] HD Pro Webcam C920
}}}
MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
now @ Microsoft Setup Wizard, audio IS detected from the Telex.

and, testing further, 'separate device' audio & video work
{{{
	WebCam video INPUT from the C920      ---> WORKS
	MIC    audio INPUT from the Telex     ---> WORKS
}}}
So, this is a working config for , e.g., WebEx use in the VM

'''[CASE_3]'''

changing device selection state @ VM 'Devices' to
{{{
	Devices
		USB
			[ ] Telex Communications, Inc. Telex USB microphone [0100]
			[X] Logitech, Inc. HD Pro Webcam C920 [0011]
}}}
automatically forces the change
{{{
		Webcams
			No WebCams detected
}}}
In this config

MS using Virtual Audio Device'Sound' > 'Recording'
{{{
	Microphone
	High Definition Audio Device
	Default Device
}}}
now @ Microsoft Setup Wizard, audio IS detected from the C920.

but there is NO detected/usable video input.",PGNd
16449,Flashing ROM on USB device fails,VirtualBox 5.1.14,Windows,2017-02-03T22:55:21Z,2017-12-12T10:11:07Z,2017-12-12T10:11:07Z,"I'm working with a custom device so there isn't an obvious way to reproduce the problem. When we flash the ROM on our custom USB device from Linux as a guest of Windows using VirtualBox, the process fails at the beginning of the process. One thing of note is that our device uses a different device ID when it's waiting to be flashed and when it is operating normally. This required 2 USB Device Filters to be added to VirtualBox. Thus process works on VMWare and on native Linux.
",capellsk
16548,Win7 guest does not enumerate COM port with new MacBook Pro,VirtualBox 5.1.14,Mac OS X,2017-03-10T11:22:59Z,2017-03-17T11:13:35Z,2017-03-17T11:13:35Z,"I have a new MacBook Pro (USB-C ports only) with macOS Sierra 10.12.3.  It has a FTDI232R serial device connected.

Attaching the serial device causes Win7 to show the device in Device Manager with errors and it cannot enumerate a COM port.

This was never a problem with my old MacBook.

I tried using VirtualHere (USB over IP) between host and guest.  This solution usually solves my USB problems with VB, but not in this case.  It has the exact same symptoms.

I tried running VirtualHere on a RaspberryPi and then the FTDI232R device successfully enumerated in the Win7 guest.

Therefore I think something has changed with the USB on the new MacBook Pro, and VB needs modifications to support it properly.",BrendanSimon
16533,Boot from usb device.,VirtualBox 5.1.14,Windows,2017-03-04T11:39:58Z,2017-03-04T11:39:58Z,2017-03-04T11:39:58Z,Add boot from usb device.,q34er6ty7
16507,Windows 10 freezes when using a KVM switch while VirtualBox is running VMs,VirtualBox 5.1.14,Windows,2017-02-23T18:53:48Z,2017-02-23T18:53:48Z,2017-02-23T18:53:48Z,"I have the following problem. I have Windows 10 PC, Virtualbox 5.1.14 r112924 installed, and a Keyboard/Mouse Switch via USB connected to this PC for Mouse and Keyboard.
Using the KVM switch is working perfectly fine with all applications.
BUT when I run a VM in VirtualBox, and then I use the KVM switch to connect to another computer, and switch back to Windows 10, I have no access to that computer anymore. Keyboard and Mouse don't work anymore. I have to hard reboot the Windows 10 computer. This is reproducible every time. The guest OS is always CentOS 7.2.",bati2712
16500,An USB issue only on Linux guest,VirtualBox 5.1.14,Windows,2017-02-21T07:55:44Z,2017-02-22T21:07:35Z,2017-02-22T21:07:35Z,"I try to use a common FTDI based USB UART (virtual serial port) chips on Win7 host and 32 bit Linux guest and it causes serial communication to drop because some received serial data is lost within seconds of usage. FTDI chips use USB 1.1 are known to work reliably on Linux too.

It has repeated at least on VBox 4.3.5, 5.1.10, 5.1.12 and 5.1.14 on two completely different host computers and various 32bit guests also (debial/ubuntu). USB mode setting 1.1, 2.0 and 3.0 have been tested - no difference.

I've tested vmWare Workstation Player on same computer and same guest image, and it WORKED FLAWLESSLY (10hr+ stress test done). Also it works on same computers with Win7 guest. So problem seems to occurs only with Linux guest + virtualbox combo.

I hope this helps!",reTok
16338,USB Root Hub Shows Yellow Exclamation Mark in Device Manager,VirtualBox 5.1.12,Windows,2016-12-30T08:47:44Z,2021-12-09T16:58:17Z,2021-12-09T16:58:17Z,"Environment:
    ASMedia USB 3.0 extended host controller with the '''vendor driver'''.[[BR]]Operating system is Windows.

Steps:
    1. Open VM VirtualBox and create virtual machine (Type is Microsoft Windows).
    2. Open Device Manager and disable ASMedia USB Host Controller.
    3. Enable ASMedia USB Host Controller.
    4. USB Root Hub shows yellow exclamation mark.
    5. Device Manager displays the following message in the USB Root Hub Properties dialog box, on the General tab, in the Device Status text box:[[BR]]Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)[[BR]]The driver could not be loaded because a previous version of the driver is still in memory.",Gary_Chen
16382,Win10: VBoxSVC hangs when thunderbolt-to-USB is disconnected (PC undocked),VirtualBox 5.1.12,Windows,2017-01-12T18:52:03Z,2020-02-11T20:59:09Z,2020-02-11T20:59:09Z,"USB ports on the HP ZBook Dock with Thunderbolt 3 is unresponsive after undocking/docking when VirtualBox is running.

Hardware: HP ZBook Studio G3 with HP ZBook Dock with Thunderbolt 3

'''To reproduce :'''
1. Start the Oracle VM VirtualBox.
2. Start the Ubuntu VM . 
3. Undock - Unplug the Thunderbolt cable. (ie. disconnect laptop from dock ...)
4. Re-dock - Plug the Thunderbolt cable.
5. The Thunderbolt dock USB ports are non-responsive.

'''Observations:'''
Something in VirtualBox seems to ""block the system from clearing the instance of the USB root hub driver from memory on the Thunderbolt disconnect"".

After the problem has occurred (ie. USB ports on dock is unresponsive), closing all programs, attempting to reboot Windows, the following Window message appears:

""VirtualBox Interface  Has active connections.""

Aborting the Windows reboot and checking ""Task Manager"" shows that the VBoxSVC.exe process is still active.

Manually killing the VBoxSVC.exe process seems to restore the Thunderbolt dock's USB ports.


This may be related to: Ticket #16338 USB Root Hub Shows Yellow Exclamation Mark in Device Manager

Forum thread:
https://forums.virtualbox.org/viewtopic.php?f=6&t=81228&hilit=Thunderbolt&sid=af360a89332f31d27ba3fc2bf64e502e&start=15

",vscheng
16374,"Problem with usb flash disk: host = W10, guest=W7 and XP",VirtualBox 5.1.12,Windows,2017-01-10T18:11:26Z,2017-01-11T19:32:01Z,2017-01-11T19:32:01Z,"I use win 10 64 bit laptop and virtualbox  5.1.12. When I use VM with W7 or XP: USB flash disk work randomly. Most of the time : doesn't work. When I catch usb device on VM, it disappear on host , doesn't appear on guest and usb device disappear of the list of USB device. You have to disconnect USB flash disk to have it on host.
All VM I use, work very well with host:W7 32b.
I have reinstall lot of time: virtualbox, extension pack and addition guests.
Bests regards.
",galexis
16358,USB MSD device BBB (bulk only) transfer fails due to CBW/CSW tag mismatch,VirtualBox 5.1.12,Windows,2017-01-05T15:11:23Z,2017-01-07T15:46:29Z,2017-01-07T15:46:29Z,"Host is Windows 7, guest is OS/2 (eComStation, latest of everything).
I am using this set of USB drivers in the guest:
http://hobbes.nmsu.edu/download/pub/incoming/usbdrv213.zip

I have an ""Alcor Micro Corp."" USB stick (vendor id: 0x58F, product id:0x6387).
If I connect that device to the guest it is properly detected as a USB 2.0 device and I can access it in the guest. However, if I start some lengthy operation like a chkdsk.exe on the device, I eventually get a mismatch of the tag word in the sent out CBW block and the subsequently received CSW block (I have detected this by enabling tracing for USBMSD.ADD in OS/2 and looking at the trace output). At the point of failure, the CSW tag is off by 1 from the tag transferred in the corresponding CBW and it is equal to the CBW and CSW of the last (successful) transmission (as can be expected). If the tag is out of sync the USBMSD.ADD driver issues a MSD reset command and subsequently clears the input and output bulk pipes which of course is reported back to the OS as a transfer failure.

If I use the very same device under a native OS/2 installation with the very same set of USB drivers, I can successfully run the chkdsk.
To me it looks like that on a large number of BBB transfers (where I cannot give a hard and fast value for ""large""), that the USB virtualization eventually gets out of sync.

Let me know if you need any Virtualbox logs.




",lerdmann
16261,no media in w7 when connecting usb3 disk with uas,VirtualBox 5.1.10,Linux,2016-12-02T19:22:58Z,2016-12-05T08:11:55Z,2016-12-05T08:11:55Z,"I'm using gentoo, kernel 4.4.26, VB version 5.1.10. Also I have an external disk seagate 3tb st3000dm001 in its native external enclosure (with usb3). I get a contradiction.
On the host (gentoo) it is seen as a disk ONLY if the module ""uas"" (USB attached SCSI) is loaded. Otherwise, only as some usb controller.
In the guest (w7pro) it appears as a disk ONLY if the ""uas"" module of the host is disabled. Otherwise, again only as some attached usb device.
I could reproduce it several times in a row. With and w/o a reboot.

Technically I can insert/remove the ""uas"" module depending on a situation. Also, I'm not sure is it a problem of ""uas"" module or VB, but the pattern is clear.

Any suggestions to solve/improve this behaviour?",alex-kas
16227,USB M-Audio fast track ultra device not working,VirtualBox 5.1.10,Windows,2016-11-24T17:07:29Z,2016-11-24T17:07:29Z,2016-11-24T17:07:29Z,"After reading several forums I managed to have my guest (windows 7 home) recognising my audio device.
I installed the appropriate M-Audio drivers with no errors.

However, if I try to play any sound the device basically freezes the program which is attempting to use it and seemed to play like a microsecond of music every several seconds. This also happens if I directly try to test it from windows (the green bars indicating the volume in output move incredibly slowly).",epifab
14815,USB redirection software and VirtualBox,VirtualBox 5.0.8,Windows,2015-11-13T07:56:59Z,2015-11-13T07:56:59Z,2015-11-13T07:56:59Z,"Description of the problem is on the forum:

https://forums.virtualbox.org/viewtopic.php?f=6&t=74487",bartekbb1976
14667,Enhancement: Forward all USB devices except some,VirtualBox 5.0.6,all,2015-10-04T19:24:52Z,2015-10-04T19:48:19Z,2015-10-04T19:48:19Z,"USB Device Filters give possibility to forward some specific USB device from host to guest.
They also give possibility to forward some set of devices specified by criteria (e.g. any Kingston-manufactured USB flash drive; great feature!).
What is missing is a possibility to make negative filters; e.g. to forward ''any USB device except keyboard and mouse'' from host to guest.

Use case 1:
For specific reasons I work mostly inside guest OS. I don't want to go to virtualbox menu and click on device every time I insert an USB device; neither I want to create filter for every manufacturer whose device I may use. (On the other hand, I can't use filter that matches all USB devices, because keyboard, mouse and some other stuff need to be in exclusion list, i.e. available to host OS, not forwarded to guest.)

Use case 1.1:
My separately-living relative (hard-learning novice in computers) works only inside guest OS. Actually, he doesn't know anything about host OS and virtualbox at all: guest OS is always in fullscreen mode, trying to behave as it's the only OS. Same problem as above: he needs all inserted USB hardware (with some exclusion list, like: keyboard, mouse, etc) to be forwarded to guest OS, but unlike use case 1 where it's all about convenience, in use case 1.1 it's a critical feature (virtualbox needs to work ''invisibly/seamlessly'' for novice user who never presses Host Key and known nothing about virtualbox menu).

Use case 2.
See https://forums.virtualbox.org/viewtopic.php?f=9&t=49100 (not my post). The topic starter uses virtualbox with guest OS for inspecting suspicious storage media; he wants all devices except some exception list to be by default forwarded to guest OS.",Sasha1024
17572,USB device named incorrectly,VirtualBox 5.0.40,Linux,2018-02-27T18:43:20Z,2018-03-02T08:49:28Z,2018-03-02T08:49:28Z,"Hi All,

Really odd behaviour we are getting from our VMs. We have 3 VMs running windows 7 and each has a dongle that grants access to proprietary software. 2 dongles grant access to HASP software and 1 grants access to Windfarmer. These usb devices are incorrectly named in Virtual box which is causing some confusion, We can only use Windfarmer software when one of the ""HASP"" dongles is connected and vice versa.

Not sure how/when this began happening or why. This would be a purely aesthetic problem but the two HASP dongles are identical and cannot be distinguished between each other using the USB filter so occasional they are assigned to the incorrect VM which means we have to manually fix it.

Logs attached.  





",DanitDan
15588,USB device passthrough does not work,VirtualBox 5.0.24,Windows,2016-07-10T09:26:02Z,2017-05-02T10:34:01Z,2017-05-02T10:34:01Z,"Hello,

Since a couple of months, I'm having trouble passing through USB devices to virtual machine.
My host operating system is Windows 7 x64 Professional with all the updates and I'm running the latest version of VirtualBox (this happens with all the latest version and since I've had the problem reverting doesn't seem to do anything).

In the VirtualBox log I've found this line, which is added twice every time I try to assign a USB device:

{{{
USBPROXY usbLibDevCfgDrGet: DeviceIoControl 1 fail winEr (31)
}}}

At the very beginning of each log file I also see the following:

{{{
usbLibDevCfgDrGet: DeviceIoControl 1 fail winEr (31)
}}}

which I've seen in a lot of log files (not related to this problem) on the internet. I'm not really sure if this is an issue o maybe a mis-initialization.

If I re-try assigning the same USB device a second time I see the following message:

{{{
Connessione del dispositivo USB USB Flash Disk [1100] alla macchina virtuale VmXP_Temp non riuscita.

USB device 'USB Flash Disk' with UUID {a416ea81-cffc-4c89-8ce1-80a66a1aedcd} is busy with a previous request. Please try again later.

Codice 'uscita: E_INVALIDARG (0x80070057)
Componente: HostUSBDeviceWrap
Interfaccia: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Chiamante: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

which might mean something is ""stuck"" in VirtualBox and this may not be an host issue.

The host logs don't contain anything suspicious and the guest logs too (it doesn't seem I reach a point in which the guest sees anything).

I didn't try with a Linux guest but I'm pretty sure that won't make any difference.

Thanks,
Filippo",filipposironi
15553,USB 1.1 (OHCI) controller stops working after a period of time,VirtualBox 5.0.22,Windows,2016-06-28T14:52:03Z,2017-12-12T10:11:26Z,2017-12-12T10:11:26Z,"I have 2 identical FTDI Quad RS232-HS USB virtual serial port chips connected to a Ubuntu 12.04.5 LTS guest running on Windows host (behaves the same on Win7x64 and Win10x64).
I am using USB 1.1 (OHCI) controller, but the FTDI chips are physically connected to the host via USB2.0 ports.
On VirtualBox 4.3.12 everything works just fine.
On higher versions (I tried 4.3.38, 5.0.22, 5.0.23, 5.1.0 Beta 3) I am able to open the virtual serial ports and read and write data to them for a few minutes (maybe 5) after which the communication stops and no data can be sent nor received.
When monitoring the USB ports on the guest with usbmon+wireshark, I can see no packets being sent or received after it stops working.
This only happens when 2 are connected and open at the same time. One on its own doesn't do it.
When I install the extension pack and use USB3.0 (xHCI), the problem doesn't appear.

I am attaching two logs, one running USB1.1 and one USB2.0 controllers both manifesting the issue.",rp3k
16852,USB Barcode Scanner not working properly under Windows Virtualbox,VirtualBox 5.0.20,Linux,2017-06-22T06:31:25Z,2017-06-22T06:31:25Z,2017-06-22T06:31:25Z,"'''Environment:''' Using a Linux host with Virtualbox 5.0.20 and a Windows 7 Prof. guest. [[BR]]

USB 3.0 XHCI activated. [[BR]] [[BR]]


There is a USB Barcode Scanner (Datalogic Powerscan) connected
and installed.
For some reasons, the scanner is not working proberly. 
It works correct for 5-10 times of scanning
and then it drops a couple of characters out for the next scan.
It correctly scans into Linux - without any error.

''It must be a reason of the Virtualbox USB Handling.''

'''If i open wireshark with USBPcap installed and start to sniff the USB ports the problem is solved, as long as the Wireshark is running.'''
See attached File for more information of scans.

There are already 2 Tickets of this problem, years ago but without any solution

[https://www.virtualbox.org/ticket/11671 Ticket 11671][[BR]]

[https://www.virtualbox.org/ticket/11772 Ticket 11772]


",itsbasti
15410,USB driver issue,VirtualBox 5.0.20,other,2016-05-11T16:33:14Z,2016-07-29T13:30:21Z,2016-07-29T13:30:21Z,"Hi guys.

New version  5.0.20 brought me unexpected problem with my ST-link device. I couldn't attach my stm32discovery board to my  guest Win 7 (64-bit). I tried usb filters and reinstalling drivers on my Win 7. No result. VirtualBox detects ST-Link attaced to my host OS X,  but don't give an access  to guest system. By that, I mean it doesn't attach it to the guest system. Next click, when I try to attache it again, VirtualBox show error ""Virtualbox failed to attach the usb device ....."".   Nothing helps. Only after I moved to version 5.0.16 I got it back. 

Please check it and do something. 
I don't wanna stay out of date. =( ",n0bd0y042
15550,Cannot access to USB device in host VM when installed USB redirection SW,VirtualBox 5.0.20,all,2016-06-27T07:50:53Z,2016-06-27T07:50:53Z,2016-06-27T07:50:53Z,"When I have installed specific software for USB device redirection (eg. Eltima - Flexihub or Incentives Pro - USB Redirector) on my Windows 7 (or Windows 10) host, I cannot access to any usb device on the guest (Windows XP or Windows 7). 

The only way to have USB working inside the guest is uninstall the software.

I found on the forum the same problem occurred to another user:
https://forums.virtualbox.org/viewtopic.php?f=6&t=74487

I also tried to install VB version 5.0.22 but the problem persists.

The steps for replicate the problem are:
1) Install Flexihub or USB Redirector
2) Run a VM
3) Try to connect an usb device

Error occurred:
USB device 'Kingston DataTraveler G3' with UUID {4b7d935e-b532-4f63-b48c-167b75cbb8c8} is busy with a previous request. Please try again later.
Exit code: E_INVALIDARG (0x80070057)
Component: HostUSBDeviceWrap
Interface: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Caller: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}



",oscarB
15393,Not able to connect to USB Webcam,VirtualBox 5.0.20,Linux,2016-05-05T17:21:44Z,2016-05-09T13:35:08Z,2016-05-09T13:35:08Z,"I am running on a Windows 10 Host. Guest is Ubuntu 14.04 LST.
I Have a Microsoft LifeCam HD-5000 webcam connected to USB 2.0

I tried to add it via settings. VB recognized the HW and I added it.

However when searching for the device with lsusb and dmesg it was nowhere to be found. 

Here is what I expected to find:
http://www.linux-hardware-guide.com/2013-05-18-microsoft-lifecam-hd-5000-hd-webcam
",Yonatan
15398,USB-devices with the same hardware-ID,VirtualBox 5.0.20,Windows,2016-05-08T07:27:26Z,2016-05-08T07:27:26Z,2016-05-08T07:27:26Z,"All USB-devices with the same hardware-ID (VID/PID) are sent to the guest system, although only one USB-device is selected. Have been tested modems and flash drives.",VitusSumy
14441,USB devices with a same name hang any further operation,VirtualBox 5.0.2,all,2015-08-14T14:29:10Z,2016-06-20T06:32:55Z,2016-06-20T06:32:55Z,If you try to connect any USB devices that have same product or manufacturer ID it will cause a hang to any further operations with any usb devices.,EAX
14532,Cannot access webcam over getUserMedia(),VirtualBox 5.0.2,Linux,2015-09-01T21:38:50Z,2016-01-15T14:22:35Z,2016-01-15T14:22:35Z,"When booting Windows 10 with the latest Edge within Virtual Box 5.0.2 from Ubuntu 15.04 I cannot access the Webcam within Edge.

Beware, it works fine when the website uses a Flash plugin. There the webcam shows up. But NOT when it's being loaded through the getUserMedia() API. It's a native Javascript function most modern browsers implement.

I have the drivers installed. Let me repeat: it works fine through Flash, but not via JavaScript. Can you please look at it? This is blocking the development of www.videomail.io where I need to test it for the latest Edge.

Many thanks!",Michael Heuberger
15323,Sandisk Extreme SDCZ80 flash drive 'no medium found',VirtualBox 5.0.18,Mac OS X,2016-04-19T20:04:26Z,2016-04-19T20:04:26Z,2016-04-19T20:04:26Z,"When connecting a Sandisk Extreme SDCZ80 64GB (partitioned as either fat32 or exfat) to either a Linux or Windows 7 guest OS in VirtualBox 5.0.18 running on OS X 10.11, the flash drive is recognised by the guest OS, but in all instances it appears as an empty drive.

On the Windows 7 VM trying to access the flash drive pops up a message requesting to insert a disk (as it does with an empty DVD drive). When trying to access the drive in Linux (Ubuntu) the OS errors ""cannot open /dev/sdb: No medium found"". Also, while lsusb on the Linux VM lists the device and /dev/sdb is created, Gparted does not list the drive for formatting and no /dev/sdb1 partition is present on the Linux VM.

The Sandisk Extreme SDCZ80 mounts fine on dedicated Linux, Windows 7 and OS X hosts. Data can be copied and read without issue. Only when using the Sandisk Extreme USB3 flash drive inside of VirtualBox VM's do they appear as an empty drive.

Other USB3 flash drives do not exhibit this behaviour in VirtualBox and data on the drives is accessible without issue inside both the Linux and the Windows 7 VM. The problem only manifests itself with the Sandisk Extreme SDCZ80 64GB model.

Dmesg output (from the Linux guest VM)
{{{
[   28.654211] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[   28.680737] usb 2-1: New USB device found, idVendor=0781, idProduct=5580
[   28.680741] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   28.680743] usb 2-1: Product: Extreme
[   28.680745] usb 2-1: Manufacturer: SanDisk
[   28.680746] usb 2-1: SerialNumber: AA010118161550470319
[   28.708104] usb-storage 2-1:1.0: USB Mass Storage device detected
[   28.708196] scsi host3: usb-storage 2-1:1.0
[   28.711502] usbcore: registered new interface driver usb-storage
[   28.717525] usbcore: registered new interface driver uas
[   29.708039] scsi 3:0:0:0: Direct-Access     SanDisk  Extreme          0001 PQ: 0 ANSI: 6
[   29.712811] sd 3:0:0:0: Attached scsi generic sg2 type 0
[   29.718321] sd 3:0:0:0: [sdb] Attached SCSI removable disk
}}}

lsusb output (from the Linux guest VM)
{{{
vm@xubuntu:~$ lsusb
Bus 002 Device 002: ID 0781:5580 SanDisk Corp. SDCZ80 Flash Drive
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
}}}

Output when trying to access the drive using cfdisk (from the Linux guest VM)
{{{
vm@xubuntu:~$ sudo cfdisk /dev/sdb
[sudo] password for vm: 
cfdisk: cannot open /dev/sdb: No medium found
}}}

So in summary:
1. Other (somewhat slower) USB3 flash drives work fine in these VirtualBox VM's (they all mount and can be read without issue on both a Linux and Windows 7 VM)
2. The Sandisk Extreme 64GB works fine on dedicated hardware and can be mounted and read by different operating systems (Windows 7, OS X, Linux). But it's detected as a drive without any media inserted (like a DVD drive) on both the Linux and Windows 7 VMs in VirtualBox.

",crahan
15282,USB subsystem or USB logging is broken,VirtualBox 5.0.16,Mac OS X,2016-03-29T20:19:04Z,2016-04-05T08:11:04Z,2016-04-05T08:11:04Z,"The USB subsystem is broken either itself or the logging.

I have a USB device that supports CDC and UVC. Putting UVC aside, I want to talk CDC with the device, but only get garbage. For that reason I ran usbmon on the Linux guest and USB logging from VirtualBox to identify the problem. The USB log from VirtualBox is garbage. Unfortunatly, I can not verify if it is only the logging or f VirtualBox send this out.

I attached the plain text log from the guest and from Virtual Box. Both should be equal, but its not.

The most obvoius is packet number 107 in guest and number 104 in host:

Guest
{{{
Frame 107: 71 bytes on wire (568 bits), 71 bytes captured (568 bits) on interface 0
USB URB
URB setup
    bmRequestType: 0x21
    bRequest: 32
    wValue: 0x0000
    wIndex: 2
    wLength: 7
Leftover Capture Data: 00c20100000008
}}}

Host
{{{
Frame 104: 72 bytes on wire (576 bits), 64 bytes captured (512 bits) on interface 0
USB URB
URB setup
    bmRequestType: 0x21
        0... .... = Direction: Host-to-device
        .01. .... = Type: Class (0x01)
        ...0 0001 = Recipient: Interface (0x01)
    bRequest: 32
    wValue: 0x0000
    wIndex: 2 (0x0002)
    wLength: 7

No.     Device Source Destination Protocol Length Info URB type URB transfer type Data length [bytes] Leftover Capture Data bString
    105 3          0.3.0                 host                  USB      72     URB_CONTROL out[Packet size limited during capture]             URB_COMPLETE URB_CONTROL       0                                         

Frame 105: 72 bytes on wire (576 bits), 64 bytes captured (512 bits) on interface 0
USB URB
[Packet size limited during capture: USB truncated]

No.     Device Source Destination Protocol Length Info URB type URB transfer type Data length [bytes] Leftover Capture Data bString
    106 3          host                  0.3.0                 USB      71     Unknown type c2 Request                                         URB_SUBMIT URB_CONTROL       0                                         

Frame 106: 71 bytes on wire (568 bits), 64 bytes captured (512 bits) on interface 0
USB URB
URB setup
    bmRequestType: 0x00
        0... .... = Direction: Host-to-device
        .00. .... = Type: Standard (0x00)
        ...0 0000 = Recipient: Device (0x00)
    bRequest: Unknown (194)
    wValue: 0x0001
    wIndex: 0 (0x0000)
    wLength: 8
}}}

Here it can be seen that the ""left over capture data"", the actual data of the USB request (setting baudrate to 115200 bps) is recognised as a 2nd USB packet. As 0xC2 is detected as request type, 0x01 as wValue, and 0x08 as wLength instead as part of the packet number 104.",Pingu
15255,USB devices not recognized when attached after wakeup,VirtualBox 5.0.16,Mac OS X,2016-03-18T22:54:46Z,2016-03-18T23:01:51Z,2016-03-18T23:01:51Z,"The following sequence of events results in an OSX host not recognizing USB devices that are attached to it.

1) Start VirtualBox VM
2) Put computer to sleep, e.g. close laptop lid and unplug USB hub connected to keyboard and mouse
3) Wake computer up
4) Re-plug USB hub

I'm using OSX 10.11.4 with VirtualBox 5.0.16. My USB hub is a Dell Monitor, model P2715Q.

The following lines from system.log seem relevant.
Mar 18 15:24:54 pwnage kernel[0]: 043192.504567 HS05@14200000: AppleUSB20XHCIPort::resetAndCreateDevice: failed to create device, disabling port
Mar 18 15:24:56 pwnage kernel[0]: 043193.752262 HS05@14200000: AppleUSB20XHCIPort::resetAndCreateDevice: failed to create device, disabling port",pwnall
15050,Can not connect USB Stick to VM,VirtualBox 5.0.14,Windows,2016-01-20T10:45:10Z,2020-05-25T18:09:52Z,2020-05-25T18:09:52Z,"How to reproduce:
Starting VM. Plugging in USB Stick. After this the following message appears:

Failed to create a proxy device for the USB device. (Error: VERR_PDM_NO_USB_PORTS).


Result Code: 
E_FAIL (0x80004005)
Component: 
ConsoleWrap
Interface: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
",Uti
15253,USB does not with VirtualBox 5.x on OpenIndiana,VirtualBox 5.0.14,Solaris,2016-03-18T05:12:42Z,2016-03-18T05:12:42Z,2016-03-18T05:12:42Z,"Guest: Windows XP with CH-340 USB to Serial driver installed
Host: SunOS watt 5.11 oi_151a9 i86pc i386 i86pc  (OpenIndiana)
VirtualBox: 5.0.14 with the extension pack installed

The USB to Serial adapter works fine in VirtualBox 4.*, but does not communicate in Virtual 5.x. The device does enumerate and shows up in the guest's Device Manager.

The VM log contains a number of:
00:00:37.203270 USBProxy:Command 0xc0185694 failed. Req.rc=VERR_PIPE_IO_ERROR
00:00:37.203291 USBProxy:usbProxySolarisUrbQueue Failed!! pProxyDev=0000000002828360[proxy 1a86:7523] pUrb=000000000282a5f0 EndPt=0x1 bEndpoint=0x81 enmType=3 enmDir=1 cbData=8 rc=VERR_PIPE_IO_ERROR

followed by...

00:00:39.525634 PCNet#0: Init: ss32=1 GCRDRA=0x01ae4420[64] GCTDRA=0x01ae4020[64]
00:00:41.820029 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:00:42.208793 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices
00:00:52.389837 OHCI#0: Lagging too far behind, not trying to catch up anymore. Expect glitches with USB devices

Current workaround is to remain on VirtualBox 4.x
",Deece
15136,After upgrade Virtual Box 5.0.14 does not recognise USB Key,VirtualBox 5.0.14,Windows,2016-02-10T09:56:47Z,2016-02-10T09:56:47Z,2016-02-10T09:56:47Z,"I upgraded VB from version 4.3.18 and the USB Key that has been always recognized is not recognized anymore, tested with all of the versions of USB selected. The USB Key is a Kingston Data Travel with 16GB.

Thanks in advance.",PHOTON
15102,Attached USB device filter causes VM to not start/crash,VirtualBox 5.0.14,Mac OS X,2016-02-02T16:54:54Z,2016-02-04T09:25:46Z,2016-02-04T09:25:46Z,"When I attach a PAX D200 pinpad device under the USB device filters and then proceed to start the VM the VM crashes. This is the only device I have this problem with and am able to connect similar devices from the same manufacturer without problem.

I have attached the logs and crash report.

Forum post for reference:
https://forums.virtualbox.org/viewtopic.php?f=8&t=66526&p=315196#p315196
",Figomann
14962,USB devices do not show up in VM,VirtualBox 5.0.12,Windows,2015-12-22T13:22:00Z,2016-03-01T17:21:14Z,2016-03-01T17:21:14Z,"Host OS: Windows 8.1 x64
VirtualBox 5.0.12

When I try to attach a USB device into VM it seems to get ""stuck"" or locked. When I click Devices->USB->My device (USB flash stick), I see it disappearing in the host OS, but it never appears in the guest OS (checked via dmesg: no messages at all about any new USB attachments). When I open that USB submenu again and hover my device, the tooltip tells that it is now ""Captured"", but there is no checkbox near the device name (which would indicate that the USB device is attached to the guest), and when I run VBoxManage showvminfo, it tells that there are no currently attached USB devices.

If I try to click the same device again, I get the error message that the device ""is busy with a previous request"". If I remove the device physically and reinsert it into another USB port, it appears in the USB menu as a new instance (while the previous one, the ""Captured"", remains there as well). However, clicking this new instance leads to absolutely the same behaviour: the device disappears from the host, never appears in the guest and remains forever locked in the ""Captured"" state.",Konstantin Vlasov
15042,Can't attach USB device Microchip MPLAB Real Ice,VirtualBox 5.0.12,Windows,2016-01-18T09:09:23Z,2016-01-28T16:55:18Z,2016-01-28T16:55:18Z,"Failed to attach Microchip MPLAB Real Ice to the VM Windows XP SP3

USB device 'Microchip Technology, Inc. (www.microchip.com) MPLAB® REAL ICE tm (www.microchip.com)' with UUID {30576387-492f-41fa-862e-c9b593202bde} is busy with a previous request. Please try again later.
Codice 'uscita: 
E_INVALIDARG (0x80070057)
Componente: 
HostUSBDeviceWrap
Interfaccia: 
IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Chiamante: 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
 ",Attylus76
14875,USB ISO packets get stuck in VB 5.X,VirtualBox 5.0.10,Linux,2015-11-29T00:11:42Z,2017-12-12T10:12:43Z,2017-12-12T10:12:43Z,"Hello VB,

After having used 4.X with great pleasure for a long time to debug Windows USB issues in Linux (Fedora), i have hit a snag in the 5.X series.

The problem is always the same. If i start streaming ISO packets they get stuck after a very short while. In the early 5.X builds the entire VM would implode, but now it just hangs the USB stream until i unplug the device.
There is some kind of bug in the 5.X USB implementation. If its the VB drivers in Linux or the virtual drivers in Windows is not clear to me.

Has anyone else seen this problem? I have tried all combinations of options i could think of but the problem persists.

I have attached a Wireshark trace that shows the problem up until the hang. Note that when this happens the *entire* USB freezes up, not just the ISO packets.

Thanks,

/pedro",donpedro
14922,Accessing Kinect Camera,VirtualBox 5.0.10,Mac OS X,2015-12-11T23:47:48Z,2015-12-11T23:47:48Z,2015-12-11T23:47:48Z,"Hi,
I posted my problem on the forum here:
https://forums.virtualbox.org/viewtopic.php?f=8&t=74789

There was no reply for 20 days so I thought to try and open a bug report, since I'm still unable to access the Kinect Camera using VirtualBox.

Thanks!

/Avner

The Original  Post:
--------------------------------------------------------------------------
Hi!
I am using VirtualBox with Boot2docker on OSX and I'm trying to access Microsoft Kinect for XBOX360 on the guest Linux OS.
I installed the extension pack and was able to share access to the 3 USB devices:


{{{
Microsoft Xbox NUI Motor
Microsoft Xbox NUI Audio
Microsoft Xbox NUI Camera
}}}


I was also able to share them from the docker machine to the docker containers using the '''--device''' flag.
However, while applications such as OpenNI2 are able to find the device, and even control its motor, the camera stream is always completely blank and I see messages such as:


{{{
[Stream 70] Lost 23351 total packets in 0 frames (inf lppf)
}}}


On rare occasions, one frame was suddenly able to pass and I could actually get one frozen image.
I read in several locations and also in this forum that at least regarding webcams, It is advised to use the ""Webcam passthrough mode"" described in the VirtualBox manual.
However the Kinect camera is not recognized on my host as a webcam, and the output of '''VBoxManage list webcams''' is just:


{{{
.1 ""FaceTime HD Camera (Built-in)""
0x1a11000005ac8510
}}}


When running ioreg, the XBOX devices appear as such:

{{{
Xbox NUI Motor@1a122000  <class IOUSBDevice, id 0x1000130c1, registered, matched, active, busy 0 (24 ms), retain 11>
Xbox NUI Audio@1a121000  <class IOUSBDevice, id 0x1000131a0, registered, matched, active, busy 0 (6 ms), retain 9>
Xbox NUI Camera@1a123000  <class IOUSBDevice, id 0x1000132a9, registered, matched, active, busy 0 (19 ms), retain 11>
}}}


Is there any way out of this mess?? Would appreciate any advice.
Thank you!

/Avner",Avnerus
14340,VBoxSVC usb initialization causes host USB device to disconnect,VirtualBox 5.0.0,Windows,2015-07-28T17:23:00Z,2017-03-27T00:56:53Z,2017-03-27T00:56:53Z,"VirtualBox is causing the (host) SD card reader on my Microsoft Surface Pro 3 to disconnect/crash when VBoxSVC attempts to enumerate / initialize theUSB devices on the host. Any VirtualBox activity that attempts to enumerate the host USB devices (i.e. starting the VirtualBOX GUI, or executing a ""VBoxManage list usbdevices"") appears to cause this problem.

This occurs without any guest VM's running, and without any USB devices being configured for capture by VirtualBox.

I don't know if this is a bug in the Windows SD card driver that's being exposed by VirtualBox, or if it's a bug in VirtualBox itself.

To reproduce:
1. On a Surface Pro 3, mount an SD card
2. Initiate a large file copy to the SD card.
3. While the file copy is underway, execute the ""VBoxManage list usbdevices"" command. (or just start the VirtualBox GUI)

Expected result:
Files continue to copy to the SD card

Actual result:
The SD card volume drops offline. Windows displays a ""destination does not exist"" error. The windows event log shows a ""An error was detected on device \Device\Harddisk2\DR2 during a paging operation."" error.

The only error that I see in VBoxSVC.log file is ""Getting USB descriptor failed with error 31"". 

I have not attached the VBox.log file, as this error occurs without any guest instances running.",Hugh
14368,Connecting Kemper Profiling Amplifier To VM Aborts the VM,VirtualBox 5.0.0,Linux,2015-08-02T03:57:21Z,2015-09-21T15:11:23Z,2015-09-21T15:11:23Z,"Connecting Kemper Profiling Amplifier (KPA) [http://www.kemper-amps.com/] via USB to a virtual machine aborts the VM.

I have tried with both Linux and Windows guests. No problems when connecting KPA to Linux or Windows machine directly.

Nothing is written to VBox.log when KPA is connected to VM. The VM just shuts down and the state in VirtualBox GUI becomes ""Aborted"".

In the attached VBox.log you can see bootup of Kubuntu 14.04 VM. After the VM had booted up, I connected KPA to it (nothing written to VBox.log at this point).

In the lsusb-kpa.txt you can see the output of command lsusb -v -d 133e:0001",Janne Rönkkö
12708,USB-Dongle with Vendor-ID 0000 cannot be attached,VirtualBox 4.3.6,Windows,2014-02-16T22:59:27Z,2018-04-26T18:51:38Z,2018-04-26T18:51:38Z,"I have to connect a USB-Licence-Dongle with Vendor-ID 0000 and Product-ID 9999 to a virtual machine (Windows 7/64 Professional).

This fails with:

{{{
Assertion failed: [mData.vendorId] at 'D:\tinderbox\win-4.3\src\VBox\Main\src-client\USBDeviceImpl.cpp' (62) in long __cdecl OUSBDevice::init(struct IUSBDevice *).

Please contact the product vendor!.

Fehlercode:E_FAIL (0x80004005)
Komponente:OUSBDevice
Interface:IUSBDevice {f8967b0b-4483-400f-92b5-8b675d98a85b}
}}}

Having a look at this Code-Line shows
{{{
ComAssertRet(mData.vendorId, E_INVALIDARG);
}}}

It seems there is no reason for failing here besides the fact, that 0000 is not an allowed vendor-id. At least VMware Workstation 10 can handle this. Don't tell me to contact the Vendor, I have to work with what I get, and what I get has Vendor-ID 0000.
",RainerHohn
13946,Unable to Use USB devices on Virtual box,VirtualBox 4.3.24,Windows,2015-03-09T15:09:41Z,2015-12-22T15:33:02Z,2015-12-22T15:33:02Z,"We are using Virtual Box 4.3.24 and inside we are using Ubuntu 14.
and also in my Local machine windows 7 we are using McAfee DLP 9.3.

* we raised a ticket with McAfee regarding this and they are saying it must be a problem with virtual Box.

when we uninstall DLP USB works fine in Virtual box. ",sathi
13728,Win 7 Guest/Linux host - integrated webcam on Dell 5520 laptop - black display,VirtualBox 4.3.20,Linux,2015-01-03T07:18:04Z,2015-09-05T15:15:34Z,2015-09-05T15:15:34Z,"On a Dell 5520 laptop, Fedora 64 bit 21 host, Win 7 64 bit guest, the integrated webcam provides nothing but a black display on passthrough, but on direct connect, the video shows but very slow/choppy.

It works fine on host applications.

An external USB camera works fine passthrough on the same system.

Attached is log.",H0wdy
13578,Option to disable the USB device filters,VirtualBox 4.3.18,Linux,2014-10-31T12:18:10Z,2015-03-21T21:47:42Z,2015-03-21T21:47:42Z,To activate USB devices on the guest they must be either registered in the USB device filter list or the device must be manually activated in the guest. Probably there could also be an option that disables the USB device filters which would cause that all USB devices would automatically be avtivated on the guest.,Sworddragon
13877,USB microscope camera on windows guest : bandwidth error,VirtualBox 4.3.18,Linux,2015-02-21T16:22:03Z,2015-02-21T16:22:03Z,2015-02-21T16:22:03Z,"Guest : Windows XP
Host : Ubuntu 14.04 64 bits
VirtualBox 4.3.10 with extension and additions

I use a professionnal camera (Toupcam) on a microscope connected to USB port of the host. It works on the host.
On the windows guest, with a specific application (Toupview) the camera is detected but when I ask a preview I get an error : the USB bandwidth is not sufficient...
USB 2.0 is activated in VBox and other USB devices work.

An idea ? Thanks.",arverne73
13513,vBox USB redirection not working for remotefx redirected USB devices,VirtualBox 4.3.18,Windows,2014-10-14T22:35:19Z,2014-10-14T22:35:19Z,2014-10-14T22:35:19Z,"Environment:  VirtualBox on Windows 7 x64 (The Windows Host is actually a Guest on a Hyper-V, Server 2012 R2)

The Windows 7 is connected via Remote Desktop while being attached with some USB devices via RemoteFx USB redirection. VirtualBox is unable to detect these USBs, thus the Nested guests are not able to use USB attached to their Host. It is possible that VirtualBox could support such ""uncommon"" configuration? 

Blow shows a snapshot (devicemanager.jpg) from the ""Device Manager"" to illustrate the hardware topology while RemoteFx USB redirection is in effect.",ganboing
10958,Windows guest does not recognized Broadcom 5880 smart card reader,VirtualBox 4.2.0,Windows,2012-09-18T15:28:16Z,2017-12-12T06:27:22Z,2017-12-12T06:27:22Z,"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?
",armillz
10309,USB is busy with a previous request [E_INVALIDARG (0x80070057)],VirtualBox 4.1.8,Windows,2012-03-06T19:03:54Z,2017-03-08T09:03:23Z,2017-03-08T09:03:23Z,"Hi,
I still have problems with connecting my USB device on this Win7-64bit host to a WinXP SP3 guest in 4.1.8 with usb_extension 4.1.8 and guest additions 4.1.8.

Connecting some usb flash drives succeeds but connecting my USB-to-CAN - device from peak-systems ([http://goo.gl/MSxX1 more info]) is not working. In earlier versions I got a message when starting the guest like ""Virtualbox USB is installing..."" and after the next complete restart of my computer the device was working. But now I don't get the windows tray message ""Virtualbox USB is installing..."" and if I want to connect my usb device while vm is running I get the error

{{{
Das USB-Gerät VER1:PEAK    
VER2:02.8.01        
DAT :06.05.2004
TIME:09:35:37
                             ... [1C11] konnte nicht an die virtuelle Maschine Windows XP gebunden werden.

USB device 'VER1:PEAK    

VER2:02.8.01        

DAT :06.05.2004

TIME:09:35:37

                             ...' with UUID {2fb58d0c-81b4-4505-9984-a67bfc272a87} is busy with a previous request. Please try again later.

Fehlercode:E_INVALIDARG (0x80070057)
Komponente:HostUSBDevice
Interface:IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee:IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
}}}

USB-filters are set correctly, as already mentioned other usb mass storages are working. On my host this peak usb device is running with latest drivers and all seems to work.

I've been searching already for some hours in google and had a look at [https://www.virtualbox.org/ticket/3033 #3033] and [https://www.virtualbox.org/ticket/5343 #5343] and [https://forums.virtualbox.org/viewtopic.php?f=5&t=31926 Forums] but nothing solved it until now.

Is there a way to find a solution? I don't want to reinstall earlier versions...
Is there a problem to disconnect the device from host because it's busy?

Thanks for your help",Jacky Ryan
9786,USB devices freeze VM instances and VB main window under certain conditions,VirtualBox 4.1.4,Windows,2011-10-19T12:33:29Z,2019-06-28T19:44:54Z,2019-06-28T19:44:54Z,"In one certain instance I have found that any tested usb Headsets will freeze the VM and the VirtualBox windows. Since the latest upgrade when connecting a USB headset (I have tried 3), upon opening any program that would use the headset the VM will freeze. It will also make the main VirtualBox windw freeze to where you cannot shut down that VM or open new ones. I have tried with a soft phone, voice recognition and sound recorder. All produce the same effect.
1. open a Windows VM on a Windows host
2. attach a USB headset
3. start Windows sound recorder
next clicking on anything shaould freeze the VM indefinitely
This was tested with Win 7 Ult. X64 host and Win 7 Pro X64 guest",Mark S Klopf
10844,Failed to attach the USB device to virtual machine,VirtualBox 4.1.18,Windows,2012-08-21T03:59:31Z,2020-01-10T14:18:26Z,2020-01-10T14:18:26Z,"64bit Windows 7 host, various 32 and 64 bit Linux guest distributions, 4.1.18r78361 extensions package installed.

Cannot get USB device to be recognized by guest (check via lsusb). Sometimes, selecting the device in the Devices->USB Devices menu just has no effect (entry doesn't get checked), and sometimes I get the following:


Failed to attach the USB device Yubico Yubikey II [0224] to the virtual machine pws-deb6.

USB device 'Yubico Yubico Yubikey II' with UUID {3c66074d-0580-47fd-921e-81da094dd391} is busy with a previous request. Please try again later.

Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}
---

Notes:
- Other USB devices can be successfully attached.
- Playing with the USB filter settings has no effect.
- On another 64bit Windows 7 host, running the same versions of VirtualBox and guest, the same (physical) device is successfully passed through to the guest. (Unfortunately, I need this working on the machine that fails...).

Please advise.

P.S. The device vendor has offered to provide assistance, including device samples.",Rony Shapiro
7213,USB: failed to create a proxy device (VERR_OUT_OF_RESOURCES),VirtualBox 4.0.8,Mac OS X,2010-07-21T15:39:26Z,2021-10-20T16:37:24Z,2021-10-20T16:37:24Z,"I'm using vbox 3.2.6 on MacOS 10.6.4, trying to attach an Android phone in ""download"" mode, and I get:


00:08:37.463 USB: Failed to open device 'p=0x6601;v=0x04e8;s=0x0000004883dc07fe;l=0x26200000', plug-in creation failed with irc=0xe00002be.
00:08:37.463 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={6375231a-c17c-464b-92cb-ae9e128d71c3} aComponent={Console} aText={Failed to create a proxy device for the USB device. (Error: VERR_OUT_OF_RESOURCES)} aWarning=false, preserve=false


I get this for all 3 of my VMs: Ubuntu, WinXP & Win7

It's the first time I've tried this particular device, although I have successfully attached other USB devices to VMs, of course. I tried rebooting the Mac.
",Calum Mackay
9007,Captured/filtered USB devices are released and reacquired when guest reboots,VirtualBox 4.0.8,Linux,2011-06-01T13:34:26Z,2016-08-23T07:18:59Z,2016-08-23T07:18:59Z,"Hi,

Host: Xubuntu 9.10 x86, VirtualBox 4.0.8 (with PUEL extension pack).
Guest: Windows XP SP3

When the guest is rebooted, VirtualBox seems to free/release any filtered USB devices, then re-capture them. I think all filtered USB devices should remain filtered when the guest reboots.

This problem is most noticeable when using a USB floppy drive. Most(?) Linux distributions treat USB floppy drives as generic removable drives. So when you insert a disk, the kernel attempts to read the last sector and scans for partition tables. In combination with the default block device readahead of 256 blocks, that process can take 30 seconds or so. *Every time you insert a disk*. It's quite annoying. Floppy disks never have a partition table of course so the scan is pointless. Anyway...

To reproduce the problem:
 - Connect a USB floppy drive to your system.
 - Add the floppy drive to the USB Device Filters of a Windows guest VM.
 - Start the Windows VM. Insert a floppy disk. Notice the drive only spins for a short time. Because it is captured, the Linux host OS doesn't attempt to access it.
 - Reboot the guest OS.
 - Notice how when the guest reboots, the kernel creates a /dev/sdX block device and scans for partitions (taking about 30 seconds). Then the block device is removed when VirtualBox re-captures the device.

Other drives are probably affected similarly, so you get an unnecessary block device creation, partition scan and device removal whenever the guest is rebooted. (That takes less time than for USB floppy drives so will be less noticeable.)

",Donuts
8801,only printable Serial-Number allowed for the USB-filter,VirtualBox 4.0.6,Linux,2011-04-27T19:08:53Z,2017-09-08T12:43:16Z,2017-09-08T12:43:16Z,"Hi, when i want to make an permanent filter for an USB-Device, which has none-printable characters, the whole VM will crash at the next startup. The failure which is shown, said that in line X a wrong value has been readed. For a workaround, the serial-number could be deleted and the VM will start. The USB-device was an ST-Link from STMicroelectronics.",BjoernC
8473,Error opening current controlling terminal for the process,VirtualBox 4.0.4,Linux,2011-03-02T06:43:45Z,2018-11-22T09:51:57Z,2018-11-22T09:51:57Z,"Trying to install Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack I got an error popup saying

Failed to install the Extension Pack /export/harri/Oracle_VM_VirtualBox_Extension_Pack-4.0.4-70112.vbox-extpack.

The installer failed with exit code 127: Error creating textual authentication agent: Error opening current controlling terminal for the process (`/dev/tty'): No such device or address.

Details

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
ExtPackManager
Interface: 
IExtPackManager {2451b1ba-ab1c-42fb-b453-c58433bea8c7}


Of course I checked the access permissions to /dev/tty. Its readable and writable for everybody:

% ls -al /dev/tty
crw-rw-rw- 1 root root 5, 0 Mar  2 06:04 /dev/tty


Please note that running Virtualbox as root is not an option.
",Harri
6632,Virtualbox should warn if you aren't in vboxusers group,VirtualBox 3.1.6,other,2010-05-03T13:18:08Z,2010-07-30T14:38:55Z,2010-07-30T14:38:55Z,"The scenario I keep finding myself here is as follows.

I perform an iPhone upgrade, the first half of the upgrade works since I can see the iphone over usb since the permissions are correct since I'm in whatever group means camera's are viewable.

The second half of the upgrade fails because the iphone turns into a different USB device, Which I know longer have permissions for unless I'm in vboxusers.

Would be a lot less painful if virtualbox just warned you",John Ferlito
6645,"Option to configure USB devices out of the Devices->""USB Devices"" menu",VirtualBox 3.1.6,other,2010-05-05T08:02:42Z,2010-05-05T08:02:42Z,2010-05-05T08:02:42Z,"It would be useful to be able to prevent host USB devices from appearing in the menu shown in the host's window for the VM's screen when using Devices->""USB Devices"".

The big benefit would be when the host's keyboard and/or mouse is a USB device because attaching either of these to a VM stops them working on the host and (ironically) on the guest too.

For other USB devices the benefit would be tidiness and simplicity.  In the case of USB devices always used with a particular VM it could prevent operational mistakes.

This enhancement could be implementated in the configuration GUI in the USB->""USB Device Filters"" list.  At the moment (version 3.1.6) this list shows all the USB devices on the host and the checked ones are attached to the VM when the VM is started.  Deleting an item from this list has no effect.  Perhaps deleting a device from this list could stop that device appearing in the Devices->""USB Devices"" menu.",Charles
6500,Virtualbox BIOS should implement USB legancy support,VirtualBox 3.1.6,other,2010-04-07T00:08:05Z,2010-04-07T00:08:05Z,2010-04-07T00:08:05Z,"Hello,

I use a VM as a multi-seat solution (USB input devices on a second monitor). However, I noticed that USB HID devices are not supported before OS kernel takes place. In boot manager, the usb keyboard is useless. I guess this is related to legancy usb suport inside BIOS.

Maybe, this will help in a possible option to use the virtual keyboard as an USB key board.",Luiz Angelo Daros de Luca
6236,"USB device ""cannot start"" after installation",VirtualBox 3.1.4,Windows,2010-02-18T14:27:48Z,2017-03-31T14:31:13Z,2017-03-31T14:31:13Z,"Host:
  - Windows 7 Professional

Client:
  - Windows XP SP3 Professional

Synopsis: 

USB smart card reader (ACS ACR80) gets recognized in client, but when the driver installation finishes, Windows XP reports the following error:

""The device cannot start. (Code 10)""

I tried rebooting both host and client, then disabling EHCI (USB 2.0) but it made no difference.

In general, USB devices handling in VirtualBox is very tricky and far for perfect. I believe this aspect of the functionality requires far more attention in the future releases.

I like how elegant USB handling is in VMware Player, but I still prefer VirtualBox for many other reasons.
",Dragan Obrenovic
6465,Blackberry synchronization appears broken => Fixed in SVN,VirtualBox 3.1.4,Linux,2010-03-30T19:21:28Z,2017-02-26T04:17:27Z,2017-02-26T04:17:27Z,"Host Debian Lenny 64 bit, client Windows XP SP3.

Blackberry synchronization works fine in VB 3.0.2. Since then, I've tried VB versions 3.0.4, 3.0.6, 3.0.8, 3.1.2 and 3.1.4 and the Blackberry USB support fails in various ways, some quite comical, so I revert back to VB 3.0.2.",George R. Young
4656,USB device is busy with a previous request,VirtualBox 3.0.2,Windows,2009-07-30T12:38:29Z,2017-09-27T15:32:17Z,2017-09-27T15:32:17Z,"Windows XP host and Fedora 11 guest. After a crash while transferring a huge amount of files between the pen drive and the Fedora guest, the pen drive becomes unavailable. When clicking Devices -> USB Devices -> Device Name this message is shown:

""Failed to attach the USB device xxx to the virtual machine Fedora 11
USB device xxx with UUID yyy is busy with a previous request. Please try again later.

Details:

Result Code: 
E_INVALIDARG (0x80070057)
Component: 
HostUSBDevice
Interface: 
IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: 
IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}
""

Forum discussion topic:

http://forums.virtualbox.org/viewtopic.php?f=6&t=20744&start=0#p89540",Clodoaldo Pinto Neto
5587,"USB device is reported as ""unknown device"" in Windows Guest on Windows Host",VirtualBox 3.0.12,Windows,2009-11-29T03:15:16Z,2015-11-06T11:06:32Z,2015-11-06T11:06:32Z,"The problem appears related to the slash contained in the device serial number. My guess is that the conversion into a # brokens the guest address. 

Using ""VBoxManage.exe list usbhost"":
{{{
UUID:               d398cf2d-92ee-44bc-aa8e-6ccef37494eb[[BR]]
VendorId:           0x1781 (1781)
ProductId:          0x0c63 (0C63)
Revision:           2.0 (0200)
Manufacturer:       B.Sauter
Product:            OpenOCD Debugger
SerialNumber:       '''GNU/GPL2'''
Address:            {eb781aaf-9c70-4523-a5df-642a87eca567}\0000
Current State:      Busy
}}}
is reported at the guest as:
{{{
UUID:               fd66cabb-4b08-4a90-a877-468e438c50b4
VendorId:           0x1781 (1781)
ProductId:          0x0c63 (0C63)
Revision:           2.0 (0200)
Manufacturer:       B.Sauter
Product:            OpenOCD Debugger
SerialNumber:       GNU/GPL2
Address:            \?\usb#vid_80ee&pid_cafe'''#gnu#gpl2#'''{00873fdf-cafe-80ee-aa5e-00c04fb1720b}
Current State:      Captured
}}}
The guest os see the device as ""unknown device"" with PID and VID to 0. ",Egon
242,No image with USB 2.0 webcams,VirtualBox 2.2.2,other,2007-03-30T21:20:40Z,2015-01-07T00:16:31Z,2015-01-07T00:16:31Z,"I need to test streaming video products inside of the virtual machine.  After installing the drivers inside the virtual machine and opening Windows Movie Maker, AMCAP, or my own software the stream is just blank.  The drivers are found and installed properly and it is not a problem with the hardware.  No error is given but the stream from the device (webcam of sorts) is just a blank black feed.",PeterValentine
4057,ER: Simpler way of accessing Windows host printer from Ubuntu guest,VirtualBox 2.2.2,Windows,2009-05-20T08:47:09Z,2009-05-20T09:05:57Z,2009-05-20T09:05:57Z,"
I am a non-technical user of VirtualBox 2.2.2 so I can run Linux programs on a Ubuntu guest for purposes of writing third-party user guides in FrameMaker on Windows XP SP3. I would like to remain a non-technical user and therefore propose that Guest Additions for all guest OSes incorporates a virtual printer that can access one or more real network/local/usb/parallel/serial printers on the host OS.

This could be a configuration option in the xVM VirtualBox GUI that allows the user to map guest printers to real printers, however then may be attached to the host.

I am trying to access my Epson CX6900F on Windows XP SP3 from an Ubuntu 9.04 Jaunty Jackalope using CUPS and Samba but without success. (I told you I was non-technical.)

I have shared a folder on Windows to try and access it from Samba but although it scans for shared folders can't find it.  Same for shared printer with CUPS.",Hedley Finger
4003,"Impossible to hide USB devices, specifically the host system disk",VirtualBox 2.2.2,Linux,2009-05-12T18:22:19Z,2009-05-13T09:13:16Z,2009-05-13T09:13:16Z,"
My host system (Ubuntu Jaunty 9.04) boots from an external USB disk that is selectable in the USB selection menu as any other connected usb device.

If I click on it by mistake it happens that the system disk gets disconnected from the host and assigned to the guest, making the system instantly unstable and unusable, and corrupting every filesystem on it.

Since this situation is not really common I don't know if this possibility should be denied in a first place, but I think that at least there should be the possibility to hide or exclude specific USB devices from the selection menu.

Perhaps a feature like filters but whith a blacklist logic...",Mico
3422,USB Filter does not distinguish two or more identical USB devices,VirtualBox 2.1.4,Mac OS X,2009-02-23T11:00:50Z,2009-03-25T19:28:13Z,2009-03-25T19:28:13Z,"Actually I want to overcome the problem described in ticket #373. It is really problematic not able to enter backslash and other chars on a German keyboard layout.

I use the Microsoft Natural Ergonomic Keyboard 4000 with a Mac Mini. Host is Mac OS X Leopard. 

My idea was the following: I tried to use two identical USB keyboards. One should be connected to the host. The other should be connected to the guest. However, when I enter the USB filter dialog, the virtualbox lists two devices with identical name ""Microsoft Natural Ergonomic Keyboard 4000 [0173]"". I selected one of both to be used with the guest.

Then, I started the guest Windows XP. However, instead of connecting only one device of both to the guest, the virtualbox connects both USB devices (Not okay). It should be possible to distinguish between identical devices in case of multiplicity.


Then, I tried to use this with Windows Vista x64 as guest. Forget it, it starts to toggling and never starts up.

",Harald Stuebinger
1930,The ability to exclude selected USB devices in the setup.,VirtualBox 1.6.4,Linux,2008-08-09T13:06:43Z,2016-10-24T15:19:14Z,2016-10-24T15:19:14Z,"I have been using VirtualBox for a couple of months now. I have had a couple of occasions where I have attempted to mount a USB flash key by doing a right mouse click selection on the icon in the lower right side of the virtual machine screen, only to accidentally select my USB mouse. This resulted in the inability to use the mouse in either the host system or virtual machine causing me to have to dump out of the GUI with a <alt><ctrl><backspace>. (not good)

Could you please include a feature in the virtual machine setup where I can 'hide' certain devices from the icon right mouse click selection, so as to prevent the accidental selection of devices that are already available to the virtual machine, and to prevent what work out to be something that disables of the system.

If you have any questions on what I am talking about please feel free to email me.

Walt Williams
Boulder, Colorado, USA",Walt L. Williams
1347,"USB device reported working, but no communication",VirtualBox 1.5.6,other,2008-03-18T11:51:25Z,2018-07-16T19:04:50Z,2018-07-16T19:04:50Z,"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 VirtualBox. 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 VirtualBox 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. ",Elod 
16707,Add port #'s to USB Filters,,all,2017-04-27T13:10:48Z,2020-07-10T22:01:34Z,2020-07-10T22:01:34Z,"The ""port"" space of the USB filter is not showing anything, making usage of USB devices with same vendorid, productid, and revision numbers, etc. difficult to sort and use.

If multiple USB devices containing different data but having identical Virtualbox USB filter information need to be reliably distributed to specific guests, the VB USB filter can't distinguish which USB device to use and sends all of them into the first guest available. Inserting another dongle into the host immediately sends the new dongle into the first guest, requiring further finagling to get the dongle into the next desired guest. Or if by chance the second guest was started first, it would not be known which of the dongles was in the guest, if not all of them at once. In either case further manual manipulation is needed after the guests are started to figure out which donlge to put in which guest.

If the port space showed which USB port the desired device was plugged into, and was filterable, then as long as the device is continually used in the same port, the VB USB filter will be able to distinguish them and filter them into the desired guests automatically.

A company called KernelPro (http://www.kernelpro.com/usb-over-ethernet.html) has a USB-over-ethernet server program that casn differentiate USB devices with the same vendorid, productid, revision, etc. by the port number the USB device is plugged into. Please see the attached screenshot. I have five license dongles attached to this USBoE server. Notice that four of the five have the same vendorid, productid, and revision numbers, even though they contain different license data in each dongle, so they are not swappable. The server can distinguish them and send them reliably, because it keeps track by port number.
",scottgus1bug
18040,Failing to attach USB device,,Windows,2018-10-09T15:53:07Z,2018-10-25T10:01:59Z,2018-10-25T10:01:59Z,"Not able to attach a USB device to VM with USB over Ethernet Connector ([https://www.eltima.com/products/usb-over-ethernet/]) installed on the host.

Virtualbox is the latest version.

Host and guest are both Win7 64-bit.

If I uninstall USB redirection software from the host, then everything works fine.

Attached a screenshot of the error message.",redhotchili
