VM Network Performance leads to SR-IOV but 'NoOSCSupport'

hello,

we upgraded server that's been in production 3 years - running server 2003. it's running hyper-v server 2012 r2 server 2012 r2 vm, we're seeing degraded network performance - has gigabit ethernet yet we're seeing 120mbps sustainable it, yet hitting on 600mbps baremetal server.

now onboard network controller isn't supported in server 2012 r2 - there microsoft inbuilt drivers, intel can't support due hardware limitations (it doesn't meet whql minimums 2012 r2). we've upgraded intel i350-t2 gives both native support in '12r2 , sr-iov (or thought) - sr-iov apparently our best option greater performance network devices vm.

unfortunately, however, sr-iov isn't working - get-netadaptersriov tells "nooscsupport". apparently there issue osc handoff, seems undocumented issue there hardly information available beyond initial technet article - http://technet.microsoft.com/en-us/library/jj130915.aspx

i have attempted speak technical support mainboard manufacturer , said if feature isn't in documentation doesn't exist.

so i'm trying determine 2 things - if there way around osc handoff limitation can enable sr-iov or if that's not possible on hardware (asus z8pe-d12x), and/or other options have improve network performance vm?

thanks help,

trevor

you should keep looking reasons can't hit 1gb nic.  should see close that.  try enabling vmq, large send offload, etc.  sr-iov shouldn't necessary network throughput under hyper-v until you're using 10gb or 20gb nics.

but, since asked specific question _osc, means bios has agreed let os (windows) manage pci express aspects of motherboard.  negotiation exists because there operating systems (like windows server 2003) written before pci express existed , bios has manage pci express when these installed.

doing sr-iov involves changing quite bit surrounding way pci express configured, , requires bios relinquish control.  server makers reluctant relinquish control because means need test servers in 2 different modes.  no server going support sr-iov unless designer of bios targeting sr-iov support, yours wasn't.

Windows Server  >  Hyper-V