VM migration error / atomic file exist

M

Mihoo

New Member
Dec 1, 2025
2
0
1
Hi Guys,

I'm trying to migrate running VM from NodeC to NodeD and have this error where atomic file exists on NodeD.
I double checked and there is NO file mentioned on NodeD.

Logs attached.


2025-12-01 14:51:40 use dedicated network address for sending migration traffic (10.10.10.4)
2025-12-01 14:51:41 starting migration of VM 103 to node 'NodeD-r3-s19' (10.10.10.4)
2025-12-01 14:51:41 starting VM 103 on remote node 'NodeD-r3-s19'







2025-12-01 14:51:44 [NodeD-r3-s19] close (rename) atomic file '/etc/pve/nodes/NodeD-r3-s19/qemu-server/103.conf' failed: File exists
2025-12-01 14:51:44 ERROR: online migrate failure - remote command failed with exit code 255
2025-12-01 14:51:44 aborting phase 2 - cleanup resources
2025-12-01 14:51:44 migrate_cancel
2025-12-01 14:51:45 ERROR: migration finished with problems (duration 00:00:05)
TASK ERROR: migration problems



netdev net0: not adding 'host_mtu' parameter for migration compat
/dev/rbd0
migration listens on unix:/run/qemu-server/103.migrate
No VM state set, removing left-over option 'runningmachine'
No VM state set, removing left-over option 'runningcpu'

TASK ERROR: close (rename) atomic file '/etc/pve/nodes/NodeD-r3-s19/qemu-server/103.conf' failed: File exists


root@NodeC-r3-s19:~# pvecm status
Cluster information
-------------------
Name: pve-a-waw
Config Version: 4
Transport: knet
Secure auth: on

Quorum information
------------------
Date: Mon Dec 1 15:13:56 2025
Quorum provider: corosync_votequorum
Nodes: 4
Node ID: 0x00000003
Ring ID: 1.56
Quorate: Yes

Votequorum information
----------------------
Expected votes: 4
Highest expected: 4
Total votes: 4
Quorum: 3
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.10.10.1
0x00000002 1 10.10.10.2
0x00000003 1 10.10.10.3 (local)
0x00000004 1 10.10.10.4

Best regards,
Mihoo
 

Attachments

Thank You @bbgeek17 for you answer.

I don't see any duplication. This is what I have:

root@NodeC-r3-s19:/etc/pve/nodes/NodeA-r3-s19/qemu-server# ls -al
total 1
drwxr-xr-x 2 root www-data 0 Sep 25 15:29 .
drwxr-xr-x 2 root www-data 0 Sep 25 15:29 ..
-rw-r----- 1 root www-data 1791 Nov 6 13:36 100.conf
-rw-r----- 1 root www-data 706 Nov 18 18:54 104.conf
root@NodeC-r3-s19:/etc/pve/nodes/NodeA-r3-s19/qemu-server# cd ../../NodeB-r3-s19/qemu-server/
root@NodeC-r3-s19:/etc/pve/nodes/NodeB-r3-s19/qemu-server# ls -al
total 1
drwxr-xr-x 2 root www-data 0 Oct 2 12:56 .
drwxr-xr-x 2 root www-data 0 Oct 2 12:56 ..
-rw-r----- 1 root www-data 673 Nov 27 21:42 102.conf
root@NodeC-r3-s19:/etc/pve/nodes/NodeB-r3-s19/qemu-server# cd ../../NodeC-r3-s19/qemu-server/
root@NodeC-r3-s19:/etc/pve/nodes/NodeC-r3-s19/qemu-server# ls -al
total 1
drwxr-xr-x 2 root www-data 0 Oct 2 15:06 .
drwxr-xr-x 2 root www-data 0 Oct 2 15:06 ..
-rw-r----- 1 root www-data 762 Dec 1 14:54 103.conf
root@NodeC-r3-s19:/etc/pve/nodes/NodeC-r3-s19/qemu-server# cd ../../NodeD-r3-s19/qemu-server/
root@NodeC-r3-s19:/etc/pve/nodes/NodeD-r3-s19/qemu-server# ls -al
total 0
drwxr-xr-x 2 root www-data 0 Oct 2 15:16 .
drwxr-xr-x 2 root www-data 0 Oct 2 15:16 ..

Best regards,
Mihoo
 
Hi,
are your nodes running the latest updates? Please share the output of qm config 103 as well as from both source and target of the migration, the system logs around the time of the issue and pveversion -v.
 
You must log in or register to reply here.
Top Bottom