The Untapped Power of Virtualizing TrueNAS in Your Homelab

Does separating storage from compute actually make sense in modern homelabs? Many enthusiasts argue that Proxmox’s native ZFS support eliminates the need for dedicated NAS solutions like TrueNAS. Yet my journey reveals surprising advantages when intentionally virtualizing TrueNAS through hardware passthrough—a technique transforming how I manage data, services, and system integrity. What began as an energy-saving experiment became a revelation in resource optimization and storage isolation.

The Catalyst: Consolidating My Homelab Footprint

My initial TrueNAS setup ran on a repurposed workstation—modest Ryzen 7 3700X/GTX 1070 Ti hardware quietly hosting services like Home Assistant and Nextcloud. When I migrated to a high-efficiency Proxmox cluster, I faced a dilemma: duplicate workloads across two servers or consolidate everything? Virtualizing TrueNAS emerged as my energy-minimizing solution:

• Power efficiency: New Proxmox server idled at <60W versus the old TrueNAS box’s >140W
• Resource optimization: Leveraging unused IOMMU capabilities on server-grade motherboards
• Service continuity: Critical apps needed uninterrupted access during migration

Hardware passthrough became key—dedicating the entire SATA controller to the TrueNAS VM.

Mastering the Migration: My Step-by-Step Passthrough Process

A flawless transition required meticulous preparation and leveragTrueNAS’s robust configuration portability:

1. Pre-migration:
   • Exported ZFS pools (zpool export)
   • Backed up configuration (.tar file containing network, drive, and service settings)
   • Powered down and physically transplanted drives
2. Proxmox VM setup:
   • Created a TrueNAS Core VM (32GB RAM, 8 vCPUs)
   • Enabled IOMMU in Proxmox kernel parameters (intel_iommu=on for Intel CPUs)
   • Identified SATA controller PCI ID via lspci -nn (e.g., 8086:7ae2)
   • Added passthrough directive: hostpci0: 00:17.0,pcie=1
3. Post-launch restoration:
   • Imported pools (zpool import -f)
   • Uploaded configuration backup (retaining SMB shares, users, services)

Success metrics: Zero downtime for apps like Immich (photo backup), full SMART diagnostics, and ZFS self-healing intact.

Why This “Stopgap” Never Ended: Separation as Security

Initially temporary, the virtualized setup proved irreplaceable due to intrinsic security advantages:

Hardware-Level Isolation Through VFIO

Passthrough via Virtual Function I/O (VFIO) creates what I call “invisible storage”:

• Proxmox sees the controller but cannot access drives (vfio-pci driver takeover)
• Verification command: lspci -nnk shows controller driver as vfio-pci
• TrueNAS handles disk I/O natively—bit rot correction and scrubbing unaffected

Comparative Flexibility vs. Proxmox Native ZFS

Source: Proxmox VE Storage Documentation & iXsystems TrueNAS Deployment Guides

Preserving Hypervisor Sanctity

Proxmox best practices emphasize minimal host modifications. While tweaking hosts is tempting, virtualizing NAS functions avoids:

• Package conflicts from manually installed NFS/SMB tools
• Kernel module instability during updates
• Unintentional zfs command executions impacting datasets

Debunking Myths: Why Virtualized NAS Faces Unwarranted Criticism

Detractors often cite two concerns—both mitigated by proper implementation:

1. “Passthrough complexity causes instability”
Modern solutions like ACS override patches and proper IOMMU grouping resolve most issues. iXsystems officially supports PCIe passthrough when:

• Hypervisors isolate controllers (not individual disks)
• Uninterruptible Power Supplies (UPS) mitigate crash risks

2. “Proxmox ZFS is sufficient”
For basic storage? Absolutely. But TrueNAS adds critical homelab advantages:

• Docker/VM orchestration unified under storage quotas
• Automated cloud sync jobs (Backblaze/Wasabi)
• Self-healing capabilities transparent to Proxmox VMs

Bridging Worlds: Using TrueNAS Storage Within Proxmox

Surprisingly, access remains seamless through network shares:
bash

On Proxmox host

mkdir /mnt/truenas_photos
mount -t cifs //truenas.local/photos /mnt/truenas_photos -o credentials=/etc/proxmox/smb.creds

This mount point can feed LXCs (Linux Containers) or VM disk images—combining Proxmox’s compute flexibility with TrueNAS’ storage resilience.

Rethinking Homelab Dogma

Virtualizing TrueNAS isn’t about rigid best practices—it’s strategic optimization. While a direct Proxmox ZFS setup works for lightweight needs, passthrough delivers uncompromised storage management. Hardware evolution (like PCIe 4.0+ bifurcation) makes this increasingly viable for enthusiast hardware. My “temporary” setup? Now my most reliable system component.

What’s your experience—have you virtualized your NAS or found better alternatives? Share your homelab breakthroughs below!