similar to: dom0 - oom-killer - memory leak somewhere ?

I had the dom0 which unfortunately didn''t have a console on it hit a race condition and saw oom errors on it also. This happened after it was running for over 36 hours with a domU whose load average was avg was around 3 most of the time. changeset: 7396:9b51e7637676 Dom0 - UP i686, Centos 4.1, 768 megs domU-1 92 megs snmpd domU-2 92 megs snmpdd domU-3 410 megs postgres, tomcat 5.5,

On Mon, Oct 13, 2014 at 04:02:52PM +1030, Rusty Russell wrote: > "Denis V. Lunev" <den at parallels.com> writes: > > From: Raushaniya Maksudova <rmaksudova at parallels.com> > > > > Excessive virtio_balloon inflation can cause invocation of OOM-killer, > > when Linux is under severe memory pressure. Various mechanisms are > > responsible for

On Mon, Oct 13, 2014 at 04:02:52PM +1030, Rusty Russell wrote: > "Denis V. Lunev" <den at parallels.com> writes: > > From: Raushaniya Maksudova <rmaksudova at parallels.com> > > > > Excessive virtio_balloon inflation can cause invocation of OOM-killer, > > when Linux is under severe memory pressure. Various mechanisms are > > responsible for

On Tue, Oct 14, 2014 at 10:14:05AM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > > On Mon, Oct 13, 2014 at 04:02:52PM +1030, Rusty Russell wrote: > >> "Denis V. Lunev" <den at parallels.com> writes: > >> > From: Raushaniya Maksudova <rmaksudova at parallels.com> > >> > >

On Tue, Oct 14, 2014 at 10:14:05AM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > > On Mon, Oct 13, 2014 at 04:02:52PM +1030, Rusty Russell wrote: > >> "Denis V. Lunev" <den at parallels.com> writes: > >> > From: Raushaniya Maksudova <rmaksudova at parallels.com> > >> > >

I think I wrote not very clearly. I say ''swap in domU will save in case lag or little mistake with balloon''. If course, there is no any kind of ballooning for dom0. Right now we running pretty much VMs for our cloud services and we use heavy memory management (it grabs and gives memory with lag less then second depends on usage in customers VM). And we have some statistics

Under both XEN 3.0.4 (2.6.16.33) and XEN 3.1 (2.6.18), I can make the OOM killer appear in dom0 of my server by doing heavy I/O from within a VM. If I start 5 VMs on the same server, each VM doing constant I/O over its boot disk (read/write a 2GB file), after about 30 minutes the OOM killer appears in dom0 and starts killing processes. This was observed using 256MB in dom0. If I bump the memory in

From: Raushaniya Maksudova <rmaksudova at parallels.com> Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS

From: Raushaniya Maksudova <rmaksudova at parallels.com> Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS

Hello, Like many trying and posting here, I''m new to VGA passthrough. Computer was bought, checking compatibility from http://wiki.xen.org/wiki/VTd_HowTo The hardware is mostly not exactly on the list, but mainly new versions of the same series (I think). IOMMU "seems" to be working (not 100% sure what to check). I used debian/wheezy kernel and xen, dom0 and HVM domu.

hi, With XEN enabled in mainline kernel 2.6.37 configured for nouveau, X failed with familiar symptoms. Found drm-tree did not have the TTM_MEMTYPE_FLAG_NEEDS_IOREMAP or the drm_scatter patches. Applied these patches (generated from my working 2.6.32.18 xen kernel with 2.6.35.4 drm-tree backported) to the 2.6.37 mainline kernel. Now starting X in dom0 invokes the OOM killer! Bare boot works, as

Hi, I''m working on the following topic from the xen roadmap as a part of an academic project: "Improve interaction between balloon driver and page allocator to avoid memory crunch." I have a few doubts regarding what exactly needs to be done: 1. Should the working of the balloon driver be same as in the case of VMware ESX balloon driver? (

Hi, I'm using linux 2.6.21.5 and our kernel is freeze. The problem is, if I create a Software bridge using $brctl command. and add two interfaces say, eth0.0 and eth0.1 using $brctl addbr br-lan $brctl addif br-lan eth0.0 $brctl addif br-lan eth0.1 and when i send traffic from a host connected to one port to host connected at other end, soon all the memory is dried up and and kernel

Yes, the clients are doing lots of creates. But my question is, if this is a memory leak, why does ocfs2 eat up the memory as soon as the clients start accessing the filesystem. Within about 5-10 minutes all physical RAM is consumed but then the memory consumption stops. It does not go into swap. Do you happen to know what version of ocfs2 has the fix? If it was a leak would the process not be

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Hello! I am writing a FS filter that will be above the ext3 filesystem. For my own purposes I need severl bytes in inode. There are not enough space current inode so I need to create my own inode functions alloc_inode() & destroy_inode(). The problem causes when destroying slab cache at removing my module (rmmod). kmem_cache_destroy: Can't free all objects What I do: - install my

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Hi all, Just watching for my first time the 'oom-killer' call in a CentOS 4.2 workstation. System was running normally but with high load of nice process, iow, rosetta and seti, others appart, nautilus, etc... i realized that after a night of standby running normally, the next moorning after few manual operations from X-session in local console, it started a massive swapping, this time