Bug 604071
| Summary: | kickstart is missing parameter during installation in kvm guest, error processing drive | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Petr Sklenar <psklenar> | ||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team-automation> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 6.0 | Keywords: | Regression | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-06-24 19:12:33 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 582655 | ||||||||
| Attachments: |
|
||||||||
Created attachment 424117 [details]
anaconda.log
anaconda.log from kvm guest
It happens only during PXE installation from local brno tree. http://download.englab.brq.redhat.com/pub/rhel/nightly/RHEL6.0-20100610.n.0/ If I start installation from http source in virt-manager, then it works well. Is your working install a graphical install and your non-working one is a text install? (In reply to comment #3) > Is your working install a graphical install and your non-working one is a text > install? Issue in only in PXE text installation Now I tried: * PXE installation in virt-manager graphical - works well , I can install rhel6 text installation - non-working, issue from Comment 0 * http source in virt-manager the both graphical and text works well. And does your kickstart file specify any partitioning information? If you can attach the complete file, that'd be great. it would be this one: http://10.34.32.211/cblr/svc/op/ks/profile/RHEL6.0-20100610.n.0_http-Server-x86_64 (from anaconda.log) its installing from Brno pxe server, and I have no idea how could I find which ks is using What appears to be happening here is that due to too little memory in your virtual machine (see "10:54:47,493 WARNING : You do not have enough RAM to use the graphical installer. Starting text mode." from your anaconda.log), you are being forced into a text install. Your kickstart file does not specify any bootloader or packaging sections. This therefore means anaconda needs to stop and prompt for these elements. However, the text installer has been stripped down to no longer include any custom partitioning, bootloader configuration, or package selection. Therefore, the installation halts because the code to prompt for this information does not exist. It looks to me like everything is working as expected here. (In reply to comment #7) > What appears to be happening here is that due to too little memory in your > virtual machine (see "10:54:47,493 WARNING : You do not have enough RAM to use > the graphical installer. Starting text mode." from your anaconda.log), you are yes, my guest had 444MB, so you are going to say that pxe installation is not working and installation from http source is working for low mem guests, right? |
Created attachment 424116 [details] anaconda error, screenshot Description of problem: cannot perform installation in kvm guest Version-Release number of selected component (if applicable): running anaconda 13.21.50 20100610.nightbuild How reproducible: always Steps to Reproduce: 1. I have virtual kvm host, rhel55 and starting kvm guest , I allocated 4000Mb of disk space , type vda 2. start installation of rhel6 - 20100610.nightbuild 3. error processing drive, clicking re-initializing Actual results: kickstart is missing parameter Expected results: disk is reinitialized Additional info: