MX Linux Forum

$ sudo systemctl edit libvirtd
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

I'm running Arch Linux and have been running into trouble trying to use QEMU/KVM on

Code: Select all

virt-manager

, and this problem is likely to address my issues while using the similar

Code: Select all

gnome-boxes

.

Resolution

This error was related to the driver opencl-amdgpu-pro-orca. This answer details some background of what causes the error. Here's how I went about resolving the problem:

1. Run

Code: Select all

sudo systemctl edit libvirtd

, which opens Nano.

• That command creates a temporary file which will save to become

  Code: Select all

  override.conf

  within the directory of the

  Code: Select all

  libvirtd

  service.

2. Enter the following into this (empty in my case) file:

Code: Select all

[Service]
Environment="LD_LIBRARY_PATH=/usr/lib"

3. Restart

Code: Select all

libvirtd

with

Code: Select all

sudo systemctl restart libvirtd

.
4. Open

Code: Select all

virt-manager

. The error should not be present.

• It's worth noting that I did not need to reboot following these changes.

0x6A7232 wrote: Sat Apr 06, 2024 8:23 pm At this point I might as well just throw in the towel as nothing seems to work right on SysV without workarounds that don't always work 100% of the time

That command creates a temporary file which will save to become

Code: Select all

override.conf

within the directory of the

Code: Select all

libvirtd

service.

DukeComposed wrote: Sat Apr 06, 2024 8:51 pm

0x6A7232 wrote: Sat Apr 06, 2024 8:23 pm At this point I might as well just throw in the towel as nothing seems to work right on SysV without workarounds that don't always work 100% of the time

Funny, I'd say the same thing about systemd.

That command creates a temporary file which will save to become

Code: Select all

override.conf

within the directory of the

Code: Select all

libvirtd

service.

Maybe I'm misunderstanding something, but what you're describing here are the basic steps of opening a text file and editing it. Is this really something you need your init system to do for you? Admittedly, systemd isn't just an init system anymore but a large, complex, and poorly-coded Gordian knot of interdependent libraries and bespoke tools. If you're complaining that editing files is broken under sysvinit, I have to wonder why you're using systemctl at all just to invoke a text editor.

I think you can specify kernel options in MX Boot Options if you want to stick to systemd full-time. There's also a systemd-only MX Linux respin that makes this step unnecessary.

0x6A7232 wrote: Sun Apr 07, 2024 12:52 am The issue is that the text file does not exist and must be created. Where is it supposed to be? In the directory of the libvirtd service. Oh, but I'm not really using systemd, now am I? So I'd much prefer to use a command to put it where it needs to go without me stabbing in the dark.

I don't mind using SysV but for whatever reason everyone is going full exclusive systemd (which is very odd given how you have 5 different install instructions for if you're using Debian based, Fedora, Arch based, etc etc etc).

Regardless, for now I'll probably just boot systemd and run the systemctl command. After that I might go back, idk.