From: Stefan Hajnoczi <stefanha@gmail.com>
To: "immersive.excel@gmail.com" <immersive.excel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] chroot jailing...
Date: Mon, 13 Jan 2014 12:11:01 +0800 [thread overview]
Message-ID: <20140113041101.GC20389@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <52D2EA57.7050905@gmail.com>
On Sun, Jan 12, 2014 at 02:17:43PM -0500, immersive.excel@gmail.com wrote:
> 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??
Isolating QEMU can be useful to prevent exposing data on the host or
from other guests.
Production systems using libvirt often run QEMU unprivileged and use
SELinux to restrict what resources the process has access to. This way
a QEMU process that has been taken over still cannot get access to much
besides the files it already has open, the network device it uses, etc.
Stefan
next prev parent reply other threads:[~2014-01-13 4:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 19:17 [Qemu-devel] chroot jailing immersive.excel
2014-01-13 4:11 ` Stefan Hajnoczi [this message]
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=20140113041101.GC20389@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=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).