USB in virtualbox[SOLVED]

I am trying to figure out how to use usb in vbox. I added the filters, but when I go to mount the flash drive in the bottom right corner of the guest OS window, all the usb devices are greyed out. Using vbox 1.6.2. What am I doing wrong?
Last edited by Raccoon1400 (2008-06-17 00:55:02)

[duncan@duncan-arch ~]$ cat /proc/bus/usb/devices
T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 8
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 2.06
S: Manufacturer=Linux 2.6.25-ARCH ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1d.7
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms
T: Bus=05 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 4 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0781 ProdID=5406 Rev= 2.00
S: Manufacturer=SanDisk
S: Product=U3 Cruzer Micro
S: SerialNumber=3512300802818E95
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=200mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=81(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 11/900 us ( 1%), #Int= 1, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 2.06
S: Manufacturer=Linux 2.6.25-ARCH uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.3
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=045e ProdID=0047 Rev= 3.00
S: Manufacturer=Microsoft
S: Product=Microsoft 5-Button Mouse with IntelliEye(TM)
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=10ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 2.06
S: Manufacturer=Linux 2.6.25-ARCH uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0557 ProdID=2006 Rev= 2.02
S: Manufacturer=ATEN UC-1284B
S: Product=ATEN UC-1284B Printer Cable
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=07(print) Sub=01 Prot=01 Driver=usblp
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 0 Alt= 1 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I: If#= 0 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=usblp
E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 4 Ivl=1ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 2.06
S: Manufacturer=Linux 2.6.25-ARCH uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0001 Rev= 2.06
S: Manufacturer=Linux 2.6.25-ARCH uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
[duncan@duncan-arch ~]$
and
[duncan@duncan-arch ~]$ ls -l /proc/bus/usb/001/007
ls: cannot access /proc/bus/usb/001/007: No such file or directory
[duncan@duncan-arch ~]$

Similar Messages

Airport Extreme will not show USB drive installed Solved!

Airport Extreme will not show USB drive installed Solved... At least for me!
Here's what I had to do to make it work with the newest 7.3.1 firmware.
Ready for this? No Joke Really!
1. Connect your USB drive to the Airport Extreme.
2. Turn it on.
3. Open the Airport Utility.
4. Go to Manual Setup.
5. Choose Disks and File Sharing.
Yep, we are going to set file sharing before we even see the disk we want to share!
You (I) had to set File Sharing on and Share Disks over Ethernet checked as well as set the Work Group (In my case). THEN restart the Airport Extreme.
After it re-started... My USB Drive was now present and ready for use.
I also dis-allowed Guest access. I re-started ALL computers in my network, both Windows and MAC. The USB drive held and works GREAT!
I know... Most of you thought this was a joke, It's not!
I tried everything to get the USB drive to work and failed every time just like most other people. Doing it this way worked like a charm.
Go Figure huh!
Hope this helps someone with this issue.
Message was edited by: DonaldH

How was the usb hard drive formatted? Was it NTFS, FAT32, or HFS+?

[SOLVED] USB on VirtualBox guest (windows 7)

hey,
- installed win7 inside vbox
- installed vbox guest additions
- installed vbox extension pack (via aur)
- i am in vboxusers group
- relogged
i plug in usb thumb drive, but usb icon in bottom left is still gray - i right click it and see that the device (verbatim clip) is listed and unchecked. if i left click it, i have a checkmark, i see windows is searching for drivers but it gives an error. thumb drive is not listed in removable devices nor my computer.
- i add a line from troubleshooting wiki in /etc/fstab
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=664 0 0
- i also added a line in .bashrc
VBOX_USB=usbfs
- rebooted, still nothing
ideas?
Last edited by developej (2013-01-13 10:33:48)

That fstab line is an old workaround, that's probably not good anymore. And the ~/.bashrc line... I have no idea what it's supposed to do.
Are you in the storage group?
Did you enable USB 2.0 from VirtualBox's settings screen?
You need to plug in the USB stick and also "plug" it in the VM. Windows asking for USB drivers is a bit odd (especially Windows 7, which takes up a heck of a lot more than Windows XP).
Last edited by DSpider (2013-01-13 09:47:55)

Usb broken in virtualbox [SOLVED](finally)

I installed virtualbox from the .bin file on the virtualbox site.
After the last kernel update, the vbox kernel module broke, so I reinstalled. This didn't fix it, so I got rid of the vbox files in opt, and reinstalled. I did save the old files.
Now, usb doesn't work. If i try to mount devices, I can see them in the menu, but they are greyed out.
Last edited by Raccoon1400 (2009-09-13 17:39:34)

ise wrote:Have you done the necessary changes to your /etc/fstab? According to this wiki article: http://wiki.archlinux.org/index.php/Vir … st_machine
I did that a long time ago.
It worked until this recent event described in the 1st post. It may also be something with the new kernel.

WRT600N USB Storage Problems Solved

For a couple of years, I've been living with all the problems others have reported with the WRT600N USB storage - lost connections, permissions problems, rebooting the router to recover access to the USB drive, etc. I solved my problems, mostly, by switching to a DLink DIR-655 router. I assume other routers in the Dlink family that support USB devices will perform similarly.
My main problem seemed to be interference from the microwave, which is in an open kitchen/keeping room arrangement in my house. However, the bottom line is that any time I lost wireless connectivity to the router, due to the microwave or unknown causes, I'd lose access to the USB drive. This meant a trip upstairs to power cycle the router and the USB drive several times a day.
With the Dlink, I still sometimes lose wireless connectivity due to the microwave or unknown causes, but not as often. Sometimes, but not always, this will cause me to lose the USB drive access. If I do need to reboot the router, I can do so from the web based interface, something that was not possible with the WRT600N, so no more trips upstairs to perform this operation. I also find have a stronger wireless signal in my work location with the Dlink.
Dlink uses a SharePort software utility to manage the USB connection and this has to be installed on all PC's that want access to the USB device. SharePort makes a USB device appear to be a local device attached directly to the computer you're using and you can attach external drives/printers/probably USB hubs. (I've experimented only with an external USB drive.) Because of this, however, only one computer can attach to the USB device at a time - not a problem for me, but you need to be aware. The software has a mechanism for requesting access to the USB device from one computer, when the device is in use by another computers. You can also set it to automatically connect to the USB device if its available, to try a reconnect if connection is lost, and to automatically run a program when the USB device connects. Dlink says SharePort will support FAT or NTFS formatted drives and there's no known limitation on the drive size.
Dlink support doesn't seem much better than here - it took about three weeks for me to get an answer on the external drive size and formatting options. There are plenty of complaints on the Dlink support site about poor support, poor performance of SharePort, etc. So, all I can say is their router/USB device sharing has worked much better for me than my Linksys WRT600N ever worked.

Welcome to the WRT600N nightmare. The Storage Link is poorly documented, and the firmware controlling it has issues. Basically, it will corrupt file date/times stamps whenever you copy files onto the attached drive. It has also been known to be a bit flaky about maintaining the drive as a connected/mapped drive. Backup programs may have difficulty accessing the drive via Storage Link. Depending on the file format you use, you may encounter file size limitations on the Storage Link drive.
I, personally, gave up after a few days of these issues mentioned above and bought extra USB hard drives for each computer in the house rather than try and use the Storage Link as a NAS.
What O/S are you using on your computer? I can try and walk you through the setup.
A+ Certified, over 15 years of hands on computer and home networking experience...and I still get lost!

USB in VirtualBox

I know this has been covered many times and I found a few threads on it but they all pretty old and no longer apply since things have changed since the switch to Systemd. The solution in the wiki (adding VBOX_USB=usbfs to .bashrc) doesn't seem to work (yes I started a new bash session) and my user is a member of the vboxdrv group, it won't work with the root account either. The kernel module is also loaded.
Here's the exact error:
Failed to access the USB subsystem.
VERR_NOT_FOUND
Result Code: NS_ERROR_FAILURE (0x00004005)
Component: Host
Interface: IHost {30678943-32df-4830-b413-931b25ac86a0}
Callee: IMachine {22781af3-1c96-4126-9edf-67a020e0e858}
I get that whenever I doubleclick on the Network section.
Last edited by brando56894 (2013-04-19 19:21:37)

This has been covered, many, many, many times on this forum.
Uninstall VirtualBox, reboot, reinstall it according to the wiki, and reboot. Use 'makepkg -s' to compile the extension pack; don't use some kind of AUR helper.
https://wiki.archlinux.org/index.php/VirtualBox
https://wiki.archlinux.org/index.php/AU … g_packages
And remove that stuff from ~/.bashrc. You don't need it. Nobody ever needed it. I don't even know why it's in the wiki...
Are you in the "storage" group? Post the output of:
$ groups your_username
Also, double click the Network section? ... ? Wut? There is no such thing in VirtualBox.

Can't mount USB in VirtualBox anymore

Hi,
I'm using VirtualBox for a very long time and never had any problems.
But today I wanted to mount my USB flash drive as I always do but I receive an error message:
Not permitted to open the USB device, check usbfs options.
Fehlercode:
NS_ERROR_FAILURE (0x80004005)
Komponente:
Console
Interface:
IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}
$ cat /etc/fstab | grep usbfs
none /proc/bus/usb usbfs auto,busgid=108,busmode=0775,devgid=108,devmode=0664 0 0
$ cat /etc/group | grep vboxusers
vboxusers:x:108:thomas,hiwi
Any idea what's going wrong? I'm not sure if there was an update of virtualbox_bin since the last time I used it.

Thanks, I'm entered this to the discussion page of the VirtualBox article in the wiki.
The wiki also says that an entry in the fstab isn't necessary anymore.
Last edited by Barghest (2009-10-20 07:03:14)

Premier elements 10 can't find a burner when using Windows 8.1 Would using a USB disc burner solve the problem?

Using Premier Elements10 with Windows8.1, the program cannot detect a burner. I understand that Windows8 designates the burner as a DVD in order to facilitate drag and drop. I don't want to get too technical and want to know if purchasing an external USB disc burner will solve the problem. Will premier elements be able to detect this burner OK. I don't want to spend the money unless I am fairly certain that it will work.

marion567
There is no guarantee that you will not get a blank field for Premiere Elements Burner Location using any internal or external Blu-ray DVD CD burner or DVD CD burner.
If you go with an USB external burner, just make sure you have the back up of return/money back from the seller.
If you are dealing with just a DVD CD burner, you might try the following if you have not already
http://helpx.adobe.com/creative-suite/kb/cd-dvd-drive-recognized-application.html
You might also want to consider an uninstall/reinstall of Premiere Elements 10 on Windows 8.1 64 bit following the scheme of
a. uninstall the usual Control Panel route
b. free ccleaner run through CCleaner - Download
c. reinstall with antivirus and firewall(s) disabled
The following is the Adobe document that goes to Supported Devices
http://helpx.adobe.com/premiere-elements/kb/supported-devices-premiere-elements.html
Updating on that unknown. Right now, it is what it is. I have burners that work fine in Premiere Elements on
Windows 7 and 8.1 64 bit and they are not on the list.
Please let us know if any questions on the above or need clarification.
Thank you.
ATR

Freenas under Virtualbox [SOLVED]

Hi,
I am trying out Freenas under virtualbox, I am looking to run server under virutal machine wondered if I can test it via my browser on same machine or one on my local network?
SOLVED http://mychael.gotdns.com/blog/2007/05/ … -bridging/
Working fine I can access virtual server via host machine :-)
MrG
Last edited by Mr Green (2008-04-29 10:55:59)

If I leave it as "ro" the filesystem stays as readonly and I can see the following before the login prompt:
mount: can't find / in /etc/fstab or /etc/mtab
and then
kinit: mounted root (xfs filesystem) readonly
fstab has no reference to any sda.
Last edited by DrZaius (2008-01-02 19:53:04)

975x Platinium Power Up- Hangs with USB Flash memory- SOLVED!

Hello.
My System is:
975x Platinium Power Up
E6300
2 SATA RAID 0, 1 IDE
MSI 7900Gs
2GB Gskill
Windows XP service pack 2 with all updates
The problem that I have is when I put a Flashh Memory on any USB drive, my computer hangs. I thought that was a windows problem and I format and reinstall all again 2 times! and I have the same problem again and again (Also I tried with Windows XP and with Windows Home edition and I have the same problem with both). Also I tried another Flash memory (the first one was Dane and the second was Transcend and with both memories my computer hang). Next I tried with my USB digitall camera and also hang...... I have a mouse (genius) in one of the USB drives but works fine.
I have the last official bios 7.1. Could be a BIOS problem? becasue I remember that when I had 7.0 I didnt have this problem.
Please help me.

Quote from: NovJoe on 06-October-06, 14:17:47
I remember alot of chassis usb has this pin 9 W& 10 problem with the GND.
You may want to check out the Good Articles Section for the solution to it.
GOOD! NovJoe you gave me part of the solution!!!, thanks!. The 975 Platinium Power up have a similar problem of old msi motherboards:
This is the USB pins of the USB 975 Platinium Power Up, take attention on pin 10!!! (in 9 dont have pin):
Now see the usb cable connectors that came with the motherboard:
The original usb cable connector dont use pin 10!!!!!! (also dont use 9 but the motherboard dont have any pin on 9)
If your usb chassis cable have a wire on pin 10 MAY BE ALL THE USB PORTS ON THE MOTHERBOARD WILL NOT WORK OR SOMETIMES WILL HAVE PROBLEMS!! (RANDOM PROBLEMS). The usb chassis pin 10 could be ground or Shield and muts be cut.
I dont know why engineers of MSI put a pin on 10 if it must not be use it! A lot of chassis have wires on pin 10, engineers should take off that pin like they did with pin 9 to solve a lot of future problems.
Finally problem SOLVED!

