-
Notifications
You must be signed in to change notification settings - Fork 55
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
max payload size? #665
Comments
Technically, it is possible. |
a UKI image typically contains the distro's initrd or it can be a custom build with the necessary content. I can't say the upper limit but it's more than 16M. I had a UKI that was ~190M and had to make the following modifications to get the new image layout generated:
|
note that this included a code modification because |
Right. We should NOT hardcode. It needs to be fixed. |
Current tools assume that payload image is loaded into a high memory region in 0xFF000000 - 0xFFFFFFFF. This restriction should be removed to let VMM load image into the low memory region to support payloads that have larger size |
I can see a few PRs working to address this. Is there something I could try already and/or any plans to merge those PRs? |
@gaojiaqi7 any comments to this? |
@mythi , feel free to create any PR. We will review. |
AFAICS, there are PRs already open and reviewed to address this. I was checking earlier that are they in a shape I could give them a try or is something else still missing? |
I tried to build an image with a systemd Unified Kernel Image as the payload but the build asserts:
AFAIUI, the spec does not limit the size but says (for firmware files section): "If the section size is 0xFFFFFF then the size is defined by a 32-bit integer that follows the 32-bit section header.". Would it make sense to support this 'extended length' approach?
The text was updated successfully, but these errors were encountered: