From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 5D0111FF145 for ; Thu, 05 Feb 2026 13:54:22 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5C0EBF94E; Thu, 5 Feb 2026 13:54:54 +0100 (CET) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: Re: [PATCH qemu-server 2/2] config: document default balloon behavior In-Reply-To: <20260205125208.311721-3-m.sandoval@proxmox.com> (Maximiliano Sandoval's message of "Thu, 5 Feb 2026 13:52:07 +0100") References: <20260205125208.311721-1-m.sandoval@proxmox.com> <20260205125208.311721-3-m.sandoval@proxmox.com> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Thu, 05 Feb 2026 13:54:50 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770296012962 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.088 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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: HTQLLEZAL5DKZ3LFT3WUVIEVJPS2IOYP X-Message-ID-Hash: HTQLLEZAL5DKZ3LFT3WUVIEVJPS2IOYP X-MailFrom: m.sandoval@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: Maximiliano Sandoval writes: > The behavior for this key is the following: > - balloning=0: Disabled > - Not defined in the config: Enabled > - balloning=N: Enabled, and target memory set to N MiB As per the previous commit, there is a typo here. Please let me know if a v2 is preferable. > Instead of special-casing balloning=1 (or turning it into a property > string) to enable the drive without setting a target memory size, we > simply document the current behavior better. > > Signed-off-by: Maximiliano Sandoval -- Maximiliano