From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Lorne Guse" <boomshankerx@hotmail.com>,
"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Morgan Littlewood" <morgan@truenas.com>
Subject: Re: [pve-devel] TrueNAS over iSCSI: Issue migrating VMs
Date: Mon, 13 Oct 2025 14:18:10 +0200 [thread overview]
Message-ID: <DDH6SIJNX7E0.19N0659SG86E9@proxmox.com> (raw)
In-Reply-To: <DM6PR17MB34666333D72DBD08D76DA2D9D0E0A@DM6PR17MB3466.namprd17.prod.outlook.com>
On Tue Oct 7, 2025 at 11:03 PM CEST, Lorne Guse wrote:
> 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.
Do you mean this chapter [0]?
Could you perhaps let me know what in particular was confusing? Maybe I
can rephrase some things there.
FWIW, making it possible to *always* mark a plugin's storage configs as
shared (like the built-in ones) is on my backlog, but I haven't gotten
around to implementing that yet.
>
> Migration now works as expected.
Glad it works!
[0]: https://pve.proxmox.com/mediawiki/index.php?title=Storage_Plugin_Development:_Writing_a_Storage_Plugin_for_SSHFS#Supporting_Storage_Sharing
>
> --
> Lorne Guse
> ________________________________
> From: Lorne Guse <boomshankerx@hotmail.com>
> Sent: Tuesday, October 7, 2025 2:25:33 PM
> To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>; m.carrara@proxmox.com <m.carrara@proxmox.com>; Morgan Littlewood <morgan@truenas.com>
> 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?
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-10-13 12:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM6PR17MB34664A8623CEC8CBE6FD7AFFD0E0A@DM6PR17MB3466.namprd17.prod.outlook.com>
2025-10-07 21:03 ` Lorne Guse via pve-devel
[not found] ` <DM6PR17MB34666333D72DBD08D76DA2D9D0E0A@DM6PR17MB3466.namprd17.prod.outlook.com>
2025-10-13 12:18 ` Max R. Carrara [this message]
2025-10-17 3:16 ` Lorne Guse via pve-devel
[not found] ` <DM6PR17MB34667EB2510D115D2D995FB2D0F6A@DM6PR17MB3466.namprd17.prod.outlook.com>
2025-10-17 10:57 ` Max R. Carrara
2025-10-07 20:25 Lorne Guse via pve-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DDH6SIJNX7E0.19N0659SG86E9@proxmox.com \
--to=m.carrara@proxmox.com \
--cc=boomshankerx@hotmail.com \
--cc=morgan@truenas.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox