blob: a74c8f4fe542c8b579f4c0c66035cbf2ce0fabbd (
plain) (
blame)
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
|
socket: 0.264
other: 0.176
semantic: 0.080
network: 0.075
vnc: 0.070
device: 0.062
performance: 0.055
PID: 0.046
graphic: 0.046
files: 0.035
debug: 0.030
permissions: 0.027
boot: 0.024
KVM: 0.012
socket: 0.369
performance: 0.194
debug: 0.080
other: 0.072
network: 0.061
PID: 0.058
semantic: 0.044
files: 0.037
device: 0.028
boot: 0.017
permissions: 0.013
vnc: 0.012
graphic: 0.009
KVM: 0.004
-netdev socket uses 100% cpu on Windows host
On Windows hosts, any `-netdev socket` option (tcp listen, tcp connect, udp passing a fd) causes qemu to use 100% cpu. The guest still runs, but only sluggishly.
A simple testcase is:
> qemu-system-i386.exe -netdev socket,listen=:8000,id=n
And, in another command prompt:
> echo foo | nc.exe localhost 8000
Where nc.exe is netcat.
Tested on qemu 3.1 (from https://qemu.weilnetz.de/w64/) and 4.0 (self compiled).
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|