[[!meta title="Running Tails in a virtual machine"]]

It is sometimes convenient to be able to run Tails without having to restart your computer every time. This is possible using [[!wikipedia Virtual_machine desc="virtual machines"]].

With virtual machines, it is possible to run Tails inside a *host* operating system (Linux, Windows, or macOS). A virtual machine emulates a real computer and its operating system, called a *guest*, which appears in a window on the *host* operating system.

When running Tails in a virtual machine, you can use most features of Tails from your usual operating system, and you can use both Tails and your usual operating system in parallel, without the need to restart the computer.

<p>We do not currently provide a solution for running a virtual machine
inside a Tails host.</p>

</div>

This is how Tails looks when run in a virtual machine on a Debian host.

[[!img tails-in-vm.png class="screenshot" alt=""]]

Security considerations

<div class="caution">

<p>Running Tails inside a virtual machine has various security
implications. Depending on the host operating system and your security
needs, running Tails in a virtual machine might be dangerous.</p>

<a id="trustworthy"></a>

Both the host operating system and the [[virtualization software|virtualization#software]] are able to monitor what you are doing in Tails.

If the host operating system is compromised with a software
keylogger or other malware, then it can break the security features
of Tails.

<div class="caution">

<p>Only run Tails in a virtual machine if both the host operating
system and the virtualization software are trustworthy.</p>

</div>

<a id="traces"></a>

Traces of your Tails session are likely to be left on the local hard disk. For example, host operating systems usually use swapping (or *paging*) which copies part of the RAM to the hard disk.

<p>Only run Tails in a virtual machine if leaving traces on the hard disk
is not a concern for you.</p>