On Thu, Sep 23, 2021 at 12:54 PM Adrian Schröter
On Donnerstag, 23. September 2021, 17:59:48 CEST Srinidhi B wrote:
On Thu, 2021-09-23 at 23:42 +0800, Kai Liu wrote:
Thanks. My original question was related. Here in this file the kernel and initrd can be appointed. But it's a machine-wide option, means every worker VM on this machines will use the same kernel & initrd to boot. Thus you will end up building a CentOS package with SLES kernel, for example. This is what I would like to solve, by following how it's done on boo.
Correct. If you want to set different kernel and initrd per build, then you need to follow what Andreas recommended - check what boot-vm-kvm does.
By following that script, I recently managed to configure a worker to build CentOS packages on SLES nodes:
* Install kernel-obs-build on the worker node * sudo ln -s /.build.kernel.kvm /boot/kernel.obs.guest * sudo ln -s /.build.initrd.kvm /boot/initrd.obs.guest
I don't know if this is the correct way of doing things or not, but this is currently working in one of our private OBS instances.
kernel-obs-build is supposed to get installed inside of the VM.
No need for using the .guest links, these are just very last resort hacks..
Is it possible for it to use the standard kernels instead of the kernel-obs-build stuff? I'd much rather reuse the standard kernel builds... -- 真実はいつも一つ!/ Always, there's only one truth!