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/
Home Products Support Community News


[Xen-devel] rootfs as RAMDisk + Hypervisor: Cannot allocate memory

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] rootfs as RAMDisk + Hypervisor: Cannot allocate memory
From: Robyn Bachofer <r.bachofer@xxxxxxxxxxxxxx>
Date: Thu, 7 Oct 2010 13:21:24 +0200
Delivery-date: Thu, 07 Oct 2010 04:22:24 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=dy7w9T/bkY9LwqArAfuu+ojw2mSWi5wZzNp5sbf/GkQ=; b=qfOOQ8anxYKUW2+UL1bVQObdIsuSAj3ZP8aAtGUB13WdtvJ2schwDSqoXEYKwwvLRK jxS+Ud9exXj8lUAiq6Q2NGxH2Sc1BkZmmGHftwzewV6J6KaJL6Dsbe8045KmCZV0ZWhL Rkb7lOAN8gj426xGswtB4/Jd2ygPS8w6RxbSM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=rNO6GzJHDZQRoG3JSLYaqtB4gs70DLKRhrHiWJs9keeSuIG6A0Mxd+BAu6PetFzfB9 tuAm0YLjCIbU0hgHENfy4Uq+PIEjq0RMC8B1Yks7nS20Lt0VfDxQv+CFL/3VmD79B7Fz PuLQujwX30jRGqdcWJYBSlKFWI2wgKpdV8wc8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello world,

i have the follow problem and hope to find help here.

- XenparavirtOps-Kernel (jeremys git)
- Xen 4.0.1 (from tarball at xensource)
- rootfs is a ext3 initrd RAMDisk (size 640M (655360)) with 130MB free space
- Hypervisor, Kernel and Ramdisk are booting from a TFTPServer with Syslinux Multiboot (mboot.c32)
- Boot parameters: $hypervisor dom0_mem=2048M loglvl=all guest_loglvl=all dom0_max_vcpus=1 dom0_vcpus_pin --- $kernel ramdisk_size=655360 root=/dev/ram0 rw $otheroptions --- $ramdisk

The boot-progress and the system integrity without the XEN-Hypervisor are fine, all works without any errors or problems.
Required modules are loaded without any problems.

With Hypervisor i get various error messages on boot or in system from user space utilities and their modules.
e.g. bonding or iscsi-module:

[hostname ~]# modprobe iscsi_tcp
Warning: at mm/vmalloc.c:108 vmap_page_range_noflush+0x22/0x2e2()
Hardware name: IBM eServer BladeCenter HS21 -[7995A1G]-
Pid: 2344, comm: modprobe Tainted: C       W #2
Call Trace:
[<ffffffffxxxxxxxx>] ? warn_slowpath_common
[<ffffffffxxxxxxxx>] ? vmap_page_range_noflush
[<ffffffffxxxxxxxx>] ? map_vm_area
[<ffffffffxxxxxxxx>] ? __vmalloc_area_node
[<ffffffffxxxxxxxx>] ? load_module
[<ffffffffxxxxxxxx>] ? do_page_fault
[<ffffffffxxxxxxxx>] ? sys_init_module
[<ffffffffxxxxxxxx>] ? sys_call_fastpath
---[ end trace xxxxxxxx ]---
FATAL: Error inserting iscsi_tcp (/lib/modules/ Cannot allocate memory
(or see http://picfront.de/d/7S63 for screenshot of management console)

I have that problem with different hardware.
But the funny is, if the rootfs size 490000 (478MB) and the
ramdisk_size 550000 (537MB), all work! (but need more space in filesystem), the filesystem use 476MB).

Perhaps is the problem based on free memory management of xen-hypervisor? (no-bootscrub param. was tested).

Best regards
Thank you for your time!


Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>