Message ID | 4FA3DF92.9080208@redhat.com |
---|---|
State | New |
Headers | show |
On Fri, 04 May 2012 15:54:26 +0200 Gerd Hoffmann <kraxel@redhat.com> wrote: > Hi, > > > There's a quite simple and stupid way to do it. When we migrate an stopped > > VM, it's automatically resumed on the target. We could do the same for a > > suspended VM: we could automatically resume it before migrating, as you said > > above. > > > > That's not the behavior I'd expect, I mean I would expect a stopped VM to > > remain stopped after it's migrated. But it has always been this way and I'm > > afraid we can't change this. > > Oh, I wasn't aware that a stopped vm behaves the same way. So resuming > on migration is sort-of bug compatible then. Patch attached. Will you > add it to your series or should I submit it separately? I can add it to my series, thanks Gerd!
diff --git a/migration.c b/migration.c index 94f7839..f9e968e 100644 --- a/migration.c +++ b/migration.c @@ -252,6 +252,7 @@ static void migrate_fd_put_ready(void *opaque) int old_vm_running = runstate_is_running(); DPRINTF("done iterating\n"); + qemu_system_wakeup_request(QEMU_WAKEUP_REASON_OTHER); vm_stop_force_state(RUN_STATE_FINISH_MIGRATE); if (qemu_savevm_state_complete(s->file) < 0) {