On Tue, Apr 07, 2026 at 15:11:45 +0200, Peter Krempa via Devel wrote:
On Sat, Mar 21, 2026 at 15:09:03 +0100, Guy Godfroy wrote:
Currently, the hook script with the "migrate" operation is only called on the destination host at the beginning of incoming migration. This makes it impossible for the source host to prepare for migration, for example to change storage locks from exclusive to shared mode when using shared LVM storage with lvmlockd.
Add a hook call on the source host at the beginning of outgoing migration using the new "migrate-outgoing" operation. The hook is called with "source" as the extra argument and "begin" as the sub-operation.
I don't think having the 'source' extra argument makes sense once we have the whole separate 'migrate-outgoing' operation.
So since that field is used to signal failure in the next patch ... I guess it makes sense here but I'd change it to either 'start' or 'begin'.