Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VF bound to Kernel driver #316

Open
ahalimx86 opened this issue Sep 5, 2018 · 3 comments
Open

VF bound to Kernel driver #316

ahalimx86 opened this issue Sep 5, 2018 · 3 comments

Comments

@ahalimx86
Copy link

Hi,
Is it possible to have the VFs bound to Linux kernel drivers and PF with igb_uio then have VFd to configure those VFs? Or it is a hard requirement to have VF bound to vfio-pci/igb_uio?

I'm considering a use-case where I might have some VFs bound to Kernel driver and some to the vfio-pci. Are there any implications one should be particularly concerned about such scenario? Thanks.

@azelezniak
Copy link
Collaborator

You can bind VFs to kernel ixfbevf driver as well as igb_uio/vfio-pci or pci-stub if you use VM’s.
In any case VFd has to be started before VFs could be used.

@ahalimx86
Copy link
Author

Thats great, thanks for the info. What about i40evf with Fortville NICs(X710)? I'm testing with this NIC at the moment. I have tried using VF's with both kernel driver and dpdk driver. It looks like VFd is applying the VF configurations regardless of the driver type, but I haven't verified them. However, I noticed when I stop VFd daemon the system crushes down. I was wondering if this was because of the VF drivers.

@azelezniak
Copy link
Collaborator

X710 NICs were not thoroughly tested yet.
Try do unload kernel i40evf driver or stop DPDK application bound to VF before stopping VFd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants