Add user to kvm (and cvdnetwork) group when podcvd-setup is executed#2590
Merged
Conversation
GoogleCuttlefishTesterBot
removed
the
kokoro:force-run
k311093
reviewed
May 20, 2026
k311093
approved these changes
May 20, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
GoogleCuttlefishTesterBot
removed
the
kokoro:force-run
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
3 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.
There was an observed issue that ACL setting is flushed but not recovered as udev change action is triggered while creating Cuttlefish instance, on some machines(not all). This PR suggests adding user to the groups owning /dev/kvm, /dev/vhost-net, and /dev/vhost-vsock, which can ensure launching Cuttlefish instances multiple time be safe at least after rebooting(or re-login).
Split from #2580
Context: b/514558958