X9DRD-7LNF4 onboard LSI 2308 SR-IOV not capable?

Hi folks,

Still tinkering with my new build, with my X9DRD-7LNF4 board and onboard LSI2308 controll, it doesn't seem to allow me to configure SR-IOV in ESXi 6.7. I've done the install and enabled all relevant options I can find in the BIOS but VMWare reports the device as not being SR-IOV capable.
The only thing I can think of is the IT BIOS I flashed for full device passthrough to the NAS VM. Ideally I'd like to have the ports split between 2 VMs running drives off expanders.

Any ideas?

 

It should support SR IOV in IT Mode without any issues. Your second comment about splitting ports is a solid "no". The Controller is what you're passing through, and all the SAS Ports split from there. You're not going to be able to split the ports between different VMs. Did you try vSphere 6.5 or similar to rule out any 6.7 foolery?

 

Hmmm I'll check out 6.5 if possible. Seems there's very little documentation/info on people using SRIOV when it comes to storage, I may have been mistaken on what it does? My understanding was that you're able to "split" the PCIe device resources amongst several VMs? The onboard quad LAN Intel i350 is reported SRIOV capable in ESXi 6.7 and presents as 4 distinct devices to passthrough

 

My apologies, I had this confused with you attempting to do IOMMU, to pass through a device to a VM. You are *only* doing SR-IOV, where you want ESXi to control the device, and break it up into virtual devices for other VMs to use.

Technically this is possible, but not with ESXi. As far as I know VMware has only ever qualified Network Adapters (and Infiniband Adapters in Ethernet Mode) to work with this virtual function breakup. There is no SAS Controller (or anything else really) on their HCL for SR-IOV.

 

SR-IOV on SAS Controllers is a bit harder than you expect. Actually, I don't have a good example of how the thing is supposed to look when it is working. Is a Port supposed to be mapped to a Virtual Function that you do PCI Passthrough of, or what?

 

Thanks @zir_blazer
The idea (in my head) was to have each of the 2 SAS connectors split to a separate VM, I have expanders and that would allow each VM to have many drives attached to them. As you and @rune-san mentioned and in that thread, this seems more trouble than it's worth but it was a "cool let me try this out" idea

 

As far as I know, SR-IOV on SAS would work like a zoned fabric. You would have to map drives to each virtual function. Though how this would be accomplished, I have no idea. With SAS Switches, they provide a utility that lets you configure zoning based on the WWPN/WWNN of the HBA.

If you make any progress, please share!

 

@vanfawx that was what I sort of thought as well, SAS basically works on a network/address based topology and has been very kind with multipath and expander/backplanes vs. SATA before it. I've stop messing with this as it's my production home server and can't have it down all the time

 

This is one of those things on my list of "gotta try it", but never gotten around to. I'm sure you'e seen this VMware Knowledge Base, but on the off chance that you haven't...

I know you said, you enabled all the right BIOS options etc...BUT..esxi disables "Virtual Functions" by default..so..

 

I have not seen that article! Thank you for pointing it out, couple things I can update based on my observations so far:

1. If one uses the compatible hardware list from VMWare, LSI literally has "0" devices that has SR-IOV supported by ESXi (bummer), just as @rune-san mentioned above - if one searches for all hardware supporting SR-IOV it's all network or FCoE stuff
2. I did not manually enable SR-IOV from console commands, but the article seems to reference ESXi 5.1/5.5, running 6.7 the host picked up the onboard quad port Intel i-350 LAN no problem, SR-IOV capable and all, this leads me to believe it's more issue on the SAS specific or VMWare support side of things

Thanks for the info again

 

Yup, it was for the 5.x version of ESXI. And my google-fu turned up almost nothing in terms of SAS SR-IOV and ESXI. I suspect there is a reason for it...it's a driver limitation....by design.

With SR-IOV storage clustering/SDS would be much much easier...and guess what that will do to the Vmware VSAN sales...

 

Nice case of "just because you could, doesn't mean you should"