Windows XP VM Guest into Host hardware USB 3.0

[PaulReis]

Hello Team

Please, I have one laptop hardware that only support current USB 3.0. The VM guest is a Windows XP SP3 OS. I need to attach the USB-to-Serial cable (this is USB 2.0 device by the way) into virtual XP. With the USB 2.0 EHCI controller enabled, when I request to Attach it by going into DEVICE menu, the following error pops up. What do you suggest to resolve, please?

"Failed to attach the USB device Prolific Technology Inc. USB-Serial Controller [0300] to the virtual machine Teste.

USB device 'Prolific Technology Inc. USB-Serial Controller' with UUID {00484bc3-6cac-4c6c-a97b-77ad9ffed8c7}
is busy with a previous request. Please try again later.

Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDeviceWrap
Interface: IHostUSBDevice {c19073dd-cc7b-431b-98b2-951fda8eab89}
Callee: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}"

Thanks in advanced for your help!
Paulo Reis

[socratis]

Follow the steps below. If there is a failure, please state which step failed:

1. Make sure that the Extension Pack is installed on the host. The same version as VirtualBox.
2. Make sure that at least USB 2.0 is enabled in your VM settings.
3. Create a USB filter in your guest settings while the device is plugged in the host. Delete all values except Name, VendorID and ProductID.
4. Unplug the device.
5. Start your guest (the one that you applied the filter to). Let it start completely. Log in if you have to.
6. Plug your device. The filter should capture it and pass control to your guest. You might get a "New hardware found" wizard on the guest, that's normal.
7. If the device shows up in your host and is not captured by the filter, either the filter is incorrect, or there might be a problem with your filter installation.
8. If the device shows up, but as unavailable, "eject" it from your host (if you can), but leave it plugged in. It should show up as available.
9. With the USB device plugged in and the VM not running, post the output of the following commands:

       VBoxManage list usbhost
       VBoxManage showvminfo "Your_Virtual_Machine_Name"

[michaln]

Please, I have one laptop hardware that only support current USB 3.0.

If you do, you need to take it back. It is infinitely more likely that your laptop supports both USB 3.0 and USB 2.0 (the latter encompasses all previous standards).

Other than that... what socratis said.

[PaulReis]

If the device shows up, but as unavailable, "eject" it from your host (if you can), but leave it plugged in. It should show up as available.

Hi Soctatis,

I have followed all steps where bring me to the step 8 above: I can see the device in the host however I cannot eject it due to its particularity. Also this USB-to-Serial cable has a driver to be installed from a disk. I have tried by removing the driver and leave it as unknown device in the host, therefore created again the filter following your instructions. Same error from the beginning pops up.

About the Vbox command I'm afraid that this resource only works for Linux host, is that correct? My host is a Windows 7 professional 64 bit OS

Again, thanks for your support.

[PaulReis]

Please, I have one laptop hardware that only support current USB 3.0.

If you do, you need to take it back. It is infinitely more likely that your laptop supports both USB 3.0 and USB 2.0 (the latter encompasses all previous standards).

Other than that... what socratis said.

Hello Mike,

Yes, I've noted that because the affected Dell's laptop comes with USB 3.0 only. I saw from others forum around -about guest VM machines problems with USB-to-serial.
From one forum I see a resolution by going to the laptop BIOS setup therefore select only USB 2.0 as a host. Where is not the case from my Dell's laptop. I agree that USB 3.0 should encompasses all previous versions.

Thanks

[michaln]

Yes, I've noted that because the affected Dell's laptop comes with USB 3.0 only.

Do you have some official Dell reference?

I don't believe it's true because if it was, you could not connect any USB mouse or keyboard, or really most USB devices.

I agree that USB 3.0 should encompasses all previous versions.

It doesn't, and that's not what I said (I hope). USB 2.0 and USB 3.0 are separate standards. USB 2.0 supersedes USB 1.x, but USB 3.0 does not supersede USB 2.0.

[scottgus1]

USB 3.0 should encompasses all previous versions.

I believe that the OP's laptop only has USB3 jacks. While USB3 is a different standard than USB2, a USB3 jack will allow a USB2 and earlier version to still connect and run. The laptop OS will be able to run 2.0 and earlier devices.

FWIW, Paul, USB 1, 1.1, 2.0 all used the same 5 wires (power, ground, +/-data, and shield). So USB 2.0 encompasses 1 and 1.1. But USB 3 requires four more wires, and therefore is incompatible with the earlier versions. However, the USB designers figured out how to put five more connections inside a standard USB jack, and so both the 5-wire and 10-wire standards could connect to the same jack on the PC. The Op's USB3 jacks will be able to connect earlier devices, at the appropriate standard and speeds for the device type being connected.

