--- Begin Message ---
I managed to answer my own question. I implemented the shared option and
explicitly set it to 1. I found it in the documentation but got confused when
it indicated that all network types are automatically marked shared in the
background.
Migration now works as expected.
--
Lorne Guse
________________________________
From: Lorne Guse <[email protected]>
Sent: Tuesday, October 7, 2025 2:25:33 PM
To: Proxmox VE development discussion <[email protected]>;
[email protected] <[email protected]>; Morgan Littlewood
<[email protected]>
Subject: TrueNAS over iSCSI: Issue migrating VMs
I'm experiencing an issue migrating VMs.
2025-10-07 14:12:08 use dedicated network address for sending migration traffic
(10.11.11.6)
2025-10-07 14:12:09 starting migration of VM 103 to node 'prox2' (10.11.11.6)
2025-10-07 14:12:09 found local disk 'nas:vm-103-disk-0' (attached)
2025-10-07 14:12:09 ERROR: Problem found while scanning volumes - can't migrate
'nas:vm-103-disk-0' - storage type 'truenas' not supported
2025-10-07 14:12:09 aborting phase 1 - cleanup resources
2025-10-07 14:12:09 ERROR: migration aborted (duration 00:00:01): Problem found
while scanning volumes - can't migrate 'nas:vm-103-disk-0' - storage type
'truenas' not supported
TASK ERROR: migration aborted
I've been bouncing back and forth between the patch plugin and native plugin. I
thought I had tested migrations with the new plugin in earlier versions.
Does my storage have to be explicitly marked as shared?
--- End Message ---
_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
