Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2024-12-24 14:59:25 -05:00
Code Issues Packages Projects Releases Wiki Activity

Fill in R4.0->R4.1 upgrade steps

Browse Source
This commit is contained in:
Marek Marczykowski-Górecki 2021-10-10 06:50:12 +02:00
parent e904cc0d68
commit f5ca579fe0
No known key found for this signature in database
GPG Key ID: F32894BE9684938A
1 changed files with 60 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

61
user/downloading-installing-upgrading/upgrade/4_1.md
View File

@ -21,7 +21,66 @@ If you would prefer to perform a clean installation rather than upgrading in-pla
## In-place upgrade
TODO
The upgrade may take several hours, and will download several gigabytes of data.
In place upgrade is a complex operation. For this reason, we provide a `qubes-dist-upgrade` tool to handle all the necessary steps automatically. You can install it with the following command in the dom0 terminal:
sudo qubes-dom0-update -y qubes-dist-upgrade
The upgrade consists of 7 stages - 6 before restarting the system - marked as "STAGE 0" through "STAGE 6" in the options list below. And the 7th stage is rebuilding the applications and features list - started with a `--resync-appmenus-features` option.
Full list of options can be obtained with `qubes-dist-upgrade --help`:
Usage: qubes-dist-upgrade [OPTIONS]...
This script is used for updating current QubesOS R4.0 to R4.1.
Options:
--double-metadata-size, -d (STAGE 0) Double current LVM thin pool metadata size.
--update, -t (STAGE 1) Update of dom0, TemplatesVM and StandaloneVM.
--template-standalone-upgrade, -l (STAGE 2) Upgrade templates and standalone VMs to R4.1 repository.
--release-upgrade, -r (STAGE 3) Update 'qubes-release' for Qubes R4.1.
--dist-upgrade, -s (STAGE 4) Upgrade to Qubes R4.1 and Fedora 32 repositories.
--setup-efi-grub, -g (STAGE 5) Setup EFI Grub.
--all, -a Execute all the above stages in one call.
--assumeyes, -y Automatically answer yes for all questions.
--usbvm, -u Current UsbVM defined (default 'sys-usb').
--netvm, -n Current NetVM defined (default 'sys-net').
--updatevm, -f Current UpdateVM defined (default 'sys-firewall').
--skip-template-upgrade, -j Don't upgrade TemplateVM to R4.1 repositories.
--skip-standalone-upgrade, -k Don't upgrade StandaloneVM to R4.1 repositories.
--only-update Apply STAGE 0, 2 and resync appmenus only to
selected qubes (coma separated list).
--keep-running List of extra VMs to keep running during update (coma separated list).
Can be useful if multiple updates proxy VMs are configured.
--max-concurrency How many TemplateVM/StandaloneVM to update in parallel in STAGE 1
(default 4).
--resync-appmenus-features Resync applications and features. To be ran individually
after reboot.
After installing the tool, upgrade can be performed all at once with:
sudo qubes-dist-upgrade --all
Optionally, an `--assumeyes` (or `-y`) option can be used to automatically accept all the actions without confirmation.
Alternatively, each upgrade stage can be started separately (see the list of options above).
After completing "STAGE 0" through "STAGE 6", restart the system. Then perform the final step:
sudo qubes-dist-upgrade --resync-appmenus-features
When this completes, you can start using Qubes OS 4.1.
### Known issues
1. The script does not convert LUKS1 to LUKS2 disk encryption format (fresh Qubes 4.1 install uses LUKS2 for disk encryption, while earlier versions use LUKS1).
2. Early Qubes 4.0 pre-releases (before R4.0-rc2) made `/boot/efi` partition only 200MB, which is too small for R4.1. In case of such partition layout, clean installation is necessary.
3. If user has created some custom qrexec policy entries, they may not be correctly handled in R4.1, resulting in denying all the calls. It is advised to verify if there are not qrexec policy errors in the log after the system restart - using `journalctl -b` command.
If any early upgrade stage fails, the `qubes-dist-upgrade` tool will try to restore previous system state. After fixing an issue, the tool can be started again, to retry the operation. If a later stage (number 3 or later) fails, the tool may not be able to rollback the changes. But it may still be possible to retry the upgrade.
## Update