-
-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bootc-native way to do configure-vfio or remove it? #1966
Comments
configure-vfio enables |
I believe sysexts also cant really help out with this either |
The fedora docs mention that "When using bootc install, it is possible to add install-time kernel arguments both in the container image, and via bootc install --karg. "Day 2 updatable" kernel arguments are supported as well." |
Oh. We could change it into a service that automatically does this weird workaround mentioned on https://docs.fedoraproject.org/en-US/bootc/kernel-args/. - Although to be completely honest I feel like this shouldn't be supported by Bluefin directly, we should just let it be a separate project or something that sets up that. |
Kargs are the easiest i would say since we need that in bazzite anyway
for bluefin and aurora obviously this can be done and enabled on the the |
The solution we are going for in bazzite (currently in testing) is to include the vfio modules in initramfs by default, if they cause any issues we set them to blacklisted by default. everything else is set using kernel arguments |
We need to find some more integrated way to do the configure-vfio thing, either by having a separate image for it, including it on the main images, or just getting rid of it entirely as we are trying to move to a bootc-only future.
The text was updated successfully, but these errors were encountered: