From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com,
Lukas Wagner <l.wagner@proxmox.com>
Subject: [pve-devel] applied: [pbs-devel] [PATCH proxmox-backup] proxmox-file-restore: allocate at least 256MB of RAM for the restore VM
Date: Tue, 15 Jul 2025 22:31:35 +0200 [thread overview]
Message-ID: <175261149294.2350789.4786280733989350110.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250715101907.303115-1-l.wagner@proxmox.com>
On Tue, 15 Jul 2025 12:19:07 +0200, Lukas Wagner wrote:
> 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:
>
> [...]
Applied, thanks!
[1/1] proxmox-file-restore: allocate at least 256MB of RAM for the restore VM
commit: 74d3d6e9da5a8e6c1abc05f3d3eb08d8c36eb8c5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
WARNING: multiple messages have this Message-ID
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com,
Lukas Wagner <l.wagner@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] proxmox-file-restore: allocate at least 256MB of RAM for the restore VM
Date: Tue, 15 Jul 2025 22:31:35 +0200 [thread overview]
Message-ID: <175261149294.2350789.4786280733989350110.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250715101907.303115-1-l.wagner@proxmox.com>
On Tue, 15 Jul 2025 12:19:07 +0200, Lukas Wagner wrote:
> 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:
>
> [...]
Applied, thanks!
[1/1] proxmox-file-restore: allocate at least 256MB of RAM for the restore VM
commit: 74d3d6e9da5a8e6c1abc05f3d3eb08d8c36eb8c5
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-07-15 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 10:19 Lukas Wagner
2025-07-15 20:31 ` Thomas Lamprecht [this message]
2025-07-15 20:31 ` [pbs-devel] applied: " Thomas Lamprecht
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=175261149294.2350789.4786280733989350110.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.