mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3008] KVM on Android Studio #1884
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#1884
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @saddy001 on GitHub (Oct 22, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3008
Android Studio throws permission denied on /dev/kvm. From the jail, here are the permissions:
Outer permission is
If we make it chown user:user from the outside, it works shortly but then the ownership changes itself (on start/use of the VM) again into the above. Also the VM crashes on some actions where it does not in normal use.
Is there any quick workaround?
@Vincent43 commented on GitHub (Oct 22, 2019):
Try
firejail --ignore=noroot android-studio(or whatever this app is named). You may need to also dropnogroups.@saddy001 commented on GitHub (Oct 23, 2019):
Thanks, in combination that helped. It might be useful to update the android_studio profile.
@Vincent43 commented on GitHub (Oct 23, 2019):
Theoretically on a modern distro access to
/dev/kvmshould be granted for logged in user through logind. In such case the profile should work out of the box. We usenoroot+nogroupsfor qemu and there were no complaints about that.@saddy001 what distro do you use? Could you try adding:
/etc/udev/rules.d/99-kvm.rulesfile with:SUBSYSTEM=="misc", KERNEL=="kvm", TAG+="uaccess"line inside then reboot and try again with default profile?@saddy001 commented on GitHub (Oct 24, 2019):
It's Ubuntu 18.04.3. The kvm.rules are also working, but even better, because the VM doesn't warn about missing group memberships.
@Vincent43 commented on GitHub (Oct 26, 2019):
I checked that on Ubuntu 19.10
/dev/kvmis accessible throughuaccessby default. I think we can leave this as is and recommend users of older distros above workaround.