fix: use linux-image-virtual metapackage for ubuntu 25.10 and 26.04#259
Open
amd-aliem wants to merge 1 commit into
Open
fix: use linux-image-virtual metapackage for ubuntu 25.10 and 26.04#259amd-aliem wants to merge 1 commit into
amd-aliem wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the Ubuntu 25.10 and 26.04 mkosi image definitions to avoid pinning specific kernel package versions that can disappear from Ubuntu repositories over time, which breaks CI image builds. It does so by switching to the linux-image-virtual metapackage so the images track the currently-available kernel without pulling in large firmware/microcode-related packages.
Changes:
- Switch Ubuntu 25.10 host/guest images from a pinned
linux-image-<ver>-generickernel package tolinux-image-virtual. - Switch Ubuntu 26.04 host/guest images from
linux-image-generic+ explicit modules packages tolinux-image-virtual. - Reduce susceptibility to repo churn (point release kernel removals) in mkosi-based image builds.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| images/host-ubuntu-26.04/mkosi.conf | Replace explicit kernel image/modules package set with linux-image-virtual. |
| images/host-ubuntu-25.10/mkosi.conf | Replace pinned kernel image package with linux-image-virtual. |
| images/guest-ubuntu-26.04/mkosi.conf | Replace explicit kernel image/modules package set with linux-image-virtual. |
| images/guest-ubuntu-25.10/mkosi.conf | Replace pinned kernel image/modules package set with linux-image-virtual. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Pinned kernel versions get removed from repos when Ubuntu publishes newer point releases, breaking image builds. Use linux-image-virtual metapackage which tracks the current kernel without pulling in firmware blobs (linux-firmware, intel-microcode, amd64-microcode). Signed-off-by: Amanda Liem <aliem@amd.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use
linux-image-virtualpackage to specify default kernel package for the distro.Pinned kernel versions get removed from repos when Ubuntu publishes newer point releases, breaking image builds:
E: Unable to locate package linux-modules-6.17.0-8-genericin https://github.com/AMDEPYC/sev-certify/actions/runs/28899258652/job/85733213329Use linux-image-virtual metapackage which tracks the current kernel without pulling in firmware blobs (linux-firmware, intel-microcode, amd64-microcode). Using linux-image-virtual vs linux-image-generic appears to save ~500MB. Making the change to 26.04 as well, since that same CI run failed for 26.04 when the host image size became > 1G.
I tested both changes on my fork and got passing results: