From: Lorne Guse via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"m.carrara@proxmox.com" <m.carrara@proxmox.com>,
Morgan Littlewood <morgan@truenas.com>
Cc: Lorne Guse <boomshankerx@hotmail.com>
Subject: Re: [pve-devel] TrueNAS over iSCSI: Issue migrating VMs
Date: Tue, 7 Oct 2025 21:03:45 +0000 [thread overview]
Message-ID: <mailman.741.1759871916.390.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <DM6PR17MB34664A8623CEC8CBE6FD7AFFD0E0A@DM6PR17MB3466.namprd17.prod.outlook.com>
[-- Attachment #1: Type: message/rfc822, Size: 11443 bytes --]
From: Lorne Guse <boomshankerx@hotmail.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, "m.carrara@proxmox.com" <m.carrara@proxmox.com>, Morgan Littlewood <morgan@truenas.com>
Subject: Re: TrueNAS over iSCSI: Issue migrating VMs
Date: Tue, 7 Oct 2025 21:03:45 +0000
Message-ID: <DM6PR17MB34666333D72DBD08D76DA2D9D0E0A@DM6PR17MB3466.namprd17.prod.outlook.com>
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 <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?
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next parent reply other threads:[~2025-10-07 21:18 UTC|newest]
Thread overview: 2+ 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 [this message]
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=mailman.741.1759871916.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=boomshankerx@hotmail.com \
--cc=m.carrara@proxmox.com \
--cc=morgan@truenas.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