May 26, 2021 · To limit ksmd impact, you can increase KSM_SLEEP_MSEC or, probably better, limit the amount of pages scanned per iteration by reducing KSM_NPAGES_MAX. So a quick fix would be to set KSM_NPAGES_MAX=300 Moreover, your KSM_THRES_COEF is way too high - you are scanning even with ample free RAM. Consider reverting it to 20 EDIT: if you want to …

May 3, 2017 · It turns out that Linux's KSM implementation was originally intended for use with VMs, but as it can save memory on non-virtual systems, is deployed by default on CentOS 6 and later. This server's memory usage has been creeping up and that apparently triggered KSMD to start scanning. Somewhere along the line the documentation for CentOS 6 didn't get updated …

Your shared memory is working properly, no doubt about it. Only thing is that as David mentions KSMD won't do anything unless it's specific requirement is met. As far as I can see, there is no problem really.

Jul 6, 2012 · Yes, it could. What this means is fairly explicit: the kernel couldn't schedule the task for 120 seconds. This indicates resource starvation, often around disk access. irqbalance might help, but that doesn't sound obvious. Can you provide us with the surrounding of this message in dmesg, in particular the stack trace that follows it? Moreover, this is not a false positive. This …

Apr 20, 2011 · The usual explanation for high load average with little cpu use under linux is too much IO (or more properly uninterruptable sleep). I have a service running on a cluster of 2-core VMs that exhibit

Mar 6, 2018 · I started with just giving every VM the maximum memory it might ever need, but that just used all the server RAM and most of it's SWAP and on top of it had ksmd running like crazy even though all VMs together aren't using even 30% of the server RAM. I than tried naively setting up currentMemory to be about 1/4 of the maximum memory for all VMs.

Mar 23, 2021 · After host's restart, I'm not able to start virtual machine: user@server-1:~$ virsh start docker-1 error: Failed to start domain docker-1 error: internal error: process exited while connecting to m...

85 root 25 5 0 0 0 S 17 0.0 28:57.08 ksmd

Something like strace output is the ultimate way to track down what's actually going on inside of this, but let's stick with something simpler for now. Log on another time in a separate terminal and share with us the output of ps xfawww while the other terminal appears "stuck"; this will show us what command (s) are being run that are taking so long to complete. Alternatively (or …

Nov 16, 2018 · There's a bunch of things you need to do here. First, the OOM killer was triggered by apache2 asking for more memory than was available, not by mysqld. But because the mysqld process was using the most memory at the time, it was the process that got killed. Consider setting the sysctl vm.oom_kill_allocating_task, which will cause the process that asked for the …