Am 30.08.2018 um 12:23 schrieb isdtor isdtor@gmail.com:
Does some one have problems related to KVM with kernel-2.6.32-754.3.5.el6.x86_64 ??
Yes, the exact same thing happened here, and I suspect it is related to older cpus that don't get any Spectre/Meltdown updates.
Thanks for the feedback. I' was assuming that some kind of Spectre/Meltdown fixes are causing this.
Doesn downgrading qemu as I proposed in the other mail fix it in your case?
I'm interested because in my case I'm having the issue on two older AMD CPUs, not Intel.
Simon, downgrading does not fix the problem in my case. I upgraded to the 3.5 kernel, disabled libvirtd and libvirtd-guests, and rebooted. Once the machine was up, I started the libvirtd service and the machine crashed immediately.
Old: qemu-img-0.12.1.2-2.506.el6_10.1, qemu-kvm-0.12.1.2-2.506.el6_10.1 (crash on 2.6.32-754.3.5) New: qemu-img-0.12.1.2-2.503.el6_9.6, qemu-kvm-0.12.1.2-2.503.el6_9.6 (crash on 2.6.32-754.3.5)
In Leon's and my case, the culprit is kernel 2.6.32-754.3.5. In CentOS bug 0015067, the bad kernel is 2.6.32-754.2.1, wich works fine here. The difference might be how different cpus are handled.
Follow up: The current kernel (kernel-2.6.32-754.6.3.el6.x86_64) seems to be usable again. No issues so far ...
-- LF