[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 2/3] runstate: introduce suspended state
From: |
Luiz Capitulino |
Subject: |
Re: [Qemu-devel] [PATCH 2/3] runstate: introduce suspended state |
Date: |
Fri, 4 May 2012 10:33:38 -0300 |
On Fri, 04 May 2012 10:50:08 +0200
Gerd Hoffmann <address@hidden> wrote:
> Hi,
>
> > However, I've ran into a different issue today: migrating while suspended
> > doesn't work. The target VM seems to be locked into S3, it just doesn't
> > resume.
> >
> > Haven't investigated yet, but this is expected to work, right?
>
> Well, that one is still on the todo list. There is the temporary
> stopgap to just resume the machine before migration so we don't have to
> migrate the is_suspended bit (not merged).
Ok.
> I plan to fix that properly, it needs some discussion to figure a sane
> way as we don't have a vmstate section for global state like this where
> we could attach a subsection to. That didn't happen yet though ...
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.