TrueNAS Storage Plugin

warlocksyno said:
@SInisterPisces @boomshankerx

Hmm, weird. Nah, it works fine afaik. I've been using TPM+EFI+Q35 based VMs on it just fine.
Click to expand...
Having looked at your code a bit I think your plugin manages iSCSI at a lower level than the native ZFS over iSCSI implementation. Proxmox relies on iscsidirect to make the connections.

iscsidirect in QEMU refers to using the built-in iSCSI initiator (via libiscsi) to allow a virtual machine to connect directly to an iSCSI Logical Unit Number (LUN). This bypasses the host operating system's storage stack, meaning the host does not mount the LUN; instead, QEMU manages the connection directly when the VM starts.
Click to expand...
 
Last edited:
boomshankerx said:
Having looked at your code a bit I think your plugin manages iSCSI at a lower level than the native ZFS over iSCSI implementation. Proxmox relies on iscsidirect to make the connections.
Click to expand...
Proxmox has added support for TPM storage for ZFS over iSCSI in qemu-server: 9.1.10
https://bugzilla.proxmox.com/show_bug.cgi?id=3662

Confirmed this fix is now in the no-subscription repo. Confirmed working on my test systems.
 
  • Like
Reactions: SInisterPisces
I am trying to configure nvme/tcp for my truenas scale installation, and the plugin, as well as the manual storage configuration seems to be failing with a 101 error. I think this may be because I am using non-standard ports for my truenas installation (83/http and 447/https). From what I can tell there is not a way to enter a port using the script (validation of the IP fails), nor manually in storage.cfg (entering IP:Port breaks the proxmox UI).

Is there a way to make the plugin work with non-standard ports, or perhaps make an enhancement request?
 
You must log in or register to reply here.
Top Bottom
Back