On Tue, 6 Jan 2026 at 20:39, Peter Xu <[email protected]> wrote:
> Copying Dan and Jiri in case ...
* Thank you for copying.
>> } else if (s->current_state == ACTIVE && s->trigger ==
>> 'error-occurred') {
>> s->current_state = STOP
>> s->reason = "Error occurred, migration failed"
>
> We can't change status that were already used, like FAILED. Libvirt and
> all mgmt may rely on it.
* True; If we decide to go in that direction, we'll have to tell
libvirtd(8) and others about new states.
> Personally I don't see much benefit on adding a new "trigger" internal API.
> If we want to forbid some state machine transitions, we can use a
> transition map. Said that, IMHO it's separate from what we're discussing
> here.
* If we can reduce/rationalise the current 17-18 states and related
complexity, it'll help to simplify things.
Thank you.
---
- Prasad
