Currently libvirt tracks these elements to consider refreshing (they are stored in the capability XMLs themselves).
<qemuctime>1558846766</qemuctime> <selfctime>1557980947</selfctime> <selfvers>4000000</selfvers> There are other ctime based caches as well like virQEMUCapsKVMUsable for /dev/kvm. The checker for the main caps is virQEMUCapsIsValid and so far checks: - libvirt ctime (binary) - libvirt version (internal build time value) - qemu bin ctime (binary) - do not not go further down if on emulated arch (won't change) - /dev/kvm got accessible since last caching (DAC) - /dev/kvm got unavailable since last caching (DAC) - microcode changed (cpuinfo) - kernel version changed - Nesting is now supported The latter sounds familiar right? => https://libvirt.org/git/?p=libvirt.git;a=commit;h=b183a75319b90d0af5512be513743e1eab950612 That is in 5.0 which means =>Disco already. Lets check how backportable that is ... ** Also affects: libvirt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830268 Title: libvirt caches nested vmx capability (in domcapabilities) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1830268/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
