From: "Rickard Borgmäster" <doktorn@sub.nu>
To: xen-devel@lists.xensource.com
Subject: Kernel with very low memory requirement (~12MB) for domU
Date: Tue, 31 Jan 2006 15:09:18 +0100 [thread overview]
Message-ID: <drnr24$ghi$1@sea.gmane.org> (raw)
Hello,
We are currently working on a master/bachelor level project, producing a
xen + knoppix bootable CD for router simulation. Our task is to provide
students as ourselves with a portable router lab that will run on any
inexpesive PC, enabling students to exercise Cisco CCNA/CCNP level
studies without access to physical equipment.
The goal is run 10x domU with nothing but the quagga/zebra daemons, on a
P3/450MHz computer with 256MB ram.
So far, the CD and it's file systems is put together. We can boot it and
run 6 routers in it's own domU before we run out of memory. And that's
where we are now. We need to reduce the memory requirements for each
domU, and possibly the dom0 later on.
Removing everything we're not dependent of (in make menuconfig) has
reduced the vmlinuz kernel to just over 800KB. Still, it is not possible
to start a domU with less than memory=17 in the config file. Although, I
do think this is possible. Some tests we did last year (Xen 2.0.6
installed in regular desktop system) showed that it was possible to boot
a domU with 2.6.11-xenU kernel with just memory=12 (I hope I remember
this correct).
I've spent a lot of time reading Xen documentation, wiki and lists.
Sometimes I find "evidence" for my theories, like this post:
http://article.gmane.org/gmane.comp.emulators.xen.devel/11459
...where this config is present:
#-------configuration xmsec1-------------------------
kernel = "/boot/vmlinuz-2.6.11-xenU"
ramdisk="/boot/U1_ramdisk.img"
#security reference identifier
ssidref= 0x00010001
memory = 10
name = "xmsec1"
cpu = -1 # leave to Xen to pick
# Number of network interfaces. Default is 1.
nics=1
dhcp="dhcp"
#-----------------------------------------------------
As you can see, Reiner uses 10M for the each domU. Further down his
post, it seems he is even running on less than that. I have no idea on
what he is up to using ramdrives and such. We use an ext2 filesystem in
a file, with cow_scripts from the xen 3 demo live cd.
To sum it up. We need to shrink the memory needed to start a domU down
to somewhere around 12MB. And we do not have much time left to
accomplish it. We'd seriuosly appreciate any feedback or tips on how to
get going.
Thanks in advance,
An by the way, xen is a stunningly cool product.
Best regards
Rickard Borgmäster
next reply other threads:[~2006-01-31 14:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 14:09 Rickard Borgmäster [this message]
2006-01-31 14:36 ` Kernel with very low memory requirement (~12MB) for domU Molle Bestefich
2006-01-31 16:03 ` Rickard Borgmäster
2006-01-31 15:48 ` CJ van den Berg
2006-01-31 17:25 ` Rickard Borgmäster
2006-01-31 22:13 ` CJ van den Berg
2006-02-01 8:41 ` Rickard Borgmäster
2006-02-01 9:58 ` Rickard Borgmäster
2006-02-01 20:34 ` CJ van den Berg
2006-02-03 9:07 ` Rickard Borgmäster
2006-02-03 12:17 ` CJ van den Berg
2006-02-03 13:56 ` Rickard Borgmäster
2006-02-03 14:51 ` CJ van den Berg
2006-02-03 15:17 ` Rickard Borgmäster
2006-02-03 16:48 ` Rickard Borgmäster
2006-02-06 13:11 ` Rickard Borgmäster
2006-02-06 13:45 ` CJ van den Berg
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='drnr24$ghi$1@sea.gmane.org' \
--to=doktorn@sub.nu \
--cc=xen-devel@lists.xensource.com \
/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.