Looking at the (not necessarily complete) list of related changes: 91684829 /dev/kvm check caching b183a753 KVM Nesting 55e5eb94 Non Native 88983855 Fix KVM enable check (has some wider code implications) -- above is disco -- 52b7d910 kernel version -- above is cosmic -- b527589d microcode -- above is bionic -- d03de54e bigger rework (using virFileCache) 731cfd5f minor rework for _virQEMUCapsCachePriv 56a047a6 minor rework (arg qemuctime) 7fcf66cf minor rework (location libvirt check) a63ef877 bigger rework (args libvirt ctime) d87df9bd KVM permission change c29e6d48 bigger rework (Caps caching in general) f2dd7259 move and static virQEMUCapsIsValid 729aa67d qemu ctime in XML 68c70118 host model in caps -- above is xenial --
We see a huge block of reworks which make backport to Xenial harder. And by that also a bigger risk which we should not do for an SRU. After all there is UCA Xenial-Queens which will is an official source for newer code as in Bionic. Given the severity/importance/commonality of those issues/use-cases I'd try to: - get Nesting to Xenial/Bionic/Cosmic - get NonNative to Bionic/Cosmic - get kernelversion to Bionic While X lacks many of the further checks, as outlined the risk/work seems too much given that we had no issues in that regard reported up to now - and there is an, albeit ugly, userspace workaround in place (delete files e.g. on boot as most of those actions require a reboot). I'll check if that would work as intended after lunch. -- 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
