TrueNAS Proxmox Plugin - Ready for Community, Under Testing for Enterprise

HoneyBadger · September 17, 2026, 8:10pm

It’s been a lot of work over the year thus far, but the TrueNAS team is proud to introduce the new storage plugin for Proxmox VE.

Alongside Kubernetes, Cinder, and Terraform, we’re working to add tighter integrations with a variety of software solutions, giving you options with convenience.

Who is this for?

This plugin is for users who have one (or more) Proxmox VE hypervisor hosts that they’re connecting to a separate TrueNAS machine.

It’s an enhancement over the current NFS or LVM-on-iSCSI flows - a way to give you a “one LUN per disk” VVOL-like experience, complete with offloaded ZFS snapshots, per-disk tunability for parameters like volblocksize, and ease of migration, but without the repetitive clicking of manual provisioning.

What’s the minimum version of TrueNAS and Proxmox VE needed?

For TrueNAS, you’ll have to be running 25.10 as a minimum, to make use of the versioned JSON-RPC WebSocket API.

For Proxmox VE, you’ll need a minimum of PVE 8.x for iSCSI, and if you want to make use of the new NVMe/TCP transport layer, that requires PVE 9.x

Is this limited to Enterprise users?

Nope - no license is required. Freely downloadable through Github now, and we’re exploring ways to make it even easier than that.

Can this completely replace the old way I do Proxmox?

Proxmox can’t store ISO images, vzdumps, or other files on iSCSI/NVMe, so you’ll still need an NFS or SMB export to map to. Thankfully, that’s just a checkbox away in the TrueNAS web UI.

Enough talk. Where do I download it?

Go grab it from https://github.com/truenas/truenas-proxmox-plugin

I think I found a bug. Where should I submit it?

Open an issue on the truenas/truenas-proxmox-plugin Github page, and we’ll look into it - but you can also link it here, to see if this is something else the community has seen or can benefit from.

chrislongros · September 18, 2026, 8:23am

Thanks !

swc-phil · September 19, 2026, 7:05am

I don’t use truenas for block storage in proxmox but widely use it for SMB shares (which are bonded to LXCs later). Would I somehow benefit from the plugin in this use case? I suppose that I won’t.

P.s. IMO, there are missing tags for this announcement.

Glitch01 · September 21, 2026, 1:11am

Thanks. Currently using TN just for ISO, backups, and various other things, but it’ll be interesting to see the plugin in action & not just direct map using NVMe-oF or iSCSI for Proxmox. I run some VM’s and Containers in Linux but not in Proxmox using NVMe-oF.

sirbryan · September 22, 2026, 3:17pm

Does this support the ARM64 build(s)?

wmo · September 22, 2026, 3:32pm

I don’t see why it wouldn’t work – but it hasn’t been tested.

HoneyBadger · September 23, 2026, 2:08pm

Correct, the plugin is only for block, not file.

As @wmo says, no reason it shouldn’t - it’s just making API calls to TrueNAS, nothing architecture specific, unless there’s a piece of the scst or nvmet puzzle that isn’t working on ARM.

ttl0 · September 25, 2026, 8:25am

It seems to only work for VM storage, whilst the README says “LXC Container Storage - Block-backed container rootfs support alongside VM disk storage”.

I do see in the Known Limitations section is says it is for VM storage only. So is the README just incorrect? Or is there a plan to add LXC storage in the future?

wmo · September 25, 2026, 1:17pm

LXC storage support exists now. I’ve updated the README and added a LXC-Setup.md to make the support more obvious.

dan · October 2, 2026, 8:18pm

root@pve1 ➜  ~ bash <(curl -sSL https://raw.githubusercontent.com/truenas/truenas-proxmox-plugin/main/install.sh) --non-interactive --apt-install

   d8P
d888888P
  ?88'    88bd88b?88   d8P d8888b  88bd88b  d888b8b   .d888b,
  88P     88P'  `d88   88 d8b_,dP  88P' ?8bd8P' ?88   ?8b,
  88b    d88     ?8(  d88 88b     d88   88P88b  ,88b    `?8b
  `?8b  d88'     `?88P'?8b`?888P'd88'   88b`?88P'`88b`?888P'

              d8b                      d8,
              88P                     `8P
             d88
   ?88,.d88b,888  ?88   d8P d888b8b    88b  88bd88b
   `?88'  ?88?88  d88   88 d8P' ?88    88P  88P' ?8b
     88b  d8P 88b ?8(  d88 88b  ,88b  d88  d88   88P
     888888P'  88b`?88P'?8b`?88P'`88bd88' d88'   88b
     88P'                         )88
    d88                          ,88P     For Proxmox VE
    ?8P                      `?8888P

  Checking system requirements...
  System requirements satisfied
  APT install mode enabled
APT suite:                     trixie
Creating keyring directory:    OK
Downloading repo key:          FAILED
  Downloaded APT key is empty or not a PGP key block -- not installing it

wmo · October 2, 2026, 8:43pm

Sorry about that. Fixed.

dan · October 2, 2026, 8:48pm

Indeed, installation now succeeds. But the README simply doesn’t match the TrueNAS 25.10 UI, and it isn’t even close.

wmo · October 2, 2026, 10:03pm

Yep, sorry about that. Looks like we carried some old 24.x details over in the README and Installation.md files. I touched those up a bit.

dan · October 3, 2026, 7:24pm

Much better match. The 25.10 instructions still seem to assume creation of a zvol somewhere between “create a dataset” and “use the iSCSI Wizard”–fair, I suppose, to assume that anyone who would be using this would be able to figure it out.

sirbryan · October 7, 2026, 1:01pm

On the nvme directions, it would be nice to include the wget command to get the automated installation script, since it’s not on the same/main page as everything else.

I went down the path of doing it manually, using the main README’s NVME config and the NVME-Setup, but it didn’t come up. The sample NVME configuration on the main README differs from the sample config on the NVME readme, as well as what the install script does, particularly “content” (images only, vs. images,rootdir on the front README). It also set “tn_api_insecure” and “tn_sparse,” which are listed as optional in the samples, but apparently were required to get it working.

FWIW this is working on ARM64 hosts (Proxmox on CCR2116’s and TrueNAS on RDS2216’s).

sirbryan · October 8, 2026, 12:47am

With build 25.10.1-MASTER-20260510-100116 for ARM64, I ran into an issue with the namespace not matching what was created. Grok found it and patched it for me. Then we ran into a 5MB write that failed, and it’s patching the NVME target code in the kernel module (I’m using a custom 6.18.x) since that’s a better fix than udev rules on dozens of proxmox hosts.

github.com/truenas/truenas-proxmox-plugin

Trying ARM64 from Proxmox 9.2.2 to TrueNAS 25.10.1-MASTER-20260510-100116

opened 12:20AM - 08 Oct 26 UTC

SirBryan

I had an issue trying to get the plugin to create and use nvme ZVOL's. After fl…ailing around, I pointed Grok at it and this is what it said (and how it fixed/patched it): ## NVMe namespace is stored on TrueNAS and never becomes a block device A disk move onto an NVMe-TCP storage can allocate the target volume and then fail while looking up the device: ```text allocated target volume 'tn-bottom-nvme-arm:vol-vm-2000-disk-0-ns<device_uuid>' TASK ERROR: storage migration failed: Could not locate NVMe device for TrueNAS UUID <device_uuid> Subsystem NQN: nqn.2026-09.n.q.n:tn-bottom-nvme-arm TrueNAS namespace publication mismatch detected. -> Linux-visible block devices: 0 -> TrueNAS API namespace count: 0 -> Selector mismatch reason: namespace_metadata_did_not_match_visible_devices -> Detail: TrueNAS metadata did not match any visible Linux NVMe namespace device ``` TrueNAS has created the zvol and the `nvmet.namespace` row. The Proxmox host is connected to that subsystem (`nvme list-subsys` shows the NQN, controller state `live`) and `nvme list` shows no namespace for it. On the TrueNAS host the namespace directory is empty: ```text /sys/kernel/config/nvmet/subsystems/<subsystem-nqn>/namespaces ``` `midclt call nvmet.namespace.query` still returns the row. The database insert succeeded. The kernel target never received the namespace, so the plugin's NGUID/NSID lookup has nothing to match. The "TrueNAS API namespace count: 0" line is a bad signal on TrueNAS 25.10.1. The plugin counts namespaces with `nvmet.namespace.query` filter `["subsys", "=", <subsys id>]`, and this release rejects that filter (`Invalid filter`). A `device_uuid` query and the UI both show the row. An empty configfs namespace directory is the check that matters. ### Cause TrueNAS 25.10.1 renders the NVMe target in `middlewared/plugins/nvmet/kernel.py`, `write_config()`. Subsystem attributes are written before namespaces. `NvmetSubsysConfig.map_attrs` sets `attr_model` from `nvmet.subsys.model` on every render. `subsys.py` `model()` builds that string with `f'TrueNAS {system_product}'` when the vendor name is empty and the product name does not already start with `TrueNAS`. An empty DMI product name produces `TrueNAS ` with a trailing space. configfs stores that value. On the next render, `update_attrs()` strips only the value read back from configfs, compares `TrueNAS` with `TrueNAS `, and writes `attr_model` again. After the first host connects, the kernel latches the model (`subsys_discovered`). `nvmet_subsys_attr_model_store` then rejects every later write: ```text nvmet: Can't set model number. TrueNAS is already assigned ``` The render raises `OSError: [Errno 22] Invalid argument` from `update_attrs()` inside `NvmetSubsysConfig.render`. `write_config()` stops there, before `NvmetNamespaceConfig.render`, so the new namespace directory is never created. `middlewared.log` records `Failed to render py:nvmet_kernel` with that `OSError` at the same time as the Proxmox task. `dmesg` on the TrueNAS host shows the model line at the same time. The plugin's existing reapply, `nvmet.subsys.update` of `allow_any_host` (the Issue #12 configfs workaround), runs this same render and stops on the same write. It cannot push the namespace into configfs while the model rewrite is failing. Any subsystem that already has a connected host is stuck this way. A subsystem whose configfs entry was written before the first connection can keep the namespaces it already had. New namespaces on a discovered subsystem do not appear until a render gets past the model update. ### Fix This is a TrueNAS middleware change, in `/usr/lib/python3/dist-packages/middlewared/plugins/nvmet/`. A TrueNAS upgrade replaces `/usr`, so the change has to be applied again. In `kernel.py`: - Import `errno`. - In `values_match()`, treat two values as equal when `str(oldval).strip() == str(newval).strip()`. The padded model is then left alone. - In `update_attrs()`, catch `OSError` around `write_text()`. If `errno` is `EINVAL` and the attribute is `attr_model`, `attr_firmware`, `attr_serial`, or `attr_ieee_oui`, continue. Those four latch after the first host connects. A rejected rewrite must not skip namespace publication. Any other write error still aborts the render. In `subsys.py` `model()`, store an empty product as `TrueNAS`: ```python return f'TrueNAS {system_product}'.strip()[:MAX_MODEL_LEN] ``` Restart middleware so the process loads the edited modules, then republish. A restart alone does not re-render configfs while the target is already running. ```text systemctl restart middlewared midclt call nvmet.global.reload ``` After the reload, `/sys/kernel/config/nvmet/subsystems/<nqn>/namespaces/<nsid>` exists and `enable` is `1`. `dmesg` shows `nvmet: adding nsid <n> to subsystem <nqn>` and no new "Can't set model number" line. On the Proxmox node, rescan the controller (`echo 1 > /sys/class/nvme/nvmeX/rescan_controller`, or the plugin's own rescan). `nvme list` shows the namespace, and its NGUID matches `device_nguid` from `nvmet.namespace.query`. The plugin can then bind the volid. --- And then I ran into the multi-megabyte bug, and Grok is fixing the nvme target portion of the modules for that.

Hopefully this is helpful and not just chasing down rabbit holes that have been fixed elsewhere.

sirbryan · October 8, 2026, 9:04pm

Apparently this is a TrueNAS middleware bug, not a plugin bug, and the patch won’t be backported to 25.10 series. So NVME with this plugin (without patching) looks like it will require 26.x.

Topic		Replies	Views
Proxmox VE against SCALE 25.10 over NVMe/TCP in production: a target-side MDTS finding, and notes on the storage plugin Apps and Virtualization	3	90	September 21, 2026
Proxmox Storage Plugin API Enhancements for dataset / zvol management TrueNAS General SCALE , Feature-Request , API	17	878	June 30, 2025
TrueNAS 25.10.6 is Now Available Announcements	28	2301	August 22, 2026
Storage plugin for Proxmox TrueNAS General SCALE , iSCSI , ProxMox	8	521	October 4, 2026
[Third Party Plugin] Add LIO or IET iSCSI target compatibility to SCALE so Proxmox "ZFS over ISCSI" can work natively Feature Requests SCALE , iSCSI , ZFS , feature-accepted	22	2175	January 6, 2026