1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
|
other: 0.102
device: 0.097
permissions: 0.094
PID: 0.089
performance: 0.073
files: 0.073
semantic: 0.071
socket: 0.067
graphic: 0.064
vnc: 0.064
KVM: 0.059
debug: 0.053
network: 0.049
boot: 0.046
debug: 0.417
PID: 0.091
device: 0.084
files: 0.065
socket: 0.064
other: 0.063
performance: 0.042
semantic: 0.036
boot: 0.034
vnc: 0.028
network: 0.026
permissions: 0.018
KVM: 0.016
graphic: 0.016
[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
|