[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 15/28] migration: create new section to store glo

From: Christian Borntraeger
Subject: Re: [Qemu-devel] [PULL 15/28] migration: create new section to store global state
Date: Wed, 08 Jul 2015 12:19:18 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

Am 08.07.2015 um 12:14 schrieb Dr. David Alan Gilbert:
> * Christian Borntraeger (address@hidden) wrote:
>> Am 07.07.2015 um 15:08 schrieb Juan Quintela:
>>> This includes a new section that for now just stores the current qemu state.
>>> Right now, there are only one way to control what is the state of the
>>> target after migration.
>>> - If you run the target qemu with -S, it would start stopped.
>>> - If you run the target qemu without -S, it would run just after migration 
>>> finishes.
>>> The problem here is what happens if we start the target without -S and
>>> there happens one error during migration that puts current state as
>>> -EIO.  Migration would ends (notice that the error happend doing block
>>> IO, network IO, i.e. nothing related with migration), and when
>>> migration finish, we would just "continue" running on destination,
>>> probably hanging the guest/corruption data, whatever.
>>> Signed-off-by: Juan Quintela <address@hidden>
>>> Reviewed-by: Dr. David Alan Gilbert <address@hidden>
>> This is bisected to cause a regression on s390.
>> A guest restarts (booting) after managedsave/start instead of continuing.
>> Do you have any idea what might be wrong?
> I'd add some debug to the pre_save and post_load to see what state value is
> being saved/restored.

migrate_global_state_pre_save saved state: paused
migrate_global_state_post_load loaded state: paused

> Also, does that regression happen when doing the save/restore using the 
> same/latest
> git, or is it a load from an older version?

It the same git that fails.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]