From: Igor Mammedov <imammedo@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: dgilbert@redhat.com, qemu-devel@nongnu.org,
Pavel.Dovgaluk@ispras.ru, quintela@redhat.com
Subject: Re: [Qemu-devel] broken backward migration due to commit 461a275 "parallel: adding vmstate for save/restore"
Date: Fri, 19 Dec 2014 12:32:52 +0100 [thread overview]
Message-ID: <20141219123252.7dc36ea5@nial.brq.redhat.com> (raw)
In-Reply-To: <549408C8.70107@redhat.com>
On Fri, 19 Dec 2014 12:15:20 +0100
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>
> On 19/12/2014 12:03, Igor Mammedov wrote:
> > steps to reproduce:
> >
> > Current master source:
> > qemu-system-x86_64 -monitor stdio -M pc-i440fx-2.1
> > (qemu) stop
> > (qemu) migrate "exec:gzip -c > STATEFILE.gz"
> >
> > Target:
> > qemu-system-x86_64-2.1 -monitor stdio -M pc-i440fx-2.1 -incoming "exec: gzip -c -d STATEFILE.gz"
> >
>
> That's expected. Backwards migration is not supported by upstream, and
> there's no equivalent of subsections for entire devices.
>
> Just use "-parallel none".
ok
There is one more commit that breaks it, this time with subsection
6c3bff0 "exec: Save CPUState::exception_index field"
qemu: warning: error while loading state for instance 0x0 of device 'cpu_common'
the same reproducer with -parallel none
>
> Paolo
next prev parent reply other threads:[~2014-12-19 11:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 11:03 [Qemu-devel] broken backward migration due to commit 461a275 "parallel: adding vmstate for save/restore" Igor Mammedov
2014-12-19 11:15 ` Paolo Bonzini
2014-12-19 11:32 ` Igor Mammedov [this message]
2014-12-19 11:39 ` Igor Mammedov
2014-12-19 12:02 ` Paolo Bonzini
2014-12-19 12:42 ` Igor Mammedov
2014-12-19 12:49 ` Igor Mammedov
2014-12-19 13:21 ` Paolo Bonzini
2014-12-19 13:10 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141219123252.7dc36ea5@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).