blob: 63c522ef55fa8b8c87ae64c22712c638780a8882 (
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
52
53
54
55
|
device: 0.704
semantic: 0.662
graphic: 0.651
hypervisor: 0.613
mistranslation: 0.544
i386: 0.523
architecture: 0.521
kernel: 0.514
performance: 0.466
vnc: 0.463
ppc: 0.444
network: 0.442
x86: 0.439
PID: 0.421
socket: 0.405
boot: 0.393
virtual: 0.382
debug: 0.341
arm: 0.328
risc-v: 0.322
register: 0.307
VMM: 0.276
assembly: 0.257
KVM: 0.238
user-level: 0.207
peripherals: 0.207
TCG: 0.205
files: 0.189
permissions: 0.119
-readconfig file doesn't interpret memory size correctly
I'm running Qemu 2.1 and have issues with the config file format.
Specifically Qemu wrote the following snippet with '-writeconfig':
[memory]
size = "1024"
However, upon starting a VM with this setting it only receives 128MiB (the default size).
I'm reverting back to using the command line option now - that works.
duplicate
Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
Good question. Over time I've got some feedback that the whole config file mechanism is really just a second class citizen anyway. I'm happy for now (running 2.7) and don't really care too much.
Nevertheless: I'd be absolutely excited if I could reliably configure (and have nice documentation that I'd even be willing to help create) Qemu instances just with a config file ...
Feel free to close this issue to get rid of old cruft ... :)
[Expired for QEMU because there has been no activity for 60 days.]
|