Description of problem: The current OS image is based on a regular Fedora kernel. This includes a configuration that has most virtualization drivers that are relevant for kata configured as modules, meaning that they need ot be loaded at boot time. We could build a kernel image optimized for Kata Containers use, with only necessary drivers enabled, and install it uncompressed so that we can boot the Linux image directly using PVH on qemu versions that support it (qemu 4.0 and later, see https://patchwork.kernel.org/patch/10741013/). The primary concerns about doing that are: 1/ Building / maintaining another kernel image (is that OK?) than the official Fedora one 2/ Build time and bulid requirements for the kernel image
It's tough to see Fedora going for something like this. The only non-standard kernel build I can recall them shipping was kernel-xen and that ended a decade ago. arm32 has a separate kernel-lpae build but that's out of necessity to support certain hardware IIRC If/when you want to investigate this, the Fedora side should start with a mail to https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org/ to solicit ideas and recommendations
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
This one is a bug that's still relevant for us, and I'm moving it to the kata-containers component as the packages for 1.x won't be updated after May 12th (as the 1.x project upstream will reach its EOL: http://lists.katacontainers.io/pipermail/kata-dev/2021-April/001843.html)
I believe that things are moving a bit in the right direction regarding the ability to build custom kernels for special use cases. @slopezpa what is the latest you got in that respect?
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This is linked to https://bugzilla.redhat.com/show_bug.cgi?id=2081292, and still applies with today's Fedora. Updating the version field.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days