[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] arm: xl vcpu-pin leads to oom-killer slashing processes

On 05.12.18 14:15, Julien Grall wrote:
Yes, it thinks so. But it is not linked to domain .

What do you mean?
It should be read as "But it is not linked to domain memory size".

A memory corruption by Xen is extremely unlikely.
I believe in that.

So it looks like to me this is a related to your domain (kernel or userspace), 
possibly because memory has not been freed correctly.
It might be. But happens only with and right after vcpu pinning.

Below a list of questions to answer:
     - Can you give the steps to reproduce it from boot?
The step is single and trivial, just try to pin vcpus from Dom0.

     - How much memory left do you have before calling xl vcpu-pin?
Meminfo says
    root@salvator-x:~# cat /proc/meminfo
    MemTotal:        2995828 kB
    MemFree:         2810360 kB
    MemAvailable:    2758420 kB

Top says:
    Mem: 185592K used, 2810236K free, 21020K shrd, 0K buff, 53000K cached
    CPU:   0% usr   8% sys   0% nic  91% idle   0% io   0% irq   0% sirq

     - When exactly do you pin the vCPUs? (i.e how long after boot)
Right after login.

     - What are the other programs running? How much memory are they using?
Weston, systemd daemons, Xen daemons, other Yocto daemons. Actually, nothing 

Andrii Anisov.

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.