Skip to content

bootc-ubuntu-setup: Exclude AMD-SEV OVMF on Ubuntu 26.04 - #58

Merged
cgwalters merged 2 commits into
bootc-dev:mainfrom
cgwalters-bot:fix/ubuntu-2604-ovmf-amdsev
Sep 14, 2026
Merged

cgwalters merged 2 commits into
bootc-dev:mainfrom
cgwalters-bot:fix/ubuntu-2604-ovmf-amdsev

Conversation

@cgwalters-bot

Copy link
Copy Markdown
Contributor

Ubuntu 26.04 splits OVMF firmware variants into separate packages, while the ovmf metapackage pulls all of them in. Its AMD-SEV descriptor can satisfy libvirt's generic secure=no firmware request, causing bcvk GRUB guests to receive stateless SEV firmware that cannot restore their boot entry.

Explicitly select ovmf-generic and exclude ovmf-amdsev while preserving the rest of apt's virtualization recommendations. Add package-state validation and a manual CentOS Stream 10 bcvk libvirt run --firmware=uefi-insecure smoke test that verifies SSH and cleanup.

This fixes the VM failures observed in bootc-dev/bootc#2454.

Testing:

@cgwalters-bot
cgwalters-bot force-pushed the fix/ubuntu-2604-ovmf-amdsev branch 2 times, most recently from 699dcb4 to ff6fb4c Compare September 14, 2026 19:03
Comment thread bootc-ubuntu-setup/action.yml Outdated
Ubuntu Resolute's OVMF metapackage selects AMD-SEV firmware by default, which is not the generic firmware expected by libvirt on these runners. Keep apt's normal recommendations while explicitly installing ovmf-generic and excluding ovmf-amdsev.

Assisted-by: AI
Signed-off-by: Colin Walters <walters@verbum.org>
Verify that Ubuntu 26.04 retains normal virtualization recommendations while selecting generic OVMF and excluding AMD-SEV firmware. Pull-request validation checks package state; manual dispatch carries the CentOS Stream 10 bcvk conversion and SSH probe separately from the required PR gate.

Assisted-by: AI
Signed-off-by: Colin Walters <walters@verbum.org>
@cgwalters-bot
cgwalters-bot force-pushed the fix/ubuntu-2604-ovmf-amdsev branch from ff6fb4c to 57151ed Compare September 14, 2026 19:21
@cgwalters-bot

Copy link
Copy Markdown
Contributor Author

The only failing required check hit a transient Quay 502 Bad Gateway while pulling quay.io/centos-bootc/centos-bootc:stream9; setup and the other matrix jobs passed. I reran the same workflow and branch on the fork, and all three jobs passed: https://github.com/cgwalters-bot/actions/actions/runs/34886804192. I cannot rerun the upstream workflow from the fork account—could a maintainer rerun the failed upstream job?

@cgwalters
cgwalters merged commit 9bce548 into bootc-dev:main Sep 14, 2026
15 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants