Comment 25 for bug 503138

Thanks Arie for providing your configuration fix to the issue for anyone else being affected - that will be really helpful.

In that sense it is much more like bug 1346917 which was about KSM.
Since the fix for that old bug they at least stopped being migrated around, but I can see how a lot of KSM based overcommit on remote nodes can make memory to be slow.

But IMHO that is just one of the potential prices to pay with KSM, not that much of a bug but a configuration which happens to overload what the system can deliver. It needs a lot very slow memory to trigger the hrtimer issue, if you think there really is an issue to fix (other than the configuration) then I'd suggest try with the latest stack in Disco (19.04) which is very up to date in regard to kernel&qemu - if it still happens there you might report that upstream to the kernel ML - maybe there is an idea how to improve MM to cause less issues, but I'd expect they say that is what the tunable is for.

But as said, if you report that to us as well - maybe once a patch exists to backport - I'd appreciate if that would be in a new bug.