From: Karim Yaghmour <karim@opersys.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
xen-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Jacques Gelinas <jack@solucorp.qc.ca>
Subject: Re: [Xen-devel] Re: [ANNOUNCE] Xen high-performance x86 virtualization
Date: Thu, 02 Oct 2003 14:42:08 -0400 [thread overview]
Message-ID: <3F7C7180.2020404@opersys.com> (raw)
In-Reply-To: <E1A57B6-0007y9-00@wisbech.cl.cam.ac.uk>
Keir Fraser wrote:
> Full recursion needs full virtualization. Our approach offers much
> better performance in the situations where full virtualization isn't
> required -- i.e., where it's feasible to distribute a ported OS.
I noticed that the SOSP Xen paper briefly mentions Jacques Gelinas' work
on VServers (http://www.solucorp.qc.ca/miscprj/s_context.hc). While
Jacques' work hasn't attracted as much public attention as other Linux
virtualization efforts, I've personally found the approach and concepts
quite fascinating. Among other things, most of the code implementing the
contexts is architecture-independent (save for a few syscalls added to
arch/*/kernel/entry.S). So, thinking aloud here, I'm wondering in what
circumstances I'd prefer using something as architecture specific as
Xen over something as architecture independent as Jacques' VServers?
(Granted VServers can't run Windows, but I'm asking this from the angle
of people looking for resource isolation in the Linux context.) Among
other things, VServers are already in use by many ISPs to provide
simultaneous hosting of many "virtual machines" on the same box while
maintaining strict separation between machines and still providing a
secure environment.
Karim
P.S.:
For those who aren't familiar with Jacques' stuff, have a look at this
document here:
http://www.solucorp.qc.ca/miscprj/s_context.hc?prjstate=1&nodoc=0
The actual concepts implemented in VServers are here:
http://www.solucorp.qc.ca/miscprj/s_context.hc?s1=2&s2=0&s3=0&s4=0&full=0&prjstate=1&nodoc=0
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 514-812-4145
next prev parent reply other threads:[~2003-10-02 18:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 9:17 [ANNOUNCE] Xen high-performance x86 virtualization Ian Pratt
2003-10-02 10:12 ` Lars Marowsky-Bree
2003-10-02 13:21 ` Oliver M. Bolzer
2003-10-02 14:25 ` Karim Yaghmour
2003-10-02 14:37 ` [Xen-devel] " Keir Fraser
2003-10-02 14:45 ` Karim Yaghmour
2003-10-02 14:48 ` Keir Fraser
2003-10-02 15:15 ` John Bradford
2003-10-02 15:30 ` Keir Fraser
2003-10-02 16:39 ` Theodore Ts'o
2003-10-02 17:23 ` Keir Fraser
2003-10-02 18:42 ` Karim Yaghmour [this message]
2003-10-02 18:53 ` Keir Fraser
2003-10-03 1:59 ` Herbert Poetzl
2003-10-03 8:13 ` Ian Pratt
2003-10-03 10:12 ` Andreas Hauser
2003-10-03 10:29 ` Ian Pratt
2003-10-03 11:53 ` Andreas Hauser
2003-10-03 12:40 ` Ian Pratt
2003-10-03 8:19 ` John Bradford
2003-10-03 9:19 ` Keir Fraser
2003-10-03 10:47 ` John Bradford
2003-10-03 13:14 ` Doug McNaught
[not found] <CA95C29D57188841ABB072EA7357C00D02C13377@orsmsx402.jf.intel.com>
2003-10-03 1:50 ` Paul Brett
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=3F7C7180.2020404@opersys.com \
--to=karim@opersys.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jack@solucorp.qc.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xen-devel@lists.sourceforge.net \
/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