Precisely. I am using libvirt and VFIO to assign SRIOV VFs to guests. Interestingly, as per my Arch package bug report, using 4.8.X doesn't trigger the bug for me, simply moving to kernel 4.9.5+ triggers it (nothing else changed in other packages or guest domain XML).
I built a custom package of libnl from the master on Github that includes the commit of your patch. I had seen this issue earlier on but had rebuilt libvirt without libnl as a work around. Your patch fixes this permanently. I'm hoping a new release of libnl is forthcoming and used or the Arch package maintainer pulls the fix in some other how. I recognize your name from the mailing list and issue report. Thanks for the fix and the note! On Mon, Jan 30, 2017, at 05:31 PM, Laine Stump wrote: > On 01/30/2017 03:56 PM, globalgorri...@fastmail.fm wrote: > > Heads-up if you're using libvirt and Arch Linux and networking VFs and > > kernel 4.9+. > > > > https://bugs.archlinux.org/task/52778 > > As the person who both reported the bug and posted the patch that fixes > it, I can verify that the problem is unrelated to the kernel version or > libvirt, (or VFIO for that matter, other than the tangential fact that > some people use VFIO to assign SRIOV VFs to guests), but is completely a > bug in the latest release of libnl: > > http://lists.infradead.org/pipermail/libnl/2017-January/002270.html > > Update libnl and it will be solved. _______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
