We have some internal tools we need to setup/tear down on the time the domain stops on the source and starts on the destination, so I don't believe full native support would fit.
An alternative could be to have an option to wait for a resume operation to progress as a client-defined migration flag exposing the pre-switchover state. This way maybe we could work it as a client feature rather than a hook? I'm happy to work on a patch and I'm open for guidance on what to do here. > On 16 Oct 2025, at 18:44, Peter Krempa <[email protected]> wrote: > > > >> On Thu, Oct 16, 2025 at 14:43:56 +0000, Rogério Vinhal Nunes via Devel wrote: >> Hello, >> >> I’m looking into the libvirt hooks that are available to make use of during >> a live migration, but there's only hooks on migration begin and migration >> end. On qemu directly I’m able to use pause-before-switchover migration >> capability to run a custom operation just before it moves to the >> destination, but within libvirt it seems that while this is leveraged >> internally, it’s not currently exposed to the client in a way I can use. >> >> Does anyone have any suggestions on how I could expose this to the client in >> a generic and sensible way? > > Yes this is currently not available. > > Can you elaborate what you'd want to use it for? E.g. what we don't > support that could be solved by this. > > We prefer if things work without hooks as hooks are really clunky for > users to setup properly and maybe your case can be improved by some > native support. >
