On 2015/08/13 22:21, Bert Kiers wrote: > On Thu, Aug 13, 2015 at 07:19:15PM +0900, Masanobu SAITOH wrote: > >> NetBSD's ixv(4) can be test with Linux KVM or VMware vSphere. >> Some people other than me must be familar with them :) > > Ah! We have Linux boxes running KVM with network hardware: > 02:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10-Gigabit > X540-AT2 (rev 01) > > But inside a VM the network shows as: > 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
It's vioif(4). > I doubt that will be ixv when I boot NetBSD. I guess there is some form > of bridging going on because there are a lot of vnet interfaces in the > host. I think I need a different method of networking for ixv. Will > have a look this weekend. To use ixv, 0) Add intel_iommu=on pci=assignbus to your kernel's boot argument 1) Use "max_vfs=n" (e.g. n=8) when probing ixgbe (e.g. add "options ixgbe max_vfs=8" into /etc/modprobe.d/ixgbe.conf) 2) modprobe -r ixgbe; modprove ixgbe 4) lspci. You will see some virtual functions. The number of virtual function is the same as the number of max_vfs > 01:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) > 02:10.0 Ethernet controller: Intel Corporation 82599 Ethernet Controller Virtual Function (rev 01) 5) Add passthrough setting of a virtual function. (You might want to add "blacklist ixgbevf" in /etc/modprobe.d/blacklist.conf) 6) You might have to add some other variable settings to your kernel's boot argument. -- ----------------------------------------------- SAITOH Masanobu (msai...@execsw.org msai...@netbsd.org)