All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <levinsasha928@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: kvm@vger.kernel.org, mingo@elte.hu, asias.hejun@gmail.com,
	gorcunov@gmail.com
Subject: Re: [PATCH 2/2] kvm tools: Allow easily sandboxing applications within a guest
Date: Fri, 02 Dec 2011 09:35:28 +0200	[thread overview]
Message-ID: <1322811328.8778.1.camel@lappy> (raw)
In-Reply-To: <CAOJsxLEOYE3PGKvGuURk9aBQkAztZKE3dYseu2SVt9orE1iBeA@mail.gmail.com>

On Fri, 2011-12-02 at 09:26 +0200, Pekka Enberg wrote:
> On Fri, Dec 2, 2011 at 9:16 AM, Sasha Levin <levinsasha928@gmail.com> wrote:
> > This patch adds a '--sandbox' argument when used in conjuction with a custom
> > rootfs, it allows running a script or an executable in the guest environment
> > by using executables and other files from the host.
> >
> > This is useful when testing code that might cause problems on the host, or
> > to automate kernel testing since it's now easy to link a kvm tools test
> > script with 'git bisect run'.
> >
> > Suggested-by: Ingo Molnar <mingo@elte.hu>
> > Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
> 
> Nice! How do I use this to run trinity sandboxed in a guest?

Assuming you have trinity installed in /usr/bin or something similar in
on the host (you can just 'cp trinity /usr/bin/'), just write this
script:

test-trinity.sh:
	#! /bin/bash
	trinity --mode=random --quiet -i

and run using:
	./kvm run -k [kernel to test] --sandbox test-trinity.sh

-- 

Sasha.


  reply	other threads:[~2011-12-02  7:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  7:16 [PATCH 1/2] kvm tools: Remove double 'init=' kernel param Sasha Levin
2011-12-02  7:16 ` [PATCH 2/2] kvm tools: Allow easily sandboxing applications within a guest Sasha Levin
2011-12-02  7:26   ` Pekka Enberg
2011-12-02  7:35     ` Sasha Levin [this message]
2011-12-02  7:39       ` Pekka Enberg
2011-12-02  7:44         ` Sasha Levin
2011-12-02  7:47           ` Pekka Enberg
2011-12-04 10:25   ` Avi Kivity
2011-12-04 12:11     ` Sasha Levin

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=1322811328.8778.1.camel@lappy \
    --to=levinsasha928@gmail.com \
    --cc=asias.hejun@gmail.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@kernel.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 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.