Re: [pve-devel] PVE child process behavior question

[Denis Kanchev via pve-devel <pve-devel@lists.proxmox.com>]

[-- Attachment #1: Type: message/rfc822, Size: 6420 bytes --]

From: Denis Kanchev <denis.kanchev@storpool.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, Wolfgang Bumiller <w.bumiller@proxmox.com>
Subject: Re: [pve-devel] PVE child process behavior question
Date: Wed, 4 Jun 2025 15:52:14 +0300
Message-ID: <CAHXTzukATnAznNmeTq2YdJqL0KRXk7e=AFKW7MNQaa9f=3+n+w@mail.gmail.com>

> 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.

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel