You are not logged in.

#1 2025-07-03 23:56:01

Arctic01
Member
Registered: 2025-07-03
Posts: 2

Starting libvirtd causes a complete system crash

Hey yall, I have been trying to figure this one out for a long time now and I think it is time to ask here. When attempting to spin up a VM using QEMU my entire system completely shuts off. I have attached an cut down version of my journal with lines from other services removed, anything I was not sure of I left in. I will note, the last line in the log is actually the last line, I did not cut anything after it; the system simply just turned off as if the power switch had been flipped. I have the libvirtd service disabled and cannot start it without crashing.
I do think it is interesting to note that I can run libvirtd commands without crashing.

libvirtd (libvirt)  version 11.4.0

Jul 03 18:13:05 archlinux sudo[98117]:   arctic : TTY=pts/1 ; PWD=/home/arctic ; USER=root ; COMMAND=/usr/bin/systemctl start libvirtd
Jul 03 18:13:05 archlinux sudo[98117]: pam_unix(sudo:session): session opened for user root(uid=0) by arctic(uid=1000)
Jul 03 18:13:05 archlinux systemd[1]: Created slice Virtual Machine and Container Slice.
Jul 03 18:13:05 archlinux systemd[1]: Listening on libvirt legacy monolithic daemon socket.
Jul 03 18:13:05 archlinux systemd[1]: Listening on libvirt legacy monolithic daemon admin socket.
Jul 03 18:13:05 archlinux systemd[1]: Listening on libvirt legacy monolithic daemon read-only socket.
Jul 03 18:13:05 archlinux systemd[1]: Listening on libvirt locking daemon socket.
Jul 03 18:13:05 archlinux systemd[1]: Listening on libvirt logging daemon socket.
Jul 03 18:13:05 archlinux systemd[1]: Virtual Machine and Container Storage (Compatibility) was skipped because of an unmet condition check (ConditionPathExists=/var/lib/machines.raw).
Jul 03 18:13:05 archlinux systemd[1]: Starting Virtual Machine and Container Registration Service...
Jul 03 18:13:05 archlinux systemd[1]: Started Virtual Machine and Container Registration Service.
Jul 03 18:13:05 archlinux systemd[1]: Starting libvirt legacy monolithic daemon...
Jul 03 18:13:05 archlinux systemd[1]: Started libvirt legacy monolithic daemon.
Jul 03 18:13:05 archlinux sudo[98117]: pam_unix(sudo:session): session closed for user root
Jul 03 18:13:05 archlinux kernel: watchdog: watchdog0: watchdog did not stop!
Jul 03 18:13:05 archlinux kernel: watchdog: watchdog0: watchdog did not stop!
Jul 03 18:13:05 archlinux kernel: NET: Registered PF_VSOCK protocol family
Jul 03 18:13:05 archlinux kernel: PPP generic driver version 2.4.2
Jul 03 18:13:05 archlinux libvirtd[98124]: libvirt version: 11.4.0
Jul 03 18:13:05 archlinux libvirtd[98124]: hostname: archlinux
Jul 03 18:13:05 archlinux libvirtd[98124]: ignoring missing fifo '/dev/log'
Jul 03 18:13:05 archlinux libvirtd[98124]: ignoring missing fifo '/dev/stderr'
Jul 03 18:13:05 archlinux libvirtd[98124]: ignoring missing fifo '/dev/stdout'
Jul 03 18:13:06 archlinux kernel: efivarfs: resyncing variable state
Jul 03 18:13:06 archlinux bluetoothd[2631]: Controller resume with wake event 0x0
Jul 03 18:13:06 archlinux libvirtd[98124]: ignoring missing fifo '/dev/tty'
Jul 03 18:13:06 archlinux kernel: r8169 0000:26:00.0: invalid VPD tag 0x00 (size 0) at offset 0; assume missing optional EEPROM
Jul 03 18:13:52 archlinux kernel: watchdog: watchdog0: watchdog did not stop!
Jul 03 18:13:52 archlinux kernel: watchdog: watchdog0: watchdog did not stop!
Jul 03 18:13:52 archlinux libvirtd[98124]: ignoring missing fifo '/dev/log'
Jul 03 18:13:52 archlinux libvirtd[98124]: ignoring missing fifo '/dev/stderr'
Jul 03 18:13:52 archlinux libvirtd[98124]: ignoring missing fifo '/dev/stdout'
Jul 03 18:13:52 archlinux kernel: efivarfs: resyncing variable state
Jul 03 18:13:52 archlinux bluetoothd[2631]: Controller resume with wake event 0x0
Jul 03 18:13:52 archlinux libvirtd[98124]: ignoring missing fifo '/dev/tty'
Jul 03 18:14:17 archlinux python3[97367]: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed
Jul 03 18:14:35 archlinux python3[97367]: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed

Any help would be greatly appreciated!

Offline

#2 2025-07-04 06:09:27

Whoracle
Member
Registered: 2010-11-02
Posts: 212

Re: Starting libvirtd causes a complete system crash

Machine XML/QEMU command please?

For example I had something like that when I passed an USB controller to a VM that belonged to the CPU instead of the Chipset. Turns out the CPU doesn't that...

My thread from back in the day with no solution, but more explanation for comparison.

Last edited by Whoracle (2025-07-04 06:16:44)

Offline

#3 2025-07-06 15:31:40

Arctic01
Member
Registered: 2025-07-03
Posts: 2

Re: Starting libvirtd causes a complete system crash

No machine. I don't even have time to create one before the system goes down

Offline

Board footer

Powered by FluxBB