Description of problem:
Under low memory conditions anaconda will attempt to fetch the secondary minstg2.img instead of the usual stage2.img file.
The anaconda script referenced requires the lspci binary to be made available. The lspci binary is available in the stage2.img but not the minstg2.img.
This makes anaconda crash if it is in an xen or vmware instance.
Version-Release number of selected component (if applicable):
RHEL 5.3 snap 5.
Steps to Reproduce:
1. create vmware guest, 256mb ram.
2. Boot vmware instance, rhel 5.3 snap 5.
Anaconda fails with OSError no such file or directory.
Anaconda to find lspci and continue on its merry way.
Traceback (most recent call first):
File "/usr/lib/python2.4/subprocess.py", line 975, in _execute_child
File "/usr/lib/python2.4/subprocess.py", line 542, in __init__
File "/usr/lib/anaconda/iutil.py", line 488, in inVmware
proc = subprocess.Popen(lspci, stdout = subprocess.PIPE)
File "/usr/lib/anaconda/yuminstall.py", line 860, in doGroupSetup
if iutil.inXen() or iutil.inVmware() or \
File "/usr/lib/anaconda/yuminstall.py", line 942, in doRepoSetup
File "/usr/lib/anaconda/backend.py", line 172, in doRepoSetup
File "/usr/lib/anaconda/dispatch.py", line 201, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 124, in gotoNext
File "/usr/lib/anaconda/text.py", line 721, in run
File "/usr/bin/anaconda", line 1006, in ?
OSError: [Errno 2] No such file or directory
This only happens to the minstg2.img
14:22:42 INFO : 255560 kB are available
14:22:42 WARNING : URLINSTALL falling back to non-GUI stage2 due to insufficient RAM
14:22:42 INFO : transferring ftp://192.168.1.1//5.3-snap5/tree/images/minstg2.img to a fd
For those on the CC,
The quick work around is to install the system with 512 or greater MB of ram.
I ran into this same problem using VM Fusion 2.1 on Mac OS 10.5.6. I was able to work around the issue by allocating at least 296 MB of ram, any thing less than 296 would reproduce the error.
Tried to install 5.3-i386(CentOS) via netboot on a 256 MB system.
On some system it's not feasibel to add more memory. Laptops or older HW with expensive or hard to get memory.
Any idea how to do with 128Mb or 192Mb ?
I have some Vectra 200 PentiumPro that takes a max of 192.
Does 5 5.1 5.2 have the same problem?
Install older version and them upgrade ?
Its been a while since I worked this original problem, but I did find a solution in rebuilding/adding the minstg2.img file.
# This is from memory, I'm not at work right now.
mkdir -p /mnt/stage2
mount minstg2.img /mnt/stage2 -t squashfs -o loop,rw
cp /sbin/lspci /mnt/stage2/
your solution is not complete, you have to use mksquashfs from squashfs-tools
Copy DVD to dir C53-i386
unsquashfs -v C53-i386/images/minstg2.img
mount -t squashfs -o loop C53-i386/images/stage2.img stage2
cp /mnt/stage2/usr/sbin/lspci squashfs-root/usr/sbin/
mksquashfs squashfs-root/ minstg2.img
cp minstg2.img C53-i386/images/
mount --bind -o context=system_u:object_r:httpd_sys_content_t C53-i386 \
Installation works OK
Created attachment 339848 [details]
this is a fix the anaconda for this bug
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
This should be fixed in 188.8.131.52-1.
I tested with i386/xen/pv guest with 256MB of memory.
While on RHEL 5.3 I didn't get a traceback (happens in VMWare only I guess) switching to tty2 revealed that lspci was missing.
With latest RHEL5.4 and anaconda-184.108.40.206-1 I can confirm that lspci is present in minstg2.img
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
*** Bug 528749 has been marked as a duplicate of this bug. ***