WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Physical Memory arrangement

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Physical Memory arrangement
From: "Gianluca Mardente" <gianluca.mardente@xxxxxxxxx>
Date: Tue, 1 Jul 2008 19:44:50 -0700
Cc:
Delivery-date: Tue, 01 Jul 2008 19:45:24 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=eF9nxCZK+twlEo89+F/35Ph/nY1/mHMzzaMuxilJheA=; b=s6fS/wB8+YWZgI9UIWowWOdUa/j5jXgZxtKgQThEq07WrRdQhhKA0x8i8qhJi9gnSV bzWs2T0PG61vVUIAW27Lr5aqdGnFTJ67cqeqieQRd97PN+GwSrympfeVn/MiicZ3aYbQ gCMEqkpVyvFpgih11kEHEhDOlPrQ8Lv6SqyOc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=LUL2A6hR8SsKUjwgjCtfUl0AKp8Is9NEURIBqh58398akc8i2AYHQc7YDUgI1Zivvr gDpyztoHr78QZhtarkue9bhB4Vf1EzzMLTjmh6mbhfIc2Z3b5eLPpEHqUNvVRXU2jMk+ MxjHfLm34WrVSpu29eNYiOr4O9iTFtauP4Wms=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,
 I have a system with 2G of RAM. I'm trying to built a rootfilesytem
over ram disk to boot XEN, but I keep getting the following error:

