So I looked in the forum and the only seemingly related issue seemed to be with start up and impacting an appvm, but i don’t seem to be having those issues… yet? So i wanted to check to see if I should be doing something to ameliorate this issues?
So I got a pop up saying:
“Memory Shortage Avoided
The background service app-qubes\x2dicon\x2dreceiver@autostart.service has been terminated by the Linux kernel because the system is low on memory. Consider closing unused applications or browser tabs.”
thats it, as far as i can remember it was there when i sat down at my computer after leaving it on overnight. I have 64GB of mem which I was thinking was enough so am hoping this can be resolved with a simple setting tweak?
My qubes desktops have either 48gb or 64gb of memory and I’ve never seen that message (not even when memory balancing has been used when opening a new qube which causes a reduction below max memory allocated to other qubes). Your memory should be enough. Is this message for a qube you are starting or for dom0 ?
Cr*p, happened again. But this time I noticed when i popped up and noted how much mem the opened VMs maxes were. So the error again is:
The background service app-qubes\x2dicon\x2dreceiver@autostart.service has been terminated by the Linux kernel because the system is low on memory. Consider closing unused applications or browser tabs.
So the open AppVMS have max allocations of:
6000, 15000, 4000, 4000, 2000, and 4000
its a hair over 30GB and I have 64GB installed so I can’t figure out what the issuse ist with this. For a bit more context I recently upgraded to 4.3.1 and restored my backups onto this new install but the mem allocations are mostly the same. The one that is given 15GB is what i use for multimedia and the others are just sys- and 1-2 “regular” appvms.
So would it be more useful for me to submit a bug report? If yes I certainly can try, though I have no idea what github repo it would be under? (there seem to be 200+ qubes repos?)
I think this is not normal behaviour, so it is not easy to know what is wrong… therefore lots of silence!
Some far-out ideas (maybe not useful, but what I might verify):
Are all your qubes regular App qubes?
Not StandAlones?
All with a min and a max memory…?
…so memory ballooning should work?
Are the restored ones all switched to a Qubes-OS 4.3 non-minimal template?
For any restored standalones, are they on an up to date distro version?
Did you check any of the xen tools? I think xentop -used in dom0- was helpful for me once.
Is your default dvm “normal”? (assuming you did not change default-mgmt-dvm: there can be several of these, but they are hidden by default)
“normal” means “not minimal, based on a regular fedora-43 template, maybe a debian one, without lots of tweaking”
qvm-ls has a lot of options - maybe it can give some hints by displaying extra columns. I suspect some of the gui widgets give some useful info about running qubes
Let us know if you get any clues, or find useful tools/commands for troubleshooting!
Just adding- maybe useful to find out for sure which qube(s) those messages are coming from!
Thanks! I had forgotten to respond. In short it seems to have fixed itself, or probably more accurately has not been an issue lately so with so many other things going its just defaulted to lower priority … until it happens again.