From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
qemu-devel@nongnu.org, Marcel Apfelbaum <marcel.a@redhat.com>
Subject: Re: [Qemu-devel] [PATCH RESEND v2 1/3] pc: Set hw_version on all machine classes
Date: Mon, 9 Nov 2015 22:45:17 +0200 [thread overview]
Message-ID: <20151109222208-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <1446233769-7892-2-git-send-email-ehabkost@redhat.com>
On Fri, Oct 30, 2015 at 05:36:07PM -0200, Eduardo Habkost wrote:
> In 2012, QEMU had a bug where it exposed QEMU version information to the
> guest, meaning a QEMU upgrade would expose different hardware to the
> guest OS even if the same machine-type is being used.
>
> The bug was fixed by commit 93bfef4c6e4b23caea9d51e1099d06433d8835a4, on
> all machines up to pc-1.0. But we kept introducing the same bug on all
> newer machines since then. That means we are breaking guest ABI every
> time QEMU was upgraded.
>
> Fix this by setting the hw_version on all PC machines, making sure the
> hardware won't change when upgrading QEMU.
>
> Note that QEMU_VERSION was "1.0" in QEMU 1.0, but starting on QEMU
> 1.1.0, it started following the "x.y.0" pattern. We have to follow it,
> to make sure we use the right QEMU_VERSION string from each QEMU
> release.
>
> The 2.5 machine classes could have hw_version unset, because the default
> value for qemu_get_version() is QEMU_VERSION. But I decided to set it
> explicitly to QEMU_VERSION so we don't forget to update it to "2.5.0"
> after we release 2.5.0 and create a 2.6 machine class.
>
> Reported-by: Laszlo Ersek <lersek@redhat.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
Ouch.
I really don't want even more churn with each version.
Can't we use the name supplied to DEFINE_PC_MACHINE at least for future
machine types?
Or maybe we should stop exposing the version to guests - does it really
have any value given it has been so unreliable historically?
How about:
---
diff --git a/util/osdep.c b/util/osdep.c
index 0092bb6..4dc635d 100644
--- a/util/osdep.c
+++ b/util/osdep.c
@@ -52,7 +52,7 @@ extern int madvise(caddr_t, size_t, int);
static bool fips_enabled = false;
-static const char *qemu_version = QEMU_VERSION;
+static const char *qemu_version = "QEMU";
int socket_set_cork(int fd, int v)
{
next prev parent reply other threads:[~2015-11-09 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 19:36 [Qemu-devel] [PATCH RESEND v2 0/3] pc: Set hw_version on all machine classes Eduardo Habkost
2015-10-30 19:36 ` [Qemu-devel] [PATCH RESEND v2 1/3] " Eduardo Habkost
2015-11-09 20:45 ` Michael S. Tsirkin [this message]
2015-11-10 17:30 ` Eduardo Habkost
2015-10-30 19:36 ` [Qemu-devel] [PATCH RESEND v2 2/3] osdep: Rename qemu_{get, set}_version() to qemu_{, set_}hw_version() Eduardo Habkost
2015-10-30 19:36 ` [Qemu-devel] [PATCH RESEND v2 3/3] megasas: Use qemu_hw_version() instead of QEMU_VERSION Eduardo Habkost
2015-11-02 11:55 ` [Qemu-devel] [PATCH RESEND v2 0/3] pc: Set hw_version on all machine classes Paolo Bonzini
2015-11-09 20:46 ` Michael S. Tsirkin
2015-11-10 15:01 ` Paolo Bonzini
2015-11-10 15:44 ` Michael S. Tsirkin
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=20151109222208-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel.a@redhat.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 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).