initrd hostonly-kernel-modules.txt varies from CPU

[bmwiedemann]

While working on reproducible builds for openSUSE, I found that our kernel-obs-build package that contained a dracut-generated initrd would vary between VMs on different hosts, if those had different CPUs.

With commit 7047294 the diff was only about crc32c_intel but since 0ef8f50 this has grown.

+++ new//.build.initrd.kvm.cpio.extract/lib/dracut/hostonly-kernel-modules.txt      2019-08-08 14:57:58.190102238 +0000
@@ -8,13 +8,6 @@
 ata_generic
 virtio_rng
 qemu_fw_cfg
-aesni_intel
-ghash_clmulni_intel
-crc32c_intel
-crc32_pclmul
-crct10dif_pclmul
-sb_edac
-intel_rapl
 acpi_cpufreq

@ryncsn - I'd like to get identical build results on different build hosts. How could we get there?

[haraldh]

Just build a non-hostonly initrd

[haraldh]

and specify the dracut modules to include

[ryncsn]

Hi, if you are make a hostonly build that is expected to be different per host, as it is a "host only" imag.
You can either make it a non hostonly image, or maybe I can make a PR to let the hostonly-kernel-modules.txt only be generated when "strict" host only mode is used. What do you think, does a non-hostonly image solution works for you?

[bmwiedemann]

We build it hostonly in KVM because we know it will only ever be run in KVM in the Open Build Service (OBS) and we need the small size to keep its performance impact low.

The other use-case is around katacontainer images.

So would be nice to have a mode where we skip the hostonly-kernel-modules.txt creation.

[haraldh]

Reopen, if PR #624 does not fix your issue