Description of problem:
Need to test that passthrough of SR-IOV virtual functions works correctly.
AFAIK, the existing VFIO passthrough code should work fine as is, but we need to check.
This relies on underlying host (PowerNV) support for SR-IOV, which appears to be missing so far. Still trying to locate the correct BZ for that, so I can mark the dependency.
*** Bug 1356329 has been marked as a duplicate of this bug. ***
This is blocked by lack of host-side SR-IOV support. Moving back to ASSIGNED state until that's resolved.
The host side prerequisite, bug 1315131 is now merged into the RHEL7.4 development tree. So we should now be able to start testing this.
Since it is TestOnly, moving to ON_QA.
SR-IOV virtual functions could be generated and assigned to guest now, however it doesn't work properly inside guest, QE filed new BZ:
Bug 1421940 - [ppc64le] SR-IOV virtual functions passthrough in VFIO didn't works well in guest
Looking at bug 1421940 the VF doesn't initialize in the host, without passthrough, either. That suggests it is a problem either in a) the VF driver part of be2net or in b) the host side SR-IOV support, rather than a KVM or qemu problem.
Do you have access to any other SR-IOV capable devices, to try to eliminate the VF driver as the cause?
With the machine borrowed from the RDMA team, are you able to proceed with testing on this bug? Can I move the status back to ON_QA?
Hi David, I haven't tried with the machine from RDMA yet. But I tried with a intel XL710 adapter occasionally. It worked. So please move the status to ON_QA. I will verify this bug with the machine from RDMA team. thanks.
Zhengtong, yes I agree. I think this bug can be VERIFIED and we track the Mellanox specific problems elsewhere.
Thanks for the confirm , set Verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.