Thanks, to answer the questions:
- Almalinux 9.3
- Libvirt 9.5.0
- It should be modular libvirt, as in addition to libvirtd there are additional daemons running, such as virtqemud and virtnodedevd. Probably because we included nova::compute::libvirt::virtqemud and nova::compute::libvirt::virtnodedevd, as it seemed necessary for VM migration
- No, with the periodic run stopped, journalctl does not report starts/stops for libvirtd, even if there are VMs running on that node
> they change behavior of libvirtd to automatically shutfown after no activity
If this is the desired behaviour, the module could have a parameter such as manage_service to make the service management optional? This might default to true to be in line with the current puppet-nova module behavior
Thanks, to answer the questions: :libvirt: :virtqemud and nova::compute: :libvirt: :virtnodedevd, as it seemed necessary for VM migration
- Almalinux 9.3
- Libvirt 9.5.0
- It should be modular libvirt, as in addition to libvirtd there are additional daemons running, such as virtqemud and virtnodedevd. Probably because we included nova::compute:
- No, with the periodic run stopped, journalctl does not report starts/stops for libvirtd, even if there are VMs running on that node
> they change behavior of libvirtd to automatically shutfown after no activity
If this is the desired behaviour, the module could have a parameter such as manage_service to make the service management optional? This might default to true to be in line with the current puppet-nova module behavior