URB Flag warnings in log when using USB with VirtualBox

Hi,
I have a VirtualBox VM and an external hard drive which is directly connected to this VM. VirtualBox extension pack is installed and USB2.0 (EHCI) Controller is enabled for this machine.
When I now copy files onto this hard drive (inside the VM) I get millions of the following warnings in my journalctl of the host computer:
Aug 21 08:42:07 jasonsOffice kernel: WARNING: CPU: 0 PID: 1837 at drivers/usb/core/urb.c:476 usb_submit_urb+0x2f0/0x600 [usbcore]()
Aug 21 08:42:07 jasonsOffice kernel: usb 4-2: BOGUS urb flags, 1 --> 0
Aug 21 08:42:07 jasonsOffice kernel: Modules linked in: fuse cfg80211 rfkill mousedev evdev mac_hid kvm_amd edac_core kvm serio_raw snd_hda_codec_hdmi k10temp edac_mce_amd microcode snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep radeon snd_pcm ttm drm_kms_helper drm sp5100_tco hwmon i2c_algo_bit i2c_piix4 snd_timer i2c_core r8169 mii snd soundcore wmi shpchp button acpi_cpufreq processor pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) nfs lockd fscache sunrpc ext4 crc16 mbcache jbd2 hid_generic usbhid hid sd_mod sr_mod cdrom crc_t10dif crct10dif_common ata_generic pata_acpi uas usb_storage atkbd libps2 pata_jmicron firewire_ohci firewire_core crc_itu_t pata_atiixp ahci libahci ehci_pci ohci_pci ohci_hcd ehci_hcd xhci_hcd libata scsi_mod usbcore usb_common i8042
Aug 21 08:42:07 jasonsOffice kernel: serio
Aug 21 08:42:07 jasonsOffice kernel: CPU: 0 PID: 1837 Comm: USBDevIo--1 Tainted: G W O 3.16.1-1-ARCH #1
Aug 21 08:42:07 jasonsOffice kernel: Hardware name: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H/GA-880GMA-UD2H, BIOS F5 09/30/2010
Aug 21 08:42:07 jasonsOffice kernel: 0000000000000000 00000000bb1ed052 ffff88017fc43c98 ffffffff8152ae6c
Aug 21 08:42:07 jasonsOffice kernel: ffff88017fc43ce0 ffff88017fc43cd0 ffffffff8106e45d ffff88021f4b4cc0
Aug 21 08:42:07 jasonsOffice kernel: 0000000000000020 0000000000000002 ffff880217031800 0000000000000001
Aug 21 08:42:07 jasonsOffice kernel: Call Trace:
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff8152ae6c>] dump_stack+0x4d/0x6f
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff8106e45d>] warn_slowpath_common+0x7d/0xa0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff8106e4dc>] warn_slowpath_fmt+0x5c/0x80
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffffa005fdd0>] usb_submit_urb+0x2f0/0x600 [usbcore]
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffffa006c248>] proc_do_submiturb+0xcb8/0xd00 [usbcore]
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffffa006c8ff>] usbdev_do_ioctl+0x59f/0x11b0 [usbcore]
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff811c173b>] ? new_sync_read+0x8b/0xd0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffffa006d53e>] usbdev_ioctl+0xe/0x20 [usbcore]
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff811d4a70>] do_vfs_ioctl+0x2d0/0x4b0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff811df18e>] ? __fget+0x6e/0xb0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff811d4cd1>] SyS_ioctl+0x81/0xa0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff81530be9>] system_call_fastpath+0x16/0x1b
Aug 21 08:42:07 jasonsOffice kernel: ---[ end trace 6fbdb725227065ca ]---
The write process seemed to work, but the warnings don't look good to me. What do you think? Can I ignore these warnings? If yes, can I disable them?
I already found some other threads out there, talking about a similar problem, but in all cases, the USB devices did not work inside the virtual machine.
(Yes, my system is up-to-date.)

