I realized today (so I don’t know if this started the day I upgraded to Fedora 41) that my Fedora 41 app qube are stuck at the minimum amount of RAM I allocated to them.
For example, if my personal qube have an initial memory of 800 MB and a maximum memory of 8000 MB, they will always be at 800 MB. Even when I am doing intensive work on the qube, they just freeze when I reach the 800 MB limit.
Make sure you have all dom0’s updates installed and run the Qubes Updater again on the fedora template. This will fix the selinux issue and should solve your issue. After using the updater, restart all qubes based on the template for them to take the change.
The problem is not solved, but I think I made a mistake.
I started to update dom0, but I saw nothing happening, so I canceled the update. However, the update was actually in progress, and I don’t know if it went through or if it really stopped in the middle.
Now when I check for dom0 updates, I get this:
Checking for available updates for dom0...
Using fedora-dvm as UpdateVM for Dom0
Checking for dom0 updates...
Updating and loading repositories:
Fedora 37 - x86_64 - Updates 100% | 9.3 KiB/s | 5.9 KiB | 00m01s
Fedora 37 - x86_64 100% | 56.1 KiB/s | 6.0 KiB | 00m00s
Qubes Host Repository (updates) 100% | 20.0 KiB/s | 2.7 KiB | 00m00s
Repositories loaded.
No new updates available
No dom0 updates available
When i check my fedora 41 Template for update it tell me that all is up to date.
Just to be sure, can you run this command in a dom0 terminal and confirm that you have version 4.2.32?
rpm -qa | grep core-dom0-linux
This version includes a plugin that fixes the memory problem using the Qubes updater. If it doesn’t work, can you run the following command in the template and check the selinux label?
I notice something strange today.
I have the new qubes boot logo when i shut down my computer but not when i start it ?
I was wondering if this was i sign that the update has gone wrong ?
Dom0 updates won’t show progress until they are completed. Always best to not cancel a dom0 update, it does a lot of critical stuff like updating the kernel loaded at boot.
You also have to restart for all dom0 update to take effect. So, if you have a persistent issue, do dom0 update then restart then do all the other updates.
Just for future reference, ‘ls -Z’ tells us the SElinux security context for a file. It seems that the correct result for meminfo-writer should probably look like this:
$ ls -Z /usr/sbin/meminfo-writer
system_u:object_r:qubes_meminfo_writer_exec_t:s0
There are many resources which can explain SElinux far better than I ever could. In very short version, it is related to allowing and forbidding things from happening.