Anaconda early startup failure - traceback

James Cammarata jimi at sngx.net
Thu Jul 2 15:20:51 UTC 2009


On Thu, 02 Jul 2009 10:54:34 -0400, Kyle Powell <kpowell at redhat.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> whitivery wrote:
>> We have a working Kickstart server for CentOS 4.4, building
>> targets running CentOS 4.4.
>> 
>> I built a new server with CentOS 5.3, to build CentOS 5.3
>> targets, adapting for the changes I noticed as I went along.  The
>> new server boots and runs but won't build a target unit.
>> 
>> When I PXE-boot a target unit, I get the boot menu and pick an
>> entry, it starts the early part fine, loads stage2.img OK, shows
>> a couple screens then a "Retrieving installation information"
>> dialog/progress bar, and just when/after that gets to 100%, it
>> halts with a traceback.
> 
> Looks like you need more RAM:
> http://www.centos.org/modules/newbb/viewtopic.php?topic_id=19367&forum=37
> 
> Same thing with Fedora:
> http://bugzilla.redhat.com/show_bug.cgi?id=499585
> 
> Minimum RAM requirement for RHEL 5 is 512MB. I assume that applies to
> CentOS as
> well:
> http://www.redhat.com/rhel/compare/

Yes I've seen this same error on systems with insufficient ram (usually
VM's).  The key is that it fails on the lspci call, which is exactly where
all of mine would fail.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




More information about the Kickstart-list mailing list