Enabled the logging on both compute and baremetal. Nothing strange in logs:
on baremetal :
Wed Aug 17 11:51:01 EEST 2016: committed 62310764 free 58501808
Wed Aug 17 11:51:01 EEST 2016: 87025667 < 123574516 and free > 24714903,
stop ksm
on compute:
Wed Aug 17 08:52:52 UTC 2016: committed 24547132
It sounds weird, but attempt to disable KSM and see would it help or no ?
From: centos-virt-boun...@centos.org on behalf
of Laurentiu Soica
Sent: Wednesday, August 17, 2016 4:56 AM
To: Discussion about the virtualization on CentOS
Subject: Re: [CentOS-virt] Nes
Both baremetal and compute ? Are there any other metrics do you consider
useful to collect for troubleshooting purposes ?
În mie., 17 aug. 2016 la 13:04, Boris Derzhavets
a scris:
> It sounds weird, but attempt to disable KSM and see would it help or no ?
>
>
> --
> *F
For myself KSM is unpredictable feature. The problem is Compute, just this node
does "copy on write" , so only Compute.
My concern exactly is where would it lead to worse or better Guest behavior ?
I am not expecting complete fix. I would track via top/htop and dmesg via
Cron on 1-2 hr
perio
