[Pkg-libvirt-maintainers] [RFC] Restart libvirtd.service after installing certain libvirt modules

[Michael Biebl]

Am 17.01.25 um 08:27 schrieb Christian Ehrhardt:
> On Thu, Jan 16, 2025 at 9:58 PM Sergio Durigan Junior
> <sergiodj at debian.org> wrote:
>>
>> On Thursday, January 16 2025, Andrea Bolognani wrote:
>>
>>> Sergio,
>>>
>>> topics like this one can, and indeed *should*, be discussed on the
>>> pkg-libvirt-maintainers list. Continuing the thread there.
>>
>> Thanks for the reply, Andrea, and apologies for not sending the message
>> to the mailing list.  I guess I had the impression that it was
>> semi-abandoned.
>>
>>> On Mon, Jan 13, 2025 at 06:49:48PM -0500, Sergio Durigan Junior wrote:
>>
>>>> The discussion I want to have with you is whether it makes sense to
>>>> implement this service restart upon the installation of *certain*
>>>> modules.  I'm not sure if this has been discussed/decided already; if it
>>>> has, would you mind sharing the rationale with us, please?
>>>
>>> This makes total sense, and I'm kinda surprised that we don't have it
>>> already.
>>>
>>> Restarting libvirtd is supposed to be a completely safe operation,
>>> even when guests are running. We would be in trouble during regular
>>> package upgrades otherwise!
> 
> I agree, and even if hooking to all packages, their
> installation/upgrade would still not be a high frequency thing.
> By the usage of triggers as proposed by Michael in most cases it will
> not be an increase of restarts at all.
> 
>>> There's an old MR by Michael that was going in the right direction:
>>>
>>>    https://salsa.debian.org/libvirt-team/libvirt/-/merge_requests/162
>>>
>>> Unfortunately I was unable to give it the attention it deserved at
>>> the time and so, understandably, it's been been closed by the author.
>>> Sorry Michael!
> 
> Indeed, neither of us found the time for it back then :-/ Sorry Michael.
> But now it comes quite handy, while no more perfectly matching and
> needing to be extended to the drivers, it is laying the groundwork how
> it conceptually might look like.

I've reopened the MR and rebased it. Just in case you want to take 
another look.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-maintainers/attachments/20250119/9f180753/attachment.sig>