PC stops working once you launch a VM through virt-manager.
PC stops working once you launch a VM through virt-manager.
I think your GPU stopped working suddenly and your system thought you were dead, so it turned off. Often when you have access to system logs, they explain what happened with PCI or GPU. A funny case I had was a sudden black screen but audio kept playing until it was off. It turned out the GPU was overheating and needed cleaning with a toothbrush. KDE has a system logs package that makes it easy to check. You can run `systemctl status qemu` to see if anything is running.
Well okay! I hope that's not the issue here lol! Thank you for sharing what happened. It seems like there might be a similar problem, but it sounds pretty serious. I'm worried it could be because of those logs showing "journalctl b -1 -p err" and other errors like hub not having ports, systemd failures, missing key files, and issues with codecs and UUIDs. It's definitely something worth checking closely.
No issue at all! Apologies too, I was away for a while. Thanks again for your support:
"Libvirtd.service is loaded but inactive. It’s not running (dead). Triggered by several sockets. Documentation available online."
Also, note I haven’t used virt-manager or started any virtual machines since the reboot, which might explain the status.
I'm trying to figure it out where the issue lies. As for dead status its simply not booted. At least that's what i think otherwise it would report errors? Can you try start the service? Here's quick copy and paste. sudo systemctl start libvirtd And see if it happens same issue. And don't worry your hardware won't die quickly by some software because smart IT's have made prevention of damage. Because my pc has crashed multiple ways and different issues probably record of crashes is 34 times and fixed it.
Hello! Initially it functioned properly until it stopped. I checked systemctl status of libvirtd – it was off. I turned it on and ran the VM; everything worked for about an hour or two. Then I went AFK and wasn't sure if my PC had hibernated or slept. The case lights up, but I just need to press a button to restart from where I left off. Suddenly, I heard a reboot sound in the background.
First, I tried the steps that made it work earlier – VM again, no delay, and it rebooted after about a minute. I looked at journalctl from the first reboot and saw errors related to IRQs and kernel logs. The system reported issues with LNKA, LNKB, LNKC, and others. There were also warnings about remapping and font settings failing.
After that, I restarted the VM quickly and it worked again. The logs showed errors like "AMD-Vi: Int err upt remapping enabled" and "fbcon: Def err ing console take-over." Eventually, the system started normally after a reboot.
If you need further help, just let me know!
Hi! Before I do all of that, is the motherboard part really necessary? It's brand new Motherboard. I can replace it if needed, they've offered me already because of a really little scratch on behind (I tried to get few $$ back) but instead they offered me to replace it for brand new one, should I take on the offer if the issue still persists? Thank you a lot! Omw to tootbrush the heck out of the GPU
I've considered both options, but they seemed dirty and outdated with dust buildup. Unless it's already spotless, I wouldn't bother. It's just a suggestion like cleaning the motherboard and PCI slot before use—just to be safe. Hopefully, the problem wasn't from other parts. For new boards, it's your decision. I tend to keep older gear because I've learned to trust and maintain it.
This experience taught me a lesson when I cleaned the GPU and motherboard casually. It failed to boot, just like it should. That made me panic and test it without the GPU, which confirmed the issue. I cleaned thoroughly, placed the PC upside down, blew air around, and brushed gently until confident. No need to disassemble everything—result was satisfactory. It took time, but both the GPU and motherboard worked again.
Afterward, I realized something could have been damaged, but it wasn't. Lucky I didn’t short anything. Thanks to hardware makers for thinking ahead and preventing such issues.