Repository navigation
Conversation
Activity Monitor shows krunkit's physical footprint, and macOS counts a page of guest memory there twice when krunkit writes it and the guest then uses it: disk reads, received packets, virtio-fs reads, and the kernel and initramfs at boot. After a guest reads a 600 MiB file, the footprint grows by about 1.2 GiB. Add a section to docs/usage.md that explains this and points to the system-wide numbers, which show what a VM really costs the host. Assisted-by: Claude Code / claude-opus-5.5 Signed-off-by: JartX <sagformas@epdcenter.es>
JartX
requested review from
jakecorrenti,
slp and
tylerfanelli
as code owners
October 26, 2026 13:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a short section to
docs/usage.mdon measuring krunkit's memory use on macOS.Activity Monitor's "Memory" column shows krunkit's physical footprint, and macOS counts a page of guest memory there twice when krunkit writes it and the guest then uses it: disk reads, received packets, virtio-fs reads, and the kernel at boot. After a guest reads a 600 MiB file, krunkit's footprint grows by about 1.2 GiB. The section explains this and points to system-wide numbers instead.
Details and a reproducer without libkrun are in libkrun/libkrun#947.