From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, lersek@redhat.com,
qemu-stable@nongnu.org, dgilbert@redhat.com, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.1 2/2] acpi: mark ACPI tables ROM blob as extend-able on migration
Date: Fri, 25 Jul 2014 19:37:41 +0200 [thread overview]
Message-ID: <53D295E5.20900@redhat.com> (raw)
In-Reply-To: <1406303338-13212-3-git-send-email-imammedo@redhat.com>
Il 25/07/2014 17:48, Igor Mammedov ha scritto:
> It fixes migration failure for machine type pc-i440fx-1.7 from
> QEMU 1.7/2.0 to QEMU 2.1
>
> Migration fails due to ACPI tables size grows across 1.7-2.1
> versions. That causes ACPI tables ROM blob to change its size
> differently for the same configurations on different QEMU versions.
> As result migration code bails out when attempting to load
> smaller ROM blob into a bigger one on a newer QEMU.
> To trigger failure it's enough to add pci-bridge device to QEMU CLI
>
> Marking ACPI tables ROM blob as extend-able on migration allows
> QEMU to load smaller ACPI tables from QEMU 1.7/2.0, fixing
> forward migration failure introduced since 2.0 which affects
> only configurations that cause ACPI ROM blob size change.
This works in this case, and it is more friendly to downstreams indeed.
It also is simpler, at least on the surface. I think the ramifications
could be a bit larger than with my own patches, but still I guess it's
more appropriate at this point of the release cycle.
It doesn't handle the case of ACPI tables that shrink, which can happen
as well. I guess if this ever happens we can just hard-code the table
size of the "old" versions to something big enough (64K?) and keep using
fine-grained sizing.
I'd like a day or two to mull about it, but I have it even if the
patches are applied. Peter, feel free to go ahead with Igor's patches.
Paolo
next prev parent reply other threads:[~2014-07-25 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 15:48 [Qemu-devel] [PATCH for-2.1 0/2] Fix migration failure due to ACPI tables size changes Igor Mammedov
2014-07-25 15:48 ` [Qemu-devel] [PATCH for-2.1 1/2] migration: load smaller RAMBlock to a bigger one if permitted Igor Mammedov
2014-07-25 17:56 ` Laszlo Ersek
2014-07-28 7:40 ` Igor Mammedov
2014-07-28 8:11 ` Laszlo Ersek
2014-07-25 15:48 ` [Qemu-devel] [PATCH for-2.1 2/2] acpi: mark ACPI tables ROM blob as extend-able on migration Igor Mammedov
2014-07-25 17:37 ` Paolo Bonzini [this message]
2014-07-28 7:56 ` Igor Mammedov
2014-07-28 8:16 ` Paolo Bonzini
2014-07-25 17:58 ` Laszlo Ersek
2014-11-03 17:36 ` Dr. David Alan Gilbert
2014-11-04 16:30 ` Paolo Bonzini
2014-11-04 16:46 ` Michael S. Tsirkin
2014-11-04 16:54 ` Paolo Bonzini
2014-11-04 17:25 ` Michael S. Tsirkin
2014-11-04 17:35 ` Paolo Bonzini
2014-11-04 17:42 ` Michael S. Tsirkin
2014-07-25 16:17 ` [Qemu-devel] [PATCH for-2.1 0/2] Fix migration failure due to ACPI tables size changes Laszlo Ersek
2014-07-26 7:03 ` 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=53D295E5.20900@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--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).