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


RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation

To: ccmail111 <ccmail111@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Fri, 19 Mar 2010 15:10:16 -0700 (PDT)
Delivery-date: Fri, 19 Mar 2010 15:12:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <702969.96103.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <702969.96103.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

You should be able to get around this problem by specifying dom0_mem= on the Xen boot line, e.g.:


kernel /boot/xen.gz noreboot loglvl=all dom0_mem=256M


From: ccmail111 [mailto:ccmail111@xxxxxxxxx]
Sent: Friday, March 19, 2010 3:43 PM
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Fw: Not enough RAM for domain 0 allocation


--- On Fri, 3/19/10, ccmail111 <ccmail111@xxxxxxxxx> wrote:

From: ccmail111 <ccmail111@xxxxxxxxx>
Subject: Not enough RAM for domain 0 allocation
To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Friday, March 19, 2010, 5:38 PM




I see above error when xen tries to boot up.


The grub.conf is:


title Dom0 Xen 3.4.2  XenLinux 2.6
       kernel /boot/xen.gz noreboot loglvl=all
       module /boot/vmlinuz.vm  root=dev/ram0 ro
       module /boot/ramdisk.gz

Looking through archives I found couple of pointers but no solution.

The closest I see:

by Keir:


" Either this restriction of the domain builder needs
to be lifted (a bit of a pain and not really on anyone's todo list), ..."


Any solutions/suggestions is appreciated !


Thanks !






Xen-devel mailing list