mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-12-20 13:14:26 -05:00
165 lines
6.0 KiB
ReStructuredText
165 lines
6.0 KiB
ReStructuredText
===========================
|
||
How to upgrade to Qubes 4.2
|
||
===========================
|
||
|
||
|
||
This page explains how to upgrade from Qubes 4.1 to Qubes 4.2. There are
|
||
two ways to upgrade: a clean installation or an in-place upgrade. In
|
||
general, a clean installation is simpler and less error-prone, but an
|
||
in-place upgrade allows you to preserve your customizations.
|
||
|
||
Back up
|
||
-------
|
||
|
||
|
||
Before attempting either an in-place upgrade or a clean installation, we
|
||
strongly recommend that you first :doc:`back up your system </user/how-to-guides/how-to-back-up-restore-and-migrate>` so that you don’t
|
||
lose any data.
|
||
|
||
Clean installation
|
||
------------------
|
||
|
||
|
||
If you would prefer to perform a clean installation rather than
|
||
upgrading in-place:
|
||
|
||
1. (optional) Run the updater to ensure all of your templates are in
|
||
their latest version.
|
||
|
||
2. Install the ``qubes-dist-upgrade`` tool. This is the inplace upgrade
|
||
tool, which is not what we’re doing. However it will be needed in
|
||
order to prepare the templates for the 4.2 version. You install it
|
||
with the following command in the dom0 terminal:
|
||
|
||
.. code:: bash
|
||
|
||
sudo qubes-dom0-update -y qubes-dist-upgrade
|
||
|
||
|
||
|
||
3. Change your templates to use the 4.2 repositories instead of the 4.1
|
||
ones. You do this with the following command in the dom0 terminal:
|
||
|
||
.. code:: bash
|
||
|
||
qubes-dist-upgrade --template-standalone-upgrade
|
||
|
||
|
||
**Note**: This step is critical to ensure the templates will receive
|
||
updates once Qubes 4.1 reaches end-of-life (EOL) and was missing in
|
||
previous clean installation instructions.
|
||
|
||
4. Create a
|
||
:ref:`backup <user/how-to-guides/how-to-back-up-restore-and-migrate:creating a backup>`
|
||
of your current installation.
|
||
|
||
5. :doc:`Download </user/downloading-installing-upgrading/downloads>` the latest 4.2 release.
|
||
|
||
6. Follow the :doc:`installation guide </user/downloading-installing-upgrading/installation-guide>` to
|
||
install Qubes 4.2.
|
||
|
||
7. :ref:`Restore from your backup <user/how-to-guides/how-to-back-up-restore-and-migrate:restoring from a backup>`
|
||
on your new 4.2 installation.
|
||
|
||
|
||
|
||
In-place upgrade
|
||
----------------
|
||
|
||
|
||
**Warning:** It is not possible to upgrade directly from releases
|
||
earlier than 4.1. If you’re still on an earlier release, please either
|
||
perform a `clean installation of 4.2 <#clean-installation>`__ or
|
||
:doc:`upgrade to 4.1 </user/downloading-installing-upgrading/upgrade/4_1>` first.
|
||
|
||
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:
|
||
|
||
.. code:: bash
|
||
|
||
sudo qubes-dom0-update -y qubes-dist-upgrade
|
||
|
||
|
||
|
||
The upgrade consists of six stages — three before restarting the system
|
||
— labeled “STAGE 1” through “STAGE 3” in the options list below, and
|
||
three after restarting the system — labeled as “STAGE 4” through “STAGE
|
||
6” below.
|
||
|
||
Full list of options can be obtained with ``qubes-dist-upgrade --help``:
|
||
|
||
.. code:: bash
|
||
|
||
Usage: qubes-dist-upgrade [OPTIONS]...
|
||
|
||
This script is used for updating current QubesOS R4.1 to R4.2.
|
||
|
||
Options:
|
||
--update, -t (STAGE 1) Update of dom0, TemplatesVM and StandaloneVM.
|
||
--release-upgrade, -r (STAGE 2) Update 'qubes-release' for Qubes R4.2.
|
||
--dist-upgrade, -s (STAGE 3) Upgrade to Qubes R4.2 and Fedora 37 repositories.
|
||
--template-standalone-upgrade, -l (STAGE 4) Upgrade templates and standalone VMs to R4.2 repository.
|
||
--finalize, -x (STAGE 5) Finalize upgrade. It does:
|
||
- resync applications and features
|
||
- cleanup salt states
|
||
--convert-policy, -p (STAGE 6) Convert qrexec policy in /etc/qubes-rpc/policy
|
||
to the new format in /etc/qubes/policy.d.
|
||
--all-pre-reboot Execute stages 1 to 3
|
||
--all-post-reboot Execute stages 4 to 6
|
||
|
||
--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.2 repositories.
|
||
--skip-standalone-upgrade, -k Don't upgrade StandaloneVM to R4.2 repositories.
|
||
--only-update Apply STAGE 4 and resync appmenus only to
|
||
selected qubes (comma separated list).
|
||
--keep-running List of extra VMs to keep running during update (comma 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).
|
||
|
||
|
||
|
||
After installing the tool, before-reboot stages can be performed at once
|
||
with:
|
||
|
||
.. code:: bash
|
||
|
||
sudo qubes-dist-upgrade --all-pre-reboot
|
||
|
||
|
||
|
||
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 1” through “STAGE 3”, restart the system. Then
|
||
perform the final steps:
|
||
|
||
.. code:: bash
|
||
|
||
sudo qubes-dist-upgrade --all-post-reboot
|
||
|
||
|
||
|
||
After performing those steps, it’s recommended to restart the system one
|
||
last time.
|
||
|
||
When this completes, you can start using Qubes OS 4.2.
|
||
|
||
Update
|
||
------
|
||
|
||
|
||
After upgrading or performing a clean installation, we strongly
|
||
recommend :doc:`updating your system </user/how-to-guides/how-to-update>`.
|