[Qemu-devel] [Bug 1689003] [NEW] USB passthrough should not fail if SET CONFIGURATION fails

[Manfred Härtel]

Public bug reported:

QEMU's USB passthrough was not working for my new smartphone.

While analyzing the problem, I found out that a SET CONFIGURATION
Request was NACKed by the USB device (probably because a SET
CONFIGURATION request was already sent from the host to the device).

So I wrote a simple program to fake a successful call to
libusb_set_configuration and did an LD_PRELOAD on this program before
starting qemu, and it worked.

Looking at QEMU's code in host-libusb.c, I can see that QEMU does not
try to claim the interface if its call to libusb_set_configuration
fails.

I think QEMU should try to claim the device anyway even if
libusb_set_configuration fails.

I did my tests against QEMU 2.6.2, but as I can see from the source
code, this problem should happen on all versions.

** 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/1689003

Title:
  USB passthrough should not fail if SET CONFIGURATION fails

Status in QEMU:
  New

Bug description:
  QEMU's USB passthrough was not working for my new smartphone.

  While analyzing the problem, I found out that a SET CONFIGURATION
  Request was NACKed by the USB device (probably because a SET
  CONFIGURATION request was already sent from the host to the device).

  So I wrote a simple program to fake a successful call to
  libusb_set_configuration and did an LD_PRELOAD on this program before
  starting qemu, and it worked.

  Looking at QEMU's code in host-libusb.c, I can see that QEMU does not
  try to claim the interface if its call to libusb_set_configuration
  fails.

  I think QEMU should try to claim the device anyway even if
  libusb_set_configuration fails.

  I did my tests against QEMU 2.6.2, but as I can see from the source
  code, this problem should happen on all versions.

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