Skip to content

fix(ci): grant ISO smoke runner scoped KVM access - #76

Open
castrojo wants to merge 2 commits into
mainfrom
fix/ci-kvm-runner-access
Open

castrojo wants to merge 2 commits into
mainfrom
fix/ci-kvm-runner-access

Conversation

@castrojo

@castrojo castrojo commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Grant only the hosted runner's current user read/write access to /dev/kvm immediately before each QEMU smoke invocation, using a named-user ACL. Install Ubuntu's acl utility and log the resulting ACL. Device ownership, other-user permissions, accelerator selection, smoke tests, and failure propagation remain unchanged.

Run 42576628747 could not initialize KVM because /dev/kvm returned Permission denied. QEMU fell back to TCG, and the x86_64 VM exited before its smoke window completed. This fixes the observed KVM access failure without world-writable device permissions or running QEMU as root; the unchanged full smoke workflow must establish whether the VM exit is also resolved.

Verification

  • just check: passed.
  • pre-commit run --all-files: passed.
  • actionlint .github/workflows/iso-smoke-test.yml: passed.
  • Standards/spec review: scoped to runner setup and its existing guide; no tests, fixtures, expected outputs, checks, or security baselines changed.
  • Full unchanged smoke run 43535361137 against source build 42574340610 failed. Both invocations retained KVM access (user:runner:rw-, root:kvm ownership, other::---), with no Permission denied or TCG fallback. The x86_64 ISO still exits before its boot window with empty serial output; the arm64 ISO only provides qemu-running evidence. KVM setup is repaired, but this is not a passing boot result.
  • PR image-build checks independently fail because upstream ghcr.io/ublue-os/bluefin:lts is missing (manifest unknown); no image references or failure rules were changed.

No LTS production promotion, tag changes, shared-action edits, new credentials, or bypass merges.

The existing smoke job fails to initialize KVM because /dev/kvm is not writable by the hosted runner user. Grant that user a device ACL rather than changing the smoke test, making the device world writable, or running QEMU as root.

Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@castrojo
castrojo requested a review from a team as a code owner November 14, 2026 00:27
The full unchanged smoke run showed the first QEMU could use KVM while a later invocation again received Permission denied. Scope the existing ACL setup directly before each invocation, preserving every ISO and existing outcome rule.

Assisted-by: GPT-6.1 via GitHub Copilot
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

1 participant