Merge branch 'rst' into toki_fix_findings

This commit is contained in:
Tobias Killer 2025-08-23 11:05:37 +02:00
commit 140789e7fc
21 changed files with 540 additions and 12 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 134 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 82 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 58 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 365 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 189 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 30 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 197 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 100 KiB

0
attachment/doc/r4.1-converting-pdf.png Executable file → Normal file
View file

Before

Width:  |  Height:  |  Size: 84 KiB

After

Width:  |  Height:  |  Size: 84 KiB

Before After
Before After

0
attachment/doc/r4.1-dom0-appmenu-select.png Executable file → Normal file
View file

Before

Width:  |  Height:  |  Size: 71 KiB

After

Width:  |  Height:  |  Size: 71 KiB

Before After
Before After

0
attachment/doc/r4.1-snapshot_40.png Executable file → Normal file
View file

Before

Width:  |  Height:  |  Size: 450 KiB

After

Width:  |  Height:  |  Size: 450 KiB

Before After
Before After

View file

@ -0,0 +1,347 @@
==========================
Qubes OS 4.3 release notes
==========================
Major features and improvements since Qubes 4.2
===============================================
- Dom0 upgraded to Fedora 41
(`#9402 <https://github.com/QubesOS/qubes-issues/issues/9402>`__).
- Xen upgraded to version 4.19
(`#9420 <https://github.com/QubesOS/qubes-issues/issues/9420>`__).
- Default Fedora template upgraded to Fedora 42 (Fedora TemplateVMs and
StandaloneVMs with version lower than 41 are not supported).
- Default Debian template upgraded to Debian 13 (Debian TemplateVMs and
StandaloneVMs with version lower than 12 are not supported).
- Default Whonix templates upgraded to Whonix 17.4.3 (Whonix TemplateVMs
and StandaloneVMs with version lower than 17 are not supported).
- Preloaded disposables
(`#1512 <https://github.com/QubesOS/qubes-issues/issues/1512>`__,
`#9907 <https://github.com/QubesOS/qubes-issues/issues/9907>`__,
`#9917 <https://github.com/QubesOS/qubes-issues/issues/9917>`__,
`#9918 <https://github.com/QubesOS/qubes-issues/issues/9918>`__ &
`#10026 <https://github.com/QubesOS/qubes-issues/issues/10026>`__).
- Device “self-identity oriented” assignment (a.k.a New Devices API)
(`#9325 <https://github.com/QubesOS/qubes-issues/issues/9325>`__).
- QWT (Qubes Windows Tools) reintroduction with improved features
(`#1861 <https://github.com/QubesOS/qubes-issues/issues/1861>`__).
|Screenshot of QWT, Welcome page|
|Screenshot of QWT, Windows 11|
UI/UX
-----
- New Device UX workflow to allow users easy utilization of new Devices API.
A dedicated ``Device Assignments`` page is added to Global Config.
Qubes Devices widget is completely redesigned.
(`#8537 <https://github.com/QubesOS/qubes-issues/issues/8537>`__).
|Screenshot of Device UX assignments|
|Screenshot of Device UX deny attachment|
|Screenshot of Device UX edit assignment|
|Screenshot of Device UX required devices|
|Screenshot of Device UX Qubes Devices widget|
- New and improved flat icons for GUI tools
(`#5657 <https://github.com/QubesOS/qubes-issues/issues/5657>`__).
|Screenshot of Qube Manager|
- The far left icons from the Qube Manager are removed
(`#9776 <https://github.com/QubesOS/qubes-issues/issues/9776>`__).
- Application icons are available in VM Settings
(`#9829 <https://github.com/QubesOS/qubes-issues/issues/9829>`__).
|Screenshot of Qube Settings Applications|
- Option to add Qubes video Companion to AppMenu
(`#9761 <https://github.com/QubesOS/qubes-issues/issues/9761>`__).
- Improved AppMenu navigation with keyboard
(`#9006 <https://github.com/QubesOS/qubes-issues/issues/9006>`__).
- Better wording to clarify updater settings and actions
(`#8096 <https://github.com/QubesOS/qubes-issues/issues/8096>`__).
- Centralized Tray Notifications
(`#889 <https://github.com/QubesOS/qubes-issues/issues/889>`__).
- Option to launch root terminal or console terminal from Qubes Domains widget
(`#9788 <https://github.com/QubesOS/qubes-issues/issues/9788>`__)
- Option to open Global Config at a selected section for user
convenience
(`#9530 <https://github.com/QubesOS/qubes-issues/issues/9530>`__).
- A ``Saving changes...`` dialog is added to Global Config
(`#9926 <https://github.com/QubesOS/qubes-issues/issues/9926>`__).
GUI Daemon/Agent improvements
-----------------------------
- Allowing the GUI Daemon background color to be configurable, mostly
useful for people with dark themes
(`#9304 <https://github.com/QubesOS/qubes-issues/issues/9304>`__).
- Audio daemon does not connect to recording stream unless recording is
explicitly enabled
(`#9999 <https://github.com/QubesOS/qubes-issues/issues/9999>`__).
- Legacy X11 App icons (e.g. Xterm) are properly displayed
(`#9973 <https://github.com/QubesOS/qubes-issues/issues/9973>`__).
- Labeling virtual pointing device as absolute and not relative
(`#228 <https://github.com/QubesOS/qubes-issues/issues/228>`__).
- Improved global clipboard notifications & configurable global clipboard size
(`#9296 <https://github.com/QubesOS/qubes-issues/issues/9296>`__ &
`#9978 <https://github.com/QubesOS/qubes-issues/issues/9978>`__).
- Supporting Windows qubes in systems with ``sys-gui*``
(`#7565 <https://github.com/QubesOS/qubes-issues/issues/7565>`__).
Hardware support improvements
-----------------------------
- Support for `Advanced Format
(AF) <https://en.wikipedia.org/wiki/Advanced_Format>`__ drives better known
as 4K sector
(`#4974 <https://github.com/QubesOS/qubes-issues/issues/4974>`__).
- Replacing bus/slot/function with full PCI paths for device assignments
(`#8681 <https://github.com/QubesOS/qubes-issues/issues/8681>`__
& `#8127 <https://github.com/QubesOS/qubes-issues/issues/8127>`__).
- Ability to filter input devices with udev rules.
(`#3604 <https://github.com/QubesOS/qubes-issues/issues/3604>`__).
- Fix for graceful rebooting on some (U)EFI systems with buggy firmware
(`#6258 <https://github.com/QubesOS/qubes-issues/issues/6258>`__).
- Better support for Bluetooth and external hot-pluggable audio devices
with dynamic AudioVM switching
(`#7750 <https://github.com/QubesOS/qubes-issues/issues/7750>`__).
Security features
-----------------
- Templates could request custom kernel command line parameters;
currently used for Kicksecure and Whonix templates ``user-sysmaint-split``
(`#9750 <https://github.com/QubesOS/qubes-issues/issues/9750>`__).
- Allow VMs to specify boot modes as being only intended for AppVMs or
templates
(`#9920 <https://github.com/QubesOS/qubes-issues/issues/9920>`__).
- Shipping GRUB2 from Fedora with all security patches and Bootloader
Specification support
(`#9471 <https://github.com/QubesOS/qubes-issues/issues/9471>`__).
- SSL client certificate and GPG key support for private template repositories
(`#9850 <https://github.com/QubesOS/qubes-issues/issues/9850>`__).
- Preventing unsafe practice of 3rd party template installation with rpm/dnf
(`#9943 <https://github.com/QubesOS/qubes-issues/issues/9943>`__).
- Ability to prohibit start of specific qubes
(`#9622 <https://github.com/QubesOS/qubes-issues/issues/9622>`__).
- UUID support for qubes and support for addressing them by UUID in policies
(`#8862 <https://github.com/QubesOS/qubes-issues/issues/8862>`__ &
`#8510 <https://github.com/QubesOS/qubes-issues/issues/8510>`__).
- Custom persist feature to avoid unwanted data to persist as much as possible
(`#1006 <https://github.com/QubesOS/qubes-issues/issues/1006>`__).
Anonymity improvements
----------------------
- Disallowing files, URLs, or any application from Whonix-Workstation
qubes to be opened in non-Whonix disposable
(`#10051 <https://github.com/QubesOS/qubes-issues/issues/10051>`__).
- Preventing users from changing their Whonix Workstation qubes netvm
to ``sys-firewall`` (or other clearnet netvms) to avoid IP leaks
(`#8551 <https://github.com/QubesOS/qubes-issues/issues/8551>`__).
- kloak: Keystroke-level online anonymization kernel
(`#1850 <https://github.com/QubesOS/qubes-issues/issues/1850>`__).
Performance optimizations
-------------------------
- Option to use volumes directly without snapshots
(`#8767 <https://github.com/QubesOS/qubes-issues/issues/8767>`__).
- Retiring ``qubes-rpc-multiplexer`` and directly executing the command from c
(`#9062 <https://github.com/QubesOS/qubes-issues/issues/9062>`__).
- Caching "system info" structure for qrexec policy evaluation
(`#9362 <https://github.com/QubesOS/qubes-issues/issues/9362>`__).
- Minimal state qubes to make NetVM and USBVM to consume as little RAM as
possible.
Updating & upgrading
--------------------
- Ability to always hide specific TemplateVMs and StandaloneVMs from
update tools
(`#9029 <https://github.com/QubesOS/qubes-issues/issues/9029>`__).
- pacman hook to notify dom0 about successful manual Archlinux upgrades
(`#9233 <https://github.com/QubesOS/qubes-issues/issues/8307>`__),
- Improved R4.2 -> R4.3 upgrade tool
(`#9317 <https://github.com/QubesOS/qubes-issues/issues/9317>`__),
- Using `lvmdevices` feature instead of device filter
(`#9421 <https://github.com/QubesOS/qubes-issues/issues/9421>`__).
New/Improved experimental features
----------------------------------
- Support for Ansible
(`#10004 <https://github.com/QubesOS/qubes-issues/issues/10004>`__).
- Support for `Qubes
Air <https://www.qubes-os.org/news/2018/01/22/qubes-air/>`__
(`#9015 <https://github.com/QubesOS/qubes-issues/issues/9015>`__).
- qrexec protocol extension to support sending source information to
destination
(`#9475 <https://github.com/QubesOS/qubes-issues/issues/9475>`__).
- Better support for GUIVM.
- GUI/Admin domain splitting
(`#833 <https://github.com/QubesOS/qubes-issues/issues/833>`__).
- Automatically removing nomodeset boot option when GPU is attached
(`#9792 <https://github.com/QubesOS/qubes-issues/issues/9792>`__).
- Initial basic steps to support Wayland session only in GUIVM (but not GUI
daemon/agent intra-communication)
(`#8515 <https://github.com/QubesOS/qubes-issues/issues/8515>`__ &
`#8410 <https://github.com/QubesOS/qubes-issues/issues/8410>`__).
Other
-----
- Allowing user to add free-form text to qubes (for descriptions, notes,
comments, remarks, reminders, etc.)
(`#899 <https://github.com/QubesOS/qubes-issues/issues/899>`__).
|Screenshot of Qube Settings Notes|
- Automatically clean up `QubesIncoming` directory if empty
(`#8307 <https://github.com/QubesOS/qubes-issues/issues/8307>`__).
- ``vm-config.*`` features to pass external configuration to inside the qube
(`#9837 <https://github.com/QubesOS/qubes-issues/issues/9837>`__).
- Admin API for reading/writing denied device-interface list
(`#9674 <https://github.com/QubesOS/qubes-issues/issues/9674>`__).
- New Devices API for salt
(`#9753 <https://github.com/QubesOS/qubes-issues/issues/9753>`__).
- IPv6 DNS support for full IPv4-less environments
(`#10038 <https://github.com/QubesOS/qubes-issues/issues/10038>`__).
Dropped or replaced features
----------------------------
- Default screen locker is changed from ``XScreenSaver`` to
``xfce4-screensaver``
- ``Create Qubes VM`` is retired in favor of the improved ``Create New Qube``
(`#6561 <https://github.com/QubesOS/qubes-issues/issues/6561>`__).
- Windows 7 support is dropped from QWT.
For a full list, including more detailed descriptions, please see
`here <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue%20label%3Atargets-4.3>`__.
Known issues
============
- Templates restored in 4.3 from a pre-4.3 backup continue to target
their original Qubes OS release repos. If you are using fresh
templates on a clean 4.3 installation, or if you performed an
:ref:`in-place upgrade from 4.2 to 4.3 <user/downloading-installing-upgrading/upgrade/4_3:in-place upgrade>`,
then this does not affect you. (For more information, see issue
`#8701 <https://github.com/QubesOS/qubes-issues/issues/8701>`__.)
Also see the `full list of open bug reports affecting Qubes
4.3 <https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+label%3Aaffects-4.3+label%3A%22T%3A+bug%22+is%3Aopen>`__.
We strongly recommend :doc:`updating Qubes OS </user/how-to-guides/how-to-update>`
immediately after installation in order to apply all available bug fixes.
Notes
=====
- Additional notes for future release candidates will be added here
Download
========
All Qubes ISOs and associated :doc:`verification files </project-security/verifying-signatures>`
are available on the `downloads <https://www.qubes-os.org/downloads/>`__ page.
Installation instructions
=========================
See the :doc:`installation guide </user/downloading-installing-upgrading/installation-guide>`.
Upgrading
=========
Please see :doc:`how to upgrade to Qubes 4.3 </user/downloading-installing-upgrading/upgrade/4_3>`.
.. |Screenshot of QWT, Welcome page| image:: /attachment/doc/4-3_qwt-hi.png
:alt: Windows 11 welcome page after installation in an HVM
.. |Screenshot of QWT, Windows 11| image:: /attachment/doc/4-3_qwt-win11.png
:alt: Windows 11 within an HVM qube showing file explorer
.. |Screenshot of Device UX assignments| image:: /attachment/doc/4-3_device-ux-assignments.png
:alt: Device Assignments page in Global Config
.. |Screenshot of Device UX deny attachment| image:: /attachment/doc/4-3_device-ux-deny-attachment.png
:alt: Deny device attachment config in Global Config
.. |Screenshot of Device UX edit assignment| image:: /attachment/doc/4-3_device-ux-edit-assignment.png
:alt: Editing device assignment for a network interface in Global Config
.. |Screenshot of Device UX required devices| image:: /attachment/doc/4-3_device-ux-required-device.png
:alt: Editing a required device in Global Config
.. |Screenshot of Device UX Qubes Devices widget| image:: /attachment/doc/4-3_qui-devices.png
:alt: Redesigned Qubes Devices widget
.. |Screenshot of Qube Manager| image:: /attachment/doc/4-3_manager.png
:alt: Qube Manager with improved flat icons
.. |Screenshot of Qube Settings Applications| image:: /attachment/doc/4-3_vmsettings-applications.png
:alt: Qube settings showing icons of Apps
.. |Screenshot of Qube Settings Notes| image:: /attachment/doc/4-3_notes.png
:alt: Qube settings showing qube notes

