Red Hat Bugzilla – Bug 169517
SAN-Boot installation on BladeCenter LS20 fails
Last modified: 2007-11-30 17:07:20 EST
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):
Steps to Reproduce:
1. boot with linux=noprobe
2. watch as your keypresses are ignored
3. bang your head against blade-chassis
Actual Results: Nothing
Expected Results: Keyboard detected
'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"
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?