On 09/05/23 3:46 pm, Juan Quintela wrote:
> "tejus.gk" wrote:
>> There are places in the code where the migration is marked failed with
>> MIGRATION_STATUS_FAILED, but the failiure reason is never updated. Hence
>> libvirt doesn't know why the migration failed when it queries for it.
>>
>> Sign
On 08/05/23 10:19 pm, Thomas Huth wrote:
> Hi!
>
> On 08/05/2023 17.32, tejus.gk wrote:
>> There are places in the code where the migration is marked failed with
>> MIGRATION_STATUS_FAILED, but the failiure reason is never updated. Hence
>
> s/failiure/failure/
Ack
>
>> libvirt doesn't know
"tejus.gk" wrote:
> There are places in the code where the migration is marked failed with
> MIGRATION_STATUS_FAILED, but the failiure reason is never updated. Hence
> libvirt doesn't know why the migration failed when it queries for it.
>
> Signed-off-by: tejus.gk
> ---
> migration/migration.c
Hi!
On 08/05/2023 17.32, tejus.gk wrote:
There are places in the code where the migration is marked failed with
MIGRATION_STATUS_FAILED, but the failiure reason is never updated. Hence
s/failiure/failure/
libvirt doesn't know why the migration failed when it queries for it.
Signed-off-by: