On 2/10/24 11:53, Johannes Kastl wrote:
Hi all,
is anyone else experiencing issues with libvirt since mid of this week?
I can no longer start VMs using vagrant. Vagrant hangs at "Waiting for domain to get an IP address..." and never gets anywhere.
Existing VMs can be started using virsh or libvirt, so it might be an issue with vagrant itself. But it was working until mid of this week, despite being outdated (due to the licensing change).
I noticed some errors regarding missing directories on Feb 8th and today:
Feb 08 13:09:28 baten systemd[1]: Starting libvirt legacy monolithic daemon... Feb 08 13:09:28 baten libvirtd[7841]: libvirt version: 10.0.0 Feb 08 13:09:28 baten libvirtd[7841]: hostname: baten Feb 08 13:09:28 baten libvirtd[7841]: Failed to initialize libnetcontrol. Management of interface devices is disabled Feb 08 13:09:28 baten systemd[1]: Started libvirt legacy monolithic daemon. Feb 08 13:09:29 baten libvirtd[7841]: Interner Fehler: failed to query mdevs from mdevctl: Error: Required directory "/usr/lib/mdevctl/scripts.d/callouts" doesn't exist. This may indicate a packaging or installation error Feb 08 13:11:28 baten systemd[1]: libvirtd.service: Deactivated successfully.
or
Feb 10 18:31:36 baten systemd[1]: Started libvirt legacy monolithic daemon. Feb 10 18:31:37 baten libvirtd[4420]: Interner Fehler: failed to query mdevs from mdevctl: Error: Required directory "/usr/lib/mdevctl/scripts.d/notifiers" doesn't exist. This may indicate a packaging or installation error
And sure enough there are no directories in /usr/lib/mdevctl/scripts.d/ on all of my machines...
You are probably getting hit by the update of glibc from 2.38 to 2.39. It shows in VirtualBox as no USB passthrough. I added the Slowroll repo and downdgraded glibc along with the 15 dependent packages and the USB access is restored. See boo#1219766 for repo details. Larry