public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Dimitry Golubovsky <golubovsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Are root privileges really needed to run kvm?
Date: Wed, 13 Jun 2007 18:33:30 +0300	[thread overview]
Message-ID: <46700E4A.50906@qumranet.com> (raw)
In-Reply-To: <bcba51a0706130826r60175d04r3e8a402f2c8f6271-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Dimitry Golubovsky wrote:
> Avi,
>
> On 6/13/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> 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/

  parent reply	other threads:[~2007-06-13 15:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 13:19 Are root privileges really needed to run kvm? Dimitry Golubovsky
     [not found] ` <bcba51a0706110619q661628b6lfd6b6968ad893c59-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-13  8:30   ` Avi Kivity
     [not found]     ` <466FAB08.5050902-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-13 14:28       ` Anthony Liguori
     [not found]         ` <466FFF13.8000102-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-06-13 14:34           ` Avi Kivity
2007-06-13 15:01           ` Dimitry Golubovsky
     [not found]             ` <bcba51a0706130801r79a77751m31d46aac630c3e80-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-13 15:08               ` Avi Kivity
     [not found]                 ` <46700887.30009-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-13 15:26                   ` Dimitry Golubovsky
     [not found]                     ` <bcba51a0706130826r60175d04r3e8a402f2c8f6271-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-13 15:33                       ` Avi Kivity [this message]
     [not found]                         ` <46700E4A.50906-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-06-13 15:39                           ` Dimitry Golubovsky
     [not found]                             ` <bcba51a0706130839l143bb209pfc4ee664ce20f300-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-06-13 15:54                               ` Avi Kivity
2007-06-13 15:10               ` Anthony Liguori

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=46700E4A.50906@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=golubovsky-Re5JQEeQqe8AvxtiuMwx3w@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