-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
R4.2: debian-11 fails to boot with in-vm kernel #8277
Comments
This seems to be caused by initramfs having ~70MB compressed (~230MB uncompressed). Default initial 400MB of RAM is not enough to handle that. 128MB is used for modules (it isn't all of them, the whole modules dir in rootfs takes over 300MB), and then 57MB is used for firmware. Both could be much more limited, but I'm not sure how to do that in an elegant way (to not list all the modules verbatim as that could change between kernel versions and also to leave an option to override by the user). |
The same issue applies to debian-12 too. |
What about keeping only the modules required to mount |
Is the issue directly the amount of RAM used by the uncompressed initramfs, or is it that plus the amount of additional RAM used during the decompression process? I seem to recall reading the latter being an issue for raspberry pi units (some < 1GB RAM) in some distro's recent move to different/newer kernel compression algs, particularly at the higher compression settings...which turned out to need an additional 200MB+ in memory dictionary space at those high compression levels. B |
Hmm, I just found out technically this is a duplicate of #8235, and I guess "not our bug" resolution applies here too. But at the some time, since I've identified it's about initramfs, actually there may be a solution: initramfs.conf has |
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The component
|
This also affects @andrewdavidwong Please re-open. |
@3hhh: Per @marmarek,
backport pending
|
Build initramfs with only required modules, not all of them. Otherwise it's too big to boot with default 400M. Additionally disable looking for suspend-to-disk signature, this feature is never used on Qubes VM (swap device is not persistent). Fixes QubesOS/qubes-issues#8277 (cherry picked from commit 9efc9e3)
Observation
openQA test in scenario qubesos-4.2-update-x86_64-system_tests_pvgrub_salt_storage@64bit fails in
TC_41_HVMGrub_debian-11
All three modes (PV, PVH, HVM) fail to boot with a timeout:
Kernel panic - not syncing: System is deadlocked on memory
If fails with both StandaloneVM, and AppVM.
Test suite description
Try booting debian-11 based VM with an in-vm kernel.
Reproducible
Fails since (at least) Build 2023060606-4.2
Expected result
Last good: 2023053020-4.2 (or more recent)
Further details
Always latest result in this scenario: latest
The text was updated successfully, but these errors were encountered: