Ubuntu
libvirt package

  1. Bug #1830268
  2. Comment #2

Comment 2 for bug 1830268

Revision history for this message
Christian Ehrhardt  (paelzer) wrote : Re: libvirt caches nested vmx capability (in domcapabilities)

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 ...