From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: Fw: Not enough RAM for domain 0 allocation Date: Fri, 19 Mar 2010 18:16:58 -0700 (PDT) Message-ID: <8ed45f58-a830-4c01-ae49-90bcc194bdce@default> References: <20998bd5-1eab-4bd3-9394-c2a64632ed9f@default 753202.80116.qm@web34207.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0112527087==" Return-path: In-Reply-To: <753202.80116.qm@web34207.mail.mud.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: ccmail111 , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0112527087== Content-Type: multipart/alternative; boundary="__126904782467891237abhmt017" --__126904782467891237abhmt017 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Your kernel and initrd are compressed and still exceed 512MB? That is very= unusual. Are you building everything in your dom0 kernel? (e.g. answering= yes to all drivers, and everything when configuring your kernel?) If so, = that's not a good idea and is likely contributing to your problem. =20 You didn't say how much memory is in your machine. If you have enough, you= can try dom0_mem=3D768M or dom0_mem=3D1GB and so on. =20 If those suggestions don't work, sorry, maybe someone else can answer but t= his is probably a xen-users list question than a xen-devel question. =20 From: ccmail111 [mailto:ccmail111@yahoo.com]=20 Sent: Friday, March 19, 2010 5:47 PM To: xen-devel@lists.xensource.com; Dan Magenheimer Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation =20 Hi Dan, Thanks for response. =20 I just tried (with dom0_mem=3D512M) and see error: "Domain 0 allocation is too small for kernel image" =20 But if I dont use the parameter I see error as in subject line which is dif= ferent. Question is: does subject line error printed by kernel ? Any kernel paramet= er that I need to change during build ? =20 Any suggestions ? Is there anyway I can specifiy the max for kernel and xen ? =20 Thanks, =20 SV =20 --- On Fri, 3/19/10, Dan Magenheimer wrote: From: Dan Magenheimer Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation To: "ccmail111" , xen-devel@lists.xensource.com Date: Friday, March 19, 2010, 6:10 PM You should be able to get around this problem by specifying dom0_mem=3D on = the Xen boot line, e.g.: =20 kernel /boot/xen.gz noreboot loglvl=3Dall dom0_mem=3D256M =20 From: ccmail111 [mailto:ccmail111@yahoo.com]=20 Sent: Friday, March 19, 2010 3:43 PM To: xen-devel@lists.xensource.com Subject: [Xen-devel] Fw: Not enough RAM for domain 0 allocation =20 --- On Fri, 3/19/10, ccmail111 wrote: From: ccmail111 Subject: Not enough RAM for domain 0 allocation To: "Fajar A. Nugraha" Cc: xen-users@lists.xensource.com Date: Friday, March 19, 2010, 5:38 PM =20 Hi, =20 I see above error when xen tries to boot up. =20 The grub.conf is: =20 title Dom0 Xen 3.4.2 XenLinux 2.6 kernel /boot/xen.gz noreboot loglvl=3Dall module /boot/vmlinuz.vm root=3Ddev/ram0 ro module /boot/ramdisk.gz Looking through archives I found couple of pointers but no solution. The closest I see: http://www.mailinglistarchive.com/xen-devel@lists.xensource.com/msg56592.ht= ml by Keir: =20 " Either this restriction of the domain builder needs to be lifted (a bit of a pain and not really on anyone's todo list), ..." =20 Any solutions/suggestions is appreciated ! =20 Thanks ! =20 SV =20 =20 =20 =20 --__126904782467891237abhmt017 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable

Your kernel and initrd are compressed and still exceed 512= MB?  That is very unusual.  Are you building everything in your dom0 kern= el? (e.g. answering yes to all drivers, and everything when configuring your = kernel?)  If so, that’s not a good idea and is likely contributing to your pr= oblem.

 

You didn’t say how much memory is in your machine.&n= bsp; If you have enough, you can try dom0_mem=3D768M or dom0_mem=3D1GB and so = on.

 

If those suggestions don’t work, sorry, maybe someon= e else can answer but this is probably a xen-users list question than a xen-deve= l question.

 

From: ccmail111 [mailto:ccmail111@yahoo.com]
Sent: Friday, March 19, 2010 5:47 PM
To: xen-devel@lists.xensource.com; Dan Magenheimer
Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocatio= n

 

Hi Dan,


Thanks for response.

 

I just tried (with d= om0_mem=3D512M) and see error:

"Domain 0 allocation is too small for kernel image"

 

But if I dont use the parameter I see error as in = subject line which is different.

Question is: does subject line error printed by ke= rnel ? Any kernel parameter that I need to change during build ?

 

Any suggestions ?

Is there anyway I can specifiy the max for kernel = and xen ?

 

Thanks,

 

SV

 



--- On Fri, 3/19/10, Dan Magenheimer <dan.magenheimer@oracle.c= om> wrote:


From: Dan Magenheimer <dan.magenheimer@oracle.com>
Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
To: "ccmail111" <ccmail111@yahoo.com>, xen-devel@lists.xensource.com
Date: Friday, March 19, 2010, 6:10 PM

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

 

kernel /boot/xen.gz noreboot loglvl=3Dall dom0_mem=3D256M

 

From: ccmail111 [mailto:ccmail111@yahoo.com]
Sent: Friday, March 19, 2010 3:43 PM
To: xen-devel@lists.xensource.com
Subject: [Xen-devel] Fw: Not enough RAM for domain 0 allocation<= /span>

 



--- On Fri, 3/19/10, ccmail111 <ccmail111@yahoo.com><= /b> wrote:


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

 

Hi,

 

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=3Dall
       module /boot/vmlinuz.vm  root=3Ddev/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 !

 

SV

 

 

 

 

--__126904782467891237abhmt017-- --===============0112527087== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0112527087==--