Hide Forgot
For Intel cards add 'enable VT-d for VFIO driver.' Reported by: rhn-support-cfields https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/network_functions_virtualization_planning_and_configuration_guide/ch-hardware-requirements#annotations:b4b5d678-62bc-4fa4-8128-7ae03097ddd1
We recently had a support case for a customer trying to use ovs-dpdk but had VT-d disabled. Symptoms looked like this: overcloud-computeo-0 ovs-vswitchd[49803]: ovs|00206|dpdk|ERR|EAL: Cannot open /dev/vfio/noiommu-1: Permission denied overcloud-computeo-0 ovs-vswitchd[49803]: ovs|00207|dpdk|ERR|EAL: Driver cannot attach the device (0000:12:00.1) This was fixed by enabling VT-d in bios. See Intels doc here: https://doc.dpdk.org/guides-16.04/linux_gsg/nic_perf_intel_platform.html#bios-settings Under section 7.1.2 Bios Settings "Disable all virtualization options when you test the physical function of the NIC, and turn on VT-d if you wants to use VFIO." Let's get "turn on VT-d for Intel nics if you want to use the VFIO driver" which is what we use for ovs-dpdk.
Published: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/network_functions_virtualization_planning_and_configuration_guide/index#review_bios_settings
Yes, the published NFV guide looks good.