1 files changed, 60 insertions, 0 deletions
diff --git a/results/classifier/118/device/1794187 b/results/classifier/118/device/1794187
new file mode 100644
index 000000000..eb8d933e1
--- /dev/null
+++ b/results/classifier/118/device/1794187
@@ -0,0 +1,60 @@
+device: 0.902
+architecture: 0.852
+performance: 0.830
+files: 0.819
+socket: 0.788
+vnc: 0.777
+ppc: 0.774
+network: 0.741
+permissions: 0.734
+graphic: 0.728
+PID: 0.724
+register: 0.723
+kernel: 0.672
+VMM: 0.648
+boot: 0.641
+risc-v: 0.639
+semantic: 0.638
+mistranslation: 0.631
+hypervisor: 0.594
+arm: 0.543
+peripherals: 0.531
+TCG: 0.531
+virtual: 0.513
+i386: 0.503
+x86: 0.466
+debug: 0.458
+user-level: 0.411
+KVM: 0.335
+assembly: 0.279
+
+improve error message, when using raspi3 and RAM>4G
+
+Running `qemu-system-aarch64 image-aarch64.iso --machine raspi3 -m 8G` prints this error message:
+
+```
+Unexpected error in visit_type_uintN() at /builddir/build/BUILD/qemu-3.0.0/qapi/qapi-visit-core.c:164:
+qemu-system-aarch64: Parameter 'vcram-base' expects uint32_t
+```
+
+The problem is, that you musn't use more than 4 GB RAM for machine raspi3. As it took me some time to figure that out, I'd be glad, if you can print better error message, like you do, when using more than 4 CPU cores with machine raspi3:
+
+```
+Invalid SMP CPUs 8. The max CPUs supported by machine 'raspi3' is 4 
+```
+
+I've submitted a patch to the list: http://patchwork.ozlabs.org/patch/1067963/
+
+With it, QEMU will give this error instead:
+
+qemu-system-aarch64: Requested ram size is too large for this machine: maximum is 1GB
+
+(Note that the maximum is 1GB, not 4GB -- it's just that values between 1 and 4GB happened not to make QEMU crash, though it wouldn't handle them very usefully before.)
+
+
+Improved diagnostic message is now in master and will be in QEMU 4.1.
+
+
+Fixed here:
+https://git.qemu.org/?p=qemu.git;a=commitdiff;h=ff3dcf28c0b7a3ac261
+