From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-15?Q?Rickard_Borgm=E4ster?= Subject: Re: Kernel with very low memory requirement (~12MB) for domU Date: Fri, 03 Feb 2006 10:07:15 +0100 Message-ID: References: <20060131154830.GA10660@prefect.vdbonline.net> <20060131221308.GA7662@prefect.vdbonline.net> <20060201203426.GA8556@prefect.vdbonline.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Return-path: In-Reply-To: <20060201203426.GA8556@prefect.vdbonline.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org CJ van den Berg wrote: > > "big" is relative I guess. :-) That's about as small as it gets for my > purposes (which is testing netfilter modules). Well, I had a hard time convincing myself that someone would need 802.11 drivers in a domU kernel... ;-) >># xm crate -c crab-domU.cfg name=test1 >>Using config file "crab-domU.cfg". >>Started domain test1 >># >> >>xm list only returns Domain-0 :-( > > > I've had plenty of strange things like this happen when the memory > parameter was border line too small. If it works once though it seems to > work always. Of course I've tried to adjust the memory parameter so that shouldn't be the limiting factor. I do of course want to see that the new kernel will start at all, before trying to get it to boot at ~12MB. However, even after setting memory to 54 it won't start. > If you want you can post your crab-domU.cfg here. That might shed more > light on the problem. I can try booting my local build of that kernel > config with it too. Well... it isn't very sophisticated but here goes: kernel = "/boot/vmlinuz-2.6.16-rc1-vdberg-xenU" memory = 54 disk = ['cow:/crab/.xen/crab-domU.cfg 30,hda1,w'] root = "/dev/hda1 ro" >>Will try a "normal" 2.6.16-rc1 kernel compile now. > > I would imagine that would be a *lot* fatter. I never did that. Instead, I started over and configured myself a new 2.6.16-rc1 kernel. But... that didn't boot either. Now, I think I have to try compile a *stock* 2.6.16-rc1 kernel to see if that will boot at all. Something is wrong. Oh... just got a thought.. Do the dom0 kernel have to be 2.6.16-rc1 aswell...? Best regards Rickard Borgmäster