Why use Qubes over other Virtualizers?

From Whonix
Jump to navigation Jump to search

Why use Qubes over other Virtualizers?[edit]

The Qubes project is focused on developing the Qubes OS desktop operating system, which is based upon the principle of "Security by Isolation". It is not a general purpose operating system where the ability to install a virtualizer is just another feature. Rather, it runs a bare-metal virtualizer (Xen) and isolates hardware controllers and multiple user domains (qubes) in separate VMs that are explicitly assigned different levels of trust.


Advanced Separation / Least Privilege[edit]

  • The Xen hypervisor and administrative domain (dom0) in Qubes OS actively discourages any activity other than running VMs.
  • The network stack and WiFi drivers are running in a dedicated, unprivileged network qube (NetVM), which substantially reduces the attack surface.
  • Future separation of the GUI (graphical) domainarchive.org from dom0 is partially implemented in Qubes 4.1.

Hardware and Protocol Protection[edit]

  • Enabling VT-d/IOMMU via BIOS provides DMA protection.
  • The USB stack can be isolated in a dedicated USB VM, protecting dom0 from untrusted USB devices.
  • Anti Evil Maid (AEM)archive.org protection is supported.
  • Yubikeyarchive.org multi-factor user authentication is available to enhance the security of logins, mitigate the risk of password snooping, and improve USB keyboard security.
  • No microphones are attached to VMs by default.


  • An additional firewall VM is used to house the Linux kernel-based firewall, providing extra protection against a compromised NetVM; see Qubes networkingarchive.org.
  • By default, Qubes OS is firewalled and no incoming ports are open.
  • No networking is present in the administrative domain (dom0). Even dom0 upgrades are done in a dedicated UpdateVM (currently set by default to sys-firewall), before those are verified and installed in dom0.
  • All Template and dom0 updates can be easily fetched over Tor via the Whonix-Gateway ProxyVM (commonly called sys-whonix).
  • TCP timestamps are disabled by default. [1]
  • ICMP timestamps are disabled by default. [2]
  • Protection against unintentional leaks of critical user data is possible by setting an empty NetVM field for the corresponding qube.
  • Tor Traffic can be white-listed using corridor as a filtering gateway, protecting against accidental clearnet leaks.
  • Availability of an experimental unikernelarchive.org firewall based on MirageOS for greater security, performance and a lower resource footprint.

Other Benefits[edit]

  • Disposablesarchive.org are available to open untrusted applications, links, attachments and documents. [3]
  • Service qubes can be configured as a static Disposablesarchive.org to mitigate the threat from persistent malware across VM reboots. [4]
  • Unforgeable, colored window borders allow easy identification of qubes with different security levels.
  • PDFs can be easily sanitized via a trusted PDF converter. [5]
  • Greater security of email-centric work environments is possible by using split GPG to protect private keys and limiting network connections exclusively to the chosen email server.
  • Joanna Rutkowskaarchive.org, security researcher, founder and developer emeritus of Qubes OSarchive.org has completed a research paper comparing the security of software compartmentalization vs. physically separated computersarchive.org (pdf). It concluded that in some cases, notably for specific, desktop-related workflows, Physical Isolation might be less secure than Qubes' compartmentalized approach.


  • OS agnostic: qubes can be based upon Fedora, Debian, Ubuntu, Whonix, Windows, Kali Linux, CentOS and Arch Linux templates, among others.
  • All isolated qubes are integrated into a single, usable system via a unified desktop.
  • Software installation and updates are centralized.
  • Creating new VMs and disposing of unwanted VMs is very easy and fast.
  • The VM start menu is integrated into the host's (dom0) start menu via Qubes VM Manager.
  • A secure and usable mechanism exists for copying and pastingarchive.org clipboard contents and files between qubes.
  • An easier backup / restore mechanism for VMsarchive.org.
  • The keyboard layout only needs to be configured once in dom0.
  • No duplicate task bars are present.
  • A default seamless mode is available for Windows (similar to VirtualBox’s Seamless Mode or VMware’s Unity Mode). [7] It is easy to distinguish which window belongs to each VM. [8]
  • See also: A Usability Evaluation of Qubes OSarchive.org.


  • VMs boot up much faster, because fewer services need to be started.
  • App Qubes therefore also use much less RAM.
  • App Qubes use far less disk space because they can share the root image of the Template in read-only mode. Separate disk storage is only used for the user's directory and per-VM settings (read more: Template Implementationarchive.org).
  • Standalonesarchive.org can be created for the installation of software in only specific domains.

Qubes-Whonix Advantages over Non-Qubes-Whonix[edit]


  • It is easier to tunnel the whole system -- including host (dom0) updates -- through Tor (besides sys-net and sys-firewall).


  • Multiple Whonix-Workstation App Qubes can easily use the same Whonix-Gateway ProxyVM without being able to make contact with one another. [9]
  • Downloads of Whonix Template images use cryptographic signatures of the dom0 package manager (qubes-dom0-update / dnf). Without the user knowing it, this makes verification transparent.
  • It is simple to run Tor Browser in a Whonix-Workstation Disposable.
  • Various operations can be securely performed in Qubes-Whonix VMs which are not available in Non-Qubes-Whonix, like:


Qubes Vulnerabilities[edit]

Qubes is not however a silver bullet - attacks are still possible against:

  • The virtualization technology (VT-x, VT-d).
  • The hypervisor (Xen). [14]
  • Additional software used by any virtualized system, like qemu and DirectX emulation.

Further, data leaks are possible via cooperative covert channels (malware working in concert across two or more VMs), and side channel attacks (malware in one VM trying to learn about processes executed in another VM).

Qubes-Whonix Security Disadvantages - Help Wanted!archive.org


  1. Disable TCP Timestamps.
  2. Disable ICMP Timestamps.
  3. From Qubes R4.0, disposable Whonix-Workstation VMs are now available, as well as multiple Disposables for other platforms.
  4. sys-net, sys-firewall and sys-usb can be configured as static Disposables. This option was first made available in Qubes R4.
  5. Right-clickConvert to Trusted PDF
  6. The minimal templates are lightweight versions of their standard template counterparts. They have only the most vital packages installed, including a minimal X and xterm installation. When properly configured and used, minimal templates can be less resource-intensive, reduce attack surface, and support more fine-grained compartmentalization.

  7. https://www.howtogeek.com/171145/use-virtualboxs-seamless-mode-or-vmwares-unity-mode-to-seamlessly-run-programs-from-a-virtual-machine/archive.org
  8. https://www.qubes-os.org/doc/GettingStarted/archive.org
  9. This issue for Non-Qubes-Whonix is documented on the Multiple Whonix-Workstation wiki page.
  10. Qubes PDF Converter is a Qubes OS application that uses Disposables and Qubes' flexible qrexec (inter-VM communication) infrastructure to securely convert untrusted PDF files into safe-to-view PDF files. This is done by using a Disposable to render each page of a PDF file into a very simple representation (RGB bitmap) that (presumably) leaves no room for malicious code. This representation is then sent back to the client qube which then constructs an entirely new PDF file out of the received bitmaps.

  11. Converting untrusted PDFs into trusted ones: The Qubes Wayarchive.org.
  12. Network Time Syncing.
  13. https://phabricator.whonix.org/T71archive.org
  14. See: Xen Security Advisoriesarchive.org.

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!