[pve-devel] PVE child process behavior question
    Denis Kanchev 
    denis.kanchev at storpool.com
       
    Wed Jun  4 14:52:14 CEST 2025
    
    
  
> how are you hooking the migration state to know whether deactivation
should be done or not?
By using the VM property "lock" which must be "migrate":
PVE::Cluster::get_guest_config_properties(['lock']);
> qm start (over SSH, is this being killed?)
> -> start_vm task worker (or this?)
> --> activate_volume
> --> fork, enter systemd scope, run_command to execute the kvm process
> ---> kvm (or this?)
The parent of the process that is executing activate_volume() is killed, in
this case it should be qm start.
    
    
More information about the pve-devel
mailing list