Processors
Intel® Processors, Tools, and Utilities
14405 Discussions

SR-IOV support for Z170 and I5-6600

yning
Beginner
5,227 Views

Dose Z170 motherboard and I5-6600 support SR-IOV?@

0 Kudos
9 Replies
idata
Employee
1,661 Views

Hello yn123abc,

 

 

Thank you for contacting the Intel community.

 

 

Both the chipset and the processor support virtualization so I'm sure it will be supported, you will need to get an Intel® Ethernet Adapters and Controllers that support SR-IOV, you can check for more information here:

 

http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005722.html?wapkw=sr-iov http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005722.html?wapkw=sr-iov

 

 

In addition, you can watch a video related with the SR-IOV:

 

http://www.intel.com/content/dam/www/program/support/us/en/videos/Intel-SR-IOV-Explanation.mp4 http://www.intel.com/content/dam/www/program/support/us/en/videos/Intel-SR-IOV-Explanation.mp4

 

 

Please let me know if that can help you.

 

 

 

Best regards,

 

 

 

Ivan.

 

0 Kudos
idata
Employee
1,661 Views

Hello yn123abc,

 

 

 

I'm following on this post to ask you if the information provided above was useful for you or if you need further assistance.

 

 

 

Regards,

 

 

 

Ivan.

 

0 Kudos
yning
Beginner
1,661 Views

Hi Ivan,

I tried a SR-IOV device in this platform and meet some problems. The VF devices configuration space return 0xff for all address.

Below is my log:

[root@localhost Linux_Driver_PF0]# lspci

00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07)

00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)

00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06)

00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)

00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)

00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI # 1 (rev 31)

00:17.0 SATA controller: Intel Corporation Device a102 (rev 31)

00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port # 17 (rev f1)

00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port # 1 (rev f1)

00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port # 5 (rev f1)

00:1c.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port # 6 (rev f1)

00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port # 9 (rev f1)

00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port # 13 (rev f1)

00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)

00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)

00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)

00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)

00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)

01:00.0 Memory controller: Xilinx Corporation FPGA Card XC7VX690T

01:00.1 Memory controller: Xilinx Corporation Device 7138

01:08.0 Unassigned class [ffff]: Xilinx Corporation Device 7238 (rev ff)

01:08.1 Unassigned class [ffff]: Xilinx Corporation Device 7238 (rev ff)

01:08.2 Unassigned class [ffff]: Xilinx Corporation Device 7238 (rev ff)

01:08.3 Unassigned class [ffff]: Xilinx Corporation Device 7238 (rev ff)

04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

05:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

[root@localhost Linux_Driver_PF0]# lspci -t

-[0000:00]-+-00.0

+-01.0-[01]--+-00.0

| +-00.1

| +-08.0

| +-08.1

| +-08.2

| \-08.3

+-02.0

+-14.0

+-14.2

+-16.0

+-17.0

+-1b.0-[02]--

+-1c.0-[03]--

+-1c.4-[04]----00.0

+-1c.5-[05]----00.0

+-1d.0-[06]--

+-1d.4-[07]--

+-1f.0

+-1f.2

+-1f.3

+-1f.4

\-1f.6

[root@localhost Linux_Driver_PF0]# lspci -s 00:01.0 -vvv

00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07) (prog-if 00 [Normal decode])

Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+

Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-

Latency: 0

Bus: primary=00, secondary=01, subordinate=01, sec-latency=0

I/O behind bridge: 0000f000-00000fff

Memory behind bridge: df200000-df2fffff

Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff

Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-

BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-

PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

Capabilities: [88] Subsystem: Gigabyte Technology Co., Ltd Device 5000

Capabilities: [80] Power Management version 3

Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)

Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-

Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-

Address: fee002b8 Data: 0000

Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00

DevCap: MaxPayload 256 bytes, PhantFunc 0

ExtTag- RBE+

DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-

RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-

MaxPayload 256 bytes, MaxReadReq 128 bytes

DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-

LnkCap: Port # 2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <256ns, L1 <8us

ClockPM- Surprise- LLActRep- BwNot+

LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

LnkSta: Speed 8GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt+

SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-

Slot # 1, PowerLimit 75.000W; Interlock- NoCompl+

SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-

Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-

SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-

Changed: MRL- PresDet+ LinkState-

RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-

RootCap: CRSVisible-

RootSta: PME ReqID 0000, PMEStatus- PMEPending-

DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd-

DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd-

LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-

Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-

Compliance De-emphasis: -6dB

LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+

EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-

Capabilities: [100 v1] Virtual Channel

Caps: LPEVC=0 RefClk=100ns PATEntryBits=1

Arb: Fixed- WRR32- WRR64- WRR128-

Ctrl: ArbSelect=Fixed

Status: InProgress-

VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-

Arb: Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256-

Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff

Status: NegoPending- InProgress-

Capabilities: [140 v1] Root Complex Link

Desc: PortNumber=02 ComponentID=01 EltType=Config

Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+

Addr: 00000000fed19000

Capabilities: [d94 v1] # 19

Kernel driver in use: pcieport

