From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 014701FF0AA for ; Tue, 22 Sep 2026 22:04:34 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id A821E21501; Tue, 22 Sep 2026 22:04:29 +0200 (CEST) Message-ID: <11d5cb89-81b0-445c-b470-9cd68d5a6f5a@proxmox.com> Date: Tue, 22 Sep 2026 22:04:23 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: applied: [PATCH pve-ha-manager 2/2] fix #7974: env: pve2: set dynamic service mem value to host memory usage To: Dominik Rusovac , pve-devel@lists.proxmox.com References: <20260828123239.1110595-1-d.rusovac@proxmox.com> <20260828123239.1110595-2-d.rusovac@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20260828123239.1110595-2-d.rusovac@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1790107463462 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.819 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: VIGGX4DZKC5MNQUJQRD6TCN3WEV4XU3Y X-Message-ID-Hash: VIGGX4DZKC5MNQUJQRD6TCN3WEV4XU3Y X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Am 28.08.26 um 14:32 schrieb Dominik Rusovac: > Make memory accounting in dynamic CRS consistent. > > Atm the imbalance value that triggers rebalancing is derived from the > guests' host memory usage, which corresponds to the respective host-side > cgroup footprints of the guests. However, the scheduler's decision > procedure predicts the changes in imbalance caused by migration > candidates based on memory usage (inside the guests). This discrepancy > can lead to oscillating migrations, as described in detail in [0]. > > For VMs, host memory usage is the relevant stat, as it better describes > the actual cost of running on a node than memory usage. Host memory > usage is not available for containers, so fall back to memory usage for > containers. > > [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7974 > > Signed-off-by: Dominik Rusovac > --- > src/PVE/HA/Env/PVE2.pm | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > applied, thanks!