Okay, I will test this and update you hopefully tomorrow.
If possible please also share journalctl log from the source pve covering the migration time, for example:
root@pve :# journalctl --since "2026-08-xx xx:00:00" --until "2026-08-yy...
Hmm so the problem only occurs whenever you use qcow2, Interesting finding.
I am not aware of such problems when using snapshot-as-volume chain. I will try to reproduce and share my result.
Hmm I think this config should work as explained in thread [0].
Could you also share the output for vgs from both nodes.
0] https://forum.proxmox.com/threads/cant-seem-to-move-disks-between-local-lvm-storage.128770/post-563425
I am not entirely sure if i understand your question, do you mean to show how many cpu on the host pve server, and the remaining cpu to assign? Similar to how you see storage now?
The thing is, with the Virtualization you can overcommit CPU, and...
Did you test this and got the error above?
I assume since the migration network on a different network it should work, assuming you still have corosync quorum on the other nodes.
Always welcome. I will keep an eye on the thread.
In case it reoccur share journalctl again covering issue time:
root@pve2 :# journalctl --since "2026-07-xx xx:00" --until "2026-07-yy yy:yy" > /tmp/syslog.txt.gz
Okay, so 10.10.10.2 is still listed at the end of the mon_host line inside the [global] section.
You can use your preferaed editor and delete the ip: 10.10.10.2. make a copy of the file before making any change.