On Fri, Jul 14, 2023 at 03:45:11PM +0100, Daniel P. Berrangé wrote:
On Fri, Jul 14, 2023 at 04:39:39PM +0200, Andrea Bolognani wrote:
This logic was necessary when socket activation was introduced in libvirt 5.6.0/5.7.0 in order to guarantee smooth upgrades.
These days, even the oldest platform that we target ships a version of libvirtd that implements socket activation, so the additional code is no longer useful and we can treat libvirtd the same as all other services.
The upgrade path though can come from a platform that we don't support, but we do support upgrade from.
eg we don't support RHEL-8, but upgrades from 8 -> 9 are supported. I think it is premature to declare this upgrade code no longer useful.
We do target RHEL 8 still :) RHEL 8 got libvirt 6.0.0, which comes with socket activation support, back in 2020 with RHEL 8.3. Based on our support policy we only consider the latest point release a valid target anyway, but in this case we should absolutely be in the clear. -- Andrea Bolognani / Red Hat / Virtualization