The source VM is locked when it was migrated to another PVE node

fuyou.han

New Member
Sep 8, 2025
8
0
1
Backgroud: I migrated a VM from one PVE node (pve1) to another node (pve2). After migrated sucess, the original VM (VM on pve1) show "locked" status [Config locked(migrate)].

Question: What's the reason it is locked? Cloud I use qm VMID unlock to unlock the VM? Any potential issue? (So that I have two copy VMs. They can backup with each other. Every time, I start only one VM.)
 
Last edited:
Hi fuyuo.han,
yes, that is the purpose oft
Code:
qm <vmid> unlock

The can be multiple reason for the behaviour.
The error message just states that the process was not able to release the lock.

Usually that is safe to do. If you like to investigate in advance you can us
Code:
ps -ef | grep <vmid>
to check, if there is still a process on the former hypervisor.

BR, Lucas
 
  • Like
Reactions: Onslow