From: Markus Ebner <info@ebner-markus.de>
To: pve-devel@lists.proxmox.com
Cc: Markus Ebner <info@ebner-markus.de>
Subject: [PATCH qemu-server v3 0/3] Extend qga file-read with chunked access for large files
Date: Thu, 26 Feb 2026 13:31:16 +0100 [thread overview]
Message-ID: <20260226123122.60418-1-info@ebner-markus.de> (raw)
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).
Since decode wasn't optional, readinb binary data encoded as JSON
string regularly caused highly inflated payload sizes due to extensive
unicode escaping.
This series extends the file-read method with three new parameters:
- decode — Controls whether the base64‑encoded data returned by the
guest agent should be decoded before being sent back through the API.
When disabled, the base64 string is passed through unchanged, which is
ideal for binary data and mirrors the existing encode parameter of
file-write.
- offset — Allows reading from an arbitrary byte offset within the
file.
- count — Allows requesting a smaller number of bytes than the
internal 16 MiB limit, granting more flexibility to avoid API
timeouts.
With these additions, the agent/file-read API now essentially behaves
like a pread() systemcall.
All parameter additions were done in a backwards-compatible fashion.
Markus Ebner (3):
agent: file-read: Allow specifying max number of bytes to read
agent: file-read: Allow maintaining base64-encoding of content
agent: file-read: Allow specifying byte offset to start reading at
src/PVE/API2/Qemu/Agent.pm | 62 ++++++++++++++++++++++++++++++++------
1 file changed, 53 insertions(+), 9 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-26 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 12:31 Markus Ebner [this message]
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 ` applied: [PATCH qemu-server v3 0/3] Extend qga file-read with chunked access for large files Fiona Ebner
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=20260226123122.60418-1-info@ebner-markus.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox