Qubes
Note: after restoring from a backup make sure to recreate the templates from the base again to save disk space because of copy-on-write.
Template VMs
In my Fedora VMs
systemctl mask packagekitecho "vm.swappiness = 1" | sudo tee systemctl.conf- I used this for Qubes 4.0 and 4.1, seeing if I don't need it for 4.2
dom0
- RPC Policy: Set USB keyboards and mice to ask for being attached to dom0
Follow https://github.com/Qubes-Community/Contents/blob/master/docs/customization/dpi-scaling.md for getting it to work with my 4k display.Went back to a non-4k display.Appearance -> Style -> Adwaita-dark- Change global copy/paste to use Win+C and Win+V
- Clock format:
%a %F %r
Create /usr/local/bin/vault, mapped to ctrl+shift+x
#!/bin/sh exec qvm-run vault keepassxc
Redshift, following https://www.bryceguinta.me/install-configure-and-autostart-redshift-on-qubes-40.html, except place the config file at
~/redshift.conf so it gets included in dom0 backups and use Settings -> Session and Startup to add the autostart entry.
Advanced debugging
In the grub bootloader you can press "E" on a menu item to edit both the Linux and Xen command lines before booting. Removing "quiet" from Linux will make the boot process verbose and you can see where you get stuck.
Boot a Qubes installer USB, select rescue mode. Select option #1, enter your decryption password. Ignore the error which says "You have no Linux partitions...", it's wrong and a known issue.
If you run e.g. fdisk -l, you should see your disks and VMs. You should be able to mount dom0 with e.g. mkdir /mnt/dom0 && mount /dev/qubes_dom0/root /mnt/dom0. To do stuff in dom0, you might chroot /mnt/dom0.
If you need /proc, /sys, etc. inside the chroot, see this post for how to mount them.
