From: Laszlo Ersek <lersek@redhat.com>
To: Dennis Luehring <dl.soluz@gmx.net>,
Richard Henderson <rth@twiddle.net>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] alpha platform is missing files after initrd load
Date: Mon, 7 Nov 2016 16:56:34 +0100 [thread overview]
Message-ID: <76237a3c-60e3-ecd2-a883-36b01896293a@redhat.com> (raw)
In-Reply-To: <320accbd-58f5-d24c-ca6e-9cc109ee5d3f@gmx.net>
On 11/07/16 15:38, Dennis Luehring wrote:
> Am 07.11.2016 um 15:12 schrieb Laszlo Ersek:
>> The second error message is incorrect in its own right (it's just
>> another symptom of running out of memory;
> there a two cpios
>
> big(~370MB) initrd.cpio + 1GB ram gives only this message: "Initramfs
> unpacking failed: write error"
> small(~14MB) initrd.cpio + 1GB ram gives only this message: "Initramfs
> unpacking failed: junk in compressed archive"
>
> so the second one couldn't be a problem with running out of memory - and
> its not alpha related same error happens with ppc64,sparc64,mips64...
The second one *is* related to running out of memory. Initrd
decompression takes unintuitive amounts of memory. And, in practice,
exactly the second error message was seen with the aarch64 target, until
Rich Jones raised the guest RAM size that libguestfs passed to QEMU.
You can try it for yourself: stick with the small (14MB) initrd, and,
say, quadruple the guest RAM size. I'm pretty sure it will succeed.
The difference between the error messages (and the initrd sizes) is that
the initrd decompression runs out of memory at different stages. With
the huge initrd, unpacking likely fails in one of the early stages. With
the smaller one, unpacking likely fails later. I never bothered to
figure out where exactly.
Thanks
Laszlo
next prev parent reply other threads:[~2016-11-07 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 10:45 [Qemu-devel] alpha platform is missing files after initrd load Dennis Luehring
2016-11-04 11:08 ` Stefan Hajnoczi
2016-11-04 16:37 ` Richard Henderson
2016-11-04 19:40 ` Laszlo Ersek
2016-11-04 21:08 ` Richard Henderson
2016-11-07 7:37 ` Dennis Luehring
2016-11-07 14:12 ` Laszlo Ersek
2016-11-07 14:38 ` Dennis Luehring
2016-11-07 15:56 ` Laszlo Ersek [this message]
2016-11-07 16:11 ` Dennis Luehring
2016-11-07 17:21 ` Laszlo Ersek
2016-11-09 6:34 ` Dennis Luehring
2016-11-11 6:49 ` Dennis Luehring
2016-11-07 7:35 ` Dennis Luehring
2016-11-07 14:15 ` Laszlo Ersek
2016-11-07 14:18 ` Laszlo Ersek
2016-11-07 15:16 ` Dennis Luehring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76237a3c-60e3-ecd2-a883-36b01896293a@redhat.com \
--to=lersek@redhat.com \
--cc=dl.soluz@gmx.net \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=rth@twiddle.net \
--cc=stefanha@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).