(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Domain 0 allocation is too small for kernel image.
(XEN) ****************************************

I didn't understant it, so I looked at the XEN's boot process output
in two different cases: when I use an initial ramdisk and when I use a
root filesystem over ramdisk.

When I use an initial ramdisk, I can boot XEN and Dom0 without any
problem. Besides, I noticed that

(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (470953 pages
to be all
              ocated)

so the reason I'm getting the error message when I use a root
filesystem (much bigger than 33M) could be that XEN does not allocate
enough RAM to load the Dom0 kernel and the ram disk.

If that's the problem, does anyone know how to fix that? ramdisk_size
doesn't seem to work.

I'm putting here also the output when I use an inital filesystem (so
when I'm able to start XEN)

(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007d681000 (usable)
(XEN)  000000007d681000 - 000000007d6ce000 (ACPI NVS)
(XEN)  000000007d6ce000 - 000000007e5f3000 (usable)
(XEN)  000000007e5f3000 - 000000007e5ff000 (reserved)
(XEN)  000000007e5ff000 - 000000007e6a3000 (usable)
(XEN)  000000007e6a3000 - 000000007e6a4000 (ACPI NVS)
(XEN)  000000007e6a4000 - 000000007e6a7000 (ACPI data)
(XEN)  000000007e6a7000 - 000000007e6f2000 (ACPI NVS)
(XEN)  000000007e6f2000 - 000000007e6ff000 (ACPI data)
(XEN)  000000007e6ff000 - 000000007e700000 (usable)
(XEN)  000000007e700000 - 000000007f000000 (reserved)
(XEN)  00000000ffe00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2021MB (2070440
(XEN) Xen heap: 9MB (10188kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE enabled, limit: 16 GB
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2400.118 MHz processor.
(XEN) HVM: VMX enabled
(XEN) VMX: MSR intercept bitmap enabled
(XEN) CPU0: Intel(R) Core(TM)2 CPU         E6600  @
(XEN) Booting processor 1/1 eip 90000
(XEN) CPU1: Intel(R) Core(TM)2 CPU         E6600  @ 2.40GHz stepping
05
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Platform timer overflows in 234 jiffies.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0xc1000000 memsz=0x2d347c
(XEN) elf_parse_binary: phdr: paddr=0xc12d4000 memsz=0x12d000
(XEN) elf_parse_binary: memory: 0xc10
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0xc0000000
(XEN) elf_xen_parse_note: ENTRY = 0xc1000000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc1001000
(XEN) elf_xen_parse_note: HV_START_LOW = 0xf5800000
(XEN) elf_xen_parse_note: FEATURES =
"writable_page_tables|writable_descriptor_t
ables|auto_translated_physmap|pae_pgdir_a
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xc0000000
(XEN)     elf_paddr_offset = 0xc0000000
(XEN)     virt_offset      = 0x0
(XEN)     virt_kstart      = 0xc1000000
(XEN)     virt_kend        = 0xc1401000
(XEN)     virt_entry       = 0xc1000000
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc1000000 -> 0xc1401000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   000000003c000000->000000003e000000 (470953 pages
to be all
                 ocated)
......

and when I use a rootfilesystem over ramdisk

(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e0000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007d681000 (usable)
(XEN)  000000007d681000 - 000000007d6ce000 (ACPI NVS)
(XEN)  000000007d6ce000 - 000000007e5f3000 (usable)
(XEN)  000000007e5f3000 - 000000007e5ff000 (reserved)
(XEN)  000000007e5ff000 - 000000007e6a3000 (usable)
(XEN)  000000007e6a3000 - 000000007e6a4000 (ACPI NVS)
(XEN)  000000007e6a4000 - 000000007e6a7000 (ACPI data)
(XEN)  000000007e6a7000 - 000000007e6f2000 (ACPI NVS)
(XEN)  000000007e6f2000 - 000000007e6ff000 (ACPI data)
(XEN)  000000007e6ff000 - 000000007e700000 (usable)
(XEN)  000000007e700000 - 000000007f000000 (reserved)
(XEN)  00000000ffe00000 - 0000000100000000 (reserved)
(XEN) System RAM: 2021MB (2070440
(XEN) Xen heap: 9MB (10188kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) PAE enabled, limit: 16 GB
(XEN) Processor #0 6:15 APIC version 20
(XEN) Processor #1 6:15 APIC version 20
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2400.137 MHz processor.
(XEN) HVM: VMX enabled
(XEN) VMX: MSR intercept bitmap enabled
(XEN) CPU0: Intel(R) Core(TM)2 CPU         E6600  @
(XEN) Booting processor 1/1 eip 90000
(XEN) CPU1: Intel(R) Core(TM)2 CPU         E6600  @ 2.40GHz stepping
05
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Platform timer overflows in 234 jiffies.
(XEN) Platform timer is 3.579MHz ACPI PM Timer
(XEN) Brought up 2 CPUs
(XEN) *** LOADING DOMAIN 0 ***
(XEN) elf_parse_binary: phdr: paddr=0xc1000000 memsz=0x2d347c
(XEN) elf_parse_binary: phdr: paddr=0xc12d4000 memsz=0x12d000
(XEN) elf_parse_binary: memory: 0xc10
(XEN) elf_xen_parse_note: GUEST_OS = "linux"
(XEN) elf_xen_parse_note: GUEST_VERSION = "2.6"
(XEN) elf_xen_parse_note: XEN_VERSION = "xen-3.0"
(XEN) elf_xen_parse_note: VIRT_BASE = 0xc0000000
(XEN) elf_xen_parse_note: PADDR_OFFSET = 0xc0000000
(XEN) elf_xen_parse_note: ENTRY = 0xc1000000
(XEN) elf_xen_parse_note: HYPERCALL_PAGE = 0xc1001000
(XEN) elf_xen_parse_note: HV_START_LOW = 0xf5800000
(XEN) elf_xen_parse_note: FEATURES =
"writable_page_tables|writable_descriptor_t
ables|auto_translated_physmap|pae_pgdir_a
(XEN) elf_xen_parse_note: PAE_MODE = "yes"
(XEN) elf_xen_parse_note: unknown xen elf note (0xd)
(XEN) elf_xen_parse_note: LOADER = "generic"
(XEN) elf_xen_parse_note: SUSPEND_CANCEL = 0x1
(XEN) elf_xen_addr_calc_check: addresses:
(XEN)     virt_base        = 0xc0000000
(XEN)     elf_paddr_offset = 0xc0000000
(XEN)     virt_offset      = 0x0
(XEN)     virt_kstart      = 0xc1000000
(XEN)     virt_kend        = 0xc1401000
(XEN)     virt_entry       = 0xc1000000
(XEN)  Xen  kernel: 32-bit, PAE, lsb
(XEN)  Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc1000000 -> 0xc1401000
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Domain 0 allocation is too small for kernel image.
(XEN) ****************************************
(XEN)


Thanks,
  Gianluca

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Physical Memory arrangement, Gianluca Mardente <=