Bug 169517

Summary: SAN-Boot installation on BladeCenter LS20 fails
Product: Red Hat Enterprise Linux 4 Reporter: Rainer Duffner <rainer>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-10-03 17:49:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Rainer Duffner 2005-09-29 08:54:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

Description of problem:
I want to install RHEL4U1 on a dual-core dual Opteron Blade from IBM (BladeCenter LS20).
According to IBM, only local installs are possible:
Our blades don't have local disks, but connect to a HP EVA3000 SAN and boot from that.
According to information I have found on the net, to enable MPIO, one has to boot with "linux noprobe" and specify the qla2300-module with the "ql2xfailover=1" option - this works for RHEL3U5-i386, but when I do that with RHEL4U1, the keyboard isn't recognized anymore and I can't continue the installation.
This is because the BladeCenter uses an USB-keyboard (infact, everything that isn't SCSI is USB)

Is there a way to only not load the qla2300-module but all the rest?

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

How reproducible:

Steps to Reproduce:
1. boot with linux=noprobe
2. watch as your keypresses are ignored
3. bang your head against blade-chassis
4. repeat..

Actual Results:  Nothing

Expected Results:  Keyboard detected

Additional info:


Comment 1 Jeremy Katz 2005-10-03 17:49:55 UTC
'noprobe' does exactly what it sounds like and doesn't probe for _anything_ now.
 You probably want one of the more granular probing things such as "nostorage"

Comment 2 Rainer Duffner 2005-10-03 18:22:27 UTC
Well, I was looking for a list of options, but I couldn't find one.
In fact, I can't even find information about this command when I explicitly feed
google with it, except for mailinglist entries.

Additionally: does RHEL4U1 actually support the qla2xfailover=1 option or do I
have to compile my own kernel?