Hi list, I'm running AlmaLinux 9.3 and I'm running several virtual machines using qemu-kvm and libvirtd ( and virt-manager). 3 VMs starts during system boot (configured with "virsh autostart VMNAME"). All works as expected until I loaded a old vm config file. When I tried to run "systemctl reload libvirtd" I got: "libvirtd.service is not active, cannot reload." It is enable on boot and running "systemctl status libvirtd" I get: Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Active: inactive (dead) since Thu 2024-01-25 16:32:40 CET; 4min 55s ago Duration: 5min 14.530s It reports that it is inactive (really dead) because I can't find it inside process table. Rebooting the system, I found libvirtd process with argument "--timeout=120" and after 120 seconds it dies. Reading libvirtd systemd unit I found Environment=LIBVIRTD_ARGS="--timeout 120" and from the man page I get: "t, --timeout *SECONDS* Exit after timeout period (in seconds), provided there are neither any client connections nor any running domains." Here I found something strange. On boot I have 3 running domains but libvirtd dies after 120 seconds. To load new configuration I need to run restart and virt-manager works without problem also if libvirtd is not running. This is a misconfiguration or it is a bug? Thank you in advance. Alessandro.
Il 25/01/24 16:44, Alessandro Baggi ha scritto:
Hi list, I'm running AlmaLinux 9.3 and I'm running several virtual machines using qemu-kvm and libvirtd ( and virt-manager). 3 VMs starts during system boot (configured with "virsh autostart VMNAME").
All works as expected until I loaded a old vm config file.
When I tried to run "systemctl reload libvirtd" I got:
"libvirtd.service is not active, cannot reload."
It is enable on boot and running "systemctl status libvirtd" I get:
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; preset: disabled) Active: inactive (dead) since Thu 2024-01-25 16:32:40 CET; 4min 55s ago Duration: 5min 14.530s
It reports that it is inactive (really dead) because I can't find it inside process table.
Rebooting the system, I found libvirtd process with argument "--timeout=120" and after 120 seconds it dies.
Reading libvirtd systemd unit I found Environment=LIBVIRTD_ARGS="--timeout 120" and from the man page I get:
"t, --timeout *SECONDS*
Exit after timeout period (in seconds), provided there are neither any client connections nor any running domains."
Here I found something strange. On boot I have 3 running domains but libvirtd dies after 120 seconds.
To load new configuration I need to run restart and virt-manager works without problem also if libvirtd is not running.
This is a misconfiguration or it is a bug?
Thank you in advance. Alessandro.
Hi, searching on the web I found this: https://access.redhat.com/solutions/7040687 (it requires a rhel login to view the resolution). They report: "It is expected behavior. Please ignore the service status because the libvirtd.service will wake up when some management app connects to its socket. If the service does not wake up or work correctly, please open the support case." They suggest to run "virsh list" and libvirtd should wake up but this not happens because running 'systemctl status libvirtd' I get dead. The same when running Virt-Mamanager or managing VMs with cockpit. This is a bug? libvirtd does not wake up when needed and I can't open support case. Any help is appreciated.
Hi, searching on the web I found this: https://access.redhat.com/solutions/7040687 (it requires a rhel login to view the resolution).
They report:
"It is expected behavior. Please ignore the service status because the libvirtd.service will wake up when some management app connects to its socket. If the service does not wake up or work correctly, please open the support case."
They suggest to run "virsh list" and libvirtd should wake up but this not happens because running 'systemctl status libvirtd' I get dead. The same when running Virt-Mamanager or managing VMs with cockpit.
This is a bug? libvirtd does not wake up when needed and I can't open support case.
Any help is appreciated.
Hi, I noticed also that if I start libvirtd and run virt-manager (before the timeout) it becomes died before its timeout.
Thanks for bringing this up! I’ve had similar issues with AlmaLinux. In my experience, reconfiguring the relevant packages and checking dependencies usually solves the problem. I also find that looking more closely at the logs can help uncover hidden bugs that I may not have noticed. Have you tried anything else?
participants (2)
-
Alessandro Baggi -
Felix Andrea