search for: baloons

Is there a baloon driver for Windows hvm guests that can be used in a commercial environment? I''ve seen sugestions to use the drivers from Xenexpress, but i''m not sure if i can use them in opensource xen 3.2.1 legally (or if they will actually work). jacek _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

"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> >> > >> > Excessive virtio_balloon inflation can cause invocation of OOM-killer, >> >

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

"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 correct virtio_balloon memory management. Nevertheless > it is often the case that these

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> > >> > >

Hello, I work in a hosting company, we have tens of Xen dom0 running just fine, but unfortunately we do have a few that get out of control. Reported behaviour : - dom0 uses more and more memory - no process can be found using that memory - at some point, oom killer kicks in, and kills everything, until even ssh the box becomes hard - when there is really no more process to kill, it crashes

hi, there is something, what i don''t understand. I have in my DomU config: memory = "128" maxmem = "1024" tsles:~ # cat /proc/xen/balloon Current allocation: 237568 kB Requested target: 237568 kB Minimum target: 237568 kB Maximum target: 1048576 kB Low-mem balloon: 804352 kB High-mem balloon: 0 kB Driver pages: 1024 kB Xen

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

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

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

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

I tryed te baloon out a domu and get: xm balloon VS01 1 Command balloon is deprecated But i need it... What can i doo? Dom0: Debian Etch - Kernel 2.6.18-6-xen-686 DomU: Debian Etch - 2.6.18-6-xen-vserver-686 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I searched a bit, but have come up short. Are there any libraries for creating popup forms w/ rails? These would not be displayed in a separate browser window, but rather made visible over an open page and adjacent to a clicked link -- similar to the google maps baloons, or the gmail popups. Lots of other examples out there... Thanks --------------------------------- Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great rates starting at 1&cent;/min. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wr...

With the lake of iommu, dom0 must have a 1:1 memory mapping for all these guest physical address. When the ballon decides to give back a page to the kernel, this page must have the same address as previously. Otherwise, we will loose the 1:1 mapping and will break DMA-capable device. Signed-off-by: Julien Grall <julien.grall@linaro.org> CC: Keir Fraser <keir@xen.org> CC: Jan Beulich