From 7eeecb9e3749c996696d4d38efa4104d1c9914af Mon Sep 17 00:00:00 2001 From: Nihal <121309701+nihalxkumar@users.noreply.github.com> Date: Tue, 21 Jul 2026 10:05:49 +0000 Subject: [PATCH 1/2] Add qvm-template-upgrade to the tools reference --- user/reference/tools.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/user/reference/tools.rst b/user/reference/tools.rst index e065e5ce9..6cbf0200e 100644 --- a/user/reference/tools.rst +++ b/user/reference/tools.rst @@ -10,6 +10,7 @@ Dom0 - :doc:`core-admin ` - :doc:`core-admin-client ` - `qvm-appmenus `__ +- `qvm-template-upgrade `__ - `qvm-xkill `__ DomU From 01b966bee310ffa00643d117b8e2ced256912e11 Mon Sep 17 00:00:00 2001 From: Nihal <121309701+nihalxkumar@users.noreply.github.com> Date: Thu, 23 Jul 2026 21:37:49 +0000 Subject: [PATCH 2/2] Add guide for automated upgrade with qvm-template-upgrade --- user/templates/debian/debian-upgrade.rst | 14 ++++++++++++++ user/templates/fedora/fedora-upgrade.rst | 14 ++++++++++++++ 2 files changed, 28 insertions(+) diff --git a/user/templates/debian/debian-upgrade.rst b/user/templates/debian/debian-upgrade.rst index 77f6ed60f..298ed372f 100644 --- a/user/templates/debian/debian-upgrade.rst +++ b/user/templates/debian/debian-upgrade.rst @@ -18,6 +18,20 @@ This page provides instructions for performing an in-place upgrade of an install By default, Qubes uses code `names` in the apt sources files (bookworm, trixie, etc), although the templates are referred to by release number. Check the code names for the templates, and ensure you are aware of any changes you have made in the repository definitions. +Automated upgrade with qvm-template-upgrade +------------------------------------------- + + +The `qvm-template-upgrade `__ tool automates the clone-and-upgrade procedure described on this page: it clones the template, upgrades the clone to the next Debian release (including updating the ``apt`` sources to the new release's code name), and sets the ``template-name`` feature used by the Qubes updater. + +.. code:: console + + [user@dom0 ~]$ qvm-template-upgrade --template=debian- + +By default, the clone is named by replacing the release number in the source name, e.g. ``debian-12`` becomes ``debian-13`` and ``debian-12-minimal`` becomes ``debian-13-minimal``. Use ``--new-name=`` to choose a different name, and ``--dry-run`` to preview the planned upgrade without creating a clone. + +After the upgrade completes, remember to :ref:`switch everything that was set to the old template to the new template ` and, optionally, make the new template the global default and uninstall the old template, as described in the manual instructions below. Use the manual instructions if you need finer control over the upgrade process or if the automated upgrade fails. + Summary instructions for Debian templates ----------------------------------------- diff --git a/user/templates/fedora/fedora-upgrade.rst b/user/templates/fedora/fedora-upgrade.rst index c3080b335..629be27c1 100644 --- a/user/templates/fedora/fedora-upgrade.rst +++ b/user/templates/fedora/fedora-upgrade.rst @@ -13,6 +13,20 @@ This page provides instructions for performing an in-place upgrade of an install .. note:: In what follows the prompt on each line indicates where each command should be entered: ``dom0``, ``fedora-``, or ``fedora-``, where ```` is the fedora version number *from* which you are upgrading, and ```` is the fedora version number *to* which you are upgrading. Remember to use the right template *version*: eg clone ``fedora--minimal`` to ``fedora--minimal``. +Automated upgrade with qvm-template-upgrade +------------------------------------------- + + +The `qvm-template-upgrade `__ tool automates the clone-and-upgrade procedure described on this page: it clones the template, upgrades the clone to the next Fedora release, and sets the ``template-name`` feature used by the Qubes updater. + +.. code:: console + + [user@dom0 ~]$ qvm-template-upgrade --template=fedora- + +By default, the clone is named by replacing the release number in the source name, e.g. ``fedora-41`` becomes ``fedora-42`` and ``fedora-41-minimal`` becomes ``fedora-42-minimal``. Use ``--new-name=`` to choose a different name, and ``--dry-run`` to preview the planned upgrade without creating a clone. + +After the upgrade completes, remember to :ref:`switch everything that was set to the old template to the new template ` and, optionally, make the new template the global default and uninstall the old template, as described in the manual instructions below. Use the manual instructions if you need finer control over the upgrade process or if the automated upgrade fails. + Summary instructions for standard Fedora templates --------------------------------------------------