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 000AE1FF16B for ; Tue, 15 Jul 2025 12:18:15 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A123938A33; Tue, 15 Jul 2025 12:19:13 +0200 (CEST) From: Lukas Wagner To: pbs-devel@lists.proxmox.com Date: Tue, 15 Jul 2025 12:19:07 +0200 Message-Id: <20250715101907.303115-1-l.wagner@proxmox.com> X-Mailer: git-send-email 2.39.5 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.019 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 RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pbs-devel] [PATCH proxmox-backup] proxmox-file-restore: allocate at least 256MB of RAM for the restore VM X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" The update from proxmox-backup-restore-image 0.7.0 -> 1.0.0 increased the size of the initramfs image by couple of megabytes (~45 -> ~49), making it too large to be successfully booted in a VM with 192MB of RAM. This led to a "VM exited before connection could be established (500)" error in the GUI when attempting to restore a single file, while /var/log/proxmox-backup/file-restore/qemu.log reported the following error: Initramfs unpacking failed: write error As a stop-gap measure, the minimum RAM allocation is bumped to 256MB. Since the amount of RAM is based on the number of disks, giving the VM more memory if a large number of disks is associated with the backup snapshot, this patch was also tested with 19, 20 and 25 disks as to ensure that the remaining cases still work fine without a bump. Signed-off-by: Lukas Wagner --- proxmox-file-restore/src/qemu_helper.rs | 1 - 1 file changed, 1 deletion(-) diff --git a/proxmox-file-restore/src/qemu_helper.rs b/proxmox-file-restore/src/qemu_helper.rs index e0e16911..4be9331c 100644 --- a/proxmox-file-restore/src/qemu_helper.rs +++ b/proxmox-file-restore/src/qemu_helper.rs @@ -316,7 +316,6 @@ pub async fn start_vm( } else { // add more RAM if many drives are given match id { - f if f < 10 => 192, f if f < 20 => 256, _ => 384, } -- 2.39.5 _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel