Description of Problem: 188072 kb virtual memory is not enough for anaconda. System is Compaq deskpro 6000, 64Meg of RAM, 4G disk, 125928kB SWAP, manual partitioning, workstation install, selected all but games. Install got stuck at kamera-3.0.1. CTRL_ALT_F2, ps, found tree python processes (normally two?) killed the last one (115) and install continued to the end. Then during about 40% of "Performing post install configuration" got a traceback dialog. Clicked on "save to floppy" and OK on next dialog. Floppy light came on. CTRL_ALT_F2, mdir says cannot initialize A:. I think before tracebacks were saved to MSDOS formatted disk? So I got another disk and pressed on "save to floppy" again. NOTHING happened. All three buttons have no effect. Here is traceback by hand: gui:682 progress_gui:148 gui:549 dispatch:149 dispatch:214 packages:754 pcmcia:42 pcmcia:28 iutil:125 childpid = os.fork OSError: [Errno 12] Cannot allocate memory
I let anaconda partition the disk which resulted in 192Meg swap and 256Meg total virtual memory. Installation completed with one minor defect: the very last "Quit" button had no effect - I had to kill anaconda by hand.
The Exit button issue is resolved. Will have to look into what uses so much RAM in post-install.
What about saving tracebacks on floppy? What format does it use and why second attempt produced no output to a floppy?
If we're unable to allocate memory, then writing tracebacks to floppy is entirely likely to fail. Trying a low-memory install now.
I just did an install with 64 megs of ram and 128 megs of swap without any problems. There have been a few changes to the package set and the like, though, which I would guess help this situation a lot.
Do you know/can take measurements what is the memory consumption peak during default installation? What would happen on a system with 32 Meg for example?
Was able to complete a 64M/128M GUI installation using the re0127.nightly tree without any problems. 32M installations force TUI mode, so there's no problem there either.