All of lore.kernel.org
 help / color / mirror / Atom feed
From: "viets@work.de" <viets@work.de>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: RAMDISK-Boot: Not enough RAM for domain 0 allocation.
Date: Tue, 07 Oct 2008 10:08:46 +0200	[thread overview]
Message-ID: <48EB190E.2010609@work.de> (raw)
In-Reply-To: <C510D6E5.1DEF1%keir.fraser@eu.citrix.com>

Hello,

the image has a size of 1048576 kilobytes uncompressed.

greetings
Torben

Keir Fraser wrote:
> On 7/10/08 08:37, "viets@work.de" <viets@work.de> wrote:
> 
>> Hello,
>> I'm trying to boot xen-3.3 from network with linux on a ramdisk, but
>> this fails with the output below:
>>
>> this are my boot-settings:
>>
>> default xen-linux
>> prompt 1
>> timeout 10
>>
>> label xen-linux
>>   kernel mboot.c32
>>   append xen-3.3.0.gz noreboot dom0_mem=2097152 console=com2
>> com2=115200,8n1 --- vmlinuz-2.6.18.8-xen0 root=/dev/ram
>> ramdisk_size=1048576 console=tty0 console=ttyS1,115200 --- jobserver.img.gz
>>
> 
> How big is the ramdisk image, uncompressed?
> 
>  -- Keir
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 


-- 
Torben Viets                              w               Viets@work.de
n@work Internet Informationssysteme GmbH  o      http://support.work.de
Wandalenweg 5                             r   Tel.: +49 40 23 88 09 - 0
D-20097 Hamburg                           k   Fax:  +49 40 23 88 09 -29
HR B 61 668  - Amtsgericht Hamburg 	      	      Gf Jan Diegelmann

  reply	other threads:[~2008-10-07  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07  7:37 RAMDISK-Boot: Not enough RAM for domain 0 allocation viets
2008-10-07  8:05 ` Keir Fraser
2008-10-07  8:08   ` viets [this message]
2008-10-07  8:14     ` Keir Fraser

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=48EB190E.2010609@work.de \
    --to=viets@work.de \
    --cc=keir.fraser@eu.citrix.com \
    --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.