USB Host Passthrough BSOD on Windows XP

USB Host Passthrough BSOD on Windows XP

[mattia.martinello]

Hi.
I installed a KVM virtual machine with Windows XP SP3 installed on it
with all updates from Windows Update.
I setted up an USB device from the host machine to be used on the
virtual machine with the command

qm set 107 -hostusb 2040:7070

The USB device is an Hauppauge WinTV Nova-T Stick DVB-T USB adapter.

Windows recognises the hardware and correctly install its drivers, but
when I try to use it (for example tuning some channels) I get the
following Blue Screen Of Death:

DRIVER_IRQL_NOT_LESS_OR_EQUAL
*** STOP: 0x000000D1 (0x048C4C04, 0x00000002, 0x00000001, 0xBA392FD3)
*** usbuhci.sys - Address BA392FD3 base at BA390000, DateStamp 480254ce

Windows' Minudump files tell that the problem is from the usbuhci.sys driver.

I'm using Proxmox VE 1.6 (the latest version) with the 2.6.32-2-pve
kernel version.

Do you have any hint?

Thank you very much for your help!
Bye.

Re: USB Host Passthrough BSOD on Windows XP

[Erik Rull]

mattia.martinello@gmail.com wrote:
> Hi.
> I installed a KVM virtual machine with Windows XP SP3 installed on it
> with all updates from Windows Update.
> I setted up an USB device from the host machine to be used on the
> virtual machine with the command
>
> qm set 107 -hostusb 2040:7070
>
> The USB device is an Hauppauge WinTV Nova-T Stick DVB-T USB adapter.
>
> Windows recognises the hardware and correctly install its drivers, but
> when I try to use it (for example tuning some channels) I get the
> following Blue Screen Of Death:
>
> DRIVER_IRQL_NOT_LESS_OR_EQUAL
> *** STOP: 0x000000D1 (0x048C4C04, 0x00000002, 0x00000001, 0xBA392FD3)
> *** usbuhci.sys - Address BA392FD3 base at BA390000, DateStamp 480254ce
>
> Windows' Minudump files tell that the problem is from the usbuhci.sys driver.
>
> I'm using Proxmox VE 1.6 (the latest version) with the 2.6.32-2-pve
> kernel version.
>
> Do you have any hint?
>
> Thank you very much for your help!
> Bye.

Hi Mattia,

I have the same issue since KVM 73.

It seems to be related to USB 2.0 hardware. Set your USB Hardware or your 
host in BIOS to 1.0 or 1.1, boot again.
This will result into a max. transfer rate of ~32-64 KB/sec but your 
Hardware will work more stable.
But some USB 2.0 components will still fail if they are not fully USB 1.x 
capable.
I have an old USB HP printer that works slow but fine and a new Canon that 
crashes Windows with exactly the same driver that hooks up (usbuhci.sys).

Sometimes it just doesn't do anything and when unplugging the printer or 
shutting down the bluescreen comes up.

Also have a look on the dmesg of your host! I recognized there a massive 
connect/disconnect occurence of the given USB device when it is physically 
connected.

The reason seems to be somewhere in the KVM usb layer I tried to find it 
out but no success.

Best regards,

Erik