Bug 2124239
| Summary: | edge-installer ISO http boot install fails on systems with <4GB RAM | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Mario Cattamo <mcattamo> | ||||
| Component: | osbuild-composer | Assignee: | Image Builder team <osbuilders> | ||||
| Status: | CLOSED MIGRATED | QA Contact: | Mario Cattamo <mcattamo> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 8.7 | CC: | obudai, qzhang, xiaofwan, yih | ||||
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged | ||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-09-18 12:45:13 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Mario Cattamo
2022-09-05 11:13:57 UTC
@xiaofwan May I ask you for help here? You are the expert on booting edge images using libvirt. :) Hi @xiaofwan and @obudai , I have found a similar situation at https://bugzilla.redhat.com/show_bug.cgi?id=1410948 As workaround, I have increased the RAM memory allocated to the VM from 3072MB to 4096MB. It works, it seems that since the installer runs in an in-memory limited to 50% of ram, with 3096MB the file system runs out of space (in RHEL 8.6 x86_64). As a clarification in previous comment, the file system runs out of space in RHEL 8.7 x86_64 not RHEL 8.6 x86_64. Thanks for your clarification, this helps us tremendously. I updated the title to reflect your findings. Same issue can be reproduced on RHEL 8.9 again. [ 8.249671] dracut-initqueue[938]: Warning: can't find installer main image path in .treeinfo [ 8.258199] dracut-initqueue[1063]: % Total % Received % Xferd Average Speed Time Time Time Current [ 8.258326] dracut-initqueue[1063]: Dload Upload Total Spent Left Speed [ 8.608244] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready 98 1159M 98 1136M 0 0 1272M 0 --:--:-- --:--:-- --:--:-- 1271M [ 9.160528] dracut-initqueue[1063]: curl: (23) Failed writing body (3728 != 16384) [ 9.260527] loop: module loaded [ 9.263693] loop0: detected capacity change from 0 to 1191800832 [ 9.283622] dracut-initqueue[1149]: mount: /run/initramfs/squashfs: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. [ 9.288721] dracut: FATAL: Failed to find a root filesystem in /tmp/curl_fetch_url1/install.img. [ 9.292556] dracut: Refusing to continue [ 9.294741] dracut-initqueue[1100]: /lib/dracut-lib.sh: line 465: echo: write error: No space left on device [ 9.294860] dracut-initqueue[1100]: /lib/dracut-lib.sh: line 466: echo: write error: No space left on device [ 9.306580] dracut-initqueue[938]: /lib/anaconda-lib.sh: line 142: printf: write error: No space left on device [ 9.306643] dracut-initqueue[938]: //lib/dracut/hooks/initqueue/online/80-anaconda-netroot.sh: line 92: echo: write error: No space left on device [ 9.319674] printk: systemd-shutdow: 25 output lines suppressed due to ratelimiting [ 9.332607] systemd-shutdown[1]: Syncing filesystems and block devices. [ 9.335753] systemd-shutdown[1]: Sending SIGTERM to remaining processes... [ 9.354227] systemd-shutdown[1]: Sending SIGKILL to remaining processes... Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |