-
-
Notifications
You must be signed in to change notification settings - Fork 489
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new glossary terms. #748
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -89,6 +89,10 @@ Application Virtual Machine. | |
A [VM](#vm) that is intended for running software applications. | ||
Typically a TemplateBasedVM, but may be a StandaloneVM. Never a TemplateVM. | ||
|
||
TemplateBasedAppVM | ||
------------------ | ||
Any [AppVM](#appvm) that depends on a TemplateVM for its root filesystem. | ||
|
||
NetVM | ||
----- | ||
Network Virtual Machine. | ||
|
@@ -105,6 +109,10 @@ Proxy Virtual Machine. | |
A type of [VM](#vm) that proxies network access for other VMs. | ||
Typically, a ProxyVM sits between a NetVM and another VM (such as an AppVM or a TemplateVM) that requires network access. | ||
|
||
TempalateBasedProxyVM | ||
--------------------- | ||
Any [ProxyVM](#proxyvm) that depends on a TemplateVM for its root filesystem. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same. Even in R3.x all ProxyVMs were based on TemplateVMs, and there are no ProxyVMs in R4.0. |
||
|
||
FirewallVM | ||
---------- | ||
Firewall Virtual Machine. | ||
|
@@ -180,6 +188,14 @@ To boost performance, fully virtualized HVM guests can use special paravirtual d | |
These drivers are optimized PV drivers for HVM environments and bypass the emulation for disk and network I/O, thus providing PV-like (or better) performance on HVM systems. | ||
This allows for optimal performance on guest operating systems such as Windows. | ||
|
||
anon-whonix | ||
----------- | ||
A type of [TemplateBasedAppVM](#templatebasedappvm) that depends on Whonix-Workstation (`whonix-ws`) TemplateVM for its root filesystem. `anon-whonix` can be created during Qubes installation by checking the option to configure the Whonix VMs or by means of [salt]((/doc/salt) when installing/reintalling the Whonix TemplateVMs. Alternatively, users can opt to create `anon-whonix` manually from [Qube Manager](/getting-started/#qubes-vm-manager-and-command-line-tools) or dom0 terminal. | ||
|
||
sys-whonix | ||
---------- | ||
A type of [TemplateBasedProxyVM](#templatebasedproxyvm) that depends on Whonix-Gateway (`whonix-gw`) TemplateVM for its root filesystem. `sys-whonix` can be created during Qubes installation by checking the option to configure the Whonix VMs or by means of [salt](/doc/salt) when installing/reintalling the Whonix TemplateVMs. Alternatively, users can opt to create `sys-whonix` manually from the [Qube Manager](/getting-started/#qubes-vm-manager-and-command-line-tools) or dom0 terminal. | ||
|
||
Windows Tools | ||
----- | ||
Qubes Windows Tools are a set of programs and drivers that provide integration of Windows [AppVMs](#appvm) with the rest of the Qubes system. | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is tautology. There are no AppVMs that are not based on TemplateVMs, and in R4.0 anything that is based on TemplateVM is AppVM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not according to the current official definition: "Application Virtual Machine. A VM that is intended for running software applications. Typically a TemplateBasedVM, but may be a StandaloneVM. Never a TemplateVM."
That's conflating AppVMs with TemplateBasedVMs. As the definition above shows, "AppVM" originally meant "VM for running applications" (hence the "App" part), regardless of whether it's standalone or based on a template. If this conflation was enforced in code beginning with 4.0, then that was a mistake.