PC shuts down after I open VM in virt-manager

[Aion76263]

Hi everybody, after a succesful upgrade I couldn't open virt-manager and play emulator games on it.
I have BlueStacks in Virt-manager (win10) so that I can play somewhat my daily like I used to before.
Before I upgraded my PC I had:
MSI H510M-A Pro Mainboard
16GB DDR4 RAM
Intel Core i5-10400F
And it was all fine, I could play all day all night on virt-manager without any issues, but after the upgrade to:
ryzen 5 7600x
32GB DDR5 RAM
B650 Tomahawk Wifi
I keep running into the same problem, my PC keeps shutting off whenever I open/play on virt-manager for 2-3 minutes after that my PC screen goes completely blank and it stays like that for 1-2 minutes and then it reboots.
I couldn't find AMD-V but I found SVM instead and I enabled it, but still, no success however.

I currently am running:

Linux 6.7.6-201.fsync.fc39.x86_64 x86_64

Idk what the problem could be here, any suggestions?

 

[tkitch]

When you upgraded did you move your SSD Over with the same install?
Or did you wipe and reinstall windows from scratch?

[Aion76263]

49 minutes ago, tkitch said:

When you upgraded did you move your SSD Over with the same install?
Or did you wipe and reinstall windows from scratch?

I moved my SSD, and I don't run windows, I run fedora39. I run windows in virti-manager so I can play Bluestacks from there

[OddOod]

Welcome to the forums!
 

What kind of crash are you having? Just straight to black or do you get a kernel panic?
I'd maybe try a fresh install
Also, make sure your RAM is stable (not sure of how on Linux)
 

[Aion76263]

2 minutes ago, OddOod said:

Welcome to the forums!
 

What kind of crash are you having? Just straight to black or do you get a kernel panic?
I'd maybe try a fresh install
Also, make sure your RAM is stable (not sure of how on Linux)
 

Could you define me "kernel panic" please?
Without knowing what kernel panic means, my screen goes completely black, PC is still running (I can see the fans spinning) and after 1-2 minutes of black screen it reboots
EDIT: Ram is pretty fine. memtest86 showed 0 problems

[HanZie82]

Replace the PSU.

As you didnt mention the PSU, i'm guessing its not capable enough for the upgraded system.
Im guessing new system need a bit more power. Most other issues would've resulted in a BSOD.

The way it shuts down and waits then powers back on again really makes me think its the over power protection on the PSU.

[OddOod]

24 minutes ago, Aion76263 said:

Could you define me "kernel panic" please?

KP is basically a linux blue screen
Some info about it here: https://www.redhat.com/sysadmin/linux-kernel-panic

 

Also, your specs seem incomplete. Neither of those CPUs have iGPUs, what GPU are you using? Did you change the GPU? And what PSU do you have?
And what do your logs show? And how are your temps?

 

10 minutes ago, HanZie82 said:

Replace the PSU.

Normally I'd say yes, but in this case it's not full off, it's losing video output and then crashing.

[Aion76263]

11 minutes ago, HanZie82 said:

Replace the PSU.

As you didnt mention the PSU, i'm guessing its not capable enough for the upgraded system.
Im guessing new system need a bit more power. Most other issues would've resulted in a BSOD.

The way it shuts down and waits then powers back on again really makes me think its the over power protection on the PSU.

Hi, I have GPU RX 6600, I went on buildapc the website and it showed max outwattage is around ~350W
I tried it with 450W +80 Gold Be quiet (maybe around 10 years old) and the problem still persistet
Then I swapped to 600W ACP-600MPC (from my previous pre-built 2 years old PC) and the problem is still here.
You think by any chance it could be because of the bad PSU?

I've never had any turning offs/shutdowns with the ACP-600MPC on my previous PC with the previous build.
This is first time I experience it

[HanZie82]

2 minutes ago, OddOod said:

Normally I'd say yes, but in this case it's not full off, it's losing video output and then crashing.

 

Just now, Aion76263 said:

Hi, I have GPU RX 6600, I went on buildapc the website and it showed max outwattage is around ~350W
I tried it with 450W +80 Gold Be quiet (maybe around 10 years old) and the problem still persistet
Then I swapped to 600W ACP-600MPC (from my previous pre-built 2 years old PC) and the problem is still here.
You think by any chance it could be because of the bad PSU?

I've never had any turning offs/shutdowns with the ACP-600MPC on my previous PC with the previous build.
This is first time I experience it

Yeah with this info im not so sure about my diagnosis anymore.
If it was PSU it would completely power down instantly and then power back on after a little while.
You say the fans keep running, this makes me think its not the PSU. (But does help to tell which you have in spec lists).

Sorry i cant be of more help, im not that versed in Linux, others are tho.

But it kinda sounds like it encounters an error, which disable video output, its unable to recover so it shuts down/restarts?!

[Aion76263]

3 minutes ago, OddOod said:

KP is basically a linux blue screen
Some info about it here: https://www.redhat.com/sysadmin/linux-kernel-panic

 

Also, your specs seem incomplete. Neither of those CPUs have iGPUs, what GPU are you using? Did you change the GPU? And what PSU do you have?
And what do your logs show? And how are your temps?

 

Normally I'd say yes, but in this case it's not full off, it's losing video output and then crashing.

Hi,
The ryzen 5 7600x does have iGPU but I have disabled the iGPU from it
The GPU I currently have is RX 6600 (it's the same from previous build, I haven't changed it)
And the Current PSU IS ACP-600MPC (it's also the same from previous build and I haven't changed it) However I have tried to swap the PSU for be quiet +80 Gold 450W and i still had same problem
The temperatures seem fine, mostly idle sitting around 40-55 Celsius and when working it's hitting the 80ish
And no, I have no kernel panic from what I understand

[BoomerDutch]

1 hour ago, Aion76263 said:

Hi,
The ryzen 5 7600x does have iGPU but I have disabled the iGPU from it
The GPU I currently have is RX 6600 (it's the same from previous build, I haven't changed it)
And the Current PSU IS ACP-600MPC (it's also the same from previous build and I haven't changed it) However I have tried to swap the PSU for be quiet +80 Gold 450W and i still had same problem
The temperatures seem fine, mostly idle sitting around 40-55 Celsius and when working it's hitting the 80ish
And no, I have no kernel panic from what I understand

I believe your GPU simply crashed and little while your system realises you have no screen so it shuts off.

 

Usually if you have acces system logs

They tell you if something happend with PCI or gpu or anything.

 

Quite funny story i have same issue sudden black screen but audio still playing till its off.

 

And realisation my GPU is overheating kekw and had to clean with toothbrush

 

Kde has system logs package for easy use.

 

You can try systemctl status qemu

To see if anything is going on.

[Aion76263]

11 minutes ago, BoomerDutch said:

I believe your GPU simply crashed and little while your system realises you have no screen so it shuts off.

 

Usually if you have acces system logs

They tell you if something happend with PCI or gpu or anything.

 

Quite funny story i have same issue sudden black screen but audio still playing till its off.

 

And realisation my GPU is overheating kekw and had to clean with toothbrush

 

Kde has system logs package for easy use.

 

You can try systemctl status qemu

To see if anything is going on.

Oh well! Hopefully that isn't the problem here lol! Sorry to hear about what you had to go through
But am afraid it sounds very higly possible I have same problem

these are the logs with "journalctl b -1 -p err"
Mar 28 13:49:06  kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mar 28 13:49:06  systemd-vconsole-setup[349]: /usr/bin/setfont failed with exit status 71.
Mar 28 13:49:06  systemd-vconsole-setup[607]: /usr/bin/setfont failed with exit status 71.
Mar 28 13:49:07  systemd-cryptsetup[663]: Failed to activate, key file '/crypto_keyfile.bin' missing.
Mar 28 13:49:31  kernel: snd_hda_intel 0000:12:00.6: no codecs found!
Mar 28 13:49:32  bluetoothd[1916]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Mar 28 13:49:32  bluetoothd[1916]: Failed to clear UUIDs: Failed (0x03)
Mar 28 13:49:32  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:32  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:32  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:32  bluetoothd[1916]: Failed to set mode: Failed (0x03)
Mar 28 13:49:32  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:32  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:32  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:41  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:41  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:41  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:41  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:43  sddm-helper[3629]: gkr-pam: unable to locate daemon control file
Mar 28 13:49:43  bluetoothd[1916]: Failed to remove UUID: Failed (0x03)
Mar 28 13:49:43  bluetoothd[1916]: Failed to remove UUID: Failed (0x03)
Mar 28 13:49:43  bluetoothd[1916]: Failed to remove UUID: Failed (0x03)
Mar 28 13:49:43  bluetoothd[1916]: Failed to remove UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:45  bluetoothd[1916]: Failed to add UUID: Failed (0x03)
Mar 28 13:49:47  bluetoothd[1916]: Failed to set mode: Failed (0x03)
Mar 28 13:49:56  kwin_wayland[3782]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 28 13:49:56  kwin_wayland[3782]: kwin_scene_opengl: Can't enable invalid framebuffer object!
 

>> Systemctl status qemu
-> Unit qemu.service could not be found.
I tried qemu.service, same results. I tried adding "sudo" in front, same result.

I tried "systemctl enable qemu" with sudo and with .service I get this error:
-> Failed to enable unit: Unit file qemu.service does not exist

[BoomerDutch]

46 minutes ago, Aion76263 said:

Oh well! Hopefully that isn't the problem here lol! Sorry to hear about what you had to go through
But am afraid it sounds very higly possible I have same problem

 

>> Systemctl status qemu
-> Unit qemu.service could not be found.
I tried qemu.service, same results. I tried adding "sudo" in front, same result.

I tried "systemctl enable qemu" with sudo and with .service I get this error:
-> Failed to enable unit: Unit file qemu.service does not exist

I don't see anything on journal that would tell me.

 

I must apologise its not called qemu it's libvirtd, had to boot my pc for sec to check.

 

Quite neat it told me what error it has.

[Aion76263]

2 hours ago, BoomerDutch said:

I don't see anything on journal that would tell me.

 

I must apologise its not called qemu it's libvirtd, had to boot my pc for sec to check.

 

Quite neat it told me what error it has.

No problem! I apologise as well, was MIA for some long ass time.
Thanks still for being here helping me out:D

"○ 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: inactive (dead)
TriggeredBy: ○ libvirtd-admin.socket
            ○ libvirtd-tcp.socket
            ○ libvirtd.socket
            ○ libvirtd-ro.socket
            ○ libvirtd-tls.socket
      Docs: man:libvirtd(8)
https://libvirt.org

"

Keep in mind- I haven't started virt-manager / opened any VM since the reboot so maybe that's why it is 'inactive'(?)
 

[BoomerDutch]

36 minutes ago, Aion76263 said:

No problem! I apologise as well, was MIA for some long ass time.
Thanks still for being here helping me out:D

"○ 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: inactive (dead)
TriggeredBy: ○ libvirtd-admin.socket
            ○ libvirtd-tcp.socket
            ○ libvirtd.socket
            ○ libvirtd-ro.socket
            ○ libvirtd-tls.socket
      Docs: man:libvirtd(8)
https://libvirt.org

"

Keep in mind- I haven't started virt-manager / opened any VM since the reboot so maybe that's why it is 'inactive'(?)
 

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.

[Aion76263]

30 minutes ago, BoomerDutch said:

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.

Hey! It seems to be working fine so far, no crashes whatsoever within the first 10 minutes.
Will try it out tomorrow for more extended period and play on it and see if it crashes or not and come back here agian.

Thank you a lot for so far!

[Aion76263]

On 3/28/2024 at 10:08 PM, BoomerDutch said:

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.

Hi!

Uhm, it worked until it didn't work.

I systemctl status libvirtd -> it was inactive -> I activated it -> I ran the VM -> everything was fine for 1h-2h

I went AFK and I'm not entirely sure but maybe my PC hibernated/sleep* (*PC Case is lighting, I just need to press a button and the PC will start again from where I left off) and I suddenly hear the reboot in the background

First thing I did was try the first steps that made it work earlier -> ... -> try VM again -> not 1 minute in the VM and it reboots again

Journalctl from 1st reboot (VM was working 1h-2h)
-> "journalctl -b -1 | grep 'err'"


Mar 29 23:36:20  kernel: ACPI: Using IOAPIC for interrupt routing
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 0
Mar 29 23:36:20  kernel: AMD-Vi: Interrupt remapping enabled
Mar 29 23:36:20  kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mar 29 23:36:20  kernel: fbcon: Deferring console take-over
Mar 29 23:36:20  kernel: sd 2:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Mar 29 23:36:20  systemd-vconsole-setup[348]: Setting fonts failed with a "system error", ignoring.
Mar 29 23:36:20  systemd-vconsole-setup[605]: Setting fonts failed with a "system error", ignoring.
Mar 29 23:36:24  kernel: fbcon: Deferring console take-over
Mar 29 23:36:40  systemd[1]: Started atd.service - Deferred execution scheduler.
Mar 29 23:36:44  xdg-desktop-por[3214]: The preferred method to match portal implementations to desktop environments is to use the portals.conf(5) configuration file
Mar 29 23:36:44  sddm-helper-start-wayland[2911]: "QSGContext::initialize: depth buffer support missing, expect rendering errors\nQSGContext::initialize: stencil buffer support missing, expect rendering errors\n"
Mar 29 23:39:42  plasmashell[4074]: kpipewire_logging: PipeWire remote error:  -2 target not found
Mar 29 23:39:42  plasmashell[4074]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 4 op:7
Mar 29 23:41:07  plasmashell[4074]: error creating screencast "Could not find window id 0"
Mar 29 23:41:09  plasmashell[4074]: kpipewire_logging: PipeWire remote error:  -2 target not found
Mar 29 23:41:09  plasmashell[4074]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 5 op:7

-> "journalctl -b -1 | grep 'libvirtd'"

Mar 29 23:38:03  polkitd[1720]: Operator of unix-session:2 successfully authenticated as unix-user:name to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.121 [systemctl start libvirtd] (ow
ned by unix-user:name)
Mar 29 23:38:03  systemd[1]: Listening on libvirtd.socket - Libvirt local socket.
Mar 29 23:38:03  systemd[1]: Listening on libvirtd-admin.socket - Libvirt admin socket.
Mar 29 23:38:03  systemd[1]: Listening on libvirtd-ro.socket - Libvirt local read-only socket.
Mar 29 23:38:03  systemd[1]: Starting libvirtd.service - Virtualization daemon...
Mar 29 23:38:03  systemd[1]: Started libvirtd.service - Virtualization daemon.
Mar 29 23:38:03  audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 29 23:38:06  systemd[1]: Stopping libvirtd.service - Virtualization daemon...
Mar 29 23:38:06  systemd[1]: libvirtd.service: Deactivated successfully.
Mar 29 23:38:06  systemd[1]: libvirtd.service: Unit process 6329 (dnsmasq) remains running after unit stopped.
Mar 29 23:38:06  systemd[1]: libvirtd.service: Unit process 6330 (dnsmasq) remains running after unit stopped.
Mar 29 23:38:06  systemd[1]: Stopped libvirtd.service - Virtualization daemon.
Mar 29 23:38:06  audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'



Journalctl from 2nd reboot (VM was working 1min max)
-> "journalctl -b -0 | grep 'err'"


Mar 29 23:44:01  kernel: ACPI: Using IOAPIC for interrupt routing
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 0
Mar 29 23:44:01  kernel: AMD-Vi: Interrupt remapping enabled
Mar 29 23:44:01  kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mar 29 23:44:01  kernel: fbcon: Deferring console take-over
Mar 29 23:44:01  kernel: sd 2:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Mar 29 23:44:01  systemd-vconsole-setup[352]: Setting fonts failed with a "system error", ignoring.
Mar 29 23:44:01  systemd-vconsole-setup[609]: Setting fonts failed with a "system error", ignoring.
Mar 29 23:44:05  kernel: fbcon: Deferring console take-over
Mar 29 23:44:22  systemd[1]: Started atd.service - Deferred execution scheduler.
Mar 29 23:44:25  xdg-desktop-por[3244]: The preferred method to match portal implementations to desktop environments is to use the portals.conf(5) configuration file
Mar 29 23:44:26  sddm-helper-start-wayland[2933]: "QSGContext::initialize: depth buffer support missing, expect rendering errors\nQSGContext::initialize: stencil buffer support missing, expect rendering errors\n"
Mar 29 23:44:37  plasmashell[3880]: error creating screencast "Could not find window id 0"
Mar 29 23:44:42  plasmashell[3880]: kpipewire_logging: PipeWire remote error:  -2 target not found
Mar 29 23:44:42  plasmashell[3880]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 3 op:7


-> "journalctl -b -0 | grep 'libvirtd'"
-> No output


I hope this helps? If anything else is needed, please let me know!

[BoomerDutch]

14 hours ago, Aion76263 said:

Hi!

Uhm, it worked until it didn't work.

I systemctl status libvirtd -> it was inactive -> I activated it -> I ran the VM -> everything was fine for 1h-2h

I went AFK and I'm not entirely sure but maybe my PC hibernated/sleep* (*PC Case is lighting, I just need to press a button and the PC will start again from where I left off) and I suddenly hear the reboot in the background

First thing I did was try the first steps that made it work earlier -> ... -> try VM again -> not 1 minute in the VM and it reboots again

Journalctl from 1st reboot (VM was working 1h-2h)
-> "journalctl -b -1 | grep 'err'"


Mar 29 23:36:20  kernel: ACPI: Using IOAPIC for interrupt routing
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 0
Mar 29 23:36:20  kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 0
Mar 29 23:36:20  kernel: AMD-Vi: Interrupt remapping enabled
Mar 29 23:36:20  kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mar 29 23:36:20  kernel: fbcon: Deferring console take-over
Mar 29 23:36:20  kernel: sd 2:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Mar 29 23:36:20  systemd-vconsole-setup[348]: Setting fonts failed with a "system error", ignoring.
Mar 29 23:36:20  systemd-vconsole-setup[605]: Setting fonts failed with a "system error", ignoring.
Mar 29 23:36:24  kernel: fbcon: Deferring console take-over
Mar 29 23:36:40  systemd[1]: Started atd.service - Deferred execution scheduler.
Mar 29 23:36:44  xdg-desktop-por[3214]: The preferred method to match portal implementations to desktop environments is to use the portals.conf(5) configuration file
Mar 29 23:36:44  sddm-helper-start-wayland[2911]: "QSGContext::initialize: depth buffer support missing, expect rendering errors\nQSGContext::initialize: stencil buffer support missing, expect rendering errors\n"
Mar 29 23:39:42  plasmashell[4074]: kpipewire_logging: PipeWire remote error:  -2 target not found
Mar 29 23:39:42  plasmashell[4074]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 4 op:7
Mar 29 23:41:07  plasmashell[4074]: error creating screencast "Could not find window id 0"
Mar 29 23:41:09  plasmashell[4074]: kpipewire_logging: PipeWire remote error:  -2 target not found
Mar 29 23:41:09  plasmashell[4074]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 5 op:7

-> "journalctl -b -1 | grep 'libvirtd'"

Mar 29 23:38:03  polkitd[1720]: Operator of unix-session:2 successfully authenticated as unix-user:name to gain TEMPORARY authorization for action org.freedesktop.systemd1.manage-units for system-bus-name::1.121 [systemctl start libvirtd] (ow
ned by unix-user:name)
Mar 29 23:38:03  systemd[1]: Listening on libvirtd.socket - Libvirt local socket.
Mar 29 23:38:03  systemd[1]: Listening on libvirtd-admin.socket - Libvirt admin socket.
Mar 29 23:38:03  systemd[1]: Listening on libvirtd-ro.socket - Libvirt local read-only socket.
Mar 29 23:38:03  systemd[1]: Starting libvirtd.service - Virtualization daemon...
Mar 29 23:38:03  systemd[1]: Started libvirtd.service - Virtualization daemon.
Mar 29 23:38:03  audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 29 23:38:06  systemd[1]: Stopping libvirtd.service - Virtualization daemon...
Mar 29 23:38:06  systemd[1]: libvirtd.service: Deactivated successfully.
Mar 29 23:38:06  systemd[1]: libvirtd.service: Unit process 6329 (dnsmasq) remains running after unit stopped.
Mar 29 23:38:06  systemd[1]: libvirtd.service: Unit process 6330 (dnsmasq) remains running after unit stopped.
Mar 29 23:38:06  systemd[1]: Stopped libvirtd.service - Virtualization daemon.
Mar 29 23:38:06  audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'



Journalctl from 2nd reboot (VM was working 1min max)
-> "journalctl -b -0 | grep 'err'"


Mar 29 23:44:01  kernel: ACPI: Using IOAPIC for interrupt routing
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKA configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKB configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKC configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKD configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKE configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKF configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKG configured for IRQ 0
Mar 29 23:44:01  kernel: ACPI: PCI: Interrupt link LNKH configured for IRQ 0
Mar 29 23:44:01  kernel: AMD-Vi: Interrupt remapping enabled
Mar 29 23:44:01  kernel: hub 8-0:1.0: config failed, hub doesn't have any ports! (err -19)
Mar 29 23:44:01  kernel: fbcon: Deferring console take-over
Mar 29 23:44:01  kernel: sd 2:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Mar 29 23:44:01  systemd-vconsole-setup[352]: Setting fonts failed with a "system error", ignoring.
Mar 29 23:44:01  systemd-vconsole-setup[609]: Setting fonts failed with a "system error", ignoring.
Mar 29 23:44:05  kernel: fbcon: Deferring console take-over
Mar 29 23:44:22  systemd[1]: Started atd.service - Deferred execution scheduler.
Mar 29 23:44:25  xdg-desktop-por[3244]: The preferred method to match portal implementations to desktop environments is to use the portals.conf(5) configuration file
Mar 29 23:44:26  sddm-helper-start-wayland[2933]: "QSGContext::initialize: depth buffer support missing, expect rendering errors\nQSGContext::initialize: stencil buffer support missing, expect rendering errors\n"
Mar 29 23:44:37  plasmashell[3880]: error creating screencast "Could not find window id 0"
Mar 29 23:44:42  plasmashell[3880]: kpipewire_logging: PipeWire remote error:  -2 target not found
Mar 29 23:44:42  plasmashell[3880]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 3 op:7


-> "journalctl -b -0 | grep 'libvirtd'"
-> No output


I hope this helps? If anything else is needed, please let me know!

Lets try cleaning with toothbrush

Just take out gpu and try holding fans and try brush crap out and hold upside down so it falls out instead inside.

 

No need for any chemicals just dry toothbrush would work.

 

Don't brush too hard just brush like you're uncovering dinosaur bones it will work fine.

 

Once you done cleaning gpu i would suggest to clean motherboard too.

 

Once that's done lets hope it solves the problem. 

 

Because software doesn't know what's going on apparently.

[Aion76263]

42 minutes ago, BoomerDutch said:

Lets try cleaning with toothbrush

Just take out gpu and try holding fans and try brush crap out and hold upside down so it falls out instead inside.

 

No need for any chemicals just dry toothbrush would work.

 

Don't brush too hard just brush like you're uncovering dinosaur bones it will work fine.

 

Once you done cleaning gpu i would suggest to clean motherboard too.

 

Once that's done lets hope it solves the problem. 

 

Because software doesn't know what's going on apparently.

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

[BoomerDutch]

31 minutes ago, Aion76263 said:

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

Ah I've thought both was dirty and old and gathered dust so no if its already clean.

 

it's just a advice like "while you're doing it might as well clean motherboard too like pci slot and such then you're sure" but if you deem thats clean and no problems.

 

Just praying that was the issue and not other hardware.

 

About new motherboard its your choice.

I usually keep old hardware because I've grown to trust and care to my hardware.

Since i know how it works and what it's capable of.

 

Little story here

When i cleaned the gpu and motherboard in lazy way.

 

It didn't boot acted like it was broken.

So i panicked and took it out tested without gpu and same issue.

 

So i cleaned thoroughly and calm and put pc upside down and other side and other side and blew air to it and brushed till i was sure.

 

Didn't have to take everything apart tho so I'm happy with result.

 

It took while tho but i got it both working gpu and motherboard.

 

After realisation i could've shorted something but it didn't so i was lucky.

 

Thank you hardware manufacturers for smart thinking for damage preventions measures.

[Aion76263]

On 3/30/2024 at 2:52 PM, BoomerDutch said:

Ah I've thought both was dirty and old and gathered dust so no if its already clean.

 

it's just a advice like "while you're doing it might as well clean motherboard too like pci slot and such then you're sure" but if you deem thats clean and no problems.

 

Just praying that was the issue and not other hardware.

 

About new motherboard its your choice.

I usually keep old hardware because I've grown to trust and care to my hardware.

Since i know how it works and what it's capable of.

 

Little story here

When i cleaned the gpu and motherboard in lazy way.

 

It didn't boot acted like it was broken.

So i panicked and took it out tested without gpu and same issue.

 

So i cleaned thoroughly and calm and put pc upside down and other side and other side and blew air to it and brushed till i was sure.

 

Didn't have to take everything apart tho so I'm happy with result.

 

It took while tho but i got it both working gpu and motherboard.

 

After realisation i could've shorted something but it didn't so i was lucky.

 

Thank you hardware manufacturers for smart thinking for damage preventions measures.

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?

 

[BoomerDutch]

4 hours ago, Aion76263 said:

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)"
 

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?

 

Okay those issues is unique, I've went ahead and booted vm and checked if i have same errors and only errors I'd have is simply storage missing because I haven't connected nfs drive. But runs regardless.

 

So it's missing system tasks?

Either libvirtd is so broken and somehow half booted service and yet fails mysteriously.

 

It does run so is it memory?

 

Can you do memory test?

Memory test is usually included in boot selection some distros have that.

 

Otherwise use installer iso and select memory test instead if they included it.

 

I'm literally scratching my head around this issue.

 

Because looks like google is so useless for this issue.

 

Other stuff you can try meanwhile

 

1. Can you reinstall libvirtd and try again?
2. try live iso test if issue persists
3. Attempt other distro and live test it.
4. Try other programs or something else and see if there is another problem if so then it's possible hardware issue.

Good luck!