From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 9E27676FA2 for ; Mon, 26 Apr 2021 15:04:54 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 946EA16237 for ; Mon, 26 Apr 2021 15:04:24 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 1A59B1622D for ; Mon, 26 Apr 2021 15:04:24 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id E2A22428F9 for ; Mon, 26 Apr 2021 15:04:23 +0200 (CEST) From: Stefan Reiter To: pbs-devel@lists.proxmox.com Date: Mon, 26 Apr 2021 15:04:16 +0200 Message-Id: <20210426130417.20979-3-s.reiter@proxmox.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20210426130417.20979-1-s.reiter@proxmox.com> References: <20210426130417.20979-1-s.reiter@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.020 Adjusted score from AWL reputation of From: address 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 Subject: [pbs-devel] [PATCH proxmox-backup 3/4] file-restore: use less memory for VM and reboot on panic 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: , X-List-Received-Date: Mon, 26 Apr 2021 13:04:54 -0000 With the vsock-pkt-buffer fix in proxmox-backup-restore-image, we can use way less memory for the VM without risking any crashes. 128 MiB seems to be the lowest it will go and still be fully reliable. While at it, add the "panic=1" argument to the kernel command line, so in case the kernel *does* run out of memory, it will at least restart automatically. Signed-off-by: Stefan Reiter --- Depends on proxmox-backup-restore-image patch, otherwise this will lead to crashes during downloads. Note that when debugging with this patch, you need to enable release builds, as the debug build of proxmox-file-restore-daemon is too big to fit in 128 MiB of memory (via the initramfs). src/bin/proxmox_file_restore/qemu_helper.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/bin/proxmox_file_restore/qemu_helper.rs b/src/bin/proxmox_file_restore/qemu_helper.rs index 0f3a7feb..46fa011b 100644 --- a/src/bin/proxmox_file_restore/qemu_helper.rs +++ b/src/bin/proxmox_file_restore/qemu_helper.rs @@ -168,13 +168,13 @@ pub async fn start_vm( "none", "-enable-kvm", "-m", - "512", + "128", "-kernel", buildcfg::PROXMOX_BACKUP_KERNEL_FN, "-initrd", &ramfs_path, "-append", - "quiet", + "quiet panic=1", "-daemonize", "-pidfile", &format!("/dev/fd/{}", pid_fd.as_raw_fd()), -- 2.20.1