|
Bugzilla – Full Text Bug Listing |
| Summary: | [HPS Bug] Dolomite did not create a UEFI boot menu entry for itself | ||
|---|---|---|---|
| Product: | [SUSE Linux Framework One] SUSE Linux Enterprise Server 16.0 | Reporter: | Randy Wright <rwright> |
| Component: | Kernel | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | Critical | ||
| Priority: | P2 - High | CC: | andy.liang, asadeghpour, bryan.gartner, cristine.chang, gail.cheng, glin, jenifer.golmitz, jerry_hoemann, joe.liao, libor.miksik, mchang, rwright, scott.norton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | The attached information is collected from the booted sle-micro disk which is enumerated as /dev/sda. Shown also is information about /dev/sdb which has Dolomite milestone 5 installed. | ||
|
Description
Randy Wright
2023-10-26 20:30:09 UTC
This might be an intended feature, the raw image would be dd to a disk and therefore would be entitled to take control of the default path, /EFI/BOOT/BOOTX64.EFI. This would not require any boot entry as the only thing needed to boot is to choose the disk and it will boot. This might be a preferred way to cloud deployment given the frequent migration to other instances may use a different firmware instance thus all boot entry lost. Anyway let's check with Jiri given this likely to be a feature. Exactly as Michael wrote; The raw disk image (equally the self-install one) are not expected to modify the uEFI menu. When you (user who deployed) booted it for the first time, one can assume that you already did needed arrangements to boot the image. Creating an uEFI entry can be matter of one command: transactional-update bootloaer which would create the uEFI entry or do any other arrangements on other boot architectures, if needed. Running it automatically on first boot is more like a hack (and in fact enforces that, which may not be wanted if one has already created the entry to boot the image). @Randy: Would documenting that be an option? Sorry for the delay, US holiday last week etc Yes documenting would work. And/or a brief message from the installer suggesting if you want an explicit boot entry to use transactional-update bootloader. Either gives information to which I can refer if an internal HPE tester encounters a similar issue. I neglected to clear needinfo when I wrote comment 3. Any further update for the bug? Thank you. I think this was more appropriate to re-target to SL-Micro. I checked SL-Micro 6 and it still doesn't create a UEFI boot entry, but we've discussed previously that was going to be documented. It is reflected in the documentation of Micro 6.0: https://documentation.suse.com/sle-micro/6.0/html/Micro-deployment-selfinstall-images/index.html#deployment-prebuilt-images-efiboot-record Closing this bug as FIXED. I have additionally suggested some improvement to the kiwi developers, no ETA about that. |