R3.1 release notes and upgrade instruction

This commit is contained in:
Marek Marczykowski-Górecki 2015-11-29 22:55:20 +01:00
parent ed0942c7a5
commit 79fb0fe2ea
No known key found for this signature in database
GPG Key ID: F32894BE9684938A
2 changed files with 170 additions and 0 deletions

View File

@ -0,0 +1,96 @@
---
layout: doc
title: Upgrading to R3.1
permalink: /doc/upgrade-to-r3.1/
redirect_from:
- /en/doc/upgrade-to-r3.1/
- /doc/UpgradeToR3.1/
- /doc/UpgradeToR3.1rc1/
---
Upgrading Qubes R3.0 to R3.1
======================================
Current Qubes R3.1 (R3.1) systems can be upgraded in-place to the latest R3.1
by following the procedure below.
**Before attempting either an in-place upgrade or a clean installation, we
strongly recommend that users back up the system by using the built-in [backup
tool](/doc/backup-restore/).**
Upgrade all Template and Standalone VM(s)
-----------------------------------------
By default, in Qubes R3.0, there is only one Template VM, however users are
free to create more Template VMs for special purposes, as well as Standalone
VMs. More information on using multiple Template VMs, as well as Standalone
VMs, can be found [here](/doc/software-update-vm/). The steps described in this
section should be repeated in **all** user's Template and Standalone VMs.
### Upgrade Fedora template:
1. Open terminal in the template VM (or standalone VM). E.g. use the Qubes
Manager's right-click menu and choose Run Command in VM and type
`gnome-terminal` there.
2. Install `qubes-upgrade-vm` package:
sudo yum install qubes-upgrade-vm
3. Proceed with normal update in the template:
sudo yum update
4. Shutdown the template VM.
### Upgrade Debian template:
1. Open terminal in the template VM (or standalone VM). E.g. use the Qubes
Manager's right-click menu and choose Run Command in VM and type
`gnome-terminal` there.
2. Update repository definition:
sudo cp /etc/apt/sources.list.d/qubes-r3.list /etc/apt/sources.list.d/qubes-r3-upgrade.list
sudo sed -i 's/r3.0/r3.1/' /etc/apt/sources.list.d/qubes-r3-upgrade.list
3. Proceed with normal update in the template:
sudo apt-get update
sudo apt-get dist-upgrade
There will be some error messages during the process, but our tests does
not revealed any negative consequences.
4. Shutdown the template VM.
Upgrading dom0
--------------
Be sure to do steps described in this section after *all* your template and
standalone VMs got updated as described in the section above. Also make sure
you haven't shutdown any of: netvm, firewallvm - you will not be able to start
them again.
1. Open terminal in Dom0. E.g. Start-\>System Settings-\>Konsole.
2. Upgrade dom0 to R3.1:
sudo qubes-dom0-update --releasever=3.1
3. If above step completed successfully you should have `qubes-core-dom0` at
least 3.1.4. If not, repeat above step with additional `--clean` option.
4. Reboot the system.
It may happen that the system hang during the reboot. Hard reset the system
in such case, all the filesystems are unmounted at this stage.
Please note that if you use Anti Evil Maid, then it won't be able to unseal the
passphrase this time, because the Xen, kernel, and initramfs binaries have
changed. Once the system boots up again, you could reseal your Anti Evil Maid's
passphrase to the new configuration. Please consult Anti Evil Maid
documentation for explanation on how to do that.
Now, when you have dom0 upgraded, you can install new templates from Qubes R3.1
repositories. Especially Fedora 23 - default Qubes R3.1 template:
sudo qubes-dom0-update qubes-template-fedora-23

View File

@ -0,0 +1,74 @@
---
layout: doc
title: Qubes R3.1 release notes
permalink: /doc/releases/3.1/release-notes/
---
Qubes R3.1 release notes
========================
*this page is a draft for yet unreleased version*
New features since 3.0
----------------------
* Management Stack based of Salt Stack in dom0 - [documentation][salt-doc]
* Out of the box Whonix setup
* UEFI support
* LIVE edition (still alpha, not part of R3.0-rc1)
* Updated GPU drivers in dom0
* Colorful window application icons (instead of just colorful lock icon)
* PV Grub support ([documentation][pvgrub-doc])
* Out of the box USB VM setup, including [handling USB mouse][input-proxy]
* Xen upgraded to 4.6, for better hardware support (especially Skylake platform)
* Improve updates proxy flexibility - especially repositories served over HTTPS
You can get detailed description in [completed github issues][github-release-notes]
Known issues
------------
* Windows Tools: `qvm-block` does not work
* Some icons in the Qubes Manager application might not be drawn correctly when using the Xfce4 environment in Dom0. If this bothers you, please use the KDE environment instead.
* For other known issues take a look at [our tickets](https://github.com/QubesOS/qubes-issues/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.1%22+label%3Abug)
It is advised to install updates just after system installation to apply bug fixes for (some of) the above problems.
Downloads
---------
See [Qubes Downloads](/downloads/).
Installation instructions
-------------------------
See [Installation Guide](/doc/installation-guide/).
Upgrading
---------
### From R3.0
The easiest and safest way to upgrade to Qubes R3.1 is to install it from
scratch and use [qubes backup and restore tools](/doc/backup-restore/) for
migrating of all of the user VMs.
Users of Qubes R3.0 can upgrade using [experimental
procedure](/doc/upgrade-to-r3.1/).
### From R2 or earlier
When upgrading from earlier versions the easiest and safest way is to install
it from scratch and use [qubes backup and restore tools](/doc/backup-restore/)
for migrating of all of the user VMs.
Alternatively you can [upgrade to R3.0
using](/doc/releases/3.0/release-notes/#upgrading) first, then follow the
instructions above. This will be time consuming process.
[salt-doc]: /doc/salt/
[pvgrub-doc]: /doc/managing-vm-kernel/#tocAnchor-1-3
[input-proxy]: https://github.com/QubesOS/qubes-app-linux-input-proxy/blob/master/README.md
[github-release-notes]: https://github.com/QubesOS/qubes-issues/issues?q=is%3Aissue+sort%3Aupdated-desc+milestone%3A%22Release+3.1%22+label%3Arelease-notes+is%3Aclosed