From: "immersive.excel@gmail.com" <immersive.excel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] chroot jailing...
Date: Sun, 12 Jan 2014 14:17:43 -0500 [thread overview]
Message-ID: <52D2EA57.7050905@gmail.com> (raw)
Would there be any security benefits, without suffering any considerable
relative loss in performance, to (chroot) jailing qemu? Can it,
practically speaking, be done?? Would that be a partial safeguard
against virtual machine escapes? Or is it the case that if a virtual
machine escape takes place, then all bets are probably off? (i.e., you
probably have already pole-vaulted over any filesystem driver/partition
access control mechanisms...) Are there any articles or discussions that
I can be directed to about it? (my focus for now is 64 bit, Intel core
i7...) Are there specific suggestions and/or guidelines for attempting
to do so -or not??
next reply other threads:[~2014-01-12 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 19:17 immersive.excel [this message]
2014-01-13 4:11 ` [Qemu-devel] chroot jailing Stefan Hajnoczi
2014-01-13 4:22 ` immersive.excel
2014-01-13 10:28 ` Markus Armbruster
2014-01-13 14:38 ` Alex Bennée
2014-01-13 17:07 ` immersive.excel
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=52D2EA57.7050905@gmail.com \
--to=immersive.excel@gmail.com \
--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).