Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-06-19 12:14:33 -04:00
Code Issues Projects Releases Packages Wiki Activity

Update "AppVM" and "DisposableVM Template" entries

Browse source 
Prompted by: https://qubes-os.discourse.group/t/difference-between-a-dedicated-and-non-dedicated-disposablevm-template/397
See also: https://github.com/QubesOS/qubes-doc/pull/748
This commit is contained in:
Andrew David Wong 2020-09-04 14:10:40 -05:00
parent cda4bd10ec
commit 3a5bf19d32
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
1 changed files with 3 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

13
user/reference/glossary.md
View file

@ -86,9 +86,8 @@ Unlike TemplateVMs, however, StandaloneVMs do not supply their root filesystems
AppVM AppVM
----- -----
Application Virtual Machine. Application Virtual Machine.
A [VM](#vm) that is intended for running software applications. A [VM](#vm) class.
Typically a TemplateBasedVM, but may be a StandaloneVM. Synonymous with [TemplateBasedVM](#templatebasedvm).
Never a TemplateVM.
NetVM NetVM
----- -----
@ -132,14 +131,6 @@ A type of [TemplateBasedVM](#templatebasedvm) on which [DisposableVMs](#disposab
By default, a DisposableVM Template named `fedora-XX-dvm` is created on most Qubes installations (where `XX` is the Fedora version of the default TemplateVM). By default, a DisposableVM Template named `fedora-XX-dvm` is created on most Qubes installations (where `XX` is the Fedora version of the default TemplateVM).
DisposableVM Templates are not [TemplateVMs](#templatevm), since (being TemplateBasedVMs) they do not have root filesystems of their own to provide to other VMs. DisposableVM Templates are not [TemplateVMs](#templatevm), since (being TemplateBasedVMs) they do not have root filesystems of their own to provide to other VMs.
Rather, DisposableVM Templates are complementary to TemplateVMs insofar as DisposableVM Templates provide their own user filesystems to the DisposableVMs based on them. Rather, DisposableVM Templates are complementary to TemplateVMs insofar as DisposableVM Templates provide their own user filesystems to the DisposableVMs based on them.
There are two main kinds of DisposableVM Templates:
* **Dedicated** DisposableVM Templates are intended neither for installing nor running software.
Rather, they are intended for *customizing* or *configuring* software that has already been installed on the TemplateVM on which the DisposableVM Template is based (see [DisposableVM Customization](/doc/disposablevm-customization/)).
This software is then intended to be run (in its customized state) in DisposableVMs that are based on the DisposableVM Template.
* **Non-dedicated** DisposableVM Templates are typically [AppVMs](#appvm) on which DisposableVMs are based.
For example, an AppVM could be used to generate and store trusted data.
Then, a DisposableVM could be created based on the AppVM (thereby making the AppVM a DisposableVM Template) so that the data can be analyzed by an untrusted program without jeopardizing the integrity of the original data.
PV PV
-- --