As expected I reproduced the issue with a multiboot unikernel. As I currently understand the issue:
- the system is under memory pressure (some AppVM won’t be able to get their highmem value)
- mirage-fw is excluded from the memory balancing process (but still seems to be implied at some point, didn’t checked without it, but @rrn has done that)
- starting a new VM is slow because that VM have to use swap due to being at its lowmem value
- shutting down an AppVM release some memory and permits to increase the memory for other AppVMs
journalctl -f -u qubes-qmemman doesn’t gives me many informations, I got this morning
Xen free = 17325363471 too small for satisfy assignments! assigned_but_unused=17471681968, domdict={'0': {'memory_current': 4278190080, 'memo...
and later
dom '22' still hold more memory than have assigned (18972307456 > 18531172964)
but that isn’t always the case 