From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Baruch Even <baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: /dev/kvm permissions
Date: Sun, 17 Jun 2007 21:52:59 +0300 [thread overview]
Message-ID: <4675830B.3020404@qumranet.com> (raw)
In-Reply-To: <46758112.4030604-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
Baruch Even wrote:
> Hello,
>
> What do peoples do/think about the permissions for /dev/kvm?
>
> I'm the maintainer for the Debian package and currently the package uses
> a group to control access, for no good reason really. I've seen that
> kqemu in Debian simply uses 0666 permissions and consider doing the same
> for kvm. I wanted to know what others do in other distributions and what
> others think the permissions should be.
>
>
I recommend 0660, and setting /dev/kvm's group to 'kvm'. Users which
need access to kvm can be added to that group.
A udev rule which does this is available in the scripts/ directory in
kvm-userspace.git (not sure if it is packaged).
When kvm stops locking so much memory, I guess this can be relaxed.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-06-17 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 18:44 /dev/kvm permissions Baruch Even
[not found] ` <46758112.4030604-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org>
2007-06-17 18:52 ` Avi Kivity [this message]
[not found] ` <4675830B.3020404-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-17 19:17 ` Baruch Even
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=4675830B.3020404@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=baruch-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox