Unified installation guide

Move "Upgrading" and "Known Issues" sections to release notes
This commit is contained in:
Marek Marczykowski-Górecki 2015-09-15 23:39:59 +02:00
parent a4fd4a595a
commit ecd22417a2
No known key found for this signature in database
GPG key ID: F32894BE9684938A
16 changed files with 252 additions and 888 deletions

View file

@ -1,37 +1,43 @@
---
layout: doc
title: InstallationGuide
title: Installation Guide
permalink: /doc/InstallationGuide/
redirect_from: /wiki/InstallationGuide/
redirect_from: /doc/InstallationGuideR1/
redirect_from: /doc/InstallationGuideR2B1/
redirect_from: /doc/InstallationGuideR2B2/
redirect_from: /doc/InstallationGuideR2B3/
redirect_from: /doc/InstallationGuideR2rc1/
redirect_from: /doc/InstallationGuideR2rc2/
redirect_from: /doc/InstallationGuideR3.0rc1/
redirect_from: /doc/InstallationGuideR3.0rc2/
---
Installation Guide (for Qubes Release 1)
Installation Guide
========================================
1. [Hardware Requirements](#HardwareRequirements)
2. [Download installer ISO](#DownloadinstallerISO)
3. [Burning the ISO onto a DVD or USB stick](#BurningtheISOontoaDVDorUSBstick)
4. [Upgrading from Qubes 1.0-rc1](#UpgradingfromQubes1.0-rc1)
5. [Migrating from Qubes Beta 3](#MigratingfromQubesBeta3)
6. [Installing Updates](#InstallingUpdates)
7. [Known Issues](#KnownIssues)
8. [Getting Help](#GettingHelp)
1. [Hardware Requirements](#hardware-requirements)
2. [Download installer ISO](#download-installer-iso)
3. [Burning the ISO onto a DVD or USB stick](#burning-the-iso-onto-a-dvd-or-usb-stick)
4. [Upgrading](#upgrading)
5. [Troubleshooting problems with the installer](#troubleshooting-problems-with-the-installer)
6. [Getting Help](#getting-help)
Hardware Requirements
---------------------
Please see the [Hardware Compatibility List](/hcl/) page for more information on required and recommended hardware.
Note: We don't recommend installing Qubes in a virtual machine! It will likely not work. Don't send emails asking about it.
Note: We don't recommend installing Qubes in a virtual machine! It will likely not work. Don't send emails asking about it. However, you can install it on an external USB hard drive and run from it, at least for testing (normally such disks are *orders* of magnitude slower than even the slowest internal hard drives).
Download installer ISO
----------------------
See [this page](/doc/QubesDownloads/) for ISO downloads. Remember, we have absolutely no control over those servers, and so you should be assuming that they might be compromised, or just be serving a compromised ISOs because their operators decided so for whatever reason. Always verify the digital signature on the downloaded ISO. See this [page](/doc/VerifyingSignatures/) for more info about how to download and verify our GPG keys, and then verify the downloaded ISO:
See [this page](/doc/QubesDownloads/) for ISO downloads. Remember, we have absolutely no control over those servers, and so you should be assuming that they might be compromised, or just be serving a compromised ISOs because their operators decided so, for whatever reason. Always verify the digital signature on the downloaded ISO. See this [page](/doc/VerifyingSignatures/) for more info about how to download and verify our GPG keys, and then verify the downloaded ISO:
{% highlight trac-wiki %}
gpg -v <iso>.asc
{% endhighlight %}
gpg -v Qubes-R2-x86_64-DVD.iso.asc
Adjust filename to the version you're installing.
Burning the ISO onto a DVD or USB stick
---------------------------------------
@ -40,11 +46,15 @@ Once you verify this is an authentic ISO, you should burn it on a DVD.
If you prefer to use USB as a source for installation, then you just need to copy the ISO onto the USB device, e.g. using dd:
{% highlight trac-wiki %}
dd if=Qubes-R1-x86_64-DVD.iso of=/dev/sdX
{% endhighlight %}
dd if=Qubes-R2-x86_64-DVD.iso of=/dev/sdX
**Be sure to use a correct device as the target in the dd command above (instead of sdX)'''**
Adjust filename to the version you're installing. **Be sure to use a correct device as the target in the dd command above (instead of sdX)'''**
On windows you can use [this](http://www.chrysocome.net/dd) tool. Example command would be (as Administrator):
dd if=Qubes-R2-x86_64-DVD.iso of=\\?\Device\Harddisk1\Partition0 bs=1M --size --progress
Adjust filename to the version you're installing. **Be sure to use a correct device as the target in the dd command above (instead of sdX or Harddisk1)**
Before proceeding with the installation, you are encouraged to first read all the information on this page, especially the *Known Issues* paragraph.
@ -52,45 +62,12 @@ Then, when finally ready, boot your system from the installer DVD and follow the
The installer loads Xen right at the beginning, so chances are high that if you can see the installer's graphical screen, Qubes will work on your system :)
Upgrading from Qubes 1.0-rc1
----------------------------
Upgrading
---------
If you're already running Qubes 1.0-rc1, you don't need to reinstall, it's just enough to update the packages in your Dom0 and the template VM(s). The easiest way for doing this is to click on the Update Button in the Qubes Manger -- one click when you selected Dom0, and one click for each of your template VM (by default there is just one template).
See [release notes](/doc/releases/) of appropriate version.
Migrating from Qubes Beta 3
---------------------------
If you have Qubes Beta 3 currently installed on your system, you must reinstall from scratch, as we offer no direct upgrade option in the installer (sorry). However, we do offer tools for smooth migration of your AppVMs. In order to do that, please backup your AppVMs using the `qvm-backup` tool [as usual](/doc/BackupRestore/). Then, after you install Qubes 1.0 rc1, you can restore them using `qvm-backup-restore` tool. However, because we have changed the default template in RC1, you should tell qvm-back-restore about that by passing `--replace-template` option:
{% highlight trac-wiki %}
qvm-backup-restore <backup_dir> --replace-template=fedora-15-x64:fedora-17-x64
{% endhighlight %}
Installing Updates
------------------
Installing updates is very easy and can be done using the "Update" button in the Qubes Manager. Alternatively it can also be done from command prompt -- see the following for more details:
- For installing updates for Dom0 -- see instructions [here](/doc/SoftwareUpdateDom0/).
- For installing updates for you domains (VMs) -- see instructions [here](/doc/SoftwareUpdateVM/).
Known Issues
------------
- Installer might not support some USB keyboards (\#230). This seems to include all the Mac Book keyboards (most PC laptops have PS2 keyboards and are not affected).
- If you don't enable Composition (System Setting -\> Desktop -\> Enable desktop effects), which you really should do, then the KDE task bar might get somehow ugly (e.g. half of it might be black). This is some KDE bug that we don't plan to fix.
- Some keyboard layout set by KDE System Settings can cause [keyboard not working at all](https://groups.google.com/group/qubes-devel/browse_thread/thread/77d076b65dda7226). If you hit this issue, you can switch to console (by console login option) and manually edit `/etc/X11/xorg.conf.d/00-system-setup-keyboard.conf` (and `/etc/sysconfig/keyboard`) and place correct keyboard layout settings (details in linked thread). You can check if specific keyboard layout settings are proper using `setxkbmap` tool.
- On systems with more than 8GB of RAM there is problem with Disposable VM. To fix it, limit maximum memory allocation for DispVM to 3GB
{% highlight trac-wiki %}
qvm-prefs -s fedora-17-x64-dvm maxmem 3072
qvm-create-default-dvm --default-template --default-script
{% endhighlight %}
- On some systems the KDE Window Manager might freeze upon resuming from S3 sleep when compositing is enabled (and the only method to log in to the system if this happens is to switch to a text console, enter your user's password, kill the kwin process, go back to the Xorg console, log in, and start a new instance of kwin using Konsole application :) If you experience such problems, make sure to disable compositing before putting the system into sleep by pressing Alt-Ctrl-F12 (and then enabling it back once you log in after resume) -- this way you should never see this problem again.
Getting Help
------------
@ -99,7 +76,8 @@ Getting Help
- Developers documentation (normally not needed by users) is [here](/doc/SystemDoc/)
- If you don't find answer in the sources given above, write to the *qubes-devel* mailing list:
- [http://groups.google.com/group/qubes-devel](http://groups.google.com/group/qubes-devel)
- `qubes-devel@googlegroups.com`
- If you don't find answer in the sources given above, write to the *qubes-users* mailing list (you don't need to be subscribed to the list, just send email to the address given below):
- [https://groups.google.com/group/qubes-users](https://groups.google.com/group/qubes-users)
- `qubes-users@googlegroups.com`
- Please do not write email to individual developers (Marek, Joanna, etc) asking questions about installation or other problems. Please send all such questions to the mailing list.