Add new device to the default `vm-pool` revisions

Go back to topic: Add new device to the default `vm-pool`

  1. v3 anchor; v3 full version
  2. v2 anchor; v2 full version

Revision #3

Edited on
2025-10-21
Edited by user
otter2
``` ``` > :information_source: for newly installed systems (not upgraded in-place) older than 4.0, you should only run `grub2-mkconfig -o /boot/grub2/grub.cfg`, see [this topic](https://forum.qubes-os.org/t/how-to-change-boot-options-for-usb-boot/36387/3)

Revision #2

Edited on
2025-10-03
Edited by user
otter2
Also, for encrypted setups I haven't figured out how to print what device is being unlocked during boot. It can be annoying, but it seems like system simply follows the order in `/etc/crypttab`. I tend to successfully guess it. Please help if you know anything about this.
The algorithm for encrypted partition is a bit different, follow [secondary storage : Example setup of second drive](https://doc.qubes-os.org/en/latest/user/advanced-topics/secondary-storage.html#example-setup-of-second-drive) until you end up with an auto-mounted luks partition, after that continue with the step 2.
The algorithm for encrypted partition is a bit different, follow [secondary storage : Example setup of second drive](https://doc.qubes-os.org/en/latest/user/advanced-topics/secondary-storage.html#example-setup-of-second-drive) until you end up with an auto-mounted luks partition, after that continue with the step 2.### Booting with encrypted devices On qubes, `systemd-cryptsetup` handles decryption during boot. It always tries available passphrases before prompting the user for a password. If you have multiple partitions with the same passphrase, you'll only need to enter it once. If, on the other hand, you want to have multiple partitions with different passphrases unlocked during boot, you will encounter the fact that qubes splash screen doesn't tell what you're currently unlocking. It does not matter. You can enter passphrases in any order, `systemd-cryptsetup` will figure out what goes where by itself. Even with that, it might be hard to figure out what's going on if you make a typo in one of your passphrases, so let's get more information printed anyway. There are two ways to print the device name when prompted for a passphrase during boot: [details="Make plymouth (program responsible for the splash screen) print the device name"] Idk, feel free to contribute... [This topic](https://forum.qubes-os.org/t/has-anyone-worked-with-plymouth-splash-animations-with-qubes-os/14188) might be a good starting point [/details] [details="Disable plymouth, enjoy the beauty of the console"] 1. Add the following parameters to `GRUB_CMDLINE_LINUX` in `/etc/default/grub`: ``` rd.plymouth=0 plymouth.enable=0 ``` 1. Generate the config: ``` # If you're using BIOS grub2-mkconfig -o /boot/grub2/grub.cfg # If you're using UEFI grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg ``` This disables plymouth and leaves you with concise console output and prompts. If you want verbose console during boot, you can remove `quiet` parameter from `GRUB_CMDLINE_LINUX`. [/details] Alternatively, if you don't want to do any of these, but get stuck entering passphrases, you can simply press ESC to exit into console. ### Notes As is, with disabled plymouth, you'll end up with UUIDs of devices in the passphrase prompt. I think you can assign aliases to partitions in `/etc/crypttab` instead...