The output from Seth's grep (in the bug description) is a little misleading because the archival of kernel configs on kernel.ubuntu.com is buggy. It is including kernel configs of the generic, lowlatency, etc., kernels in the directories of the derivative kernels. For example, these config files should not exist because the linux-kvm source package does not produce an i386 generic or lowlatency binary package:
The output from Seth's grep (in the bug description) is a little misleading because the archival of kernel configs on kernel.ubuntu.com is buggy. It is including kernel configs of the generic, lowlatency, etc., kernels in the directories of the derivative kernels. For example, these config files should not exist because the linux-kvm source package does not produce an i386 generic or lowlatency binary package:
cosmic/ linux-kvm/ 4.15.0- 1008.8/ i386-config. flavour. generic linux-kvm/ 4.15.0- 1008.8/ i386-config. flavour. lowlatency
cosmic/
If we inspect the directory contents while logged into kernel.ubuntu.com, we see this:
$ ls -1 ~kernel- ppa/public_ html/config/ cosmic/ linux-kvm/ 4.15.0- 1008.8/ config. flavour. generic config. flavour. kvm config. flavour. lowlatency config. flavour. generic config. flavour. snapdragon config. flavour. generic config. flavour. generic- lpae flavour. generic flavour. lowlatency config. flavour. generic config. flavour. generic
amd64-
amd64-
amd64-
arm64-
arm64-
armhf-
armhf-
i386-config.
i386-config.
ppc64el-
s390x-
Of those files, only amd64-config. flavour. kvm is valid for linux-kvm and it does not contain CONFIG_ BINFMT_ AOUT=m because it is a 64 bit kernel.