From: Chris Marusich <cmmarusich@gmail.com>
To: 36335@debbugs.gnu.org
Subject: bug#36335: Is /dev/kvm missing ACLs?
Date: Sat, 22 Jun 2019 21:20:03 -0700 [thread overview]
Message-ID: <87sgs1c4r0.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
Hi,
I was trying to run some VMs via "guix system vm", and I noticed that
I didn't have permission to use KVM. This issue can be worked around by
running qemu as root, or by adding yourself to the "kvm" group.
However, I found it curious that the /dev/kvm device didn't have ACLs
granting me access:
--8<---------------cut here---------------start------------->8---
$ getfacl /dev/kvm
getfacl: Removing leading '/' from absolute path names
# file: dev/kvm
# owner: root
# group: kvm
user::rw-
group::rw-
other::---
--8<---------------cut here---------------end--------------->8---
Is it expected that on Guix System, /dev/kvm does not by default receive
ACLs granting me access? I'm logged into a GNOME session via GDM, and I
was under the impression that logind or udevd would automatically set up
ACLs for me to access local devices, such as /dev/kvm and /dev/sr0, in
this case.
Note that I DO have ACLs for some other devices, such as video0:
--8<---------------cut here---------------start------------->8---
$ getfacl /dev/video0
getfacl: Removing leading '/' from absolute path names
# file: dev/video0
# owner: root
# group: video
user::rw-
user:marusich:rw-
group::rw-
mask::rw-
other::---
--8<---------------cut here---------------end--------------->8---
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2019-06-23 4:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 4:20 Chris Marusich [this message]
2019-06-24 19:54 ` bug#36335: Is /dev/kvm missing ACLs? Ludovic Courtès
2019-06-27 6:32 ` Chris Marusich
2019-06-27 13:45 ` Ludovic Courtès
2019-07-01 8:41 ` Danny Milosavljevic
2019-07-10 6:23 ` Chris Marusich
2019-07-10 17:10 ` Ludovic Courtès
2019-07-11 7:18 ` Danny Milosavljevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgs1c4r0.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=36335@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.