On Mon, Jan 12, 2026 at 2:24 PM Ani Sinha <[email protected]> wrote: > @@ -2764,6 +2749,11 @@ sev_common_instance_init(Object *obj) > cgs->set_guest_policy = cgs_set_guest_policy; > > QTAILQ_INIT(&sev_common->launch_vmsa); > + > + /* add migration blocker */ > + error_setg(&sev_mig_blocker, > + "SEV: Migration is not implemented"); > + migrate_add_blocker(&sev_mig_blocker, &error_fatal); > }
.instance_init callbacks cannot have side effects. For patch 17 this is particularly bad because it causes a dangling pointer (the notifier is attached to an object that might not be ever used, and instead unreferenced/freed immediately), here it's just causing migration to be blocked forever. If you can find a good place to place these that would be best, otherwise you can add the usual "static bool first" method/hack. Paolo
