fix(examples): 10 declares the lavapipe payload it runs on without a GPU - #569
Merged
Conversation
The README states the artifact runs on the software driver payload when no vendor ICD is present, but the manifest never named it, so a machine with no GPU had no device at all. The example now provisions xim:mesa-lavapipe like its other payloads.
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
2 participants
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.
The README states the artifact runs on the software driver payload when no vendor ICD is present, but the manifest never named
xim:mesa-lavapipe, so a machine with no GPU (the sandbox verification of 2026.9.5.3) had no Vulkan device at all:device unavailable. The example now provisions the payload like its other[xlings.workspace]entries. One-line manifest change plus its comment; no engine change.