I've been testing the patch few days, the bolloon OOM notifier patch
seems to
do a good jobs freeing memory before OOM killer is about to kill a process.
Although on few ocassions it wasn't enough.
But if you're memory target is anywhere within some range of freeram, and
it's hard to say how much
Thanks for the pointer I'll try it out.
- mario
On 02/06/2015 07:57 AM, Paolo Bonzini wrote:
>
>
> On 06/02/2015 02:18, Mario Smarduch wrote:
>> Hi,
>>
>> I'm looking into qemu/balloon driver VM overcommit. I noticed
>> virtio-balloon driver will take any setting from virtio-balloon-device
>> t
On 06/02/2015 02:18, Mario Smarduch wrote:
> Hi,
>
> I'm looking into qemu/balloon driver VM overcommit. I noticed
> virtio-balloon driver will take any setting from virtio-balloon-device
> to the point Guest dies.
>
> For a 1G guest
> $ sudo echo balloon 100 | socat - tcp4-connect:127.0.0.1:44
Hi,
I'm looking into qemu/balloon driver VM overcommit. I noticed
virtio-balloon driver will take any setting from virtio-balloon-device
to the point Guest dies.
For a 1G guest
$ sudo echo balloon 100 | socat - tcp4-connect:127.0.0.1:
you get (same with libvirt setmem)
root@localhost:~# fre
