all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 36335@debbugs.gnu.org
Subject: bug#36335: Is /dev/kvm missing ACLs?
Date: Mon, 24 Jun 2019 21:54:54 +0200	[thread overview]
Message-ID: <87v9wu4v3l.fsf@gnu.org> (raw)
In-Reply-To: <87sgs1c4r0.fsf@gmail.com> (Chris Marusich's message of "Sat, 22 Jun 2019 21:20:03 -0700")

Hi Chris,

Chris Marusich <cmmarusich@gmail.com> skribis:

> 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:
>
> $ getfacl /dev/kvm
> getfacl: Removing leading '/' from absolute path names
> # file: dev/kvm
> # owner: root
> # group: kvm
> user::rw-
> group::rw-
> other::---
>
>
> Is it expected that on Guix System, /dev/kvm does not by default receive
> ACLs granting me access?

Guix System doesn’t use ACLs at all.

However, the udev rule for kvm sets it up like this:

  crw-rw---- 1 root kvm 10, 232 Jun 24 08:38 /dev/kvm

and the build users are part of the ‘kvm’ group.  I personally arrange
to have my user account in that group too.

Thanks,
Ludo’.

  reply	other threads:[~2019-06-24 19:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-23  4:20 bug#36335: Is /dev/kvm missing ACLs? Chris Marusich
2019-06-24 19:54 ` Ludovic Courtès [this message]
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=87v9wu4v3l.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36335@debbugs.gnu.org \
    --cc=cmmarusich@gmail.com \
    /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.