search for: baloon

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

...s reminds me of the balloon fs that Google once proposed. > This really needs to be controlled from host though. > At the moment host does not expect guest to deflate before > requests. > So as a minimum, add a feature bit for this. what if you want a mix of > mandatory and optional balooning? I guess we can use multiple balloons, > is that the idea? Trying to claw back some pages on OOM is almost certainly correct, even if the host doesn't expect it. It's roughly equivalent to not giving up pages in the first place. Cheers, Rusty. PS. Yes, a real guest-driven balloon...

...ome amount of sense. This reminds me of the balloon fs that Google once proposed. This really needs to be controlled from host though. At the moment host does not expect guest to deflate before requests. So as a minimum, add a feature bit for this. what if you want a mix of mandatory and optional balooning? I guess we can use multiple balloons, is that the idea? > But I suggest a few minor changes: > > > +static int oom_vballoon_pages = OOM_VBALLOON_DEFAULT_PAGES; > > +module_param(oom_vballoon_pages, int, S_IRUSR | S_IWUSR); > > +MODULE_PARM_DESC(oom_vballoon_pages, &qu...

...ome amount of sense. This reminds me of the balloon fs that Google once proposed. This really needs to be controlled from host though. At the moment host does not expect guest to deflate before requests. So as a minimum, add a feature bit for this. what if you want a mix of mandatory and optional balooning? I guess we can use multiple balloons, is that the idea? > But I suggest a few minor changes: > > > +static int oom_vballoon_pages = OOM_VBALLOON_DEFAULT_PAGES; > > +module_param(oom_vballoon_pages, int, S_IRUSR | S_IWUSR); > > +MODULE_PARM_DESC(oom_vballoon_pages, &qu...

"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 fs that Google once proposed. > > This really needs to be controlled from host though. > > At the moment host does not expect guest to deflate before > > requests. > > So as a minimum, add a feature bit for this. what if you want a mix of > > mandatory and optional balooning? I guess we can use multiple balloons, > > is that the idea? > > Trying to claw back some pages on OOM is almost certainly correct, > even if the host doesn't expect it. It's roughly equivalent to not > giving up pages in the first place. Well the difference is that...

...on fs that Google once proposed. > > This really needs to be controlled from host though. > > At the moment host does not expect guest to deflate before > > requests. > > So as a minimum, add a feature bit for this. what if you want a mix of > > mandatory and optional balooning? I guess we can use multiple balloons, > > is that the idea? > > Trying to claw back some pages on OOM is almost certainly correct, > even if the host doesn't expect it. It's roughly equivalent to not > giving up pages in the first place. Well the difference is that...

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

...ory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free some memory at the last moment before some process will be get killed by OOM-killer. This does not provide a security breach as baloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() fun...

...ory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free some memory at the last moment before some process will be get killed by OOM-killer. This does not provide a security breach as baloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() fun...

...ancing of memory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free memory at the last moment before some process get killed by OOM-killer. This does not provide a security breach as baloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() fun...

...ancing of memory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free memory at the last moment before some process get killed by OOM-killer. This does not provide a security breach as baloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() fun...

...ancing of memory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free memory at the last moment before some process get killed by OOM-killer. This does not provide a security breach as baloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() fun...

...ancing of memory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free memory at the last moment before some process get killed by OOM-killer. This does not provide a security breach as baloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() fun...

...ancing of memory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free memory at the last moment before some process get killed by OOM-killer. This does not provide a security breach as baloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() fun...

...ancing of memory by use of the virtio balloon should not cause the termination of processes while there are pages in the balloon. Now there is no way for virtio balloon driver to free memory at the last moment before some process get killed by OOM-killer. This does not provide a security breach as baloon itself is running inside guest OS and is working in the cooperation with the host. Thus some improvements from guest side should be considered as normal. To solve the problem, introduce a virtio_balloon callback which is expected to be called from the oom notifier call chain in out_of_memory() fun...

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

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://w...

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