From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: /dev/kvm permissions Date: Sun, 17 Jun 2007 21:52:59 +0300 Message-ID: <4675830B.3020404@qumranet.com> References: <46758112.4030604@ev-en.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Baruch Even Return-path: In-Reply-To: <46758112.4030604-6P1Dz+XQpLLYtjvyW6yDsg@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.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/