Go back to topic: Automated Qubes OS Installation using Kickstart and/or PXE Network Boot
---- | |
---- | |
------ | |
----- | |
- Every Qubes OS install already comes with Kickstart files. For anyone curious, check your dom0 root directory for `/root/anaconda-ks.cfg` and `/root/initial-setup-ks.cfg`. | - Every Qubes OS install already comes with Kickstart files. For anyone curious, check your dom0 root directory for `/root/anaconda-ks.cfg` and `/root/initial-setup-ks.cfg`. - The PXE server could even potentially be an AppVM on another Qubes OS machine :scream: |
- Maybe your laptop is lost/stolen/damaged/seized, and you want to get back your custom-configured Qubes OS back up and running ASAP. Just plug it in, PXE network boot, go get a coffee, and | - Maybe your laptop is lost/stolen/damaged/seized, and you want to get back your custom-configured Qubes OS back up and running ASAP. Just plug it in, PXE network boot, go get a coffee, and you'll have your Qubes OS machine back before you know it! |
- | - Maybe you just want to run your Qubes OS dom0 in RAM. With a bit of tweaking this guide could be adapted to that purpose... |
Now all we need is a GUI tool for developing SaltStack configs that create 100% custom VMs (I'm not going to lie, I'm a little confused by the .top and .sls files, where they go, why they can't just be a single file etc., but I'm trying!), and we've got a 100% | Now all we need is a GUI tool for developing SaltStack configs that create 100% custom VMs (I'm not going to lie, I'm a little confused by the .top and .sls files, where they go, why they can't just be a single file etc., but I'm trying!), and we've got a 100% automated, easy-to-use, and zero-interaction method to set up every single aspect of a Qubes OS machine :sunglasses: |