PC stops working once you launch a VM through virt-manager.
PC stops working once you launch a VM through virt-manager.
Yup, will keep the new mobo then. MonkaS! If it were to happen you'd be happier to keep it as 'defect' as it was compared to short circuiting it xD Thanks for the advices again! However, unfortunately the problem still persists even after doing so like you told me. Sometimes it works for hours and shuts down randomly, sometimes it immediately shuts down. I noticed one thing: When I "systemctl status libvirtd" it says "inactive (dead)" then I "systemctl start libvirtd" it and open virtual-machine-manager and do again "systemctl status libvirtd" it again goes "inactive (dead)" So what I did is, I "systemctl start libvirtd" and my virtual-machine-manager closes itself and the VM QEMU-Agent as well, but VM is running in background but I can't do much since I have no windows to click/use it. I go to "systemctl status libvirtd" and it says "active (running)" Here's the logs: ● libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled ; preset: disabled ) Drop-In: /usr/lib/systemd/system/service.d └─10-timeout-abort.conf Active: active (running) since Tue 2024-04-02 23:02:16 CEST; 1s ago TriggeredBy: ○ libvirtd-tls.socket ● libvirtd-admin.socket ● libvirtd-ro.socket ● libvirtd.socket ○ libvirtd-tcp.socket Docs: man:libvirtd(8) https://libvirt.org Main PID: 9000 (libvirtd) Tasks: 23 (limit: 32768) Memory: 101.0M CPU: 330ms CGroup: /system.slice/libvirtd.service ├─ 7563 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper ├─ 7564 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/libexec/libvirt_leaseshelper └─ 9000 /usr/sbin/libvirtd --timeout 120 Apr 02 23:02:16 systemd[1]: Starting libvirtd.service - Virtualization daemon... Apr 02 23:02:16 systemd[1]: Started libvirtd.service - Virtualization daemon. Apr 02 23:02:17 dnsmasq[7563]: read /etc/hosts - 7 names Apr 02 23:02:17 dnsmasq[7563]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 names Apr 02 23:02:17 dnsmasq-dhcp[7563]: read /var/lib/libvirt/dnsmasq/default.hostsfile Apr 02 23:02:17 libvirtd[9000]: libvirt version: 9.7.0, package: 3.fc39 (Fedora Project, 2024-03-12-17:39:29, ) Apr 02 23:02:17 libvirtd[9000]: hostname: user Apr 02 23:02:17 libvirtd[9000]: Failed to open file '/sys/fs/cgroup/machine.slice/machine-qemu\x2d1\x2dwin10.scope/libvirt/tasks': No such file or directory Apr 02 23:02:17 libvirtd[9000]: Unable to read from '/sys/fs/cgroup/machine.slice/machine-qemu\x2d1\x2dwin10.scope/libvirt/tasks': No such file or directory ~ I'm not sure if this is supposed to be this way?
These problems seem specific to your setup. I started the VM and verified if the same errors occur, but only storage issues appear—likely due to missing NFS drive. The application still functions, so it might be related to system tasks. libvirtd appears partially broken; it seems to be running but failing unexpectedly. Memory usage isn’t clear—consider a memory test during boot selection. Some distros include this feature. If you need, I can guide you through reinstalling libvirtd and testing again. You could also try another distribution or run a live test. Other programs might help isolate the cause. Good luck!