Hi Tomasz,
It would also be interesting to see if the issue disappears when restarting the VM.
It did not help. I have tried that.
Before stopping virtual machines working in system shell was hard because even listing files took seconds. When I stopped virtual machines the situation improved but as soon as I tried to start them again, system has become unresponsive again. Then I rebooted.
this reminds me of a situation I sporadically encountered on my Gen12 Framework laptop. Once heavily stressing the system by a large compile in "high-performance" mode, some kind of overheat protection of the firmware kicks in and forcibly throttles all cores to 400 Mhz.
Interestingly, the forced throttling is retained long after all temperatures have cooled down to less than 50 degrees. Usually, the situation recovers after 1/4 hour. In one case, however, the situation wouldn't even recover after reboot, even on the day after. Only detaching and re-attaching the battery (can be done in the BIOS menu) fixed it. It goes without saying that I keep using the "balanced" mode since then.
The effects of the firmware can be nicely observed using Alex' MSR GUI tool. I leave it running at all times.
I also have a copy of /report/log from that time, but I don't see anything suspicious there. By the way it would be useful if there was some kind of timestamp with log (it doesn't have to be a real time). Trying to correlate information from log with the performed actions is hard if you do not have any information about "age" of each log.
Noted [1].
[1] https://github.com/genodelabs/genode/issues/5422
Cheers Norman