"Dr. David Alan Gilbert" wrote:
> * Juan Quintela (quint...@redhat.com) wrote:
>> We use global state in both savevm & migration. The easiest way is to
>> put the setup in a single place.
>>
>> Signed-off-by: Juan Quintela
>
> I don't think this works; I think pre-save is called after the migr
* Juan Quintela (quint...@redhat.com) wrote:
> We use global state in both savevm & migration. The easiest way is to
> put the setup in a single place.
>
> Signed-off-by: Juan Quintela
I don't think this works; I think pre-save is called after the migration
code has changed the runstate, so yo
We use global state in both savevm & migration. The easiest way is to
put the setup in a single place.
Signed-off-by: Juan Quintela
---
migration/migration.c | 30 --
1 file changed, 12 insertions(+), 18 deletions(-)
diff --git a/migration/migration.c b/migration/mi
