Hello Andrea, Daniel,

I would like to understand how we can give some momentum to this topic,

@Daniel P. Berrangé : Are you still convinced that libvirt should only deploy the modules-load.d file as part of the installation ?
If we take this route, one solution to work-around the reboot need is to call the /usr/lib/systemd/systemd-modules-load binary on the installed conf file (example : /usr/lib/systemd/systemd-modules-load /etc/modules-load.d/msr.conf) at installation.

If you both agree on this design, I will go ahead and submit something.


On Fri, Jul 25, 2025 at 3:48 PM Andrea Bolognani <abologna@redhat.com> wrote:
On Fri, Jul 25, 2025 at 01:25:47PM +0100, Daniel P. Berrangé wrote:
> On Fri, Jul 25, 2025 at 01:45:51PM +0200, Hector Cao wrote:
> > One thing I'm worried about with modules-load.d approach is that at libvirt
> > installation, the module
> > is not actually loaded, a reboot is necessary to make it happen.
>
> You need that to make systemd service activation happen too, so the need
> for a reboot isn't new.

Unlike Fedora/RHEL, on Debian/Ubuntu services are automatically
started right after the package is installed. So a reboot is
generally not needed.

--
Andrea Bolognani / Red Hat / Virtualization



--
Hector CAO
Software Engineer – Partner Engineering Team
hector.cao@canonical.com
https://launchpad.net/~hectorcao