Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 591397 - anaconda refuses to run graphical installation with 512MB RAM
anaconda refuses to run graphical installation with 512MB RAM
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Anaconda Maintenance Team
Release Test Team
Depends On:
  Show dependency treegraph
Reported: 2010-05-12 02:35 EDT by Miroslav Vadkerti
Modified: 2010-05-12 09:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-12 09:51:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
anaconda logs (12.85 KB, application/gzipped-tar)
2010-05-12 02:36 EDT, Miroslav Vadkerti
no flags Details

  None (edit)
Description Miroslav Vadkerti 2010-05-12 02:35:44 EDT
Description of problem:
In newest compose 20100511.3 (Workstation) with virtual machine with 512MB RAM installer refuses to run graphical installation and fails with message that I don't have enough RAM to run the graphical installer.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run network installation with virtual machine with 512MB RAM
Actual results:
text mode installation

Expected results:
graphical installation

Additional info:
used x86_64 installation
Comment 1 Miroslav Vadkerti 2010-05-12 02:36:14 EDT
Created attachment 413336 [details]
anaconda logs
Comment 2 Miroslav Vadkerti 2010-05-12 03:18:16 EDT

The graphical installation also FAILS with 600MB RAM

The graphical installation WORKS with 700MB RAM
Comment 3 Chris Lumens 2010-05-12 09:51:27 EDT
Memory requirements for the x86-64 install in particular are rather high due to bigger python objects.  Combine this with your installation method and the memory needs for yum and lvm, and this is what happens.

Note You need to log in before you can comment on or make changes to this bug.