Bug 101504
| Summary: | Mylex/buslogic driver missing | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Sander Steffann <sander> |
| Component: | kernel | Assignee: | Tom Coughlan <coughlan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0 | CC: | bill.stephens, bugproxy, jon, riel, tburke |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-09-19 00:34:35 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
Sander Steffann
2003-08-01 23:08:12 UTC
This is because the buslogic driver is in kernel-unsupported which means that it's not available during installation. Is it going to be added, Jeremy? It's awfully difficult to install under VMWare without it. Voting doesn't seem to be enabled in this bugzilla installation, so consider this a vote. What exactly determines when a piece of code goes into kernel-unsupported? Is it based on Red Hat qa tests, or based on the actual maintainer of that code? we've got a kb article about this now: http://www.vmware.com/support/kb/enduser/std_adp.php?p_lva=&p_faqid=1101 hopefully this situation has changed w/ beta 2, but the ftp directories seem to still be locked... driver is still missing. can anyone from redhat comment on this situation? is there a way to make kernel-unsupported available to an installation? We received some Mylex cards and did the QA, so the DAC960 driver was removed from the unsupported list on Aug. 11. Assuming this is the driver you are referring to, it should be available in recent kernels. I can't seem to find any info in the kernel dosc about the DAC960 driver (the Readme.Mylex points me to the Readme.Buslogic), but the generic buslogic support is what we really need. If we send you some copies of vmware to qa, could this driver still make it into the final release? We have a report that the BusLogic driver can crash the system when it is in error recovery. In addition, this driver has not been maintained for years. This is why the BusLogic driver is in the unsupported rpm. The drivers/block/DAC960 driver that I mentioned earlier is for a different family of Mylex adapters (AcceleRAID/eXtremeRAID PCI RAID Controllers), so it will not help with the VMWare issue. Unless... Is it possible for VMWare to switch to a more modern driver that is actually maintained? The deadline for driver changes in RHEL 3 was over a month ago. It is too late to make any changes in this driver at this time. It would appear that, for the initial release of RHEL 3, it will be necessary for VMWare to use emulated IDE storage as opposed to emulated SCSI/BusLogic storage. I understand that this imposes a performance penalty. If it is not possible for VMWare to change to a different driver, we will consider adding support for the BusLogic driver in an update to the RHEL 3 release. We agreed to remove the BusLogic driver from modules-unsupported, and add a release note saying that the BusLogic driver is only supported with VMWare. VMWare will be responsible for all support matters on the BusLogic driver when used in the VMWare VM, as well as any other problems that are are shown to occcur only when running Linux as a guest o.s. in VMWare. *** Bug 104683 has been marked as a duplicate of this bug. *** Reopening to change the state from "closed deferred" to "closed currentrelease" to note that this feature request was provided. I can confirm that this bug has been fixed in the release candidate. |