From: Herbert Poetzl <herbert@13thfloor.at>
To: Jerome Warnier <jwarnier@beeznest.net>
Cc: List qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Qemu sandbox for teaching
Date: Sun, 29 May 2005 15:49:12 +0200 [thread overview]
Message-ID: <20050529134912.GA11324@MAIL.13thfloor.at> (raw)
In-Reply-To: <1117302653.4733.12.camel@mobj>
On Sat, May 28, 2005 at 07:50:53PM +0200, Jerome Warnier wrote:
> Le samedi 28 mai 2005 à 14:13 +0100, Paul Brook a écrit :
> > On Saturday 28 May 2005 13:42, Jerome Warnier wrote:
> > > Does someone here have an idea on how to do the following using Qemu,
> > > but I'm open to other suggestions:
> > >
> > > I would like to provide a UNIX CLI sandbox for users to poke around in a
> > > UNIX course. It would be better if available from the web (preferably
> > > without having to install anything on the users' PC), and Free (as in
> > > free speach).
> > > The problem is that I need to give them root access, or at least a
> > > simulation.
> > > It would be even better if we could for instance install RedHat in it,
> > > but it's not really required.
> >
> > It's not really answering your question, but qemu is probably OTT for this. If
> > I was setting this up I'd use UML and a java web based telnet/ssh client.
> Well, I was thinking about what the snapshot feature of qemu could bring
> me.
>
> In fact, I thought about the following solutions:
> - qemu (or whatever other virtualization system)
> - chroot (or specifically dchroot in Debian) and remote telnet or ssh
> access
> - UML
>
> Advantages of every solution:
> - qemu virtualizes a complete machine, which means installation of an OS
> is possible and it is pretty safe (security-wise) to setup
> - chroot is fast to run and pretty safe
> - UML is fast to run and pretty safe
>
> Problems of every solution:
> - qemu is slow, and a lot of virtual machines at the same time on the
> same machine will slow it down and use too much memory, I think (I'm
> talking about 10 people «playing» at the same time). Using only a
> text-mode virtual machine may probably help, though
> - chroot does not allow much and may take time to setup correctly
> - UML is difficult to setup, and needs a kernel patch (even on 2.6?) to
you might want to have a look at linux-vserver
http://linux-vserver.org/
it allows you to have VPS with certain root rights
on a shared host, in a secure manner (no overhead)
HTH,
Herbert
> work
>
>
> > Paul
> --
> Jerome Warnier <jwarnier@beeznest.net>
> BeezNest
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2005-05-29 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 12:42 [Qemu-devel] Qemu sandbox for teaching Jerome Warnier
2005-05-28 13:13 ` Paul Brook
2005-05-28 17:50 ` Jerome Warnier
2005-05-29 13:49 ` Herbert Poetzl [this message]
2005-05-30 9:06 ` Henrik Nordstrom
2005-05-28 13:22 ` Tom Sandholm
2005-05-28 13:31 ` Lennert Buytenhek
2005-05-28 13:37 ` Paul Brook
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=20050529134912.GA11324@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=jwarnier@beeznest.net \
--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).