[Bug 1776486] Re: detect error when kernel and initrd images exceed ram size

[Peter Maydell]

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.


** Changed in: qemu
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1776486

Title:
  detect error when kernel and initrd images exceed ram size

Status in QEMU:
  Fix Released

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1776486/+subscriptions