All of lore.kernel.org
 help / color / mirror / Atom feed
* RAMDISK-Boot: Not enough RAM for domain 0 allocation.
@ 2008-10-07  7:37 viets
  2008-10-07  8:05 ` Keir Fraser
  0 siblings, 1 reply; 4+ messages in thread
From: viets @ 2008-10-07  7:37 UTC (permalink / raw)
  To: xen-devel

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



 \ \/ /___ _ __   |___ / |___ / / _ \
  \  // _ \ '_ \    |_ \   |_ \| | | |
  /  \  __/ | | |  ___) | ___) | |_| |
 /_/\_\___|_| |_| |____(_)____(_)___/ ting enabled.
                                      tm) Processor 2210 stepping 03
(XEN) Xen version 3.3.0 (root@talentrun.de) (gcc version 4.2.3 (Ubuntu
4.2.3-2ubuntu7)) Tue Oct  7 09:04:36 CEST 2008
(XEN) Latest ChangeSet: unavailableng Node #0
(XEN) Command line: noreboot dom0_mem=2097152 console=com2 com2=115200,8n1
(XEN) Video information:ne check reporting enabled.
(XEN)  VGA is text mode 80x25, font 8x16) Processor 2210 stepping 03
(XEN)  VBE/DDC methods: none; EDID transfer time: 1 seconds
(XEN)  EDID info not retrieved because no DDC retrieval method detected
(XEN) Disc information: method
(XEN)  Found 1 MBR signaturesation across 2 CPUs: passed.
(XEN)  Found 1 EDD information structuresTimer
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e4000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000dfff0000 (usable)0x86a810
(XEN)  00000000dfff0000 - 00000000dfffe000 (ACPI data)
(XEN)  00000000dfffe000 - 00000000e0000000 (ACPI NVS)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec01000 (reserved)
(XEN)  00000000fee00000 - 00000000fef00000 (reserved)
(XEN)  00000000ff780000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000120000000 (usable)
(XEN) System RAM: 4095MB (4193852kB)
(XEN) ACPI: RSDP 000FAE30, 0024 (r2 ACPIAM)
(XEN) ACPI: XSDT DFFF0100, 004C (r1 A M I  OEMXSDT  12000613 MSFT       97)
(XEN) ACPI: FACP DFFF0290, 00F4 (r3 A M I  OEMFACP  12000613 MSFT       97)
(XEN) ACPI: DSDT DFFF04A0, 5EB0 (r1  S39_3 S39_3B13      B13 INTL 20051117)
(XEN) ACPI: FACS DFFFE000, 0040
(XEN) ACPI: APIC DFFF0390, 0076 (r1 A M I  OEMAPIC  12000613 MSFT       97)
(XEN) ACPI: SPCR DFFF0410, 0050 (r1 A M I  OEMSPCR  12000613 MSFT       97)
(XEN) ACPI: OEMB DFFFE040, 0060 (r1 A M I  AMI_OEM  12000613 MSFT       97)
(XEN) ACPI: SRAT DFFF6350, 00C8 (r1 AMD    HAMMER          1 AMD         1)
(XEN) Xen heap: 14MB (14636kB)
(XEN) Domain heap initialised
(XEN) Processor #0 15:1 APIC version 16
(XEN) Processor #1 15:1 APIC version 16
(XEN) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 1809.325 MHz processor.
(XEN) AMD SVM: ASIDs disabled.
(XEN) HVM: SVM enabled
(XEN) CPU0: AMD K8 machine check reporting enabled.
(XEN) CPU0: AMD Dual-Core AMD Opteron(tm) Processor 2210 stepping 03
(XEN) Booting processor 1/1 eip 8c000
(XEN) AMD: Disabling C1 Clock Ramping Node #0
(XEN) AMD SVM: ASIDs disabled.
(XEN) CPU1: AMD K8 machine check reporting enabled.
(XEN) CPU1: AMD Dual-Core AMD Opteron(tm) Processor 2210 stepping 03
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 2 CPUs
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, lsb, paddr 0x200000 -> 0x86a810
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Not enough RAM for domain 0 allocation.
(XEN) ****************************************
(XEN)
(XEN) Manual reset required ('noreboot' specified)

After some researching, I've found this
thread(http://lists.xensource.com/archives/html/xen-devel/2008-08/msg00518.html),
but the solution doesn't work for me.

Thanks in advance

greetings
Torben Viets

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: RAMDISK-Boot: Not enough RAM for domain 0 allocation.
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Keir Fraser @ 2008-10-07  8:05 UTC (permalink / raw)
  To: viets@work.de, xen-devel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: RAMDISK-Boot: Not enough RAM for domain 0 allocation.
  2008-10-07  8:05 ` Keir Fraser
@ 2008-10-07  8:08   ` viets
  2008-10-07  8:14     ` Keir Fraser
  0 siblings, 1 reply; 4+ messages in thread
From: viets @ 2008-10-07  8:08 UTC (permalink / raw)
  To: Keir Fraser; +Cc: xen-devel

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: RAMDISK-Boot: Not enough RAM for domain 0 allocation.
  2008-10-07  8:08   ` viets
@ 2008-10-07  8:14     ` Keir Fraser
  0 siblings, 0 replies; 4+ messages in thread
From: Keir Fraser @ 2008-10-07  8:14 UTC (permalink / raw)
  To: viets@work.de; +Cc: xen-devel

Xen wants to allocate smallest power-of-two sized memory block which will
fit both kernel and initrd. This will be 2GB on your system, and there is no
such 2GB aligned block. Either this restriction of the domain builder needs
to be lifted (a bit of a pain and not really on anyone's todo list), or you
could just reduce your initrd size by 100MB and cross your fingers -- it's
likely that Xen will be able to find an aligned 1GB memory block.

 -- Keir

On 7/10/08 09:08, "viets@work.de" <viets@work.de> wrote:

> 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
>> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-10-07  8:14 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2008-10-07  8:14     ` Keir Fraser

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.