Merge branch 'patch-4' of https://github.com/sarru1291/qubes-doc into sarru1291-patch-4

This commit is contained in:
Andrew David Wong 2020-06-04 08:09:34 -05:00
commit 5e5a5d4e7d
No known key found for this signature in database
GPG Key ID: 8CE137352A019A17

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)