From: Sasha Levin <levinsasha928@gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Pekka Enberg <penberg@kernel.org>,
Cyrill Gorcunov <gorcunov@gmail.com>,
Asias He <asias.hejun@gmail.com>,
Anthony Liguori <anthony@codemonkey.ws>,
"Michael S. Tsirkin" <mst@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Secure KVM
Date: Mon, 07 Nov 2011 08:29:03 +0200 [thread overview]
Message-ID: <1320647343.3202.3.camel@lappy> (raw)
In-Reply-To: <877h3cu75a.fsf@rustcorp.com.au>
On Mon, 2011-11-07 at 10:37 +1030, Rusty Russell wrote:
> On Sun, 06 Nov 2011 22:40:20 +0200, Sasha Levin <levinsasha928@gmail.com> wrote:
> > The solution is also simple to explain: Split the devices into different
> > processes and use seccomp to sandbox each device into the exact set of
> > resources it needs to operate, nothing more and nothing less.
>
> lguest does a process per device. Actually, it uses clone for legacy
> reasons, but I have a patch which changes it to processes.
>
> It works well, and it's *simple*. I suggest looking at
> Documentation/virtual/lguest/lguest.c.
>
> Good luck!
> Rusty.
Yup, thats pretty much what I want to have.
As you said, clone() isn't really an option - sharing things like the VM
and handles is something which I want to avoid. How does your patch
handle IPC?
--
Sasha.
next prev parent reply other threads:[~2011-11-07 6:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 20:40 Secure KVM Sasha Levin
2011-11-07 0:07 ` Rusty Russell
2011-11-07 6:29 ` Sasha Levin [this message]
2011-11-07 6:37 ` Pekka Enberg
2011-11-07 6:46 ` Sasha Levin
2011-11-07 7:03 ` Pekka Enberg
2011-11-07 22:49 ` Rusty Russell
2011-11-07 9:26 ` Avi Kivity
2011-11-07 10:17 ` Sasha Levin
2011-11-07 10:27 ` Avi Kivity
2011-11-07 11:27 ` Stefan Hajnoczi
2011-11-07 12:40 ` Sasha Levin
2011-11-07 12:51 ` Avi Kivity
2011-11-07 14:56 ` Stefan Hajnoczi
2011-11-07 17:43 ` Anthony Liguori
2011-11-07 18:41 ` Avi Kivity
2011-11-07 17:39 ` Anthony Liguori
2011-11-07 18:43 ` Avi Kivity
2011-11-07 19:07 ` Anthony Liguori
2011-11-07 19:54 ` Avi Kivity
2011-11-07 22:56 ` Rusty Russell
2011-11-07 17:37 ` Anthony Liguori
2011-11-07 17:37 ` [Qemu-devel] " Anthony Liguori
2011-11-07 17:52 ` Sasha Levin
2011-11-07 17:52 ` [Qemu-devel] " Sasha Levin
2011-11-07 18:03 ` Anthony Liguori
2011-11-07 18:03 ` Anthony Liguori
2011-11-07 23:06 ` Rusty Russell
2011-11-07 23:06 ` Rusty Russell
2011-11-08 19:51 ` Will Drewry
2011-11-08 19:51 ` [Qemu-devel] " Will Drewry
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=1320647343.3202.3.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=aarcange@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=asias.hejun@gmail.com \
--cc=avi@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=penberg@kernel.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.