View file

@ -0,0 +1,20 @@
===========================
Qubes R4.3 release schedule
===========================
**Please note:** *This page is still an unfinished draft in progress. It is being updated as Qubes 4.3 development and testing continues.*
The table below is based on our :ref:`release schedule policy <developer/releases/version-scheme:release schedule>`.
.. list-table::
:widths: 10 10
:align: center
:header-rows: 1
* - Date
- Stage
* - TBD
- 4.3.0-rc1 release

View file

@ -22,4 +22,6 @@ Release notes
Qubes R4.2 release notes </developer/releases/4_2/release-notes> Qubes R4.2 release notes </developer/releases/4_2/release-notes>
Qubes R4.3 release notes </developer/releases/4_3/release-notes>

View file

@ -18,4 +18,6 @@ Release schedules
Qubes R4.2 release schedule </developer/releases/4_2/schedule> Qubes R4.2 release schedule </developer/releases/4_2/schedule>
Qubes R4.3 release schedule </developer/releases/4_3/schedule>

View file

@ -47,13 +47,15 @@ Great! Thank you for taking the time and effort to help improve Qubes! To ensure
6. Do not delete the provided issue template. Fill out every applicable section. 6. Do not delete the provided issue template. Fill out every applicable section.
7. Make sure to mention any relevant documentation and other issues youve already seen. We dont know what youve seen unless you tell us. If you dont list it, well assume you havent seen it. 7. Please note that AIs often `hallucinate <https://en.wikipedia.org/wiki/Hallucination_(artificial_intelligence)>`__ about Qubes OS. If you're using an AI to assist you, please check its conclusions against the `official documentation <https://doc.qubes-os.org/>`__.
8. If any sections of the issue template are *truly* not applicable, you may remove them. 8. Make sure to mention any relevant documentation and other issues youve already seen. We dont know what youve seen unless you tell us. If you dont list it, well assume you havent seen it.
9. Submit your issue. 9. If any sections of the issue template are *truly* not applicable, you may remove them.
10. Respond to any questions the official team asks. For example, you may be asked to provide specific logs or other additional information. 10. Submit your issue.
11. Respond to any questions the official team asks. For example, you may be asked to provide specific logs or other additional information.
@ -171,18 +173,23 @@ If your issue is not actionable, please see :doc:`Help, Support, Mailing Lists,
This guideline is extremely important for making the issue tracker a useful tool for the developers. When an issue is too big and composite, it becomes intractable and drastically increases the likelihood that nothing will get done. Such issues also tend to encourage an excessive amount of general discussion that is simply not appropriate for a technical issue tracker (see `the issue tracker is not a discussion forum <#the-issue-tracker-is-not-a-discussion-forum>`__). This guideline is extremely important for making the issue tracker a useful tool for the developers. When an issue is too big and composite, it becomes intractable and drastically increases the likelihood that nothing will get done. Such issues also tend to encourage an excessive amount of general discussion that is simply not appropriate for a technical issue tracker (see `the issue tracker is not a discussion forum <#the-issue-tracker-is-not-a-discussion-forum>`__).
New issues should not be duplicates of existing issues
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Before you submit an issue, check to see whether it has already been reported. Search through the existing issues both open and closed by typing your key words in the **Filters** box. If you find an issue that seems to be similar to yours, read through it. If you find an issue that is the same as or subsumes yours, leave a comment on the existing issue rather than filing a new one, even if the existing issue is closed. If an issue affects more than one Qubes version, we usually keep only one issue for all versions. The Qubes team will see your comment and reopen the issue, if appropriate. For example, you can leave a comment with additional information to help the maintainer debug it. Adding a comment will subscribe you to email notifications, which can be helpful in getting important updates regarding the issue. If you dont have anything to add but still want to receive email updates, you can click the “Subscribe” button at the side or bottom of the comments.
Every issue must be of a single type Every issue must be of a single type
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Every issue must be exactly one of the following types: a bug report (``bug``), a feature or improvement request (``enhancement``), or a task (``task``). Do not file multi-typed issues. Instead, file multiple issues of distinct types. The Qubes team will classify your issue according to its type. Every issue must be exactly one of the following types: a bug report (``bug``), a feature or improvement request (``enhancement``), or a task (``task``). Do not file multi-typed issues. Instead, file multiple issues of distinct types. The Qubes team will classify your issue according to its type.
New issues should not be duplicates of existing issues
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Before you submit an issue, check to see whether it has already been reported. Search through the existing issues both open and closed by typing your key words in the **Filters** box. If you find an issue that seems to be similar to yours, read through it.
For bug reports, if you find an issue that is the same as or subsumes yours, leave a comment on the existing bug report issue rather than opening a new one, even if the existing bug report is closed. If a bug report affects more than one Qubes version, we usually keep only one bug report for all versions. The Qubes team will see your comment and reopen the bug report, if appropriate. For example, you can leave a comment with additional information to help the maintainer debug it. Adding a comment will subscribe you to email notifications, which can be helpful in getting important updates regarding the issue. If you dont have anything to add but still want to receive email updates, you can click the “Subscribe” button at the side or bottom of the comments.
For feature requests, it depends on what you want to report. If the initial implementation was incomplete or unsuccessful, then please leave a comment on the existing feature request issue, and we will reopen it. However, if the initial implementation of the feature was successful, and you are reporting a problem with the feature that arose later, then please open a separate bug report (if one doesn't already exist for that bug) instead of commenting on the old feature request, as we generally prefer not to reopen old feature requests the initial implemntation of which was successfully completed.
New issues should include all relevant information New issues should include all relevant information
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

View file

@ -55,7 +55,7 @@ Qubes OS releases are supported for **six months** after each subsequent major o
* - Release 4.3 * - Release 4.3
- TBD - TBD
- TBD - TBD
- In development - In testing
@ -94,6 +94,8 @@ The table below shows the OS used for dom0 in each Qubes OS release.
- Fedora 32 - Fedora 32
* - Release 4.2 * - Release 4.2
- Fedora 37 - Fedora 37
* - Release 4.3
- Fedora 41
@ -120,8 +122,11 @@ It is the responsibility of each distribution to clearly notify its users in adv
- Fedora - Fedora
- Debian - Debian
* - Release 4.2 * - Release 4.2
- 41 - 41, 42
- 12 - 12
* - Release 4.3
- 41, 42
- 12, 13

View file

@ -0,0 +1,143 @@
===========================
How to upgrade to Qubes 4.3
===========================
This page explains how to upgrade from Qubes 4.2 to Qubes 4.3. 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 dont 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 qubes are in their latest version.
2. Create a :ref:`backup <user/how-to-guides/how-to-back-up-restore-and-migrate:creating a backup>` of your current installation.
3. `Download <https://www.qubes-os.org/downloads/>`__ the latest 4.3 release.
4. Follow the :doc:`installation guide </user/downloading-installing-upgrading/installation-guide>` to install Qubes 4.3.
5. :ref:`Restore from your backup <user/how-to-guides/how-to-back-up-restore-and-migrate:restoring from a backup>` on your new 4.3 installation.
6. Install the ``qubes-dist-upgrade`` tool. This is the inplace upgrade tool, which is not what were doing. However it will be needed in order to upgrade the templates to the 4.3 version. You install it with the following command in the dom0 terminal:
.. code:: bash
sudo qubes-dom0-update -y qubes-dist-upgrade
7. Change your templates to use the 4.3 repositories instead of the 4.2 ones. You do this with the following command in the dom0 terminal:
.. code:: bash
sudo qubes-dist-upgrade --releasever=4.3 --template-standalone-upgrade
**Note**: This step is critical to ensure the templates will receive updates once Qubes 4.2 reaches end-of-life (EOL).
In-place upgrade
----------------
**Warning:** It is not possible to upgrade directly from releases earlier than 4.2. If youre still on an earlier release, please either perform a `clean installation of 4.3 <#clean-installation>`__ or :doc:`upgrade to 4.2 </user/downloading-installing-upgrading/upgrade/4_2>` 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 --releasever=4.3 --help``:
.. code:: bash
Usage: qubes-dist-upgrade --releasever=VERSION [OPTIONS]...
This script is used for updating QubesOS to the next release.
Options:
--releasever=VERSION Specify target release, for example 4.3 or 4.2.
Usage: /usr/lib/qubes/qubes-dist-upgrade-r4.3.sh [OPTIONS]...
This script is used for updating current QubesOS R4.2 to R4.3.
Options:
--update, -t (STAGE 1) Update of dom0, TemplatesVM and StandaloneVM.
--release-upgrade, -r (STAGE 2) Update 'qubes-release' for Qubes R4.3.
--dist-upgrade, -s (STAGE 3) Upgrade to Qubes R4.3 and Fedora 41 repositories.
--template-standalone-upgrade, -l (STAGE 4) Upgrade templates and standalone VMs to R4.3 repository.
--finalize, -x (STAGE 5) Finalize upgrade. It does:
- resync applications and features
- create LVM devices cache
- update PCI device IDs
- enable minimal-netvm / minimal-usbvm services
- cleanup salt states
- enable preloaded disposables if system has more than 16GB memory
--check-supported-templates (STAGE 6) Check if all templates are supported
--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.3 repositories.
--skip-standalone-upgrade, -k Don't upgrade StandaloneVM to R4.3 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).
--enable-current-testing, -e Enable current-testing repositories for the update time.
The enabling with this option do not persist after
successful update. If you want to keep it enabled,
use the normal method instead.
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, its recommended to restart the system one last time.
When this completes, you can start using Qubes OS 4.3.
Update
------
After upgrading or performing a clean installation, we strongly recommend :doc:`updating your system </user/how-to-guides/how-to-update>`.

View file

@ -28,4 +28,6 @@ These guides are for upgrading from one version of Qubes to another. If youre
Upgrade from 4.1 to 4.2 </user/downloading-installing-upgrading/upgrade/4_2> Upgrade from 4.1 to 4.2 </user/downloading-installing-upgrading/upgrade/4_2>
Upgrade from 4.2 to 4.3 </user/downloading-installing-upgrading/upgrade/4_3>