[Bug 211062] [ixv] sr-iov virtual function driver fails to attach
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 18 Oct 2021 21:35:49 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211062 xygzen <j@iamplugged.in> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |j@iamplugged.in --- Comment #15 from xygzen <j@iamplugged.in> --- If it helps any - I was getting the exact same issue at one cloud provider. When I enabled SR-IOV in the BIOS it had a cryptic message about needing to enable ASPM (Active State Power Management) for the SR-IOV to work properly. Nothing I did allowed it to work. When I switched providers, there was an ASPM setting in the BIOS of the new machine that wasn't there previously - and these were both Supermicro boards so it looks like not all motherboards support this functionality or maybe there is a newer version of the BIOS that has the setting correctly enabled. I still needed to enable hw.pci.honor_msi_blacklist=0 in /boot/loader.conf and used the latest IX and IXV drivers from Intel: IX - v3.3.25 - https://www.intel.com/content/www/us/en/download/14303/intel-network-adapters-driver-for-pcie-10-gigabit-network-connections-under-freebsd.html IXV -v.1.5.28 - https://www.intel.com/content/www/us/en/download/645984/intel-network-adapter-virtual-function-driver-for-pcie-10-gigabit-network-connections-under-freebsd.html Once I ran iovctl -C -f /etc/iovctl.conf the VF driver correctly attached to ixv0 (no passthrough) and the pci devices were configured correctly for the ixv1-3 for passthrough without drivers attached. Setting iovctl_files="/etc/iovctl.conf" in rc.conf and changing the ip to be configured on ixv0 instead of ix0 got this up and running automatically on reboot. If you're looking for a good cloud host with support for this I can highly recommend https://www.zare.com Hope that helps! -- You are receiving this mail because: You are the assignee for the bug.