mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2025-12-10 21:49:07 -05:00
Merge branch 'master' into vm-troubleshooting
This commit is contained in:
Enjeck Cleopatra
GitHub
commit
23c0523810
79 changed files with 2123 additions and 1204 deletions
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Upgrading Debian TemplateVMs
|
||||
title: In-place upgrade of Debian TemplateVMs
|
||||
permalink: /doc/template/debian/upgrade/
|
||||
redirect_from:
|
||||
- /doc/template/debian/upgrade-8-to-9/
|
||||
|
|
@ -13,7 +13,7 @@ redirect_from:
|
|||
# Upgrading Debian TemplateVMs
|
||||
|
||||
This page provides instructions for performing an in-place upgrade of an installed [Debian TemplateVM].
|
||||
If you wish to install a new, unmodified Debian TemplateVM instead of upgrading a template that is already installed in your system, please see the [Debian TemplateVM] page instead.
|
||||
If you wish to install a new, unmodified Debian TemplateVM instead of upgrading a template that is already installed in your system, please see the [Debian TemplateVM] page instead. ([Learn more about the two options.][Debian TemplateVM Upgrade])
|
||||
|
||||
In general, upgrading a Debian TemplateVM follows the same process as [upgrading a native Debian system][upgrade].
|
||||
|
||||
|
|
@ -152,6 +152,7 @@ We strongly recommend against using any Debian release that has reached [end-of-
|
|||
|
||||
|
||||
[Debian TemplateVM]: /doc/templates/debian/
|
||||
[Debian TemplateVM Upgrade]: /doc/templates/debian/#upgrading
|
||||
[upgrade]: https://wiki.debian.org/DebianUpgrade
|
||||
[switch]: /doc/templates/#switching
|
||||
[jessie]: https://www.debian.org/releases/jessie/amd64/release-notes/ch-upgrading.en.html
|
||||
|
|
|
|||
|
|
@ -41,12 +41,16 @@ After installing a fresh Debian TemplateVM, we recommend performing the followin
|
|||
|
||||
## Updating
|
||||
|
||||
Please see [Updating software in TemplateVMs].
|
||||
For routine daily TemplateVM updates within a given Debian release, see [Updating software in TemplateVMs].
|
||||
|
||||
|
||||
## Upgrading
|
||||
|
||||
Please see [Upgrading Debian TemplateVMs].
|
||||
There are two ways to upgrade your TemplateVM to a new Debian release:
|
||||
|
||||
- [Install a fresh template to replace the existing one.](#installing) This option may be simpler for less experienced users. After you install the new template, redo all desired template modifications and [switch everything that was set to the old template to the new template][switch]. You may want to write down the modifications you make to your templates so that you remember what to redo on each fresh install. In the old Debian template, see `/var/log/dpkg.log` and `/var/log/apt/history.log` for logs of package manager actions.
|
||||
|
||||
- [Perform an in-place upgrade of an existing Debian template.][Upgrading Debian TemplateVMs] This option will preserve any modifications you've made to the template, but it may be more complicated for less experienced users.
|
||||
|
||||
|
||||
## Release-specific notes
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Upgrading Fedora TemplateVMs
|
||||
title: In-place upgrade of Fedora TemplateVMs
|
||||
permalink: /doc/template/fedora/upgrade/
|
||||
redirect_from:
|
||||
- /doc/template/fedora/upgrade-26-to-27/
|
||||
|
|
@ -24,7 +24,7 @@ redirect_from:
|
|||
# Upgrading Fedora TemplateVMs
|
||||
|
||||
This page provides instructions for performing an in-place upgrade of an installed [Fedora TemplateVM].
|
||||
If you wish to install a new, unmodified Fedora TemplateVM instead of upgrading a template that is already installed in your system, please see the [Fedora TemplateVM] page instead.
|
||||
If you wish to install a new, unmodified Fedora TemplateVM instead of upgrading a template that is already installed in your system, please see the [Fedora TemplateVM] page instead. ([Learn more about the two options.][Fedora TemplateVM Upgrade])
|
||||
|
||||
|
||||
## Summary instructions for standard Fedora TemplateVMs
|
||||
|
|
@ -194,14 +194,11 @@ In this case, you have several options:
|
|||
However, you may end up having to increase the disk image size anyway (see previous option).
|
||||
3. Do the upgrade in parts, e.g., by using package groups.
|
||||
(First upgrade `@core` packages, then the rest.)
|
||||
4. Do not perform an in-place upgrade.
|
||||
Instead, simply download and install a new template package, then redo all desired template modifications.
|
||||
Here are some useful messages from the mailing list that also apply to TemplateVM management and migration in general from
|
||||
[Marek](https://groups.google.com/d/msg/qubes-users/mCXkxlACILQ/dS1jbLRP9n8J) and
|
||||
[Jason M](https://groups.google.com/d/msg/qubes-users/mCXkxlACILQ/5PxDfI-RKAsJ).
|
||||
4. Do not perform an in-place upgrade, see [Upgrading Fedora TemplateVMs].
|
||||
|
||||
|
||||
[Fedora TemplateVM]: /doc/templates/fedora/
|
||||
[Fedora TemplateVM Upgrade]: /doc/templates/fedora/#upgrading
|
||||
[resize-disk-image]: /doc/resize-disk-image/
|
||||
[Additional Information]: #additional-information
|
||||
[switch]: /doc/templates/#switching
|
||||
|
|
|
|||
|
|
@ -1,32 +0,0 @@
|
|||
---
|
||||
layout: doc
|
||||
title: The Fedora Xfce TemplateVM
|
||||
permalink: /doc/templates/fedora-xfce/
|
||||
---
|
||||
|
||||
The Fedora Xfce TemplateVM
|
||||
=====================
|
||||
|
||||
If you would like to use Fedora Xfce (more lightweight compared to GNOME desktop environment) Linux distribution in your qubes, you can install one of the available Fedora Xfce templates.
|
||||
|
||||
|
||||
Installing
|
||||
----------
|
||||
|
||||
To install a specific Fedora Xfce TemplateVM that is not currently installed in your system, use the following command in dom0:
|
||||
|
||||
$ sudo qubes-dom0-update --enablerepo=qubes-templates-itl qubes-template-fedora-XX-xfce
|
||||
|
||||
(Replace `XX` with the Fedora Xfce version number of the template you wish to install.)
|
||||
|
||||
To reinstall a Fedora Xfce TemplateVM that is already installed in your system, see [How to Reinstall a TemplateVM].
|
||||
|
||||
|
||||
Upgrading
|
||||
---------
|
||||
|
||||
To upgrade your Fedora TemplateVM, please see [Upgrading Fedora TemplateVMs].
|
||||
|
||||
[Upgrading Fedora TemplateVMs]: /doc/template/fedora/upgrade/
|
||||
[How to Reinstall a TemplateVM]: /doc/reinstall-template/
|
||||
|
||||
|
|
@ -6,7 +6,7 @@ permalink: /doc/templates/fedora/
|
|||
|
||||
# The Fedora TemplateVM
|
||||
|
||||
The Fedora [TemplateVM] is the default TemplateVM in Qubes OS. This page is about the standard (or "full") Fedora TemplateVM. For the minimal and Xfce versions, please see the [Minimal TemplateVMs] and [Fedora Xfce] pages.
|
||||
The Fedora [TemplateVM] is the default TemplateVM in Qubes OS. This page is about the standard (or "full") Fedora TemplateVM. For the minimal and Xfce versions, please see the [Minimal TemplateVMs] and [Xfce TemplateVMs] pages.
|
||||
|
||||
|
||||
## Installing
|
||||
|
|
@ -33,24 +33,21 @@ After installing a fresh Fedora TemplateVM, we recommend performing the followin
|
|||
|
||||
## Updating
|
||||
|
||||
Please see [Updating software in TemplateVMs].
|
||||
For routine daily updates within a given release, see [Updating software in TemplateVMs].
|
||||
|
||||
|
||||
## Upgrading
|
||||
|
||||
Please see [Upgrading Fedora TemplateVMs].
|
||||
There are two ways to upgrade your TemplateVM to a new Fedora release:
|
||||
|
||||
- [Install a fresh template to replace the existing one.](#installing) This option may be simpler for less experienced users. After you install the new template, redo all desired template modifications and [switch everything that was set to the old template to the new template][switch]. You may want to write down the modifications you make to your templates so that you remember what to redo on each fresh install. To see a log of package manager actions, open a terminal in the old Fedora template and use the `dnf history` command.
|
||||
|
||||
## Release-specific notes
|
||||
|
||||
This section contains notes about specific Fedora releases.
|
||||
|
||||
(There is currently no release-specific information documented.)
|
||||
- [Perform an in-place upgrade of an existing Fedora template.][Upgrading Fedora TemplateVMs] This option will preserve any modifications you've made to the template, but it may be more complicated for less experienced users.
|
||||
|
||||
|
||||
[TemplateVM]: /doc/templates/
|
||||
[Fedora Xfce]: /doc/templates/fedora-xfce/
|
||||
[Minimal TemplateVMs]: /doc/templates/minimal/
|
||||
[Xfce TemplateVMs]: /doc/templates/xfce/
|
||||
[end-of-life]: https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
|
||||
[supported]: /doc/supported-versions/#templatevms
|
||||
[How to Reinstall a TemplateVM]: /doc/reinstall-template/
|
||||
|
|
@ -60,3 +57,4 @@ This section contains notes about specific Fedora releases.
|
|||
[Updating software in TemplateVMs]: /doc/software-update-domu/#updating-software-in-templatevms
|
||||
[Upgrading Fedora TemplateVMs]: /doc/template/fedora/upgrade/
|
||||
[install]: /doc/templates/#installing
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ redirect_from:
|
|||
The Minimal [TemplateVMs] are lightweight versions of their standard TemplateVM counterparts.
|
||||
They have only the most vital packages installed, including a minimal X and xterm installation.
|
||||
The sections below contain instructions for using the template and provide some examples for common use cases.
|
||||
There are currently three Minimal TemplateVMs corresponding to the standard [Fedora], [Debian] and [CentOS] TemplateVMs.
|
||||
There are currently three Minimal TemplateVMs corresponding to the standard [Fedora], [Debian], [CentOS] and [Gentoo] TemplateVMs.
|
||||
|
||||
|
||||
## Important
|
||||
|
|
@ -25,7 +25,9 @@ There are currently three Minimal TemplateVMs corresponding to the standard [Fed
|
|||
If you encounter problems with the Minimal TemplateVMs, we recommend that you use their standard TemplateVM counterparts instead.
|
||||
|
||||
2. If something works with a standard TemplateVM but not the minimal version, this is most likely due to user error (e.g., a missing package or misconfiguration) rather than a bug.
|
||||
In such cases, you should write to [qubes-users] to ask for help rather than filing a bug report, then [contribute what you learn to the documentation][doc-guidelines].
|
||||
In such cases, please do *not* file a bug report.
|
||||
Instead, please see [Help, Support, Mailing Lists, and Forum] for the appropriate place to ask for help.
|
||||
Once you have learned how to solve your problem, please [contribute what you learned to the documentation][doc-guidelines].
|
||||
|
||||
3. The Minimal TemplateVMs are intentionally *minimal*.
|
||||
[Do not ask for your favorite package to be added to the minimal template by default.][pref-default]
|
||||
|
|
@ -92,7 +94,8 @@ As usual, the required packages are to be installed in the running template with
|
|||
- NetVM, such as the template for `sys-net`: `qubes-core-agent-networking` `qubes-core-agent-network-manager` `NetworkManager-wifi` `network-manager-applet` `wireless-tools` `notification-daemon` `gnome-keyring` `polkit` `@hardware-support`. If your network devices need extra packages for the template to work as a network VM, use the `lspci` command to identify the devices, then run `dnf search firmware` (replace `firmware` with the appropriate device identifier) to find the needed packages and then install them. If you need utilities for debugging and analyzing network connections, install `tcpdump` `telnet` `nmap` `nmap-ncat`.
|
||||
- [USB qube](/doc/usb-qubes/), such as the template for `sys-usb`: `qubes-usb-proxy` to provide USB devices to other Qubes and `qubes-input-proxy-sender` to provide keyboard or mouse input to dom0.
|
||||
- [VPN qube](/doc/vpn/): Use the `dnf search "NetworkManager VPN plugin"` command to look up the VPN packages you need, based on the VPN technology you'll be using, and install them. Some GNOME related packages may be needed as well. After creation of a machine based on this template, follow the [VPN instructions](/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-networkmanager) to configure it.
|
||||
|
||||
- `default-mgmt-dvm`: requires `qubes-core-agent-passwordless-root` and `qubes-mgmt-salt-vm-connector`.
|
||||
|
||||
In Qubes 4.0, additional packages from the `qubes-core-agent` suite may be needed to make the customized minimal template work properly.
|
||||
These packages are:
|
||||
|
||||
|
|
@ -113,7 +116,7 @@ Also, there are packages to provide additional services:
|
|||
- `qubes-pdf-converter`: For implementing safe conversion of PDFs.
|
||||
- `qubes-img-converter`: For implementing safe conversion of images.
|
||||
- `qubes-snapd-helper`: If you want to use snaps in qubes.
|
||||
- `qubes-thunderbird`: Additional tools for use in thunderbird.
|
||||
- `thunderbird-qubes`: Additional tools for use in thunderbird.
|
||||
- `qubes-app-shutdown-idle`: If you want qubes to automatically shutdown when idle.
|
||||
- `qubes-mgmt-salt-vm-connector`: If you want to use salt management on the template and qubes.
|
||||
|
||||
|
|
@ -143,7 +146,8 @@ As usual, the required packages are to be installed in the running template with
|
|||
- NetVM, such as the template for `sys-net`: `qubes-core-agent-networking` `qubes-core-agent-network-manager`. If your network devices need extra packages for a network VM, use the `lspci` command to identify the devices, then find the package that provides necessary firmware and install it. If you need utilities for debugging and analyzing network connections, install the following packages: `tcpdump` `telnet` `nmap` `nmap-ncat`.
|
||||
- [USB qube](/doc/usb-qubes/), such as the template for `sys-usb`: `qubes-usb-proxy` to provide USB devices to other Qubes and `qubes-input-proxy-sender` to provide keyboard or mouse input to dom0.
|
||||
- [VPN qube](/doc/vpn/): You may need to install network-manager VPN packages, depending on the VPN technology you'll be using. After creating a machine based on this template, follow the [VPN howto](/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-networkmanager) to configure it.
|
||||
|
||||
- `default-mgmt-dvm`: requires `qubes-core-agent-passwordless-root` and `qubes-mgmt-salt-vm-connector`.
|
||||
|
||||
In Qubes 4.0, additional packages from the `qubes-core-agent` suite may be needed to make the customized minimal template work properly.
|
||||
These packages are:
|
||||
|
||||
|
|
@ -184,6 +188,7 @@ As usual, the required packages are to be installed in the running template with
|
|||
- NetVM, such as the template for `sys-net`: `qubes-core-agent-networking` `qubes-core-agent-network-manager` `NetworkManager-wifi` `network-manager-applet` `wireless-tools` `notification-daemon` `gnome-keyring`. If your network devices need extra packages for a network VM, use the `lspci` command to identify the devices, then find the package that provides necessary firnware and install it. If you need utilities for debugging and analyzing network connections, install the following packages: `tcpdump` `telnet` `nmap` `nmap-ncat`
|
||||
- [USB qube](/doc/usb-qubes/), such as the template for `sys-usb`: `qubes-usb-proxy` to provide USB devices to other Qubes and `qubes-input-proxy-sender` to provide keyboard or mouse input to dom0.
|
||||
- [VPN qube](/doc/vpn/): You may need to install network-manager VPN packages, depending on the VPN technology you'll be using. After creating a machine based on this template, follow the [VPN howto](/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-networkmanager) to configure it.
|
||||
- `default-mgmt-dvm`: requires `qubes-core-agent-passwordless-root` and `qubes-mgmt-salt-vm-connector`.
|
||||
|
||||
In Qubes 4.0, additional packages from the `qubes-core-agent` suite may be needed to make the customized minimal template work properly.
|
||||
These packages are:
|
||||
|
|
@ -211,7 +216,8 @@ You could, of course, use `qubes-vm-recommended` to automatically install many o
|
|||
[Fedora]: /doc/templates/fedora/
|
||||
[Debian]: /doc/templates/debian/
|
||||
[CentOS]: /doc/templates/centos/
|
||||
[qubes-users]: /support/#qubes-users
|
||||
[Gentoo]: /doc/templates/gentoo/
|
||||
[Help, Support, Mailing Lists, and Forum]: /support/
|
||||
[doc-guidelines]: /doc/doc-guidelines/
|
||||
[pref-default]: /faq/#could-you-please-make-my-preference-the-default
|
||||
[testing]: /doc/testing/
|
||||
|
|
|
|||
|
|
@ -62,6 +62,8 @@ In addition, these templates may be somewhat less stable, since the Qubes develo
|
|||
* [Arch Linux]
|
||||
* [CentOS]
|
||||
* [CentOS Minimal]
|
||||
* [Gentoo]
|
||||
* [Gentoo Minimal]
|
||||
|
||||
## Installing
|
||||
|
||||
|
|
@ -78,8 +80,13 @@ Usually, the installation method is to execute the following type of command in
|
|||
|
||||
$ sudo qubes-dom0-update qubes-template-<name>
|
||||
|
||||
(where `qubes-template-<name>` is the name of your TemplateVM package)
|
||||
where `qubes-template-<name>` is the name of your TemplateVM package.
|
||||
|
||||
If you wish to install a community template, you must enable the community template repo:
|
||||
|
||||
$ sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-<name>
|
||||
|
||||
If you receive the message that no match is found for `qubes-template-<name>`, see [here][no-match].
|
||||
|
||||
## After Installing
|
||||
|
||||
|
|
@ -112,6 +119,10 @@ If the Applications Menu entry doesn't go away after you uninstall a TemplateVM,
|
|||
|
||||
$ rm ~/.local/share/applications/<template-vm-name>
|
||||
|
||||
Applications Menu entries for backups of removed VMs can also be found in `/usr/local/share/applications/` of dom0.
|
||||
|
||||
$ rm /usr/local/share/applications/<template-vm-name>
|
||||
|
||||
|
||||
## Reinstalling
|
||||
|
||||
|
|
@ -252,7 +263,7 @@ Note the word "clean" means in this context: the same as their template filesyst
|
|||
[TemplateBasedVMs]: /doc/glossary/#templatebasedvm
|
||||
[Fedora]: /doc/templates/fedora/
|
||||
[Fedora Minimal]: /doc/templates/minimal/
|
||||
[Fedora Xfce]: /doc/templates/fedora-xfce
|
||||
[Fedora Xfce]: /doc/templates/xfce
|
||||
[Debian]: /doc/templates/debian/
|
||||
[Debian Minimal]: /doc/templates/minimal/
|
||||
[Whonix]: /doc/templates/whonix/
|
||||
|
|
@ -260,6 +271,10 @@ Note the word "clean" means in this context: the same as their template filesyst
|
|||
[Arch Linux]: /doc/building-archlinux-template/
|
||||
[CentOS]: /doc/templates/centos/
|
||||
[CentOS Minimal]: /doc/templates/minimal/
|
||||
[CentOS Xfce]: /doc/templates/xfce
|
||||
[Gentoo]: /doc/templates/gentoo/
|
||||
[Gentoo Minimal]: /doc/templates/minimal/
|
||||
[Gentoo Xfce]: /doc/templates/xfce
|
||||
[Qubes Builder]: /doc/qubes-builder/
|
||||
[TemplateVM Implementation]: /doc/template-implementation/
|
||||
[How to Remove VMs Manually]: /doc/remove-vm-manually/
|
||||
|
|
@ -274,3 +289,4 @@ Note the word "clean" means in this context: the same as their template filesyst
|
|||
[uninstall the old TemplateVM]: #uninstalling
|
||||
[Updating software in TemplateVMs]: /doc/software-update-domu/#updating-software-in-templatevms
|
||||
[How to Reinstall a TemplateVM]: /doc/reinstall-template/
|
||||
[no-match]: /faq/#when-i-try-to-install-a-templatevm-it-says-no-match-is-found
|
||||
|
|
|
|||
50
user/managing-os/xfce-templates.md
Normal file
50
user/managing-os/xfce-templates.md
Normal file
|
|
@ -0,0 +1,50 @@
|
|||
---
|
||||
layout: doc
|
||||
title: Xfce TemplateVMs
|
||||
permalink: /doc/templates/xfce/
|
||||
redirect_from:
|
||||
- /doc/templates/xfce/
|
||||
- /doc/xfce/
|
||||
- /en/doc/templates/xfce/
|
||||
- /doc/Templates/Xfce/
|
||||
- /wiki/Templates/Xfce/
|
||||
---
|
||||
|
||||
# Xfce TemplateVMs
|
||||
|
||||
If you would like to use Xfce (more lightweight compared to GNOME desktop environment) Linux distribution in your qubes,
|
||||
you can install one of the available Xfce templates for [Fedora], [CentOS] or [Gentoo].
|
||||
|
||||
|
||||
## Installation
|
||||
|
||||
The Fedora Xfce TemplateVMs can be installed with the following command (where `X` is your desired distro and version number):
|
||||
|
||||
[user@dom0 ~]$ sudo qubes-dom0-update qubes-template-X-xfce
|
||||
|
||||
If your desired version is not found, it may still be in [testing].
|
||||
You may wish to try again with the testing repository enabled:
|
||||
|
||||
[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-itl-testing qubes-template-X-xfce
|
||||
|
||||
If you would like to install a community distribution, like CentOS or Gentoo, try the install command by enabling the community repository:
|
||||
|
||||
[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-X-xfce
|
||||
|
||||
If your desired version is not found, it may still be in [testing].
|
||||
You may wish to try again with the testing repository enabled:
|
||||
|
||||
[user@dom0 ~]$ sudo qubes-dom0-update --enablerepo=qubes-templates-community-testing qubes-template-X-xfce
|
||||
|
||||
The download may take a while depending on your connection speed.
|
||||
|
||||
To reinstall a Xfce TemplateVM that is already installed in your system, see [How to Reinstall a TemplateVM].
|
||||
|
||||
[How to Reinstall a TemplateVM]: /doc/reinstall-template/
|
||||
|
||||
[TemplateVMs]: /doc/templates/
|
||||
[Fedora]: /doc/templates/fedora/
|
||||
[Debian]: /doc/templates/debian/
|
||||
[CentOS]: /doc/templates/centos/
|
||||
[Gentoo]: /doc/templates/gentoo/
|
||||
[testing]: /doc/testing/
|
||||
Loading…
Add table
Add a link
Reference in a new issue