Hi,
I have a VirtualBox VM and an external hard drive which is directly connected to this VM. VirtualBox extension pack is installed and USB2.0 (EHCI) Controller is enabled for this machine.
When I now copy files onto this hard drive (inside the VM) I get millions of the following warnings in my journalctl of the host computer:
Aug 21 08:42:07 jasonsOffice kernel: WARNING: CPU: 0 PID: 1837 at drivers/usb/core/urb.c:476 usb_submit_urb+0x2f0/0x600 [usbcore]()
Aug 21 08:42:07 jasonsOffice kernel: usb 4-2: BOGUS urb flags, 1 --> 0
Aug 21 08:42:07 jasonsOffice kernel: Modules linked in: fuse cfg80211 rfkill mousedev evdev mac_hid kvm_amd edac_core kvm serio_raw snd_hda_codec_hdmi k10temp edac_mce_amd microcode snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep radeon snd_pcm ttm drm_kms_helper drm sp5100_tco hwmon i2c_algo_bit i2c_piix4 snd_timer i2c_core r8169 mii snd soundcore wmi shpchp button acpi_cpufreq processor pci_stub vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) nfs lockd fscache sunrpc ext4 crc16 mbcache jbd2 hid_generic usbhid hid sd_mod sr_mod cdrom crc_t10dif crct10dif_common ata_generic pata_acpi uas usb_storage atkbd libps2 pata_jmicron firewire_ohci firewire_core crc_itu_t pata_atiixp ahci libahci ehci_pci ohci_pci ohci_hcd ehci_hcd xhci_hcd libata scsi_mod usbcore usb_common i8042
Aug 21 08:42:07 jasonsOffice kernel: serio
Aug 21 08:42:07 jasonsOffice kernel: CPU: 0 PID: 1837 Comm: USBDevIo--1 Tainted: G W O 3.16.1-1-ARCH #1
Aug 21 08:42:07 jasonsOffice kernel: Hardware name: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H/GA-880GMA-UD2H, BIOS F5 09/30/2010
Aug 21 08:42:07 jasonsOffice kernel: 0000000000000000 00000000bb1ed052 ffff88017fc43c98 ffffffff8152ae6c
Aug 21 08:42:07 jasonsOffice kernel: ffff88017fc43ce0 ffff88017fc43cd0 ffffffff8106e45d ffff88021f4b4cc0
Aug 21 08:42:07 jasonsOffice kernel: 0000000000000020 0000000000000002 ffff880217031800 0000000000000001
Aug 21 08:42:07 jasonsOffice kernel: Call Trace:
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff8152ae6c>] dump_stack+0x4d/0x6f
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff8106e45d>] warn_slowpath_common+0x7d/0xa0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff8106e4dc>] warn_slowpath_fmt+0x5c/0x80
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffffa005fdd0>] usb_submit_urb+0x2f0/0x600 [usbcore]
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffffa006c248>] proc_do_submiturb+0xcb8/0xd00 [usbcore]
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffffa006c8ff>] usbdev_do_ioctl+0x59f/0x11b0 [usbcore]
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff811c173b>] ? new_sync_read+0x8b/0xd0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffffa006d53e>] usbdev_ioctl+0xe/0x20 [usbcore]
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff811d4a70>] do_vfs_ioctl+0x2d0/0x4b0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff811df18e>] ? __fget+0x6e/0xb0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff811d4cd1>] SyS_ioctl+0x81/0xa0
Aug 21 08:42:07 jasonsOffice kernel: [<ffffffff81530be9>] system_call_fastpath+0x16/0x1b
Aug 21 08:42:07 jasonsOffice kernel: ---[ end trace 6fbdb725227065ca ]---
The write process seemed to work, but the warnings don't look good to me. What do you think? Can I ignore these warnings? If yes, can I disable them?
I already found some other threads out there, talking about a similar problem, but in all cases, the USB devices did not work inside the virtual machine.
(Yes, my system is up-to-date.)

