blob: fa216ac21c97ebe560a1153e300b6ff8492f0150 (
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
51
|
i386: 0.972
socket: 0.931
performance: 0.775
network: 0.766
graphic: 0.712
x86: 0.710
device: 0.659
vnc: 0.598
ppc: 0.589
kernel: 0.457
architecture: 0.456
mistranslation: 0.450
PID: 0.444
permissions: 0.441
debug: 0.426
peripherals: 0.424
semantic: 0.408
files: 0.399
register: 0.396
arm: 0.344
user-level: 0.342
boot: 0.299
TCG: 0.290
hypervisor: 0.270
risc-v: 0.232
virtual: 0.220
VMM: 0.212
assembly: 0.096
KVM: 0.067
-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.]
|