Bug 1224263 - Ensure installer initrd in Agama is small enough to load on PowerVM with secure boot and vTPM emabled
Summary: Ensure installer initrd in Agama is small enough to load on PowerVM with secu...
Status: RESOLVED FEATURE
Alias: None
Product: SUSE Linux Enterprise Server 16.0
Classification: SUSE Linux Framework One
Component: Installation (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-15 08:47 UTC by Michal Suchanek
Modified: 2024-05-15 11:45 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Suchanek 2024-05-15 08:47:38 UTC
On PowerVM platform the memory available to the bootloader is limited leading to out of memory error when ramdisk is too large.
Comment 1 Lukas Ocilka 2024-05-15 08:50:35 UTC
(In reply to Michal Suchanek from comment #0)
> On PowerVM platform the memory available to the bootloader is limited
> leading to out of memory error when ramdisk is too large.

Please define "limited".
Comment 2 Michal Suchanek 2024-05-15 08:50:50 UTC
SLE bug 1223982
Detailed discussion in bug 1223383
Comment 3 Imobach Gonzalez Sosa 2024-05-15 10:35:20 UTC
Hi all,

First of all, we would appreciate it if bug reports contained all the required information (like the initrd limit, in this case) instead of pointing to a long discussion elsewhere[1].

Having said that, I checked the initrd sizes of the soon-to-be-released Agama version and that's what I found:

* aarch64: 101MB
* ppc64le: 84MB
* x86_64: 93MB
* s390x: 58MB

So assuming 124MB as the limit, I would say it meets this requirement. However, we should put some mechanism in place to detect a potential problem regarding the initrd size.

In any case, I would say that the correct way to handle this is through a feature request via JIRA. Michal, please, could you submit such a feature including the relevant information?

Thanks in advance!

Regards,
Imo

[1] https://confluence.suse.com/display/YAST/How+to+Write+a+Good+Bug+Report
[2] https://confluence.suse.com/display/YAST/RFC%3A+Feature-Requesting+Howto
Comment 4 Michal Suchanek 2024-05-15 10:43:41 UTC
(In reply to Imobach Gonzalez Sosa from comment #3)
> Hi all,
> 
> First of all, we would appreciate it if bug reports contained all the
> required information (like the initrd limit, in this case) instead of
> pointing to a long discussion elsewhere[1].
> [1] https://confluence.suse.com/display/YAST/How+to+Write+a+Good+Bug+Report

The limit is not known. So I have the choice to not write a bug report at all and leave you in the dark or write a bug report that points to the ongoing discussion.

> Having said that, I checked the initrd sizes of the soon-to-be-released
> Agama version and that's what I found:
> 
> * aarch64: 101MB
> * ppc64le: 84MB

That's much more reasonable than what we get with installation-images and should not cause problems as is at this time.

> * x86_64: 93MB
> * s390x: 58MB
> 
> So assuming 124MB as the limit, I would say it meets this requirement.

Clearly it is not.

> However, we should put some mechanism in place to detect a potential problem
> regarding the initrd size.
> 
> In any case, I would say that the correct way to handle this is through a
> feature request via JIRA. Michal, please, could you submit such a feature
> including the relevant information?

What would you expect in that feature?
Comment 5 Imobach Gonzalez Sosa 2024-05-15 11:45:22 UTC
(In reply to Michal Suchanek from comment #4)

[..]

> What would you expect in that feature?

We, as the team responsible for building the installer, do not set any limits on the initrd size. We rely on our experts to do that. And if we need to meet some requirements, it would be nice to have it clearly documented.