|
|
Just reproduced this issue by *rebooting* a running VM, and a sistem VM jumped to 100% CPU and unresponsive. |
|
|
Dmesg from a VM as it hit this bug. log2.png (85,648 bytes) log1.png (80,747 bytes) |
|
|
I believe I am seeing the same effect issue. I'm using Rocky but reporting here just because the situation seems very similar to this issue and it could be rare. The environment is a little complex. Nested virtualization is being used on a Mac. The Outer host is a VirtualBox VM with Rocky 8 installed. The Outer VM hosts inner VMs using KVM. The inner VMs are running Rocky 8 as well. The first two inner VMs work. When starting the third of fourth, all cpus allocated to inner VMs go to 100% and the inner VMs become almost unresponsive. One inner VM has been seen to produce the following message into /var/log/messages: chronyd[7233]: Forward time jump detected! Stopping one of the inner VMs returns the system to a relatively normal state. |
|
|
Are you both still seeing this issue? I'm encountering an issue which I believe is similar, although it may not necessarily be exactly the same. My issue is just an unexplained freeze of the VM. The qemu-kvm process at or near 100% of given CPU. But the VM itself (running top inside the VM) doesn't show a high load or a lot going on. Both nodes (and VMs) are running Almalinux 8. There's not really a rhyme or reason as to why or when this will happen. Nothing in any logs, that I can find, that indicate any problem. It's happened twice within a couple of weeks on one VM. Another VM has had this happen once in the past couple of weeks. A third AlmaLinux node with an AlmaLinux 8 VM has yet to experience this issue. The one that has had this happen twice is an older Intel E3-1270v2. The other one that's had this happen once is an Intel i9-11900K. The one that has yet to have this happen is an AMD Ryzen 9 3900X. When these freezes happen, my only recourse is to destroy the VM and start it back up. |
- Anonymous