Error migration the vms beetween 2 hosts in HA

elleti

New Member
Jun 29, 2026
7
0
1
Hello everyone,
i tried to solved this error by myself but nothing works, i changed something in these 2 hosts before having this error.
PROXMOX VERSION: 8.2.7
task started by HA resource agent
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @

Tell me if you need more info about the cluster and the 2 hosts pve.

Thank you guys
elleti
 

Attachments

  • error.txt
    error.txt
    1.2 KB · Views: 3
  • pv1.txt
    pv1.txt
    3.4 KB · Views: 0
  • pv1net.jpg
    pv1net.jpg
    65.6 KB · Views: 2
  • pv2.txt
    pv2.txt
    3.4 KB · Views: 0
  • pv2net.jpg
    pv2net.jpg
    62.3 KB · Views: 2
Try as mentioned in the error.txt to run:
Code:
~ # ssh-keygen -f "/etc/pve/nodes/pv2/ssh_known_hosts" -R "pv2"
 
Could you share the output for it
Sorry, via ssh from pv2 to pv1 i can access but from pv1 to pv2 says : Permission denied (publickey).
This is the output:
root@pv1:~# ssh-keygen -f "/etc/pve/nodes/pv2/ssh_known_hosts" -R "pv2"
# Host pv2 found: line 1
link /etc/pve/nodes/pv2/ssh_known_hosts to /etc/pve/nodes/pv2/ssh_known_hosts.old: Function not implemented
root@pv1:~#
 
Aha this make sense, Proxmox ve uses pmxcfs, its FUSE-based filesystem that stores configuration in a SQLite database and synchronizes it across the cluster.
There's a pve command to correct this, I will look for it and update you
 
Aha this make sense, Proxmox ve uses pmxcfs, its FUSE-based filesystem that stores configuration in a SQLite database and synchronizes it across the cluster.
There's a pve command to correct this, I will look for it and update you
thank you very much
 
thank you very much
ehy i fixed this problem right now, many months ago i configured the routing rules for the ssh access in the pv2, i removed the rules and i did this ssh-keygen -f "/root/.ssh/known_hosts" -R "pv2".
Thank you for your support Sir
 
Glad you managed to solve it! I didn't notice your reply before my last answer, but yeah, I'll keep it so it's easy to fetch that command in the future hehe
Thanks for sharing the fix.
 
Last edited: