Editing Openai/695158d7-1b68-800b-a02f-4817bf1f6d25 (section)

==== Only follow this if you understand CLI and have a backup. Replace device names and sizes to match your layout. ====

Assume you created partitions:
* /dev/nvme0n1p1 — EFI (vfat), 600 MiB — unencrypted
* /dev/nvme0n1p2 — /boot 1024 MiB — unencrypted
* /dev/nvme0n1p3 — 150 GiB — intended for LUKS (system)
* /dev/nvme0n1p4 — media (rest) — unencrypted

Commands (run in the live installer terminal):

<syntaxhighlight lang="bash"># 1) format and set up LUKS on the partition
sudo cryptsetup luksFormat --type luks2 /dev/nvme0n1p3
=== open it (choose a name like cryptroot) ===
sudo cryptsetup open /dev/nvme0n1p3 cryptroot

=== 2) create LVM PV and VG inside the decrypted mapping ===
sudo pvcreate /dev/mapper/cryptroot
sudo vgcreate Notebook /dev/mapper/cryptroot

=== 3) create dom0 logical volumes (example sizes) ===
sudo lvcreate -L 20G -n qubes-dom0-root Notebook
sudo lvcreate -L 33G -n qubes-dom0-swap Notebook

=== 4) create a thin-pool to back thin LVs (choose size for pool; here 90G as example) ===
sudo lvcreate --type thin-pool -L 90G -n thinpool Notebook

=== 5) create thin logical volumes for VMs (virtual size can be larger than physical) ===
=== e.g., create a 200G-thin LV (virtual size) for VM storage ===
sudo lvcreate -V 200G -T Notebook/thinpool -n qubes-vm-pool

=== 6) create filesystems on LVs where expected (dom0 uses ext4 etc.) ===
sudo mkfs.ext4 /dev/Notebook/qubes-dom0-root
sudo mkswap /dev/Notebook/qubes-dom0-swap
=== DO NOT mkfs on the thin pool itself ===

</syntaxhighlight>

After this you’d tell the installer where root, swap and the VM pool are (if doing everything manually) or let the installer proceed if it detects these LVs. Again, manual approach requires care.