On Fri, Dec 15, 2017 at 01:59:06PM +0100, Landry Breuil wrote: > On Fri, Dec 15, 2017 at 06:21:08PM +1000, Jonathan Matthew wrote:
<snip> > > So, for me at least, adding 'kvm-intel.preemption_timer=0' to the linux > > kernel > > commandline (on the host) fixes this. This option disables kvm's use of the > > vmx preemption timer to schedule lapic counter events. I think there's some > > problem in how kvm calculates the tsc deadline, or the relationship between > > that and the time value it uses for lapic counter reads, but I'm not sure > > what > > exactly. > > > > I'm also running with this option now, will bang the vms with some heavy > workload and keep an eye on it. Thanks for the time you spent on this ! :) Been running with it since a week without crashes/hardlocks, and i'm also able to reboot VMs without issues. Sounds good!
