Skip to content
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

Failed to kexec boot system #118

Closed
phillxnet opened this issue Jul 29, 2022 · 3 comments
Closed

Failed to kexec boot system #118

phillxnet opened this issue Jul 29, 2022 · 3 comments

Comments

@phillxnet
Copy link
Member

Our image="oem" and installiso="true" Leap15.3.x86_64 profile currently produces an installer iso that fails to KEXEC it's way from the installer to the freshly-transferred/installed image. Resulting in the following message:

"Failed to kexec boot system" with an OK option.

failed-kexec-boot-system

Waiting 1 minute or so, or selecting OK, results in a reboot into the oem/jeos-firstboot image which then works as intended.

Previously, on earlier installer builds with this profile the installed system was successfully invoked form the installer just after the image was transferred to the intended system disk selected in the "Loading ..." step. As per our doc showing the progress of our iso installer here: https://rockstor.com/docs/installation/installer-howto.html

Noting changes in Feburary this year in kiwi-ng regarding expected behaviour of oem images documented here:
https://documentation.suse.com/kiwi/9/single-html/kiwi/index.html#oem-customize
referenced in the following kiwi-ng pr:

Fixed handling of oem reboot settings

OSInside/kiwi#2055

Linking also, in the hope this helps, to kexec changes here:

Prefer file based syscall in kexec when possible

OSInside/kiwi#2155

and a seemingly related recent report upstream re kexec failure here:

"Failed to kexec boot system" when using PXE with AlmaLinux 8.6

OSInside/kiwi#2178

Seen with opensuse Leap 15.3 host and kiwi-ng version:

i+ | python3-kiwi    | package    | 9.24.45-lp153.1.1                             | x86_64 | Virtualization_Appliances_Builder
i  | kiwi-tools      | package    | 9.24.45-lp153.1.1                             | x86_64 | Virtualization_Appliances_Builder
@phillxnet
Copy link
Member Author

Testing an earlier install of python3-kiwi resulting in the same issue arrising:

zypper se -s | grep "^i....python3-kiwi\|^i....kiwi-tools"
i  | kiwi-tools                                                    | package    | 9.24.45-lp153.1.1                                                 | x86_64 | Virtualization_Appliances_Builder
i+ | python3-kiwi                                                  | package    | 9.24.17-150100.3.50.1                                             | x86_64 | repo-sle-update

So this version is thought to pre-date the oem reboot settings changes mentioned above.
Note that we do have different versions of kiwi-tools but still, it is though to be a relevant test.

@phillxnet
Copy link
Member Author

There is an upstream pull request to address this issue. We are awaiting a requested review and it's merge, if that is what happens, before closing this issue post out own tests which are tricky before package update release given the nature and location of the associated fix. I.e. the proposed upstream fix is within the initrd used by the installer itself.

@FroggyFlox
Copy link
Member

There is an upstream pull request to address this issue. We are awaiting a requested review and it's merge, if that is what happens, before closing this issue

The upstream pull request in question (OSInside/kiwi#2183) has now been merged and published as part of kiwi-ng 9.24.48 (https://github.com/OSInside/kiwi/releases/tag/v9.24.48).
Using this latest version installed either from PyPi, or from the OBS repository produces an ISO that installs successfully and reboots without this kexec error. This has been tested in both UEFI and non-UEFI boot mode in a libvirt VM.
I'm thus closing this now. @phillxnet, feel free to re-open, of course, if you see something I missed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants