On 04.02.26 19:46, Chaney, Ben wrote:
On 2/1/26, 11:21 AM, "Vladimir Sementsov-Ogievskiy" <[email protected] <mailto:[email protected]>> wrote:+ if (tap->incoming_fds && + (tap->fd || tap->fds || tap->helper || tap->script || + tap->downscript)) { + error_setg(errp, "incoming-fds is incompatible with " + "fd=, fds=, helper=, script=, downscript="); + return -1; + }Is it possible to relax this constraint at all? If so, I would prefer to allow script= and downscript= parameters to remain in place.
That possible, but this requires some additional logic I think. What if migration fails? Who should call downscript? Migration may be successful on source, and fail on target.. In this case, management tool usually resume stopped source. And in this case source should get again a responsibility to call downscript. So, I think it should be additional patch on top, which introduce support for script/downscript together with backend-transfer. -- Best regards, Vladimir
