From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Fw: not syncing Date: Sat, 20 Mar 2010 09:14:04 +0200 Message-ID: <20100320071404.GQ1878@reaktio.net> References: <301885.9273.qm@web34208.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <301885.9273.qm@web34208.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 Cc: Dan Magenheimer , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sat, Mar 20, 2010 at 12:00:40AM -0700, ccmail111 wrote: >=20 > Attaching error I see on serial: >=20 >=20 > (XEN) Dom0 has maximum 1 VCPUs >=20 > (XEN) Scrubbing Free RAM: > ....................................................................don= e. >=20 > (XEN) Xen trace buffers: disabled >=20 > (XEN) Std. Loglevel: All >=20 > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) >=20 > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch inp= ut to Xen) >=20 > (XEN) Freed 128kB init memory. >=20 > Bootdata ok (command line is root=3Ddev/ram0 ro console=3Dhvc0 earlypri= ntk=3Dxen > nomodeset) >=20 "console=3Dhvc0 earlyprintk=3Dxen" are options for a pvops dom0 kernel, I don't think linux-2.6.18-xen can use them. -- Pasi > Linux version 2.6.18.8-xen (stevyang@wilma) (gcc version 4.1.2 20080704= (Red Hat > 4.1.2-44)) #1 SMP Mon Mar 15 23:23:21 PDT 2010 >=20 > BIOS-provided physical RAM map: >=20 > Xen: 0000000000000000 - 0000000040800000 (usable) >=20 > kernel direct mapping tables up to 40800000 @ 3f736000-3f93d000 >=20 > DMI 2.4 present. >=20 > bootmem alloc of 14794752 bytes failed! >=20 > Kernel panic - not syncing: Out of memory >=20 > (XEN) Domain 0 crashed: 'noreboot' set - not rebooting. >=20 > Any thoughts/suggestions, appreciated ! >=20 > Thanks, > SV >=20 > --- On Sat, 3/20/10, ccmail111 wrote: >=20 > From: ccmail111 > Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation > To: xen-devel@lists.xensource.com, "Dan Magenheimer" > Date: Saturday, March 20, 2010, 2:37 AM >=20 > Thanks Dan. > I am past that and see different error now: >=20 > "Xen: Scrubbing Free RAM ............" > Then the xterm(screen) goes blank.. >=20 > Any thoughts ? >=20 > SV > --- On Fri, 3/19/10, Dan Magenheimer wro= te: >=20 > From: Dan Magenheimer > Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation > To: "ccmail111" , xen-devel@lists.xensource.co= m > Date: Friday, March 19, 2010, 9:16 PM >=20 > Your kernel and initrd are compressed and still exceed 512MB? That= is very > unusual. Are you building everything in your dom0 kernel? (e.g. an= swering yes > to all drivers, and everything when configuring your kernel?) If s= o, that=E2**s > not a good idea and is likely contributing to your problem. >=20 >=20 >=20 > You didn=E2**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 >=20 >=20 > If those suggestions don=E2**t work, sorry, maybe someone else can = answer but this > is probably a xen-users list question than a xen-devel question. >=20 >=20 >=20 > 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 allocation >=20 >=20 >=20 > Hi Dan, >=20 > Thanks for response. >=20 >=20 >=20 > I just tried (with dom0_mem=3D512M) and see error: >=20 > "Domain 0 allocation is too small for kernel image" >=20 >=20 >=20 > But if I dont use the parameter I see error as in subject line whic= h is > different. >=20 > Question is: does subject line error printed by kernel ? Any kernel= parameter > that I need to change during build ? >=20 >=20 >=20 > Any suggestions ? >=20 > Is there anyway I can specifiy the max for kernel and xen ? >=20 >=20 >=20 > Thanks, >=20 >=20 >=20 > SV >=20 >=20 >=20 > --- On Fri, 3/19/10, Dan Magenheimer w= rote: >=20 > From: Dan Magenheimer > Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocati= on > To: "ccmail111" , xen-devel@lists.xensource.= com > Date: Friday, March 19, 2010, 6:10 PM >=20 > You should be able to get around this problem by specifying dom0_= mem=3D on the > Xen boot line, e.g.: >=20 >=20 >=20 > kernel /boot/xen.gz noreboot loglvl=3Dall dom0_mem=3D256M >=20 >=20 >=20 > 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 >=20 >=20 >=20 > --- On Fri, 3/19/10, ccmail111 wrote: >=20 > 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 >=20 >=20 > Hi, >=20 >=20 >=20 > I see above error when xen tries to boot up. >=20 >=20 >=20 > The grub.conf is: >=20 >=20 >=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 >=20 > Looking through archives I found couple of pointers but no solution= . >=20 > The closest I see: >=20 > [1]http://www.mailinglistarchive.com/xen-devel@lists.xensource.com/= msg56592.html >=20 > by Keir: >=20 >=20 >=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 >=20 >=20 > Any solutions/suggestions is appreciated ! >=20 >=20 >=20 > Thanks ! >=20 >=20 >=20 > SV >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 > References >=20 > Visible links > 1. http://www.mailinglistarchive.com/xen-devel@lists.xensource.com/m= sg56592.html > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel