From: panda23@hush.ai
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Changing vmexit behavior for a running guest
Date: Sat, 17 Dec 2011 14:22:12 +0000 [thread overview]
Message-ID: <20111217142212.5E019E6736@smtp.hushmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
For sandboxing some forms of untrusted code, the risk of a red pill
could be greatly reduced if qemu had "seccomp" mode, i.e., a way for a
guest OS to request that qemu drop any future unwhitelisted vmexit
calls. How complicated would it be to add this functionality to qemu
and which parts of qemu would I need to modify?
Jason
[-- Attachment #2: Type: text/html, Size: 407 bytes --]
reply other threads:[~2011-12-17 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111217142212.5E019E6736@smtp.hushmail.com \
--to=panda23@hush.ai \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).