[michaln]

I believe that the OP's laptop only has USB3 jacks. While USB3 is a different standard than USB2, a USB3 jack will allow a USB2 and earlier version to still connect and run. The laptop OS will be able to run 2.0 and earlier devices.

That's not how I would put it. The so-called "USB3" ports (typically blue) actually contain two physically and electrically different connectors, USB3 and USB2. It's not just that USB3 needs more wires but the signaling and routing protocol is completely different. For one thing, USB2 is broadcast (every device sees all traffic from the host), while USB3 is point-to-point (there's routing information for each device).

The issue of physical ports is separate from the USB host controllers. The original USB 1.x controllers were UHCI and OHCI, and the USB 2.0 controller (which could also handle USB 1.x, but didn't always) was EHCI. For USB 3.0, the xHCI host controller standard was developed, but it can handle older devices as well.

I think the confusion comes from the fact that the laptop has no EHCI controller (guessing) and only has xHCI. But that is irrelevant to VirtualBox, there just needs to be a USB driver on the host.

To reiterate, I don't see why the fact that the laptop only has USB3-capable ports and only a xHCI controller would be a problem.

[PaulReis]

I believe that the OP's laptop only has USB3 jacks. While USB3 is a different standard than USB2, a USB3 jack will allow a USB2 and earlier version to still connect and run. The laptop OS will be able to run 2.0 and earlier devices.

Yes, it has only USB 3.0 as standard jacks. It is the brand new Dell latitude E5470. See that some Dell models has the option to choose USB 2 or 3 from BIOS setup. Not this case.

The issue I'm facing is the same as the following example from MS Technet Forum. See that the resolution for one guy was change from USB 2 to 3 in the BIOS. My initial problem was from MS Virtual Machine application, feature available on Windows 7 - I have installed Windows XP mode also provided by MS tool.

https://social.technet.microsoft.com/Fo ... 7itprovirt

Also I can see some other devices such as onboard webcan; external CD-ROM; Network adapter and Intel chipset. All of them not works into WinXP guest. Same error as the USB pops up from Virtual Box. Also from MS Virtual Machine and XP mode the USB-to-Serial device and all other related ones, don't attach to the guest XP too. Appears the laptop hardware is to much for windows XP.

Thanks again!

[socratis]

Did you unplug the device before you started the VM? And plugged it after you were logged in to the guest OS?

Open a Command Prompt window. Navigate to the VirtualBox installation directory (typically "C:\Program Files\Oracle\VirtualBox\"). With the USB device plugged in and the VM not running, post the output of the following commands:

• VBoxManage list usbhost
  VBoxManage showvminfo "Your_Virtual_Machine_Name"

[PaulReis]

To reiterate, I don't see why the fact that the laptop only has USB3-capable ports and only a xHCI controller would be a problem.

That is the point! Let me note you my initial plan and where I am now. I have one brand new Dell Latitude E5470 device with Windows 7 professional 64 bit. Due to some old application only works on Windows XP, I have tried inhouse solution: MS Virtual PC with XP mode OS - this one was very good from my old Dell's laptop model 5430.

From current XP mode it cannot attach the USB-to-Serial device also external CD-ROM, INtel NIC card and chipset. This is the same issue as below link. Note the solution to a guy was changing USB 3 to 2 from BIOS setup also was dell laptop affected.

https://social.technet.microsoft.com/Fo ... 7itprovirt

Without success with MS inhouse solution, I went to Oracle Virtual Box, installing the guest Windows XP SP3 by a MS media. Here we have the initial error in the post, also for other devices that cannot attach returning same error. Appears the laptop hardware is to much to the WinXP guest. Also believe I should go to some linux OS as Host for better result when virtualization hardware. Do you agree?

Thanks

[michaln]

Do you agree?

Sort of. The problem seems to be with the host OS, not the hardware. What USB drivers do you have installed in the host OS? Important question since Windows 7 does not come with any USB3 drivers, so the OEM needs to provide drivers, and there are at least 4 or 5 different ones.

So yes, I do agree that the host OS is the problem. I actually think that upgrading to Windows 8 or later would also help, since Windows 8 has built-in USB3 drivers that work well.

Still would be good to get the output of the commands that socratis asked for.

[PaulReis]

Did you unplug the device before you started the VM? And plugged it after you were logged in to the guest OS?

Yes. I did. Also tried all USB ports and situation as possible. Always following your steps. Here we have the out put for first command:

Code: Select all

C:\Program Files\Oracle\VirtualBox>vboxmanage list usbhost
Host USB Devices:

UUID:               bca67b7f-6eef-4719-ae0b-ea24e52ab243
VendorId:           0x8087 (8087)
ProductId:          0x0a2b (0A2B)
Revision:           0.1 (0001)
Port:               0
USB version/speed:  2/High
Manufacturer:       IntelCorp.
Address:            {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}\0000
Current State:      Busy

UUID:               47fcda46-575c-4de7-8573-43147dff9fb8
VendorId:           0x413c (413C)
ProductId:          0x9016 (9016)
Revision:           0.0 (0000)
Port:               0
USB version/speed:  2/High
Manufacturer:       Dell Inc.
Product:            Dell DVD+/-RW Drive DW316
SerialNumber:       KX1Z76K1311
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0017
Current State:      Busy

UUID:               3e0cac08-5c1b-4cd4-b1a7-774b884fd987
VendorId:           0x0bda (0BDA)
ProductId:          0x5686 (5686)
Revision:           87.41 (8741)
Port:               0
USB version/speed:  2/High
Manufacturer:       RealtekSemiconductorCorp.
Product:            Integrated_Webcam_HD
SerialNumber:       0001
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0004
Current State:      Busy

UUID:               beca98e9-8f62-4ead-8dfb-180ce2d6f15a
VendorId:           0x0a5c (0A5C)
ProductId:          0x5800 (5800)
Revision:           1.1 (0101)
Port:               0
USB version/speed:  1/Full
Manufacturer:       BroadcomCorp.
Product:            5880
SerialNumber:       0123456789ABCD
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0002
Current State:      Busy

UUID:               afd83fb5-f2ca-4b6b-9de1-83b23e0f4a9d
VendorId:           0x067b (067B)
ProductId:          0x2303 (2303)
Revision:           3.0 (0300)
Port:               0
USB version/speed:  1/Full
Manufacturer:       Prolific Technology Inc.
Product:            USB-Serial Controller
Current State:      Available

Now for the second command:

Code: Select all

C:\Program Files\Oracle\VirtualBox>vboxmanage showvminfo Teste
Name:            Teste
Groups:          /
Guest OS:        Windows XP (32-bit)
UUID:            c45d5089-db53-4c37-a278-de232c27f454
Config file:     C:\Users\manutencao\VirtualBox VMs\Teste\Teste.vbox
Snapshot folder: C:\Users\manutencao\VirtualBox VMs\Teste\Snapshots
Log folder:      C:\Users\manutencao\VirtualBox VMs\Teste\Logs
Hardware UUID:   c45d5089-db53-4c37-a278-de232c27f454
Memory size:     192MB
Page Fusion:     off
VRAM size:       16MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       off
Triple Fault Reset: off
APIC:            on
X2APIC:          off
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          off
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: None
State:           powered off (since 2016-10-27T17:43:58.000000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
IDE (0, 0): C:\Users\manutencao\VirtualBox VMs\Teste\Snapshots/{192e9b3a-3c80-4d
4b-9316-62eb77145b83}.vdi (UUID: 192e9b3a-3c80-4d4b-9316-62eb77145b83)
IDE (1, 0): Empty
NIC 1:           MAC: 080027E84B32, Attachment: NAT, Cable connected: on, Trace:
 off (file: none), Type: 82543GC, Reported speed: 0 Mbps, Boot priority: 0, Prom
isc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, re
ceive: 64)
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: DSOUND, Controller: AC97, Codec: STAC9700)
Clipboard Mode:  Bidirectional
Drag and drop Mode: Bidirectional
VRDE:            disabled
USB:             enabled
EHCI:            enabled
XHCI:            disabled

USB Device Filters:

Index:            0
Active:           yes
Name:             ProlificTechnology,Inc. PL2303SerialPort [0202]
VendorId:         067b
ProductId:        2303
Revision:
Manufacturer:
Product:
Remote:           0
Serial Number:

Index:            1
Active:           yes
Name:             Prolific Technology Inc. IEEE-1284 Controller [0202]
VendorId:         067b
ProductId:        2305
Revision:
Manufacturer:
Product:
Remote:           0
Serial Number:

Bandwidth groups:  <none>

Shared folders:

Name: 'Temp', Host path: 'C:\Temp' (machine mapping), writable

Video capturing:    not active
Capture screens:    0
Capture file:       C:\Users\manutencao\VirtualBox VMs\Teste\Teste.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB

Snapshots:

   Name: Snapshot 1 (UUID: ab11727a-c9e8-4115-8018-7496a47bc7df) *

Again, thanks for your support