Created attachment 730527 [details] screen-shot of the crash in text mode with 512mb (not in the logs) Description of problem: When having a system (KVM Guest in this case) with only 512mb ram, booting with the 'text' boot parameter fails. Version-Release number of selected component (if applicable): F19a TC3 How reproducible: always Steps to Reproduce: 1. Set the guest to have 512mb RAM 2. boot and add the kernel boot parameter: 'text' 3. anaconda will not start, printing an error (but no anaconda-tb-XXX file) Actual results: cannot install in text mode with 512mb ram Expected results: working text mode Additional info:
Created attachment 730528 [details] anaconda.log
Created attachment 730529 [details] program.log
Created attachment 730530 [details] storage.log
Created attachment 730531 [details] syslog file
This happens if you boot graphical mode with 512MB of RAM too. Booting either graphical or text with 768MB of RAM succeeds. Note the screenshot: The problem is in a check for sufficient RAM for VNC, not in the installer's own check for minimum sufficient RAM. So this is actually blocking text installs with 512MB of RAM (a 'supported' configuration) as things stand. Discussed at 2013-04-03 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-03/f19alpha-blocker-review-4.2013-04-03-16.01.log.txt . Rejected as a blocker: there's clearly a bug here, but all you're going to get if we fix it is a better error message (graphical) or a later failure (text). It doesn't hit any of the release criteria. We might be open to FE status for this one if the installer team comes up with a fix and thinks it's worth applying. It's more likely to be counted FE if a 512MB text install actually succeeds once this is fixed - otherwise, this error is really just saving people time...
I'm going to take the commit of a fix for this as an implied FE request from the anaconda team.
Discussed at 2013-04-08 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-04-08/f19alpha-blocker-review-5.2013-04-08-16.01.log.txt . Accepted as a freeze exception for the benefit of potentially fixing 512MB text installs.
python-blivet-0.10-1.fc19,anaconda-19.17-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-blivet-0.10-1.fc19,anaconda-19.17-1.fc19
Package python-blivet-0.10-1.fc19, anaconda-19.17-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-blivet-0.10-1.fc19 anaconda-19.17-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5323/python-blivet-0.10-1.fc19,anaconda-19.17-1.fc19 then log in and leave karma (feedback).
Confirmed fixed in RC2, I can boot and initiate a text install with 512MB of RAM.
I can also complete and boot a minimal text install with 512MB RAM, FWIW.
We're well past 19.17 in stable now (19.22 is stable), so let's close this.