From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: http://sf.net/projects/xen
Date: Tue, 23 Nov 2004 17:02:07 +0000 [thread overview]
Message-ID: <20041123170207.GA6250@lkcl.net> (raw)
In-Reply-To: <20041122103142.GA4400@rns-nis.co.yu>
On Mon, Nov 22, 2004 at 11:31:42AM +0100, Milan P. Stanic wrote:
> On Sat, Nov 20, 2004 at 08:40:20PM +0000, Luke Kenneth Casson Leighton wrote:
> > vmware, _and_ who also don't want the slowness or features of UML,
>
> When I backported SELinux from Debian/unstable to woody, I did that
> using UML only. I didn't had any problem with UML, only with my own
> slowness :-)
:)
this page demonstrates it best:
http://www.cl.cam.ac.uk/Research/SRG/netos/xen/performance.html
also, UML, unless it is patched (yes someone has provided
such patches), provides the host running the UML linux apps
with direct access to their kernel memory - for debugging
purposes, obviously.
i'm evaluating xen as a means to run applications like mozilla
in an isolated selinux machine (!) also to suspend them down
to disk, and use xen to start an entire virtual machine up
when a user needs to run the application (!)
my only concern is how to stop absolutely anyone from running
a xen guest OS: management of xen is done on port 8000.
l.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2004-11-23 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 20:40 http://sf.net/projects/xen Luke Kenneth Casson Leighton
2004-11-21 1:05 ` http://sf.net/projects/xen Luke Kenneth Casson Leighton
2004-11-22 10:31 ` http://sf.net/projects/xen Milan P. Stanic
2004-11-23 17:02 ` Luke Kenneth Casson Leighton [this message]
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=20041123170207.GA6250@lkcl.net \
--to=lkcl@lkcl.net \
--cc=selinux@tycho.nsa.gov \
/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.