Libvirtd stopped working after pacman -Syu

GreenBackbone · Yesterday 06:31:42

After a full system update, libvirtd stopped working, virt-manager will not connect to qemu:///system
i solved this but wanted to leave reference in case some one else is having this problem
there isn't any mention to any change in archlinux.org and there is no mention to a change in the libvirt wiki article

systemctl start libvirtd gives "Dependency failed for libvirt legacy monolithic daemon."

to fix this disable libvirtd.socket in case it is enabled,
and enable the following sockets:
virtqemud.socket
virtnetworkd.socket

i was able to run my vms after those were enabled, and just to be sure i also enabled the following:
virtsecretd.socket
virtstoraged.socket

hope this helps some one...

Last edited by GreenBackbone (Yesterday 08:29:47)

seth · Yesterday 08:22:31

systemctl start libvirtd gives "dependecy error"
and journalctl -xe says "Error in monolithic libvirt dependecy"

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

GreenBackbone · Yesterday 08:30:25

seth wrote:

systemctl start libvirtd gives "dependecy error"
and journalctl -xe says "Error in monolithic libvirt dependecy"
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

sorry, edited with the exact error message

seth · Yesterday 08:46:45

https://github.com/NixOS/nixpkgs/issues … 4092515359

Is this you: https://www.reddit.com/r/cachyos/commen … nt_update/ ?

GreenBackbone · Yesterday 09:07:27

seth wrote:

https://github.com/NixOS/nixpkgs/issues … 4092515359
Is this you: https://www.reddit.com/r/cachyos/commen … nt_update/ ?

no, i didnt messed with tpm at all..
also that is from 18 days ago, i just had this problem yesterday morning (march 20th)
also i didnt posted about this anywhere else, or asked about it anywhere else..
and im not using cachy, im using arch..

seth · Yesterday 09:24:12

I asked because of the similar commands compared to your pre-edit OP and the "cgb" partly meeting the initials of your nick and to determine timing and ubiquity of the problem.

Did you check for /var/lib/libvirt/secrets/secrets-encryption-key presence and errors?

GreenBackbone · Yesterday 09:56:17

seth wrote:

I asked because of the similar commands compared to your pre-edit OP and the "cgb" partly meeting the initials of your nick and to determine timing and ubiquity of the problem.
Did you check for /var/lib/libvirt/secrets/secrets-encryption-key presence and errors?

its a far reach to go from cbg to greenbackbone i think
but no, i didnt check for errors in secrets-encryption-key,

all i did was to reinstall qemu libvirt and virt-manager because maybe in the update some dependency was left out i thought, but didnt changed nothing,
then i ran 'systemctl list-unit-files --type=socket' and went though each of them, and enabled virtqemud.socket and with that virt-manager was able to connect to qemu:///system, but was missing the virtual network so i enabled virtnetworkd.socket and with that i was able to get my vm running again, and just for "being safe" i enabled all sockets that had virt in them that i thought seemed relevant, i dont think that hurts since sockets only execute services if needed...
i spent a few hours with this until i got my vm running again, vm that i need for work, so i thought this post would help, i didnt think it would be a big deal

seth · Yesterday 12:23:13

i didnt think it would be a big deal

It's not but it's better to get to the bottom of this than to pitch anecdotal resolutions.
You can check older journals to see whether you had those secrets-encryption-key related errors.

sudo journalctl | grep -C3 secrets-encryption-key

GreenBackbone · Yesterday 16:21:16

seth wrote:

i didnt think it would be a big deal
It's not but it's better to get to the bottom of this than to pitch anecdotal resolutions.
You can check older journals to see whether you had those secrets-encryption-key related errors.
sudo journalctl | grep -C3 secrets-encryption-key

i did checked journal but didn't see any messages about that, the message was very generic about dependency too, unfortunately i kept clearing the journal every time i tried new things to see the logs because the old messages threw me off, so now i don't have the exact error message it gave me, probably a horrible practice that's why i deleted that from the original post i made

Arch Linux

#1 Yesterday 06:31:42

Libvirtd stopped working after pacman -Syu

#2 Yesterday 08:22:31

Re: Libvirtd stopped working after pacman -Syu

#3 Yesterday 08:30:25

Re: Libvirtd stopped working after pacman -Syu

#4 Yesterday 08:46:45

Re: Libvirtd stopped working after pacman -Syu

#5 Yesterday 09:07:27

Re: Libvirtd stopped working after pacman -Syu

#6 Yesterday 09:24:12

Re: Libvirtd stopped working after pacman -Syu

#7 Yesterday 09:56:17

Re: Libvirtd stopped working after pacman -Syu

#8 Yesterday 12:23:13

Re: Libvirtd stopped working after pacman -Syu

#9 Yesterday 16:21:16

Re: Libvirtd stopped working after pacman -Syu

Board footer