Repository navigation
Conversation
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>
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>
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.
Summary
Grant only the hosted runner's current user read/write access to
/dev/kvmimmediately before each QEMU smoke invocation, using a named-user ACL. Install Ubuntu'saclutility 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/kvmreturned 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.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 providesqemu-runningevidence. KVM setup is repaired, but this is not a passing boot result.ghcr.io/ublue-os/bluefin:ltsis 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.