1 files changed, 27 insertions, 0 deletions
diff --git a/results/classifier/zero-shot/105/instruction/1776486 b/results/classifier/zero-shot/105/instruction/1776486
new file mode 100644
index 000000000..ac7ec2ea1
--- /dev/null
+++ b/results/classifier/zero-shot/105/instruction/1776486
@@ -0,0 +1,27 @@
+instruction: 0.739
+device: 0.712
+KVM: 0.706
+boot: 0.654
+graphic: 0.616
+vnc: 0.603
+semantic: 0.532
+mistranslation: 0.494
+other: 0.487
+network: 0.443
+socket: 0.430
+assembly: 0.304
+
+detect error when kernel and initrd images exceed ram size
+
+I was unable to figure out why my VM wasn't booting when I added a "-initrd" image.  I would launch qemu and get no output, and no error message, it would just spin.
+
+Turns out my initrd image was around 270 MB but I wasn't giving an explicit ram size to qemu.  I was told the default memory size was around 120 MB so this was definitely a problem.  I think that the qemu "pseudo-bootloader" should detect when the kernel image and initrd image sizes exceed the size of ram and print a nice error to the user, something like:
+
+Error: the total size of the given boot images (342M) exceeds the size allocated for memory (120M)
+
+We could also do a better job of identifying when different things (initrd, kernel, dtb) overlap in memory.
+
+
+As of the 4.1 release we should now do a better job of identifying overlaps between initrd, kernel, end of ram, etc, for the built-in arm bootloader.
+
+