From: Tom Sandholm <sandholm@gsinet.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu sandbox for teaching
Date: Sat, 28 May 2005 09:22:23 -0400 [thread overview]
Message-ID: <4298708F.1060607@gsinet.net> (raw)
In-Reply-To: <1117284129.30948.16.camel@mobj>
[-- Attachment #1: Type: text/plain, Size: 2421 bytes --]
Jerome,
Yes.
Using a fairly large server, (i.e. xeon dual with 4Gb ram & 120GB disk),
and installing...
1. Qemu
2. vde (virtual distributed ethernet)
3. tun/tap device drivers (usually kernel module).
I've been able to create 8 conncurrent qemu instances with reasonable
performance.
I recompiled qemu, without sdl, as to get qemu able to run in batch,
without the need of a console window.
I haven't been able to get qemu to run in batch using any of the
redirected console options (like pty, or -nographic option).
I created a script that starts the vde (tun/tap), used as a tunnel from
my home network, to the virtual network that all the qemu instances
connect to.
Then I run a qemu startup script that starts the qemu instance, with
assigned disk image, assigned mac address (remember you'll need
differenct Mac's for each instance), and places it in background.
I then installed Debian "sarge" on a "master qemu instance", and also
install bootcdwrite tools to "image" the newly installed Unix "base".
(of course you'll also want to install ssh services).
Then I "imaged" the live system onto a cdrom image. I can then just
boot the cdrom image, to start-up a qemu-instance, and use the
bootcdwrite command to write the cdrom image to virtual hard disk. Of
course you could just run the qemu-instance fromthe live-run-cdrom ISO,
and just nfs mount a home directory for any form of "perm" storage (of
course you'd NFS mount from the host-os. You may also use the virtual
floppy image to hold qemu-instance specifics, such as hostname,
ipaddress, etc. See the Debian doc's on bootcdwrite for details.
I expect that you may be able to install apache on the host machine, and
use java-webstart to invoke some form of ssh-client, that users would
use to ssh into their assigned qemu-instance engine.
Best of luck
Tom Sandholm
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.
>
>Thanks
>
>
[-- Attachment #2: sandholm.vcf --]
[-- Type: text/x-vcard, Size: 101 bytes --]
begin:vcard
fn:Tom Sandholm
n:Sandholm;Tom
email;internet:sandholm@gsinet.net
version:2.1
end:vcard
next prev parent reply other threads:[~2005-05-28 13:28 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
2005-05-30 9:06 ` Henrik Nordstrom
2005-05-28 13:22 ` Tom Sandholm [this message]
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=4298708F.1060607@gsinet.net \
--to=sandholm@gsinet.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).