All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rickard Borgmäster" <doktorn@sub.nu>
To: xen-devel@lists.xensource.com
Subject: Re: Kernel with very low memory requirement (~12MB) for domU
Date: Fri, 03 Feb 2006 10:07:15 +0100	[thread overview]
Message-ID: <drv6g4$qjs$1@sea.gmane.org> (raw)
In-Reply-To: <20060201203426.GA8556@prefect.vdbonline.net>

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

  reply	other threads:[~2006-02-03  9:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 14:09 Kernel with very low memory requirement (~12MB) for domU Rickard Borgmäster
2006-01-31 14:36 ` 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 [this message]
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='drv6g4$qjs$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.