Ticket #69 (closed defect: needinfo)

Opened 3 years ago

Last modified 15 months ago

libusb_bulk_transfer taks long time in VMWare virtual machine

Reported by: searockcliff Owned by: stuge
Milestone: Component: libusb-1.0
Keywords: libusb_bulk_transfer delay Cc:
Blocked By: Blocks:

Description

Hi,

Host OS: Windows XP
VMware Workstation 7.0
Client OS: OpenSuse? 11.2 Linux

With libusb 1.0, the libusb_bulk_transfer hangs for a long time(few minutes) before return.

The libusb 0.8 does not have the problem.

Please fix it.

Change History

comment:1 Changed 3 years ago by searockcliff

  • Owner changed from searockcliff to hjelmn
  • Status changed from new to assigned

comment:2 follow-up: Changed 3 years ago by xiaofan

Hmm, I am not so sure if you should assign the owner. Probably the developers and admins can assign the owner.

And why do you think it is a libusb issue and not a VMWare Workstation issue? VMWare is kind of flaky in terms of USB as far as I read.

comment:3 follow-up: Changed 3 years ago by stuge

  • Owner changed from hjelmn to stuge
  • Status changed from assigned to accepted

Yes, please don't assign tickets to others. Thanks.

VMware Workstation is a somewhat exotic machine, and an expensive one at that, so in order to resolve this issue you will have to do some debugging and provide us with the needed information. I would certainly like to see the issue fixed, especially if it lies within libusb 1.0.

There is no libusb version 0.8 - please clarify which version of libusb it was that worked correctly?

Could you provide a minimal test program which exhibits the problem when run in the virtual machine? Please attach the source code to the ticket. We may not have your USB device, but it still helps to see how you are using the library and we'll need debug output from a program which we know the source code of.

Please build the latest libusb.git source code, configured with debugging enabled, and run the minimal test program linked with that library. It should produce fairly verbose debug output. Please attach a file with that debug output to the ticket.

usbmon output from the guest kernel while running your minimal test program and capturing the debug output would also be very helpful, maybe even instrumental, for finding the problem.

Thank you!

comment:4 in reply to: ↑ 2 Changed 3 years ago by searockcliff

Sorry,I find him as the owner of some tickets, so ...

Replying to xiaofan:

Hmm, I am not so sure if you should assign the owner. Probably the developers and admins can assign the owner.

And why do you think it is a libusb issue and not a VMWare Workstation issue? VMWare is kind of flaky in terms of USB as far as I read.

comment:5 in reply to: ↑ 3 Changed 3 years ago by searockcliff

Thanks for your advice!
We are from SafeNet?, we once use an old version of libusb in our USB Key product, which works fine.

The procedure is to open the device and use libusb_bulk_transfer to communicate.

We will try the debug and upload the log.

Replying to stuge:

Yes, please don't assign tickets to others. Thanks.

VMware Workstation is a somewhat exotic machine, and an expensive one at that, so in order to resolve this issue you will have to do some debugging and provide us with the needed information. I would certainly like to see the issue fixed, especially if it lies within libusb 1.0.

There is no libusb version 0.8 - please clarify which version of libusb it was that worked correctly?

Could you provide a minimal test program which exhibits the problem when run in the virtual machine? Please attach the source code to the ticket. We may not have your USB device, but it still helps to see how you are using the library and we'll need debug output from a program which we know the source code of.

Please build the latest libusb.git source code, configured with debugging enabled, and run the minimal test program linked with that library. It should produce fairly verbose debug output. Please attach a file with that debug output to the ticket.

usbmon output from the guest kernel while running your minimal test program and capturing the debug output would also be very helpful, maybe even instrumental, for finding the problem.

Thank you!

comment:6 Changed 15 months ago by stuge

  • Resolution set to needinfo
  • Status changed from accepted to closed

Please reopen this ticket if you can provide the requested information. Thanks!

Note: See TracTickets for help on using tickets.