Based on RFC posted and discussion therein:
http://www.redhat.com/archives/libvir-list/2015-May/msg00655.html
Threw away 1/2 from the RFC, but kept 2/2 since that seemed to be
generally acceptible - even if it's still not clear the exact steps
taken in order to create the problem. So 2/2 becomes 1/2 here.
Added in a new 2/2 which adds LIBVIR_VERSION_NUMBER as a variable
in the decision process for whether to refresh the cache. The theory
behind this is if there's any oddities with time algorithms and
time changes perhaps affecting 'ctime' - at least if the version
is different in the cache file than determined for the running
libvirtd, then we'll refresh that cache file.
John Ferlan (2):
qemu: Force capabilities cache refresh if libvirtd date is different
qemu: Add libvirt version check to refresh capabilities algorithm
src/qemu/qemu_capabilities.c | 25 +++++++++++++++++++------
1 file changed, 19 insertions(+), 6 deletions(-)
--
2.1.0