On 29.04.24 16:06, Fabiano Rosas wrote:
Vladimir Sementsov-Ogievskiy writes:
On 25.04.24 23:30, Fabiano Rosas wrote:
@@ -797,13 +801,18 @@ fail:
MIGRATION_STATUS_FAILED);
migration_incoming_state_destroy();
-if (migrate_has_error(s)) {
-
Vladimir Sementsov-Ogievskiy writes:
> On 25.04.24 23:30, Fabiano Rosas wrote:
>>> @@ -797,13 +801,18 @@ fail:
>>> MIGRATION_STATUS_FAILED);
>>> migration_incoming_state_destroy();
>>>
>>> -if (migrate_has_error(s)) {
>>> -
On 25.04.24 23:30, Fabiano Rosas wrote:
@@ -797,13 +801,18 @@ fail:
MIGRATION_STATUS_FAILED);
migration_incoming_state_destroy();
-if (migrate_has_error(s)) {
-WITH_QEMU_LOCK_GUARD(>error_mutex) {
-error_report_err(s->error);
+if
Vladimir Sementsov-Ogievskiy writes:
> Now we do set MIGRATION_FAILED state, but don't give a chance to
> orchestrator to query migration state and get the error.
>
> Let's provide a possibility for QMP-based orchestrators to get an error
> like with outgoing migration.
>
> For
Vladimir Sementsov-Ogievskiy writes:
> Now we do set MIGRATION_FAILED state, but don't give a chance to
> orchestrator to query migration state and get the error.
>
> Let's provide a possibility for QMP-based orchestrators to get an error
> like with outgoing migration.
>
> For
Now we do set MIGRATION_FAILED state, but don't give a chance to
orchestrator to query migration state and get the error.
Let's provide a possibility for QMP-based orchestrators to get an error
like with outgoing migration.
For hmp_migrate_incoming(), let's enable the new behavior: HMP is not
