-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
investigate why we need > 2G memory for live ISO/PXE boot #407
Comments
Did some more probing of this. With 1024M of RAM, the kernel and initrd are loaded successfully, but the kernel is never started. With 2048M of RAM, the kernel can start, but systemd crashes. One thing I was wondering was whether somehow unzipping all the CPIOs took up all the space. Though doing a
(This is before systemd nukes everything.) |
I just ran some tests with the latest
|
I think we can close this now. 1G for the live ISO seems reasonable and 2G for PXE makes sense too since it needs to host the full rootfs. |
Agreed. I just ran a test against the artifacts from |
Okay, coreos/fedora-coreos-docs#196 updates docs for the current RAM requirements. |
Given coreos/fedora-coreos-docs#196 (comment), I think there's still a mystery re. why the concatenated approach needs more RAM. But at least the other more common cases are under control now. Let's keep this closed and we can re-open this or a separate issue to investigate what's going on in the concatenated approach if it becomes a sore point. |
That behavior is expected, no? The concatenated approach should require 2x rootfs RAM during unpack, but the streaming approach should require 1x. |
Right, but shouldn't the memory taken up by the CPIOs be freed once the kernel is done extracting them? So it would need only roughly 700M x 2 + some more memory to get the CPIOs extracted. I guess this gets into the specifics of how the bootloader loads the initrds and how the kernel processes them, which changes per architecture. It's likely that how that works is just not matching my mental model and there's not much for us to improve on here. :) |
A lot of people are hitting #388. In the discussion in the documentation PR coreos/fedora-coreos-docs#46 a few of us seem to think we should be able to get by with less than 2G of RAM so we should investigate why we need more than that to see where the disconnect is.
The text was updated successfully, but these errors were encountered: