QEMU/KVM, slight hiccup on setup

Topic: QEMU/KVM, slight hiccup on setup (Read 811 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.

QEMU/KVM, slight hiccup on setup

12 May 2025, 17:09:08

I was setting up QEMU with KVM and virtmanager today and I had a slight hiccup on the setup.
I'm on runit and while it mentioned that libvirtd had to be setup as a service, it didn't mention libvirtlogd or libvirtlockd which are both necessary for it to work. (both are included in libvirtd-runit package)
Just thought you guys should know, I think it should tell you to link all 3 to /run/runit/service/

Re: QEMU/KVM, slight hiccup on setup

Reply #1 – 13 May 2025, 11:02:39

Can you link to the process you are following?

I used the arch instructions and just substituted for systemd. It was convoluted with multiple threads needing to be followed (3 or 4 tabs of instructions open at once) but worked out in the end and mentioned starting these services.

Re: QEMU/KVM, slight hiccup on setup

Reply #2 – 14 May 2025, 17:14:36

Quote from: metwo – on 13 May 2025, 11:02:39

Can you link to the process you are following?

I used the arch instructions and just substituted for systemd. It was convoluted with multiple threads needing to be followed (3 or 4 tabs of instructions open at once) but worked out in the end and mentioned starting these services.

https://www.youtube.com/watch?v=wxxP39cNJOs
this video from mental outlaw, he was using artix openrc.

Re: QEMU/KVM, slight hiccup on setup

Reply #3 – 20 May 2025, 05:44:43

I would recommend following official pages.

Code: [Select]

Start both libvirtd.service and virtlogd.service. Optionally enable libvirtd.service (which will also enable virtlogd.socket and virtlockd.socket units, so there is NO need to also enable virtlogd.service).

Another possibility is to only start/enable libvirtd.socket and virtlogd.socket for on-demand socket activation. [/quote]

https://wiki.archlinux.org/title/Libvirt