From: "Richard W.M. Jones" <rjones@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: peter.maydell@linaro.org, nick@bytemark.co.uk, lersek@redhat.com,
qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] wdt_i6300esb: fix vmstate versioning
Date: Wed, 22 May 2013 17:46:38 +0100 [thread overview]
Message-ID: <20130522164638.GB28893@redhat.com> (raw)
In-Reply-To: <1369240371-21253-1-git-send-email-mdroth@linux.vnet.ibm.com>
On Wed, May 22, 2013 at 11:32:51AM -0500, Michael Roth wrote:
> When this VMSD was introduced it's version fields were set to
> sizeof(I6300State), making them essentially random from build to build,
> version to version.
>
> To fix this, we lock in a high version id and low minimum version id to
> support old->new migration from all prior versions of this device's
> state. This should work since the device state has not changed since
> its introduction.
>
> The potentially breaks migration from 1.5+ to 1.5, but since the
> versioning was essentially random prior to this patch, new->old
> migration was not consistently functional to begin with.
>
> Reported-by: Nicholas Thomas <nick@bytemark.co.uk>
> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
ACK. I guess no one uses watchdog much, or they don't try to
migrate those guests :-(
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into KVM guests.
http://libguestfs.org/virt-v2v
next prev parent reply other threads:[~2013-05-22 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 16:32 [Qemu-devel] [PATCH v2] wdt_i6300esb: fix vmstate versioning Michael Roth
2013-05-22 16:46 ` Richard W.M. Jones [this message]
2013-05-22 19:40 ` Laszlo Ersek
2013-05-23 11:24 ` Amit Shah
2013-06-11 21:53 ` mdroth
2013-06-18 18:07 ` mdroth
2013-06-18 18:43 ` Anthony Liguori
2013-06-18 18:47 ` Juan Quintela
2013-06-21 15:34 ` Anthony Liguori
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=20130522164638.GB28893@redhat.com \
--to=rjones@redhat.com \
--cc=lersek@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nick@bytemark.co.uk \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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).