On Sat, Mar 20, 2010 at 12:44:25AM -0700, ccmail111 wrote:
> Hi Pasi/Dan,
>
> 1) The error below is:
>
> > Kernel panic - not syncing: Out of memory
>
Please paste your grub.conf and the full boot log of the hypervisor.
-- Pasi
> 2) The printk options below seem to be ok.
> But if that not recommended, for Xen 3.4.2/linux-2.6.18-xen how to enable
> serial then ?
>
> Any thoughts ?
>
> --- On Sat, 3/20/10, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
>
> From: Pasi Kärkkäinen <pasik@xxxxxx>
> Subject: Re: [Xen-devel] Fw: not syncing
> To: "ccmail111" <ccmail111@xxxxxxxxx>
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Dan Magenheimer"
> <dan.magenheimer@xxxxxxxxxx>
> Date: Saturday, March 20, 2010, 3:14 AM
>
> On Sat, Mar 20, 2010 at 12:00:40AM -0700, ccmail111 wrote:
> >
> > Attaching error I see on serial:
> >
> >
> > (XEN) Dom0 has maximum 1 VCPUs
> >
> > (XEN) Scrubbing Free RAM:
> > ....................................................................done.
> >
> > (XEN) Xen trace buffers: disabled
> >
> > (XEN) Std. Loglevel: All
> >
> > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
> >
> > (XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input
> to Xen)
> >
> > (XEN) Freed 128kB init memory.
> >
> > Bootdata ok (command line is root=dev/ram0 ro console=hvc0 earlyprintk=xen
> > nomodeset)
> >
>
> "console=hvc0 earlyprintk=xen" 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
> >
> > BIOS-provided physical RAM map:
> >
> > Xen: 0000000000000000 - 0000000040800000 (usable)
> >
> > kernel direct mapping tables up to 40800000 @ 3f736000-3f93d000
> >
> > DMI 2.4 present.
> >
> > bootmem alloc of 14794752 bytes failed!
> >
> > Kernel panic - not syncing: Out of memory
> >
> > (XEN) Domain 0 crashed: 'noreboot' set - not rebooting.
> >
> > Any thoughts/suggestions, appreciated !
> >
> > Thanks,
> > SV
> >
> > --- On Sat, 3/20/10, ccmail111 <[1]ccmail111@xxxxxxxxx> wrote:
> >
> > From: ccmail111 <[2]ccmail111@xxxxxxxxx>
> > Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
> > To: [3]xen-devel@xxxxxxxxxxxxxxxxxxx, "Dan Magenheimer"
> <[4]dan.magenheimer@xxxxxxxxxx>
> > Date: Saturday, March 20, 2010, 2:37 AM
> >
> > Thanks Dan.
> > I am past that and see different error now:
> >
> > "Xen: Scrubbing Free RAM ............"
> > Then the xterm(screen) goes blank..
> >
> > Any thoughts ?
> >
> > SV
> > --- On Fri, 3/19/10, Dan Magenheimer <[5]dan.magenheimer@xxxxxxxxxx>
> wrote:
> >
> > From: Dan Magenheimer <[6]dan.magenheimer@xxxxxxxxxx>
> > Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
> > To: "ccmail111" <[7]ccmail111@xxxxxxxxx>,
> [8]xen-devel@xxxxxxxxxxxxxxxxxxx
> > Date: Friday, March 19, 2010, 9:16 PM
> >
> > 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.
> >
> >
> >
> > You didnâ**t say how much memory is in your machine. If you have
> enough, you
> > can try dom0_mem=768M or dom0_mem=1GB and so on.
> >
> >
> >
> > If those suggestions donâ**t work, sorry, maybe someone else can
> answer but this
> > is probably a xen-users list question than a xen-devel question.
> >
> >
> >
> > From: ccmail111 [mailto:[9]ccmail111@xxxxxxxxx]
> > Sent: Friday, March 19, 2010 5:47 PM
> > To: [10]xen-devel@xxxxxxxxxxxxxxxxxxx; Dan Magenheimer
> > Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
> >
> >
> >
> > Hi Dan,
> >
> > Thanks for response.
> >
> >
> >
> > I just tried (with dom0_mem=512M) 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 kernel ? 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 <[11]dan.magenheimer@xxxxxxxxxx>
> wrote:
> >
> > From: Dan Magenheimer <[12]dan.magenheimer@xxxxxxxxxx>
> > Subject: RE: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
> > To: "ccmail111" <[13]ccmail111@xxxxxxxxx>,
> [14]xen-devel@xxxxxxxxxxxxxxxxxxx
> > Date: Friday, March 19, 2010, 6:10 PM
> >
> > 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:[15]ccmail111@xxxxxxxxx]
> > Sent: Friday, March 19, 2010 3:43 PM
> > To: [16]xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: [Xen-devel] Fw: Not enough RAM for domain 0 allocation
> >
> >
> >
> > --- On Fri, 3/19/10, ccmail111 <[17]ccmail111@xxxxxxxxx> wrote:
> >
> > From: ccmail111 <[18]ccmail111@xxxxxxxxx>
> > Subject: Not enough RAM for domain 0 allocation
> > To: "Fajar A. Nugraha" <[19]fajar@xxxxxxxxx>
> > Cc: [20]xen-users@xxxxxxxxxxxxxxxxxxx
> > 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=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:
> >
> >
>
> [1][21]http://www.mailinglistarchive.com/xen-devel@xxxxxxxxxxxxxxxxxxx/msg56592.html
> >
> > 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
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > References
> >
> > Visible links
> > 1.
>
> [22]http://www.mailinglistarchive.com/xen-devel@xxxxxxxxxxxxxxxxxxx/msg56592.html
>
> > _______________________________________________
> > Xen-devel mailing list
> > [23]Xen-devel@xxxxxxxxxxxxxxxxxxx
> > [24]http://lists.xensource.com/xen-devel
>
> References
>
> Visible links
> 1. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
> 2. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
> 3.
> http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
> 4. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
> 5. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
> 6. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
> 7. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
> 8.
> http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
> 9. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
> 10.
> http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
> 11. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
> 12. http://us.mc342.mail.yahoo.com/mc/compose?to=dan.magenheimer@xxxxxxxxxx
> 13. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
> 14.
> http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
> 15. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
> 16.
> http://us.mc342.mail.yahoo.com/mc/compose?to=xen-devel@xxxxxxxxxxxxxxxxxxx
> 17. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
> 18. http://us.mc342.mail.yahoo.com/mc/compose?to=ccmail111@xxxxxxxxx
> 19. http://us.mc342.mail.yahoo.com/mc/compose?to=fajar@xxxxxxxxx
> 20.
> http://us.mc342.mail.yahoo.com/mc/compose?to=xen-users@xxxxxxxxxxxxxxxxxxx
> 21.
> http://www.mailinglistarchive.com/xen-devel@xxxxxxxxxxxxxxxxxxx/msg56592.html
> 22.
> http://www.mailinglistarchive.com/xen-devel@xxxxxxxxxxxxxxxxxxx/msg56592.html
> 23.
> http://us.mc342.mail.yahoo.com/mc/compose?to=Xen-devel@xxxxxxxxxxxxxxxxxxx
> 24. http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home