On Dienstag, 28. April 2020, 11:39:34 CEST wrote Berthold Gunreben:

Hi,

I am currently working on updating the OBS z/VM Worker implementation. Currently, package building works without issues, but container building fails. The reason seems to be that I do have a mismatch between installed and running kernel.

In the original implementation, the system just takes the kernel image from the controlling guest to make the actual builder bootable. However, this typically is not kernel-obs-build. Now, the kernel-obs-build package does not provide the image file below /boot/image to make the system bootable via the s390x bootloader zipl. Therefore, I am a bit stuck and don't exactly know how to proceed. There are several possibilities, and I would like to hear what would be a preferred solution:

1. Add the image file to kernel-obs-build for s390x. This would allow me to just use the provided image file to make the target disk bootable.

That is the only solution with stays remain reliable. Linux kernels/udev/... stuff is to different meanwhile between different distribution versions that the matching one needs to get installed. All of the following proposals most likely become too distribution specific IMHO, so they will break in future again.

2. Setup the two stage bootprocess with grub and do a kexec boot during the build process to reboot the worker with the current kernel.

3. Boot the worker over the reader. In that case I would not need zipl and kernel-obs-build would be sufficient to boot. This is similar to booting for Installation.

4. ??? I have no idea what else could be done. Maybe you have some suggestion.

Any suggestions are welcome.

Thanks

Berthold (azouhr@opensuse.org)

-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org