Finally, the KVM hanging issue on E55xx CPUs is resolved with kernel.x86_64-3.10.0-1160.88.1.el7! On 11/16/22 02:50, Petko Alov wrote: >> >> On 2022-11-08 15:49, Orion Poplawski wrote: >> >> On 11/8/22 13:12, Simon Matter wrote: >> >> Is anyone else experiencing trouble with >> kernel-3.10.0-1160.80.1.el7.x86_64? >> >> I'm seeing a kernel panics in the kvm module on one of our VM hosts with >> >> it. >> >> I did notice a new libvirt update as well, but it seems to work fine with >> >> the >> older kernel (.76.1). >> >> Where did you get the .80.1 kernel from? I'm a bit confused because I can >> >> only see .76.1 on my systems. >> >> Simon >> >> I'm actually running Scientific Linux, which seems to be a little ahead here. >> Probably not related, but vmlinuz-4.18.0-372.32.1.el8_6.x86_64 (AlmaLinux 8.6) had a kernel panic >> on a Intel Xeon E5504 processor, but works fine on Xeon E56XX processors (5620 specifically in our >> tests). * Believe from kernel version, the original email is for Centos 7, possible the same >> change that went into the EL8 kernel went also to EL7 Triggered right after I used virsh start to >> start the vm. (Caused Black Screen, and reboot. Found this in the crashed kernel logs on >> /var/crash) Works fine on vmlinuz-4.18.0-372.26.1.el8_6.x86_64 and >> vmlinuz-4.18.0-372.16.1.el8_6.x86_64 > > In fact, related - on our systems attempt to start qemu-kvm VM under > kernel-3.10.0-1160.80.1.el7.x86_64 freezes any of 5 workstations with dual E5507 (all worked OK > under kernel-3.10.0-1160.76.1.el7.x86_64 and any previous version). The workstations with E5-2609, > E5-2650 or E5-2630 are not affected - all of them run qemu-kvm VM under > kernel-3.10.0-1160.80.1.el7.x86_64 without problems. > > Any ideas? > > Regards, > > Petko > > -- Petko Alov Department of QSAR & Molecular Modelling Institute of Biophysics and Biomedical Engineering, BAS 21 G. Bontchev Str 1113 Sofia, BULGARIA phone: +359 2 9793647 mobile: +359 87 7294336 e-mail: petko.alov at biophys.bas.bg