Ubuntu
libvirt package

  1. Bug #1830268
  2. Comment #3

Comment 3 for bug 1830268

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

There also was the discussion (on this bug) to re-probe on reboots in general.
That was already discussed upstream multiple times, but didn't happen to be implemented so far.
There is some pro (more reliable data) and con (this is really a heavy task) to this.

See discussions on:
=> https://www.redhat.com/archives/libvir-list/2017-October/msg00916.html
=> https://www.redhat.com/archives/libvir-list/2018-January/msg00657.html

So far the outcome always was to add just another minor check for whatever new case was identified instead of really probing all again on each reboot.

For some stuff that was mentioned in IRC discussions:
In no way seems "refresh on libvirtd restart" an option.
=> https://www.redhat.com/archives/libvir-list/2018-December/msg00722.html
=> https://www.redhat.com/archives/libvir-list/2019-January/msg00061.html
=> https://www.redhat.com/archives/libvir-list/2018-September/msg00662.html

Nor "provide something nicer than rm xml files"
=> https://www.redhat.com/archives/libvir-list/2018-November/msg00614.html

For all the MDS and its predecessors I wonder if "/proc/cpuinfo flags" would be another good candidate going forward to polish the existing caching mechanism even further. I might send an RFC about that, but will look at back-portability of the existing first.