Git-Mirrors/Qubes-Community-Content
1
0
Fork 0
mirror of https://github.com/Qubes-Community/Contents.git synced 2024-12-22 21:59:26 -05:00
Code Issues Packages Projects Releases Wiki Activity

Fix wrong numbering

Browse Source
This commit is contained in:
Sarvottam Kumar 2020-05-30 23:05:55 +05:30 committed by GitHub
parent d1dfc2378d
commit b26f7b9d9a
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
troubleshooting/out-of-memory.md
View File

@ -19,17 +19,17 @@ qvm-console-dispvm <VMname>
If this does not work, check the size of /var/lib/qubes/qubes.xml. If it is zero, you'll need to use one of the file backup (stored in /var/lib/qubes/backup), hopefully you have the current data there. Find the most recent one and place in /var/lib/qubes/qubes.xml instead of the empty file.
In any case you'll need some disk space to start the VM. Check `df -h` output if you have some. If not, some hints how to free some disk space:
In any case you'll need some disk space to start the VM. Check `df -h` output if you have some. If not, here are some hints how to free some disk space:
1. Clean yum cache:
1. Clean yum cache
~~~
sudo yum clean all
~~~
1. Delete .img files of a less important VM, that can be found in
2. Delete .img files of a less important VM, that can be found in /var/lib/qubes/appvms/
/var/lib/qubes/appvms/. Then, when the system is working again, cleanup the rest with:
Then, when the system is working again, cleanup the rest with:
~~~
qvm-remove <VMname>
@ -37,11 +37,11 @@ qvm-remove <VMname>
With this method you lose the data of one VM, but it'll work more reliably.
1. Decrease filesystem safety margin (5% by default):
3. Decrease filesystem safety margin (5% by default)
~~~
sudo tune2fs -m 4 /dev/mapper/vg_dom0-lv_root
~~~
1. Remove some unneeded files in dom0 home (if you have any, most likely not).
4. Remove some unneeded files in dom0 home (if you have any, most likely not)