diff options
Diffstat (limited to 'results/scraper/launchpad/1776486')
| -rw-r--r-- | results/scraper/launchpad/1776486 | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/results/scraper/launchpad/1776486 b/results/scraper/launchpad/1776486 new file mode 100644 index 00000000..b1c9b3a5 --- /dev/null +++ b/results/scraper/launchpad/1776486 @@ -0,0 +1,14 @@ +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. + + |