VM Migration error

F

Frank-75

New Member
Dec 3, 2025
17
1
3
Code: 
026-08-01 19:39:00 use dedicated network address for sending migration traffic (172.21.21.7)
2026-08-01 19:39:00 starting migration of VM 101 to node 'pve-ML350pGen8' (172.21.21.7)
2026-08-01 19:39:01 found local disk 'LOCALSTORE_RAID5_VM:vm-101-disk-0.qcow2' (attached)
2026-08-01 19:39:01 found local disk 'LOCALSTORE_RAID5_VM:vm-101-disk-1.qcow2' (attached)
2026-08-01 19:39:01 found local disk 'LOCALSTORE_RAID5_VM:vm-101-disk-2.qcow2' (attached)
2026-08-01 19:39:01 copying local disk images
2026-08-01 19:39:01 ERROR: storage migration for 'LOCALSTORE_RAID5_VM:vm-101-disk-0.qcow2' to storage 'LOCALSTORE_RAID5_VM' failed - cannot migrate from storage type 'lvm' to 'lvm'
2026-08-01 19:39:01 aborting phase 1 - cleanup resources
2026-08-01 19:39:01 ERROR: migration aborted (duration 00:00:02): storage migration for 'LOCALSTORE_RAID5_VM:vm-101-disk-0.qcow2' to storage 'LOCALSTORE_RAID5_VM' failed - cannot migrate from storage type 'lvm' to 'lvm'
TASK ERROR: migration aborted

Hi all,
I converted the datastores of two separate servers with RAID storage from directories to LVM (volumegroup).
In between, I used an iSCSI-LVM datastore on NAS to move the VM disks then 'ive have migrated the VM to second server.
Now that I'm done, the servers have the same datastore configuration with the same name. I can no longer migrate the VMs from one server to the other with the error reported.
What am I missing? I switched to LVM to have more resilience between the two nodes (I have a qDevice acting as a witness), but instead I find myself in a worse situation. Why can't the system migrate VMs between two identically created LVM storage devices?
 
Code: 
dir: local
    path /var/lib/vz
    content iso,vztmpl
    shared 0

lvmthin: local-lvm
    thinpool data
    vgname pve
    content images,rootdir

cifs: NAS-DS216se
    path /mnt/pve/NAS-DS216se
    server 172.20.20.231
    share ProxMox-BackupLXC
    content backup,snippets
    domain NAS-DS216se
    prune-backups keep-all=1
    username bstoczio.ahahah

pbs: LXC-ProxMoxServerBackup
    datastore NAS-DS216se
    server 172.20.20.19
    content backup
    fingerprint 0d:-----------:dd
    namespace Backup-VM
    prune-backups keep-all=1
    username bassoreta@pbs

iscsi: iSCSI-NAS-DS213
    portal 172.20.20.232
    target iqn.2000-01.com.synology:DS213-3TB.Target-1--------
    content images

lvm: iSCSI-LVM
    vgname VolumeGroup-iSCSI-LVM
    base iSCSI-NAS-DS213:0.0.1.scsi-36001405218e9a--------
    content images,rootdir
    saferemove 0
    saferemove_throughput -52428800
    shared 1
    snapshot-as-volume-chain 1

lvm: LOCALSTORE_RAID5_VM
    vgname LOCALSTORE_RAID5_VM
    content images,rootdir
    nodes pve-ML350pGen8,DL160gen9
    saferemove 0
    shared 0
    snapshot-as-volume-chain 1

The LXC migration is working correctly.
This morning I rebooted one of the nodes because I had done the updates (damn, once a week! :-( ) ), but nothing changed in the VMs.
The two servers have a dedicated network (class 172.21) with direct communication (no switch) at 10Gb, so it's right that the class is different.

Code: 
2026-08-02 08:44:20 use dedicated network address for sending migration traffic (172.21.21.7)
2026-08-02 08:44:20 starting migration of CT 504 to node 'pve-ML350pGen8' (172.21.21.7)
2026-08-02 08:44:20 found local volume 'LOCALSTORE_RAID5_VM:vm-504-disk-0' (in current VM config)
2026-08-02 08:44:22   Logical volume "vm-504-disk-0" created.
2026-08-02 08:44:25 1025245184 bytes (1.0 GB, 978 MiB) copied, 3 s, 342 MB/s
--
2026-08-02 08:45:04 15747710976 bytes (16 GB, 15 GiB) copied, 42 s, 375 MB/s
2026-08-02 08:45:04 245760+0 records in
2026-08-02 08:45:04 245760+0 records out
2026-08-02 08:45:04 16106127360 bytes (16 GB, 15 GiB) copied, 43.0763 s, 374 MB/s
2026-08-02 08:45:09 186406+118708 records in
2026-08-02 08:45:09 186406+118708 records out
2026-08-02 08:45:09 16106127360 bytes (16 GB, 15 GiB) copied, 46.8497 s, 344 MB/s
2026-08-02 08:45:09 successfully imported 'LOCALSTORE_RAID5_VM:vm-504-disk-0'
2026-08-02 08:45:09 volume 'LOCALSTORE_RAID5_VM:vm-504-disk-0' is 'LOCALSTORE_RAID5_VM:vm-504-disk-0' on the target
2026-08-02 08:45:09 # /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve-ML350pGen8' -o 'UserKnownHostsFile=/etc/pve/nodes/pve-ML350pGen8/ssh_known_hosts' -o 'GlobalKnownHostsFile=none' root@172.21.21.7 pvesr set-state 504 \''{}'\'
  Logical volume "vm-504-disk-0" successfully removed.
2026-08-02 08:45:10 start final cleanup
2026-08-02 08:45:12 migration finished successfully (duration 00:00:52)
TASK OK
 
Last edited:
good morning, maybe your remount of or nas share don't work correct and now you are working local on the mount point?
 
The storage is not shared.
I enabled the option and then disabled it to verify that I hadn't accidentally moved the VMs to the wrong node with the files on the other. But that's not the case.
Anyway: CT (LXC) VMs, Linux VM migrations, no problem, VM migrations with RAW disks have no issues. However, the problem is with Windows VMs with QCOW2 format disks (essential because I need snapshots).
@news: If I switch from LVM NAS storage, no problem except for the longer migration time (it's a 1GB network).
@longer: what's is vgs (excuse i don't understand)
 
Last edited:
You must log in or register to reply here.
Top Bottom
Back