0 Kudos
yning
Beginner
1,661 Views

Initializing cgroup subsys cpuset

Initializing cgroup subsys cpu

Linux version 2.6.32-504.el6.x86_64 (mailto:mockbuild@c6b9.bsys.dev.centos.org mockbuild@c6b9.bsys.dev.centos.org) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) # 1 SMP Wed Oct 15 04:27:16 UTC 2014

Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-504.el6.x86_64 ro root=UUID=1790d28d-642c-4e06-ac13-9624e84b6240 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet

KERNEL supported cpus:

Intel GenuineIntel

AMD AuthenticAMD

Centaur CentaurHauls

BIOS-provided physical RAM map:

BIOS-e820: 0000000000000000 - 000000000009c800 (usable)

BIOS-e820: 000000000009c800 - 00000000000a0000 (reserved)

BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)

BIOS-e820: 0000000000100000 - 0000000082c16000 (usable)

BIOS-e820: 0000000082c16000 - 0000000082c17000 (ACPI NVS)

BIOS-e820: 0000000082c17000 - 0000000082c41000 (reserved)

BIOS-e820: 0000000082c41000 - 0000000082c99000 (usable)

BIOS-e820: 0000000082c99000 - 000000008318a000 (reserved)

BIOS-e820: 000000008318a000 - 00000000870fd000 (usable)

BIOS-e820: 00000000870fd000 - 00000000871d7000 (reserved)

BIOS-e820: 00000000871d7000 - 0000000087312000 (usable)

BIOS-e820: 0000000087312000 - 00000000877d4000 (ACPI NVS)

BIOS-e820: 00000000877d4000 - 0000000087ffe000 (reserved)

BIOS-e820: 0000000087ffe000 - 0000000087fff000 (usable)

BIOS-e820: 0000000088000000 - 0000000088100000 (reserved)

BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)

BIOS-e820: 00000000fe000000 - 00000000fe011000 (reserved)

BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)

BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)

BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved)

BIOS-e820: 0000000100000000 - 0000000472000000 (usable)

DMI 2.8 present.

SMBIOS version 2.8 @ 0xF05E0

DMI: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z170N-WIFI-CF, BIOS FA 07/11/2016

AMI BIOS detected: BIOS may corrupt low RAM, working around it.

e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)

e820 update range: 0000000000000000 - 0000000000001000 (usable) ==> (reserved)

e820 remove range: 00000000000a0000 - 0000000000100000 (usable)

last_pfn = 0x472000 max_arch_pfn = 0x400000000

MTRR default type: write-back

MTRR fixed ranges enabled:

00000-9FFFF write-back

A0000-BFFFF uncachable

C0000-FFFFF write-protect

MTRR variable ranges enabled:

0 base 00C0000000 mask 7FC0000000 uncachable

1 base 00A0000000 mask 7FE0000000 uncachable

2 base 0090000000 mask 7FF0000000 uncachable

3 base 008C000000 mask 7FFC000000 uncachable

4 base 008A000000 mask 7FFE000000 uncachable

5 base 0089000000 mask 7FFF000000 uncachable

6 base 0088800000 mask 7FFF800000 uncachable

7 disabled

8 disabled

9 disabled

x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106

last_pfn = 0x87fff max_arch_pfn = 0x400000000

initial memory mapped : 0 - 20000000

Using GB pages for direct mapping

init_memory_mapping: 0000000000000000-0000000087fff000

0000000000 - 0080000000 page 1G

0080000000 - 0087e00000 page 2M

0087e00000 - 0087fff000 page 4k

kernel direct mapping tables up to 87fff000 @ 10000-13000

Use unified mapping for non-reserved e820 regions.

init_memory_mapping: 0000000100000000-0000000472000000

0100000000 - 0440000000 page 1G

0440000000 - 0472000000 page 2M

kernel direct mapping tables up to 472000000 @ 12000-14000

RAMDISK: 35ac8000 - 36d5b768

ACPI: RSDP 00000000000f05b0 00024 (v02 ALASKA)

ACPI: XSDT 00000000877580a8 000CC (v01 ALASKA A M I 01072009 AMI 00010013)

ACPI: FACP 000000008777abf8 0010C (v05 ALASKA A M I 01072009 AMI 00010013)

ACPI Warning: FADT (revision 5) is longer than ACPI 2.0 version, truncating length 268 to 244 (20090903/tbfadt-288)

ACPI: DSDT 0000000087758208 229F0 (v02 ALASKA A M I 01072009 INTL 20120913)

ACPI: FACS 00000000877d3f80 00040

ACPI: APIC 000000008777ad08 00084 (v03 ALASKA A M I 01072009 AMI 00010013)

ACPI: FPDT 000000008777ad90 00044 (v01 ALASKA A M I 01072009 AMI 00010013)

ACPI: FIDT 000000008777add8 0009C (v01 ALASKA A M I 01072009 AMI 00010013)

ACPI: MCFG 000000008777ae78 0003C (v01 ALASKA A M I 01072009 MSFT 00000097)

