From: Roland via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: Roland <devzero@web.de>
Subject: Re: [PVE-User] A less aggressive OOM?
Date: Tue, 8 Jul 2025 14:05:54 +0200 [thread overview]
Message-ID: <mailman.1122.1751976670.395.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <aegsjl-66q.ln1@leia.lilliput.linux.it>
[-- Attachment #1: Type: message/rfc822, Size: 9044 bytes --]
From: Roland <devzero@web.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] A less aggressive OOM?
Date: Tue, 8 Jul 2025 14:05:54 +0200
Message-ID: <6b15b452-0fc6-41ee-a1f7-34cd7943ab38@web.de>
hi,
it's a little bit weird that OOM kicks in with VMs <32GB RAM when you
have 64GB
take a closer look why this happens , i.e. why OOM thinks there is ram
pressure
roland
Am 07.07.25 um 11:26 schrieb Marco Gaiarin:
> We have upgraded a set of clusters from PVE6 to PVE8, and we have found that
> in newer kernels, OOM is a bit more 'aggressive' and sometime kill a VMs.
>
> Nodes have plently of RAM (64GB, VMs are 2-3, each 8GB ram), VMs have qemu
> agent installed and ballooning enabled, but still sometime OOM happen.
> Clearly, if get OOM the main VMs that have the local DNS, we get some
> trouble.
>
>
> I've looked in PVE wiki, but found nothing. There's some way to relax OOM,
> or control their behaviour?
>
> In nodes there's no swap, so probably the best thing to do (but the hardest
> one ;-) is to setup some swap with a lower swappiness, but i'm seeking
> feedback.
>
>
> Thanks.
>
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
prev parent reply other threads:[~2025-07-08 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 9:26 Marco Gaiarin
2025-07-07 21:39 ` Victor Rodriguez
2025-07-08 16:31 ` Marco Gaiarin
2025-07-10 8:56 ` Victor Rodriguez
2025-07-10 9:08 ` Roland via pve-user
2025-07-10 14:49 ` dorsy via pve-user
2025-07-10 16:11 ` Roland via pve-user
[not found] ` <98ace9cf-a47f-40cd-8796-6bec3558ebb0@web.de>
2025-07-10 16:15 ` dorsy via pve-user
2025-07-13 14:28 ` Marco Gaiarin
2025-07-08 12:05 ` Roland via pve-user [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mailman.1122.1751976670.395.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=devzero@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox