VirtualBox

Opened 12 years ago

Closed 7 years ago

#10730 closed defect (fixed)

Can't use SCSI/SAS LsiLogic HBA with NetWare 6.5's LSIMPTNW.HAM driver => fixed in SVN

Reported by: kumba Owned by:
Component: virtual disk Version: VirtualBox 4.0.16
Keywords: netware, lsilogic, disk, scsi, sas Cc:
Guest type: other Host type: Windows

Description

It seems that the included LSIMPTNW.HAM driver, version 5.02, as well as the updated 5.03.01 version fetched from LSI's website cannot detect the SCSI HBA when VirtualBox emulates it in LsiLogic mode under NetWare 6.5 SP8. It also doesn't detect the same HBA in SAS mode, either, failing with the same exact error message in the screenshot.

Not certain if this is a VirtualBox-specific issue or not. I am also opening a support request with LSI and providing them with this ticket number and the same attached screenshot to see if it is something they can fix on their end with an updated LSIMPTNW.HAM driver.

It also appears that SATA emulation is also not possible with NW65SP8 because the Intel ICH* emulation is only in AHCI mode, which neither IDEATA.HAM or IDESATA.HAM can recognize. This appears to be a more NetWare-specific issue and likely will not be fixed by Novell anytime soon (though I might go file a bug with them, too, just in case).

So for now, the only properly-supported disk adapter in VBox with NetWare is IDE emulation OR SCSI BusLogic if you can hunt down the ~1998 copy of BLMM3.HAM/BLMM3.DDI, available from a site which documents extremely similar issues with NetWare under VMWare.

Attachments (2)

vbox4016-lsilogic-20120705-nw65sp8.txt (50.4 KB ) - added by kumba 12 years ago.
VBox.log of NW65SP8 Startup with an LsiLogic SCSI HBA on Slot 21
vbox4016-screenshot-20120705-nw65sp8-LSIMPTNW_HAM-fail.png (38.4 KB ) - added by kumba 12 years ago.
Screenshot of the NW65SP8 console on Vbox 4.0.16 of the failure code/message from LSIMPTNW.HAM

Download all attachments as: .zip

Change History (8)

by kumba, 12 years ago

VBox.log of NW65SP8 Startup with an LsiLogic SCSI HBA on Slot 21

by kumba, 12 years ago

Screenshot of the NW65SP8 console on Vbox 4.0.16 of the failure code/message from LSIMPTNW.HAM

comment:1 by Frank Mehnert, 11 years ago

Still relevant with VBox 4.1.22 / 4.2.0?

in reply to:  1 comment:2 by kumba, 11 years ago

Replying to frank:

Still relevant with VBox 4.1.22 / 4.2.0?

Impossible to test due to a block on #10728. I am stuck on 4.0.16 until NW65 can boot in newer releases of Vbox.

Ideally would like SMP support (#10729) to work, too, but I'll start with it actually booting, first.

comment:3 by michaln, 11 years ago

Did you get any information from Novell on IDESATA.HAM? The driver is definitely meant to support AHCI (for systems in compatibility mode, IDEATA.HAM will be used instead) but it appears that the driver is restricted to a tiny set of SATA controllers with specific PCI IDs.

comment:4 by aeichner, 11 years ago

Summary: Can't use SCSI/SAS LsiLogic HBA with NetWare 6.5's LSIMPTNW.HAM driverCan't use SCSI/SAS LsiLogic HBA with NetWare 6.5's LSIMPTNW.HAM driver => fixed in SVN

We fixed the LsiLogic controller emulation to work with NetWare. Because this required some changes in the saved state the fix will be available in the next major release only.

Our AHCI controller is not supported by NetWare because it doesn't has the required PCI Ids in the driver.

in reply to:  4 comment:5 by kumba, 11 years ago

Replying to aeichner:

We fixed the LsiLogic controller emulation to work with NetWare. Because this required some changes in the saved state the fix will be available in the next major release only.

Our AHCI controller is not supported by NetWare because it doesn't has the required PCI Ids in the driver.

Is it possible to "lie" to the NetWare SATA/AHCI driver about the PCI ID in the hopes that one of the IDs that it does support is for a generic-enough SATA chip that NW could make use of VBox's SATA support?

comment:6 by Michael Thayer, 7 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use