From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Are root privileges really needed to run kvm? Date: Wed, 13 Jun 2007 18:33:30 +0300 Message-ID: <46700E4A.50906@qumranet.com> References: <466FAB08.5050902@qumranet.com> <466FFF13.8000102@codemonkey.ws> <46700887.30009@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Dimitry Golubovsky Return-path: In-Reply-To: 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 Dimitry Golubovsky wrote: > Avi, > > On 6/13/07, Avi Kivity wrote: > >> > BTW if qemu_system_x86-64 runs at user privileges, can the memory >> > consumed be subject to whatever per-user limits that may be set >> > systemwide? >> > >> >> That's the intent, but currently this isn't implemented. > > So, expecting that eventually it will be, it seems to be worth > pursuing running kvm at users privileges at the moment memory is being > consumed. Such memory limit control will be easier to implement in > this case rather than if all instances of KVM ran at root. > Sure. Running kvm as a nonprivileged user is a supported and recommended way of working. A virtual machine is subject to all user access restrictions except, at the moment, the memory locking limits. [We could as a temporary measure check against RLIMIT_MEMLOCK, but this seems hardly worthwhile; better to fix the issue instead] -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- 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/