blob: 21dd5d15b6b42691171d5ad1b84e46d82033c5b4 [file] [log] [blame]
Greg Roseecc67032010-01-09 02:24:50 +00001Linux* Base Driver for Intel(R) Network Connection
2==================================================
3
Jeff Kirsherc4b8c012010-10-05 01:16:44 +00004Intel Gigabit Linux driver.
5Copyright(c) 1999 - 2010 Intel Corporation.
Greg Roseecc67032010-01-09 02:24:50 +00006
7Contents
8========
9
Greg Roseecc67032010-01-09 02:24:50 +000010- Identifying Your Adapter
11- Known Issues/Troubleshooting
12- Support
13
Greg Roseecc67032010-01-09 02:24:50 +000014This file describes the ixgbevf Linux* Base Driver for Intel Network
15Connection.
16
17The ixgbevf driver supports 82599-based virtual function devices that can only
18be activated on kernels with CONFIG_PCI_IOV enabled.
19
20The ixgbevf driver supports virtual functions generated by the ixgbe driver
21with a max_vfs value of 1 or greater.
22
23The guest OS loading the ixgbevf driver must support MSI-X interrupts.
24
25VLANs: There is a limit of a total of 32 shared VLANs to 1 or more VFs.
26
27Identifying Your Adapter
28========================
29
30For more information on how to identify your adapter, go to the Adapter &
31Driver ID Guide at:
32
Jeff Kirsherc4b8c012010-10-05 01:16:44 +000033 http://support.intel.com/support/go/network/adapter/idguide.htm
Greg Roseecc67032010-01-09 02:24:50 +000034
35Known Issues/Troubleshooting
36============================
37
38 Unloading Physical Function (PF) Driver Causes System Reboots When VM is
39 Running and VF is Loaded on the VM
40 ------------------------------------------------------------------------
41 Do not unload the PF driver (ixgbe) while VFs are assigned to guests.
42
43Support
44=======
45
46For general information, go to the Intel support website at:
47
48 http://support.intel.com
49
50or the Intel Wired Networking project hosted by Sourceforge at:
51
52 http://sourceforge.net/projects/e1000
53
54If an issue is identified with the released source code on the supported
55kernel with a supported adapter, email the specific information related
56to the issue to e1000-devel@lists.sf.net