From: Juan Quintela <quintela@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: TeLeMan <geleman@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] vmstate: fix vmstate_subsection_load
Date: Wed, 28 Jul 2010 15:51:45 +0200 [thread overview]
Message-ID: <m3tynjd89a.fsf@trasno.mitica> (raw)
In-Reply-To: <4C502CBC.3030005@redhat.com> (Paolo Bonzini's message of "Wed, 28 Jul 2010 15:12:28 +0200")
Paolo Bonzini <pbonzini@redhat.com> wrote:
> On 07/28/2010 02:51 PM, TeLeMan wrote:
> Even if they are mandatory, subsections still improve the situation
> here, because they provide a clean way to "branch" off an upstream
> vmstate version. At least the failure will be clear, because an
> unsupported subsection is easily detected when migrating to (or
> restoring with) upstream.
>
> Instead, for example RHEL5.5's "version 9" cpu save format will often
> crash upstream version 9 with a SIGSEGV.
Old kvm (pre start of merge with qemu) and qemu device versions are out
of sync. You can't migrate between them at all. Basically you can't
migrate from anything older than qemu-0.12. In qemu-0.12 firmware for
devices got moved to pci bars and memory layout changed in such a way
that it is not compatible at all.
Later, Juan.
prev parent reply other threads:[~2010-07-28 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 4:37 [Qemu-devel] [PATCH] vmstate: fix vmstate_subsection_load TeLeMan
2010-07-28 10:43 ` [Qemu-devel] " Juan Quintela
2010-07-28 11:23 ` TeLeMan
2010-07-28 11:51 ` Juan Quintela
2010-07-28 12:17 ` TeLeMan
2010-07-28 12:32 ` Juan Quintela
2010-07-28 12:51 ` TeLeMan
2010-07-28 13:12 ` Paolo Bonzini
2010-07-28 13:51 ` Juan Quintela [this message]
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=m3tynjd89a.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=geleman@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.