To run a Tails VM, scaricare the corrente ISO from tails.net, verificare it, create a new guest with the hypervisor's normal Linux impostazioni, attach the ISO as optical media, and disable cartelle condivise, appunti, trascinamento, and saved snapshot unless you have a clear reason to use them. A VM keeps the host operating system and hypervisor inside the confine di sicurezza, so use it for learning or a threat model that accepts that dependency.
Cosa può e non può fare Tails macchina virtuale
A Tails macchina virtuale is a guest operating system running in a window on Windows, macOS, or Linux. It lets you explore the Tails desktop, wait for a Tor connection, and test a documented flusso di lavoro without restarting the computer. The normal setup uses an ISO as virtual optical media, while the immagine USB is intended for writing to removable media and direct boot.
The convenience changes the security model. The host controls the hypervisor, physical rete adapter, firmware, archiviazione, and often the macchina virtuale memory and snapshot. A compromised host can observe or alter a guest, and a person with access to the host can inspect its files or logs. Tor routing inside the guest does not hide the existence of the VM from the host or make a host account anonymous.
Usa a Tails VM when the goal is a controlled demonstration, a compatibility check, or a disposable lab that accepts host dependence. Scegli a USB verificata when you need the normal Tails flusso di lavoro, easier Persistent Storage, portability, or a stronger separation from an everyday operating system. The useful decision is the boundary you can trust, not the visual appearance of a Tails window.
- A VM avoids a reboot and is convenient for training or testing.
- The host, hypervisor, firmware, and virtual disk remain in scope.
- A VM does not make personal accounts, documents, or behavior anonymous.
- Usa the official USB path for normal recurring Tails sessions.
| Decision | Tails macchina virtuale | Verified Tails USB |
|---|---|---|
| Learn the interface | Comodo | Funziona, ma richiede un riavvio |
| Distrust the everyday host | Scelta debole perché l’host resta al controllo | Separazione migliore quando l’hardware lo consente |
| Persistent Storage | Virtual disk and hypervisor dependent | Normal supported flusso di lavoro |
| Portability | Legato all’host e ai file della VM | Porta la USB dedicata |
| Hardware compatibility | Emula solo l’hardware | Testa il computer reale |
A successful Tails VM boot proves that the guest can start in that hypervisor. It does not prove that a physical USB will boot or that the host cannot inspect the session.
Scaricare e verificare l’ISO di Tails
Start at the ufficiale di Tails scaricare pages rather than a mirror, video description, or file-sharing link. The scaricare page changes as releases change; on November 16, 2026, its release notes link identified Tails 7.12. This page deliberately does not hard-code a version or file size because a VM guida should keep sending you to the corrente first-party instructions.
Save the ISO in a normal Scaricares folder or in the archiviazione location recommended by Tails. Do not save the only copy inside the guest, and do not rename it until verifica is complete. A partial scaricare, an interrupted transfer, or an ISO from an untrusted source can create a boot failure that looks like a hypervisor problem.
Verification is part of the VM setup, not an optional extra. Complete the official verifica before attaching the image to VirtualBox, GNOME Boxes, VMware, or Proxmox. If the check fails, scaricare again from tails.net and investigate the transfer before changing VM impostazioni.
- Usa tails.net for the ISO and its matching verifica flow.
- Mantieni the scaricareed file outside the guest until it has been verified.
- Do not extract the ISO before attaching it as optical media.
- Treat a failed verifica as a scaricare problem first.
- 1
Open the official page
Controlla the address bar for tails.net and choose the corrente ISO option intended for macchina virtuales or documented advanced use.
- 2
Scaricare the release
Mantieni the ISO in a known folder and read the corrente release notes for changes or known issues.
- 3
Run verifica
Usa the official browser verifica flow or the documented method for your corrente Tails release.
- 4
Mantieni one traceable copy
Record which release you verified and remove ambiguous duplicate files before attaching the image to a new guest.
Configurare una VM VirtualBox o GNOME Boxes più sicura
Crea a new guest instead of attaching the ISO to a personal VM that already contains accounts, cartelle condivise, or snapshot. Select a corrente 64-bit Linux profile when the hypervisor offers one, and follow the corrente Tails requirements for memory, processor features, and display. Avoid inventing a resource number that may become stale; if the guest is slow, increase resources only within what the host can safely provide.
Attach the verified ISO to the virtual optical drive and place that drive first in the guest boot order. Mantieni the virtual rete in the mode recommended by the official documentation for your goal. A rete setting can change what the host and local rete can observe, so do not describe one adapter mode as universally private or safe.
The most important configuration is the integration surface. Turn off shared appunti, trascinamento, cartelle condivise, host-mounted drives, and automatic USB passthrough unless a documented task needs one of them. Every enabled bridge is a way for text, files, or device state to cross between the guest and host. If you enable one temporarily, disable it again before sensitive work.
Usa a fresh virtual disk and a clear name that includes the purpose and release date. Do not store a VM image in a cloud-synced personal folder or an unencrypted external location without understanding who can read it. A VM file can contain the guest disk, saved memory, configuration, logs, and snapshot even when the Tails session itself is designed to forget ordinary state.
- Start with a new guest and a corrente 64-bit Linux profile.
- Attach the ISO as optical media and confirm the boot order.
- Disattiva appunti, trascinamento, cartelle condivise, and unnecessary USB access.
- Mantieni the virtual disk, snapshot, and logs in a controlled location.
- Usa corrente Tails documentation for supported hypervisors and resource guidance.
- 1
Crea a new guest
Scegli a descriptive VM name, a supported 64-bit Linux type, and a new virtual disk rather than reusing a personal guest.
- 2
Set conservative resources
Give the guest enough memory and processor capacity for the corrente Tails requirements while leaving the host responsive.
- 3
Attach the ISO
Select the verified ISO in the virtual optical drive and put that drive before the empty virtual disk in the boot order.
- 4
Review rete and display
Usa documented rete and display defaults, then remove extra adapters, webcams, audio devices, and host integrations you do not need.
- 5
Disattiva transfer paths
Turn off shared appunti, folders, trascinamento, automatic USB mounting, and saved-state features before the first boot.
| Surface | Safer starting choice | Perché conta |
|---|---|---|
| Clipboard | Disattivad | Prevents accidental text transfer |
| Shared folders | Disattivad | Mantienis host files outside the guest |
| Snapshots | Disattivad until understood | Can retain old disk or memory state |
| USB passthrough | Only when required | Connects physical devices to the guest |
| VM archiviazione | Controlled local location | Configuration and disk files can reveal activity |
Avviare Tails e controllare le impostazioni di integrazione
Start the guest with the verified ISO connected. The first screen should be the Tails welcome flow rather than a host operating system or a generic boot error. If the hypervisor reports that no bootable medium exists, stop and check the ISO path, optical-drive attachment, and boot order before changing CPU or rete impostazioni.
Once the desktop appears, wait for the Tor connection process and test only the flusso di lavoro you intended to learn. Do not sign into a personal account simply because the browser opens. The host can still know that virtualization software is running, and a service can still associate activity with an account or an identifying document.
Before doing anything sensitive, re-open the VM impostazioni and confirm that the hypervisor did not silently re-enable appunti sharing, guest additions, a shared directory, a webcam, or a saved snapshot. Hypervisor updates and imported appliance defaults can change these values. Treat the impostazioni review as part of every fresh guest, not as a one-time checkbox exercise.
- Conferma the guest starts from the verified ISO, not an old virtual disk.
- Wait for Tor to connect before judging a site or application unavailable.
- Mantieni personal accounts and identity-linked documents out of the test session.
- Review integration impostazioni again after importing, cloning, or updating a VM.
- 1
Start from optical media
Power on the new guest with the ISO attached and watch for the Tails welcome screen.
- 2
Wait for the rete
Allow the Tor connection flusso di lavoro to finish before testing a browser or scaricare.
- 3
Run the smallest test
Open only the page or feature needed for the learning objective and avoid identity-linked logins.
- 4
Recheck the host bridge
Inspect appunti, folders, snapshot, USB devices, and guest tools before continuing.
A page that blocks Tor or needs an ordinary browser is a different flusso di lavoro. Move that task to a suitable trusted system instead of adding extensions or turning the Tails guest into a general desktop.
Persistent Storage e gestione dei dati in Tails macchina virtuale
Persistent Storage is more complicated in a VM because the hypervisor owns the virtual disk and its retention features. A DVD is read-only, while a virtual disk can be copied, snapshotted, backed up, or inspected by anyone who can access the host. Do not assume that a persistent volume inside the guest has the same operational properties as a dedicated Tails USB.
If a documented test requires persistence, create it only after the base ISO and guest configuration are verified. Mantieni the virtual disk in a protected location, turn off automatic snapshot, and plan how you will back up or delete it. Do not place identity-linked files in persistence merely to make a demo convenient. A later export or host backup can preserve the file after the guest shuts down.
For repeatable everyday use, a dedicated USB verificata is usually easier to reason about. It supports the normal Tails update and archiviazione flusso di lavoro and can be removed from the host when the session ends. A VM remains useful for learning, but the host boundary should be stated every time the setup is shared with another person.
- Treat the virtual disk as host-controlled data.
- Disattiva snapshot and saved memory unless a test explicitly needs them.
- Back up or delete persistent VM data deliberately, not by assumption.
- Usa the USB guida for normal Persistent Storage and recurring sessions.
| Data path | Possible retained state | Review before use |
|---|---|---|
| Guest disk | Persistent files and impostazioni | Host permissions and backup location |
| Snapshot | Older disk and memory state | Disattiva or delete after testing |
| Shared folder | Files copied between host and guest | Mantieni disabled unless required |
| Clipboard | Copied text or commands | Disattiva during sensitive work |
| Exported document | Metadata and identity clues | Inspect before moving to another system |
A verified ISO proves the release file was checked. It does not make a host-controlled virtual disk, snapshot, or backup invisible.
Diagnosticare problemi di avvio, rete e prestazioni
Start with the simplest boundary: file, optical drive, and boot order. A zero-byte ISO, a partial scaricare, a disconnected virtual CD drive, or a virtual disk placed before the ISO can all produce a black screen or a “not bootable” message. Re-verificare the ISO before scaricareing another hypervisor or copying a random configuration from a forum.
If Tails starts but Tor does not connect, separate guest reteing from the service itself. Conferma that the host is online, that the VM has the single adapter required for the test, and that the system clock is reasonable. A site may also reject Tor or fail because its scripts are incompatible with the browser's privacy impostazioni. Do not disable protections just to make one page look normal.
Slow performance usually means that the host is short on memory or processor capacity, the display adapter is poorly configured, or the guest is competing with another workload. Close unrelated host applications, confirm that virtualization support is enabled, and adjust resources within the official requirements. If the physical machine is the target, move to a USB verificata test: a VM cannot reveal real Wi-Fi, graphics, firmware, or startup-menu problems.
- Re-verificare the ISO before changing the hypervisor.
- Controlla optical attachment and boot order for “not bootable” errors.
- Classify Tor, host-rete, clock, and site-blocking symptoms separately.
- Usa a physical USB to test real hardware compatibility.
- Do not install unverified guest tools or browser extensions as a shortcut.
- 1
Verify the input
Conferma the ISO is complete, verified, attached to the optical drive, and selected before the empty disk.
- 2
Controlla the guest
Review the 64-bit profile, memory, processor count, display controller, and single intended rete adapter.
- 3
Wait for Tor
Let the connection flusso di lavoro finish, then test a second page to distinguish a service block from a local failure.
- 4
Move to hardware
When the question is Wi-Fi, graphics, UEFI, Secure Boot, or USB startup, use the USB verificata and the relevant hardware guida.
Sapere quando passare dalla VM a una USB verificata
A Tails VM is a useful learning environment when its limitations are visible. It helps you understand the desktop, Tor Browser, and the general live-session flow without interrupting the host. It is a poor replacement for hardware boot when the host is outside your trust boundary, when you need portable sessions, or when your threat model includes someone who can inspect the host.
Usa the VM as a checkpoint, not as a promise. Verify the ISO, keep integration paths closed, test the smallest flusso di lavoro, and record what the host can still observe. When the task becomes recurring or requires normal Persistent Storage, follow the official USB installation and verifica guidas. Mantieni the ISO link and this page nearby because supported virtualization details can change with a release.
The safest page-level decision is simple: choose a VM for an explicitly accepted host dependency, choose a USB for the normal Tails experience, and choose an ordinary trusted system for work that needs personal accounts or a familiar browser profile. Naming the boundary makes the setup easier to troubleshoot and harder to misunderstand.
- VM for learning, compatibility checks, and a defined lab threat model.
- USB for portability, recurring sessions, and the normal archiviazione flusso di lavoro.
- A separate trusted system for identity-linked everyday browsing.
- Re-read official virtualization guidance after major Tails releases.
Checklist di Tails macchina virtuale prima di iniziare
Usa the ufficiale di Tails ISO page, verificare the image, and create a new guest whose purpose is clear. Review the host boundary before the first boot: the hypervisor, virtual disk, snapshot, physical rete, and host logs all remain relevant to what the session can expose.
Mantieni the integration surface small. Disattiva shared appunti, cartelle condivise, trascinamento, automatic USB access, saved memory, and unneeded devices. If a test needs one of them, enable it for the shortest possible time, document the reason, and turn it off again before handling sensitive data.
When the question changes from “Can the guest start?” to “Will this real computer boot safely?” or “Can I rely on Persistent Storage every day?”, stop using the VM as evidence. Move to the USB verificata flusso di lavoro and read the corrente Tails documentation for the release you scaricareed.
- Verify the ISO before attaching it.
- Treat the host and hypervisor as part of the confine di sicurezza.
- Mantieni transfer paths and retained state disabled by default.
- Usa a USB verificata for normal Tails sessions and real hardware tests.
FAQ su Tails macchina virtuale
Can I run Tails in VirtualBox?
La documentazione ufficiale di Tails describes running Tails in a macchina virtuale with an ISO. Usa the corrente supported guidance, verificare the ISO, and remember that VirtualBox and the host remain inside the confine di sicurezza.
Can I run Tails in VMware or GNOME Boxes?
A hypervisor may be able to boot the ISO ufficiale, but support and impostazioni can change. Controlla the corrente Tails virtualization page and keep integrations disabled unless the documented task needs them.
Is Tails in a VM as private as Tails from USB?
Usually no. The host controls the hypervisor, memory, archiviazione, rete hardware, and often snapshot. A USB verificata is the safer default when the host is not trusted.
Do I need the Tails ISO or immagine USB for a VM?
The ISO is the usual virtual optical media choice. The immagine USB is intended for writing to removable media and direct boot; follow the official page when a release gives a specific exception.
Can Persistent Storage work in a Tails VM?
A virtual disk can hold dati persistenti, but the hypervisor and host control that disk, its backups, and its snapshot. Do not treat it as equivalent to the normal dedicated USB flusso di lavoro.
Why does my Tails VM show a black screen?
Verify the ISO, confirm the optical drive is attached, check the boot order and corrente 64-bit profile, then review display resources. Usa a physical USB for hardware-specific startup problems.
Should I enable shared appunti or folders?
Mantieni them disabled by default. They create direct transfer paths between the host and guest. Enable one only for a documented, low-risk task and disable it again afterward.
Verifica dati tecnici e download nella ufficiale di Tails virtualization documentation. Questa guida indipendente non ospita né modifica immagini di Tails.