Bug 456325
Summary: | cmdline kickstart option not honored | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Chris Lumens <clumens> |
Component: | anaconda | Assignee: | Martin Sivák <msivak> |
Status: | CLOSED ERRATA | QA Contact: | Alexander Todorov <atodorov> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.4 | CC: | atodorov, charles_duffy, cward, ddumas, duck, jfeeney, ndevos, pasteur, tao, wwlinuxengineering |
Target Milestone: | rc | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-02 09:55:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chris Lumens
2008-07-22 21:08:31 UTC
*** Bug 461230 has been marked as a duplicate of this bug. *** Steps to reproduce: 1. Start a virtual guest with less than 288MB RAM (200MB, PV Xen guest) * 2. Provide a complete kickstart file which contains 'cmdline' command 3. Proceed with install 4. X can't start (not enough memory, X not on minstg2.img) - anaconda falls back to curses based text mode instead of going to cmdline mode. * - in the code GUI_STAGE2_RAM 294912 = 288MB 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 release. The fix will be available in anaconda 11.1.2.169 Is related bug 499143 also solved with the upcoming anaconda? *** Bug 499143 has been marked as a duplicate of this bug. *** ~~ Attention - RHEL 5.4 Beta Released! ~~ RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner! If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity. Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value. Questions can be posted to this bug or your customer or partner representative. VERIFIED with 0701.0 tree and the steps to reproduce in comment #2 Confirmed -- cannot reproduce with 5.4 beta. 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. http://rhn.redhat.com/errata/RHBA-2009-1306.html |