summaryrefslogtreecommitdiffstats
path: root/results/classifier/105/device/1358287
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/105/device/1358287')
-rw-r--r--results/classifier/105/device/135828738
1 files changed, 38 insertions, 0 deletions
diff --git a/results/classifier/105/device/1358287 b/results/classifier/105/device/1358287
new file mode 100644
index 00000000..a9fa5945
--- /dev/null
+++ b/results/classifier/105/device/1358287
@@ -0,0 +1,38 @@
+device: 0.704
+semantic: 0.662
+graphic: 0.651
+instruction: 0.587
+mistranslation: 0.544
+vnc: 0.463
+network: 0.442
+other: 0.428
+socket: 0.405
+boot: 0.393
+assembly: 0.257
+KVM: 0.238
+
+-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.]
+