blob: 904ba03a0c08d4da59c30e446664557b3750fda7 (
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
|
mistranslation: 0.769
device: 0.714
network: 0.520
socket: 0.427
semantic: 0.384
graphic: 0.312
vnc: 0.308
register: 0.305
architecture: 0.297
PID: 0.242
risc-v: 0.238
boot: 0.237
virtual: 0.222
kernel: 0.218
ppc: 0.215
TCG: 0.174
files: 0.170
hypervisor: 0.164
user-level: 0.162
peripherals: 0.158
VMM: 0.149
i386: 0.121
permissions: 0.110
KVM: 0.096
arm: 0.093
performance: 0.091
x86: 0.081
debug: 0.076
assembly: 0.050
-nodefaults has unclear documentation
-nodefaults has an unclear documentation, I believe it should states it does not applies to devices created by a machine model.
See https://stackoverflow.com/questions/52908614/qemu-s-nodefaults-not-working-as-expected-to-me to read how I came to this.
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/156
|