From 256b02d0d38c04f95e30e3d48532612150a6b48a Mon Sep 17 00:00:00 2001 From: Bryce Guinta Date: Sat, 29 Aug 2020 18:59:09 -0400 Subject: [PATCH] Document use of xl info to find total memory I had to do some digging to figure out why I thought dom0 was reporting an incorrect amount of total memory available, and finally found this command. This document comes up very high in the search results for Qubes memory so I thought I'd put it here since it provides some concrete context to the architecture. --- developer/services/qmemman.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/developer/services/qmemman.md b/developer/services/qmemman.md index 356ddbf5..f9581adb 100644 --- a/developer/services/qmemman.md +++ b/developer/services/qmemman.md @@ -75,3 +75,8 @@ Whenever *qmemman* is asked to return X megabytes of memory to Xen free pool, th 4. wait BALOON\_DELAY (0.1s) 5. if some domain have not given back any memory, remove it from the donors list, and go to step 2, unless we already did MAX\_TRIES (20) iterations (then return error). + +Notes +----- + +Conventional means of viewing the memory available to Qubes will give incorrect values for `dom0` since commands such as `free` will only show the memory allocated for `dom0`. Run the `xl info` command in `dom0` and read the `total_memory` field to see the total memory available to Qubes.