Hi,
After upgrade to 1.5 my 2 ZVM hosts do not start. One is an ubuntu server and another HAOS. In both cases same error message: “Failed to connect socket to ‘/var/run/libvirt/virtlogd-sock’: No such file or directory”. Any idea what went wrong and how can I fix it?
Thanks for sharing the details.
I suggest checking whether libvirt services are running correctly after the 1.5 update, as the error:
Failed to connect socket to ‘/var/run/libvirt/virtlogd-sock’: No such file or directory
usually means virtlogd (logging service for VMs) didn’t start.
A few quick things to try:
1) Check service status
systemctl status virtlogd
systemctl status libvirtd
2) Try restarting
systemctl restart virtlogd
systemctl restart libvirtd
3) Confirm the socket exists
ls -l /var/run/libvirt/virtlogd-sock
If the socket is missing, restarting services normally recreates it.
Also, I suggest letting us know:
• ZVM type (native or container)
• If any VMs run, or all fail
• Logs from:
journalctl -u virtlogd --no-pager | tail -n 50
This will help us confirm if the issue is service-level or config-level after the upgrade.
1 Like
Hi, I took a risk to use beta version and this somehow solved my problem. Will stay with this beta until new stable version will be released.
Keep an eye on your ZVM hosts for a little while to make sure everything is stable.
If you have time, I also suggest sharing which beta build you installed, just so others can reference it if they run into the same virtlogd-sock issue.
1 Like
ZimaOS v1.5.1-beta1 solved my problem
2 Likes