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.
So at the moment, the daemon successfully restarted, and running for more than hour.
Looking at journalctl may provide related information, so the last crash from shared crash info was at 2026-07-27 23:21, therefore take look what happend before...
Not really sure, but did you verify different port portv2 and v3 to see if any differences?
Just my 2 cent, Do you have IPMI/iDRAC? maybe you can attempt from IPMI console and check this issue after booting.
The recommendation is to use virtio dirvers for best performance:
https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices
In the wiki its also mentioned:
"the latest VirtIO iso do not include drivers for Windows 2003. You need to download...