public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Cc: Dimitry Golubovsky
	<golubovsky-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Are root privileges really needed to run kvm?
Date: Wed, 13 Jun 2007 17:34:28 +0300	[thread overview]
Message-ID: <46700074.7060501@qumranet.com> (raw)
In-Reply-To: <466FFF13.8000102-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>

Anthony Liguori wrote:
> Avi Kivity wrote:
>> Dimitry Golubovsky wrote:
>>  
>>> Am I missing anything else root privileges might be needed for?     
>>
>> I think you got it covered.
>>   
>
> One thing to consider is that if a userspace process can create KVM 
> guests, they are capable of pinning large quantities of physical 
> memory.  This could be used as a DoS attack so consider VM creation a 
> privileged operation.
>

Good point.

This will go away when we merge the guest paging patch.  We will still 
pin 4MB per virtual machine for shadow page tables, but that, too, will 
go away when we move to a global limit on the number of shadow page 
tables (say 0.5-1% of total memory, configurable).


-- 
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 14:34 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 [this message]
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
     [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=46700074.7060501@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=anthony-rdkfGonbjUSkNkDKm+mE6A@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