ACPI: HPET 000000008777aeb8 00038 (v01 ALASKA A M I 01072009 AMI. 0005000B)

ACPI: SSDT 000000008777aef0 0036D (v01 SataRe SataTabl 00001000 INTL 20120913)

ACPI: SSDT 000000008777b260 00490 (v02 Intel PerfTune 00001000 INTL 20120913)

ACPI: LPIT 000000008777b6f0 00094 (v01 INTEL SKL 00000000 MSFT 0000005F)

ACPI: SSDT 000000008777b788 00248 (v02 INTEL sensrhub 00000000 INTL 20120913)

ACPI: SSDT 000000008777b9d0 02BAE (v02 INTEL PtidDevc 00001000 INTL 20120913)

ACPI: SSDT 000000008777e580 00C45 (v02 INTEL Ther_Rvp 00001000 INTL 20120913)

ACPI: DBGP 000000008777f1c8 00034 (v01 INTEL 00000000 MSFT 0000005F)

ACPI: DBG2 000000008777f200 00054 (v00 INTEL 00000000 MSFT 0000005F)

ACPI: SSDT 000000008777f258 01E95 (v02 INTEL xh_rvp10 00000000 INTL 20120913)

ACPI: SSDT 00000000877810f0 05384 (v02 SaSsdt SaSsdt 00003000 INTL 20120913)

ACPI: UEFI 0000000087786478 00042 (v01 ALASKA A M I 00000000 00000000)

ACPI: SSDT 00000000877864c0 00E58 (v02 CpuRef CpuSsdt 00003000 INTL 20120913)

ACPI: DMAR 0000000087787318 000A8 (v01 INTEL SKL 00000001 INTL 00000001)

ACPI: TPM2 00000000877873c0 00034 (v03 Tpm2Tabl 00000001 AMI 00000000)

ACPI: ASF! 00000000877873f8 000A5 (v32 INTEL HCG 00000001 TFSM 000F4240)

ACPI: Local APIC address 0xfee00000

Setting APIC routing to flat.

No NUMA configuration found

Faking a node at 0000000000000000-0000000472000000

Bootmem setup node 0 0000000000000000-0000000472000000

NODE_DATA [0000000000013000 - 0000000000046fff]

bootmap [0000000000100000 - 000000000018e3ff] pages 8f

(8 early reservations) ==> bootmem [0000000000 - 0472000000]

# 0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]

# 1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000]

# 2 [0001000000 - 000202abe4] TEXT DATA BSS ==> [0001000000 - 000202abe4]

# 3 [0035ac8000 - 0036d5b768] RAMDISK ==> [0035ac8000 - 0036d5b768]

# 4 [000009c800 - 0000100000] BIOS reserved ==> [000009c800 - 0000100000]

# 5 [000202b000 - 000202b44f] BRK ==> [000202b000 - 000202b44f]

# 6 [0000010000 - 0000012000] PGTABLE ==> [0000010000 - 0000012000]

# 7 [0000012000 - 0000013000] PGTABLE ==> [0000012000 - 0000013000]

found SMP MP-table at [ffff8800000fcb90] fcb90

Reserving 130MB of memory at 48MB for crashkernel (System RAM: 18208MB)

[ffffea0000000000-ffffea000edfffff] PMD -> [ffff880028600000-ffff8800359fffff] on node 0

[ffffea000ee00000-ffffea000fbfffff] PMD -> ...

0 Kudos
idata
Employee
1,661 Views

Thanks for your reply, please allow me to find the best support for you.

 

 

 

Ivan.

 

0 Kudos
idata
Employee
1,661 Views

Hello yn123abc ,

 

 

After doing some investigation, most likely reason for this to happen is if the motherboard does not support SR-IOV since it is a client platform (vs. Server platform).

 

 

We are not familiar with that motherboard – it is strongly suggested that you checks with the motherboard manufacturer to see what the Ethernet is on it, since most likely does not support SR-IOV, thus the error.

 

 

 

Best regards,

 

 

 

Ivan.

 

0 Kudos
yning
Beginner
1,661 Views

This is a FPGA PCIe card. It's

 

inserted to the motherboard PCIe slot. The SR-IOV function worked well when

 

it's inserted in an E3/X79 platform. As I know, the PCIe lanes connect with CPU

 

directly. And the CPU can support VT-X/VT-D. So I think it's only related with

 

CPU. If there is any setting needed for I5-6600/Z170 to support SR-IOV? Have

 

this platform tested SR-IOV?
0 Kudos
idata
Employee
1,661 Views

Ok, let me find out for you.

 

 

Thank you,

 

 

Ivan.
0 Kudos
idata
Employee
1,661 Views

After further review, your best contact support is with your motherboard manufacturer, we have check on this and most likely reason for this to happen is if the motherboard does not support SR-IOV since it is a client platform.

 

 

It is strongly suggested that you check with the motherboard manufacturer to see what the Ethernet is on it, since most likely does not support SR-IOV, thus the error.

 

 

 

Best regards,

 

 

 

Ivan.

 

0 Kudos
Reply