Usb Hd problems [SOLVED!]

Hi guys,
I'm trying to leave the n00b status behind, and switch my distro from Ubuntu to Arch recently. I really love this distro, but the things are quite hard here. Right now I'm trying to mount a external/USB hd without sucess. This HD is working, I test it at my university, in a Debian machine.
I try a pen drive at the same usb port and it mount without problem.
Any help or advice will be appreciated. Some code follows:
lsusb before plug it:
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0002
lsusb after plug it:
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 012: ID 13fd:160e
Bus 001 Device 001: ID 1d6b:0002
He dont appears in fdisk -l (it has 160GB):
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0xbd6ecc2a
Dispositivo Boot Start End Blocks Id System
/dev/sda1 * 1 3315 26627706 7 HPFS ou NTFS
/dev/sda2 3316 4774 11719417+ 83 Linux
/dev/sda3 9667 9729 506047+ 82 Linux swap / Solaris
/dev/sda4 4775 9666 39294990 83 Linux
Partições lógicas fora da ordem do disco
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0xcef9c4c5
Dispositivo Boot Start End Blocks Id System
/dev/sdb1 1 60801 488384001 7 HPFS ou NTFS
Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cilindros of 16065 * 512 = 8225280 bytes
Disk identifier: 0x09820982
Dispositivo Boot Start End Blocks Id System
/dev/sdc1 1 9728 78140128+ 7 HPFS ou NTFS
dmseg last 3 after plug the HD lines:
hub 1-0:1.0: unable to enumerate USB device on port 5
usb 1-5: new high speed USB device using ehci_hcd and address 12
usb 1-5: configuration #1 chosen from 1 choice
my rc.conf, (only hardware and daemons part):
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(forcedeth mii slhc via-rhine snd-mixer-oss snd-pcm-oss snd-hwdep snd-pa
ge-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
#MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng @network netfs crond alsa hal fam gdm)
Last edited by Gralha (2008-09-20 04:34:14)

Guys forget about it!
I boot my machine and try to mount in Windows. And the HD does not mount!!!
So I remember that once I have a problem with "low voltage" usb ports with a cellphone. Once this HD does not have a power supply I try the back USB port and... IT WORKS!

Is it possible to wait longer for USB with mkinitcpio-solved

Hi,
I recently installed from an arch0.7.2-base CD, but can't boot after the mkiniticpio upgrade, including with the kernel26-fallback.img.
My root partiition is on a USB hard-drive, and it seems like the drive isn't being detected in time.
With mkinitrd I could specify a delay to wait for USB devices to settle, but there doesn't appear to be anything similar in mkinitcpio, is there?
This may not be the problem at all, of course, but on one occasion when I booted with break=y, just after the message about break requested, there is no ls binary etc.,
usb2-4: new fullspeed USB device using OHCI_HCD address 2
came up, which looked like it had found the USB device, but too late.
(This is after it says it failed to detect the filesytem type etc.)
When I do break=y and echo /dev/*, my hda devices are there, but there are no sda devices, just a series of usbdev files (e.g. usbdev1.1_ep00 ). Is that normal?
Sorry for posting yet another mkinitcpio question.
Any suggestions would be greatly appreciated. Let me know if there's any other output I should post.
Thanks,
Fishonadish

Update:
I'm fairly certain the lack of wait time for USB is the problem now.
I can now boot into arch fine provided I use break=y.
I get the messages about about not finding the root device then the break requested section then, after the ramfs$ prompt appears I get
SCSI device sda: [number] 512-byte hdwr sectors [number] MB
and so on...
and when I type exit at the prompt it boots fine.
To get this far I rebuilt the kernel26.img with the following in mkinitcpio.conf:
MODULES="usb-storage ext3"
HOOKS="base udev autodetect usb filesystems"
(Not sure about this, but it seems putting usb-storage in modules got me this far?)
I still need to get it to delay for USB for a bit longer so I don't have to type 'exit' at the ramfs prompt every time I want to boot, or is it some other problem?
If this has been dealt with before, then sorry for the repetition, but I can't find anything covering it elsewhere.
Thanks.
Fishonadish

Wich file system is recomended for an usb key? [SOLVED]

Hi. I have an 8Gb USB Stick (USB key or pendrive).
I will use it to store my backups and ocassionaly to move some files between PCs. I don't use windows so i don't need niether want compatibility, so i don't want to use FAT32.
So, wich file system is recomended to use on an usb key??
Should i use ext3, reiserfs, xfs, jfs??? or maybe ext4???
Has any of them any implication with the lifetime of the usb?
Thanks
Last edited by Thalskarth (2009-02-12 03:05:33)

BoppreH wrote:Isn't there any chance that you might need to stick it at a Windows based computer?
I use it for backups, so i wont need it. i have another one much smaller for that cases
Xyne wrote:Wouldn't a journalling filesystem reduce the lifetime of the USB stick?
Wintervenom wrote:Go with ext2. You generally do not want a journaled filesystem on a Flash device. It may cut the device's lifespan by up to fifty percent or more.
I was afraid of something like that... thanks for the advice
so, ext2 would be the best option, wouldn't it?
Thanks to all for your help

Libusb requires write access to USB device nodes [SOLVED]

Hi,
I have used gtkam to upload photos from my camera for some time now - though on an occasional basis because I don't take very many photographs. On attempting to use it today for the first time in a while I find that I can't do so as a user.
"libusb couldn't open USB device /dev/bus/usb/003/002: Permission denied.
libusb requires write access to USB device nodes."
Can anyone tell me how to fix this please?
Last edited by perseus (2011-01-03 22:46:46)

I did some additional research and found the udev file for libgphoto2: /lib/udev/rules.d/40-gphoto.rules
I also realized that my camera is not listed in that file:
Bus 001 Device 011: ID 04a9:31f6 Canon, Inc.
I tried to add this device and vendor ID to the list of Canon cameras and restarting udev
ATTRS{idVendor}=="04a9", ATTRS{idProduct}=="31f6", ENV{ID_GPHOTO2}="1", ENV{GPHOTO2_DRIVER}="proprietary", MODE="0660", GROUP="camera"
# killall udevd && udevd -d
Unfortunately this didn't work out.
I also tried to add the following line to that gphoto udev file as suggested by Digital Cameras wiki
PROGRAM="/lib/udev/check-ptp-camera", MODE="0660", GROUP="camera"
Still nothing after restarting udev...
My next try was adding the camera to the HAL fdi file /usr/share/hal/fdi/information/20thirdparty/10-camera-libgphoto2.fdi and restarting HAL.
This didn't help either.
I'm getting short on clues...
For sure I can access the camera as root but that's not what I want to do.
!! UPDATE !!
I was dumb. PTP cameras are handled separately so I don't need to have the USB IDs in the udev or fdi files.
So the question is why PTP cameras are not handled correctly, why the group for these devices is not "camera"?
Last edited by KoS (2011-01-03 22:19:57)

USB in virtualbox[SOLVED]

Similar Messages

Maybe you are looking for