qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1198350] [NEW] USB pass-through fails with USBDEVFS_DI


From: Pete Scott
Subject: [Qemu-devel] [Bug 1198350] [NEW] USB pass-through fails with USBDEVFS_DISCONNECT: Invalid argument
Date: Fri, 05 Jul 2013 22:11:11 -0000

Public bug reported:

Host Gentoo linux 32bit
Guest Windows XP SP3
qemu 1.4.2 and
qemu fresh get clone and build 2013-07-04 (version1.5.50)
qemu command line

qemu-system-i386 -enable-kvm localtime -m 2047 -boot d
/archive3/qemu/WindowsXP.img -net nic,model=rtl8139 -net user -usb
-device usb-ehci,id=ehci -usbdevice host:1493:19

The device I am trying to use with the guest is an interface for the
Suunto Ambit 2 GPS watch which has no linux support.

When the USB device is plugged in qemu reports to the command line:

USBDEVFS_DISCONNECT: Invalid argument
Invalid argument

dmesg shows

[237755.495968] usb 2-1.5: new full-speed USB device number 34 using ehci-pci
[237755.582778] usb 2-1.5: config 1 has an invalid interface number: 1 but max 
is 0
[237755.582781] usb 2-1.5: config 1 has no interface number 0
[237755.583628] usb 2-1.5: New USB device found, idVendor=1493, idProduct=0019
[237755.583631] usb 2-1.5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[237755.583633] usb 2-1.5: Product: Ambit
[237755.583634] usb 2-1.5: Manufacturer: Suunto
[237755.583636] usb 2-1.5: SerialNumber: CE83095110000700
[237756.584937] usb 2-1.5: reset full-speed USB device number 34 using ehci-pci
[237756.832658] usb 2-1.5: reset full-speed USB device number 34 using ehci-pci
[237757.143585] usb 2-1.5: usbfs: process 12684 (qemu-system-i38) did not claim 
interface 1 before use

In the windows guest Device Manager a HID device is listed but nothing
else happens, no found new hardware dialog or the Suunto software (which
is sitting there waiting) is not triggered as it should be.

I have tried successfully with several other devices (flash drive,
mouse, printer and video capture device). Because this device pretends
to be an HID device my kernel's hid-generic driver was picking it up
first until I modified hid-core.c to ignore this vendorid/productid. But
still no joy.

I'm guessing it has something to do with the the dmesg lines:

[237755.582778] usb 2-1.5: config 1 has an invalid interface number: 1 but max 
is 0
[237755.582781] usb 2-1.5: config 1 has no interface number 0

But read that these warnings are not important though I don't get them
for other devices. Nor do I get:

[237757.143585] usb 2-1.5: usbfs: process 12684 (qemu-system-i38) did
not claim interface 1 before use

I've done alot of searching and I've run out of ideas. Any help would be
great.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1198350

Title:
  USB pass-through fails with USBDEVFS_DISCONNECT: Invalid argument

Status in QEMU:
  New

Bug description:
  Host Gentoo linux 32bit
  Guest Windows XP SP3
  qemu 1.4.2 and
  qemu fresh get clone and build 2013-07-04 (version1.5.50)
  qemu command line

  qemu-system-i386 -enable-kvm localtime -m 2047 -boot d
  /archive3/qemu/WindowsXP.img -net nic,model=rtl8139 -net user -usb
  -device usb-ehci,id=ehci -usbdevice host:1493:19

  The device I am trying to use with the guest is an interface for the
  Suunto Ambit 2 GPS watch which has no linux support.

  When the USB device is plugged in qemu reports to the command line:

  USBDEVFS_DISCONNECT: Invalid argument
  Invalid argument

  dmesg shows

  [237755.495968] usb 2-1.5: new full-speed USB device number 34 using ehci-pci
  [237755.582778] usb 2-1.5: config 1 has an invalid interface number: 1 but 
max is 0
  [237755.582781] usb 2-1.5: config 1 has no interface number 0
  [237755.583628] usb 2-1.5: New USB device found, idVendor=1493, idProduct=0019
  [237755.583631] usb 2-1.5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [237755.583633] usb 2-1.5: Product: Ambit
  [237755.583634] usb 2-1.5: Manufacturer: Suunto
  [237755.583636] usb 2-1.5: SerialNumber: CE83095110000700
  [237756.584937] usb 2-1.5: reset full-speed USB device number 34 using 
ehci-pci
  [237756.832658] usb 2-1.5: reset full-speed USB device number 34 using 
ehci-pci
  [237757.143585] usb 2-1.5: usbfs: process 12684 (qemu-system-i38) did not 
claim interface 1 before use

  In the windows guest Device Manager a HID device is listed but nothing
  else happens, no found new hardware dialog or the Suunto software
  (which is sitting there waiting) is not triggered as it should be.

  I have tried successfully with several other devices (flash drive,
  mouse, printer and video capture device). Because this device pretends
  to be an HID device my kernel's hid-generic driver was picking it up
  first until I modified hid-core.c to ignore this vendorid/productid.
  But still no joy.

  I'm guessing it has something to do with the the dmesg lines:

  [237755.582778] usb 2-1.5: config 1 has an invalid interface number: 1 but 
max is 0
  [237755.582781] usb 2-1.5: config 1 has no interface number 0

  But read that these warnings are not important though I don't get them
  for other devices. Nor do I get:

  [237757.143585] usb 2-1.5: usbfs: process 12684 (qemu-system-i38) did
  not claim interface 1 before use

  I've done alot of searching and I've run out of ideas. Any help would
  be great.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1198350/+subscriptions



reply via email to

[Prev in Thread] Current Thread [Next in Thread]