On (Wed) 15 Jul 2015 [10:19:04], Juan Quintela wrote:
> Amit Shah <amit.s...@redhat.com> wrote:
> > On (Wed) 15 Jul 2015 [09:56:22], Juan Quintela wrote:
> >> Previous commit only stored a valid state for migration. It stored the
> >> empty string for savevm. Now, we are also storing the current state for
> >> savevm.
> >
> > Can you include some more information in the commit message? Like the
> > commit hash instead of previous commit, and what bug this fixes?
> >
> > Thanks,
> >
> > Amit
>
> What about:
Nice :-)
> Commit df4b1024526cae3479da3492d6371fd4a7324a03 introduced global_state
> section. But it only filled the state while doing migration. While
> doing a savevm, we stored an empty string as state. So when we did a
> loadvm, it complained that state was invalid.
>
> Fedora 21, 4.1.1, qemu 2.4.0-rc0
> > ../../configure --target-list="x86_64-softmmu"
>
> 068 2s ... - output mismatch (see 068.out.bad)
> --- /home/bos/jhuston/src/qemu/tests/qemu-iotests/068.out 2015-07-08
> 17:56:18.588164979 -0400
> +++ 068.out.bad 2015-07-09 17:39:58.636651317 -0400
> @@ -6,6 +6,8 @@
> QEMU X.Y.Z monitor - type 'help' for more information
> (qemu) savevm 0
> (qemu) quit
> +qemu-system-x86_64: Unknown savevm section or instance 'globalstate' 0
> +qemu-system-x86_64: Error -22 while loading VM state
> QEMU X.Y.Z monitor - type 'help' for more information
> (qemu) quit
> *** done
> Failures: 068
> Failed 1 of 1 tests
>
> Actually, there were two problems here:
> - we registered global_state too late for load_vm (fixed on another
> patch on the list)
> - we didn't store a valid state for savevm (fixed by this patch).
>
>
> Reported-by: John Snow <js...@redhat.com>
Thanks,
Amit
