From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Markus Ebner <info@ebner-markus.de>
Subject: applied: [PATCH qemu-server v3 0/3] Extend qga file-read with chunked access for large files
Date: Thu, 26 Feb 2026 13:42:30 +0100 [thread overview]
Message-ID: <177210973523.86312.8411001521851992446.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260226123122.60418-1-info@ebner-markus.de>
On Thu, 26 Feb 2026 13:31:16 +0100, Markus Ebner wrote:
> The file-read command of the QEMU guest agent previously had several
> practical limitations. It always read a fixed 16 MiB block starting at
> offset 0, making it impossible to retrieve larger files in multiple
> chunks. On busy or resource‑constrained hosts, requests for large files
> often timed out because the agent attempted to read and JSON‑encode the
> entire 16 MiB block at once (while producing high CPU load in both
> qemu-guest-agent, as well as pvedaemon).
>
> [...]
Applied, thanks!
[1/3] agent: file-read: Allow specifying max number of bytes to read
commit: 5c623f82c07624528c6b107cc6c9660ec6b84d98
[2/3] agent: file-read: Allow maintaining base64-encoding of content
commit: a1397a11dd6092ae252d2cc8c65b1ca1eb815e58
[3/3] agent: file-read: Allow specifying byte offset to start reading at
commit: ec268ede5b1cfc050ff3a6d252bebabacee3154e
prev parent reply other threads:[~2026-02-26 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 12:31 Markus Ebner
2026-02-26 12:31 ` [PATCH qemu-server v3 1/3] agent: file-read: Allow specifying max number of bytes to read Markus Ebner
2026-02-26 12:31 ` [PATCH qemu-server v3 2/3] agent: file-read: Allow maintaining base64-encoding of content Markus Ebner
2026-02-26 12:31 ` [PATCH qemu-server v3 3/3] agent: file-read: Allow specifying byte offset to start reading at Markus Ebner
2026-02-26 12:42 ` Fiona Ebner [this message]
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=177210973523.86312.8411001521851992446.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=info@ebner-markus.de \
--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.