After I upgraded my PDM CT instance to Beta, I migrated a VM between 2 nodes (PVE1 to PVE2). As I wanted to keep the source VM, I did not tick 'Delete Source' on the 'Migrate' form/webpage.
After the successful migration, in the PVE webpage, the source VM had the migration icon visible on it against it with the wording, Status : stopped, Config locked (migrate)
I then did did a migration from PVE2 to 1, again not deleting the source and I got the same result.
I next did a migration from PVE1 to 2, this time deleting the source and this worked with no error. I went the other way, again deleting the source and again I had no error. In both cases the source VM was deleted.
In all 4 cases the source VM was not running ie it was stopped.
I did not have this problem when I was on the Alpha version of PDM.
Below is the logfile of my 1st action ( In order to cut on the size of the log file, I've deleted most of the log details relating to the VM size being copied across)
2025-09-26 13:35:38 remote: started tunnel worker 'UPID
ve1:0001DEDF:001AB711:68D5EDEA:qmtunnel:500:root@pam!pdm-admin:'
tunnel: -> sending command "version" to remote
tunnel: <- got reply
2025-09-26 13:35:38 local WS tunnel version: 2
2025-09-26 13:35:38 remote WS tunnel version: 2
2025-09-26 13:35:38 minimum required WS tunnel version: 2
websocket tunnel started
2025-09-26 13:35:38 starting migration of VM 182 to node 'pve1' (192.168.1.11)
tunnel: -> sending command "bwlimit" to remote
tunnel: <- got reply
2025-09-26 13:35:38 found local disk 'pve2data:182/vm-182-disk-0.qcow2' (attached)
2025-09-26 13:35:38 copying local disk images
tunnel: -> sending command "disk-import" to remote
tunnel: <- got reply
tunnel: accepted new connection on '/run/pve/182.storage'
tunnel: requesting WS ticket via tunnel
tunnel: established new WS for forwarding '/run/pve/182.storage'
26648576 bytes (27 MB, 25 MiB) copied, 1 s, 26.6 MB/s
----to reduce the log size I've removed the lines detailing the file move ---
8580341760 bytes (8.6 GB, 8.0 GiB) copied, 318 s, 27.0 MB/s
2097536+0 records in
2097536+0 records out
8591507456 bytes (8.6 GB, 8.0 GiB) copied, 318.388 s, 27.0 MB/s
tunnel: -> sending command "query-disk-import" to remote
tunnel: done handling forwarded connection from '/run/pve/182.storage'
tunnel: <- got reply
2025-09-26 13:40:59 disk-import: Formatting '/mnt/pve/nvmedata/images/500/vm-500-disk-0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=8589934592 lazy_refcounts=off refcount_bits=16
tunnel: -> sending command "query-disk-import" to remote
tunnel: <- got reply
2025-09-26 13:41:00 disk-import: 44+519302 records in
tunnel: -> sending command "query-disk-import" to remote
tunnel: <- got reply
2025-09-26 13:41:02 disk-import: 44+519302 records out
tunnel: -> sending command "query-disk-import" to remote
tunnel: <- got reply
2025-09-26 13:41:03 disk-import: 8591507456 bytes (8.6 GB, 8.0 GiB) copied, 318.331 s, 27.0 MB/s
tunnel: -> sending command "query-disk-import" to remote
tunnel: <- got reply
2025-09-26 13:41:04 volume 'pve2data:182/vm-182-disk-0.qcow2' is 'nvmedata:500/vm-500-disk-0.qcow2' on the target
2025-09-26 13:41:04 mapped: net0 from vmbr0 to vmbr0
tunnel: -> sending command "config" to remote
tunnel: <- got reply
tunnel: -> sending command "unlock" to remote
tunnel: <- got reply
tunnel: -> sending command "quit" to remote
tunnel: <- got reply
2025-09-26 13:41:05 migration finished successfully (duration 00:05:27)
TASK OK
My environment is as below
PVE1 running 8.4.14
PVE2 running 9.0.10
I have not created a cluster with both of them as members - ie they are not 'linked' in any way
PDM is running as a CT container/instance on PVE1. The PDM version is 0.9.0
I created the CT instance using the " bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/proxmox-datacenter-manager.sh)" community helper script.
I then followed the instructions on https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta to upgrade this instance from Alpha to Beta.
Can you advise what I'm doing wrong.
After the successful migration, in the PVE webpage, the source VM had the migration icon visible on it against it with the wording, Status : stopped, Config locked (migrate)
I then did did a migration from PVE2 to 1, again not deleting the source and I got the same result.
I next did a migration from PVE1 to 2, this time deleting the source and this worked with no error. I went the other way, again deleting the source and again I had no error. In both cases the source VM was deleted.
In all 4 cases the source VM was not running ie it was stopped.
I did not have this problem when I was on the Alpha version of PDM.
Below is the logfile of my 1st action ( In order to cut on the size of the log file, I've deleted most of the log details relating to the VM size being copied across)
2025-09-26 13:35:38 remote: started tunnel worker 'UPID
ve1:0001DEDF:001AB711:68D5EDEA:qmtunnel:500:root@pam!pdm-admin:'tunnel: -> sending command "version" to remote
tunnel: <- got reply
2025-09-26 13:35:38 local WS tunnel version: 2
2025-09-26 13:35:38 remote WS tunnel version: 2
2025-09-26 13:35:38 minimum required WS tunnel version: 2
websocket tunnel started
2025-09-26 13:35:38 starting migration of VM 182 to node 'pve1' (192.168.1.11)
tunnel: -> sending command "bwlimit" to remote
tunnel: <- got reply
2025-09-26 13:35:38 found local disk 'pve2data:182/vm-182-disk-0.qcow2' (attached)
2025-09-26 13:35:38 copying local disk images
tunnel: -> sending command "disk-import" to remote
tunnel: <- got reply
tunnel: accepted new connection on '/run/pve/182.storage'
tunnel: requesting WS ticket via tunnel
tunnel: established new WS for forwarding '/run/pve/182.storage'
26648576 bytes (27 MB, 25 MiB) copied, 1 s, 26.6 MB/s
----to reduce the log size I've removed the lines detailing the file move ---
8580341760 bytes (8.6 GB, 8.0 GiB) copied, 318 s, 27.0 MB/s
2097536+0 records in
2097536+0 records out
8591507456 bytes (8.6 GB, 8.0 GiB) copied, 318.388 s, 27.0 MB/s
tunnel: -> sending command "query-disk-import" to remote
tunnel: done handling forwarded connection from '/run/pve/182.storage'
tunnel: <- got reply
2025-09-26 13:40:59 disk-import: Formatting '/mnt/pve/nvmedata/images/500/vm-500-disk-0.qcow2', fmt=qcow2 cluster_size=65536 extended_l2=off preallocation=metadata compression_type=zlib size=8589934592 lazy_refcounts=off refcount_bits=16
tunnel: -> sending command "query-disk-import" to remote
tunnel: <- got reply
2025-09-26 13:41:00 disk-import: 44+519302 records in
tunnel: -> sending command "query-disk-import" to remote
tunnel: <- got reply
2025-09-26 13:41:02 disk-import: 44+519302 records out
tunnel: -> sending command "query-disk-import" to remote
tunnel: <- got reply
2025-09-26 13:41:03 disk-import: 8591507456 bytes (8.6 GB, 8.0 GiB) copied, 318.331 s, 27.0 MB/s
tunnel: -> sending command "query-disk-import" to remote
tunnel: <- got reply
2025-09-26 13:41:04 volume 'pve2data:182/vm-182-disk-0.qcow2' is 'nvmedata:500/vm-500-disk-0.qcow2' on the target
2025-09-26 13:41:04 mapped: net0 from vmbr0 to vmbr0
tunnel: -> sending command "config" to remote
tunnel: <- got reply
tunnel: -> sending command "unlock" to remote
tunnel: <- got reply
tunnel: -> sending command "quit" to remote
tunnel: <- got reply
2025-09-26 13:41:05 migration finished successfully (duration 00:05:27)
TASK OK
My environment is as below
PVE1 running 8.4.14
PVE2 running 9.0.10
I have not created a cluster with both of them as members - ie they are not 'linked' in any way
PDM is running as a CT container/instance on PVE1. The PDM version is 0.9.0
I created the CT instance using the " bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/proxmox-datacenter-manager.sh)" community helper script.
I then followed the instructions on https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Upgrade_from_Alpha_to_Beta to upgrade this instance from Alpha to Beta.
Can you advise what I'm doing wrong.