permissions: 0.908
PID: 0.903
device: 0.881
graphic: 0.876
register: 0.870
virtual: 0.869
risc-v: 0.865
performance: 0.864
assembly: 0.855
vnc: 0.854
arm: 0.852
semantic: 0.846
socket: 0.846
user-level: 0.845
architecture: 0.845
alpha: 0.837
operating system: 0.830
TCG: 0.828
KVM: 0.827
debug: 0.826
files: 0.820
boot: 0.815
hypervisor: 0.815
x86: 0.815
kernel: 0.809
VMM: 0.801
ppc: 0.792
i386: 0.782
mistranslation: 0.781
peripherals: 0.770
network: 0.769

[Qemu-devel]  [BUG] qemu stuck when detach host-usb device

Description of problem:
The guest has a host-usb device(Kingston Technology DataTraveler 100 G3/G4/SE9 
G2), which is attached
to xhci controller(on host). Qemu will stuck if I detach it from guest.

How reproducible:
100%

Steps to Reproduce:
1.            Use usb stick to copy files in guest , make it busy working.
2.            virsh detach-device vm_name usb.xml

Then qemu will stuck for 20s, I found this is because libusb_release_interface 
block for 20s.
Dmesg prints:

[35442.034861] usb 4-2.1: Disable of device-initiated U1 failed.
[35447.034993] usb 4-2.1: Disable of device-initiated U2 failed.
[35452.035131] usb 4-2.1: Set SEL for device-initiated U1 failed.
[35457.035259] usb 4-2.1: Set SEL for device-initiated U2 failed.

Is this a hardware error or software's bug?

On Tue, Nov 27, 2018 at 01:26:24AM +0000, linzhecheng wrote:
>
Description of problem:
>
The guest has a host-usb device(Kingston Technology DataTraveler 100
>
G3/G4/SE9 G2), which is attached
>
to xhci controller(on host). Qemu will stuck if I detach it from guest.
>
>
How reproducible:
>
100%
>
>
Steps to Reproduce:
>
1.            Use usb stick to copy files in guest , make it busy working.
>
2.            virsh detach-device vm_name usb.xml
>
>
Then qemu will stuck for 20s, I found this is because
>
libusb_release_interface block for 20s.
>
Dmesg prints:
>
>
[35442.034861] usb 4-2.1: Disable of device-initiated U1 failed.
>
[35447.034993] usb 4-2.1: Disable of device-initiated U2 failed.
>
[35452.035131] usb 4-2.1: Set SEL for device-initiated U1 failed.
>
[35457.035259] usb 4-2.1: Set SEL for device-initiated U2 failed.
>
>
Is this a hardware error or software's bug?
I'd guess software error, could be is libusb or (host) linux kernel.
Cc'ing libusb-devel.

cheers,
  Gerd

>
-----Original Message-----
>
From: Gerd Hoffmann [
mailto:address@hidden
>
Sent: Tuesday, November 27, 2018 2:09 PM
>
To: linzhecheng <address@hidden>
>
Cc: address@hidden; wangxin (U) <address@hidden>;
>
Zhoujian (jay) <address@hidden>; address@hidden
>
Subject: Re: [Qemu-devel] [BUG] qemu stuck when detach host-usb device
>
>
On Tue, Nov 27, 2018 at 01:26:24AM +0000, linzhecheng wrote:
>
> Description of problem:
>
> The guest has a host-usb device(Kingston Technology DataTraveler 100
>
> G3/G4/SE9 G2), which is attached to xhci controller(on host). Qemu will
>
> stuck
>
if I detach it from guest.
>
>
>
> How reproducible:
>
> 100%
>
>
>
> Steps to Reproduce:
>
> 1.            Use usb stick to copy files in guest , make it busy working.
>
> 2.            virsh detach-device vm_name usb.xml
>
>
>
> Then qemu will stuck for 20s, I found this is because
>
> libusb_release_interface
>
block for 20s.
>
> Dmesg prints:
>
>
>
> [35442.034861] usb 4-2.1: Disable of device-initiated U1 failed.
>
> [35447.034993] usb 4-2.1: Disable of device-initiated U2 failed.
>
> [35452.035131] usb 4-2.1: Set SEL for device-initiated U1 failed.
>
> [35457.035259] usb 4-2.1: Set SEL for device-initiated U2 failed.
>
>
>
> Is this a hardware error or software's bug?
>
>
I'd guess software error, could be is libusb or (host) linux kernel.
>
Cc'ing libusb-devel.
Perhaps it's usb driver's bug. Could you also reproduce it?
>
>
cheers,
>
Gerd