diff options
author | Juraj Linkeš <juraj.linkes@pantheon.tech> | 2021-10-12 10:03:04 +0200 |
---|---|---|
committer | Juraj Linkeš <juraj.linkes@pantheon.tech> | 2021-11-08 11:56:33 +0100 |
commit | 0cdda6c6612da7ae37de78e3d2a0b2272bab742a (patch) | |
tree | 6296ede3cd5b547c0fd82b2dfa53f10c61e0ec36 /csit.infra.vagrant/Vagrantfile | |
parent | df03302555c697928d3529ce050f3629b4e055a0 (diff) |
vpp_device: bind to vfio-pci before running tests
In rare cases, binding the whole /dev/vfio folder will result in
unusable VFs:
notice dpdk EAL: Cannot open /dev/vfio/151: Device or resource busy
[0], section 4.3.1. provides some clues as to what's going on and how to
avoid the failure. Mounting /dev/vfio reset the file descriptors of all
devices under /dev/vfio. Vfio-pci creates a device when an interface is
bound to it. The rare failure then occurs when /dev/vfio is mounted
while a process is using the file descriptors result in that process
using invalid file descriptors (or file descriptors belonging to a
different VF).
Fix the issue by binding i40e and ice VFs to vfio-pci before containers
are created and make sure that the VFs are not unbound later in testing.
Only bind DUT VFs since the TG uses the kernel driver.
[0]: https://connect.redhat.com/sites/default/files/2021-03/Cloud Native Network Function Requirements.pdf
Ticket: CSIT-1794
Change-Id: I83db91b29d16669fb034b141ad247f6f796fdf64
Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
Diffstat (limited to 'csit.infra.vagrant/Vagrantfile')
0 files changed, 0 insertions, 0 deletions