[PATCH docs v2 4/5] zfsnvme: document target reboot prerequisites

[Joaquin Varela <joaquinvarela@neatech.ar>]

Document module loading and configfs availability on the Linux nvmet
target. Clarify that target configuration is derived state reconstructed
from ZFS properties during activation.

Signed-off-by: Joaquin Varela <joaquinvarela@neatech.ar>
---
 pve-storage-zfsnvme.adoc | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/pve-storage-zfsnvme.adoc b/pve-storage-zfsnvme.adoc
index 35f09f8..edfb938 100644
--- a/pve-storage-zfsnvme.adoc
+++ b/pve-storage-zfsnvme.adoc
@@ -26,6 +26,21 @@ modules. Configure root SSH access like for the ZFS over iSCSI backend. The key
 for the server address is stored at
 `/etc/pve/priv/zfs/<server>_id_rsa`.
 
+The NVMe target modules and configfs must be available after a target reboot,
+before a {pve} node attempts to reconcile the exported namespaces. On a Linux
+target using systemd, load the transport at boot and verify the configfs mount:
+
+----
+# echo nvmet_tcp >/etc/modules-load.d/pve-nvmet.conf
+# modprobe nvmet_tcp
+# mountpoint /sys/kernel/config
+----
+
+The target configuration below configfs is derived state. It does not need a
+separate persistence service: after the module and ZFS pool are available, the
+backend reconstructs subsystems, namespaces, UUIDs, ACLs, and ports from the
+ZFS user properties during activation.
+
 Each {pve} node needs `nvme-cli`, the `nvme-tcp` module, native NVMe multipath,
 a unique `/etc/nvme/hostnqn`, and `/etc/nvme/hostid`. Interface names listed in
 the storage configuration must exist on every node where the storage is
-- 
2.54.0.windows.1