On 12/23/2017 10:20 AM, Holger Schranz wrote: > Sorry for an additional question: > > In the bug report where Jim was wrote in his answer: > https://libvirt.org/git/?p=libvirt.git;a=commit;h=2d07f1f0ebd44b0348daa61afa0de34f3f838c22 > > is a pointer to the report: > https://bugzilla.redhat.com/show_bug.cgi?id=1522682 > > In this report the fixed version is: libvirt-3.9.0-6.el7 > > How can I check/find whether this fix is include in the 3.10 which > I used? It's not fixed there: $ git describe 2d07f1f0ebd44b0348daa61afa0de34f3f838c22 v3.10.0-32-g2d07f1f0e Which means, that the commit is 32'nd after 3.10.0 release. You'll have to wait for: a) new release, b) your distro to pick up the commit and backport it. Michal _______________________________________________ libvirt-users mailing list libvirt-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvirt-users
