82576 Virtual Function support in Windows guest

[idata]

Dear Experts,

I have a Supermicro X8DT board with 5520 chipset and Intel 82576 LOM. I have setup SR-IOV and successfully tested it in both Linux and Windows guest environement - thanks a lot to developers!

However, I am not sure of the following. Windows driver package PROWinx64 v16.3 contains drivers for 82576 chipset that support DEV_10CA flavour of 82576 under Windows 2008 only, and not under Windows 2008R2/Win7. In return, driver for Windows 2008R2 only supports DEV_1520 flavour. Is there a reason for not supporting DEV_10CA under Windows 2008R2? (Please see below a scan through inf files)

I actually tried a little trick of editing the .inf file for v1q62x64 driver in NDIS62 directory and replaces all occurences of 1520 by 10CA. After manually installing such this driver, my virtual function connection worked just fine in Windows 2008R2 guest! Of course, I am not really going to use it a production enviroment w/o full support from Intel.

Thanks in advance!

Artem.

find intel16.3/ -name "*inf" -print -exec grep "Virtual N" {} \;

intel16.3/PRO100/Winx64/NDIS5x/eFE5b32e.infintel16.3/PROXGB/Winx64/NDIS5x/ixn51x64.infintel16.3/PROXGB/Winx64/NDIS5x/ixg5132e.infintel16.3/PROXGB/Winx64/NDIS5x/ixe51x64.infintel16.3/PROXGB/Winx64/NDIS61/ixg60x64.infintel16.3/PROXGB/Winx64/NDIS61/ixn60x64.infintel16.3/PROXGB/Winx64/NDIS61/vxn60x64.infDiskName = "Intel(R) 10G Virtual Network Device Driver Disk"Service.Displayname = "Intel(R) 10G Virtual Network Connection"E10EDVF.DeviceDesc = "Intel(R) 10G Virtual Network Connection"intel16.3/PROXGB/Winx64/NDIS61/ixe60x64.infintel16.3/PROXGB/Winx64/NDIS62/ixe62x64.infintel16.3/PROXGB/Winx64/NDIS62/ixn62x64.infintel16.3/PROXGB/Winx64/NDIS62/vxn62x64.infDiskName = "Intel(R) 10G Virtual Network Device Driver Disk"Service.Displayname = "Intel(R) 10G Virtual Network Connection"E10EDVF.DeviceDesc = "Intel(R) 10G Virtual Network Connection"E152EVF.DeviceDesc = "Intel(R) 10G Virtual Network Connection"intel16.3/PLATFORM/IOATDMA/Winx64/NDIS5x/ioatdma.infintel16.3/PLATFORM/IOATDMA/Winx64/NDIS5x/qd252x64.infintel16.3/PLATFORM/IOATDMA/Winx64/NDIS5x/qd3nodrv.infintel16.3/PLATFORM/IOATDMA/Winx64/NDIS61/qd160x64.infintel16.3/PLATFORM/IOATDMA/Winx64/NDIS61/qd260x64.infintel16.3/PLATFORM/IOATDMA/Winx64/NDIS61/qd3nodrv.infintel16.3/PLATFORM/IOATDMA/Winx64/NDIS62/qd162x64.infintel16.3/PLATFORM/IOATDMA/Winx64/NDIS62/qd3nodrv.infintel16.3/PLATFORM/IOATDMA/Winx64/NDIS62/qd262x64.infintel16.3/PRO1000/Winx64/NDIS5x/e1c51x64.infintel16.3/PRO1000/Winx64/NDIS5x/e1q51x64.infintel16.3/PRO1000/Winx64/NDIS5x/e1r51x64.infintel16.3/PRO1000/Winx64/NDIS5x/e1k51x64.infintel16.3/PRO1000/Winx64/NDIS61/e1c60x64.infintel16.3/PRO1000/Winx64/NDIS61/e1y60x64.infintel16.3/PRO1000/Winx64/NDIS61/v1q60x64.infDiskName = "Intel(R) Virtual Network Device Driver Disk"Service.Displayname = "Intel(R) Virtual Network Connection"E10CAVF.DeviceDesc = "Intel(R) Virtual Network Connection"intel16.3/PRO1000/Winx64/NDIS61/e1e6032e.infintel16.3/PRO1000/Winx64/NDIS61/e1k60x64.infintel16.3/PRO1000/Winx64/NDIS61/e1q60x64.infintel16.3/PRO1000/Winx64/NDIS61/e1g6032e.infintel16.3/PRO1000/Winx64/NDIS61/e1r60x64.infintel16.3/PRO1000/Winx64/NDIS62/e1q62x64.infintel16.3/PRO1000/Winx64/NDIS62/e1k62x64.infintel16.3/PRO1000/Winx64/NDIS62/e1r62x64.infintel16.3/PRO1000/Winx64/NDIS62/e1y62x64.infintel16.3/PRO1000/Winx64/NDIS62/e1c62x64.infintel16.3/PRO1000/Winx64/NDIS62/e1e6232e.infintel16.3/PRO1000/Winx64/NDIS62/v1q62x64.infDiskName = "Intel(R) Virtual Network Device Driver Disk"Service.Displayname = "Intel(R) Virtual Network Connection"E1520VF.DeviceDesc = "Intel(R) Virtual Network Connection"

[Waseem_A_Intel]

Artem,

At the moment there are no plans to support Intel 82576 controller based Virtual funtions on Windows Server 2008 R2 Guests.

Thanks,

Waseem

[idata]

Hi Waseem

Thanks for your reply!

May be I didn't furmulate correctly - 82576 based VFs are already supported in e.g. 16.3, but not every device id. For example,1520 is a 82576 based VF and is supported in 2008R2, while 10CA is also 82567 based is not supported (not in driver's ini file)

cheers

Artem.